Age | Commit message (Collapse) | Author | Files | Lines |
|
The archive goes from looking like this:
.
./buildconfig
./config
./init
./init_functions
./VERSION
./lib64
./sbin
To:
buildconfig
config
init
init_functions
VERSION
lib64
sbin
Note the lack of the "root" entry and leading "./". This fixes an issue
with packing ucode into the initramfs since the kernel really wants an
exact match, and not path equivalency.
|
|
This hook adds host-specific configuration to the image. Currently,
it adds the hostname and machine-id files for usage with journald.
|
|
As seen:
https://bbs.archlinux.org/viewtopic.php?id=185204
https://bbs.archlinux.org/viewtopic.php?id=185265
|
|
Fixes FS#41273.
|
|
Use this to only add files matching *.conf in the modconf hook.
Fixes FS#39994.
|
|
Fixes FS#40217.
|
|
Fallback on no compression at all, since we don't want to make
potentially poor assumptions about what the kernel might support.
Fixes FS#39659.
|
|
Fixes FS#39560.
|
|
|
|
|
|
Fixes FS#38603.
|
|
This patch adds in some extra hackery to make sure that users with btrfs
root filesystems don't end up with unusable initrds due to the following
change made upstream [1]. TL;DR: The btrfs module has dropped it's
libcrc32c dependency, so mkinitcpio no longer pulls in the crc32c module
necessary for the btrfs module to be inserted. The crc32c module was
only pulled in previously due to mkinitcpio hackery [2], so extra
hackery now seems like the logical path.
This problem can be experienced by using linux-mainline on an Arch
machine with a btrfs root filesystem. Besides from this extra hackery,
an alternative workaround would be for users in this situation to add
crc32c to their MODULES aray in their mkintcpio.conf. Of course, this
needs to be done ahead of the linux-3.14 upgrade for them to avoid the
problem (assuming none of their other modules depend on libcrc32c).
[1] http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg30912.html
[2] https://projects.archlinux.org/mkinitcpio.git/tree/functions?id=v16#n398
|
|
Prevents problems with bogusly named filesystems, e.g.:
mount -t tmpfs / /mount/point
Fixes FS#39090.
|
|
|
|
Should have been removed as part of previous commit, as this was
clearly just a typo.
|
|
Reported in FS#38264.
|
|
This isn't documented, but it's needed since the kernel lz4 support is
based on the original streaming format and not the newer default. Use
-l to force the legacy codec.
Fixup lsinitcpio to support the older format, and, add a warning when
the newer format is detected. Who knows when this will be "resolved" ...
Upstream discussion: https://code.google.com/p/lz4/issues/detail?id=102
|
|
|
|
This hook works together with the systemd hook from the systemd
package and requires the add_systemd_unit function.
It launches systemd-vconsole-setup.service in initramfs
and is especially useful to unlock encrypted volumes in
initramfs.
|
|
Pretty much everyone benefits from this service, as it is always better than
having no shutdown-ramfs. If someone puts their own shutdown-ramfs in place,
it will likely be done by initramfs and this service will be skipped
automatically.
In more obscure situations, it can still be masked.
|
|
|
|
This is surely a configuration error as it's an infinite loop.
|
|
|
|
This lets users shoot themselves in the foot more easily, as they can
put their own modified hooks into /etc/initcpio/{hooks,install} to
override those shipped by the distro in /usr/lib/initcpio.
To make debugging easier, include the full path of the hook being used
when mkinitcpio runs in verbose mode.
Implements FS#37796.
|
|
When the module directory matching $(uname -r) cannot be found, generation
of the shutdown ramfs aborted:
systemd[1]: Starting Generate shutdown-ramfs...
mkinitcpio[1944]: ==> ERROR: '/lib/modules/3.12.1-1-ARCH' is not a valid kernel module directory
systemd[1]: mkinitcpio-generate-shutdown-ramfs.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Generate shutdown-ramfs.
systemd[1]: Unit mkinitcpio-generate-shutdown-ramfs.service entered failed state.
Tell mkinitcpio that we do not wish to add any kernel modules.
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
The '-k none' switch prevents mkinitcpio from adding modules to the
image and keeps it from bailing out when it cannot find any.
|
|
This allows booting from devices which have labels like LABEL=/.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
When enabled, this service generates an "initramfs" that systemd
pivots to on shutdown to ensure clean umounting and shutdown of
loop and dm devices.
The actual work is done by systemd-shutdown.
|
|
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
The -d (--generatedir) option writes the root of the generated image
directly to the specified directory.
Useful for generating a shutdown-ramfs with mkinitcpio -d /run/initramfs/.
|
|
This essentially reverts 306dcbd7b21f8a680 which foolishly assumes that
kernel and libarchive decompression support stay in sync.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
This will allow systemd's kernel-install script to generate and install
an initrd as per the freedesktop boot loader specs.
See kernel-install(8) for details.
Notice that 'profiles' are not used.
This will eventually be hooked up so that calling "make install" from
a kernel build will do the right thing.
Signed-off-by: Tom Gundersen <teg@jklm.no>
|
|
Since b5927393d103af9, mkinitcpio acknowledges that lz4 exists.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
As suggested by Harald Hoyer, this is more accurate for the sake of
following where udev gets its modaliases from. In some rare cases, it
may even be more complete than scraping the raw modalias files.
Also, introduce a wrapper around modprobe so that the options passed
are never ommitted, or wrongly specified. In this case, a subtle bug
with the -r flag is fixed due to using the wrong variable with
modprobe's -d flag.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
It doesn't make any sense that this was added during the final image
creation. This fixes a subtle bug that would manifest itself if the
user archived the build root manually.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
The impetus for doing this was a bug in util-linux's hexdump which never
saw a release. For uniformity, simply echo an empty line here.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Note that this requires a very recent version of lz4 utilities as it
uses lz4, and not the original lz4c tool, in order to be command line
API compliant with other compression tools. See upstream discussions:
https://code.google.com/p/lz4/issues/detail?id=83
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Running as non-root is usually for my own dev purposes, but someone
might do this and be surprised when a directory/file that needs
permissions other than root isn't preserved.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Using --tab-file for findmnt calls is redundant if we can rely on the
defaults. Sanitize the environment from any LIBMOUNT_* variables so
that we can be sure of what file we're reading.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Doing this oddly results in findmnt never stat(2)'ing the target
directory, which might be problematic with stale NFS mounts and maybe
autofs.
Fixes FS#36629, I suppose.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Add an annoying warning in case the root device is fsck'd and about to
be mounted RO.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
Shaves a trivial, but measurable, amount of time off of early userspace
at the cost of a small cache file.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|
|
This allows 'quiet rd.log=kmsg' to produce a silent boot while still
logging the full output that would have been written to the console.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
|