Hi all!
I have found a somehow strange systemd "feature" that I'm not sure if it's
a bug. Let me know if you prefer having this reported on GitHub instead.
First, let me explain my setup: I have a data filesystem that is split in
two encrypted partitions (with LUKS) formated as a single btrfs rai
Am 29.08.19 um 20:58 schrieb Dave Howorth:
>> We do this for safety reasons. Please declare all your mounts as
>> "nofail" and then systemd will boot up even without them being
>> around. But of course things will fall apart badly then as soon as a
>> device goes missing as all services will assu
On Thu, 29 Aug 2019 15:57:37 +0200
Lennart Poettering wrote:
> On Do, 29.08.19 07:46, Ulrich Windl
> (ulrich.wi...@rz.uni-regensburg.de) wrote:
>
> > Hi!
> >
> > I agree to almost everything, except:
> >
> > The handling of /etc/fstab is a true mess. Maybe other config files
> > are handles simil
On Do, 29.08.19 07:46, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> Hi!
>
> I agree to almost everything, except:
>
> The handling of /etc/fstab is a true mess. Maybe other config files
> are handles similarly, but I haven't discovered. For some reason
> SLES does not set up a German
On Do, 29.08.19 08:19, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> >
> > # After editing this file, run 'systemctl daemon‑reload' to update systemd
> > # units generated from this file.
> >
> >
>
> Unfortunately it's only half of the truth: Even if you do not modify
> /etc/fstab, b
Am 29.08.19 um 08:19 schrieb Ulrich Windl:
> I really don't understand what "unload this on our doorstep" means: Bring a
> common problem to your attention, while you consider any problems to be the
> user's fault?
at least you understand when you come up with "that's why i hate
systemd" and sim
