>>I'm a sissy, I use YaST, SuSE's config tool. Set up my dhcp, scanner, printer and zip drive out of the box.
>
>You know, I only have one big gripe with SuSE. What the hell is up with them using variables for their SysV init script decisions?

They use /etc/rc.config as the major connection between YaST and the main
install script, SuSEConfig, which fires all the other perl scripts relating
to all the other services. You can edit rc.config yourself. There is an option in YaST to do that directly, after which SuSEConfig fires automatically. Or, as root you can edit rc.config manually and then fire SuSEConfig manually when you've saved your rc.config edits. Just editing rc.config without firing SuSEConfig will result in nothing happening, even after a reboot of the system.

> How are you supposed to add new stuff that isn't already in the SuSE/Yast(2) package??

You can fire YaST without putting a CD in the CDROM drive. Then, when it asks you for "SOURCE:", you can supply the internet URL or local directory where the rpm(s) reside that you want to install. Or, if you have xrpm or (in KDE) Kpackage you can fire them and point them at the rpms you which to install. It's all the same rpm database. Actually, in KDE, just clicking on the rpm file will bring up KPackage automatically. As you know, of course, doing that as a user or root depends on the package and/or the intent.

In using either of these options you will have to edit either boot.local or ./.bashrc to add any needed environmental vars, or menu options to KDE, which is very easy to do.

>
>Yast(2) is nice, but I find it a little difficult to follow.

I've used it twice. In fact, YaST2 is the ONLY way you can setup an alsa sound server for your installation, a fact that doesn't make me happy since I prefer not to use YaST.

>
>Of course, I'm old school "edit the config yourself so you know what is happening".

As I acquire more knowledge of Linux I find myself doing the same. However, somethings are always more easily (and accurately) done with scripts and using a menu program to access those scripts makes their use even easier, and less accident prone, something to always avoid while in as root.

>
>j