Linked by Eugenia Loli on Wed 18th Oct 2006 21:54 UTC
Permalink for comment 173165
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2006-05-24
But, unfortunately, I don't have the time these days to do all the things I love.
However, I would *strongly* recommend Slackware for anyone who wants to *learn* about this stuff, and be able to really claim they know it well. I am forever indebted to Pat for having that system available when I was first exploring UNIX. In particular -- at that time, I was just given the responsibility to generate the nucleus of an IBM 370 VM/CMS system, and it scared me to death just thinking about what would happen if I damaged a system that 500 people depended on. But at home, I discovered I needed to recompile my kernel on Slackware to address a problem with dicey hardware from a no-name vendor. After having to do that a few times, my fear of doing it on the mainframe ebbed to almost roller-coaster thrills, and I was far more self-confident.
You never really *know* a system until you have to do a lot of things yourself, and so if you want that kind of experience without going FreeBSD, get slack, and roll up your sleeves. You'll never regret it.