LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 06-13-2019, 11:10 AM   #1
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 269

Rep: Reputation: 91
Slackware current update installed from liveslak


Sorry for the newbie questions. I'm new to UEFI, and current.

https://docs.slackware.com/howtos:sl...:systemupgrade

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?

Last edited by garpu; 06-13-2019 at 11:14 AM.
 
Old 06-13-2019, 12:53 PM   #2
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 269

Original Poster
Rep: Reputation: 91
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.)
 
Old 06-13-2019, 03:20 PM   #3
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 269

Original Poster
Rep: Reputation: 91
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.)
 
1 members found this post helpful.
Old 06-13-2019, 04:38 PM   #4
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 488
Blog Entries: 3

Rep: Reputation: 131Reputation: 131
Slackware current update installed from 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).
 
Old 06-13-2019, 04:47 PM   #5
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 269

Original Poster
Rep: Reputation: 91
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.
 
Old 06-15-2019, 06:06 AM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,547

Rep: Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924Reputation: 5924
Quote:
Originally Posted by garpu View Post
Sorry for the newbie questions. I'm new to UEFI, and current.

https://docs.slackware.com/howtos:sl...:systemupgrade

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.
 
4 members found this post helpful.
Old 06-15-2019, 04:16 PM   #7
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 269

Original Poster
Rep: Reputation: 91
Quote:
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.
Yup, figured that out.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
A full-featured XFCE desktop for net surfing with 2.6GB installed size, aka: How to install the Eric's XFCE LiveSlak on your hard drive Darth Vader Slackware 124 08-01-2018 07:55 PM
The LiveSlak Project: Running Slackware-Current Live Images With or Without Persistence and Installing Them onebuck Slackware 1 07-25-2018 05:03 AM
[SOLVED] HOWTO Maintain LiveSlak and -current with slackpkg. Sanity Check please bamunds Slackware 16 03-23-2017 08:41 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 04:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration