| 1 |
On 9/11/2011 8:28 PM, Albert W. Hopkins wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> On Sunday, September 11 at 18:54 (-0500), Dale said: |
| 5 |
> |
| 6 |
>> I think I saw it mentioned on -dev that some time shortly /usr |
| 7 |
>> and /var |
| 8 |
>> will be needed on / or you will need the init* thingy to boot. |
| 9 |
|
| 10 |
> Hmm, that doesn't smell right to me. What I think you may have heard is |
| 11 |
> about /run. systemd and some other things are preferring to |
| 12 |
> move /var/run to /run. The reason being is that /var does not have to |
| 13 |
> be on the root fs. sysdemd needs /run early (before mounting |
| 14 |
> filesystems) so the idea was to put /var/run on the rootfs, thus /run. |
| 15 |
> |
| 16 |
> I don't think /usr should or ever will be required to be on the rootfs. |
| 17 |
> That's just dumb. The reason we have /bin /sbin, etc. is so that /usr |
| 18 |
> need not be on the rootfs. It doesn't make sense to change that well |
| 19 |
> known/established notion. |
| 20 |
|
| 21 |
Nope, Dale is exactly correct. If the upcoming changes to |
| 22 |
udev make it into Gentoo unaltered and unscathed, it will |
| 23 |
become necessary to have essentially your full system |
| 24 |
available very early in the boot process -- at least as |
| 25 |
early as when udev runs. This includes /usr, where I believe |
| 26 |
the udev scripts and libraries are being moved, and anything |
| 27 |
that any program in those scripts might access, which almost |
| 28 |
definitely includes /var. |
| 29 |
|
| 30 |
Any setup where only / is mounted when udev's device |
| 31 |
population happens will become "unsupported" (if not |
| 32 |
"impossible"). |
| 33 |
|
| 34 |
The proposed alternative to a single huge partition is to |
| 35 |
use an initramfs that mounts your separate /usr (and /var) |
| 36 |
very early in the boot process. |
| 37 |
|
| 38 |
--Mike |
Archives