Am Sat, 29 Jun 2013 13:48:46 +0200, scheib Per Jessen:
root wrote:
That is fine Per, if you "know" what kernel you are building, which system installs usually don't, it is in a makefile somewhere in an RPM, so yes your suggestion is ok, mkinitrd -b $opt_boot -i initrd-$tag -M System.map-$tag -k vmlinuz-$tag -v is what I use, just so I can use mkinitrd AS IS, but that is a workround to the basic BUG, mkinitrd should not disturb EXISTING initrds, just leave them alone, saves al problems with a simple call of mkinitrd hosing all kernels. I found this chasing down a non 86 arch bug that broke symlinks made by cpio, but mkinitrd clobbering slowed the debug loop X 5. See attachment mkKern
The sole problem is that mkinitrd re-makes ALL initrds by DEFAULT, and thus silently break existing boot combinations. Also mkinitrd's command line arguments, which let you linit this are un-intuitive and complex.
Isn't that just: mkinitrd -i <initrd> -k <kernel> ?
-- Per Jessen, Zürich (13.7°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Greetings (mit freundlichen Grüßen), Brian. Dr. Brian O'Mahoney Email: omb@teraflex.ch Phone: +44 (0) 7711 489965 GPG Key ID: E4A3BCF8 2009-12-11, old PGP Key Id: 0xA0481D676FBC700C