On Wed, 24 Apr 2002, Tigran Aivazian wrote:
> On Wed, 24 Apr 2002, Roy Sigurd Karlsbakk wrote:
>
> > > On Wed, 24 Apr 2002, Roy Sigurd Karlsbakk wrote:
> > > > # CONFIG_BLK_DEV_RAM is not set
> > > > # CONFIG_BLK_DEV_INITRD is not set
> > >
> > > enable CONFIG_BLK_DEV_RAM and /dev/ram* will become useable. If you also
> > > use initrd then enable CONFIG_BLK_DEV_INITRD as well.
> >
> > sorry - wrong .config-file. I thought the one I sent was identical to the
> > one I used.
>
> no, there must be yet another (3rd) .config file that was _actually_ used
> for the kernel that you booted, because your /proc/devices didn't show the
> ramdisk registered on major 1. Or did you use /proc/devices from some
> other machine too? :)
Too much mess.
Of course, the /proc/devices was from my computer, compiled without proper
ramfs support. I don't have /proc/devices from the other one, as I can't
boot it, lacking RAMFS support.
sorry about this
-- Roy Sigurd Karlsbakk, DatavaktmesterComputers are like air conditioners. They stop working when you open Windows.
- 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/
This archive was generated by hypermail 2b29 : Tue Apr 30 2002 - 22:00:09 EST