Re: hacking Linux and Win

Douglas O'Neal wrote:
The Natural Philosopher wrote:
Gordon wrote:
The Natural Philosopher wrote:


It might be, its just that there are far far less of them.


Umm no. there are about equal numbers of Linux servers as Windows ones
(AFAIK) and it's the WINDOWS ones that get hacked........

Muy Bad..I meant there are less obvious *weaknesses* in Linux than windows..not the least of which has already been mentioned: Root access to a server is a jealously guarded secrete. Root access to windows is routine...

Linux/Unix was conceived from the ground up as a multiuser environment where system administration was an entirely different function, usually carried out by different personnel, to user functionality.
Windows was a basic program loader and IO handler, not a real operating system as such, and never had the concept of multiuser much before NT appeared. Nor anything approaching sane memory management, or concepts of protected areas.,

Its been market driven to provide facile functionality, at the almost complete expense of regular API's.

Unix and VMS were where TCP/IP came from more or less: Its been grafted onto windows, and it never really caught up.

The Internet is a multi user, layered access of TCP/IP networking: Windows a single user program loader with almost no networking native to it, simply entered this arena and never ever caught up.

Its sole remaining strength is its installed user base and the software available that only runs on it.

In every other way its a load of steaming wombat turds.

Have to quibble with you about VMS. The original networking protocol
for VMS was DECnet - a LAN only network. TCP/IP was grafted onto VMS
version 4 (maybe 5 - it's been a while) and the first few
implementations from Digital were very bad. Multinet did quite well
with their third-party TCP/IP stack for VMS because of Digital's lame
offerings.

Again, I was not at my best the last few days. I meant DEC machines and said VMS when I should have said Ultrix.

Since I made a lot pf money selling TCP/IP for VMS I should have spotted that.

.

Relevant Pages

  • Re: Drag it to the trash...
    ... There might be a piece of software utility out there to help in finding and administering these "roaming profiles" for windows. ... A lot of MSDOS programmers entering into the VMS system schools abhorred vms at first, but later it sank in to just how flexible the system was designed to be. ... the so called installer is basically just a script that has been given priviledges to create files and directories, make changes to the system logical tables, and creating new aliases. ... in hardware to do all that. ...
    (comp.sys.mac.advocacy)
  • Re: In the Shallow End
    ... When a document claims how an API is supposed to be used and then gives the user examples that actually work, ... Vague in your instance means you have no context to VMS or UNIX of that era. ... Windows offers lots of this stuff. ... That's why Apple had to dump a whole paradigm to plunge ahead and take the lead. ...
    (comp.sys.mac.advocacy)
  • Re: "Shanghai Stock Exchange" and OpenVMS
    ... Windows was shipping without any "documentation". ... "right out of the box" VMS has no applications at all. ... Guess it depends on the style of manuals you are used ... that I need to use the MS-DOS command window in the first place!)? ...
    (comp.os.vms)
  • Re: "Shanghai Stock Exchange" and OpenVMS
    ... Windows was shipping without any "documentation". ... What about VMS as a back-end? ... have never found the VMS manuals to be all that readable or easy to ... where's the secret documentation for all the MS-DOS commands, ...
    (comp.os.vms)
  • Re: Connecting 2 machines with crossover cable
    ... >Any properly configured installation of Windows will run just fine with ... necessary, and it can make browsing a Windows network unreliable, ... If a network doesn't work with TCP/IP as the only protocol, ... Steve Winograd, MS-MVP (Windows Networking) ...
    (microsoft.public.windowsxp.network_web)