Processed: Re: /sys/devices/system/cpu/online SELinux context

2016-12-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 849637 policycoreutils Bug #849637 [systemd] /sys/devices/system/cpu/online SELinux context Bug reassigned from package 'systemd' to 'policycoreutils'. No longer marked as found in versions systemd/232-8. Ignoring request to alter fixed v

Bug#849637: /sys/devices/system/cpu/online SELinux context

2016-12-30 Thread Laurent Bigonville
reassign 849637 policycoreutils thanks On Thu, 29 Dec 2016 12:36:30 +0100 cgzones wrote: > When running a SELinux enabled system /sys/devices/system/cpu/online > is mislabeled after boot: > > root@test1:/root/selinux/policy# restorecon -vv -R -F -n /sys > Would relabel /sys/devices/system/cpu/o

Re: Bug #826214: Bug #826215: init-d-script and systemd: solution

2016-12-30 Thread Andreas Henriksson
Hi Christian, Thanks for considering my negative feedback in a constructive way. On Thu, Dec 29, 2016 at 05:24:26PM +0100, Christian Seiler wrote: > Hi Andreas, [] > > After reading the other emails, maybe we can converge on the > following consensus / compromise? > > For stretch: > > - I

Migration from sysvinit to systemd: reboot fails to complete

2016-12-30 Thread Francesco Poli
Hello Debian systemd Maintainers! I had to migrate one amd64 Debian GNU/Linux stretch box from sysvinit to systemd. I followed the procedure suggested on the Debian wiki [1]. [1] https://wiki.debian.org/systemd Manually adding the "init=/bin/systemd" boot parameter to the Linux kernel (from the

Re: Migration from sysvinit to systemd: reboot fails to complete

2016-12-30 Thread Felipe Sateler
Hi Francesco, On 30 December 2016 at 13:08, Francesco Poli wrote: > Hello Debian systemd Maintainers! > > I had to migrate one amd64 Debian GNU/Linux stretch box from sysvinit > to systemd. > I followed the procedure suggested on the Debian wiki [1]. > > [1] https://wiki.debian.org/systemd > > Ma

Bug#849316: machinctl: fails to list anything if a libvirt qemu container is running

2016-12-30 Thread Felipe Sateler
On 29 December 2016 at 14:54, Felipe Sateler wrote: > On 26 December 2016 at 06:18, Michael Biebl wrote: >> >> Am 25.12.2016 um 22:32 schrieb Felipe Sateler: >> > PR 4978 was closed in favor of 4972. However, it has not been merged >> > yet. The patch is small so at least I don't have a problem w

Re: Migration from sysvinit to systemd: reboot fails to complete

2016-12-30 Thread Francesco Poli
On Fri, 30 Dec 2016 14:15:17 -0300 Felipe Sateler wrote: > Hi Francesco, Hello Felipe, first off, thanks for your prompt reply! > > On 30 December 2016 at 13:08, Francesco Poli > wrote: [...] > > I then scheduled a reboot: > > > > # at 'now + 1 minute' > > warning: commands will be execut

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

2016-12-30 Thread Michael Biebl
On Sat, 13 Feb 2016 22:02:02 +0100 Francesco Poli wrote: > Control: found -1 systemd/228-6 > > > On Sun, 29 Nov 2015 01:05:44 +0100 Michael Biebl wrote: > > > Am 28.11.2015 um 19:23 schrieb Francesco Poli: > > > > > Please tell me whether you need any further information in order to > > > inve

Re: Migration from sysvinit to systemd: reboot fails to complete

2016-12-30 Thread Felipe Sateler
On 30 December 2016 at 15:01, Francesco Poli wrote: > On Fri, 30 Dec 2016 14:15:17 -0300 Felipe Sateler wrote: > >> Hi Francesco, > > Hello Felipe, > first off, thanks for your prompt reply! > >> >> On 30 December 2016 at 13:08, Francesco Poli >> wrote: > [...] >> > I then scheduled a reboot: >>

Re: Migration from sysvinit to systemd: reboot fails to complete

2016-12-30 Thread Michael Biebl
Am 30.12.2016 um 22:16 schrieb Felipe Sateler: > Well, rebooting from sysvinit to systemd is supposed to work too, Indeed. If that's broken, it should be fixed. so > it doesn't explain everything. But, your experience appears to uncover > another bug: for some reason the sysvinit mount scripts

Re: Migration from sysvinit to systemd: reboot fails to complete

2016-12-30 Thread Francesco Poli
On Fri, 30 Dec 2016 18:16:02 -0300 Felipe Sateler wrote: > On 30 December 2016 at 15:01, Francesco Poli > wrote: > > On Fri, 30 Dec 2016 14:15:17 -0300 Felipe Sateler wrote: [...] > >> I am assuming you were running this in a boot running with > >> init=/bin/systemd > > > > Ouch! That probably