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: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Original Poster
Rep:
Quote:
Originally Posted by Windu
The .txt file containing the script that mlangdn shared was not identical to the original version of that script which I downloaded at http://www.slackware.com/~alien/tool...are-current.sh
The version from slackware.com works out of the box for me.
yes, I changed the URL in that script and then worked. It was an extra slackware64-current/ which I removed and then worked, see below. Thanks!
Slackware is the stable version - which is 15.0 (32 bit)
Slackware-current is the testing version. (32 bit)
Slackware64 is the stable version - which is 15.0 (64 bit)
Slackware64-current is the testing version (64 bit)
Each stable version only changes for security updates.
Obviously, the testing versions will change often, and running current means you are willing to except a risk of breakage.
Distribution: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Original Poster
Rep:
Quote:
Originally Posted by mlangdn
Slackware is the stable version - which is 15.0 (32 bit)
Slackware-current is the testing version. (32 bit)
Slackware64 is the stable version - which is 15.0 (64 bit)
Slackware64-current is the testing version (64 bit)
Each stable version only changes for security updates.
Obviously, the testing versions will change often, and running current means you are willing to except a risk of breakage.
Then what is slackware-15.0/ and slackware64-15.0/? I thought these are the frozen versions for 32b respective 64b.
Is any diff between slackware64-15.0/ and Slackware64/ ?
Distribution: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Original Poster
Rep:
Quote:
Originally Posted by mlangdn
No diff between slackware64-15.0 and Slackware64.
Slackware64 is the 64 bit version. Slackware by itself is 32 bit. It is not hard.
my questions was not about arch either 32 or 64. I understand now there is no diff between slackware64-15.0 and Slackware64 OR slackware-15.0 and Slackware my question was why there are 2 similar folders? Just one would not be enough?
Although the URLs for slackware64 and slackware64-15.0 are different, my guess is that we're looking at the result of the equivalent of symlinks. Different names that ultimately resolve to the same files.
When Slackware 15.1 (or whatever the next stable version is) comes along, Slackware64 will change its destination to the latest stable version (-15.1), leaving Slackware-15.0 to continue to be updated as a "not-the-most-current-but-still-stable" version.
People on the bleeding edge can always go to -current, while people seeking the most recent stable version can always got to Slackware64. People wanting older stable versions go to the one with the version number they need.
Distribution: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Original Poster
Rep:
Quote:
Originally Posted by dhalliwe
Although the URLs for slackware64 and slackware64-15.0 are different, my guess is that we're looking at the result of the equivalent of symlinks. Different names that ultimately resolve to the same files.
When Slackware 15.1 (or whatever the next stable version is) comes along, Slackware64 will change its destination to the latest stable version (-15.1), leaving Slackware-15.0 to continue to be updated as a "not-the-most-current-but-still-stable" version.
People on the bleeding edge can always go to -current, while people seeking the most recent stable version can always got to Slackware64. People wanting older stable versions go to the one with the version number they need.
you are right about that, that is why I questioned. They are the same symlinks.
slackware64-15.0 (for the latest-stable) and slackware64-current (for edge) would have been enough.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
