Am Tuesday 16 December 2003 10:32 schrieb ext john gennard:
> On Tue, Dec 16, 2003 at 07:56:46AM +0100, Dirk Heinrichs wrote:
> > Am Monday 15 December 2003 19:07 schrieb ext john gennard:
> > > I meant /fd0 exists in /dev directory as does about a couple of
> > > dozen of varieties (eg /fd0u1440).
> > > It shows 'brw-rw----   1  root   floppy  2   etc'.
> >
> > That means you have the device file, and from that I guess you're not
> > using devfs, right? If you where using devfs, you would have
> > /dev/floppy/0* (and /dev/fd0* would be symlinks to those). And this
> > only if the driver is active (compiled in or module loaded). Do you see
> > the floppy driver print some version info at boot time (or with dmesg).
>
> I don't have access to 'dmesg' or the /var/log files I'm used to.

Hmm, you should. I just booted into a Live CD (1.4 RC4) and when I get a 
prompt, dmesg gives me the info I want (near the end):

        inserting floppy driver for 2.4.20-xfs-r2
        Floppy drive(s): fd0 is 1.44M

And, the LiveCD in fact uses devfs so you should have something like:

ls -l /dev/fd0
lr-xr-xr-x    1 root     root            8 Dec  3 09:26 /dev/fd0 -> floppy/0

ls -l /dev/floppy/0
brw-rw----    1 root     root       2,   0 Jan  1  1970 /dev/floppy/0

From this I guess you're trying to access the floppy from within chroot, is 
this correct? If so, can you access the floppy when _not_ in chroot (i.e. 
mke2fs /dev/floppy/0), right after booting LiveCD?

So we need to clarify which /dev we are talking about, the one from the CD, 
created by devfs, or the one in chroot, which is a statical one unless you 
deleted its contents and did the bind mount as in the handbook, chapter 
6.a. Since I use devfs, here is what I did when I installed gentoo:

Before chroot'ing, I deleted the contents of the future /dev (which 
is /mnt/gentoo/dev, if you follow the handbook precisely) with "rm 
-rf /mnt/gentoo/dev/*" and the bind-mounted (means: made visible) /dev from 
the cd on /mnt/gentoo/dev as described in the handbook.

> Jason Stubbs suggested I use the Handbook to do my original install
> instead of the install guide that I was trying - he was certainly
> right in my case. I've got to the end of the install, but haven't
> yet been able to boot as I cannot make a boot floppy or put lilo on
> a floppy (since I can't mount the floppy - none of the entries I've
> tried for fstab have worked). To get into the install I have to use
> a liveCD like a 'rescue disk'.

Since I use grub, I never created a lilo floppy, but I guess you don't need 
to mount it, since lilo writes to the floppy device (/dev/floppy/0) 
directly.

So, could you

1) boot with the live cd
2) issue dmesg to verify that the floppy driver is active
3) verify that the floppy works, using mke2fs as above
4) then mount your allready prepared gentoo install (/dev/hdXY) 
on /mnt/gentoo
4) to be save, rename /dev on /mnt/gentoo and make a new one: 
mv /mnt/gentoo/dev /mnt/gentoo/dev.bak; mkdir /mnt/gentoo/dev
5) bind-mount /dev from the live cd: mount -o bind /dev /mnt/gentoo/dev
6) enter the chroot environment as per handbook
7) try 3) again

Tell me how far you get with this. If this all works, there should be no 
problem with genkernel, either. But you should now also enable devfs in 
your kernel config.

HTH...

        Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)151 1513 6954
Configuration Manager   | Fax:  +49 (0)211 47068 111
Cap Gemini Ernst & Young| Mail: [EMAIL PROTECTED]
Hambornerstra�e 55      | Web:  http://www.cgey.com
D-40472 D�sseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

Attachment: pgp00000.pgp
Description: signature

Reply via email to