| View previous topic :: View next topic |
| Author |
Message |
Dr_Stein
Guru
Joined: 21 Mar 2003
Posts: 303
Location: Mountain View, CA
|
 Posted: Sat Jan 24, 2004 9:23 pm Post subject: LILO harfs during install |
 |
|
"Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/ide/host0/bus1/target0/lun0/disc' -> '/dev/hda'
The kernel was compiled with DEVFS_FS, but 'devfs=mount' was omitted
as a kernel command-line boot parameter; hence, the '/dev' directory
structure does not reflect DEVFS_FS device names.
"
I *did* compile the kernel with the defvs support, and selected "mount automatically at boot" per the Gentoo installation docs.
I have searched Google, and found stuff about an append line for lilo.conf, so I have "append = defs=mount" in /etc/lilo.conf
This box has 1x30gb HD and 1x80gb HD, the 30gb HD is what I installed Gentoo on.
It USED to have SuSE 8.0 on it, and Gentoo is replacing it.. I can't figure out what's causing this. It's preventing my installation from proceeding. =/
Should I just try Grub? Any ideas?  |
|
| Back to top |
|
 |
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Sat Jan 24, 2004 9:29 pm Post subject: |
|
|
| Quote: | | Should I just try Grub? |
Absolutely.
Superior, easier, better.
You can even recover from faulty configs while you're booting. |
|
| Back to top |
|
|
Corw|n of Amber
Apprentice
Joined: 08 Aug 2003
Posts: 221
Location: Socialist Sovietic Republic of Belgium
|
| Posted: Sat Jan 24, 2004 11:26 pm Post subject: |
|
|
| adaptr wrote: | | You can even recover from faulty configs while you're booting. |
And THAT is real handy... I can't count how many times I made typos in grub.conf, or forgot to remove a line that prevented booting, whaterver --if your computer accepts GRUB (I have one where grub just won't install), you have to use it.
_________________
Whoever is enough of a fanatic to KILL people should be shot on sight. |
|
| Back to top |
|
|
moron
n00b
Joined: 16 Sep 2003
Posts: 70
|
| Posted: Sun Jan 25, 2004 4:01 am Post subject: let the flames begin |
|
|
I beg to differ. Grub sucks if you have anything beyond a very simple one drive system. Grub does not have persistant device naming so if you change your boot order (something needed quite often I would think when performing upgrades or installs), grub's configuration will no longer be correct (since hd0,0 is not a reference to a specific disk, just the first disk in the current boot order). LILO does not have this problem.
Another grub glitch is that it has odd behaviour with some graphics cards. On my Nvidia Geforce2 MX400 for example I get grabled text until well into the boot sequence which makes it a pain sometimes to catch errors during the boot up stage or to type in a kernel name if something goes wrong.
LILO has proven far more reliable in my experience.
Cheers
_________________
--
---> (culture) http://industrial.org : (label) http://deterrent.net
---> (community) http://ampfea.org : (hire me) http://codegrunt.com
---> (send EEEI news to) infosuck@industrial.org
---> Whomever dies with the most URLs wins!!!!!!!!!!!!! |
|
| Back to top |
|
|
amne
Bodhisattva
Joined: 17 Nov 2002
Posts: 6378
Location: Graz / EU
|
| Posted: Sun Jan 25, 2004 12:27 pm Post subject: |
|
|
I got the same message inside a chroot environment. if lilo also wrote some "Adding *kernel" stuff, it should have worked anyway. Once you have finished your installation and (with sucess, i hope) booted into your system, lilo should work without these warnings.
Note: Don't know for sure why exactly i had to boot my install cd and chroot today, but for some reason my lilo broke completely with the last upgrade. Should try grub one day.  |
|
| Back to top |
|
|
Deathwing00
Bodhisattva
Joined: 13 Jun 2003
Posts: 4087
Location: Dresden, Germany
|
|
| Back to top |
|
|
|
Duplicate Threads
