Posted Dec 5, 2012 20:53 UTC (Wed) by nix (subscriber, #2304)
[Link]
Currently my kernel install is
make install modules_install
which I think beats yours by one line. :)
(Yet again: initramfses *do not* need to be installed in separate files -- distros just do that because it makes it easier to ship prepackaged kernels. If you link them into the kernel image, they don't make it harder to test kernels at all: the installed kernel is exactly one file, just as before. A bloody good thing too given the amount of bisection I seem to have been doing recently...)
What's initramfs do now?
Posted Dec 5, 2012 21:14 UTC (Wed) by dlang (✭ supporter ✭, #313)
[Link]
but his approach is trivial to put the kernel on a different machine, yours is not.
What's initramfs do now?
Posted Dec 5, 2012 22:17 UTC (Wed) by nix (subscriber, #2304)
[Link]
Uh? You put the kernel on a different machine by... copying one file (and copying the modules tree if need be). How is that hard?
What's initramfs do now?
Posted Dec 5, 2012 23:02 UTC (Wed) by dlang (✭ supporter ✭, #313)
[Link]
plus the system specific initramfs config (raid config, etc)....
What's initramfs do now?
Posted Dec 8, 2012 19:10 UTC (Sat) by nix (subscriber, #2304)
[Link]
If you need that sort of system-specific config baked into the initramfs, you are doing something wrong. Both mdadm and LVM can scan for things to mount: you should be relying on that, and using config files at most as defaults overrideable on the kernel command line. (A few lines of shell while loop to parse the command line and bingo.)