supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: fungal-net <fungalnet@obarun.org>
To: 66 <66@obarun.org>, supervision@list.skarnet.org
Subject: Debian and init freedom (logging freedom?)
Date: Mon, 23 Dec 2019 20:39:30 +0200	[thread overview]
Message-ID: <c3bf49cd-7da6-5930-2d74-b32185ab3f0c@obarun.org> (raw)

While upgrading my antiX-sid (Debian) with s6 and 66 installed today I
got two interesting messages.

This is copy paste from the terminal screen.  If systemd-log is on the
/etc/ files then you have nothing to worry about.  :)
At least they ask whether you allow Lenny to sweep your /etc/ for you.


Package configuration

 ┌────────────────────────────────────────┤ Configuring base-passwd
├────────────────────────────────────────┐
 │
                                    │
 │ update-passwd has found a difference between your system accounts and
the current Debian defaults.  It    │
 │ is advisable to allow update-passwd to change your system; without
those changes some packages might not  │
 │ work correctly.  For more documentation on the Debian account
policies, please see                        │
 │ /usr/share/doc/base-passwd/README.
                                    │
 │
                                    │
 │ The proposed change is:
                                    │
 │
                                    │
 │ Remove group "log" (19)
                                    │
 │
                                    │
 │ If you allow this change, a backup of modified files will be made
with the extension .org, which you can  │
 │ use if necessary to restore the current settings.  If you do not make
this change now, you can make it    │
 │ later with the update-passwd utility.
                                    │
 │
                                    │
 │ Do you want to remove the group log?
                                    │
 │
                                    │
 │                               <Yes>
<No>                                 │
 │
                                    │
 └───────────────────────────────────────────────────────────────────────────────────────────────────────────┘






 ┌────────────────────────────────────────┤ Configuring base-passwd
├────────────────────────────────────────┐
 │
                                    │
 │ update-passwd has found a difference between your system accounts and
the current Debian defaults.  It    │
 │ is advisable to allow update-passwd to change your system; without
those changes some packages might not  │
 │ work correctly.  For more documentation on the Debian account
policies, please see                        │
 │ /usr/share/doc/base-passwd/README.
                                    │
 │
                                    │
 │ The proposed change is:
                                    │
 │
                                    │
 │ Remove user "s6log" (19)
                                    │
 │
                                    │
 │ If you allow this change, a backup of modified files will be made
with the extension .org, which you can  │
 │ use if necessary to restore the current settings.  If you do not make
this change now, you can make it    │
 │ later with the update-passwd utility.
                                    │
 │
                                    │
 │ Do you want to remove the user s6log?
                                    │
 │
                                    │
 │                               <Yes>
<No>                                 │
 │
                                    │
 └────────


             reply	other threads:[~2019-12-23 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 18:39 fungal-net [this message]
2019-12-25  5:43 ` Jonathan de Boyne Pollard
2019-12-25 11:08   ` fungal-net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c3bf49cd-7da6-5930-2d74-b32185ab3f0c@obarun.org \
    --to=fungalnet@obarun.org \
    --cc=66@obarun.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).