LinuxQuestions.org

This is a semi-random collection of posts on nearly all things Slackware and Linux-related -- at least as I see it.

Slackware “Clean Upgrade” (with pre- and post-installation tasks)

If you are upgrading to the very next version (eg 13.37 to 14.0) I suspect that there is not very much difference between following UPGRADE.TXT and your third method. However, many of the steps you list in your third method make sense to follow which ever method you upgrade with.

One advantage of following UPGRADE.TXT is that new /etc configuration files are copied and given the extension *.new. If I run diff somefile somefile.new (something UPGRADE.TXT doesn't say to do) I can examine the output and then decide whether to switch to the .new file, keep the old file or just incorporate some of the changes from the new file into the old file. This helps to ensure that I don't run into problems because of some customization that I forgot about in a new installation.

Posted 02-21-2013 at 11:03 PM by psionl0 psionl0 is offline

Updated 02-21-2013 at 11:06 PM by psionl0

Slackware “Clean Upgrade” (with pre- and post-installation tasks)

I noticed no one had commented on this nicely presented set of instructions so I wanted to give you a thumbs up on what you wrote up. A friend of mine instructed me on this method of upgrade a while back when I jumped from Slackware 11 to 12. I am about to go from 13 to 14 and could not find his instructions so this post really helped me out. This post was way more detailed however much of it might not apply but it is still worth having.

I am a little more paranoid so before I upgrade I also ghost my drives using dd or fsarchiver so that I can do a full recovery if something goes wrong. I also do this in case of a hard drive going bad ... which almost never happens ;^)

cheers!

Posted 02-20-2013 at 03:00 PM by cygnus-x1 cygnus-x1 is offline

Build Notes for LFS 6.6 with Package Users -- Part 2

great stuff! Thanks!

Posted 06-07-2011 at 09:22 AM by Janek566

Keeping multi-lib Slackware64 up-to-date. . .

Lufbery,

Good post. I have been manually doing the same things to keep my multilib Slackware13.1_64 updated, all the while thinking to myself that I need to write a script to automate it. I appreciate what you have done, and I will try it out. A sticking point in my thinking has been how to handle the 32-bit system files. I had about come to the conclusion that it would be more efficient for me to just download AlienBOB's converted "compat32" files rather than maintain a list and convert them, but it hasn't been clear to me whether or not he is maintaining 13.1 compat32 files since they haven't changed. I see that the "current" compat32 file list has been changing.

Thanks again,
--DrWhyN0t

Posted 12-10-2010 at 06:28 PM by DrWhyN0t DrWhyN0t is offline

First post: building Gnash on Slackware with src2pkg

for example: http://koji.fedoraproject.org/koji/b...buildID=191393

Code:

boost-date-time.i686 : Runtime component of boost date-time library
boost-date-time.x86_64 : Runtime component of boost date-time library
boost-devel.i686 : The Boost C++ headers and shared development libraries
boost-devel.x86_64 : The Boost C++ headers and shared development libraries
boost-doc.noarch : HTML documentation for the Boost C++ libraries
boost-filesystem.i686 : Runtime component of boost filesystem library
boost-filesystem.x86_64 : Runtime component of boost filesystem library
boost-iostreams.i686 : Runtime component of boost iostreams library
boost-iostreams.x86_64 : Runtime component of boost iostreams library
boost-math.x86_64 : Stub that used to contain boost math library
boost-mpich2.i686 : Runtime component of Boost.MPI library
boost-mpich2.x86_64 : Runtime component of Boost.MPI library
boost-mpich2-devel.i686 : Shared library symlinks for Boost.MPI
boost-mpich2-devel.x86_64 : Shared library symlinks for Boost.MPI
boost-mpich2-python.i686 : Python runtime component of Boost.MPI library
boost-mpich2-python.x86_64 : Python runtime component of Boost.MPI library
boost-openmpi.x86_64 : Runtime component of Boost.MPI library
boost-openmpi-devel.i686 : Shared library symlinks for Boost.MPI
boost-openmpi-devel.x86_64 : Shared library symlinks for Boost.MPI
boost-openmpi-python.x86_64 : Python runtime component of Boost.MPI library
boost-program-options.i686 : Runtime component of boost program_options library
boost-program-options.x86_64 : Runtime component of boost program_options
                             : library
