The machine only runs with users as root if the user doesn't set it up
right.
the argument you made is mostly based on setup of the machine, its easy
enough for a person with no idea to screw up Linux as windows.

I use windows 2k and almost never login as admin (fathers machine hasn't had
admin logged in for 5 months now). Any XP system I've used I make sure to
setup people using user level access and an admin account.
if you want to in doze you can lock the users down to the point the system
is basically unusable for anything other than browsing the net with one
window open and no toolbars. (and you can turn that off if you want too)
again its all down to setup not OS.

I believe the buffer overrun causing crashes is in parts of the OS and
drivers not in userland applications.
I have written code that has crashed explorer (i.e. everything you see in
windows) but the system itself has been fine underneath, started explorer
again and all was well.




> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Herbert Graf
> Sent: Friday, 5 December 2003 1:32 AM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: [OT]: NASA's new mandate ???
>
>
> > It has nothing to do with OS.
> > There is a reason they are called Lusers remember.
> > he wasn't even talking about a re-boot
> > anyway
> > the common Luser will click on anything that pops up on their
> > screen saying
> > "download me to keep your computer all spiffy" these things are
> invariably
> > scumware. one friend of mine had 18 count them 18 things running in the
> > system tray, and he wanted a new computer because his one was
> running like
> > crap.
> > it doesn't matter if you have a UNIX, bsd or godlike OS, there is
> > no way to
> > combat the Luser.
>
>         Actually it does have to do with the OS. Windows, in it's
> current form (and
> most common use) is always running as "root", the user can do
> whatever they
> want. In *nix this isn't the case, root is almost never used by a user,
> therefore the worst a user can do to a system is destroy their own small
> environment, which can be restored with a few commands by root. Windows,
> from a security standpoint, has been, and remains to a large part,
> defective. Why can a buffer overrun in an application cause the
> whole system
> to crash?? That's NOT how it's supposed to work, and even today Windows is
> vulnerable to this sort of thing. TTYL
>
> ----------------------------------
> Herbert's PIC Stuff:
> http://repatch.dyndns.org:8383/pic_stuff/
>
> --
> http://www.piclist.com hint: The list server can filter out subtopics
> (like ads or off topics) for you. See http://www.piclist.com/#topics

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics