related?
http://freshmeat.net/projects/lilo/
LILO can't acces /dev/fd0
by Joel Kaasinen - Nov 16th 2003 03:39:10
Im working on a linux-on-a-disk-thingie, and ive got evrything ready, boot.b, the kernel and etc/lilo.conf (BTW boot=/dev/fd0 and root=/dev/fd0) in their places, but when i try to install lilo unto the disk with
"lilo -v -r /mnt/floppy"
lilo says: "cant acces dev/fd0: permission defined"
As im doing this as root, the file permissions of /dev/fd0 shouldn't be the cause
It would be nice, if someone could help...
--
cheers, J
[reply] [top]
[»] Re: LILO can't acces /dev/fd0
by John Coffman - Nov 16th 2003 11:53:09
This is a well known gotcha when using "-r". It is expected that you have a full Linux installation at the point you are 'chroot'ing to. Specifically, you need a /dev directory, with all device permissions set correctly. Sounds like you have omitted this step in creating your floppy image. You might check the method used by the LILO utility "mkrescue", a shell script, and adopt its methods of avoiding the need for a 'chroot'.
[reply] [top]
[»] Re: LILO can't acces /dev/fd0
by Joel Kaasinen - Nov 16th 2003 22:56:25
I have a dev directory with fd0, console and null in it. I got lilo to eork by first mounting fd0 with:
mount -o dev /dev/fd0
I heard this from someone on the net, and I would like to know exactly why did it work. The documentation for the dev option is quite cryptic:
dev Interpret character or block special devices
on the file system.
thx in advance
J
--
cheers, J
[reply] [top]
[»] Re: LILO can't acces /dev/fd0
by Kari Hurtta - Nov 29th 2003 12:01:35
> I have a dev directory with fd0, console
> and null in it. I got lilo to eork by
> first mounting fd0 with:
> mount -o dev /dev/fd0
> I heard this from someone on the net,
> and I would like to know exactly why did
> it work. The documentation for the dev
> option is quite cryptic:
>
> dev Interpret character or block
> special devices
> on the file system.
'nodev' tradiotionally prevents doing 'character' or 'block' special files to filesystem. So 'dev' is just opposite.
crw-rw-rw- 1 root root 5, 0 Nov 29 21:06 /dev/tty
That 'c' indicates that this is character special file.
brw-rw---- 1 root disk 3, 0 Apr 7 2003 /dev/hda
That 'b' indicates that this is block special file.