On 23/08/14 15:57, Bzzzz wrote:
> Effectively, I did not care formerly because it caused no problem,
> but it was tagged 'auto'.
To be clear: that's "auto" in the filesystem column, i.e. automatically
detect a filesystem. "auto" (the default) or "noauto" in the options
column (the one with "user" etc.) determines whether to mount the
filesystem on boot or not; "fail" (the default) or "nofail" determines
whether failure to mount it is considered to be a problem or not.
> This is done ('noauto,nofail,' added in front of 'user,…').
That is correct, yes. Something like this (all one line):
/dev/sdg1 /media/KEY auto
noauto,nofail,user,async,noatime,nodev,nosuid,noexec 0 2
> Hmm, very possible, I've a (bad) habit: I disabled some daemons by
> chmod -x /etc/init.d/<daemon name>
That is not causing this bug, but might not be effective (the daemon
will run even though you didn't want it to) under systemd. The correct
way to disable a system service in Debian is:
update-rc.d <daemon name> disable
which works equally well for systemd, sysvinit and Upstart. Replace
<daemon name> with the name of the script in init.d, or the name of the
systemd unit without the .service suffix, e.g. disabling D-Bus would be
"update-rc.d dbus disable" (but don't do that).
> In this state (/dev/sdg1 line modified but /etc/init.d/ disabled
> scripts still disabled), can I safely reboot or not?
You should be able to reboot after that, yes. Worst case, you'll end up
in systemd's emergency mode, which is basically the same situation
you're in now...
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
