Michael Biebl writes:
>> But even with this in place, the new logic should be prepared for
>> duplicate mac addresses. There are plenty of USB devices with non-
>> unique mac addresses out there. It's more of a rule than an exception
>> for GSM/LTE modem devices...
>
> Please consider raising t
Michael Biebl writes:
> Hi Bjørn,
>
> On Mon, 25 Jan 2016 09:27:31 +0100 =?utf-8?q?Bj=C3=B8rn_Mork?=
> wrote:
>> I just noticed that the new "predictable" network device names logic
>> fails in a most ugly way with USB devices with no permanent mac
>> address:
>>
>> [ 10.989584] qmi_wwan 6-4
I believe adding '--force' is just as important when the root account
has a password, to allow system access in case /etc/password and/or
/etc/shadow are unreadable or otherwise damaged.
This is of course much less likely to happen than needing su access in
general. But there are no real reasons
Martin Pitt writes:
> - [ifnames] For about two years (since 197) upstream's udev has a
>builtin persistant name generator which checks firmware/BIOS
>provided index numbers or slot names (like biosdevname), falls back
>to slot names (PCI numbers,
Note that this makes the same bogus
Package: systemd
Version: 215-5+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind puts what seems like debugging messages in the kernel
log. Examples:
systemd-logind[2790]: Failed to start user service: Unknown unit:
user@106.service
systemd-logind[2790]: New se
Package: systemd
Version: 215-5+b1
Severity: critical
Justification: breaks unrelated software
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind breaks acpid by default.
Merely installing systemd with default configuration causes it to start
handling the PowerKey, LidSwitch, Hibernate
Package: systemd
Version: 215-5+b1
Severity: normal
File: systemd-hostnamed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I get this noise in the kernel log when systemd-hostnamed starts (which
it seems to do for whatever default reason):
systemd-hostnamed[2574]: Warning: nss-myhostname is not
Michael Biebl writes:
> Am 06.07.2014 21:11, schrieb Bjørn Mork:
>> Michael Biebl writes:
>>
>>> Be aware that systemd-modules-load does *not* read module parameters
>>> from /etc/modules. You'll need to set them via a /etc/modprobe.d/ file.
>>
>&
Michael Biebl writes:
> Be aware that systemd-modules-load does *not* read module parameters
> from /etc/modules. You'll need to set them via a /etc/modprobe.d/ file.
Hmm... Is that considered a bug, or is it just the way things are going
to be?
The modules(5) man page from the kmod package sti
