RE: [MLUG] SuSE

["Matt Ross" <EMAIL:PROTECTED>]

> Slackware lacks the graphics because Patrick tries to keep it simple, the
> extra graphics SuSE throws in uses up RAM/Swap and is simply a waste of
> electricity. I mean seriously who needs a geko and a blue screen on your
> tty1?

Its a convenience. YaST is a bit buggy, but I find it easier and quicker for
adding users. I've not had much trouble with it, though some have. But as
for your complaint, the difference in memory and electricity usage is
insignifigant compared to what X takes. Besides, its shell 'graphics' are
all in tools that you don't need.

> Slackware is easy to use if you don't care how secure your
> system is.

Its easy to use even if you do care. It requires reading, but not a lot of
thinking.

> Then again so is any distro/OS. One thing about Slack is you
> hafta lock it
> down, make sure you disable all services you don't absolutely
> need running
> and write a good iptables script.

Thats also true of any distro/OS. Thats why I think SuSE can be harder. You
have a LOT more to disable ;-)

> Another thing that's nice is
> you're totally
> in control of everything and it's not automated like SuSE.

Could you explain what you mean by this? SuSE gives you the option to accept
defaults which has some crappy choices, but only a fool ever accepts
defaults.

> SuSE
> is nice but
> it's so similiar to windoze it's frightening. It forces you to
> accept a ton
> of programs you don't need,

Again, you can choose what programs you put on it. Or you can choose
defaults which we all agree are crap in any system, not just SuSE.

> taking up disk space and just plain being
> annoying. Not to mention you hardly know what's going on and how can you
> really know if you're running a secure box when you use the SuSE firewall
> when you have no idea what the heck it's really doing when you click on
> Paranoid (or whatever security setting you choose). Slack forces
> you to learn
> about TCP wrappers and about TCP/IP protocols so you can write a good
> iptables script.

You can configure them in SuSE. SuSE gives you a default setup that keeps
newbies from getting into too much trouble. Just because it alllows you to
use it without getting burned, doesn't mean an experienced user can't use it
just as effectively as slackware.

> Without this knowledge you can't run a secure
> server

Agreed.

> ...and
> by the way I set up my PCMCIA wireless networking card (linksys)
> to run just
> fine on slackware.

Again, that was a driver issue. If you wrote your own driver thanks to the
skills slackware taught you, then I'll consider changing distros ;-)

> just to clarify my statement - I have nothing against SuSE, but
> in my opinion
> using SuSE is like running Windows without the BSOD. So in other
> words SuSE
> is excellent but I prefer slackware because you become more intimate with
> your box..

More correctly, you are forced to be. You can still use SuSE like any other
distro, or you can find which features make your job more efficient, use
those, and junk the rest.


_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members