LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


View Poll Results: How often do you update your system?
As soon as I see updates are available 113 61.08%
Every few days 29 15.68%
Once a week 17 9.19%
Once a week - once a month 19 10.27%
Longer than once a month 16 8.65%
Multiple Choice Poll. Voters: 185. You may not vote on this poll

Reply
  Search this Thread
Old 01-30-2018, 01:31 PM   #31
andrew.46
Member
 
Registered: Oct 2007
Distribution: Slackware
Posts: 970

Rep: Reputation: 235Reputation: 235Reputation: 235

Quote:
Originally Posted by enorbet View Post
So why is it, I'd like to know, why apparently so many Linux users are so locked into to nearly instant upgrade cycles?
I do it for fun
 
Old 01-30-2018, 03:55 PM   #32
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 552

Rep: Reputation: 148Reputation: 148
Quote:
Originally Posted by andrew.46 View Post
I do it for fun
yes.. and for the adrenaline rush... of course: will it still work after....???? I love bugs, they're my dayjob... ;-)
 
1 members found this post helpful.
Old 01-30-2018, 03:57 PM   #33
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,486

Original Poster
Blog Entries: 3

Rep: Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503
Quote:
Originally Posted by brobr View Post
yes.. and for the adrenaline rush... of course: will it still work after....????
So this is actually a 'thing'. I wondered.
 
Old 01-30-2018, 04:08 PM   #34
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,155

Rep: Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152Reputation: 2152
Quote:
Originally Posted by brobr View Post
yes.. and for the adrenaline rush... of course: will it still work after....???? I love bugs, they're my dayjob... ;-)
I find that very odd. What sort of updates are you doing that risk anything but the new app not working? For me one of the major benefits of Slackware is that the worst that can happen, even if compiling directly from source and running "make install" instead of making a package, is that the new app won't run... until you fix it. The rest of my system is never at risk on Slackware.

Last edited by enorbet; 01-31-2018 at 10:36 AM. Reason: typo fixed
 
Old 01-30-2018, 04:20 PM   #35
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 881

Rep: Reputation: Disabled
Quote:
Originally Posted by enorbet View Post
I find that very odd. What sort of updates are you doing that risk anything but the new app not working? For me one of the major benefits of Slackware is that the worst that can happen, even if compiling directly from source and running "make install" instead of making a package, is that the new app won't run... until you fix it. The rest of my system is never at risk on Slaxckware.
He must work on Windows machines......
 
Old 01-30-2018, 04:33 PM   #36
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 552

Rep: Reputation: 148Reputation: 148
Yes, great toys to crash, give me 5 min ;-)

Last edited by brobr; 01-30-2018 at 04:34 PM.
 
Old 01-31-2018, 12:41 AM   #37
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 120

Rep: Reputation: 44
I use slackpkg to update my system. Usually, I do it as soon as new updates are released. However, being that I use the current branch on my production machine, if the update is a major one, I often wait for several days, just to be sure that everything is OK.

Last edited by Andersen; 01-31-2018 at 12:45 AM.
 
Old 01-31-2018, 02:15 AM   #38
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 881

Rep: Reputation: Disabled
@Lysander666,

You should take into account that if you are running stable, currently 14.2, that updates are *mostly* security related.

IMO any security updates should be taken seriously and applied ASAP.

But caution should be used for kernel updates if you switch to a generic kernel or generate a initrd or if you use nVidia graphic drivers.
 
Old 01-31-2018, 03:48 AM   #39
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,486

Original Poster
Blog Entries: 3

Rep: Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503Reputation: 1503
Quote:
Originally Posted by Skaendo View Post
@Lysander666,

You should take into account that if you are running stable, currently 14.2, that updates are *mostly* security related.

IMO any security updates should be taken seriously and applied ASAP.

But caution should be used for kernel updates if you switch to a generic kernel or generate a initrd or if you use nVidia graphic drivers.
Updating through slackpkg is easy on my low-powered system since it just downloads and installs the .txz files. I have indeed switched to generic and use an initrd. Can you let me know why I should be cautious in this instance? EDIT: answered here https://www.linuxquestions.org/quest...3/#post5812603

My desktop uses a beefy ATI card and my netbook onboard Intel graphics so no problems with nVidia there.

I currently refrain from installing updates from sbopkg because they don't look that necessary to me, e.g. qpdfview has had an incremental update which I haven't installed, and I have to rebuild QMplay2 for the libass update, which I can't be bothered to do currently since it works perfectly as is.

Last edited by Lysander666; 01-31-2018 at 05:48 AM.
 
Old 01-31-2018, 10:31 AM   #40
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,592

Rep: Reputation: Disabled
Quote:
Originally Posted by brobr View Post
yes.. and for the adrenaline rush... of course: will it still work after....???? I love bugs, they're my dayjob... ;-)
Well, for some people running current the goal is to find bugs before you do.
 
Old 01-31-2018, 11:17 AM   #41
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 552

