On 10/15/2011 4:42 AM, Canek Peláez Valdés wrote:
Which one? That /var is not going into /? It's not disinformation, it
is th true. If not, please be so kind of showin one single developer
reference that says so. One. Single. One.
Email, blog post, wiki, you choose it. But one single one.
I don't think anyone is claiming that there are *currently*
plans to require /var, either on / or via initramfs.
The claim being made is that /var suffers from the exact
same problem that /usr does, with regard to udev, namely
that arbitrary programs running from within udev rules could
(and some do) require /var to be present to function. Thus,
the arguments being applied to /usr *currently* can be
applied equally to /var, once it becomes an issue.
The classic example being given is a bluetooth keyboard: to
make a bluetooth keyboard available, udev executes a rule
which requires /var/bluetooth to be present. (Certain other
rules similarly require data from /var, such as sound cards
or printers.)
The extremely logical deduction being made is as follows:
Some udev rules require /usr to be preset to properly
execute. The solution favored by the udev maintainer is to
simply make /usr always required for udev to run. Running
udev without /usr present will become unsupported.
Similarly, some udev rules require /var to be present to
properly execute. The solution that will be favored by the
udev maintainer, when such an issue is raised, is most
likely going to be similar to the solution proposed for
/usr: the mandating of /var being present before udev runs.
Running udev without /var present will most likely become
unsupported.
Programs designed to run out of /bin expect to be run
without any other locations present. Programs designed to
run out of /usr/bin generally assume that the rest of the
system, including /var, is available for use. You can't have
one without the other.
--Mike
