| Age | Commit message (Collapse) | Author | Files |
|---|
|
This allow to set a custom timeout for udev events processing.
Close FS#20764
Signed-off-by: Seblu <seblu@seblu.net>
|
|
Close FS#19952
Signed-off-by: Seblu <seblu@seblu.net>
|
|
fakeraid and lvm
|
|
|
|
|
|
|
|
|
|
This check was removed in the bashification, add it back.
|
|
been activated.
|
|
No idea why it would output anything, but it does in case of failure.
Suppress the standard error.
|
|
The original version was incorrect and misleading. The new one is
confusing and too long. Instead of printing it on boot, we should
document license handling in the beginner's guide.
|
|
The copyright makes no sense, as a variety of people worked on Arch.
Remove it.
Clarify that software distributed in Arch is often distributed under
licenses different than the GPL.
|
|
The check was wrong, every device was treated as LUKS. Also remove
the _isluks variable, as now it is not used by the SWAP sanity check
anymore.
|
|
This improves the sanity check before overwriting a partition with randomly
encrypted swapspace. A device will only be overwritten if blkid finds no valid
file system on it, otherwise the process will be aborted.
|
|
Filter blacklisted modules with a parameter expansion and add an extra
conditional to modprobe to only act if the resultant expansion has a
value. It's important that no quoting takes place here, or else a
variable is defined with a null terminator and which will cause the
extra conditional to pass and modprobe will error out.
Signed-off-by: Dave Reisner <d@falconindy.com>
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
This is usefull for udev and other processes that do not get a
PATH set by /etc/profile.
The particular choice of paths to export was taken from systemd,
the rationale being that systemd is designed to be compatible with
all the major distros and in particular with udev.
The paths are also the same as set as standard in /etc/profile
With this patch we handle the PATH variable similarly to what systemd
does (in their case the variable is set in init).
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
Variable was not set before use, so the check for LUKS always failed. As noted, this could be dangerous.
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
For LUKS encrypted root partitions it is possible to store a keyfile hidden as raw data onto a USB stick with the dd command. This has the advantage, that the key is saved on a USB stick, but can't be found be just mounting the USB stick.
The appropriate line in /etc/crypttab is similar to the kernel parameter in /boot/grub/menu.lst:
home/dev/sdaXBLOCKDEVICE:OFFSET:SIZE
[teg: fixed whitespace and expanded paths to binaries]
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
It now follows the vim modeline at the bottom of the file.
|
|
Monitoring does not work when /var is mounted ro, so only enable monitoring when we know that /var is rw.
Thanks to Thomas Bächler for pointing this out.
|
|
|
|
in locale.sh
This should go some way towards obsoleting /etc/profiled.d/locales.sh
(FS#20911).
The remaining, and admittedly main, obstacle is proper inheritance of LANG, which Roman is
working on.
|
|
this is done by udev since version 155
|
|
No FS reference, but this is what is done upstream (in udev's systemd
service files).
|
|
The standard type to trigger is devices. This patch makes the type explicit
and also triggers events of type subsystems. This is what is done
upstream (in udev's systemd service files).
|
|
|
|
|
|
|
|
Split out reading /etc/crypttab and procssing the individual lines into
their own helper functions, and bashify the resulting shorter code.
Processing this file is still ugly, though. :(
|
|
Use bash-style conditionals when setting up the hardware clock.
Trying to stick with POSIX syntax only just slows things down.
Bashify module loading in rc.sysinit.
bashify bringing up the loopback adaptor.
Simplify test to see if we should assemble arrays at startup
find has a builtin delete action. Use it instead of exec'ing rm.
Flatten adding persistent rules.
|
|
Use findmnt command new in util-linux-ng 2.18 to make mtab
based on /proc/self/mountinfo. Otherwise use current method.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
(added a check whether /proc/self/mountinfo exists -- Thomas)
|
|
Our current process of initializing /etc/mtab is
hackish and probably error-prone, replace it by
simply copying /proc/mounts.
|
|
Creating the RTC device will result in an error if devtmpfs is used,
as it already exists after loading the module. The new code skips
the mknod if the device is already present.
Additionally to rtc-cmos, we now also try to load rtc and genrtc,
as some custom kernels use the "old" misc RTC device instead of
the newer RTC class. In this case, the created device is also
different. This should fix FS#18078.
|
|
This sets FSCK_STDERR to /dev/stdout, but still makes it possible
to override this behaviour in a hook.
|
|
This is necessary as the new udev defaults to --action=change which
breaks network device renaming.
|
|
devtmpfs instead of tmpfs if supported by the kernel
|
|
We don't want fsck looking at any network device, and we would otherwise
check things like iSCSI devices during boot before the network was up. This
doesn't quite work.
Fixes FS#17887.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
The cryptsetup binary will move to /sbin/cryptsetup and the static binary
will be removed. Add code that will try /sbin/cryptsetup first, then
/usr/sbin/cryptsetup and fall back to the old /sbin/cryptsetup.static
if everything else fails.
|
|
|
|
|
|
|
|
|
|
This is an Arch initscripts original (commit 98c76a4), but is not actually
necessary for hwclock to operate correctly, so kill it. The file is created
automatically when `hwclock --systohc` is invoked.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
hwclock calls appear to block somewhere between 1 and 2 seconds when we have
back-to-back calls. My theory (without looking at the code) is that hwclock
has to synchronize to the 1 second intervals of the hardware clock, so it
can sometimes take up to a second to complete.
To get around this unpleasant behavior, we can background the calls at point
X in the boot sequence, and then later at point Y in the script (when we
absolutely need the clock actions to be complete), we wait on the
subprocess. This allows the rest of the boot sequence, after the hwclock
code block, to continue until the point where we wait on the subprocess.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
combination with the new udev-based device mapper node creation
|
|
after udev has settled
|
|
latest device-mapper rules
|
