Re: systemd woes continue

I do have similar issue with systemd.

It fails "local-fs.target" task, unless I remove /boot (which is on
separate device) entry from "/etc/fstab"

swap works (based on "free" and "/proc/swaps"), and systemd does enable it
automatically.

Another issue I do face, is that systemd doesn't bring up network
interface, and does complain about "ifup" or even before it that it failed.
It just says: "Starting of /sys/subsystem/net/devices/enp0s1 not
supported". Huh?

Manually doing "ifup enp0s1" works just fine.

Unfortunately, the logs are rather sparse, and they don't tell me why it
failed.

The entry in /etc/network/interfaces looks just fine.

And the entry in /etc/fstab is fine too (it do use UUID), because if I
restore it and do manually "mount /boot" or "mount -a", it works fine.

śr., 17 lip 2019 o 09:12 Michael Cree <[email protected]> napisał(a):

> On Wed, Jul 10, 2019 at 09:54:40PM -0500, Bob Tracy wrote:
> > First, "systemd" still cannot handle systems with persistent filesystems
> > other than "/" and "/usr".  As far as I know, the bug report I filed
> > against "systemd" is still open, and no progress has been made on that
> > front.
>
> The bug I see on my XP1000 with systemd is that it fails to mount
> the filesystems in /etc/fstab and so stops in emergency mode; one
> can enter the root password, issue "mount -a" and "swapon -a" and
> exit and the boot resumes fines.  I never had this problem with
> sysvinit and have no idea why systemd does not cope.  I will
> probably reinstall sysvinit.  Every time I have tried systemd on
> my Alpha I have ended up deinstalling it and reverting back to
> sysvinit and it looks like this time will be no exception.
>
> Cheers,
> Michael.
>
>

-- 
Witold Baryluk
My PGP keys for 2017-02-17 - 2019-02-17:
5B8C 48CB 8B2F CF53 CA55  0995 16D9 6FA2 20A8 F130
https://functor.xyz/pgp/witold.baryluk-gmail.gpg.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=0x16D96FA220A8F130