Hey Santiago,
Santiago Vila [2014-04-28 17:51 +0200]:
> For now, /etc/machine-id is a configuration (or state) file for the
> systemd package. Documentation about machine-id even says that
> removing the file on reboots is mostly harmless (you could have a
> different machine-id every time the mac
On Mon, 28 Apr 2014, Michael Biebl wrote:
> Am 28.04.2014 17:51, schrieb Santiago Vila:
> > For now, /etc/machine-id is a configuration (or state) file for the
> > systemd package. Documentation about machine-id even says that
> > removing the file on reboots is mostly harmless (you could have a
>
Santiago Vila [2014-04-26 12:16 +0200]:
> IMHO, such bug is ridiculous: On systems where systemd is the init
> manager, systemd becomes essential and you simply *don't* remove it!
On Debian we support multiple init systems, so in theory a user could
install sysvinit or upstart or openrc etc., and
On Sat, 26 Apr 2014, Santiago Vila wrote:
> In fact: What's the benefit of generating this file in base-files at all?
> block -1 by 745876
Bug #619244 [systemd] systemd: unowned files after purge (policy 6.8, 10.8):
/etc/machine-id
619244 was not blocked by any bugs.
619244 was not blocking
On Sat, 26 Apr 2014, Michael Stapelberg wrote:
> Package: base-files
> Version: 7.2
> Severity: normal
> Tags: patch
>
> D-Bus, systemd and other programs use /etc/machine-id. Given that this
> file is per-machine and very central, it should live in base-files.
>
> The attached patch creates the
Package: base-files
Version: 7.2
Severity: normal
Tags: patch
D-Bus, systemd and other programs use /etc/machine-id. Given that this
file is per-machine and very central, it should live in base-files.
The attached patch creates the file unless it already exists. The patch
works on Linux and shoul
6 matches
Mail list logo
