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.
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.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
If i continually run -current, does it mean i run the latest Slackware version?
Don't need to upgrade ? Never?
So long as you constantly sync to the Changelog (i.e. keep up to date with changes) you will be always running the current development branch which will for a short time be the same as a stable release. The easiest way of achieving this I think is to mirror the tree and rsync it when changes occur. Then updgradepkg when needed keeping an eye on the Changelog.txt for possible gotchas.
If i continually run -current, does it mean i run the latest Slackware version?
Yes, and you'll have a lot of "fun" with it.
Running -current is not for everyone and definitely not for production systems or a desktop you really rely on.
Things *do* stop working once in a while, you might even encounter problems booting your installation, etc.
I run -current on two systems (one desktop and one notebook) to test new features etc. But my main computer runs the stable version, so that I can always access the internet, pay my bills, read my mail, download patches, etc.
If you are willing to test new versions, running -current is very interesting and your feedback can help other users and the Slackware team to make an even better product.
But if you want stability, stick with the stable version.
Yes, and you'll have a lot of "fun" with it.
Running -current is not for everyone and definitely not for production systems or a desktop you really rely on.
Things *do* stop working once in a while, you might even encounter problems booting your installation, etc.
I run -current on two systems (one desktop and one notebook) to test new features etc. But my main computer runs the stable version, so that I can always access the internet, pay my bills, read my mail, download patches, etc.
If you are willing to test new versions, running -current is very interesting and your feedback can help other users and the Slackware team to make an even better product.
But if you want stability, stick with the stable version.
OK.
I will contunue with the -current.
And if i got problem, i alwais have another partition with Linux ...
I always thought a fresh install was the lazy way (it's the route I usually take), as it seems to involve less work and less possible hitches than an upgrade.
For me, upgrading is the easy way. If I were to reinstall, I would repartition my drive (right now I'm wasting space and I've been meaning to do that for a while -- actually since before 12.1 came out...). Also, I would have to recompile all of my third-party apps (I am pressed for time right now, so I will probably only recompile anything that breaks -- if anything). I keep SlackBuilds for everything, so it wouldn't be *too* bad, but it would still take a long time. I would also use a LUKS/LVM setup if I actually reinstalled, and I would have to read up on that since I've never done it before. Unless I kept my /home partition I would have to copy it from a backup post-install (but keeping the partition handy would be the easy way). All in all, I think after reading UPGRADE.TXT and CHANGES_AND_HINTS.TXT, it seems like a very straightforward upgrade (simpler than 12.0 to 12.1 perhaps), and I don't think it would take much time. But I could be wrong.
so is anyone using kde4 on their new shiny 12.2 slackware ?
Trying to get it to work on gentoo laptop but the steps you have to go through on that to get it working is unreal - so i may put slackware back on there, but just wondering hows the performance of it ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.