Re: Of mice and men





"Donald Tees" <donald_tees@xxxxxxxxxxxx> wrote in message

[more than what appears but I snipped forgetting to mark that in
here...sorry]

> It is an open OS, that runs as a client/server model, full fledged
> multi-user system ... unix at the command line, with enough security that
> logged in as a normal user, I cannot change even another user's data, let
> alone the OS software (as with a virus)

This would depend on how well the sysadm (you or otherwise) and your users
maintained their environment no?
This is no different to many environments OS - even windows. Your system is
only as strong as its weakest point.


> Then, on top of that, you have a user logging in and using a GUI, browser,
> etc., in the local user space. That is the reason the security is so good
> ... if I log in as a user and erase everything I can find on the disk, I
> only harm my own account.
Again, this is not wholly true. It depends on ....see above.

There are many programs that have in the past been used to exploit Linux -
programs running as "root" even though you are just a plebian user.

I'd be less inclined to comment if you stated that its "more automatically
encouraged". Many distributions will force you to use a non admin
account....but this could also be done in Windows etc etc....people just
view windows as a "home" OS and most "home" users just don't want to deal
with the fact that there are more than one way to protect yourself.

> I can then log out, log in as an administrator, and create a new account
> for myself that will be set up from scratch. That user will start with a
> brand new "welcome to" screen etc., just like a new OS for a single user.
> I digress.

> RPM files. The RPM file is a relatively new way of packaging Linux
> software. This is a system, actually, that unpacks, compiles, installs
> and keeps track of software installed in a local data base. It has
> facilities for checking specified sites for changes, upgrades etc, and
> automatically installing them. It can also remove software, give you
> lists of dependancies, etc. I would recogmend to any beginner that they
> stick to RPM packages until they have their feet wet. Mandrake and Suse
> both use this package by default.
SUSE actually has a delta rpm system now I understand.

> KDE and Gnome. KDE and Gnome are the two more poular GUI's. Both run
> under Xorg screens, so can co-exist. The Xorg screen's can run remotely
> under both Windows and Linux, so you can run a program on a windows
> machine that is actually running on a remote Linux server. KDE is a more
> business-like look to me ... quite a formal screen. Gnome looks more like
> a kid's toy, bright colours, larger icons. Lots swear by it, though, and
> I understand it is extremely good for those with bad eyes.
> There are also several stripped down GUIs that would be ideal for building
> OEM systems. I can start with a blank screen and no menu's, for example,
> and build a very restricted GUI for something like a cash register.
>
> Caveats. The learning curve is horendous. After a year, I am past the
> screaming in rage and banging on my screen with the keyboard stage, but
> not by a lot. Documentation ranges from not too bad to "what?". There
> are a million variations for everything, and only 75 of each have been
> tried. The people that tried them in 70 of those cases will be rude and
> obnoxious. They will talk to you, but probably not until after you have
> figured it out for yourself (what else is new?).
I've found that the Linux community is a varied bunch like CLC. For every
one that is obnoxious there is one that wants to help :-) I have found that
there are occasions when I go through a dependency loop (download RMP A
which needs RPM B which needs RPM C which needs RPM D)...

I have found that the "non kernel" packages are so dynamic it's a constant
case of - if it aint broke don't fix it....then after 6-7 months download a
new distro :-)


> Bottom line ... I am having more fun than I've had for years, and the
> damned thing does *exactly* what you tell it to. If you are really stuck
> ... check the source. There are no secrets. Backup and restore work,
> without having to jump through hoops. The annoyances are of the "so
> *thats* the way it works!" sort rather than "those bastards! they screwed
> me AGAIN!" type. I like it.
>
> Donald

A lack of help is no different to a secret: "Documentation ranges from not
too bad to "what?"."

I do like your post, it corresponds much to what I have found - and neither
of us are (or pretend) to be experts so it's - if I may speak for you - a
novices guide to crap that we've found starting on this which I think is
good for other new starters. I am *amazed* at the level of growth and
improvement over the last 5 years....

JCE


.