Top White Papers
Byte.com: Building A Slackware SystemDec 11, 2000, 21:54 (8 Talkback[s])
(Other stories by Jerry Pournelle)
"One of the strengths of Red Hat is that it does a pretty good job of recognizing your hardware and configuring it appropriately during installation, or even when you do something like changing out a Network Interface Card (NIC). Slackware, on the other hand, does some basic probing of video and network cards, but then leaves the rest, including kernel optimization, to the user. This has both strong points and weaknesses."
"Slackware booted up just fine off the installation CD; we logged in as the "root" superuser, then ran the cfdisk program to partition the hard drive and, alas, Slackware didn't see the brand-new Seagate drive in Ultra/66 mode. A quick BIOS check showed that the BIOS believed it was there; this was a Slackware problem...."
"With Slackware, when you tell the system to install everything, it doesn't argue with you or play cute tricks -- it installs EVERYTHING. And so we watched as all the libraries, binaries, utilities, etc., were copied over (it took about 15 minutes, as compared to an hour for the Red Hat upgrade, admittedly on a slower machine). I gave the machine the obvious name "Slacker," and an IP address for the local network. We also identified the Chaos Manor DNS server, and told it how to get out to the Internet via my Linux-based firewall Netwinder from www.rebel.com."
0 Talkback[s] (click to add your comment)