Messages in this thread |  | | Date | Tue, 23 Jul 1996 22:31:08 +0100 (BST) | From | John Storrs <> | Subject | Ramdisk Bug? |
| |
Hi all
> Is this a bug or do I have a configuration problem?
Thanks for replies and the rapid solution to the problem. Ramdisks are broken with the latest kernels if a ramdisk=0 option is passed on booting. Slackware liloconfig does just that for some reason from the past, making an entry in lilo.conf: ramdisk = 0 # paranoia setting. If this is removed, or the value changed to say 4096, ramdisks work as they should. So my problem was configuration, though I'd say there is a bug there too - very badly defined behaviour.
John
----------------------------------------------------------------------------- Buy Goldstar! From the box of a just-installed 8x IDE/ATAPI CDROM drive: Windows 95/NT3.5, OS/2 Warp, Linux, Solaris compatible. And it works too.
|  |