Re: [Linux/390] 2.4.17 Upgrade Problem

2002-07-05 Thread John Summerfield
Is there any existing documentation (mini-HOWTO?) for converting from a 2.2 kernel with a normal /dev to a 2.4 with devfs active. What changes do I have to make to /etc/fstab? How can I make the changes compatible (for backout)? What kernel options can I pass to control devfs? What can I

Re: [Linux/390] 2.4.17 Upgrade Problem

2002-07-05 Thread John Summerfield
Dougie, I suspect having an /etc/fstab that uses the disk labels, rather than device names would be the way to go if you want to be able to flip-flop between devfs/non-devfs. If you do that, beware of attaching disks from other Linux systems. Many times I've attached a root disk from

Re: 2.4.17 Upgrade Problem

2002-07-04 Thread Rob van der Heij
At 12:52 03-07-02 -0400, Post, Mark K wrote: This sounds like the default of devfs being turned on in the new kernel problem. Reboot your old kernel (if you can), go into the kernel source top level directory, and do a make menuconfig. Go into file systems and turn off devfs support,

Re: [Linux/390] 2.4.17 Upgrade Problem

2002-07-04 Thread Dougie Lawson
Is there any existing documentation (mini-HOWTO?) for converting from a 2.2 kernel with a normal /dev to a 2.4 with devfs active. What changes do I have to make to /etc/fstab? How can I make the changes compatible (for backout)? What kernel options can I pass to control devfs? What can I do if

Re: [Linux/390] 2.4.17 Upgrade Problem

2002-07-04 Thread Sergey Korzhevsky
Read /usr/src/linux/Documentation/filesystems/devfs/README I tried do this but with no success. WBR, Sergey Dougie Lawson dougie_lawson@uTo: [EMAIL PROTECTED] k.ibm.com cc: Sent by:

Re: [Linux/390] 2.4.17 Upgrade Problem

2002-07-04 Thread Post, Mark K
AM To: [EMAIL PROTECTED] Subject: Re: [Linux/390] 2.4.17 Upgrade Problem Is there any existing documentation (mini-HOWTO?) for converting from a 2.2 kernel with a normal /dev to a 2.4 with devfs active. What changes do I have to make to /etc/fstab? How can I make the changes compatible

2.4.17 Upgrade Problem

2002-07-03 Thread Geyer, Thomas L.
I am trying to upgrade my SLES 2.4.7 kernel to 2.4.17. I have followed the procedure in the HOW-TO from linuxvm.org and in the Linux on zSeries and S390: Systems Management Redbook. When I try to boot the new kernel I get the following errors: Parallelizing fsck version 1.19a (13-Jul-2000)

Re: 2.4.17 Upgrade Problem

2002-07-03 Thread Post, Mark K
-Original Message- From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 10:47 AM To: [EMAIL PROTECTED] Subject: 2.4.17 Upgrade Problem I am trying to upgrade my SLES 2.4.7 kernel to 2.4.17. I have followed the procedure in the HOW-TO from linuxvm.org and in the Linux

Re: 2.4.17 Upgrade Problem

2002-07-03 Thread Konkol, Josh
-tools from the non-may2002 stream is even enough if you don't need the new OSA features. HTH Josh -Original Message- From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 9:47 AM To: [EMAIL PROTECTED] Subject: 2.4.17 Upgrade Problem I am trying to upgrade my

Re: 2.4.17 Upgrade Problem

2002-07-03 Thread Mike Grundy
On Wed, Jul 03, 2002 at 10:47:09AM -0400, Geyer, Thomas L. wrote: I am trying to upgrade my SLES 2.4.7 kernel to 2.4.17. I have followed the procedure in the HOW-TO from linuxvm.org and in the Linux on zSeries and S390: Systems Management Redbook. When I try to boot the new kernel I get the

Re: [Linux/390] 2.4.17 Upgrade Problem

2002-07-03 Thread Mike Kershaw
fsck.ext2: No such file or directory while trying to open /dev/dasdb1 Most likely it is devfs - mount on boot is enabled by default in the kernel patches, which means /dev gets replaced with the dynamically generated devfs which doesn't have dasd in the same place. If you turn off the