On Thu, 20 May 2004 09:05:41 +1200, Don Gould <[EMAIL PROTECTED]> wrote:
Yes the flame about what user I was logged in as went on and on and on to
the point where I just skipped over the messages in the end.

Always a good way to learn - just ignore the "community" who are trying to educate not just you, but onlookers. It's obvious that you don't want to know how to do things, just "what buttons to press". Ever wondered why Microsoft documentation is a series of screenshots, and unix documentation is a discussion on how the software works?


What I learnt from that was that root has access to everything (which I
already knew) and using it is a good idea if you don't want security rights getting in your way!

What you might need to learn one day, especially if you mess with computers belonging to other people (i.e. customers) is that security rights are there to protect you and the system from each other. Firewalls don't protect a machine from an application problem, do they? So an internet-connected machine better be locked down internally as well as externally. If you keep reading, you might learn something.


<rant>
As far as all this linux box hacking goes, I say bring it on community if
you want to help MS win!!!
That is the fastest way I can see of helping MS win the open source war and getting us all back on track to a 100% MS world!
</rant>

Hacking? Do you mean hacking as in "cracking", or hacking as in "fixing/exploring"?


It's already too late for a 100% Microsoft world. There never was such a thing in the past, and there will never be one in the future. There is more to the world than just the cheap Intel x86 chipset, which is the only place that Microsoft run (basically). Even if we don't have Linux, we'll still have Open Source ... and if you look further into the subject, there's Open Hardware projects too. Should Intel etc. go down the hardware-DRM route, geeks will move over to Apple/SGI/Sun expensive hardware, and then hack the Open Hardware specs until they can rebuild cheap computers again.

-jim

Reply via email to