Menu
▾
▴
mkdump-devel — discuss mkdump development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(16) |
Feb
|
Mar
(3) |
Apr
(6) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(8) |
Mar
|
Apr
|
May
(11) |
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(2) |
Nov
|
Dec
(3) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: skunk <sk...@le...> - 2005-03-09 02:30:44
|
hi all! i'm having some troubles with a isp server and want to get a kernel backtrace to work on... i don't have free disk space for an extra dump partitition, so i specified the swap partitition in /proc/mkexec/dumpdev and commented out the swap partitition from /etc/fstab so it won't automatically activated at boot time... is there something wrong with this setup? will i get a useful dump at next kernel panik? where can i find the tools necessary for extracting the dump from my swap partitition? thank you! |
|
From: panxj <xue...@io...> - 2005-01-26 09:35:12
|
Thanks very much for your help! > > > (2)When the disk is full, the tool doesn't generate a > > warning, but also print write success > What is this "tool"? Is it mini-kernel? > ennenen Mr. Itsuro Oda has supplied me a tool that could convert the format of mkdump to the format of lkcd. Here I refers to this mkd2lkcd tool. > > (3)Why the memery end is always 0xa8190173618f23ed? > Which tool outputs this address?$B!!(BWhen does it output? > When I have converted the format and used lcrash to analyse the dumpfile. I typed #lcrash -i -d dumpfile then lcrash displayed the dump header of dump file. The "memory end" is one of these informations. Sincerely yours Xuejian Pan |
|
From: Chiyohiko M. <mo...@va...> - 2005-01-25 04:39:02
|
Hi, I am sorry to delay response. Instead of Mr. Itsuro Oda, I write a reply. > Dear Dr. Itsuro Oda: > I have converted the minik dump to the lkcd format. > However, there are three problems: (1)How can I > get the Kerntypes for the lcrash? I have patched the > lkcd-6.1.0_2.6.9.patch for my kernel and then compiled, but > can't find the kerntypes file. How can it be generated? With the old LKCD patch of a version, the portion of crash dumping and the portion which generates kerntypes file had been independent. With the patch of the present version, the portion which generates kerntypes file has not been independent. Attached is a tool to generate kerntypes file.(for your evaluation) (Tool of the attached file is not perfect. ) > (2)When the disk is full, the tool doesn't generate a > warning, but also print write success What is this "tool"? Is it mini-kernel? > (3)Why the memery end is always 0xa8190173618f23ed? Which tool outputs this address? When does it output? > Thank you very much. > > Sincerely yours > Xuejian Pan > > In the following, hello is the converted file, and we have no > /boot/Kerntypes-2.6.9-mkexec-b3 at all( we can't make it) > > > > [root@mid mkd2lkcd]# lcrash -d hello > lcrash 0.10.2 (xlcrash) build at Jan 22 2005 13:14:10 > Lcrash is free software. It is covered by the GNU General > Public License. You are welcome to change it and/or > distribute copies of it under certain conditions. Type "help > -C" to see the conditions. Absolutely no warranty is given > for Lcrash. Type "help -W" for warranty details. > > map = /boot/System.map-2.6.9-mkexec-b3 > dump = hello > kerntypes = /boot/Kerntypes-2.6.9-mkexec-b3 > > > Please wait... > Check dump architecture: > Dump arch set. > > Initializing host arch data ... Done. > Initializing dump access data... Done. > Opening dump for access... Done. > Loading type info (Kerntypes) > ...check_namelist_format: open on namelist file failed > > > > --__--__-- > > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel -- Chiyohiko Morita <mo...@va...> |
|
From: Chiyohiko M. <mo...@va...> - 2005-01-25 03:01:23
|
Hellow, Regrettably swap area is not extracted by minik. It is possible to extract swap area by the dd command.(After reboot, before becoming swap-on) However, there is no tool which analyzes it. Thank you. > Dear Sir, > I have successful extract the LKCD format dump from dumping > device and analyse kernel with lcrash. > Is it possible to get swap dump using minkdump and use it to > analyse application after rebooting. > > Sincerely yours > xuejian pan > > > > --__--__-- > > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel |
|
From: panxj <xue...@io...> - 2005-01-23 13:45:12
|
Dear Sir,
I have successful extract the LKCD format dump from dumping
device and analyse kernel with lcrash.
Is it possible to get swap dump using minkdump and use it to
analyse application after rebooting.
Sincerely yours
xuejian pan
|
|
From: panxj <xue...@io...> - 2005-01-22 15:01:47
|
Dear Dr. Itsuro Oda:
I have converted the minik dump to the lkcd format. However, there are three problems: (1)How can I get the Kerntypes for the lcrash? I have patched the lkcd-6.1.0_2.6.9.patch for my kernel and then compiled, but can't find the kerntypes file. How can it be generated?
(2)When the disk is full, the tool doesn't generate a warning, but also print write success
(3)Why the memery end is always 0xa8190173618f23ed?
Thank you very much.
Sincerely yours
Xuejian Pan
In the following, hello is the converted file, and we have no /boot/Kerntypes-2.6.9-mkexec-b3
at all( we can't make it)
[root@mid mkd2lkcd]# lcrash -d hello
lcrash 0.10.2 (xlcrash) build at Jan 22 2005 13:14:10
Lcrash is free software. It is covered by the GNU General Public License.
You are welcome to change it and/or distribute copies of it under certain
conditions. Type "help -C" to see the conditions. Absolutely no warranty
is given for Lcrash. Type "help -W" for warranty details.
map = /boot/System.map-2.6.9-mkexec-b3
dump = hello
kerntypes = /boot/Kerntypes-2.6.9-mkexec-b3
Please wait...
Check dump architecture:
Dump arch set.
Initializing host arch data ... Done.
Initializing dump access data... Done.
Opening dump for access... Done.
Loading type info (Kerntypes) ...check_namelist_format: open on namelist file failed
|
|
From: Itsuro O. <od...@va...> - 2005-01-22 12:32:43
|
Hi, The dump format of the mini kernel dump is not same as the format of the lkcd. A conversion tool is need. Attached is the conversion tool (i386 only). (for your evaluation) Note that the conversion tools are under development and not released officially yet. Thank you. On Sat, 22 Jan 2005 15:04:16 +0800 panxj <xue...@io...> wrote: > Dear Dr. Oda, > I have successfully let mink dumped > to my block device /dev/hdb11 for example. > But there is a problem to handle it with > lcrash. (unrecognized header) > It has been mentioned that there is a > tool to convert from minik format to > lkcd format. Can you give that tool to me. > > Sinerely yours > Xuejian Pan > > Following is my terminal output: > > [root@localhost root]# ls > anaconda-ks.cfg install.log install.log.syslog tmp > [root@localhost root]# lcrash -d /dev/hdb11 > lcrash 0.10.2 (xlcrash) build at Jan 22 2005 13:14:10 > Lcrash is free software. It is covered by the GNU General Public License. > You are welcome to change it and/or distribute copies of it under certain > conditions. Type "help -C" to see the conditions. Absolutely no warranty > is given for Lcrash. Type "help -W" for warranty details. > > map = /boot/System.map-2.6.9-mkexec-b3 > dump = /dev/hdb11 > kerntypes = /boot/Kerntypes-2.6.9-mkexec-b3 > > > Please wait... > Check dump architecture: > invalid dump header in dump > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel -- Itsuro ODA <od...@va...> |
|
From: panxj <xue...@io...> - 2005-01-22 07:04:32
|
Dear Dr. Oda,
I have successfully let mink dumped
to my block device /dev/hdb11 for example.
But there is a problem to handle it with
lcrash. (unrecognized header)
It has been mentioned that there is a
tool to convert from minik format to
lkcd format. Can you give that tool to me.
Sinerely yours
Xuejian Pan
Following is my terminal output:
[root@localhost root]# ls
anaconda-ks.cfg install.log install.log.syslog tmp
[root@localhost root]# lcrash -d /dev/hdb11
lcrash 0.10.2 (xlcrash) build at Jan 22 2005 13:14:10
Lcrash is free software. It is covered by the GNU General Public License.
You are welcome to change it and/or distribute copies of it under certain
conditions. Type "help -C" to see the conditions. Absolutely no warranty
is given for Lcrash. Type "help -W" for warranty details.
map = /boot/System.map-2.6.9-mkexec-b3
dump = /dev/hdb11
kerntypes = /boot/Kerntypes-2.6.9-mkexec-b3
Please wait...
Check dump architecture:
invalid dump header in dump
|
|
From: Chiyohiko M. <mo...@va...> - 2005-01-07 06:51:41
|
Hello,
I thought about the cause to which the system did reboot without giving the
message.
Two reasons that the system reboots are thought.
1) Mini-kernel cannot use initrd. Are not you using initrd?
2) The memory of mini-kernel doesn't suffice.
In 1), please change a configuration not to use initrd.
Please try the following, if 2) is thought.
- Please make the smallest possible kernel.
- The value of "/proc/mkexec/mem" is enlarged.
Example :
#echo 8 > /proc/mkexec/mem
There is a proposal for outputting a message.
Please pass a parameter to mini-kernel.
Example :
#echo "console=tty0 console=ttyS0,9600n8r" > /proc/mkexec/parameter
A possibility that a problem is in mini-kernel is high.
Please send the configuration file (.config) of mini-kernel.
Thanks.
--
Chiyohiko Morita <mo...@va...>
|
|
From: panxj <xue...@io...> - 2005-01-06 08:46:07
|
Hi, I used /dev/hda7 as the dumping partition: # ll /dev/hda7 brw-rw---- 1 root disk 3, 7 2004-02-24 /dev/hda7 and then typed the following commands: #echo 4 > /proc/mkexec/mem #echo "0x300007" > /proc/mkexec/dumpdev #echo "/boot/vmlinux.bin" > /proc/mkexec/path #echo 1 > /proc/mkexec/stats Here is the result of "cat /proc/mkexec/*" : 0x300007 4 /boot/vmlinux.bin 1 When I tested the dump: echo 2>/proc/mkexec/stats The system restarted without any message putting in the screen After restarting , I checked the files /var/log/debug and /var/log/messages, there seemed nothing about the mkexec. Help me please, thanks a lot! On Thu, 06 Jan 2005 11:27:00 +0900 Itsuro Oda <od...@va...> wrote: > Hi, > > Maybe the mini kernel is incorrect. Plese let me know the detail > operations you did. (and the log of "cat /proc/mkexec/*" before doing > "echo 2 > /proc/mkexec/stats") > > Thanks. > > >Sorry, there was no message when I typed the command: > ># echo 2 > /proc/mkexec/stats > >The system standed for a while, and then suddenly rebooted. > >What else should I be seeing about in the dumping test? > >Thanks a lot! > -- > Itsuro ODA <od...@va...> > > |
|
From: Itsuro O. <od...@va...> - 2005-01-06 02:27:04
|
Hi, Maybe the mini kernel is incorrect. Plese let me know the detail operations you did. (and the log of "cat /proc/mkexec/*" before doing "echo 2 > /proc/mkexec/stats") Thanks. >Sorry, there was no message when I typed the command: ># echo 2 > /proc/mkexec/stats >The system standed for a while, and then suddenly rebooted. >What else should I be seeing about in the dumping test? >Thanks a lot! -- Itsuro ODA <od...@va...> |
|
From: panxj <xue...@io...> - 2005-01-06 01:03:55
|
Sorry, there was no message when I typed the command: # echo 2 > /proc/mkexec/stats The system standed for a while, and then suddenly rebooted. What else should I be seeing about in the dumping test? Thanks a lot! On Thu, 06 Jan 2005 08:34:25 +0900 Itsuro Oda <od...@va...> wrote: > Hi, > > If you looked like the following message at the end of the mini kernel, > it was success. > > --- > ...(kernel initializing messages) > Dump start. dump device = 300007 > dumping pfn 0 - fbf7f (1032064 pages) > ................................................................................ > ................................................................................ > (...) > ................................................................................ > ................................................................ > Dump done. > Shutdown: hda > System reboot. > --- > > How about you? > > It is better to use a sirial console that saves console massages to analyze > problems. Please try. > > Thanks. > > On Wed, 5 Jan 2005 14:17:55 +0800 > panxj <xue...@io...> wrote: > > > Thank you」。 > > I did everything as you say」ャ and when I typed > > # echo 2 > /proc/mkexec/stats > > the mini kernel seemed starting ,and the system rebooted after a while > > But I could see nothing in the partition > > Is there anything else I should do before testing the dump? > > > > > > -- > Itsuro ODA <od...@va...> > > |
|
From: Itsuro O. <od...@va...> - 2005-01-06 00:37:09
|
Hi, A Happy new year. We released the Beta-3 version of mkdump end of last year. We checked the code from crash occur to the mini kernel start carefully and eliminate the possibility of the deadlock/hang condition. (We hope :-)) Please check it. http://mkdump.sourceforge.net/ -- Itsuro ODA <od...@va...> |
|
From: Itsuro O. <od...@va...> - 2005-01-05 23:34:35
|
Hi, If you looked like the following message at the end of the mini kernel, it was success. --- ...(kernel initializing messages) Dump start. dump device = 300007 dumping pfn 0 - fbf7f (1032064 pages) ................................................................................ ................................................................................ (...) ................................................................................ ................................................................ Dump done. Shutdown: hda System reboot. --- How about you? It is better to use a sirial console that saves console massages to analyze problems. Please try. Thanks. On Wed, 5 Jan 2005 14:17:55 +0800 panxj <xue...@io...> wrote: > Thank you」。 > I did everything as you say」ャ and when I typed > # echo 2 > /proc/mkexec/stats > the mini kernel seemed starting ,and the system rebooted after a while > But I could see nothing in the partition > Is there anything else I should do before testing the dump? > > -- Itsuro ODA <od...@va...> |
|
From: panxj <xue...@io...> - 2005-01-05 06:17:59
|
Thank you！ I did everything as you say， and when I typed # echo 2 > /proc/mkexec/stats the mini kernel seemed starting ,and the system rebooted after a while But I could see nothing in the partition Is there anything else I should do before testing the dump? On Wed, 05 Jan 2005 11:22:34 +0900 Itsuro Oda <od...@va...> wrote: > Hi, > > For example you use /dev/hda7 as a dump device, type "ls -l /dec/hda7" > # ls -l /dev/hda7 > brw-rw---- 1 root disk 3, 7 Jul 1 2004 /dev/hda7 > # > The device number is "0x300007". > > Of course you should prepare a dump device (a disk partition) in > advance. > > Thanks. > > On Sun, 2 Jan 2005 15:37:54 +0800 > panxj <xue...@io...> wrote: > > > Dear all: > > I'm trying this tool now, but don't know where to get the dumpping result. In the mkexec README ,there are following lines: > > # echo "0x800012" > /proc/mkexec/dumpdev > > specify the device number of the dump device. higher 12 bit is major, lower 20 bit is minor. check device number of your device to use "ls -l". > > > > Should I create the device myself? And what's the parameter of the new device? > > > > Thanks a lot! > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > Mkdump-devel mailing list > > Mkd...@li... > > https://lists.sourceforge.net/lists/listinfo/mkdump-devel > > -- > Itsuro ODA <od...@va...> > > |
|
From: Itsuro O. <od...@va...> - 2005-01-05 02:22:36
|
Hi, For example you use /dev/hda7 as a dump device, type "ls -l /dec/hda7" # ls -l /dev/hda7 brw-rw---- 1 root disk 3, 7 Jul 1 2004 /dev/hda7 # The device number is "0x300007". Of course you should prepare a dump device (a disk partition) in advance. Thanks. On Sun, 2 Jan 2005 15:37:54 +0800 panxj <xue...@io...> wrote: > Dear all: > I'm trying this tool now, but don't know where to get the dumpping result. In the mkexec README ,there are following lines: > # echo "0x800012" > /proc/mkexec/dumpdev > specify the device number of the dump device. higher 12 bit is major, lower 20 bit is minor. check device number of your device to use "ls -l". > > Should I create the device myself? And what's the parameter of the new device? > > Thanks a lot! > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel -- Itsuro ODA <od...@va...> |
|
From: panxj <xue...@io...> - 2005-01-02 07:38:02
|
Dear all: I'm trying this tool now, but don't know where to get the dumpping result. In the mkexec README ,there are following lines: # echo "0x800012" > /proc/mkexec/dumpdev specify the device number of the dump device. higher 12 bit is major, lower 20 bit is minor. check device number of your device to use "ls -l". Should I create the device myself? And what's the parameter of the new device? Thanks a lot! |
|
From: Itsuro O. <od...@va...> - 2004-12-13 08:55:47
|
Hi, I am sorry to delay response. (due to unfamiliar with SourceForge.net) > 1) Is there a plan to backport this function to 2.4 kernel? We don't have a plan to backport this function to 2.4 kernel. But Yotam have done that. So we will include the function for 2.4 kernel based his code in future release. > - 64GB High Memory, It should be OK. For x86_64, we have tested with 8GB and work well. For i386, we have not tested over 2GB memory yet. > - HIGHMEMORY I/O, It is independent with the mini kernel dump function. > - 4GB Kernel-space$B!!(Band 4GBUser-space virtual memory We don't support the 4G/4G split system. > SMP It should be OK. But it is not stable yet. It will be fix the next release. (end of December hopefully) > > Regards > Hiroshi Nakano Thank you. -- Itsuro ODA <od...@va...> |
|
From: Itsuro O. <od...@va...> - 2004-12-09 23:22:56
|
Hi, Thank you for your cooperation. We will check promptly. Thanks. On Thu, 9 Dec 2004 16:36:56 +0200 Yotam Medini <yo...@ql...> wrote: > > With some help of colleagues, > I have back-ported Mini-Kernel-Dump 2.6.6-0.2 to Linux 2.4. > > Since Linux 2.4 is still widely used in production sites, > I think it would be beneficial, to have this functionality > merged in future releases of Mini-Kernel Dump. > > The attached tar.gz file consists of > yotamm@yotamm:+/minikernel:702> tar tvfz mkd-bp24-2004-12-09.tgz > -rw-rw-r-- yotamm/yotamm 8235 2004-12-09 16:08:41 mkd-2.6.6-0.2-backport24k.patch > -rw-rw-r-- yotamm/yotamm 29949 2004-12-09 15:10:45 mkd-2.6.6-0.2-backport24m.patch > > Where > + mkd-2.6.6-0.2-backport24k.patch is a 'manual' port of > some 'home' grown _variant_ of kernel 2.4.18. > + mkd-2.6.6-0.2-backport24m.patch is diffs of the mkexec module. > > Probably the biggest change to Kernel 2.4 is include/linux/mmzone.h > /* #define MAX_ORDER 10 --> 11*/ > #define MAX_ORDER 11 /* for minikernel-dump */ > > -- yotam > -- Itsuro ODA <od...@va...> |
|
From: Yotam M. <yo...@ql...> - 2004-12-09 14:39:05
|
With some help of colleagues, I have back-ported Mini-Kernel-Dump 2.6.6-0.2 to Linux 2.4. Since Linux 2.4 is still widely used in production sites, I think it would be beneficial, to have this functionality merged in future releases of Mini-Kernel Dump. The attached tar.gz file consists of yotamm@yotamm:+/minikernel:702> tar tvfz mkd-bp24-2004-12-09.tgz -rw-rw-r-- yotamm/yotamm 8235 2004-12-09 16:08:41 mkd-2.6.6-0.2-backport24k.patch -rw-rw-r-- yotamm/yotamm 29949 2004-12-09 15:10:45 mkd-2.6.6-0.2-backport24m.patch Where + mkd-2.6.6-0.2-backport24k.patch is a 'manual' port of some 'home' grown _variant_ of kernel 2.4.18. + mkd-2.6.6-0.2-backport24m.patch is diffs of the mkexec module. Probably the biggest change to Kernel 2.4 is include/linux/mmzone.h /* #define MAX_ORDER 10 --> 11*/ #define MAX_ORDER 11 /* for minikernel-dump */ -- yotam |
|
From: Itsuro O. <od...@va...> - 2004-12-01 23:58:58
|
Hi, Attached is the conversion tool (i386 only). (for your evaluation) Note that the conversion tools are under development and not released officially yet. Thank you. On Wed, 1 Dec 2004 11:09:15 +0200 Yotam Medini <yo...@ql...> wrote: > > Hello MkDump group, > > In http://mkdump.sourceforge.net/ it says: > We also have prepared a tool which allows for the copied crash dump to > be converted to the LKCD or netdump format. This is a very simple conversion. > Could you please point me to this tool? > > Thanks -- yotam > -- Itsuro ODA <od...@va...> |
|
From: Yotam M. <yo...@ql...> - 2004-12-01 09:09:32
|
Hello MkDump group, In http://mkdump.sourceforge.net/ it says: We also have prepared a tool which allows for the copied crash dump to be converted to the LKCD or netdump format. This is a very simple conversion. Could you please point me to this tool? Thanks -- yotam |
|
From: Hiroshi N. <h-n...@ps...> - 2004-10-25 11:44:23
|
Hello, I also want to know whether this function tested on SMP system. (I do not have available SMP machine also now, I'm sorry). Regards Hiroshi Nakano > Hello, > > I have following questions about this function (Mini Kernel dump): > > 1) Is there a plan to backport this function to 2.4 kernel? > 2) Is this function available(/tested) under the following configuration? > - 64GB High Memory, > - HIGHMEMORY I/O, > - 4GB Kernel-space and 4GBUser-space virtual memory > > I'd like to check these, but I don't have available machine to > confirm this, now. If it had already been tested, I would like to > know whether it has been tested or not. > Thank you beforehand. > > Regards > Hiroshi Nakano > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel > |
|
From: Hiroshi N. <h-n...@ps...> - 2004-10-25 11:24:23
|
Hello, I have following questions about this function (Mini Kernel dump): 1) Is there a plan to backport this function to 2.4 kernel? 2) Is this function available(/tested) under the following configuration? - 64GB High Memory, - HIGHMEMORY I/O, - 4GB Kernel-space and 4GBUser-space virtual memory I'd like to check these, but I don't have available machine to confirm this, now. If it had already been tested, I would like to know whether it has been tested or not. Thank you beforehand. Regards Hiroshi Nakano |
1 message has been excluded from this view by a project administrator.
