Heh. Speaking of "morons"- compare the organizational structure of a Slackware package (and yes, they are packages) to a Debian one. If you would rather have simplicity, that's fine- but questioning the intelligence behind one of the most organized distributions out there is a rather flawed stance.
Calling ~1000 hard working *volunteers* working on Debian "morons", and is just too ignorant to be considered insulting before any Debian user that knows more than what he's read from the back of a CD, or angsty Slashdot posts (you've get the idea).
Slackware, to me, seems more like a wanna-be FreeBSD more than anything else. And it doesn't even have ports... so what's the point? I love FBSD, but realy loathe using Slackware now, with all of the highly more organized and supported alternatives available.
Any halfwit could create his own distro (with lil shell scripts and all) in a day or two. You want to build everything from source?- Debian provides that, and in a much cleaner way than/usr/local/ or SRPM's could ever provide.
Use what you want. Say one way sucks. But trying to insult talented volunteers, just maintaining packages to make life easier for their friends, is pretty harsh.:)
You can just as easily use sid/unstable with the security.debian.org deb's. I do. Works fine.
But I do agree, you shouldn't be using sid for reliable servers. Example being- the latest libpam-modules (-26) was released with a typo in a debian patch for it... which rendered it unusable (no user could login). If you *just happened* to dist-upgrade at this time, say on a colo'd server out of town, you wouldn't be very happy with yourself:)
Slashdot Mirror
FIRST POST
this is dedicated to my main nizza gt!@#
gtisgay
Heh. Speaking of "morons"- compare the organizational structure of a Slackware package (and yes, they are packages) to a Debian one. If you would rather have simplicity, that's fine- but questioning the intelligence behind one of the most organized distributions out there is a rather flawed stance.
Calling ~1000 hard working *volunteers* working on Debian "morons", and is just too ignorant to be considered insulting before any Debian user that knows more than what he's read from the back of a CD, or angsty Slashdot posts (you've get the idea).
Slackware, to me, seems more like a wanna-be FreeBSD more than anything else. And it doesn't even have ports... so what's the point? I love FBSD, but realy loathe using Slackware now, with all of the highly more organized and supported alternatives available.
Any halfwit could create his own distro (with lil shell scripts and all) in a day or two. You want to build everything from source?- Debian provides that, and in a much cleaner way than /usr/local/ or SRPM's could ever provide.
Use what you want. Say one way sucks. But trying to insult talented volunteers, just maintaining packages to make life easier for their friends, is pretty harsh. :)
Nathaniel Hewitt
But I do agree, you shouldn't be using sid for reliable servers. Example being- the latest libpam-modules (-26) was released with a typo in a debian patch for it... which rendered it unusable (no user could login). If you *just happened* to dist-upgrade at this time, say on a colo'd server out of town, you wouldn't be very happy with yourself
Nathaniel Hewitt