SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
That looks great. I might use it more for people I install Slackware for (I don't want to bother with any crappy distribution nor Microsoft outside work)! Looking forward to grub support...
For myself, I keep my personal copy of the package tree with custom rsync script derived from Alien Bob's and upgrade by hand.
Still, I am lazy and use slackpkg after that to check for *.new files...
I use slackroll to do updates on most of my machines now and I have a helper script to create my initrd as well as run grub (slackroll allows you to jump to a shell to run whatever you want when it detects a kernel upgrade).
Please don't view the above comment as anything negative about @Chuck56's script! (It's just how I do stuff now.) He wrote something that he found useful and shared it with the rest of us. That's a very good thing and I have absolutely no wish to discourage others from doing something similar.
I wish you the best of success, maybe I'll use it someday. So far, I err on the side of caution, weighing the inconvenience of updating vs letting the script do it.
So far I am not inconvenienced enough to try automation, because if something goes wrong then I'd like to be there, consciously.
Like that one time I accidentally deleted my home partition and could stop it just in time (not related to slackpkg updates, but, an example) and it only ate my virtualbox images, phew.
Granted, there's backups for that, but blehhhhHHHHHHHhhhhHHhhHHhhHH.
One of the things that I had been intending to do was to write a script to do what autoslackpkg does. So when I read this post I was quite interested. I installed autoslackpkg on 12/1/19, after I had done the updates of that date, including the 5.4.1 kernel. autoslackpkg handled the updates of 12/1/19 with no problems at all.
I have another -current installation in vbox, which had not been updated to the 11/30/19 changes. This update contained a kernel update & autoslackpkg choked on the kernel update. All worked well until the reboot in the middle of the update process, & elilo failed on the reboot. I rebooted with the install disk, then chrooted into my system. The new kernel has been installed properly, the new initrd has been installed, & all have been copied into the /boot/efi/EFI/Slackware directory. However, elilo.conf is strange:
Did you edit elilo.conf before launching autoslackpkg? For sure the default line is a mess. I'll look at it some more later today. I need some recovery time from the morning out in the snow.
Yes. I modified all files before running autoslackpkg. elilo.conf looked like the first part of what I posted, down through the first two stanzas, except for the Default line. Thanks.
Bill
I wonder how "#slackpkgupdate" got inserted as the release number instead of "5.4.0". I'm impressed! The kernel_search function does the heavy lifting for those values. I'm not sure yet how that value was introduced.
I wonder how "#slackpkgupdate" got inserted as the release number instead of "5.4.0". I'm impressed! The kernel_search function does the heavy lifting for those values. I'm not sure yet how that value was introduced.
I have no clue. I do intend to crawl through the script to try to figure how it works, but haven't done any bash scripting except for simple ones for my own use (I used to make a living programming in C++, but haven't done that for 20 years). I did go back in & modified elilo.conf to have the last two stanzas refer to 5.4.1, as they should, & now the vm boots as it should, I can select either Generic or Huge from either 5.4.0 or 5.4.1. The 12/2 upgrades were posted before I finished, so ran autoslackpkg again. It worked perfectly without the kernel upgrades.
Regards,
Bill
The script is designed to ignore kernels from testing. I’ll take a look at what happens when a testing kernel is already installed like in your case. Thanks for giving it a go!
OK. I hadn't even thought that I was updating a testing kernel. If I have time, I will install a 4.19.X kernel in the vbox system & see how the upgrade from that to 5.4.1 goes. I keep the vbox system pristine for for compiling programs for my main systems.
Thanks again,
Bill
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
