1. The following config has worked fine on 2.6.23.x and earlier, gentoo and hardened sources # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # This along with lilo.conf = boot=/dev/hda4 prompt ignore-table timeout=100 default=Hard23r7 image=/boot/kernel-2.6.23-gentoo-r8 label=Gentoo23r8 ramdisk=300000 read-only root=/dev/hda11 image=/boot/kernel-2.6.23-hardened-r7 label=Hard23r7 ramdisk=300000 read-only root=/dev/hda11 image=/boot/kernel-2.6.24-hardened-r3 label=Hard24r3 ramdisk=300000 read-only root=/dev/hda11 After booting up, I've always been able to mount /dev/ram. to a directory and use ramdisk files. e.g. mke2fs -q -m 0 /dev/ram5 sleep 1 #mke2fs -q -m 0 /dev/ram6 mount /dev/ram5 /ramdisk5 sleep 1 #mount /dev/ram6 /ramdisk6 cp -Rp /jail/tor1 /ramdisk5 2. As of 2.6.24.x, my standard mounting procedures no longer work - in the example above, /ramdisk5 runs out of space. A.) I .....suspect..... that it has something to do with CONFIG_RAMFS (=y) no longer appearing as an option. B.) It may also have to do with " Default number of RAM disks". In pre-2.26.4.x version, it defaulted to "8" and actually produced 16; it now defaults to 8 and produces only "8" (/dev/ram(0-7) ). I tried it both at default 8, and then changing it to 16. Reproducible: Always
Please attach your kernel config. Have you confirmed this problem also occurs with gentoo-sources-2.6.24-r8?
Created attachment 159666 [details] /usr/src/linux-2.6.24-hardened-r3/.config (hope I did this right..... newbie) 1. Yes, It occurred (first) on gentoo-sources-2.6.24-r8. I then uninstalled that and downloaded the hardened sources kernel, and it failed there in the same manner. In each case, I simply copied the .config over from the earlier kernel(s) and ran make oldconfig. The only changes from the earlier configs had to do with adding CONFIG_CRYPTO_XTS=y 2. Here is my .config for hardened.
Created attachment 159668 [details] /usr/src/linux-2.6.24-hardened-r3/.config (hope I did this right..... newbie) 1. Yes, It occurred (first) on gentoo-sources-2.6.24-r8. I then uninstalled that and downloaded the hardened sources kernel, and it failed there in the same manner. In each case, I simply copied the .config over from the earlier kernel(s) and ran make oldconfig. The only changes from the earlier configs had to do with adding CONFIG_CRYPTO_XTS=y 2. Here is my .config for hardened.
(In reply to comment #0) > ramdisk=300000 First, double check that the source to be copied is smaller than the destination ramdisk. Please try removing the ramdisk=300000 line and using: append="ramdisk_size=300000" Been awhile since I used lilo but I'm pretty sure you have to re-run lilo after this change. Lastly, updating summary, reassigning to kernel@g.o, removing hardened@g.o, CCing myself.
SUCCESS! Your changes did the trick! Thanks for hanging in there - espcially given it was a user config problem!! Which begs the question, WHY... did the kernel suddenly become finicky about that lilo wording, given lilo hasn't changed in months, and given I'd been using that lilo.conf for over a year? Thanks again! (though it looks like I'll be sending in another note - one on "arpstar" - once I gather some info and confirm there's an issue there :-( )
Nice find on the configuration change, Gordon.
