Niels Thykier writes:
> I had a look at the introduction section of Policy to check who the
> target audience is. I cannot find an explicit mention of the target
> audience. I suspect there is a conflict here on the content because we
> have different audiences in mind for the Policy and the Pol
Alexandre Detiste writes:
> The ugly magic behind the curtain:
> ls /usr/libexec/cruft/ -1
> LOGROTATE -> that parses these for path
> SERVICES -> added today reading this discussion, it reads
> CacheDirectory= & StateDirectory= from *.service
> TMPFILES -> that p
Bill Allombert writes:
> As I said, filling the caches in /var/cache. For that they need to exist
> with correct ownership and permissions.
Sorry, I think I saw that and then edited my message more and lost it
again.
That use case makes sense to me, and without the directory already
present, yo
On Sun, Sep 17, 2023 at 08:28:56AM -0700, Russ Allbery wrote:
> Bill Allombert writes:
> > On Sun, Sep 17, 2023 at 10:41:55AM +0200, Marco d'Itri wrote:
> >> On Sep 17, Russ Allbery wrote:
>
> >>> (I am a little confused by this wording, but I think what you're
> >>> saying is that /usr is encry
So there are 3 distinct interlinked goals:
- tmpfiles.d itself
- recovering from missing /var (+ later /etc)
- volatile file tracking
Just finishing the first step without going to far in either
other tracks would be so great already.
Le dim. 17 sept. 2023 à 19:57, Russ Allbery a écrit :
>
Luca Boccassi writes:
> Let me clarify, here I meant something much simpler - the image
> installed is a 'normal' one, with r/w root and managed by apt as usual
> (ie: not immutable image-based) but with a repart.d snippet that causes
> a new /var to be created on-the-fly on first boot if missing
On Sun, 17 Sept 2023 at 00:12, Russ Allbery wrote:
>
> Luca Boccassi writes:
>
> > Aside from more practical considerations, shipping /var content in
> > packages is problematic because it's supposed to be local variable data,
> > that can be removed without breaking a system.
>
> Unless I'm miss
On Sep 17, Bill Allombert wrote:
> Does not that would break users expectation that the system image contains
> /var
> before the first boot ?
I am not aware of such expectations.
> A lot of things in /var are caches that are mostly instance-independent and
> can
> be prefilled, but for that,
Ansgar writes:
> But the subject of this issue talks about "script interpreters", not
> just `/bin/sh` (which I guess is safe to assume would be one of the
> "handful").
> It is unclear what files the Jackson symlink farm proposal would leave
> in /bin. Would /bin/python3 stay? Or would it sta
Bill Allombert writes:
> On Sun, Sep 17, 2023 at 10:41:55AM +0200, Marco d'Itri wrote:
>> On Sep 17, Russ Allbery wrote:
>>> (I am a little confused by this wording, but I think what you're
>>> saying is that /usr is encrypted and read-only, and /var is recreated
>>> on each boot. That at least
On Sun, 17 Sep 2023 at 02:03:52 +0200, Santiago Vila wrote:
> If the files are intended to be modified "in place" by the
> system admin, we call them configuration files (and we try hard
> to put them in /etc). If they are not intended to be modified by
> the system admin, we don't call them config
On Sun, Sep 17, 2023 at 10:41:55AM +0200, Marco d'Itri wrote:
> On Sep 17, Russ Allbery wrote:
>
> > (I am a little confused by this wording, but I think what you're saying is
> > that /usr is encrypted and read-only, and /var is recreated on each boot.
> > That at least is my understanding of th
On Sun, 2023-09-17 at 11:54 +0200, Bill Allombert wrote:
> /bin/perl, /bin/env, /bin/python3 did not exist in the old scheme, so
> there is no point in creating them now.
No, in Debian's current filesystem layout (Debian stable and later;
partly Debian oldoldstable and later) all of these exist.
Russ Allbery:
Bill Allombert writes:
[...] Quite a lot of Policy is of the general format "here's a bunch of
complex things you need to do, wait, never mind, just use debhelper, go
see its documentation for the configuration files you should use instead"
and some of the rest of Policy is "here
On Sun, Sep 17, 2023 at 08:52:17AM +0200, Ansgar wrote:
> > Control: unblock 1051371 by 1050001
> >
> > Ansgar writes:
> >
> > > However, there is a proposal by Jackson for an alternative filesystem
> > > layout based on symlink farms in consideration by the technical
> > > committee. This advo
On Sun, Sep 17, 2023 at 12:12:18AM +0200, Daniel Gröber wrote:
> Sam, Russ, Bill,
>
> Thanks for your input. To be quite frank I still don't see how the
> interpretation of allowing configuration files outside of /etc can be
> supported based on the policy text.
>
> Ultimately I'm just concerned
On Sep 17, Russ Allbery wrote:
> (I am a little confused by this wording, but I think what you're saying is
> that /usr is encrypted and read-only, and /var is recreated on each boot.
> That at least is my understanding of the pattern that you're trying to
> enable.)
The general idea is to be abl
17 matches
Mail list logo
