Randy Kramer wrote:
>
> I can't resist either -- sorry!
>
> [EMAIL PROTECTED] wrote:
> > i can't resist this one. to add further to John's response, why are you
> > having to su so much? the only time i have to su is to install programs. i
> > just tried this, i can su & type in a password in 4 seconds. you do this so
> > often that it results in a "fair amount of lost time"? i'm sure i'm not the
> > only one who would be curious to know what you are doing to that computer.
>
> For me (and I'm not the original poster), the four seconds does not
> account for all the lost time or inconvenience. Usually I first try
> something as user. Then I realize (when it doesn't work) that I should
> have been root. Then I su to root. Then I try to remember the commands
> I typed before, and I can't use command history to scroll back to them
> -- they're in the user account command history. At first, I couldn't
> even cut and paste them from the user to the root command line (now I
> keep two konsoles open and I can cut and paste one command at a time,
> and I suspect there is something better I can learn to do in the
> future). If I haven't completely lost my train of thought by now, I do
> soon.
>
> I'm (conservatively counting) on about day 120 into my Linux sojourn,
> and my coworkers used to be amazed (at least sometimes) by what I could
> do at the dos command line.
>
> And yes, a lot of my time so far has been spent trying to get programs
> installed and running, so I needed to be root.
>
> >
> > Day One: I hate M$. I think I'll try Linux.
> > Day Two: This crap sucks. It isn't Windows.
> >
> > Windows is not Linux, Linux is not Windows. Decide which you want & use it.
>
> No -- try to get the best of both worlds, and try to go beyond the best
> of both worlds if possible!
>
> Randy Kramer
One thing thing thats great about logging in as a regular user and
"SUING" when you have to is that you really begin to understand the
inner-workings of that system. personally, being an all to trusting
Admin in a NT environment, I feel too comfortable with the rights. You
don't know exactly what you can do and the user can't, which foroges the
purpose of security in a network. I certainly wouldn't want to be
responsible for setting up a critical system share only to give everyone
and their alter-ego permissions to it. (I hate being called to the
office...I had enough in high school) <smiles> In any event, forgive me
if this point has already been made, I honestly did not read through the
entire thread before responding. But if your purpose is for a insecure
user friendly internet machine, stay with windows...no harm done. But if
you want to get intmate enough with the system to adminster its every
move, learn how it works and manipulate it.
(apologies for the last comment...I think I just gave out one of womens
biggest secrets on how to control men) <smiles<
