1 |
On Sunday, September 11 at 18:54 (-0500), Dale said: |
2 |
|
3 |
> I think I saw it mentioned on -dev that some time shortly /usr |
4 |
> and /var |
5 |
> will be needed on / or you will need the init* thingy to boot. |
6 |
> That's |
7 |
> was my understanding of this mess. So, if you are about to do a |
8 |
> install |
9 |
> that needs /var on its own partition, I would ask a dev to see how |
10 |
> you |
11 |
> should plan. I could have misunderstood but I'm pretty sure it's |
12 |
> coming. It may also depend on what you are going to be running too. |
13 |
> I |
14 |
> mention because no need doing it one way now and having to fix it |
15 |
> later. That sucks! |
16 |
> |
17 |
> That said, I have /var on its own partition and mine boots fine, |
18 |
> although I haven't rebooted in a week or so. I don't think the |
19 |
> change |
20 |
> has happened yet but is coming. I may have a different answer in a |
21 |
> month or so. ;-) |
22 |
> |
23 |
> Dale |
24 |
> |
25 |
|
26 |
Hmm, that doesn't smell right to me. What I think you may have heard is |
27 |
about /run. systemd and some other things are preferring to |
28 |
move /var/run to /run. The reason being is that /var does not have to |
29 |
be on the root fs. sysdemd needs /run early (before mounting |
30 |
filesystems) so the idea was to put /var/run on the rootfs, thus /run. |
31 |
|
32 |
I don't think /usr should or ever will be required to be on the rootfs. |
33 |
That's just dumb. The reason we have /bin /sbin, etc. is so that /usr |
34 |
need not be on the rootfs. It doesn't make sense to change that well |
35 |
known/established notion. |
36 |
|
37 |
See also the FHS. |