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.
Hello to everyone,
Been lurking on these forums for a while now, I mostly "active" on the #! forums but am running slackware for a while now.
Started out in the slackworld with Zenwalk and from there to Salix and finally to the mothership. I came from the Debian world.
But slackware had me convinced pretty quick.
I'm running stable.
At work I still have to rely on windows however....
Glad to have you in the Slackware forum and LQ.
Jump in, the waters not to bad here at LQ!
Click here to see the post LQ members have rated as the most helpful post in this thread.
This is a great guide, but please remove the "M$" and change it to MS or Windows. The M$ stuff looks unprofessional, and it needs to die.
Thanks for the compliment and I hope this thread will continue to be useful for everyone.
I use M$ and will continue to use the software when necessary. I've used 'M$' from the beginning and will continue. As to unprofessional for using a icon[3] representation for Microsoft, your call or opinion not mine.
"You must look into people as well as at them."-Chesterfield
Thanks for the compliment and I hope this thread will continue to be useful for everyone.
I use M$ and will continue to use the software when necessary. I've used 'M$' from the beginning and will continue. As to unprofessional for using a icon[3] representation for Microsoft, your call or opinion not mine.
"You must look into people as well as at them."-Chesterfield
Does the "$" stand for pharmacy symbol ("medical snake") ?
;^)
P.S.
Hi, onebuck,
Just a side-note, I greatly appreciate Your efforts around here, got trough many a showstoppers thanks to Your thread... , do keep up as much as You can!
I do attempt to stay current with this thread without redundancy. Things are slowly starting to happen in '-current' and 13.37 tweaks are available within the Slackware Forum by doing a Slackware Forum Search. Plus do not forget Alien_Bob's Blog, very useful & informative from a Slackware contributor.
If you have not signed up for Slackware's Security Advisories, please do so.
Look too SlackwareŽ-Links for very useful links. More than just Slackware links!
Be sure to look at 'current' ChangeLogs for a track of what is happening.
I do attempt to stay current with this thread without redundancy. Things are slowly starting to happen in '-current' and 13.37 tweaks are available within the Slackware Forum by doing a Slackware Forum Search. Plus do not forget Alien_Bob's Blog, very useful & informative from a Slackware contributor.
If you have not signed up for Slackware's Security Advisories, please do so.
Look too SlackwareŽ-Links for very useful links. More than just Slackware links!
Be sure to look at 'current' ChangeLogs for a track of what is happening.
Hi Onebuck,
The security advisories page is not in sync with the actual changelog.txt. If you want to stay up-to-date with Slackware security, the best way to do it is by following the changelog for your version of Slackware.
Hi Onebuck,
The security advisories page is not in sync with the actual changelog.txt. If you want to stay up-to-date with Slackware security, the best way to do it is by following the changelog for your version of Slackware.
The link that I provided is for Slackware's Security Advisories main page. Some users do not use '-current' so they can use the security advisories. The heads up from PV & team can be had via email when a user signs up.
As to the 'changelog' for user's version of Slackware, well that is for the recent stable version architectures. There are loads of Slackware users that still use earlier versions so a means to advise of potential problems via the advisories is a good thing. Slackware is used throughout the world and not everyone is using the newest version.
The thing with Slackware is,
that the releases outlast any other distro releases out there, and might be compared only to Win NT5.1 which was "actual" form 2001 up to 2009
Besides that, Slackware beats any other I know about?
The link that I provided is for Slackware's Security Advisories main page. Some users do not use '-current' so they can use the security advisories. The heads up from PV & team can be had via email when a user signs up.
As to the 'changelog' for user's version of Slackware, well that is for the recent stable version architectures. There are loads of Slackware users that still use earlier versions so a means to advise of potential problems via the advisories is a good thing. Slackware is used throughout the world and not everyone is using the newest version.
BTW, more than one way to skin a cat!
Thanks for the point of view as a user.
I haven't received an advisory email since Oct.14. Even then, it was 3 days behind the date on the changelog. The changelog for 13.37 x86_64 stable reflects 5 security fixes since oct14, and I did not receive an advisory email for any of them. The advisory pages also do not reflect the changelog's security fixes. I have had a few people confirm the out-of-sync lists and they've all told me to follow changelog.txt instead.
Thanks for taking the time to reply, onebuck. Is there still something about this issue that I'm missing?
well, one should watch fr changes in the /patches directory of it's release.
And consider SBO-ing the packages affected in -current's Changelog?
I did a slackbuild of a Firefox on a 12.2 once to bypass the old one in /patches
:2c:
I haven't received an advisory email since Oct.14. Even then, it was 3 days behind the date on the changelog. The changelog for 13.37 x86_64 stable reflects 5 security fixes since oct14, and I did not receive an advisory email for any of them. The advisory pages also do not reflect the changelog's security fixes. I have had a few people confirm the out-of-sync lists and they've all told me to follow changelog.txt instead.
Thanks for taking the time to reply, onebuck. Is there still something about this issue that I'm missing?
The differences between the changelog for '-current' and stable will be different. As the disparity with stable and advisories, PV would have to answer that.
Personally, I do watch '-current', advisories and changelog(s) to see if something needs attention. I have yet to experience issues by watching all. If a user doesn't watch or even signs up for advisories then the only way to know an issue is to physically do the checks or experience the problem then check to find a solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
?
won't happen again sir!
