On Tue, Jun 7, 2011 at 00:48, Michal Schmidt wrote:
> The kernel now provides the /sys/fs/selinux mountpoint and libselinux
> prefers it if it's available.
>
> systemd currently tests only for /selinux and this leads to an infinite
> loop of policy reloads in the latest Rawhide.
>
> Fix it by chec
The kernel now provides the /sys/fs/selinux mountpoint and libselinux
prefers it if it's available.
systemd currently tests only for /selinux and this leads to an infinite
loop of policy reloads in the latest Rawhide.
Fix it by checking both possible mountpoints.
Also add the new path to ignore_p
On Mon, Jun 6, 2011 at 22:31, Michal Schmidt wrote:
> cryptsetup-generator parses the options in /etc/cryptsetup incorrectly.
> It fails to find the 'swap' option in
> swap,foo
> and instead it matches on
> swaplalala,foo
>
> The condition for the comma separator is reversed.
>
> https://bugzill
cryptsetup-generator parses the options in /etc/cryptsetup incorrectly.
It fails to find the 'swap' option in
swap,foo
and instead it matches on
swaplalala,foo
The condition for the comma separator is reversed.
https://bugzilla.redhat.com/show_bug.cgi?id=710839
---
src/cryptsetup-generator.
On Mon, Jun 6, 2011 at 17:58, Avi Kivity wrote:
> On 06/06/2011 06:47 PM, Kay Sievers wrote:
>> On Mon, Jun 6, 2011 at 15:01, Avi Kivity wrote:
>> > I have a system which was upgraded to F15 and thus systemd. During the
>> > boot
>> > process it times out starting various .device units, like s
On 06/06/2011 03:01 PM, Avi Kivity wrote:
I have a system which was upgraded to F15 and thus systemd. During the
boot process it times out starting various .device units, like
sda1.device.
A general advice: Always use stable names (UUID, LABEL,
/dev/disk/by-*/...). You never know which disk th
On 06/06/2011 06:47 PM, Kay Sievers wrote:
On Mon, Jun 6, 2011 at 15:01, Avi Kivity wrote:
> I have a system which was upgraded to F15 and thus systemd. During the boot
> process it times out starting various .device units, like sda1.device. If I
> let it alone it will boot in about a week
On Mon, Jun 6, 2011 at 15:01, Avi Kivity wrote:
> I have a system which was upgraded to F15 and thus systemd. During the boot
> process it times out starting various .device units, like sda1.device. If I
> let it alone it will boot in about a week or so, but meanwhile it is
> unusable. I am abl
I have a system which was upgraded to F15 and thus systemd. During the
boot process it times out starting various .device units, like
sda1.device. If I let it alone it will boot in about a week or so, but
meanwhile it is unusable. I am able to start it up using
emergency.target and various h
