[SOLVED] Slackware current update installed from liveslak
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is this still accurate for current? But I won't have to do a clean system upgrade, since it's already slackware-current once I run setup2hd? And is this still the process for installing a new kernel? Am I completely overthinking things, and this is like what I'm used to on stable?
Answering my own question, I think, but I'm leaving it open, if anyone has any words of advice on upgrading a kernel with UEFI and slackware-current, but it seems exactly the same as stable. (I'm installing multilib atm.)
Another answer to my own question. Found this, which looks to be useful: https://blog.paranoidpenguin.net/201...lackware-14-2/ (For 14.2, but the process seems to be same. I haven't updated the kernel yet from what was on liveslak.)
Upgrading current is flawless unless changelog has a warning and usually it's a shared library bump that only breaks third party packages.
Keep in mind that current may break things. To be more secure, update your local mirror and wait a few days before upgrading after a look at this excellent forum (where you might see if there's any glitch).
Yah. I was expecting things to blow up, because a new install on brand-new hardware ALWAYS blows up. And...it didn't. Was smooth as silk. I haven't done the kernel yet, but that's usually no big deal.
Is this still accurate for current? But I won't have to do a clean system upgrade, since it's already slackware-current once I run setup2hd? And is this still the process for installing a new kernel? Am I completely overthinking things, and this is like what I'm used to on stable?
The URL you mention is useful when you upgrade from, say, 14.1 to 14.2 or 14.2 to -current.
Apparently you installed Slackware using the 'setup2hd' script of Slackware Live. Once you have done that, your fresh install has zero relation to the Live OS: what you installed is a 'regular' slackware-current.
From that moment onwards you can treat your computer's OS like any other -current installation. There's ample documentation for maintaining a -current installation.
The thing with UEFI is that you need a copy of your installed kernel (from /boot) and optionally an initrd in /boot/efi/EFI/Slackware/ and the elilo.conf file in that directory needs to be configured to boot that kernel and its initrd. The 'eliloconfig' script takes care of that when you install Slackware (it also installs a "Slackware" boot entry in your computer's UEFI configuration).
Kernel updates have to be handled manually by you afterwards.
From that moment onwards you can treat your computer's OS like any other -current installation. There's ample documentation for maintaining a -current installation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.