| Age | Commit message (Collapse) | Author |
|---|
|
things unnecessarily
|
|
It was possible for the "ExecStartPre=-/bin/plymouth quit" to race
with plymouth-start.service which is pulled in indirectly by
basic.target -> sysinit.target.
The race left plymouth running on the terminal, making it unusable for
rescue purposes.
https://bugzilla.redhat.com/show_bug.cgi?id=710487
|
|
FUSE and configfs is very very similar, so handle both the same way.
|
|
systemd to refuse the rescue.service
|
|
mounted since we'll enumerate that fact anyway
|
|
Since hugetlbfs cannot be compiled as kernel module there's little point
in doing on-demand mounting via autofs for it.
|
|
Since the mqueue support cannot be built as a module there's little
benefit in having an autofs mount point set up for this.
|
|
Since securityfs cannot be build as module there's little value in
having an on-demand autofs mount point for it.
|
|
Since debugfs cannot be compiled as module there's little benefit in
having it as autofs mount point.
|
|
The mount point directory /sys/kernel/config is only created after the
module is loaded, hence there's little value in having this an automount
unit: the runtime penalty for mounting an autofs here should be the same
as for a real mount.
|
|
|
|
mounted the directory
|
|
With output of services going to syslog by default now, the rescue shell
units need to direct their output to tty explicitly.
Specify stderr too, just in case.
|
|
|
|
$LANGUAGE is a GNU extension that is probably worth supporting, since it
allows specifiying an order of languages.
https://bugs.freedesktop.org/show_bug.cgi?id=40510
|
|
non-socket-activatable syslogs anymore where that was ncessary
|
|
|
|
transaction to allow dynamically disabled plymouth
|
|
|
|
creds on connections
|
|
binary we'll spawn
|
|
|
|
enabled in kernel
|
|
|
|
|
|
|
|
/etc/rc.local is a symlink.
|
|
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
Explicitly disconnect all clients from a VT when a getty starts/finishes
(requires TIOCVHANGUP, available in 2.6.29).
Explicitly deallocate getty VTs in order to flush scrollback buffer.
Explicitly reset terminals to a defined state before spawning getty.
|
|
|
|
|
|
|
|
|
|
|
|
This commit consists of the initial work to include MeeGo as a ported
distribution for systemd.
The majority of the changes are small configuration additions to auto
tools, so that MeeGo is identified as a valid distribution option.
Some small deviations will be noticed between the configuration of MeeGo
and other distributions. As MeeGo is a distribution striving for
compliancy to support its near embedded attributes and target users,
there is less user configuration options available by default. Most
services will be enabled by systemd as part of the distribution
requirements, and as such most links and service files will be pre-setup
for the MeeGo distribution. As much of this is going to be done within
the MeeGo distribution packaging this is still noteworthy to mention, as
it explains why in systemd you will observe configuration differences
where the MeeGo distribution removes all links in the pkgsysconfdir for
instance. MeeGo will be user configurable if there is desire, but most
services will be enabled by the distribution as designated by the MeeGo
compliancy standards.
Other changes are in source to add such areas as meego-release defined
in utils, and hostname in hostname-setup, defining vconsole-setup,
localizations and rescue additions as needed.
As this is all ground work, MeeGo will continue to strive for complete
compatibility.
|
|
|
|
|
|
http://www.freedesktop.org/wiki/Software/systemd/hostnamed
|
|
|
|
|
|
around when isolating
|
|
emergency mode without pulling in sysinit
|
|
don't have it
|
|
|
