[arch-dev-public] [mkinitcpio][RFC] a better fallback image?
pierre at archlinux.de
Mon Jul 30 05:55:48 EDT 2012
Am 30.07.2012 00:18, schrieb Tom Gundersen:
> On Wed, Jul 25, 2012 at 11:21 PM, Tom Gundersen <teg at jklm.no> wrote:
>> It seems to me that a more useful fallback image, would be one that is
>> generated at compile-time, rather than at install-time, and shipped as
>> a part of the kernel package. This would avoid user errors, and
>> mkinitcpio run-time problems.
>> This fallback image should contain the widest sets of hooks and
>> modules so that it should work on any hardware and any setup (at least
>> to the extent possible with our current hooks).
> I put a PKGBUILD up on AUR. Rather than making it part of the
> kernel package, I made it separate (at Thomas' request). At least this
> should make it easy to test without having to rebuild kernels.
> At the moment it simply includes all the hooks I could think of. If,
> in the future, we would like to add more features to it (e.g. pacman,
> arch-install-scripts or better networking tools), we should add
> mkinitcpio hooks to the relevant pacakges.
> Any thoughts?
> : <https://aur.archlinux.org/packages.php?ID=61313>
It'll be better to make it a split of the linux package to make sure
modules are compatible.
Pierre Schmitz, https://pierre-schmitz.com
More information about the arch-dev-public