Hey gang;
Yes I already know this might belong on the bug tracker. Then again it
should also be promulgated more widely. A recent experience with the
bugtracker also dissuades me from posting there. So I will post it here.
If this info is on the forums; well I do not post there as a rule, and
certainly have not checked there (yet).
Two things came up during my recent upgrade on my desktop machine at
work. I started the upgrade last Thursday and completed it yesterday
morning.
1 - From lilo.conf (which most likely will be named /etc/lilo.conf.pacnew):
image=/boot/vmlinuz
label=arch
root=/dev/hda3
read-only
2 - From PKGBUILD for kernel26:
cp arch/i386/boot/bzImage $startdir/pkg/boot/vmlinuz26
i.e. lilo (...$ /sbin/lilo) will not successfully run with the two
different names for the image file, or worse yet; it will successfully run
with some other image that might happen to reside at /boot/vmlinuz26.
Yes, I am aware that on a previous install that is now upgraded to the new
kernel and therefore the new udev system will require the user to edit his
fstab, and lilo conf. at the very least. And he will know to do so, if he
carefully reads the console output generated during the upgrade from
kernel26.install. Nonetheless, a new install (for instance from an ftp
style install) will potentially have problems with this.
While on the subject of new installs and to whomever is in charge of said
install machinations; I filed a bug report in the last month or two at the
bugtracker. I have not received any notification that it has been attended
to *and* repaired. It was a relatively bad bug in that file(s) were NOT
being installed on an ftp install. Someone who cares might want to go look
this one up.
Anyways, thanks everyone for the attention and your time.
Very best regards;
Bob Finch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
