Linked by Thom Holwerda on Sat 17th Sep 2011 00:19 UTC
Permalink for comment 489982
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2009-03-27
I also used Arch a few years back, so it's good to hear the perspective of a fellow Slack user who was in a similar position on Arch today. Stability was my main issue back then. Also, I'm a big fan of Slackware's fat DVD install, which means that I rarely have to worry about dependencies even when building my own packages.
At any rate, I'll have to try Arch out again, though Slack works perfectly on my MacBook for now (almost--wicd has some issue with the Intel wifi chipset where if there are too many networks it won't detect any, but this is surely a wicd/iwtools issue). Thanks for the heads up!