Slashdot Mirror


User: styroteqe

styroteqe's activity in the archive.

Stories
0
Comments
5
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 5

  1. Re:Why? on Linux Snobs, The Real Barriers to Entry · · Score: 1

    That's ridiculous! If you want a babied down candified experience that is engineered for the lowest common denominator, fine, maybe there's no desktop solution for that yet, though MickeySoft is coming awfully close. For those of us that like to think of things on a more logical level, with less limitations on what we can do with OUR hardware, there are a great many options. And if we learn them and then shun others who wish to learn, what are we accomplishing?

  2. Re:An Unfortunate Reality on Linux Snobs, The Real Barriers to Entry · · Score: 1

    Well put, brother. I don't think any little bit of knowledge makes you superior, and especially not if you don't share it. And, regardless of what you might know, what obscure bits of knowledge you might have crusted up in your cranium, there's always someone out there that knows more, there's no need to try and be king of the knowledge hill. This holds true regardless of what OS you're running under the hood.

  3. VNC debate on Which VNC Software Is Best? · · Score: 1

    TightVNC is pretty good both on a LAN and over long range IP connections. You can tweak it's compression options to get some nice performance. Plus, it has nice scaling to view larger displays on a lower-res host. If you're going from a unix box to a windows box though, i'd recommend using radmin and the built in windows terminal services. It has way better performance than the win32 vnc server.

  4. hmm on Jumping From Computer To Computer · · Score: 1

    this sounds like something i already accomplish daily through the use of ssh, screen, and vnc

  5. Re:Not just monopolies on The Software Monoculture · · Score: 1

    the potential for attacks is there, but the user is given a lot more ability to narrow the range of vulnerabilities.. and if you're knowledgable enough, you don't need to wait for some dork in Redmond to write a patch for said insecure service, you can peep into the issue yourself