Plase see bug #403863 as well, as this seems directly related. Whether this bug should be assigned to chkrootkit or initscripts is debatable. [For some reason the reassignment to chkrootkit seems not to have actually occurred.] The argument for why the .ramfs file exists in /lib/init/rw seems to be because of burocracy -- or at least that's how I interpret it.
I have also found a workaround for ignoring the .ramfs error here: http://stereo.lu/chkrootkit.diff.html which was referenced to from: http://stereo.lu/chkrootkit-finds-libinitrwramfs-on-debian-etch -- Chris -- Chris Knadle [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
