Thanks Mark, I guess I was thinking more on the lines of an enhancement request and also just sending out a warning on it.
I know I'll never do a mkinitrd command again without doing a cat of the fstag first .. adding a few disks is such a basic thing and then booting and having it go straight to kernel panic is no fun at all ... -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, June 22, 2007 5:28 PM To: [email protected] Subject: Re: mkinitrd bug ? >>> On Fri, Jun 22, 2007 at 3:47 PM, in message <[EMAIL PROTECTED]>, "Ayer, Paul W" <[EMAIL PROTECTED]> wrote: -snip- > Everything is all set now and fixed .. but what I am wondering is if > mkinitrd or a forked process it kicks off > > should at least give a warning message that the /etc/fstab is empty and > do not boot or you won't come back up .... Paul, That sounds more like an enhancement request to me than a bug. Checking for a completely empty fstab file would be pretty easy. Doing a thorough job of checking the contents for broken entries would be a lot more difficult, since I'm not aware of any generalized fstab checker code out there. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
