The Democrats and Republicans are only different with respect to how *far* they want to crawl up your ass and what they want to do once they get there.
Gee, who gives a rat's ass. If popularity was worth a tinker's damn, then we'd all just use Windows. If you want a distribution who enjoys being the Keeper of the Toilet Paper, then fine - use it - but leave the rest of us alone.
I won't say this for sure, but my first reaction is "YDIW." If one follows the instructions for upgrading from one release to the next, there won't be an "critically damag[ed] libraries" or "reinstall[ing] from scratch" at all. Granted, the docs are generally better since the 11.0 days (sorry, I have to toot my own horn with that), but even before then, they were good enough.
Heh, maybe I'm being dense (perhaps that's excusable after the last few weeks), but I'm not convinced that you're disagreeing with me. Anyone who is familiar with unix/linux at all, or is looking to switch to unix/linux, will immediately recognize Slackware as a linux-based operating system. Perhaps I wasn't clear about it, but my main point was "If grandma doesn't recognize Slackware as being a unix-like OS, then grandma doesn't need to know."
This isn't definitive, but lots of "patches" aren't patches -- they're upgrades to later releases due to upstream not providing actual patches. Sometimes that's not a problem (the new release actually is ABI-stable with the older one, or the fix is easy to backport), but in other cases, the choice is either to "fix" the security problem (which often isn't *much* of a problem anyway) or to *break* the application/library (or something else that uses it).
Generally speaking, if a security issue is serious *and* it affects a network-facing service *and* it's feasible to fix, then it's fixed in $release/patches/
Nah, there's not really a policy, and I'm not sure I can even put the decision making process into words:-) Let's just say "a long time" and leave it at that -- last I checked, Pat was still pushing occasional patches for 8.1.
There's just no way to defend this sort of behavior by the teacher in question - decisions based on ignorance are almost surely bad...
That being said, I'm a high school science teacher, and I'd be *thrilled* to see a student passing out linux cdroms. Perhaps I'm an edge case though -- I'm on the development team of an "old" linux distribution and have started a linux user group at the high school where I teach:)
Re:A site geared towards Linux user, to learn Open
on
OpenBSD 4.4 Released
·
· Score: 1
Show me a single Linux distro which has a man page for either bash or grep, two tools you mention.
Aha! Whoever maintains the.org must have noticed and changed his www record, or perhaps I just haven't noticed that before. I'm betting on the first one.:)
Yes, there is a difference.
Patrick controls one of them, and has no control over the other.
Just because it's a mirror right now does not mean that it will be a mirror in ten minutes.
That sounded like a round-a-bout way of saying "I'm couldn't figure out how to get anything working on Slackware, so I'm assuming everybody else has the same problem."
If AMD pressures their new acquisition to create a half-decent set of Linux drivers, then this will all be worth the hassle. Or even if they convince ATI to open up the specs, that would be ok too.
Um, didn't you get that backwards? The *best* thing would be to get the specs opened up; in fact, I would argue that anything less is unacceptable, but that's just me...
RW
Great post - I've thought the same for quite some time.
I won't necessarily argue that it should be different, but the popularity of a distribution is determined by several factors, of which stability and overall quality are not by default the most important. They certainly play a role in it, but ultimately, those distributions which do more "advertising" (whether intentional or not) on distrowatch have higher ratings.
It's a rigged system (in some ways), but I'm okay with it - I'll be using my trusty Slackware regardless of whether everyone else appreciates it or not...:)
Sometimes you can get away with it (early in the development cycle before big changes; some packages are just repackaged binaries; etcetera), but generally speaking, you're asking for trouble by using -current packages on a stable release. For example, this development cycle has seen major upgrades to glibc and gcc as well as several new library dependencies, so a package plucked from -current that's been built recently almost certainly won't work on 10.2.
Anyway, what you're wanting is the./slackware-10.2/patches/ directory on the mirror - keep an eye on the ChangeLog.txt for your release, as security/stability patches are always announced there.
Most of us take our rights pretty damn seriously?
How many people exercise their "right" to keep and bear arms without getting *permission* from government?
How many people exercise their "right" to peacefully assemble without getting *permission* (parade permit) from government?
How many people exercise their "right" to the fruits of their labor by refusing to allow government to confiscate it?
While evils are sufferable, they should be suffered.
RW
Well, I *try* to make my classes that way, but it's tough to do in a society that's tailored to instant gratification - everyone is like "just give me the answer."
We're covering Forces and Motion right now (focusing on velocity, acceleration, and momentum type problems), and so many of the students just sit and wait for me to finish working the examples, then write down the answers rather than actively pay attention to the process followed to obtain the answers. The analogy I gave them today went something like this:
If I'm teaching you how to build a computer from parts, you can either watch and follow along with me using the parts on your desk (learn the process), or you can wait until I'm finished putting it together and come look at the result (just give me the answer) - which one is going to give you a better chance of putting it together?
Slashdot Mirror
The Democrats and Republicans are only different with respect to how *far* they want to crawl up your ass and what they want to do once they get there.
Gee, who gives a rat's ass. If popularity was worth a tinker's damn, then we'd all just use Windows.
If you want a distribution who enjoys being the Keeper of the Toilet Paper, then fine - use it - but leave the rest of us alone.
I won't say this for sure, but my first reaction is "YDIW." If one follows the instructions for upgrading from one release to the next, there won't be an "critically damag[ed] libraries" or "reinstall[ing] from scratch" at all. Granted, the docs are generally better since the 11.0 days (sorry, I have to toot my own horn with that), but even before then, they were good enough.
Heh, maybe I'm being dense (perhaps that's excusable after the last few weeks), but I'm not convinced that you're disagreeing with me. Anyone who is familiar with unix/linux at all, or is looking to switch to unix/linux, will immediately recognize Slackware as a linux-based operating system. Perhaps I wasn't clear about it, but my main point was "If grandma doesn't recognize Slackware as being a unix-like OS, then grandma doesn't need to know."
Quite frankly, if you don't know what it is, then you're not ready for it, so it doesn't matter.
http://slackware.osuosl.org/slackware-8.1/ChangeLog.txt -- last update was 20 February 2009 :-)
This isn't definitive, but lots of "patches" aren't patches -- they're upgrades to later releases due to upstream not providing actual patches. Sometimes that's not a problem (the new release actually is ABI-stable with the older one, or the fix is easy to backport), but in other cases, the choice is either to "fix" the security problem (which often isn't *much* of a problem anyway) or to *break* the application/library (or something else that uses it).
Generally speaking, if a security issue is serious *and* it affects a network-facing service *and* it's feasible to fix, then it's fixed in $release/patches/
-RW
Nah, there's not really a policy, and I'm not sure I can even put the decision making process into words :-) Let's just say "a long time" and leave it at that -- last I checked, Pat was still pushing occasional patches for 8.1.
Ah, an old-timer who still keeps up with us; I like that three-digit id. ;-)
Just FYI, slackpkg is now in the main tree (AP series).
-Robby
http://slackware.com/~rworkman/
Wow. Just damn.
There's just no way to defend this sort of behavior by the teacher in question - decisions based on ignorance are almost surely bad...
That being said, I'm a high school science teacher, and I'd be *thrilled* to see a student passing out linux cdroms. Perhaps I'm an edge case though -- I'm on the development team of an "old" linux distribution and have started a linux user group at the high school where I teach :)
Show me a single Linux distro which has a man page for either bash or grep, two tools you mention.
$ cat /etc/slackware-version /usr/man/man?/{grep,bash}.?.gz
/usr/man/man1/bash.1.gz /usr/man/man1/grep.1.gz
Slackware 12.1.0
$ ls
Aha! Whoever maintains the .org must have noticed and changed his www record, or perhaps I just haven't noticed that before. I'm betting on the first one. :)
Yes, there is a difference. Patrick controls one of them, and has no control over the other. Just because it's a mirror right now does not mean that it will be a mirror in ten minutes.
slackware.com has address 64.57.102.34 slackware.org has address 12.246.148.57
Modded "redundant" ?? I guess at least one of the people with mod points this time around needs a "-1 HUA"
and again, it's .COM, not .ORG
12.0 released in July 2007. When anticipating a /. arrival, minimizing content on the main page is good.
The official Slackware site is at slackware.COM, not slackware.ORG. (and it's already dead as of comment #3).
That sounded like a round-a-bout way of saying "I'm couldn't figure out how to get anything working on Slackware, so I'm assuming everybody else has the same problem."
Um, didn't you get that backwards? The *best* thing would be to get the specs opened up; in fact, I would argue that anything less is unacceptable, but that's just me...
RW
Great post - I've thought the same for quite some time.
:)
I won't necessarily argue that it should be different, but the popularity of a distribution is determined by several factors, of which stability and overall quality are not by default the most important. They certainly play a role in it, but ultimately, those distributions which do more "advertising" (whether intentional or not) on distrowatch have higher ratings.
It's a rigged system (in some ways), but I'm okay with it - I'll be using my trusty Slackware regardless of whether everyone else appreciates it or not...
RW
The subject line says it all.
./slackware-10.2/patches/ directory on the mirror - keep an eye on the ChangeLog.txt for your release, as security/stability patches are always announced there.
Sometimes you can get away with it (early in the development cycle before big changes; some packages are just repackaged binaries; etcetera), but generally speaking, you're asking for trouble by using -current packages on a stable release. For example, this development cycle has seen major upgrades to glibc and gcc as well as several new library dependencies, so a package plucked from -current that's been built recently almost certainly won't work on 10.2.
Anyway, what you're wanting is the
RW
Most of us take our rights pretty damn seriously? How many people exercise their "right" to keep and bear arms without getting *permission* from government? How many people exercise their "right" to peacefully assemble without getting *permission* (parade permit) from government? How many people exercise their "right" to the fruits of their labor by refusing to allow government to confiscate it? While evils are sufferable, they should be suffered. RW
Well, just damn... I was *so* thinking of Amendment X as I was reading, and I suffered a *tremendous* brainfart obviously... my apologies... RW
Um, that's amendment 10...
Well, I *try* to make my classes that way, but it's tough to do in a society that's tailored to instant gratification - everyone is like "just give me the answer."
We're covering Forces and Motion right now (focusing on velocity, acceleration, and momentum type problems), and so many of the students just sit and wait for me to finish working the examples, then write down the answers rather than actively pay attention to the process followed to obtain the answers. The analogy I gave them today went something like this:
If I'm teaching you how to build a computer from parts, you can either watch and follow along with me using the parts on your desk (learn the process), or you can wait until I'm finished putting it together and come look at the result (just give me the answer) - which one is going to give you a better chance of putting it together?
RW