Messages in this thread | | | Date | Wed, 31 Jul 2002 11:28:26 +0200 | From | Soewono Effendi <> | Subject | initial ramdisk + devfs |
| |
Hi all!
I was able to to use linux (2.4.x and 2.5.x) on a floppy with busybox using this great devfs only, which saves me lots of spaces. I use the initial ram disk.
But since I downloaded linux-2.5.29, nothing worked anymore. Then I came a long about the problem with ramdisk driver and applied the patch. To my surprise :) it worked again. I was able to boot again.
As I tried to mount the boot floppy I got instead my floppy(ext2), driverfs mounted??? How can that be? I'll send you my boot-floppy image, if you ask me for that.
--------------------------------------------------------- I did the following: without file system type specified: # mount /dev/floppy/0 /mnt **** driverfs is mounted instead of my ext2-floppy # mount ... /dev/floppy/0 on /mnt type driverfs (rw) with file system type specified: # mount -t ext2 /dev/floppy/0 /mnt **** I got the following kernel dump generic_make_request: Trying to access nonexistent block-device fd(2,0) (0) Unable to handle kernel NULL pointer dereference at virtual address 000000a0 ... ... floppy0: timeout handler died: floppy shutdown ----------------------------------------------------------- I have "Kernel automounter version 4 support" compiled in. Would someone, who has enough time to "break" some linux-API behaviour, also has time to notes this down! Maybe there should be a kind of separate "WARNING_API_CHANGED" file under Documentation, so that everybody might keep up with the latest "What might be broken now?". cheers, -sE -- visit us at http://www.sysgo.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |