[systemd-devel] [RFC] the chopping block
Andrei Borzenkov
arvidjaar at gmail.com
Thu Feb 11 17:57:03 UTC 2016
11.02.2016 20:52, Lennart Poettering пишет:
> On Thu, 11.02.16 20:48, Andrei Borzenkov (arvidjaar at gmail.com) wrote:
>
>> 11.02.2016 20:06, Lennart Poettering пишет:
>>>
>>> 5) Here's the controversial one I think: support for booting up
>>> without /var. We have kludges at quite a few places because we
>>> cannot access /var early during boot. I am tempted to stop
>>> supporting this altogether. Of course, this does *not* mean that
>>> people with split off /var would be left in the cold. It just means
>>> that they have to mount /var from the initrd, exactly like this is
>>> already handled from /usr.
>>>
>>
>> Does it apply to whole /var, to each part of /var or to specific subdirs
>> in /var? In openSUSE various subtrees under /var are split off in
>> individual volumes on btrfs, forcing mounting them all in initrd is not
>> much appealing.
>
> btrfs's subvolumes are pretty nice as they are just special
> directories. There's no need to mount them in any special way.
>
There is, but this is off topic here.
> That said, this is about /var/log and these kinds of things. If some
You will need to be specific, which kind of things then. And yes,
/var/log is mount point by default as well. Please if you are going to
drop support for these things being mount point, list them precisely and
exhaustively.
> random late-boot package needs something under /var (let's say mysql
> needs /var/lib/mysql), then systemd really doesn't care about it...
>
> Lennart
>
More information about the systemd-devel
mailing list