Hi Jacco.
 
Happy Holidays :)
 
I haven't tried, but can /boot/kernel.img (or /boot/kernel7.img) be a symlink? 
Can the bootloader handle this, if so, removing the kernel would be a cleaner 
process - just redirecting the symlink to another kernel.
 Or why don't just use the upstream pre/post scripts in the RPM ?
 
> 
> Nice! (I always edit the thing by hand)
> 
> i would recommend to use mock in stead of rpmbuild -ba, but that's a
> minor thing here.
 Haha, a discrete kick I my b*** to get my koji project going :P(on that note - 
I'm still struggling with getting sigul working correct - its so so so 
undocumented) ofc I prefer mock as well. The script was sort of a shout-out to 
the community until somebody (cough* you Jacco) will make a repo available with 
regular builds - could easily be done with a GitHub-githook (should I make 
one?).
> If you want to spend some brain cycles on this, I recently found a
> rather annoying bug in the rpm. the bug is in the (un)install scripts.
> Installation goes fine, but on remove it does the wrong thing. (and as
> update is actually an install followed by a remove, updates don't work
> as expected.) I remember some recommendation somewhere long time ago NEVER 
> "update" a kernel, always do an "install". I think it is set in upstream 
> yum.conf only to install kernels. 

> point is that there are files called kernel-<version> in /boot and that
> the one to be used is to be copied to kernel.img. on install this works
> well, we know what kernel was installed and copy that to kernel.img. on
> remove however we should make sure that one of the kernels, that is
> still there, is copied to kernel.img (people might want to remove the
> latest kernel). Hmm not a 100% perfect solution could be doing a cp 
> /boot/kernel.img /boot/kernel-<the_new_kernel_verion>-bak.imgon pre-insand on 
> post-uncopy it back to /boot/kernel.img Then at least you do a backup and 
> restore in the RPM?
BR
Bjarne

                                          
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users

Reply via email to