Today I used apt-get to update my suse 8.0 instalation. All went well until I rebooted later. LILO didnt work. It stopped on L. Fortunately I remembered doing the update so I figured that was the culprit. It was. After booting an installed system with a floppy, I simply went to a term window as su and ran lilo. Moral, save yourself some heartache. After an update either run lilo or have a boot disk handy so you can recover without spending a day trying to make the disks through windows. ra
Yes, I got caught with my pants down once on this as well. I did a full update after a fresh install and didn't realize that in the 496 RPM's being updated that there was a kernel update in there as well. I just simply didn't look at everything that had been downloaded. For anyone who's interested. You can see what apt has downloaded in /var/cache/apt/archives. After you've looked at what is there you can delete those RPM's unless you want them. I only got smacked once with that. The issue is though...after you do the massive update after the 8.0 install if you run apt to upgrade your system about once every week or so..your not going to get the huge amount of updates and it's much easier to manage. :) * Richard (ratcheson@earthlink.net) [020902 04:06]: ::Today I used apt-get to update my suse 8.0 instalation. All went well until I ::rebooted later. LILO didnt work. It stopped on L. Fortunately I remembered ::doing the update so I figured that was the culprit. It was. :: ::After booting an installed system with a floppy, I simply went to a term ::window as su and ran lilo. :: ::Moral, save yourself some heartache. After an update either run lilo or have a ::boot disk handy so you can recover without spending a day trying to make the ::disks through windows. ::ra -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
Greetings! There has been silencd for quite some time from the SuSE labs about the new release, so... I have to ask... When will SuSE Linux 8.1be ready to come out? Regards. ~W.
On Monday 02 September 2002 11:24 am, Ben Rosenberg wrote:
Yes, I got caught with my pants down once on this as well. I did a full update after a fresh install and didn't realize that in the 496 RPM's being updated that there was a kernel update in there as well. I just simply didn't look at everything that had been downloaded. For anyone who's interested. You can see what apt has downloaded in /var/cache/apt/archives. After you've looked at what is there you can delete those RPM's unless you want them.
I only got smacked once with that. The issue is though...after you do the massive update after the 8.0 install if you run apt to upgrade your system about once every week or so..your not going to get the huge amount of updates and it's much easier to manage. :)
Thanks to Richard Bos and Ben for your info. Richard is right, the info + cautions are there. They're just camoflaged. It would help the unwashed, like myself, if the warnings were a little less cryptic. A simple but bold CAUTION in the useage area when I was first doing the update would have made my day a lot brighter. APT is a wonderful addition and probably should be used instead of YOU. I know I will be using it more and more. Thanks to those who have made this possible. This is a great app but please, please tell us about the gotchas in plain simple terms. A simple "Watch your ass!" can save someone a lot of grief. ra
It's possible to let apt take care of executing the correct boot manager, etc after downloading/installing a kernel package via a postinstall script: Answer 29: http://apt4rpm.sourceforge.net/faq.html#q29 How do to execute a post install script from apt-get? This requires a change to apt.conf file and a wrapper around rpm. First add the following lines to apt.conf: Dir { bin { rpm "/usr/bin/aptrpm"; }; }; SystemConfig { KernelPkg k_deflt; BootMgr /sbin/lilo; } This will execute the script /usr/bin/aptrpm instead of /bin/rpm. In this script all kind of actions can be programmed. The actions can be made configurable by adding more attributes to the apt.conf file. This is just an example, it is up to your fantasy to do whatever you want it to. If you think it is interesting for others, please let us know, we can make it part of the apt4rpm project! Get the a working script (aptrpm-1) and explaination (README) from: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/apt4rpm/apt4rpm/client/ And there is a warning for this phenomenom in the apt for suse webpage: Pay attention to the packages being upgraded. If a kernel rpm (e.g. k_deflt, k_psmp, k_i386, k_*, etc) is to be updated you must execute mk_initrd and lilo. If you forget to run these 2, your system won't come up next time it's booted! If you like, you can configure APT to execute the before mentioned tools as explained here. Or use the possibility to prevent that certain rpms are to be updated, see below for more info. Op maandag 2 september 2002 13:32, schreef Richard:
Today I used apt-get to update my suse 8.0 instalation. All went well until I rebooted later. LILO didnt work. It stopped on L. Fortunately I remembered doing the update so I figured that was the culprit. It was.
After booting an installed system with a floppy, I simply went to a term window as su and ran lilo.
Moral, save yourself some heartache. After an update either run lilo or have a boot disk handy so you can recover without spending a day trying to make the disks through windows. ra
-- Richard Bos Without a home the journey is endless
participants (4)
-
Ben Rosenberg -
Richard -
Richard Bos -
Whitehawk Stormchaser