Slashdot Mirror
Slackware 11 is Coming
ejd3 writes "In the slackware-current changelog Pat has stated that 'Although there's still quite a bit in the TODO queue here I'm making my steps carefully as -current is very stable, and I think it should ship as a stable 11.0 soon so that we can get back to the business of breaking things in -current. :-)' How much longer will the slackers have to wait?"
I doubt that... Never tried Slamd64, but maybe Patrick could make it some sort of "official port" or something like that... I've heard Slamd64 was rock solid and very "conservative" (maybe that's not the right word to use, but what I want to say is that it follows Slackware's path/philosophy).
- English is not my native language, so please excuse me if I mess things up -
Or just install 10.2, then install slapt-get and add your favorite slackware mirror's -current as a source.
You could use Slamd64. But regular Slackware will work fine on an AMD64: I believe that Pat is using one as his development machine. He wrote somewhere that he tried compiling 64-bit versions of various things, but he didn't see any performance improvement from it, so he abandoned the experiment. Of course it would be a different matter on a high-end server with lots of memory, but that's not Slackware's target market.
I hate to disagree with you, but you must be both misinformed *AND* smoking pretty powerfull shit ...
...
Slackware is _THE_ most rocksolid stable distro there is. Which is why slack fanboys can give mac fanboys a run for their money on sheer loyalty.
And also why a *large* proportion of slackware installs are servers. It is most definitively *not* just a hobby system, although you can learn a lot using Slackware.
If you really insist, you can automate Slackware just as well as any other distro (slapt-get?).
Somehow I start wondering what you mean by 'custumize'-ing
I've seen a few comments above from people saying that Slackware makes poor economic sense. I say it can make economic sense in many cases.
/etc/init.d though?).
Slackware is a distro, like any other - and just like any other distro you tend to have to be familiar with it in order to get things done efficiently. However, what Slackware does let you get away with is to update packages direct from the developers without having to worry about exploding the "package database" or maintainance system. If you want "fancy" package handling systems you can use the likes of slapt-get or similar. Slackware won't tear you apart or breakdown into a locked up mess if you install something from a "non-slackware-approved" source package.
The default relative daemon sparseness of Slackware makes it quite easy to keep an eye on, especially if you're trying to keep an eye out for malicious things. The whole start up script system is rather simple enough too (will we get a soft-linked
That said, there's a few things which I wish were included by default in slackware (and perhaps will be in the future) but no single distro is perfect. Nearly all distros require some degree of tweaking.
Best of all though, Slackware is quick to download, quite often you only need the first ISO and you've got yourself a fairly comprehensive system ready to go, for someone who knows what they're doing.
well i can only say that we use Slackware at our company...and guess what we, are in the train control business and yes we handle ppl safety. Train control itself is done with propriatary solutions but sopport servers run slackware. regards SD
There are a couple of slack-based AMD64 systems besides SLAMD64. I liked SLAMD64, but haven't found it as trouble-free as some others apparently have. Frugalware claims to be pretty much Slackware with Pacman bolted on, and I liked it a lot. I also just downloaded something called Bluewhite 64 Linux, another unofficial port. That goes on my testing partition this weekend (replacing STX Linux, another Slackware derivative I was testing for installation on a friend/potential convert's older laptop).
So if Slackware is a niche player now (which I don't believe), then one part of that niche is as a base for new distros -- the excellent Zenwalk (which I run on my laptop), STX, Frugalware, Voltalinux (Slackware with pkgsrc?), Slax and Vector, just off the top of my head. Not as many derivatives as Debian, perhaps, but certainly a healthy number and probably indicative of a healthy distro.
I think Slackware's biggest "problem" is that it has little to no "community," at least as far as vocal fanboys (you know, the kind who visit Distrowatch to click through and drive up its numbers). I think it tends to attract and keep a self-sufficient, quieter crowd, and therefore its presence isn't as great as its numbers, if that makes any sense.
And text, of course. As soon as I boot up and people see text instead of a pretty splash screen I see that sphincter-tightening look come over some of their faces.
But beyond the entertainment value it's probably a bad thing.
that's a bad idea
...; do cd "$i"; upgradepkg --install-new *.tgz; cd ..; done; updatedb && ldconfig; init 3
swaret and slapt-get can bork your install very easily
unless you know exactly what slapt-get does
it's much wiser to rsync the current tree
then following the instruction in UPGRADE.TXT
which is basicly go to init 1
upgrade glibc shared libs, sed and pkgtools
then the rest: for i in a ap
Other than noting that he is recovered, none that I've noticed. A private person, which I respect.
If you want your life to be different, live it differently.
Bollocks. I use Slackware ina very production environment (Telecomms) where money counts and have never had a single failure or any issues whatsoever accountable to Slackware. Our RedHat servers often break and to fix them you either compile yourself and RedHat usually breaks or you call RedHat and get their official patches (for which you need to pay support). I know what I'd rather be using.
you have the a.o.l.s usenet newsgroup and more importantly :D
the ##slackware channel on freenode
Don't forget the wiki!
I am not your blowing wind, I am the lightning.
Pat already does that.
Change your slapt-get sources over to the stable branch, and you'll get security updates.
Or you can pre-order 11 here http://store.slackware.com/cgi-bin/store/slack11.0 ?id=7qg7pUeb:mv_pc=27 support the project, and look forward to 12.
Having to work for a living is the root of all evil.