Rep: Reputation: 148Reputation: 148
Well I am mostly not looking for them; I grow them ;-)

A reason to run current is better/easier support for my newish hardware; and then, yes, part of the fun is installing and thereby testing updates as they come along; mostly it is fine; sometimes a bug that is often wide-spread, i.e. not immediately Slackware related, but still important to (help) to identify. One learns a lot that way. Waste of time?? See it as a hobby.... ;-)
 
Old 01-31-2018, 12:00 PM   #42
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 881

Rep: Reputation: Disabled
Quote:
Originally Posted by Lysander666 View Post
Updating through slackpkg is easy on my low-powered system since it just downloads and installs the .txz files. I have indeed switched to generic and use an initrd. Can you let me know why I should be cautious in this instance? EDIT: answered here https://www.linuxquestions.org/quest...3/#post5812603
This is less likely on stable, but due to the recent flaws found in CPUs might be relevant.

If you switched to the generic kernel, generated a initrd, set LiLo to boot Slackware by default and let slackpkg upgrade your kernel, you can be in for some work. My advice there would be to blacklist kernel updates and make sure that you read about upgrading kernels. Personally I just run the huge kernel, so I just let it update kernels as our BDFL sees fit. Sure there might be some performance gain by switching and generating a initrd, but from what I've seen it is slight (for me at least).

Quote:
Originally Posted by Lysander666 View Post
I currently refrain from installing updates from sbopkg because they don't look that necessary to me, e.g. qpdfview has had an incremental update which I haven't installed, and I have to rebuild QMplay2 for the libass update, which I can't be bothered to do currently since it works perfectly as is.
There can be security patches and fixes with packages from SBo as well, one recent one that I use is Transmission that recently had a security patch added. So you should at least keep an eye on them.

Last edited by Skaendo; 01-31-2018 at 12:01 PM.
 
Old 02-01-2018, 10:25 AM   #43
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,592

Rep: Reputation: Disabled
Quote:
Originally Posted by brobr View Post
Well I am mostly not looking for them; I grow them ;-)

A reason to run current is better/easier support for my newish hardware; and then, yes, part of the fun is installing and thereby testing updates as they come along; mostly it is fine; sometimes a bug that is often wide-spread, i.e. not immediately Slackware related, but still important to (help) to identify. One learns a lot that way. Waste of time?? See it as a hobby.... ;-)
Yea, the Slackware maintainers catch most of the issues before they release packages, but some issues won't be present themselves unless tested on a wide variety of configurations, this is where current comes in. That said most of the bugs I find spend time on are for programs available at SBo which can have bugs/regressions due to something in Slackware updating or when the program itself updates.
 
1 members found this post helpful.
Old 02-01-2018, 05:37 PM   #44
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 552

Rep: Reputation: 148Reputation: 148
Quote:
..for programs available at SBo which can have bugs/regressions due to something in Slackware updating or when the program itself updates.
Yes, very valid; that's why this thread is helpful

BTW when I grow bugs I am literal; no computer-speak here. But to analyse/present results of experiments I use a lot of SBo-stuff some of which, I would argue, could be better in the main repository because of their high level of interoperability with stuff produced by windows/mac-programs one has to share at many work-places. Libreoffice, inkscape etc. are my tools of choice (together with gimp) which basically replaces functionality of the kde-suite which I have not installed.

Other, more specific stuff on SBo I use as well and I also run into programs that don't work/compile in current. In many cases a more recent release of the software, especially when that has been corrected to adhere to gcc-7 standards, often compiles/works again (providing the slackbuild is not heavily tweaked to adapt the software to Slackware; then a simple version change often won't work)..
 
2 members found this post helpful.
Old 02-01-2018, 06:51 PM   #45
Regnad Kcin
Member
 
Registered: Jan 2014
Location: Beijing
Distribution: Slackware 64 -current .
Posts: 198

Rep: Reputation: 132Reputation: 132
Updates to poppler and various libraries will often break Inkscape and KSnapshot, but I've been staying updated to -current for a couple of years now and I see no reason to change. If Inkscape breaks, I usually go to ponce's repo and get the newest build. Alternatively one can create symlinks that make things work again.

The benefits of staying with -current outweigh the occasional minor hassles. Although 14.2 is "stable", it doesn't mean that -current is "unstable", per se.
 
2 members found this post helpful.
  


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
system update issue using emerge --deep --update world fedoralinuxjunkie Gentoo 4 08-17-2010 03:18 AM
Online Update, System Update, WTF? Crito SUSE / openSUSE 6 05-11-2006 01:43 PM
When i update my system with yum update Yihya Linux - Newbie 1 02-22-2006 09:33 AM
Help, I can't update my system LinuxSeeker Mandriva 5 04-24-2004 06:06 AM
Can't update my system LinuxSeeker Linux - General 1 03-07-2004 09:59 AM

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

All times are GMT -5. The time now is 01:43 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