Re: How to get into single user mode - RHEL 5.6
Yes it is... rootvg :-) mounted at / But, easier than that was CP IPL 100 PARM SINGLE, no messing around with detaching/linking mdisks and so on. But I'll look into Scot's advice of creating a single disk rescue system On Sat, Jun 25, 2011 at 17:59, Richard Troth vmcow...@gmail.com wrote: Is the volume group of the damaged system the same as the volume group of the repairing system? -- R; On Jun 25, 2011 5:49 PM, Donald Russell russell@gmail.com wrote: Thanks Scott There are other files systems that also use LVM, but I know the root file system is all on the 100 disk only. I can't actually unmount anything... but I can shut the whole server down and log it off. On my healthy system I can attach (link) the disk, but that's where you're saying I'll have a name conflict because there will already be rootvg volume group. Interrupted ... Solved: #CP 100 PARM SINGLE Whuwho! I'm in and problem fixed. On Sat, Jun 25, 2011 at 13:48, Scott Rohling scott.rohl...@gmail.com wrote: If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume. And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.com wrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/ -- 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/ -- 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
Re: How to get into single user mode - RHEL 5.6
Some good ideas there Scott. :-) Even though IPL cuu PARM SINGLE is great for getting me into single user mode, the other nice thing about having the menu reinstated is it lets me back out a kernel more easily... reboot... choose the older one ... done. The few second delay in having it time out is not a concern at all. Cheers, On Sat, Jun 25, 2011 at 16:08, Scott Rohling scott.rohl...@gmail.comwrote: I meant unmount it from the system you were trying to recover it from -- cuz you needed to mount is as an LVM -- not as a filesystem. But - the duplicate vg apparently would have stopped you. I forgot about the SINGLE parm -- nice one. Couple recommendations: - ensure /etc/zipl.conf has the correct menu listings - and issue 'zipl' without the -X option.. hopefully that gives you the boot menu back -- but maybe you don't want it now that you have the magic incantation. - you may want to define yourself a recovery server that doesn't use LVM -- just have a minimal system on a single minidisk. avoid volume group name conflicts completely. Only bring it up when needed. Scott Rohling On Sat, Jun 25, 2011 at 3:46 PM, Donald Russell russell@gmail.com wrote: Thanks Scott There are other files systems that also use LVM, but I know the root file system is all on the 100 disk only. I can't actually unmount anything... but I can shut the whole server down and log it off. On my healthy system I can attach (link) the disk, but that's where you're saying I'll have a name conflict because there will already be rootvg volume group. Interrupted ... Solved: #CP 100 PARM SINGLE Whuwho! I'm in and problem fixed. On Sat, Jun 25, 2011 at 13:48, Scott Rohling scott.rohl...@gmail.com wrote: If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume.And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.com wrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/ -- 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
How to get into single user mode - RHEL 5.6
RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/
Re: How to get into single user mode - RHEL 5.6
If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume.And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.comwrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/
Re: How to get into single user mode - RHEL 5.6
Thanks Scott There are other files systems that also use LVM, but I know the root file system is all on the 100 disk only. I can't actually unmount anything... but I can shut the whole server down and log it off. On my healthy system I can attach (link) the disk, but that's where you're saying I'll have a name conflict because there will already be rootvg volume group. Interrupted ... Solved: #CP 100 PARM SINGLE Whuwho! I'm in and problem fixed. On Sat, Jun 25, 2011 at 13:48, Scott Rohling scott.rohl...@gmail.comwrote: If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume.And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.com wrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/ -- 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/
Re: How to get into single user mode - RHEL 5.6
I meant unmount it from the system you were trying to recover it from -- cuz you needed to mount is as an LVM -- not as a filesystem. But - the duplicate vg apparently would have stopped you. I forgot about the SINGLE parm -- nice one. Couple recommendations: - ensure /etc/zipl.conf has the correct menu listings - and issue 'zipl' without the -X option.. hopefully that gives you the boot menu back -- but maybe you don't want it now that you have the magic incantation. - you may want to define yourself a recovery server that doesn't use LVM -- just have a minimal system on a single minidisk. avoid volume group name conflicts completely. Only bring it up when needed. Scott Rohling On Sat, Jun 25, 2011 at 3:46 PM, Donald Russell russell@gmail.comwrote: Thanks Scott There are other files systems that also use LVM, but I know the root file system is all on the 100 disk only. I can't actually unmount anything... but I can shut the whole server down and log it off. On my healthy system I can attach (link) the disk, but that's where you're saying I'll have a name conflict because there will already be rootvg volume group. Interrupted ... Solved: #CP 100 PARM SINGLE Whuwho! I'm in and problem fixed. On Sat, Jun 25, 2011 at 13:48, Scott Rohling scott.rohl...@gmail.com wrote: If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume.And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.com wrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/ -- 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/
Re: How to get into single user mode - RHEL 5.6
sorry - bad wording.. you needed to mount it as an LVM -- not a dasd device.. Scott Rohling On Sat, Jun 25, 2011 at 5:08 PM, Scott Rohling scott.rohl...@gmail.comwrote: I meant unmount it from the system you were trying to recover it from -- cuz you needed to mount is as an LVM -- not as a filesystem. But - the duplicate vg apparently would have stopped you. I forgot about the SINGLE parm -- nice one. Couple recommendations: - ensure /etc/zipl.conf has the correct menu listings - and issue 'zipl' without the -X option.. hopefully that gives you the boot menu back -- but maybe you don't want it now that you have the magic incantation. - you may want to define yourself a recovery server that doesn't use LVM -- just have a minimal system on a single minidisk. avoid volume group name conflicts completely. Only bring it up when needed. Scott Rohling On Sat, Jun 25, 2011 at 3:46 PM, Donald Russell russell@gmail.comwrote: Thanks Scott There are other files systems that also use LVM, but I know the root file system is all on the 100 disk only. I can't actually unmount anything... but I can shut the whole server down and log it off. On my healthy system I can attach (link) the disk, but that's where you're saying I'll have a name conflict because there will already be rootvg volume group. Interrupted ... Solved: #CP 100 PARM SINGLE Whuwho! I'm in and problem fixed. On Sat, Jun 25, 2011 at 13:48, Scott Rohling scott.rohl...@gmail.com wrote: If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume.And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.com wrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/ -- 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
Re: How to get into single user mode - RHEL 5.6
Is the volume group of the damaged system the same as the volume group of the repairing system? -- R; On Jun 25, 2011 5:49 PM, Donald Russell russell@gmail.com wrote: Thanks Scott There are other files systems that also use LVM, but I know the root file system is all on the 100 disk only. I can't actually unmount anything... but I can shut the whole server down and log it off. On my healthy system I can attach (link) the disk, but that's where you're saying I'll have a name conflict because there will already be rootvg volume group. Interrupted ... Solved: #CP 100 PARM SINGLE Whuwho! I'm in and problem fixed. On Sat, Jun 25, 2011 at 13:48, Scott Rohling scott.rohl...@gmail.com wrote: If it's really a single disk LVM -- unmount it.. You need to do a pvscan, vgscan, and then vgchange -ay volume-group.. then mount /dev/volume-group/logical-volume. And if your other server already uses the same volume-group name - you will have to rename it before you can activate the new one. (if the lvm consists of more than the 100 disk - you need to link and activate those too..) Sounds like you did a zipl -X at some point, which eliminates the startup menu.. Good luck! Scott Rohling On Sat, Jun 25, 2011 at 2:11 PM, Donald Russell russell@gmail.com wrote: RHEL 5.6 on zVM 6.1 I made a change to /etc/pam.d/system-auth and didn't test it before logging off again. :-( Now, nobody can logon because they get an error, Module not found. (I must have fat-fingered the module name I was adding. OK, no big deal, signal shutdown user x within 300 to bring the server down and reboot in single user mode Except the server doesn't stop at the usual prompt asking what to boot, it just comes up. (Normally that's when I would say #CP VI VMSG 0 1 to come up in single user mode... So, I tried shutting it down and logging off, then attach the 100 mdisk (boot and root file systems) to another running zLinux system. From the running zLinux system I linked to the other 100 disk in write mode (while its proper owner was logged off) and tried to mount the partition at /mnt... where I thought I could then correct the bad file. I said mount /dev/dasdm2 /mnt and was told I had to specify the file system type mount -t ext3 /dev/dasdm2 /mnt Nope... it says it can't find an ext3 file system there. I have no reason to think the data is damaged in anyway... but it is also an LVM disk So, I'm looking for some help in how to recover from this snafu. :-) Thank you -- 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/ -- 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/