boost-python.i686 : Runtime component of boost python library
boost-python.x86_64 : Runtime component of boost python library
boost-regex.i686 : Runtime component of boost regular expression library
boost-regex.x86_64 : Runtime component of boost regular expression library
boost-static.x86_64 : The Boost C++ static development libraries
boost-system.i686 : Runtime component of boost system support library
boost-system.x86_64 : Runtime component of boost system support library
boost-thread.i686 : Runtime component of boost thread library
boost-thread.x86_64 : Runtime component of boost thread library
boost-wave.i686 : Runtime component of boost C99/C++ preprocessing library
boost-wave.x86_64 : Runtime component of boost C99/C++ preprocessing library
mingw32-boost.noarch : MinGW Windows port of Boost C++ Libraries
mingw32-boost-static.noarch : Static version of the MinGW Windows Boost C++
                            : library
boost.x86_64 : The free peer-reviewed portable C++ source libraries
boost-graph.i686 : Runtime component of boost graph library
boost-graph.x86_64 : Runtime component of boost graph library
boost-graph-mpich2.i686 : Runtime component of parallel boost graph library
boost-graph-mpich2.x86_64 : Runtime component of parallel boost graph library
boost-graph-openmpi.x86_64 : Runtime component of parallel boost graph library
boost-serialization.i686 : Runtime component of boost serialization library
boost-serialization.x86_64 : Runtime component of boost serialization library
boost-signals.i686 : Runtime component of boost signals and slots library
boost-signals.x86_64 : Runtime component of boost signals and slots library
boost-test.i686 : Runtime component of boost test library
boost-test.x86_64 : Runtime component of boost test library

Honestly, I do not need 60 megabytes of the complete boost library, I just need the relevant parts for Gnash.

Posted 11-26-2010 at 04:30 PM by Tryum Tryum is offline

Updated 12-04-2010 at 09:18 AM by Tryum

	First post: building Gnash on Slackware with src2pkg I would like to know if it is possible to build a smaller package of Boost (with the SlackBuild script) by including only the libraries that are really needed (e.g. like Halite BitTorrent Client)?
	Posted 11-22-2010 at 05:58 AM by Tryum Updated 11-22-2010 at 01:13 PM by Tryum

Transferring data from Palm Desktop to Thunderbird Lightning...

