|
I've found that slackware is not at all difficult to get going.
what you need to know:
the basics of partitioning.
how to run setup (type setup, ididoth)
the X configuration utilities (xorgcfg, xorgconfig, X -configure)
how to type startx.
now you're at your web browser and you have the necessary means to do the rest yourself.
dial-up or wireless internet will set you back quite a bit, figure it out on another distro with command line stuff, then you'll be somewhat prepared.
drivers come in the form of kernel modules, whether they're there is entirely dependant on the version of the kernel, whether the distro felt like including them, and if they're in the kernel at all. if they aren't some distros might have their kernel patched with it. ownership of such a device is a major pain.
And then there's this (in)famous platitude: "If you use RedHat, you learn RedHat. If you use Slackware, you learn Linux."
I hate that saying, it's misguided, what it really means is
If you configure linux using distro-specific tools, you've learned nothing that will help you if you ever get off your arse and try something else.
the saying comes from the fact that slackware doesn't have many distro-specific tools at all. the one that babies you the most being 'netconfig' but it really is necessary so that people who just installed can get further assistance. it does however make you want to learn not to use it anymore by making you redo your network config every time you want to change one setting.
slackware provides the best environment for you to get experience that will mean something in nearly any distribution of linux.
|
