Hello from Gregg C Levine obviously with Jedi Knight Computers Not surprisingly, Rob, you are right. Every time I build a kernel, based on the 2.4.x series I have to be careful about that setting. Since my setup is right between the devfs based systems, and non-devfs, it can be annoying. If you turn it on, in the kernel, and forget to configure the system for it beforehand, everything gets thrown out the airlock. I always turn it off. And this is on Intel Linux. I shudder to think of what can go wrong, on S/390 Linux. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > Rob van der Heij > Sent: Monday, May 27, 2002 12:41 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] Antwort: Re: Antwort: Re: patch problem > > At 10:40 27-05-02, Tim-Chr. Hanschen wrote: > > >Than I tried to reboot the new kernel.... the system run into a corrupted > >filesystem situation... when I booted the old kernel again, the error of > >the filesystem seems to be cleared... > > A popular path to confusion and despair, encouraged by the defaults > in the kernel configuration, is to select CONFIG_DEVFS_MOUNT=y when > you have not configured devfsd yet or adjusted fstab to deal with it. > The devfs gets mounted on top of /dev which means Linux can not find > the /dev/dasd* entries anymore that lead to the disks that hold the > rest of your filesystem. > > Rob
