Sorry! Please note, that if I was insulting anything, it was a file,
not any person. Please don't be quite so testy!
I should have said "Probably violates the Debian rules for the
filesystem hierarchy standard, as shown on
http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#LIBESSENTIALSHAREDLIBRARIESANDKERN
"
According to that document, /lib is reserved for "shared library images
needed to boot the system and run the commands in the root filesystem".
My understanding is that /lib/init/rw/.ramfs is not a shared library
image, so it probably shouldn't be there. If there *is* a good
reason, that's one thing, but please stick to the technical issues.
Petter Reinholdtsen wrote:
[Greg Kochanski]
The file /lib/init/rw/.ramfs is created, presumably by initscripts.
It's not in the package list, and that's not at all a good place to
dynamically create a file. Not to mention, putting a hidden file
under /lib is pretty low-class.
I did not quite get what problem you are describing. "not a good
place" and "pretty low-class" do not seem like descriptions of a bug
nor a problem to me. They more visualises your personal values, and
I'm not sure how it is relevant for the boot system.
/lib/init/rw/.ramfs is created by the initscripts to flag that the
directory is a ramfs. It is intentional hidden to avoid name conflict
with anything we want to store there.
Friendly,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
