Does it necessary to code network parameter in this. On Thu, Aug 25, 2011 at 6:28 PM, Raymond Higgs <rayhi...@us.ibm.com> wrote:
> Your netmask and network aren't consistent. > > NETMASK=255.255.248.0 > NETWORK=10.241.1.0 > > If the network is correct, shouldn't the netmask be 255.255.255.0 ? > > Regards, > > Ray Higgs > System z FCP Firmware Development > Bld. 706, B42 > 2455 South Road > Poughkeepsie, NY 12601 > (845) 435-8666, T/L 295-8666 > rayhi...@us.ibm.com > > Linux on 390 Port <LINUX-390@vm.marist.edu> wrote on 08/25/2011 02:50:41 > AM: > > > From: saurabh khandelwal <sourabhkhandelwal...@gmail.com> > > To: LINUX-390@vm.marist.edu > > Date: 08/25/2011 02:55 AM > > Subject: Re: Mount error - Network config problem > > Sent by: Linux on 390 Port <LINUX-390@vm.marist.edu> > > > > Thanks to all for solving the problem. There was two logical volume and > I > > was able to monut and created network config. Then I bring down the > > sles9sp2 and unmobut the sles10 logical disk. > > > > Then I bring sles10 z/linux up but its it not taking the netwokr > > configuration. > > > > > > > > sles10:/etc/sysconfig/network # ls > > ls > > bkp-ifcfg-qeth-bus-ccw-0.0.0468 ifcfg-qeth-bus-ccw-0.0.0468 > > config ifcfg.template > > dhcp ifroute-lo > > if-down.d ifservices.template > > if-up.d providers > > ifcfg-eth0 routes > > ifcfg-lo scripts > > sles10:/etc/sysconfig/network # > > > > > > I modified the ifcfg-qeth-bus-ccw-0.0.0468 file and route file for > netwokr > > configuration > > > > > > sles10:/etc/sysconfig/network # cat ifcfg-qeth-bus-ccw-0.0.0468 > > cat ifcfg-qeth-bus-ccw-0.0.0468 > > BOOTPROTO=STATIC > > IPADDR=10.241.1.193 > > STARTMODE=ONBOOT > > NETMASK=255.255.248.0 > > NETWORK=10.241.1.0 > > BROADCAST=10.241.1.255 > > _nm_name=qeth-bus-ccw-0.0.0468 > > sles10:/etc/sysconfig/network # > > > > > > sles10:/etc/sysconfig/network # cat routes > > cat routes > > default 10.241.0.1 - - > > sles10:/etc/sysconfig/network # > > > > > > > > sles10:/etc/sysconfig/network # ifconfig > > ifconfig > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:10 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:652 (652.0 b) TX bytes:652 (652.0 b) > > > > sles10:/etc/sysconfig/network # > > > > > > looks like system is not able to pick the netowrk configuration file.. > Can > > you please help with points that where i am making mistake. > > > > Thanks & Regards > > Saurabh > > > > On Thu, Aug 25, 2011 at 12:43 AM, Scott Rohling > > <scott.rohl...@gmail.com>wrote: > > > > > Sorry - try 'vgdisplay -v system' -- this should show the logical > volumes > > > and also the disks that make up the volumes. And there is also > 'lvscan' to > > > see logical volumes. > > > > > > Let's say that you see there is a 'root' logical volume -- then to > mount: > > > > > > mount /dev/system/root /mnt > > > > > > Scott Rohling > > > > > > On Wed, Aug 24, 2011 at 12:55 PM, saurabh khandelwal < > > > sourabhkhandelwal...@gmail.com> wrote: > > > > > > > I have followed the sugged way to find out, if these disk are part > of > > > LVM. > > > > > > > > O/P of command issued > > > > > > > > sles9sp2:~ # pvscan > > > > pvscan > > > > PV /dev/dasdl1 VG system lvm2 -2.29 GB / 0 free- > > > > PV /dev/dasdm1 VG system lvm2 -2.29 GB / 0 free- > > > > Total: 2 -4.58 GB- / in use: 2 -4.58 GB- / in no VG: 0 -0 - > > > > sles9sp2:~ # > > > > > > > > > > > > sles9sp2:~ # vgscan > > > > vgscan > > > > Reading all physical volumes. This may take a while... > > > > Found volume group "system" using metadata type lvm2 > > > > sles9sp2:~ # > > > > > > > > > > > > > > > > then I activted this LVM and > > > > > > > > sles9sp2:~ # vgdisplay > > > > vgdisplay > > > > --- Volume group --- > > > > VG Name system > > > > System ID > > > > Format lvm2 > > > > Metadata Areas 2 > > > > Metadata Sequence No 3 > > > > VG Access read/write > > > > > > > > VG Status resizable > > > > MAX LV 0 > > > > Cur LV 2 > > > > Open LV 0 > > > > Max PV 0 > > > > Cur PV 2 > > > > Act PV 2 > > > > VG Size 4.58 GB > > > > PE Size 4.00 MB > > > > Total PE 1172 > > > > Alloc PE / Size 1172 / 4.58 GB > > > > Free PE / Size 0 / 0 > > > > VG UUID kKrkDt-61J0-GnEs-ei7T-vabU-NDNo-pZxQsN > > > > > > > > sles9sp2:~ # > > > > > > > > > > > > > > > > Can you please suggest, now what will the the command to mount and > which > > > > logical volume has to be monut > > > > > > > > Thanks & Regards > > > > Saurabh > > > > > > > > > > > > On Wed, Aug 24, 2011 at 11:58 PM, Scott Rohling > <scott.rohl...@gmail.com > > > > >wrote: > > > > > > > > > Do a 'pvscan' and 'vgscan' to see if these are actually disks > belonging > > > > to > > > > > an LVM -- you won't be able to mount these directly... If you > find > > > > the > > > > > disks are an LVM -- (let's say it's called 'system'): > > > > > > > > > > vgchange -ay system (activate the LVM) > > > > > > > > > > Then you can vgdisplay system and figure out what logical volume > you > > > can > > > > > mount. > > > > > > > > > > If you already use LVM on the system you are linking the disks > from and > > > > use > > > > > the same names -- then you won't be able to mount since they are > > > > > duplicates. > > > > > > > > > > Scott Rohling > > > > > > > > > > On Wed, Aug 24, 2011 at 12:18 PM, saurabh khandelwal < > > > > > sourabhkhandelwal...@gmail.com> wrote: > > > > > > > > > > > Hello Ron, > > > > > > The problem is I don't know in which volume > /etc is > > > > > > mounted in the for the sles10 mini disk. I am really confused > that > > > Why > > > > I > > > > > > am > > > > > > able to mount only first disk of sles10. But rest of the sles10 > mini > > > > disk > > > > > I > > > > > > am bot able to mount and getting error. device number 300 to > 304 > > > > belong > > > > > to > > > > > > sles10 system. > > > > > > > > > > > > Below is the output of lsdasd command from sles9sp2 system. > > > > > > > > > > > > 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize > 4096, > > > > > > 1802880 bl > > > > > > ocks, 7042 MB > > > > > > 0.0.0300(ECKD) at ( 94: 40) is dasdk : active at blocksize > 4096, > > > > > > 600840 > > > > > > blo > > > > > > cks, 2347 MB > > > > > > 0.0.0301(ECKD) at ( 94: 44) is dasdl : active at blocksize > 4096, > > > > > > 600840 > > > > > > blo > > > > > > cks, 2347 MB > > > > > > 0.0.0302(ECKD) at ( 94: 48) is dasdm : active at blocksize > 4096, > > > > > > 600840 > > > > > > blo > > > > > > cks, 2347 MB > > > > > > 0.0.0303(ECKD) at ( 94: 52) is dasdn : active at blocksize > 4096, > > > > > > 600840 > > > > > > blo > > > > > > cks, 2347 MB > > > > > > 0.0.0304(ECKD) at ( 94: 56) is dasdo : active at blocksize > 4096, > > > > > > 600840 > > > > > > blo > > > > > > cks, 2347 MB > > > > > > > > > > > > > > > > > > Also when I am trying to monut these dasd, I am getting below > error > > > > > > > > > > > > sles9sp2:~ # mount /dev/dasdl1 /d1 > > > > > > mount /dev/dasdl1 /d1 > > > > > > mount: /dev/dasdl1 already mounted or /d1 busy > > > > > > > > > > > > > > > > > > sles9sp2:~ # mount /dev/dasdm1 /d1 > > > > > > mount /dev/dasdm1 /d1 > > > > > > mount: /dev/dasdm1 already mounted or /d1 busy > > > > > > > > > > > > > > > > > > sles9sp2:~ # mount /dev/dasdn1 /d1 > > > > > > mount /dev/dasdn1 /d1 > > > > > > FAT: bogus number of reserved sectors > > > > > > VFS: Can't find a valid FAT filesystem on dev dasdn1. > > > > > > Aug 24 11:14:42 sles9sp2 kernel: FAT: bogus number of reserved > > > sectors > > > > > > Aug 24 11:14:42 sles9sp2 kernel: VFS: Can't find a valid FAT > > > filesystem > > > > > on > > > > > > dev d > > > > > > asdn1. > > > > > > mount: you must specify the filesystem type > > > > > > > > > > > > > > > > > > sles9sp2:~ # mount /dev/dasdo1 /d1 > > > > > > mount /dev/dasdo1 /d1 > > > > > > FAT: bogus number of reserved sectors > > > > > > VFS: Can't find a valid FAT filesystem on dev dasdo1. > > > > > > Aug 24 11:15:07 sles9sp2 kernel: FAT: bogus number of reserved > > > sectors > > > > > > Aug 24 11:15:07 sles9sp2 kernel: VFS: Can't find a valid FAT > > > filesystem > > > > > on > > > > > > dev d > > > > > > asdo1. > > > > > > mount: you must specify the filesystem type > > > > > > > > > > > > Output of df -h from sles9sp2 > > > > > > > > > > > > > > > > > > sles9sp2:~ # df -h > > > > > > df -h > > > > > > Filesystem Size Used Avail Use% Mounted on > > > > > > /dev/dasda1 6.8G 1.9G 4.7G 29% / > > > > > > tmpfs 1002M 4.0K 1002M 1% /dev/shm > > > > > > > > > > > > > > > > > > > > > > > > Can you please help me why output is showing me that /dev/dasdl1 > > > > already > > > > > > mounted or /d1 busy. I dont see anything is mounted in /d1 > > > > > > > > > > > > > > > > > > Thanks & Regards > > > > > > Saurabh > > > > > > > > > > > > On Wed, Aug 24, 2011 at 7:09 PM, Ron Foster at Baldor-IS < > > > > > > rfos...@baldor.com > > > > > > > wrote: > > > > > > > > > > > > > Saurabh, > > > > > > > > > > > > > > First we need to determine if you really need to reach out > from one > > > > > Linux > > > > > > > system to fix another Linux system. > > > > > > > > > > > > > > At some point in the life of SLES, it became possible to put > an > > > > > > appropriate > > > > > > > entry in the /etc/inittab. That entry allowes you to access > the > > > > ASCII > > > > > > > console emulator that is a part of the HMC. If your system is > at > > > the > > > > > > > appropriate SLES level, and you have the appropriate entry in > > > > > > /etc/inittab, > > > > > > > and the only problem you are having is the fact that TCP/IP is > not > > > > up, > > > > > > then > > > > > > > you will have a way to use vi and YaST to fix your problem. > > > > > > > > > > > > > > The entry is: > > > > > > > #zVM 5.3 Guest ASCII Console Support > > > > > > > cn:2345:respawn:/sbin/agetty -L 9600 ttyS1 xterm > > > > > > > > > > > > > > In order for a guest to access the console, someone have to > issue > > > the > > > > > > > following command: > > > > > > > > > > > > > > att sysa to linuxguest > > > > > > > > > > > > > > (where linux guest is the machine you are attaching the > console > > > to.) > > > > > > > > > > > > > > Then navigate to your z/VM LPAR on the HMC and start the ASCII > > > > console. > > > > > > > Hit enter a couple of times and you should get a Linux logon > > > prompt. > > > > > > > > > > > > > > But if you cannot use that method... > > > > > > > You have to know a little bit about the how your filesystems > are > > > > > > structured > > > > > > > to do this. > > > > > > > > > > > > > > Just a thought, in zLinux, yes you have to make volumes > available > > > so > > > > > that > > > > > > > they are online, but you mount filesystems. If you are using > LVM, > > > > then > > > > > > one > > > > > > > mount can access filesystems on more than one volume. > > > > > > > > > > > > > > Is either one of the systems using LVM? We happen to use LVM > on > > > our > > > > > boot > > > > > > > volume, so we have had to construct a special Linux guest that > does > > > > not > > > > > > run > > > > > > > LVM in order perform a task like this. In our case, our > mounts > > > that > > > > we > > > > > > use > > > > > > > looks like this. > > > > > > > > > > > > > > mount -v -t reiserfs /dev/system/root /mnt > > > > > > > mount -v -t ext2 /dev/dasda1 /mnt/boot > > > > > > > mount -v -t reiserfs /dev/system/home /mnt/home > > > > > > > mount -v -t reiserfs /dev/system/opt /mnt/opt > > > > > > > mount -v -t reiserfs /dev/system/tmp /mnt/tmp > > > > > > > mount -v -t reiserfs /dev/system/usr /mnt/usr > > > > > > > mount -v -t reiserfs /dev/system/var /mnt/var > > > > > > > > > > > > > > (Notice the mounts must contain the type of filesystem you are > > > > using.) > > > > > > > > > > > > > > First you mount the root (/) filesystem. In this case, it is > an > > > LVM, > > > > > and > > > > > > > we mount it to /mnt. > > > > > > > (mnt is where the other systems disks will start to appear.) > > > > > > > Next we mount the /boot filesystem at /mnt/boot. > > > > > > > > > > > > > > Now due to the way we have structured things, we then have to > mount > > > > our > > > > > > > /home, /opt, /tmp, /var, /usr, and /var > > > > > > > filesystems. > > > > > > > > > > > > > > Once we get done, then the "other systems drives" are > available > > > from > > > > a > > > > > > > directory structure in /mnt. The local > > > > > > > system, is available from a directory structure in /. > > > > > > > > > > > > > > How did you all set up things? Did you all use LVM? > > > > > > > > > > > > > > If you did not use LVM, then you have to know that /mnt should > be > > > > > mounted > > > > > > > to a particular partition. > > > > > > > > > > > > > > Hope this helps, > > > > > > > Ron > > > > > > > > > > > > > > > > > > > > > > > > > > > > When you booted the > > > > > > > > > > > > > > ________________________________________ > > > > > > > From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of > > > > saurabh > > > > > > > khandelwal [sourabhkhandelwal...@gmail.com] > > > > > > > Sent: Wednesday, August 24, 2011 1:38 AM > > > > > > > To: LINUX-390@VM.MARIST.EDU > > > > > > > Subject: Mount error > > > > > > > > > > > > > > Hello, > > > > > > > I have two z/linux system.In both tcpip is not working. so > Iogged > > > on > > > > > one > > > > > > > z/linux in 3270 session and copied all disk of another linux > to > > > this > > > > > > linux > > > > > > > user directory. > > > > > > > now I want to change the network config of the another linux > by > > > > > mounting > > > > > > > the > > > > > > > another Linux disk here.I made that another Linux down,so that > this > > > > > linux > > > > > > > have r/w access to its dasd. > > > > > > > > > > > > > > Output of LSDAD in another linux, where I monut 5 dasd of the > > > another > > > > > > > linux. > > > > > > > > > > > > > > > > > > > > > lsdasd > > > > > > > 0.0.0200(ECKD) at ( 94: 0) is dasda : active at > blocksize > > > 4096, > > > > > > > 1802880 bl > > > > > > > ocks, 7042 MB > > > > > > > 0.0.0300(ECKD) at ( 94: 40) is dasdk : active at > blocksize > > > 4096, > > > > > > > 600840 > > > > > > > blo > > > > > > > cks, 2347 MB > > > > > > > 0.0.0301(ECKD) at ( 94: 44) is dasdl : active at > blocksize > > > 4096, > > > > > > > 600840 > > > > > > > blo > > > > > > > cks, 2347 MB > > > > > > > 0.0.0302(ECKD) at ( 94: 48) is dasdm : active at > blocksize > > > 4096, > > > > > > > 600840 > > > > > > > blo > > > > > > > cks, 2347 MB > > > > > > > 0.0.0303(ECKD) at ( 94: 52) is dasdn : active at > blocksize > > > 4096, > > > > > > > 600840 > > > > > > > blo > > > > > > > cks, 2347 MB > > > > > > > 0.0.0304(ECKD) at ( 94: 56) is dasdo : active at > blocksize > > > 4096, > > > > > > > 600840 > > > > > > > blo > > > > > > > cks, 2347 MB > > > > > > > sles9sp2:~ # > > > > > > > > > > > > > > Out of these dasd 300-304 is from another linux, which I am > trying > > > to > > > > > > monut > > > > > > > here. > > > > > > > > > > > > > > > > > > > > > now when I am trying to monut the dasd . I was able to monut > the > > > > first > > > > > > dasd > > > > > > > with below command > > > > > > > > > > > > > > mount /dev/dasdl1 /d1 > > > > > > > > > > > > > > but, when I triyng to mount another dasd, I am getting below > > > command > > > > > > > > > > > > > > > > > > > > > mount /dev/dasdl1 /d2 > > > > > > > mount: /dev/dasdl1 already mounted or /d2 busy > > > > > > > > > > > > > > > > > > > > > > > > > > > > sles9sp2:~ # mount /dev/dasdn1 /d2 > > > > > > > mount /dev/dasdn1 /d2 > > > > > > > FAT: bogus number of reserved sectors > > > > > > > VFS: Can't find a valid FAT filesystem on dev dasdn1. > > > > > > > mount: you must specify the filesystem type > > > > > > > Aug 23 23:07:46 sles9sp2 kernel: FAT: bogus number of reserved > > > > sectors > > > > > > > Aug 23 23:07:46 sles9sp2 kernel: VFS: Can't find a valid FAT > > > > filesystem > > > > > > on > > > > > > > dev d > > > > > > > asdn1. > > > > > > > sles9sp2:~ # > > > > > > > > > > > > > > > > > > > > > > > > > > > > User directory entry for sles9sp2 > > > > > > > > > > > > > > SLES9SP2 DIRMPART A1 F 80 Trunc=80 Size=37 Line=0 Col=1 > Alt=0 > > > > > > > > > > > > > > USER SLES9SP2 SLES9SP2 2g > > > > > > > *INCLUDE $VOLINKS > > > > > > > option todenable lnknopas quickdsp > > > > > > > CLASS G > > > > > > > MAXSTORAGE 4g > > > > > > > MACHINE ESA > > > > > > > CPU 0 BASE NODEDICATE > > > > > > > CPU 1 NODEDICATE > > > > > > > CPU 2 NODEDICATE > > > > > > > ipl cms parm autocr > > > > > > > iucv *ident gateany gateway revoke > > > > > > > iucv allow > > > > > > > * OSA QDIO device definitions > > > > > > > dedicate 468 4038 > > > > > > > dedicate 469 4039 > > > > > > > dedicate 46a 403a > > > > > > > dedicate 46b 403b > > > > > > > CONSOLE 009 3270 A mvscons > > > > > > > SPOOL 000C 2540 READER * > > > > > > > SPOOL 000D 2540 PUNCH A > > > > > > > SPOOL 000E 3203 A > > > > > > > LINK MAINT 190 190 RR > > > > > > > LINK MAINT 19E 19E RR > > > > > > > LINK MAINT 19D 19D RR > > > > > > > *link $volumes 6CB1 6CB1 mw r6CB1 w6CB1 m6CB1 > > > > > > > *link $volumes 6D04 6D04 mw r6D04 w6D04 m6D04 > > > > > > > * > > > > > > > mdisk 191 3390 0091 0040 542w01 mr read write multiple > > > > > > > * > > > > > > > *mdisk 200 3390 0001 3338 lnx011 mr read write multiple > > > > > > > *mdisk 201 3390 0001 3338 lnx013 mr read write multiple > > > > > > > *mdisk 204 3390 0001 3338 lnx015 mr read write multiple > > > > > > > mdisk 200 3390 0001 10016 VL9141 mr read write multiple > > > > > > > mdisk 300 3390 0001 3338 lnx082 mr read write multiple > > > > > > > mdisk 301 3390 0001 3338 lnx083 mr read write multiple > > > > > > > mdisk 302 3390 0001 3338 lnx084 mr read write multiple > > > > > > > mdisk 303 3390 0001 3338 lnx085 mr read write multiple > > > > > > > mdisk 304 3390 0001 3338 lnx086 mr read write multiple > > > > > > > I am not surte, why m I getting these error. Please help me to > > > > resolve > > > > > . > > > > > > > -- > > > > > > > Thanks & Regards > > > > > > > Saurabh Khandelwal > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Thanks & Regards > > > > > > > Saurabh Khandelwal > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > For LINUX-390 subscribe / signoff / archive access > instructions, > > > > > > > send email to lists...@vm.marist.edu with the message: INFO > > > > LINUX-390 > > > > > or > > > > > > > visit > > > > > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > For more information on Linux on System z, visit > > > > > > > http://wiki.linuxvm.org/ > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > For LINUX-390 subscribe / signoff / archive access > instructions, > > > > > > > send email to lists...@vm.marist.edu with the message: INFO > > > > LINUX-390 > > > > > or > > > > > > > visit > > > > > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > For more information on Linux on System z, visit > > > > > > > http://wiki.linuxvm.org/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Thanks & Regards > > > > > > Saurabh Khandelwal > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > For LINUX-390 subscribe / signoff / archive access instructions, > > > > > > send email to lists...@vm.marist.edu with the message: INFO > > > LINUX-390 > > > > or > > > > > > visit > > > > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > > > > ---------------------------------------------------------------------- > > > > > > For more information on Linux on System z, visit > > > > > > http://wiki.linuxvm.org/ > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > For LINUX-390 subscribe / signoff / archive access instructions, > > > > > send email to lists...@vm.marist.edu with the message: INFO > LINUX-390 > > > or > > > > > visit > > > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > ---------------------------------------------------------------------- > > > > > For more information on Linux on System z, visit > > > > > http://wiki.linuxvm.org/ > > > > > > > > > > > > > > > > > > > > > -- > > > > Thanks & Regards > > > > Saurabh Khandelwal > > > > > > > > > ---------------------------------------------------------------------- > > > > For LINUX-390 subscribe / signoff / archive access instructions, > > > > send email to lists...@vm.marist.edu with the message: INFO > LINUX-390 or > > > > visit > > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > ---------------------------------------------------------------------- > > > > For more information on Linux on System z, visit > > > > http://wiki.linuxvm.org/ > > > > > > > > > > ---------------------------------------------------------------------- > > > For LINUX-390 subscribe / signoff / archive access instructions, > > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or > > > visit > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > ---------------------------------------------------------------------- > > > For more information on Linux on System z, visit > > > http://wiki.linuxvm.org/ > > > > > > > > > > > -- > > Thanks & Regards > > Saurabh Khandelwal > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Thanks & Regards Saurabh Khandelwal ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
