[systemd-devel] [RFC] the chopping block

[Lennart Poettering]

On Thu, 11.02.16 20:57, Andrei Borzenkov (arvidjaar at gmail.com) wrote:

> 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.

Well, /var/log/journal/* /var/lib/systemd/* is what I personally care about.

Lennart

-- 
Lennart Poettering, Red Hat