I may be missing something, but I've read this a couple of times. I've seen no major issues syncing my palm TX to both my jpilot ('buntu) and my PD on Windoze. That being said, I'd suggest jpilot for both of your home machines with a twice daily rsync of your jpilot and hers. Then configure Jpilot to use T-bird for mail-to. No need for cloud calendar. Hope it helps.

Posted 11-19-2010 at 06:35 PM by slingshotsuicide slingshotsuicide is offline

	Build Notes for LFS 6.6 with Package Users -- Part 2 about smilies ... Quote: Originally Posted by crts Hi, is it possible to disable the smilies? E.g. in the section perl: 'perlerl' has a smilie in between. Yeah. I noticed that. I'll take a look to see if I can disable them and update the post. Yup. I disabled the smilies.
	Posted 11-07-2010 at 07:11 PM by Lufbery Updated 11-07-2010 at 07:56 PM by Lufbery

	Build Notes for LFS 6.6 with Package Users -- Part 2 about smilies ... Hi, is it possible to disable the smilies? E.g. in the section perl: 'perl:perl' has a smilie in between.
	Posted 11-02-2010 at 12:40 PM by crts

Build Notes for LFS 6.6 with Package Users -- Part 1

Thanx for the articles, I plan to look at this later.

Posted 10-22-2010 at 05:55 AM by peonuser

	A slacker builds Linux From Scratch! Thank you Lufbery, well written, very informative, quite useful, looking forward to reading about your subsequent efforts with BLFS. much appreciated, CAI ENG
	Posted 10-19-2010 at 03:29 PM by caieng

	A slacker builds Linux From Scratch! LFS is just a lots of fun and lots of learning, if making it for the first time It's not a big performance overhead in fact, but can be great for some unstandard server environment.
	Posted 10-14-2010 at 02:54 AM by Web31337

A Script for Keeping Slackware Up-to-date...

Quote:

Originally Posted by Web31337

The general catch of Slackware, IMO is that you actually free to update whenever you want. And since that, I guess most users won't need that if they doing this manually.
But that looks nice though i didn't test it

Thanks!

True enough. However, the updates often have more than one package, and this script saves a bunch of time downloading each package, checking their integrity, and upgrading with them.

Thanks for looking!

-Drew

Posted 02-04-2010 at 12:06 PM by Lufbery Lufbery is offline

	A Script for Keeping Slackware Up-to-date... The general catch of Slackware, IMO is that you actually free to update whenever you want. And since that, I guess most users won't need that if they doing this manually. But that looks nice though i didn't test it Thanks!
	Posted 02-04-2010 at 09:40 AM by Web31337

"Slackware Linux assumes you're smart."

slackware...
i'll tell how i came to know that system.
one day, back in 2008 i got back home after a day i spent watching my friend configuring router on slackware. i thought i can manage it that easy myself, lol!
i got slackware 12.1 that day(it was latest back then) and tried to install. i was totally confused =) i decided to wait. then one my buddies brought me ubuntu 7.10 and that was trashed as well. i tried ubuntu 8 later and with the same feelings it was thrown away but i never really thrown away that slackware DVD knowing that one day i will beat that system. at that moment i was working in windows(yes, since 2005 i was by the summer of 2009).
then i got to know all the real destruction power of windows that was killing my PC and moved to linux, to debian lenny. since i work on it. in august 2009 i installed it to a very old PC (PI, 200mhz, 64M SIMM RAM 2.1G hdd) and made a router from it with debian lenny and iptables(i failed to do that with router-distros are meant to be user-friendly but it came out they are hardware unfriendly requiring either too much ram or space or doing some things i don't want to). i felt like im skilled with linux enough so i tried gentoo. when i built it and run from a first try(o_0 i thought it can't be) i thought it's a good time to challenge slackware ;)
so i did. fetched 13.0 release and started installing. at the point of installing LILO it failed to install it automatically(12.x won't fail at that step). it was trying to install boot loader or find kernel(don't remember now what) on /dev/hdc which simply not existed in my system(NO IDEA where it has taken it from, perhaps some bug, my cdrom was /dev/hda and hard drive was /dev/hdd ) i configured it by googling and manually editing lilo config booting from slackware DVD and mounting my newly created partitions.
i really love this system but right now im using gentoo and debian.
i see gentoo as a half-way to creating my LFS in a nearest future(yes i will make lfs, for ARM PC when i will get one here in Russia).
planning to move entirely on gentoo and move secondary server from gentoo to slackware =) i found these two distros as most "transparent" and since that, they seem easy for me to manage.
<3 slackware <3 gentoo

Posted 11-26-2009 at 12:39 AM by Web31337 Web31337 is offline

	So when should one upgrade? I agree with you on your upgrade opinons. If your software is working with no problems then why upgrade? I even hesitate on Security some times. It seems everytime I do an upgrade there are other problems created that have to be worked out.
	Posted 11-13-2009 at 05:53 AM by Larry Webb

A quick review of Slackware 13 and KDE 4.3.1 on my old laptop...

Quote:

Originally Posted by rich_c

I'm doing a similar exercise (i.e. dipping my toe in the KDE4 water) with a KDE4 version of SimplyMepis (DanumLinux Canteras 3c) and have come to much the same conclusion. By which I mean I'm looking forward to the day when KDE4 makes an appearance on my main desktop!

So far, I'm liking KDE 4. It's not as drastically different from KDE 3.5 as I expected, but it is a little cleaner and faster. I'll probably drop it on my Desktop when I get around to upgrading it, but I want to work out the bugs with it on my laptop first.

-Drew

Posted 10-16-2009 at 12:23 PM by Lufbery Lufbery is offline

	A quick review of Slackware 13 and KDE 4.3.1 on my old laptop... I'm doing a similar exercise (i.e. dipping my toe in the KDE4 water) with a KDE4 version of SimplyMepis (DanumLinux Canteras 3c) and have come to much the same conclusion. By which I mean I'm looking forward to the day when KDE4 makes an appearance on my main desktop!
	Posted 10-12-2009 at 03:14 PM by rich_c

about smilies ...

about smilies ...