I've got a Fedora 22, 23, 24, 25 bug where systemd offline updates of
kernel results in an unbootable system when on XFS only (/boot is a
directory), the system boots to a grub menu. The details of that are
in this bug's comment:
https://bugzilla.redhat.com/show_bug.cgi?id=1227736#c39
The gist of
On Wed, Mar 15, 2017 at 12:21:49AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Sat, Mar 11, 2017 at 06:14:17PM +0100, Sam Ravnborg wrote:
> > Hi all.
> >
> > How can we set environment variables so they are available for everyone?
> >
> >
> > Background:
> >
> > On an embedded target we use
Am 16.03.2017 um 18:21 schrieb Michal Sekletar:
On Thu, Mar 16, 2017 at 4:29 PM, Reindl Harald wrote:
with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25
"/usr/bin/vmware-networks" while this is just a phyiscal file and was not
touched
[root@rh:~]$ rpm -q systemd
systemd
On Thu, Mar 16, 2017 at 4:29 PM, Reindl Harald wrote:
> with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25
> "/usr/bin/vmware-networks" while this is just a phyiscal file and was not
> touched
>
> [root@rh:~]$ rpm -q systemd
> systemd-231-14.fc25.x86_64
>
> Mar 16 16:25:23 rh
and once again sytstemd can't handle it's own restrictions as it was a
few releases ago the case when /proc and /sys where set as "
ReadOnlyDirectories="
but what is then the nonsense about "Too many levels of symbolic links"
and why did it work with F22, F23 and F24 unchanged until new systemd
with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25
"/usr/bin/vmware-networks" while this is just a phyiscal file and was
not touched
[root@rh:~]$ rpm -q systemd
systemd-231-14.fc25.x86_64
Mar 16 16:25:23 rh systemd: vmware-vmnet.service: Failed at step
NAMESPACE spawning
