remote-fs.target is ordered after the {auto,}mount units. In case of automount
we do not want to wait for the network to come up before proceeding. In case
of a regular mount unit, the unit will be ordered after network.target
so the behavior is unchanged.
This speeds up boot quite a bit for me when having some services needing
NetworkManager-wait-online.service, and having my home partition on nfs
under an automountpoint.
sysinfo returns the total memory size in multiples of mem_unit bytes.
As long as the size in bytes fits into unsigned long, the kernel uses
mem_unit = 1, but this is not true on i386 with more than 4 GB RAM.
https://bugzilla.redhat.com/show_bug.cgi?id=712341
MSI machines have some different vendor name, and the refix on those vendor
name are "MICRO-STAR" or "Micro-Star". So, merge the original two rules to
one, and use asterisk on dmi vendor name for support more MSI machines.
Tested on MSI U270 netbook.
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
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_paths[].
/selinux appears also in nspawn.c. I don't think it's necessary to
change it there at this point.
https://bugzilla.redhat.com/show_bug.cgi?id=711015
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
>> On Tue, May 24, 2011 at 15:33, Tom Gundersen <teg@jklm.no> wrote:
>
> Close, but no cigar. Looks like the static nodes are not assigned
> permissions 0660 even if a gid is set (the nodes have perms 0600).
>
> Cheers,
>
> Tom
We don't want to fiddle around changing the RTC, not on bootup, not
on shutdown.
If we don't run NTP, we have absolutely no clue what's the current
time to store in the RTC. If we run NTP, the kernel syncs the system
time every 11 minutes to the RTC.
Especially in multi-boot environents we must not call hwclock(8)
which tries to be smart with calculating/storing/applying drifts
and such.
Live-CDs must never touch the RTC, because we don't know if it is
running in UTC or locatime.
We check for LOCAL in /etc/adjtime and if needed, ask the kernel to
apply the timezone delta to the system clock.
The very first call of settimeofday() without a time, but a timezone
warps the system clock, so that it properly runs in UTC.
Lennart Poettering
Michal Schmidt
Tom Gundersen
Kay Sievers
Keshav P.R
Marco d'Itri
Lee, Chun-Yi
Frederic Crozat
Martin Pitt
Peter Jones
Bastien Nocera
Ozan Çağlayan
William Swanson
Harald Hoyer