fsck forced on every system crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



commence  David Chase quotation:

> Ok, there's obviously something really dumb that I'm missing and
> I'll probably feel like an ass when someone points it out.  Oh well,
> here goes.  I executed the following:
>
> $ mkinitrd -v -f initrd-2.4.7-10smp.img 2.4.7-10smp
>
> It executes without a hitch and reports that ext3 has been loaded.
> Then I run lilo and it too executes without a hitch.  Here is my
> lilo.conf:
>
> image=/boot/vmlinuz-2.4.7-10smp
> 	label=Linux
> 	read-only
> 	root=/dev/hda1
> 	append="hdd=ide-scsi"

I don't use initrd, but isn't there an option you have to add to the
lilo stanza to tell it where the initrd is?

-- 
 /////////////////  |                  | The spark of a pin
<sneakums@zork.net> |  (require 'gnu)  | dropping, falling feather-like.
 \\\\\\\\\\\\\\\\\  |                  | There is too much noise.





[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux