Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This is the counterpart to a similar patch to initscripts, making sure that the change applies regardless of whether initrd is used.
Thanks to David Reisner for pointing out that this was needed.
|
|
Fixes FS#19666
|
|
If a symlink such as /dev/disk/by-uuid/xxxxx is provided on the kernel cmdline,
resolve it and mount that device instead of the symlink. This prevents some
ugliness in the output of commands such as mount or df.
Signed-off-by: Dave Reisner <d@falconindy.com>
|
|
|
|
|
|
These devices might be actually needed before (dev)tmpfs is mounted,
for example when uvesafb is built into the kernel (no module). By
creating them in the image, they will be present as soon as initramfs
has been extracted. Fixes https://bugs.archlinux.org/task/19903.
|
|
install/memdisk
|
|
|
|
This rule creates /dev/memdisk if a memdisk has been found.
|
|
This hook creates a block device for virtual disks created
by memdisk (http://syslinux.zytor.com/wiki/index.php/MEMDISK).
|
|
All it does for now is cause a Btrfs scan so we can mount multi-device
volumes.
|
|
Replace some seds with tr and bash pattern removal
|
|
Needed to get libcrc32c and therefore btrfs to work. Also remove the
equivalent section in autodetect, which wasn't working anyway.
|
|
This error went unnoticed after auto_modules was switched over to
resolve-modalias. As a result, ata_generic and ide-generic weren't
filtered anymore.
|
|
|
|
These devices used to be present because they were added in the image.
Since we now mount {dev,}tmpfs early in initramfs, the devices from
the image will be invisible. In the tmpfs-case, create the devices
manually so everything will be in order until udev is started, or
if udev isn't used at all.
|
|
|
|
persistent storage rules
|
|
|
|
before switch_root
|
|
the real root
|
|
|
|
|
|
remove more eval hacks
|
|
Patch was provided by Mark (voidzero) in https://bugs.archlinux.org/task/19109
This requires busybox commit http://git.busybox.net/busybox/commit/?id=8ce1dc03c1b2b61e51527b987579c09c991cc4b2
which is in the 1.7 branch, a backport will be included in an updated mkinitcpio-busybox package
|
|
In this way, remove eval hacks and enviroments vars, just use blkid
syntax.
I guess in this way will fix/hide "command not found" when fstype
is not property setup in fs, reported by some users.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
|
|
|
|
|
|
Devices will never "magically" appear when udevd is not running. Thus,
poll_device now exits instantly when a device when udevd is not running.
The return value is unchanged, just the delay is removed.
Assuming that the drive is available just after loading the module is
unsafe. However, "fast" devices like most (all?) pata/sata seem to
work this way for many people. On "slow" devices like USB, we still
have to wait - those will not work without udev.
|
|
|
|
rootdev variable
This is nicer and more explicit than before, based on a patch by Benjamin Richter
|
|
This matches the change from http://repos.archlinux.org/wsvn/packages/?op=comp&compare[]=%2Fudev%2Ftrunk@68711&compare[]=%2Fudev%2Ftrunk@69509
|
|
|
|
|
|
|
|
|
|
NFS options of the style nfsaddrs=* and ip=dhcp (without the long : syntax) used to be supported
by kinit, but were undocumented in Arch's help. This change hopefully restores full compatibility
with old kinit configurations.
|
|
|
|
|
|
mount point
The old check couldn't distinguish different tmpfs mounts and failed to work with aufs (archiso).
This check is actually the same one that busybox/switch_root uses to determine where
to stop deleting files. If this check fails and we still launch switch_root it may start
deleting data.
|
|
|
|
mount handler (default_mount_handler)
|
|
Instead of having special NFS code in /init, make it possible for a hook to register a mount handler
When a hook sets the mount_handler environment variable, the normal mount code will be skipped and
the handler will be called with the path to mount point as the first and only argument.
|
|
terminate before continuing
|
|
|
|
exist on it, bail out instead of panicing
In these cases, we will exec /bin/sh, such that manual recovery is still possible as sh has PID 1
An expert might be able to mount and switch_root manually. In any case, this is less scary than a panic and a useless trace.
|
|
|
|
|