Slashdot Mirror


Why UNIX is better than Windows... By Microsoft

BenBenBen writes "According to a whitepaper found on "a fairly insecure server", UNIX not only is more reliable and easier to maintain than Windows (2000 in this case), it's cheaper too. These shock results are reported on both The Register and (the source) Security Office."

128 of 804 comments (clear)

  1. Is This Necessarily Bad? by carb · · Score: 5, Interesting

    At least it shows Microsoft is keeping some goal in mind in developing Windows - personally I was beginning to wonder ...

    1. Re:Is This Necessarily Bad? by dnoyeb · · Score: 5, Insightful

      Sorry to bust your bubble. Most big corporations have intelligent technicians. However, the message gets lost somewhere between tech and management.

      I am sure managements response to this letter was to start an 'investigation team.' Or send the techs to a '7 habits' seminar or 5S, QS9000, pokeyoke...

      Years later nothing has changed I assure you. They are still using Windows Servers no?

    2. Re:Is This Necessarily Bad? by red_dragon · · Score: 5, Insightful

      Most big corporations have intelligent technicians. However, the message gets lost somewhere between tech and management.

      This, of course, is the basis for the SNAFU principle:

      In the beginning was the plan, and then the specification; And the plan was without form, and the specification was void. And darkness was on the faces of the implementors thereof; And they spake unto their leader, saying: "It is a crock of shit, and smells as of a sewer." And the leader took pity on them, and spoke to the project leader: "It is a crock of excrement, and none may abide the odor thereof." And the project leader spake unto his section head, saying: "It is a container of excrement, and it is very strong, such that none may abide it." The section head then hurried to his department manager, and informed him thus: "It is a vessel of fertilizer, and none may abide its strength." The department manager carried these words to his general manager, and spoke unto him saying: "It containeth that which aideth the growth of plants, and it is very strong." And so it was that the general manager rejoiced and delivered the good news unto the Vice President. "It promoteth growth, and it is very powerful." The Vice President rushed to the President's side, and joyously exclaimed: "This powerful new software product will promote the growth of the company!" And the President looked upon the product, and saw that it was very good.
      --
      In Soviet Russia, Jesus asks: "What Would You Do?"
    3. Re:Is This Necessarily Bad? by red_dragon · · Score: 5, Funny

      Ugh... the Submit button needs to be placed farther away from the Preview button (*covers head with brown paper bag*).

      --
      In Soviet Russia, Jesus asks: "What Would You Do?"
    4. Re:Is This Necessarily Bad? by Pig+Hogger · · Score: 4, Funny
      Most big corporations have intelligent technicians. However, the message gets lost somewhere between tech and management.
      As always. Nothing new there...
    5. Re:Is This Necessarily Bad? by smittyoneeach · · Score: 4, Insightful

      Your observation holds true in a large number of cases.
      But beware.
      The technician/sergeant with the tactical view of things is not the manager/general with the strategic view.
      The Big Picture and the Little Picture will remain in tension indefinitely.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    6. Re:Is This Necessarily Bad? by ryochiji · · Score: 4, Interesting
      > intelligent technicians. However, the message gets lost somewhere between tech and management

      One of the things I like about my current job is that that doesn't happen. Okay, I don't work for a big corporation, but a university bookstore run by the student organization (employing something like 100 students).

      The web-group (which does web design, development, and server administration) reports directly to the bookstore manager (we're the only non-staff employees to do so). The really cool thing is, he trusts our judgement and actually listens to our recommendations. Hell, the other day, we even got him to start using Mozilla!

      But I know my manager's an exception. I don't know what it is with managers. I think it's a lot like politicians...the people who want to achieve power are the last ones to deserve it.

  2. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  3. Re:Huh? by program21 · · Score: 5, Insightful

    Agreed. Now, if they would just be a little more upfront about this sort of thing, I'd feel a little better.
    It seems like most of what we have in this regard is leaked stuff, so internally MS knows, but their public face would never admit to it (IMHO).

    --
    This has been a test. Had this been a real emergency, we would have fled in terror and you would not have been informed.
  4. slashdotted by An+Onimous+Cow+Herd · · Score: 3, Funny

    B******s - i just discovered this artive via another site and tried to read - instantly slashdotted!
    WTF is it runing on - a quad Xeon IIS 2.0/w2k machine with 1 GB memory?

    1. Re:slashdotted by phil+reed · · Score: 4, Funny

      SecurityOffice.net is in Turkey. We've probably slashdotted the entire country's bandwidth.

      --

      ...phil
      "For a list of the ways which technology has failed to improve our quality of life, press 3."
  5. Does republishing these... by MacAndrew · · Score: 5, Insightful

    ...constitute some sort of business tort, like disclosing trade secrets? I'm not trying to give MS lawyers any ideas (like they need them) but I've certainly seen Apple goes nuts over this sort of thing.

    BTW, that it was on a "fairly insecure server" is as much a defense as "his house had cheap locks." :P

    1. Re:Does republishing these... by MacAndrew · · Score: 5, Funny

      I realized after I hit submit that I was thinking by the old rules -- I should have asked whether pilfering documents from their server wasn't punishable by a federal death penalty by now. (I wish that was entirely a joke.)

      Also, isn't the paper just the opinion of the writer, and dismissable by MS like the tobacco industry dismissed the memo by one of its ad exec mapping out marketing cigarettes to children. They would never do such a thing, no.

      That MS has one honest soul in its ranks shouldn't be all that much of a shocker, right? Oops, I guess that was a troll.

    2. Re:Does republishing these... by dpilot · · Score: 4, Interesting

      Or at the very least, a violation of the DMCA?

      --
      The living have better things to do than to continue hating the dead.
    3. Re:Does republishing these... by schlach · · Score: 3, Funny

      MS might sick [sic] their lawyers...

      yuck yuck yuck

      =)

  6. Microsoft.... by dirkdidit · · Score: 5, Funny

    may have insecure server products(and desktop products for that matter) but whatever Security Office was running is nothing more than a smoking pile of silicon and hard drive.

  7. Pardon my scepticism by Anonymous Coward · · Score: 4, Insightful

    But Security Office wants us to believe that they hax0red some random MS Server and just happened to find a detailed analysis on Unix vs Windows? And this analysis happened to say "we should eat our own dog food"? Not one analysis I have ever read had such a ridiculous analogy in it.

    And let's look at this:
    The whitepaper, by MS Windows 2000 Server Product Group member David Brooks, has been posted on the Web by Security Office, which says it discovered the item and numerous other confidential MS documents on a poorly protected server.

    So Security Office is admitting to criminal activity? Sorry, I call hoax.

    1. Re:Pardon my scepticism by NickV · · Score: 5, Informative

      Actually, I have a few friends who interned at MS this summer and apparently the phrase "eat your own dog food" is very very very popular on the campus.

      If anything, including that phrase in the document only makes it seem MORE credible.

    2. Re:Pardon my scepticism by SquadBoy · · Score: 5, Informative

      No it was almost certainly this over the next few days and weeks I have a feeling we will see many more of these kinds of things.

      Also see this.
      So no it is not criminal it was a screw up at MS.

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    3. Re:Pardon my scepticism by schon · · Score: 5, Informative

      Security Office is admitting to criminal activity?

      Not necesarily. They never said they "hacked" it. Read this article at Wired yesterday. Apparently there was a public FTP server at MS that MS employees were using to store sensitive files, because they weren't aware that it was public.

      The funny thing is that MS was notified, took the server down, cleaned it, put it back up, and the same employees started doing it again.

      If the data is in a public server, then it's not "hacking".

    4. Re:Pardon my scepticism by sparkz · · Score: 5, Informative

      It's a common phrase - I've worked at ICL and Sun, and they both use it. It's just another cliche like "singing from the same hymnsheet" and all the other stupid phrases that nobody would use after 5pm.

      --
      Author, Shell Scripting : Expert Re
    5. Re:Pardon my scepticism by ENOENT · · Score: 4, Insightful

      The idea that a company's employees should eat their own dog food doesn't make the dog food any better. It just ensures that the people who find the idea of eating dog food disgusting will work somewhere else.

      By the way, if MS engineers really have to "eat their own dog food", does that mean the the developers for the Paperclip were required to be running the Paperclip while they wrote their code in MS Word? "It looks like you're trying to declare a variable. Would you like to use a handy 12-step wizard to assist you in writing this declaration?" Hopefully, they remembered to turn off auto-correct and "smart" quotes.

      --
      That's "Mr. Soulless Automaton" to you, Bub.
    6. Re:Pardon my scepticism by schon · · Score: 5, Insightful

      So someone was portscanning MS, and just bumped into a public server with secret files on it?

      No, not even a little bit. Please READ THE WIRED ARTICLE before commenting further.

      MS had a PUBLIC, ADVERTISED FTP server, which they used to distribute drivers and documentation, and was referenced in many places on MS's web sites.

      Employees at MS didn't know that the server was used to serve files to the public, and started putting sensitive internal documents (such as this one) on it.

    7. Re:Pardon my scepticism by mosch · · Score: 5, Insightful
      I read the whitepaper, and I definitely don't call hoax. It offers an objective overview of the Hotmail FreeBSD to Windows transition, and doesn't portray either system as being perfect.

      One of the main reasons for the transition to Windows was obviously not only to be able to say 'Hotmail runs Windows', but also to find the places where Windows was weak and to fix them. The paper details a number of places where Windows had trouble (unattended installation, IIS configuration, software distribution, content and code updates, inability to change various parameters without a reboot), but it also mentions that this input was given to the various development teams, to try to make the next version of Windows better.

      Yes, the document explicitly states that there was not a straightforward business case for the transition due to the license fees which would be incurred by customers, and that a number of Microsoft technologies (AD, WLBS) were either useless in that setting, or were not price competitive to the alternatives, but it looks to me like Microsoft was smart enough to use this experience to find and address their shortcomings.

      The whitepaper is real and accurate; the sensationalistic headline on this article, is not.

    8. Re:Pardon my scepticism by stinky+wizzleteats · · Score: 4, Insightful

      Not one analysis I have ever read had such a ridiculous analogy in it.

      This report was not written by a marketing department, it was written by someone familiar with the project (probably an engineer). It is quite common for reports written by technical people for a technical audience to include such "ridiculous" statements due to the lack of wordsmithing acumen on the part of people who actually work for a living, as opposed to those who talk (and write) about it. As someone who spends a great deal of my professional time reading and writing such documents, I indeed use this characteristic to determine how close the material is to "where the goats graze":).

      If I'm writing that document, and I know that everyone reading it will understand "eating one's own dog food", I am not going to take the time to translate that to:

      Further, due to the visibility of Hotmail, there existed a marketing concern with regard to using Microsoft server solutions following the acquisition, in that Microsoft's credibility in selling those solutions depended on actually using them.
    9. Re:Pardon my scepticism by Rich0 · · Score: 4, Funny

      Hopefully, they remembered to turn off auto-correct and "smart" quotes.

      And now we understand the origin of all the MS security holes.

      Clippy: It looks like you're trying to copy an unchecked buffer, would you like help with this feature?...

  8. UNIX better than Windows? by Noryungi · · Score: 3, Funny

    You mean... You mean... That instead of paying for Win2000, I could have installed FreeBSD instead?

    Oh, the humanity!

    (Yes, this was sarcastic!)

    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    1. Re:UNIX better than Windows? by Iamthefallen · · Score: 4, Insightful

      yes, instead of paying for an OS you can demand to get it for free, you can also see the development of said OS grind to a halt cause of lack of finances.

      If you use it, pay for it and support OSS development.

      --
      Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
  9. Slow down cowboy! by Theodore+Logan · · Score: 5, Funny

    There has been one hour and 46 minutes since the last MS critical article was posted. You need to wait at least two hours.

    --

    "If you think education is expensive, try ignorance" - Derek Bok

    1. Re:Slow down cowboy! by w1r3sp33d · · Score: 5, Funny

      it was taco who put up this story not neal, apparently he didn't get that memo... we should ALL send him a copy of the "two hour" memo along with his TSP reports!

  10. Exactly. by rebelcool · · Score: 5, Insightful
    Are slashdotters extremely naive or something? Every company takes a look at the competition and compares it to their own product, distributing memos on whats better about the competition so that they can improve on their own products.

    This isn't news. It's business.

    --

    -

    1. Re:Exactly. by Anarchofascist · · Score: 5, Insightful

      Are slashdotters extremely naive or something? ... This isn't news. It's business.

      That's right. I agree. Companies lying about the capabilities of their products is not news, it's just marketing, just business. It's like political promises, we know everyone does it, so please don't draw attention to it - you're disturbing the happy sleeping consumers.

      Nothing to see here. Please move along. Please raise no confusing or irritating questions, citizen. Consume more products. Let us be thankful we have an occupation to fill. Work hard, increase production, prevent accidents and be happy. Let us be thankful we have commerce. Buy more. Buy more now. Buy. And be happy.

      thx1138

      --
      Once more unto the breach, dear friends, once more, Or close the wall up with our American dead!
    2. Re:Exactly. by grub · · Score: 5, Funny


      WARNING: Your comment "Are slashdotters extremely naive or something" brings common sense into a slashdot discussion. Common sense on slashdot goes against several RFCs.Your karma will be appropriately decimated.

      Thank you,

      The Editors

      --
      Trolling is a art,
    3. Re:Exactly. by sql*kitten · · Score: 3, Interesting

      Are slashdotters extremely naive or something? Every company takes a look at the competition and compares it to their own product, distributing memos on whats better about the competition so that they can improve on their own products.

      Indeed and it goes both ways. For example the open source community have been imitating features from commercial software for years - GIMP and Photoshop, KDE and CDE, ext3 and XFS, Mesa and OpenGL, OpenOffice and MS Office etc, etc. It's hardly fair to criticize a commercial entity for studying BSD. Or are the /. editors just bitter because Microsoft hasn't found anything worth incorporating from Linux?

    4. Re:Exactly. by kubla2000 · · Score: 5, Informative

      Are slashdotters extremely naive or something? Every company takes a look at the competition and compares it to their own product, distributing memos on whats better about the competition so that they can improve on their own products. This isn't news. It's business.

      I was about to mod you down but decided to respond instead.

      Have you read the article? I suspect not. As you are clearly unaware, Microsoft bought Hotmail. At the time they bought it, Hotmail was running on FreeBSD. Much to Microsoft's shame, they couldn't port Hotmail to Windows and keep the service running. Finally, after months and months and months of effort, they did it. But it isn't done well and as this report demonstrates, their own engineers aren't happy with how it's been done.

      This has nothing to do with "looking at the competition". This has everything to do with Microsoft's engineers writing up the reasons for the inadequacy of w2k for a large-scale deployment of this kind. Key phrases from the article:

      - "Although Hotmail uses Microsoft software without license fees, we must consider this project as a model for real customers. Use of WLBS requires Advanced Server, but Server provides all the other features used by Hotmail. Using list prices, the cost comparison for a farm of 3500 servers is: Using WLBS (hence Advanced Server): $15M+ / Using LD and Server: $6M+"
      - "A service may be hung, and rather than take the time to find and fix the problem, it is often more convenient to reboot [a Windows machine]. By contrast, UNIX administrators are conditioned to quickly identify the failing service and simply restart it; they are helped in this by the greater transparency of UNIX and the small number of interdependencies."

      ...and so on. You accuse the /. masses of rabidity but it is, as a point of fact, you who are knee-jerking in defence of the justified laughter and celebration of those of us who have to fight against Microsoft FUD on a daily basis. How nice to have a document to point to now and say, "look, if you don't believe me, believe microsoft. Deploying on a *nix platform is cheaper and better!"

    5. Re:Exactly. by shyster · · Score: 5, Insightful
      - "Although Hotmail uses Microsoft software without license fees, we must consider this project as a model for real customers. Use of WLBS requires Advanced Server, but Server provides all the other features used by Hotmail. Using list prices, the cost comparison for a farm of 3500 servers is: Using WLBS (hence Advanced Server): $15M+ / Using LD and Server: $6M+"

      The costs issues you quote was between Windows 2000 Advanced Server and Windows 2000 Server...nothing about *nix.

      As for the whitepaper, it seems to me it was written by a *nix admin with little Windows server experience (which describes a majority of /. readers as well). I mean, what is this:

      - "A service may be hung, and rather than take the time to find and fix the problem, it is often more convenient to reboot [a Windows machine]. By contrast, UNIX administrators are conditioned to quickly identify the failing service and simply restart it; they are helped in this by the greater transparency of UNIX and the small number of interdependencies."

      If it's more convenient to reboot the machine, then what's the complaint? If it's inconvenient to reboot (which describes 90% of the servers I work on), then find the service and restart it. Hint: Look in the Services console...then right click and Restart. Or, if you prefer the CLI, use net stop/start . For bonus points, you can use the short or long name of the service. What's so difficult about that?

      Oh...and interdependencies? Look in the Services console and click on Dependencies. Most even have a short description so you know what it does. If that's not enough info for you, search Google or Technet. Or get a test server. It's not rocket science, nor is it any more difficult than UNIX.

      The CLI is pretty flexible and allows most maintenance work to be done in it, and when that doesn't work AutoIt (3rd party freeware) can script GUI events (pretty easily I might add). WSH scripts can also automate just about everything you can think of.

      "A fact about UNIX is that it is easy for an administrator to ensure that there are no irrelevant services running. As well as giving the potential for maximizing performance, it is useful to be sure that there are no random TCP/IP or UDP ports open that could be used as a basis for an attack," the paper notes.

      Once again, the Services console could really help this guy get a clue. As for random ports being open, that's one reason we have these things called firewalls...not to mention port scanners and knowledgeable Windows admins.

      "...there are many services that have a complex set of dependencies, and it is never clear which ones are necessary and which can be removed to improve the system's efficiency."

      I think what he meant to say was, "it is never clear TO ME OR MY TEAM which services are necessary". Others do quite well at it.

      Imaging servers should be done by multicasting, effectively negating bandwidth concerns. Windows 2000 rarely needs a reboot (though apps and the like will prompt you to do it even if they don't need it), and you can easily stop and restart a service.

      The author does have points on the Task Scheduler/at command which is a real PITA. There are 3rd party utilities to help with that, but MS does need some work done in that department. Also, the GUI and performance concerns are relevant when discussing a web server, which is why I wish MS would just come out with a web server version of Windows (wasn't that in the pipe a while ago?). And I think Windows 2000 has proven to be pretty stable (as long as it's on quality hardware, of course).

    6. Re:Exactly. by Anonymous Coward · · Score: 3, Insightful

      > If it's more convenient to reboot the machine,
      > then what's the complaint? If it's inconvenient
      > to reboot (which describes 90% of the servers I
      > work on), then find the service and restart it.
      > Hint: Look in the Services console...then right
      > click and Restart. Or, if you prefer the CLI, use
      > net stop/start . For bonus points, you can use
      > the short or long name of the service. What's so
      > difficult about that?

      That doesn't work a surprising number of times. It's very easy to get some services in an unkillable state on Windows 2000. When that happens, rebooting is the only option.

      Also, because of the service interdepency, it's possible to kill a service that causes the desktop to crash. Normally the desktop will respawn or log you out, but not always. When that happens, you lose the task bar, lose icons on the desktop, and have no way of launching any other program or shutting down (sometimes ALT-CTRL-DEL allows you to get to the "shutdown" button though).

      The key to all this is complexity. Windows is an integrated system that tries to stuff as much into the OS as possible. When one thing fails, it can effect any other thing. Also, Windows programs tend to be multitreaded since process creation is so expensive. Programming safe threads is *a lot* more difficult than programming safe processes because of memory space isolation. Processes also allow you to be more sloppy with memory management. If there's a tiny leak in a short running process, it will disappear when the process ends. If there's a tiny leak in a short running thread, it'll survive the thread death. If you respawn that thread several times, it'll be a major leak.

      Unix is layered. If one layer fails, you can go to the lower layer to fix a problem. Also, because Unix tends to use multiprocessing (because process creation is designed to be cheap), processes tend to last longer.

    7. Re:Exactly. by Anonymous+Brave+Guy · · Score: 4, Funny

      Noooooooo! Now you've spawned a whole new generation of bad jokes...

      Karma: xcellent (ostly affcted by oderationdone to yur commens and subequent dcimation)

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    8. Re:Exactly. by Fulcrum+of+Evil · · Score: 4, Interesting

      The costs issues you quote was between Windows 2000 Advanced Server and Windows 2000 Server...nothing about *nix.

      And $15M is nothing to sneeze at. That's probably on par with the hardware cost.

      As for the whitepaper, it seems to me it was written by a *nix admin with little Windows server experience (which describes a majority of /. readers as well).

      I dunno, looks fairly accurate - in windowsland, admins are prone to Retry, Reboot, Reinstall because it's often difficult or impossible to find out what is really happening. Also, keep in mind that this guy and his team probably have access to the devs who wrote this stuff, which is more than you can say for almost everybody else (on windows, anyway)

      Oh...and interdependencies? Look in the Services console and click on Dependencies. Most even have a short description so you know what it does.

      He's probably referring to the compex and non-obvious interactions going on in a windows system. When something breaks, your first clue is when something seemingly unrelated falls over. This is the problem with tight integration.

      Once again, the Services console could really help this guy get a clue.

      Where ddid he ssay that he had no clue? He merely stated that Unix made it easier

      As for random ports being open, that's one reason we have these things called firewalls.

      And you're supposed to use both. It's this thing called defense in depth - you don't want to be compromised by a single failure.

      I think what he meant to say was, "it is never clear TO ME OR MY TEAM which services are necessary". Others do quite well at it.

      Bullshit. given that he is working on a high-profile project within MS, it's probably as clear to him as to anybody. The fact is that another company, when doing a large deployment will have trouble.

      You seem to have a rather large chip on your shoulder. Just because some admin says that some specific things in windows are lacking, or overly confusing does not make him a high school dropout with an MCSE.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    9. Re:Exactly. by geekoid · · Score: 3, Funny

      "Windows 2000 rarely needs a reboot "

      yes, it is nearly 2 nines...

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    10. Re:Exactly. by shyster · · Score: 3, Insightful

      You make the assumption that the UNIX admin is a highly skilled dedicated professional, and that the NT admin is nothing more than a high school dropout with no other tools than a power switch and an NT cd to reinstall with. Hardly realistic in the real world.

  11. Nothing spectacular by comic-not · · Score: 5, Insightful

    Read the paper - pretty reasonable stuff. The only thing that may raise eyebrows is the origin of the paper. Goes to show that Microsoft has some competent people working for them (did anybody doubt that, it's after all the company policy that is rotten) but also a horde of absolutely brilliant PR weasels which can turn black to white when you're not watching.

    --
    Existence usually comes as a surprise (Idem)
  12. Bingo! by Saint+Aardvark · · Score: 5, Interesting
    From the Register article:

    Another strike against Windows is the GUI: "GUI operations are essentially impossible to script. With large numbers of servers, it is impractical to use the GUI to carry out installation tasks or regular maintenance tasks."

    I love Unix. But a huge reason for this unnatural affection is the command line, and the enhancements Unix has made to it (pipes, file descriptors, everything-is-a-file, shell scripting). Even if Microsoft turned around tomorrow and made everything GPL, fixed their security holes and sent chocolates and hookers to Linus and RMS, I'd still prefer Unix for the power of the command line.

    In Windows, the command line almost seems like an optional afterthought. In Unix, it's the other way around. (Disclaimer: I'm partly joking, and much more familiar w/U. than M [as I'm sure everyone can tell].) And I think for admin purposes, that makes Unix the more powerful choice.

    1. Re:Bingo! by kcbrown · · Score: 4, Funny
      Even if Microsoft turned around tomorrow and made everything GPL, fixed their security holes and sent chocolates and hookers to Linus and RMS, I'd still prefer Unix for the power of the command line.

      Yeah, but what if they sent chocolates and hookers to you?

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    2. Re:Bingo! by Havokmon · · Score: 3, Insightful
      And that walks right into the cron stuff:

      For example, TechNet assures us that, "administrators generally find benefit from porting 'cron' jobs to Windows Task Scheduler events. Both Microsoft Interix 2.2 and SFU allow administrators to port 'cron' files to Windows 2000 without any changes in most cases, allowing administrators to gradually transition scheduled events and scripts without impacting operations i.e. at migration scheduled events can still run as 'cron' jobs. After the migration, the 'cron' jobs can be migrated to Windows Task scheduler events. The Windows task scheduler has better integration with event logs."

      Personally, I like consistancy. I use cron, WinCron, and WarpCron. That way, if you want to reschedule something on any OS in the building, you used the same format.

      Easy, Simple, Effective.

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    3. Re:Bingo! by Planesdragon · · Score: 3, Informative

      Au contraire. The whole thing is built around that 16 bit 8-3 filename DOS shell. It's the GUI part that's an "afterthought".

      Was. WAS built around that 16-bit 8.3 quick and dirty operating system.

      It was rebuilt in 1995 to a 32-bit 256 filename DOS replacement, and shortly thereafter in a not-really-DOS-at-all OS called NT.

      And in NT, I think the command line was an afterthought. There's a lot that can be done with it, but not nearly enough.

      If the paper's legit, expect a command-line resurgance for Windows server. Or at least, hope for one.

      (And on a totally different note--I think I'd rather have a "GUI first CLI later" structure than a "CLI first GUI later" strucutre like Linux.)

    4. Re:Bingo! by tshak · · Score: 5, Informative

      As a full time Windows developer, I would hate working in Windows if EVERYTHING wasn't easily scriptable. I'll agree that the original nonsense with the registry and VBScript/COM based WSH was a mess, but almost everything has gone XML and by WIndows.NET server everything will be XML configurable. For example, IIS6 is configured like Apache's httpd.conf (but true XML) and there's just a GUI on top for those who want to waste their time or setup a personal web site really quick. Actually, I know people who work internally at MS and they use Perl all the time for automation scripts. I'm not saying that Windows's scripting better, Unix scripting is still a bit more 'natural' IMHO. The problem with Windows is more that the sysadmins generally don't know how to code.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    5. Re:Bingo! by pointym5 · · Score: 4, Insightful
      This effectively makes the command line as powerful as it is in Unix.


      You have to be joking. Have you ever tried to actually use the "cmd.exe" program? Are you familiar with the capabilities of even the simplest UNIX shell? The "cmd.exe" program seems to me as if it were written by somebody who overheard a brief conversation about what UNIX shells can do. Just about everything about it is inadequate by comparison: quoting syntax, wildcards, variable expansion, conditionals, iteration, redirection, etc. It's useless for all but the most absolutely basic launching of programs.
    6. Re:Bingo! by gorilla · · Score: 3, Informative

      2.0 had pipes and redirection too. At the time when MS was going from 1.0 to 2.0, their stratagy was for Unix to eventually replace DOS. That's why they created Xenix.

    7. Re:Bingo! by Surak · · Score: 4, Interesting

      After a few OS/2 releases, MicroSoft quit and took the code they had from OS/2 and made it into Windows 95.

      Uh, sorry, but this is just plain wrong. Microsoft took the code they had from OS/2 and made it into Windows NT. Actually, more correct would be to say that when Microsoft and IBM were working on OS/2 3.0, they had a parting of ways by ending their Joint Development Agreement. There was a settlement, and in the settlement they split the OS/2 code -- Microsoft got the new stuff, and IBM got the old stuff. Ever wonder why the first release of Windows NT was called '3.1'? Now you know. :)

      Having knowledge of the internals of all three operating systems, I can honestly say it would be *impossible* for Microsoft to have based much of Windows 95 on OS/2 code. Windows 95 is a DOS-based operating system. Its lineage from Windows 3.x is clear. The internals are almost identical, i.e., VMM32.VXD (aka DOS386.EXE) which has always been 32-bit since Windows/386. It's only the GUI and API that changed to 32-bit, the rest of the stuff is nearly identical.

    8. Re:Bingo! by tshak · · Score: 3, Informative

      Active State's Perl for Win32 is the only thing that has made it possible at all. It's gotten easier as time has gone by, not so much because Microsoft has given us better tools (although they have) but because the various modules that allow Perl to interact with the Windows APIs have gotten better.

      Who do you think invested in Active State to get Perl on Windows (and .NET)? Microsoft.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    9. Re:Bingo! by doug363 · · Score: 3, Interesting
      I think this was one of the improvements that the the Hotmail article noted. Firstly, he/she notes:
      It proves to be difficult to configure IIS in a precisely controlled way. The metabase is obscure and poorly documented, and produced too many surprises. Furthermore, a system created using sysprep does not produce a ready-to-run metabase.

      Consequently, it was necessary to construct the metabase by using scripts. The scripts were a mixture of command files that repeatedly call the mdutil utility, and some special-purpose pieces of scripting code (VBScript in this case, although any language that supports COM would work). The scripts are run as part of the mini-setup step that follows construction of the operating system on the target computer.

      Figuring out the metabase structure, which elements needed to be set, and how to suppress the unwanted elements (for example, the trees defining the default and administration site) was the most complex and error-prone part of the entire setup design. Considerable reverse engineering was necessary. Major improvement is needed in the way the metabase is described to users, and the way that administrators can script the commonest tasks.

      In the conclusion, the fact that IIS6 programmers are looking into that issue is stated:
      3) The metabase needs to be ripped out and replaced with something that is much easier for an administrator to see and understand, and be confident that there are no hidden surprises. The IIS6 planners have heard this opinion.
      So that feature may be due to Microsoft's Hotmail experience.
  13. Seriously, by platypus · · Score: 3, Insightful

    this seems to be a quite well written paper (as far as I can see from the Register's summary, the server is /.'ed).

    Everything I read there points out things I don't like on windows, much better than I am capable of. While there exist many papers pointing out these things, they are often to "evangelistic" to be seriously considered for convincing management types.

    I'm eager to get the whole document, it might have its worth even without mentioning the originaters (watch the copyright, though).

  14. Re:Hotmail? by petis · · Score: 5, Funny

    > Wouldn't it be neat if MS put out a fully
    > reliable, configurable, cheap O/S?

    Yeah, they could call it MS/Linux.

  15. Stupid headline by be-fan · · Score: 5, Informative

    I hate Microsoft much as the next guy, but the headline is *way* overwrought. If you actually read the linked article, it's just an honest pro/con comparison. They mention certain advantages of UNIX (text configuration, small size) and certain advantages of Windows (better internationalization, more developer support, better throughput). Entirely realistic and a perfectly fine rationale document. There are some bits I disagree with (eg. Visual Studio being better than the UNIX development tools) but overall, this is just a document written by an engineer weighing the various issues involved in switching from UNIX to Windows.

    --
    A deep unwavering belief is a sure sign you're missing something...
  16. Wait a minute... by RomikQ · · Score: 3, Informative
    Well, the original article is slashdotted, but here are my two cents:

    I tend to view any such "inside" source very suspiciously - the halloween paper about how to bring linux down was fairly believable, but this... Well, the register says:

    ...but concludes that the company ought to set the right example by ensuring that each division "should eat its own dogfood."

    ... Huh? what kind of an official document would claim that their product is crap? This suggests that the paper is of an unofficial status. Well, then, why the hell does it matter. If I worked for microsoft and said things like 'yeah, windows sucks, unix rules' would that make a bit of difference to the company's policy(internal and external)? And the fact that securityfocus "dicovered on a poorly protected server" adds more doubt. Were they hacking into MS servers searching for compromising documents?

    Now, I didnt read the paper itself, so I apologize if this post is missing the point.

    --
    Join the elite! Post at score:2! Ghostwheel is online.
    1. Re:Wait a minute... by jedidiah · · Score: 5, Informative

      You people are reading WAY TOO MUCH into this expression. "We should eat our own dogfood" merely expresses the sentiment that the company should use it's own product. It is in no way an admission of poor quality.

      Real software vendors do actually include such statements in official policy statements.

      Sometimes I wonder if some of you people have made it out of middle school yet.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  17. Re:Looks like a justification post-facto by _ganja_ · · Score: 5, Informative

    Tit. FTFA: "The whitepaper, by MS Windows 2000 Server Product Group member David Brooks"

    --

    A journey of a thousand miles starts with a brutal anal raping at airport security

  18. Difference of approach by Hasie · · Score: 5, Insightful
    Windows is not intended for servers and UNIX is. That's essentially all that is said. Windows is built for the lowest common denominator (hence all the GUIs) and UNIX is built for people that know what they are doing to get the job done quickly and efficiently.


    If Microsoft were to modify their configuration files to be more UNIX like, and offer a decent UNIX-like shell, most of the UNIX advantages would fall away. But this kind of modification would be difficult because of the way Windows is structured. UNIX, on the other hand, doesn't have this problem. It is much easier to build a decent GUI on top of a fundamentally sound architecture than it is to build a fundamentally sound architecture under a good GUI.


    This represents a tremendous opportunity for UNIX. The UNIX world must develop GUIs to rival Windows' and make sure that the performance is equal to that of Windows. Then one can have the best of both worlds. And then nobody can argue that Windows is better.

    1. Re:Difference of approach by jedidiah · · Score: 3, Insightful

      The point of Unix is not the shell. The point of Unix is the kernel, the lack of a registry and the level of transparency when it comes to services/daemons. The shells are only one aspect of the overall point of Unix as an end user interface: CONTROL.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Difference of approach by sql*kitten · · Score: 5, Insightful

      The point of Unix is not the shell. The point of Unix is the kernel, the lack of a registry and the level of transparency when it comes to services/daemons.

      Umm, yeah. Back in the day, the original Unix developers though "Hey! Let's write an operating system without a registry!". NOT. As for transparency, it's all a matter with what you are familiar with. I've just look at a ps -ef on my Octane and there are at least half a dozen daemons running that I'd have to look at the docs to work out what they were - and I've been using Unix for over a decade. If you only knew Unix and you looked at Windows Task Manager, of course you'd be confused, and vice versa.

      Oh, and Windows has a kernel too, btw.

      Unix is better for some things, Windows is better for others. As I've said many times, a skilled engineer has many tools in his toolbox and knows how to use them all, and how to pick the right one for the job at hand.

    3. Re:Difference of approach by Rorschach1 · · Score: 5, Insightful

      UNIX-like configuration files? Yeah, there's nothing I enjoy more than tweaking my sendmail.cf...

      Config files in *nix are often inconsistent and obscure. Not that hairy, undocumented registry keys are any better. How about an open, common XML format for configuration files? That way we can edit them in vi, or build whatever fancy GUI you want.

    4. Re:Difference of approach by pmz · · Score: 3, Insightful

      I've just look at a ps -ef on my Octane and there are at least half a dozen daemons running that I'd have to look at the docs to work out what they were...

      However, on that Octane, a simple `man ` would probably answer most of your questions. Where is the non-Internet-base on-line documentation for everything in the Windows Task Manager.

      One of the reasons for UNIX's transparency is the fact that UNIX is extremely well documented. Many people who are knowledgeable about UNIX are almost entirely self-tought using the documentation bundled with the OS. For example, I got a UNIX sysadmin certification using only the bundled documentation--nothing else.

    5. Re:Difference of approach by dohcvtec · · Score: 3, Informative

      Config files in *nix are often inconsistent and obscure
      The article specifically talks about FreeBSD, so maybe you should take a look at FreeBSD's configuration files. What could be easier than /etc/defaults/rc.conf (unless you can't read)? To wit: sshd_enable=YES. OMG that was soooo inconsistent and obscure?!?! Or how about: hostname="foo.bar.com" WTF? Where do I press OK? What is this, text? Wow, who uses text anymore... Seriously, you have a point about sendmail.cf, but most config files aren't so bad, and even then the defaults are usually what you need, and they're already there, so all that's needed is to turn daemons on or off.

      --
      -- Never hit a man with glasses. Hit him with a baseball bat.
    6. Re:Difference of approach by IamTheRealMike · · Score: 3, Interesting
      Config files in *nix are often inconsistent and obscure. Not that hairy, undocumented registry keys are any better.

      Hmm, about about clean, documented registry keys? That's the approach GConf takes, it has a lot of advantages over raw text. Too bad all the keys aren't documented at the moment, but that's bugs with individual apps rather than a design flaw.

  19. Re:Huh? by Saint+Aardvark · · Score: 5, Interesting
    Exactly -- my first impression was "They really are smart, aren't they?"

    [#include unixfan_disclaimer], but honestly: look at the advantages of Unix over Windows in so many situations. I'd always kind of wondered if MS was ignoring those problems/advantages for marketing purposes, or if they Just Didn't Get It. Looks like the former, which is reassuring.

  20. Obligitory Simpsons Quote by Tassach · · Score: 3, Funny


    Ha, Ha
    </simpsons>

    Looks like once again, M$ gets busted for lying through it's teeth. Of course, that's what all good marketing is. Not that any of this comes as a suprise for anyone who's administered both Windows and *nix boxen.

    --
    Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
  21. Why doesn't Microsoft... by dubious9 · · Score: 5, Interesting

    Spend money to fix problems with its software? If they know its poorly coded, why don't they launch an entire other branch dedicated to fixing bugs/product maintenance? It's not like they don't have the money. Throw a billion dollars at .net and windows and see if you can make it better. Hell throw five. They'll still have enough money to run the company for a year without any other income.

    As much as we'd all like to think, they people over at Microsoft are not idiots. They have enough money to hire the best and the brightest. They do have some quality products (i.e. those whose securities problems are not much of a problem like games, and i personally like their Intellimouse Optical.).

    Can anybody tell me why so many smart people won't see the light of day and dedicate big resources to overcome their biggest drawback?

    --
    Why, o why must the sky fall when I've learned to fly?
    1. Re:Why doesn't Microsoft... by jedidiah · · Score: 5, Insightful

      They don't have to.

      They have been immune from market pressures since at least 1987.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Why doesn't Microsoft... by Sloppy · · Score: 4, Interesting
      Why should they improve quality? Would doing this increase their revenue? If anything, I think it might decrease their revenue. Combine that with the increased expense, and you've got a publicly-traded company intentionally making less profit than it could -- I smell lawsuit!

      I bet almost everyone who has tried to help Windows users over the last few years has heard actual people (not actors auditioning for the part of a moron on a sitcom) say things like this in real life:

      • "Darn it, my Windows 98 system is crashing too often. I need to upgrade to that new one, XP."
      • "Darn it, Excel95 locked up the whole machine when I tried to load that document. I guess I need to buy the latest version."
      • "Darn, I got a virus again."
      • "This computer is slow and unreliable, but I'm going to buy a new Dell soon."
      If your customers said things like that, what would you do? Ok, now pretend that you are an evil son of a bitch, and answer that question again.
      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  22. This shouldnt be surprising by quantax · · Score: 5, Insightful

    I do not know what people are acting all surprised. What MS says and what MS knows are two very seperate things. Why do you think they say Linux is a competitor to be watched? Yea, they say 'MS software is better for xyz reasons, yatta yatta' but you better be damn sure that privately they are analyzing their competition inside and out. The first way to get raped by your competition is to ignore it. The second is to assume that you are automatically better than the competition, product quality wise. If a company is dishonest in its internal evaluations of its products against their competition, they will merely alienate their customers even more due to poor design decisions. Remember, MS has a shitload of investors, so going out publicly saying 'our product is subpar to unix' would result in their stocks playing a rollercoaster game. Never mistake self-honesty with PR.

    --
    "What can a thoughtful man hope for mankind on Earth, given the experience of the past million years? Nothing." -Bokonon
  23. Re:Looks like a justification post-facto by platypus · · Score: 3, Insightful

    Hmm, this explanation doesn't fit well with what I read at the Reg:

    The whitepaper, by MS Windows 2000 Server Product Group member David Brooks,

    Whereas in Win2K: "Some parameters that control the system's [...]

    Cleary, the original hotmail guys wouldn't have thought about W2k, which was non-existant at that time.

    The team was unable to reduce the size of the image below 900MB

    Dito, I doubt any MS operating system's image at that time couldn't be reduced to less than 900MB.

    They also mention Advanced Server, that "at" is deprecated, Interix 2.2 and so on.

    No, I doubt your are right.

  24. I would accuse Microsoft of a lot of things... by craenor · · Score: 3, Insightful

    ...but being unrealistic isn't one of them. They know what their products are like and they know the golden rule, "You don't have to have the best product to win the product wars."

    Beta vs. VHS...Zip drives vs. Jazz drives...etc, etc.

  25. The goal in mind being UNIX? by Pac · · Score: 5, Insightful

    Why bother then? If Apple, with far less resources of any kind whatsoever, managed to plug a decent user interface on the top of a free UNIX-like layer, Microsoft could certainly do the same, only better and faster.

    1. Re:The goal in mind being UNIX? by agallagh42 · · Score: 3, Funny

      Actually, AMG doesn't build faster processors, they build faster Mercedes Benzes. AMD builds faster processors.

      --
      Carpe Cerevisi - Seize the Beer
    2. Re:The goal in mind being UNIX? by TheWanderingHermit · · Score: 5, Insightful

      This reminds me of somehting a well known programmer from the days when the Apple ][e was still big said. (I'm sorry I can't remember who it was.) I can't remember it exactly, but he said he had no problem with M$'s success, they had earned it. His complaint was that they had earned it selling 3rd rate software.

      To restate the obvious -- M$ can create a clone of anything quickly, the point is this company has NEVER come out with ANYTHING original, only clones of competitor's programs. The difference is M$ puts out something that looks competitive, with loads of holes in it, but offers it for free, or integrates it with Windows, and stops improving it once they've wiped out the competition.

    3. Re:The goal in mind being UNIX? by spencerogden · · Score: 5, Insightful

      Sorry, but Office does not fit this mold. Word was there from the CLI beginning and along with Excel the suite has stedily progressed. I am always amazed at what I can do in these programs, they just work. The only thing close is OpenOffice and even that is not there. I know other programs are great for writing letters and such, but when you need to do a little layout etc. the lack of features starts to show.

      Now I dislike all of the automatic, wizard clippy crap as much as the next person, but the core of the programs are very powerful.

    4. Re:The goal in mind being UNIX? by Squareball · · Score: 4, Funny

      So that new benz I just bought ISN'T going to run UT2003 faster? DAMN IT!!!!!!!!

    5. Re:The goal in mind being UNIX? by El · · Score: 3, Informative

      Sorry to disagree with you, but if you can get work done with Office, which tends to hang without saving your work when inserting graphics, then you should really be able to get a lot more done with FrontPage, which is much cleaner and easier to understand, more reliable, and has productivity features such as macros that Office doesn't. Unfortunately, their marketing sucks. Oh, and by the way, Word was obviously a clone of WordPerfect, just as Excel was obviously a clone of Lotus123 which was a clone of VisiCalc. Original programs, indeed!

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    6. Re:The goal in mind being UNIX? by Hammer · · Score: 5, Interesting

      Office is originally a clone...
      Word is a ripoff from WordPerfect
      Excel a copy of 1-2-3
      (and those copies of Visi-Calc and Visi-Text from early 80-s or was it late 70-s)

      Yes Word and Excel has a lot of "features" like the ability to run viru^H^H^H^Hprograms and so on. But OOo is just as good for me (at a much nicer price tag)

    7. Re:The goal in mind being UNIX? by mini+me · · Score: 4, Funny

      No, but it will bring GTA3 to a whole new level.

    8. Re:The goal in mind being UNIX? by tmark · · Score: 3, Insightful

      The irony of this Jobs quote is that without MS - i.e., without Word, Excel, and IE, Apple might be long dead, or at least even more effectively marginalized than it is now.

    9. Re:The goal in mind being UNIX? by tmark · · Score: 5, Insightful

      Word is a ripoff from WordPerfect ??? This is no more valid than a claim that WordPerfect is a ripoff of WordStar. Word is, and always has been, substantially different from WordPerfect in ways that people (myself included) chose to use Word in the old days, even though WordPerfect was by far the dominant standard.

      It was SO far from being a clone that the poster's claim is ludicrous. Anyone vaguely familiar with the two systems, their key bindings and document models would know this. They worked COMPLETELY differently.

    10. Re:The goal in mind being UNIX? by (void*) · · Score: 3, Informative

      Actually, Word is a clone of Lotus AmiPro.

    11. Re:The goal in mind being UNIX? by RAMMS+EIN · · Score: 4, Insightful

      I disagree. The problem is exactly that they _don't_ clone. They see what somebody else does, and then do it their own way. When they made DOS, they looked at Unix for an example. They didn't clone it; DOS is single-user, single-tasking, with no security or proper separation of tasks (why, if it's single-tasking?), in strong opposition to Unix (even in it's earliest incarnations, I think, but these were made before I was born ;-) ).

      When they started to do networking, there certainly were networking protocols. I think there even was TCP/IP, but MicroSoft cam up with NetBeui, which is arguably lacking in features, and certainly incompatible.

      Office software. MS Word has long been competing with WordPerfect (now owned by Corel?), and all the time it was lacking and incompatible. With the advent of Windos 95, _MS_ Word had better integration with _MS_ Windows, and computers started to ship with both preinstalled. It even gets to the point where people buy a computer with Windows XP and assume that it has Office XP installed. Talk about manipulation. (Similar arguments for Lotus 1-2-3 vs. Excel, yada yada.)

      Remote administration. RDP is one of the new killer features of Windows XP. Unix has had X since, what? 1985? And where is SSH or even telnet on Windows? True, there's a telnet _client_, but MicroSoft is still behing on the rest of the world here (which isn't so bad for desktop systems, but it certainly is for servers).

      Internet software. Rather than going with the standards others are trying to establish, MicroSoft rolls its own. Result? ActiveX vulnerabilities, incompatible `Java' runtimes, VBScript exploits, automatic execution of virii by the mail client, ... Apache? Nah. We'll give people IIS (It Isn't Secure) just so the script kiddies can demonstrate the ability of Windows to do distributed computing in the form of DDoS attacks.

      Many of the problems with MicroSoft's software would not have happened if they had stuck with the true and tested designed of others, or hadn't written their own software to do what other software already did better (which I wouldn't call cloning because M$'s products usually are highly incompatible). Morale? Don't reinvent the wheel, Keep It Simple, Stupid!

      ---
      Our country has plenty of good five-cent cigars, but the trouble is
      they charge fifteen cents for them.

      --
      Please correct me if I got my facts wrong.
    12. Re:The goal in mind being UNIX? by Fulcrum+of+Evil · · Score: 3, Informative

      When they made DOS, they looked at Unix for an example.

      They didn't make DOS, they bought it for something like $50k.

      When they started to do networking, [...] MicroSoft cam up with NetBeui.

      I think that one is IBM's fault.

      And where is SSH or even telnet on Windows? True, there's a telnet _client_, but MicroSoft is still behing on the rest of the world here (which isn't so bad for desktop systems, but it certainly is for servers).

      You can get an ssh client several places, and I'm fairly certain that win2k ships with a telnet server, though I don't know how useful that is, since windows software is so gui oriented. A better remoting solution is to use VNC or to get XP pro and use their single-client term server.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    13. Re:The goal in mind being UNIX? by 5KVGhost · · Score: 4, Informative

      Office is originally a clone...
      Word is a ripoff from WordPerfect


      Only if you consider WordPerfect to be a "ripoff" of Wordstar. Or EasyWriter. Or Electric Pencil. Or one of the other dedicated word processing systems that were around for a good decade before WordPerfect was published.

      Excel a copy of 1-2-3

      Excel was more of an evolution of MS Multiplan, created for the original Mac back in 1985. It had a graphical interface from the start. It followed the same general conventions as 1-2-3, but it would have been silly not to.

      (and those copies of Visi-Calc and Visi-Text from early 80-s or was it late 70-s)

      VisiCalc was introduced in 1979 . The other Visi-On suite applications did not achieve the same level of success.

      Fighting over who did what first is pretty pointless. Software inspires others software. Look at all the open source projects that exist only to ape their existing commercial counterparts.

    14. Re:The goal in mind being UNIX? by Charm · · Score: 3, Funny

      It isn't plagiarism just because you re-order your phrases.

      --
      -- RTFM:Slackware::Beer:Saturday
  26. more developer support? by phorm · · Score: 4, Interesting

    I might be missing this one, as I don't see it in the article, but...
    Since when has the windows community had more developer support? MSDN is a bloody nightmare... in 'nix I've had very little problems tracking down assistance, howtos, and code samples.

    1. Re:more developer support? by SirSlud · · Score: 3, Informative

      Allow me to preface this by saying that I feel this way *regardless* of which platform you are developing for:

      Anybody who doesn't RTFM _before_ asking is asking for trouble. Doesn't matter what platform they're developing for. If you have time to code, you have the time to read the documentation, or a book, or ... otherwise you're just wasting people's time. Of course, if you actually *did* develop for *nix, you'd know that there are tons of good mailing lists out there with kind curteous professionals who dont mind answering your questions if they havn't already been answered in the manual.

      BUT, in the windows world, there are way more casual programmers who will help other casual programmers be lazy, in order to learn the bare minimum of what must be done to solve a problem. So people are generally more patient in the Windows world because there are less people who would apply the 'what should a professional do' metric against developers seeking help.

      That doesn't make *nix developers elitist. Honest to god mechanics dont wanna stand around all day and explain how your engine works. If you're interested enough, you have time to learn the basics yourself .. once you're up to speed and can formulate intelligent questions that havn't been answered a million times before, that mechanic will be much more receptive towards helping you learn new things. Its a pretty natural dynamic, and one thats been around in pretty much any profession or industry.

      --
      "Old man yells at systemd"
    2. Re:more developer support? by gorilla · · Score: 3, Insightful
      Anybody who doesn't RTFM _before_ asking is asking for trouble.

      No arguments here, however in my experience the FM is much easier to R in the Unix world than in the Microsoft world. Part of this is the differences in the API. The Unix API was very small and well designed, and while it's had some weird things added, it's still fairly compact. The Windows API tends to have a lot of different ways of doing basically the same thing. For example, under Unix, you have read() which will read a file. Under Windows, you have read() which is a ANSI C way of reading a file. You also have ReadFile(), ReadFileScatter(), and ReadFileEx, which are 3 different windows specific APIs. That means that if I want to do the same task under Unix and under Windows, I've got to read more documentation under Windows.

    3. Re:more developer support? by be-fan · · Score: 3, Informative

      Visual C++ is a pile of stinking shit. A C++ compiler cannot call itself a C++ compiler if it only has half-ass support for a nearly 5 year old standard! VC++ 7 is getting better, and the 7.1 beta is supposed to be quite good, but GCC was there a good while before, and GCC's C++ support is *extremely* robust. Visual Studio has a good code editor (though, the auto-indent tries to force you to layout your code in weird ways, like no indent after public: declaration) and a very good class browser, but other than that, it's not great at all. GDB is perfectly comparable to Visual C++'s debugger, and the remote debugging feature has much less overhead on the target (good for developing embedded code) and an open protocol. Visual C++'s make system uses binary files (ugh) and can be quite delicate and easy to fool (at least in VC++ 6.x). Visual C++ is just peachy for writing Windows/MFC/RAD code, but for anything else, the numerous UNIX tools are far better.

      PS> Don't even get me started on Visual Source Safe...

      --
      A deep unwavering belief is a sure sign you're missing something...
  27. full article abstract by job0 · · Score: 4, Informative

    lamenes filter won't let me post the whole document so I will have to break it up

    Abstract

    This white paper discusses the approach used to convert the Hotmail web
    server farm from UNIX to Windows 2000, and the reasons the features and
    techniques were chosen. It will focus primarily on the planners,
    developers, and system administrators. The purpose of the paper is to
    provide insight for similar deployments using Windows 2000. We will
    discuss the techniques from the viewpoint of human engineering as well
    as software engineering.

    Early results from the conversion, which was limited to the front-end
    web servers, are:

    Windows 2000 provides much better throughput than UNIX.

    Windows 2000 provides slightly better performance than UNIX.

    There is potential, not yet realized, for stability of
    individual systems to be equal to that of UNIX. The load-balancing
    technology ensures that the user experience of the service is that
    stability is as good as it was before the conversion.

    As this paper will show, while the core features of Windows
    2000 are able to run the service, its administrative model is not well
    suited to the conversion.

    The observations related here are derived from experience gained at a
    single site. More work would be needed to establish whether they are
    representative.

  28. MS employee vs MS corporation by Hays · · Score: 5, Insightful

    You have to remember that MS employees are real human beings. They aren't idiots for the most part. This guy was being very candid about the shortfalls of a windows server, perhaps with hopes of seeing it improved it in the future. It's the higher ups in the corporate ladder and the marketers that candy-coat all things windows and belittle all things *nix.

    Ironically, many of those (perfectly valid) reasons that *nix can make a better server are the same reasons I don't like it on my desktop. Text configuration is a blessing for server farms but a nightmare for newbies with a fresh install.

  29. Slashdotted by bckspc · · Score: 5, Informative
  30. Re:Hotmail? by syd02 · · Score: 5, Interesting

    Hotmail still runs FreeBSD...behind the Windows 2000 front-end facade.

    Go to http://uptime.netcraft.com/ and type in one of the IP addresses that you find in the HTML source at Hotmail's login page.

  31. Drivers by labratuk · · Score: 5, Insightful

    Having read their section on Windows' Strengths, there are several bits that I disagree with, but really the hardware issue is the most annoying.

    Better hardware detection. Setting up UNIX on a new PC is difficult, requiring a more intimate knowledge of how the hardware is built. That's an up-front cost; given the existence of multiple identically configured systems, cloning an established system doesn't present the same problems.

    This I don't agree with. Granted that you need a little bit more knowledge to get hardware working, if you do know what you're doing (and this paper is aimed at people who do, or at least should know what they're doing), it is far more reliable. If something goes wrong, there is a reason it went wrong, and a way to fix it. In windows, even the biggest guru finds the hardware detection system to be black magic to say the least. At worst, it can be completely random!

    Plus cloning a Linux is very easy and reliable, because as a general rule there are fewer driver dependencies. Think about a Slackware setup booting into console only server mode. How many hardware/module dependencies are there? All I can think of is the Ethernet card. Other than that, the image is completely transferrable.

    --
    Malike Bamiyi wanted my assistance.
  32. mirror by Anonymous Coward · · Score: 4, Informative
  33. Re:Huh? by capt.Hij · · Score: 5, Interesting
    How many years old is Windows?

    The fact that you can ask that question is a key issue. MS has made a decision to be backwards compatible. This represents a huge liability. It isn't such a big deal for BSD since upgrading is just a matter of typing "make." What MS is doing makes a heck of a lot more sense to me than what Appled has done. (Oh great, here goes my karma, but now I've started...) Apple built a culture of bravado about how advanced its OS (interface really) is. Then when they hit a wall they decided to just change the processor and the instruction set. They then did it again when going to OSx.

    MS on the other hand is trying to evolve rather than start over. If they are willing to admit that there are flaws then they can make necessary changes. That is the reason that you can ask how old Windows is.

    Personally, I wished that they had tossed out a lot of bad baggage a long time ago. I especially liked the last paragraph from the Guardian:
    It is terrifying to contemplate the efficiency bonus MS would have enjoyed if it had only been willing to base its entire corporate operations on UNIX instead of eating its own dog food. The software monopolist might today be in the bizarre position of being the world's only consumer of unices.

  34. Re:slashdotted - bandwidth by Insightfill · · Score: 5, Funny

    Agreed - most likely, it's just some guy with a 28K modem who's got a dedicated phone line. Sometimes, his mom picks up the wrong line and the whole site goes down.

  35. Re:Wow, you guys have no shame by marauder404 · · Score: 4, Insightful

    I totally agree ... The Register is no more a credible source than Slashdot is. It is entertainment, though.

  36. Re:Wow, you guys have no shame by dbarclay10 · · Score: 4, Interesting
    I read "The Register" like I read "The Weekly World News." It's a tabloid in every sense.

    See, that's the problem.

    In almost every instance, The Register has been right. Yeah, it may still be irresponsible journalism - but as individuals, and as a company, these guys know what the hell they're doing. They check their stuff, even if it won't hold up to normal journalistic integrity checks.

    It's kind of like the difference between talking to a judge and talking to a jury. When you're talking to a jury, you can still be telling the truth, but you don't need to present *nearly* so much hard evidence as you need were you trying to convince a judge.

    Not that you couldn't present evidence everybody on the planet considers "hard", but courtrooms have their own standards (think about all the cases that were overturned because some extremely incriminating piece of evidence was thrown out of court on some technicality).

    --

    Barclay family motto:
    Aut agere aut mori.
    (Either action or death.)
  37. A bit about David Brooks by mj01nir · · Score: 5, Informative

    I was curious about the author, so I started Googling a bit. Many of his newsgroup posts are in relation to Microsoft's UNIX products (like Outlook Express for HP-UX and IE for Solaris) and his .sig is ususally "Test Lead, Microsoft Corp." Here he mentions being an ex-employee of OSF and The Open Group.

    Enquiring minds and all that.

    --
    the no .sig .sig
  38. The Truth? You can't handle the truth by Drestin · · Score: 3, Interesting
    Well, this IS Slashdot so the rush to accept ANYTHING even remotely antiMS is to be expected but I'm suprised that so many haven't spent even a few minutes to think this through.

    First, is it a real document downloaded while an FTP server had some unsecured directories exposed recently? Possibly. So what? Does this mean that this is official MS scripture? Do you mean that if we review every file on your hard drive we won't find something that a) wasn't written by you, b) you probably don't want us to see, c) doesn't represent your current thoughts.

    Ahh the C option... perhaps this was really written by someone who happens to be an MS employee. Perhaps this guy was just given the job; take Hotmail and move it from BSD to Windows and this guy is like many who might say; but it works as it is. Lets not break it to fix it - lets leave it as it is so I'll write up every reason I can think of not to do this!

    Has everyone missed/forgotten the MS papers describing the reasons why and exactly how Hotmail WAS moved from BSD to Windows 2000?

    In this document you'll find how untrue so much of what was written in the stolen document. No scripting support in windows 2000 because it also includes a GUI? Are you fucking stupid or what? There is complete scripting control in windows 2000, always has been. You can control every part of windows 2000 networking and services and disks and users and security through scripting. Sure, you can use the GUI too. Does the fact that Linux can run a GUI mean that suddenly it's scripting goes away?

    In the conversion to Hotmail they employeed scipts and automation tools builtin to windows. They moved because Windows 2000 was faster and more efficient. It is obviously stable as any honest person running W2K/XP can tell you.

    I understand there is a need to attack MS at every step around here. I understand the desire to believe every antiMS piece ever submitted. But sometimes even the more ignorant *nix admin has to eventually read the facts and find that NO OS is perfect. That W2K is not utterly and totally flawed and that it actually is a real competitor for other Server OSes. Once you accept this you can drop the zealous approach and do things in a logic, calm and professional manner. If is really better - prove it to us with grown up responses and facts - not running around waving a copy of The Enquirer which tells us Michael Jackson and Bill Clinton were seperated at birth by aliens somewhere near Roswell.

    1. Re:The Truth? You can't handle the truth by sql*kitten · · Score: 5, Insightful

      If W2000 is so fast and efficient why can't I run it on a P133 with 24MB of RAM like I can Linux?

      If you want to be taken seriously, you have to compare like with like. For example, compare Windows 2000's hardware requirements to that of the complete KDE 2.

      Because you can run MS-DOS on a 286 but you can't run even the earliest Linux on a 286, does that make MS-DOS a better operating system? No, of course not.

    2. Re:The Truth? You can't handle the truth by nagora · · Score: 5, Insightful
      If you want to be taken seriously, you have to compare like with like. For example, compare Windows 2000's hardware requirements to that of the complete KDE 2.

      I don't use KDE on any of my machines, I hate it precisely because it repeats Window's bloat and design errors. I use WindowMaker on even my fastest machines and it will run fine on the P133 as well. Windows 2000 does not give you the choice which is why, if you want to be taken seriously, you would avoid using it.

      Because you can run MS-DOS on a 286 but you can't run even the earliest Linux on a 286, does that make MS-DOS a better operating system? No, of course not.

      But it might make it faster and more efficient (until you want a lot of memory or multi tasking etc), which was the original assertion. "Better" is a broader topic but, given two 32Bit, multi tasking OSes, faster and more efficent becomes a lot closer to meaning "better" than it does when comparing a 16bit single-tasker and a 32bit multi-tasker. Then there's security to consider; DOS and Windows are not secure systems.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    3. Re:The Truth? You can't handle the truth by thelexx · · Score: 5, Insightful

      Apparently you can't handle it either, or do more than skim TFA.

      You:
      "No scripting support in windows 2000 because it also includes a GUI? Are you fucking stupid or what?"

      From the article:
      "There are, indeed, many non-GUI administrative programs provided in the core Windows 2000 product and in the Resource Kit. The problem is that
      the collection is somewhat arbitrary, incoherent and inconsistent. Programs seem to have been written to fill an immediate need and there
      is stylistic inconsistency and poor feature coverage."

      You:
      "They moved because Windows 2000 was faster and more efficient."

      Article:
      "The conversion of the Hotmail web servers to Windows is an ongoing
      project with several rationales. The team was hoping for better
      utilization of the existing hardware resources. The superior development
      and internationalization tools are important. A Microsoft property
      should eat its own dogfood. Finally, we wished to use the conversion
      experience as a model for other UNIX conversions that we hope to carry
      out in the future."

      You:
      "It is obviously stable as any honest person running W2K/XP can tell you."

      Article:
      "2) Reputation for stability. Both the UNIX kernel, and the design
      techniques it encourages, are renowned for stability. A system of
      several thousand servers must run reliably and without intervention to
      restart failed systems. For Windows 2000, we must first prove the
      stability in the same environment, and we must then convince the rest of
      the world."

      If it's so obvious, to 'any honest person', why do they have to try and convince anyone at all?

      You:
      "That W2K is not utterly and totally flawed and that it actually is a real competitor for other Server OSes. Once you accept this you can drop the zealous approach and do things in a logic, calm and professional manner."

      Getting people who have been repeatedly burned to accept this is a Microsoft problem, not mine. In the meantime, I will continue to use superior software in a quite logical, calm and professional manner.

      --
      "Gold still represents the ultimate form of payment in the world." - Alan Greenspan, 1999
  39. class TechEvaluate public: vs private: by 4of12 · · Score: 5, Insightful

    Microsoft's "public" interface is constantly tearing at the bounds of credibility. Witness Balmer's talk about how they didn't adequately sell their customers on the benefits of Software Assurance:)

    Internally, though, this shows that Microsoft is quite rational and realistic. As a company, they will survive and prosper a lot longer on that course than if too much of the internal management started to actually believe what is destined for external public consumption in the marketplace.

    Let's all learn the good lesson from Microsoft here.

    It should be obvious that if you're in a business that relies on evaluation of information technology that you should rely only very loosely upon what is presented to you publicly.

    Second, keep your internal evaluations

    • private,
    • rational, and
    • closely-based on reality.

    Shoot, I knew years ago that BSD was a cheap solid workhorse after learning about ftp.cdrom.com

    --
    "Provided by the management for your protection."
  40. Re:GIVE ME A BREAK!! by forsetti · · Score: 5, Informative

    Three clicks in Computer Management won't shut down all services, only user-administerable services.

    There are a number of services (RPC, NetBIOS, etc) that are VERY difficult to shutdown, and are only useful if you run in a domain or workgroup.

    If I have to run IIS on a standalone Windows 2000 box, I DO NOT want these extraneous services running. I want a box that only has ports 80,443, /maybe/ some file access port for ftp or sftp to upload files. That's it -- none of those silly TCP/UDP135-139 (generalization) ports!

    --
    10b||~10b -- aah, what a question!
  41. Death penalty, I wish!... by coyote-san · · Score: 5, Funny

    Nope, not the death penalty.

    A special clause on page 394 of the enacting legislation says that anyone convicted of publishing Microsoft's dirty laundy is enjoined from using any other operating system for life. It's Microsoft only, baby!

    Repeat offenders are enjoined from using any operating system other than Windows ME.

    And for the hard-core cases... they bring out BOB.

    --
    For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
    1. Re:Death penalty, I wish!... by Zordak · · Score: 3, Funny
      What are you afraid of? A fate worse than death?

      No, just death. Isn't that enough?

      ...

      Apparently it isn't.

      --

      Today's Sesame Street was brought to you by the number e.
  42. Re:Huh? by MrResistor · · Score: 5, Interesting

    You make some good points, but here's my response:

    How many years old is UNIX?

    I'm unaware of any significant functional breaks during the evolution of UNIX. As far as I can tell there haven't been any, or if there has been it was on the order of the transition from DOS to NT; minor breaks here and there, but on the whole, compatability is maintained.

    --
    Under capitalism man exploits man. Under communism it's the other way around.
  43. Am I the only one... by Zonekeeper · · Score: 3, Funny

    that upon opening http://www.microsoft.com/servers , read "Build and Deploy", as "Build and Destroy"?

  44. Not a question of which came first... by Inominate · · Score: 3, Insightful

    The windows command line seems to be built as an emergency backup tool, for when it can't be done in a GUI for some reason. It is in no way intended for the system to be USED from the command line.

    Modern unix shells however, are designed to be comfortable, and easy to use. (Easy as in, the lack of the amount of work required from a dos-style shell.)

  45. Re:Hotmail? by dohcvtec · · Score: 3, Interesting

    We probably don't need a whitepaper to tell us what we already knew
    No, but this paper shows us that Microsoft already knew what we knew: that FreeBSD is much better in terms of reliability, configuration, and administration. I'd read the "marketingized" version of the (attempted, partially successful) Hotmail conversion before, but this document sheds light on what really happened and why.

    --
    -- Never hit a man with glasses. Hit him with a baseball bat.
  46. Re:Huh? by El · · Score: 5, Insightful

    Where have you been? There was the BSD vs. AT&T Unix compatibility issues, the OSF compatibility issues, and in Linux the switch to glibc5 was a major backwards compatibility breaker. Of course, these problems pale in comparison to the incompatibility problems caused by some new releases of windows, but Unix and Linux in particular have never been shy about breaking backwards compatibility in order to improve functionality.

    --

    "Freedom means freedom for everybody" -- Dick Cheney

  47. Like it matters... by hendridm · · Score: 3, Funny

    I am reminded of a time during my short term at Best Buy where I was demoing an eMachine with Windows XP for a customer. All of a sudden, the screen froze and there was no response from keyboard or mouse. Embarrassed, I quickly made up some excuse and went to Start -> "Turn off computer" to restart the machine.

    The next words out of the customer's mouth were, "Oooh, I like how it fades."

    Apparently, this customer was an ex-Millenium user who looked past computer lockups as commonplace, or perhaps they just really dig user interfaces and could care less about the fact that a new display computer is having problems locking up during a simple mouse meneuver.

  48. Here's another wonderful giggle... by talks_to_birds · · Score: 3, Interesting
    ...from a Micro$oft "server"..

    Regarding the much touted recent Windows 2000 Common Criteria Certification, see: Chapter 3 - Secure Configuration for this gem:

    "Installation of applications conforming to Windows Installer-based package requirements will have difficulty installing from a CD-ROM on a computer running a Windows 2000 operating system in the Evaluated Configuration.

    "The reason is that the Windows Installer service is not a service that was evaluated and is therefore disabled in the Evaluated Configuration of Windows 2000. Additionally, the AllocateCDRoms Registry value that is set in the Evaluated Configuration will not allow Windows Installer to open a .Cap file directly from a CD-ROM.

    "Therefore, to install an application conforming to Windows Installer-based package requirements, the Windows Installer service must be temporarily enabled and the "MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateCDRoms" Registry value must be temporarily set to 0 (this can be accomplished through the Local Security Policy interface)."

    So, in order to install any apps on your "secure" Win 2K box, you have to hack the registry and disable the protections that the very Windows 2000 Common Criteria Certification itself were set up to require!

    And of course, the "secure" configuration has to have the floppy drive removed, or made inaccessible!

    But hey! who's gonna install Office 2K from floppies, anyway?

    What are these people smoking?

    t_t_b

    --
    I'm on PJ's "enemies" list! Are you?
  49. Very interesting reading by m0i · · Score: 3, Interesting

    If what's inside is to be taken as facts, it's interesting to see that in a large scale environment:
    -IIS management is not easy (due to the metabase, and reloading their custom ISAPI module required an additionnal layer to do it without iisreset)
    -there's actually no equivalents for rdist, cron, syslog. They ported them to win32.
    -they had to hack the net driver to change MTU on the fly

    More important to me: they had an hard time figuring out stuff because of the lack of documentation and all undocumented interfaces. They even didn't suspected all the CLI facilities of Win2000 (nor do I).
    So, W2K Server is powerful, yet it's setup in a bloated way making it difficult to manage. I wish some good papers would be written on the subject for all of us stuck with administring such boxes to benefit of other's experiences.

    --
    have you been defaced today?
  50. Re:Hotmail? by syd02 · · Score: 3, Interesting

    It may depend on what the load balancer gives you. It does look like they're moving more IIS into the back end. Eventually it will probably be all Microsoft. When someone pointed this out to me a year or two ago, it was pretty clear that most files were being served by IIS, but when you went to login (or do anything else) the form was submitted to FreeBSD.

    Now I see that 64.4.14.24 is Running IIS 5, but 64.4.14.23 is running Apache on FreeBSD.

    At least loginnet.passport.com is running Windows.

  51. Systemantics by jefu · · Score: 5, Interesting
    Along the same lines (more or less) is "Systemantics" by John Gall. Everyone in any kind of organization should read this - especially managers. (Don't worry, they'll have little problem finishing it, it doesn't use too many big words, there are pictures and its only about 100 pages long.)

    But it portrays, about as accurately as I've ever seen it, how systems are created to do one thing and end up doing something very different - and usually not something all that valuable.

    The following is quoted (excerpted) from the back cover.

    • Systems are seductive. They promise to do a hard job faster better and more easily ... But ... you are likely to find you time ... now being consumed in the care ... of the system itself. New prolems are created by its very presence.
    • Once set up, it won't go away.
    • It begins to do strange and wonderful things
    • Breaks down in ways you never thought possible
    • It kicks back, gets in the way
    • Your own perspective becomes distorted by being in the system
    • You push on it to make it work
    • Eventually you come to believe that the misbegotten product it so grudgingly delivers is what you really wanted all that time.
    • You are now a Systems Person
  52. PPT was a rip of HG by MrChuck · · Score: 3, Informative
    It's been sort of said, but recall that MS had Excel and Word.

    The dominant presentation tool was Harvard Graphics. It was used by EVERY business that needed a tool like that. Microsoft used it all the time.

    Then they created PowerPoint. As typical of their strategy, version one and two we're worth wiping your butt with. A friend at MS was ORDERED to stop using HG and start using PowerPoint. He lost animation, audio, etc.
    "PPT is a multimedia presentation tool without the burden of being multi or very useful" in his words.

    How to get market share for this ? Hmmmm (/me strokes beard).
    I know! Bundle it with Word and Excel, call it "Office" and make that the only way for businesses to buy it!

    It was a two-fer. If you lived on WordPerfect and Excel, or Word and 1-2-3 or Quattro Pro, well, when you upgraded, you have both MS products. It's now a bad business idea to also go get WordPerfect or 1-2-3 (to be fair, Lotus never really upgraded 1-2-3 in a timely way and Quattro smoked it for $119).

    Need a presentation tool? PowerPoint is Free! (no, your honor, it was fair competitive practices - we just gave customers the 3 tools and charged them for Word and Excel but we didn't make PowerPoint "free").

    As it aged, it did become more useful. And bloated. And proprietary.

  53. Moderators on crack! by Lethyos · · Score: 5, Informative

    Uh, sorry, but this is just plain wrong. Microsoft took the code they had from OS/2 and made it into Windows NT.

    Uh, sorry, but this is just plain wrong. NT is the product of VMS engineers bringing their talents and experience into a different product.

    Ever wonder why the first release of Windows NT was called '3.1'?

    No, actually. It was to avoid maturity confusion between NT and Windows 3.1. Releasing Windows NT as 1.0 would have made marketing less effective. Given it had the same UI as Windows 3.1 was another reason.

    While your last paragraph is true, it hardly constitutes receiving a score of 5. Moderators need less crack.

    --
    Why bother.
  54. Re:Chocolate and Hookers by Jason+Earl · · Score: 5, Funny

    I don't think that I would accept a hooker from Microsoft. My guess is that she would have a virus.

    Chocolate, on the other hand...

  55. University is not Earth... by E-Rock · · Score: 3, Insightful

    Do not think that any experience from working in any Institutional environment maps to the 'real world'.

  56. Re:You really don't get it, do you? by shyster · · Score: 4, Interesting
    You defend Windows as if it were your lifeline, but tell me... How often do you actually walk into your server room, use the KVM switch to get to the proper server, administer the server in person while looking at a monitor? With a GUI, you almost need to do this.

    Disclaimer: Windows is my lifeline. I'm paid to work on Windows machines. And to answer your question, I do it quite often if it's the most convenient way to get things done. Of course, I also have an admin workstation with MMC tools loaded, can telnet in, can run TightVNC, or Terminal Services for remote control, or can use a lot of tools (native Win2K + 3rd party) to administer from the CLI of my own box. Or, I can automate things via WSH using VBScript (my scripting language of choice) if it's something repetitive. Whichever suits me and the problem at hand at the moment and makes my life easier.

    Not saying that UNIX is wrong in it's CLI, but saying that a GUI in Windows is not a good excuse for not being able to automate or run from the CLI if you want.

    A server is not something that you should not have a mouse or a keyboard hooked up to. It's a little box, in a darkened and protected room. It should NEVER go down. Ideally, it should never even be touched after the day it's installed.

    Servers DO go down, both UNIX and Windows. It's a cost of doing business. And you usually don't have to touch a Windows server after it's installed unless you want to change something. That's about the same as for UNIX, isn't it?

    You say that open ports on Windows servers should be taken care of by a firewall. Tell me, if Windows were secure, why would a firewall be necessary at all?

    So, do you run *nix boxes on the internet without a firewall? I don't. I'd say it's pretty standard practice to put webservers of all kinds behind firewalls, so the paper pointing out open ports is a bit of a red herring.

    The imaging servers / multicasting solution you speak of is the lazy man's solution. It is the state of programming society that has lost the interest in efficiency, because modern hardware can cover up inefficiency. The inefficiency still remains. This lazy way is not the kind of mindset that a forward looking, intelligent individual should have. So what if the right way is sometimes a little more difficult?

    When the "right way" takes more time, specialized skill, and effort, then it's the "more expensive way". And then you have to weigh the costs involved as well. A forward looking, intelligent individual uses the resources available to him to do the job in the most EFFICIENT manner. When hardware is cheaper than eeking out another .1% performance boost from recoding or optimizing, then throwing hardware at the problem is a viable solution. I can buy 512MB of RAM for less than what it costs for a client to pay me for 1 hour. If that solves the problem, then it makes more sense to buy the RAM. That's business.

    Sometimes we don't have fibre, sometimes we don't have 1000BT. Most times, we don't have the massive RAID arrays and ultra expensive hardware that MS can provide.
    Yeah, multicasting a 900MB image requires fiber and 1000BT. And huge terabyte SAN's of course. Right. And don't forget the massive supercomputer cluster to process that huge load. My god, it's almost 1.5 CD's worth! That's half of the RedHat download! (I know, RedHat includes more than just Linux, but it's quite feasible to download all 3 ISO's on a DSL line, so I don't think Gigabit Ethernet is required for a 900MB image).

    Oh, and a *Nix can have just about everything turned off with exception of the kernel. I can load hardware drivers without rebooting, I can kill every process that isn't necessary.

    Umm...you can kill every process in Windows that isn't necessary too. That's why they're called unnecessary. Admittedly, if your only tool is the taskmanager then you're not a knowledgeable admin, so Windows will protect you from yourself...but I see that as a good thing.

    I can completely update my system without a reboot, yet every service pack I've encountered requires at least 1 reboot.

    Like a reboot is that big of a deal. It takes all of 5 minutes, and can even be scheduled. Let's get off the uptime high horse, eh? If you need 24/7 uptime, there's ways to get it, but be prepared to pay for it...both with *nix or Windows.

    I've run into situations where I couldn't "Stop" a service that was running on Win2k, but never with *nix.

    Like I said, you're probably not a Windows admin. I am, and have never run into a service I couldn't stop. There are some I shouldn't have stopped, but that's another story. =)

    Bottom line is that both Windows (2000) and *nix are good operating systems. Well suited to almost any task required of a server. They both require knowledgeable admins to be used to their fullest potential, but Windows has the edge in ease of use. A semi-technical manager can have a Windows network up in an weekend...not so for *nix. Of course, the price the manager pays is that his server isn't really set up correctly, but that's what you get when a manager or low skilled admin sets up a server. Same thing as when I work on my car, I know it's not up to the same standards as a professional mechanic, but sometimes it's worth the tradeoff. Linux and FreeBSD have advantages in that they're free, highly configurable, and can run on old hardware. Strong selling points for some, not so for others. Everything involves tradeoffs.

  57. Re:That's different. by Hektor_Troy · · Score: 3, Insightful
    [...]but I don't like reporters hacking into servers for personal gain either.
    Why do you think they did that?

    They found the documents on a publicly announced ftp server. An ftp server that Microsoft links to, that their customers can download all kinds of stuff from. If you say I can take anything from your garage, and you place a stack of 100$ bills in there by accident - does that mean I can't take them? You just told me I could!

    That's why I made the example of them handing out free newspapers and then accidently printing a confidential memo in the paper. That's not my fucking fault, and it has absolutely nothing to do with lousy protection. It does, however, have everything to do with the right hand not knowing what the left hand is doing.

    You can't give me a picture and then tell me I can't look at it when you find out that it's a pornographic picture of you and someone you wish you'd never had sex with. It doesn't work like that. You gave it to me - now it's mine. You still have copyright on it, but you can't claim that I was stealing something that you gave me.

    Now ... was that clear enough as to the difference between stealing and being given something?
    --
    We do not live in the 21st century. We live in the 20 second century.
  58. Re:That's different. by Hektor_Troy · · Score: 3, Informative

    I didn't need to read the linked article, as I've read around ... 6 or 7 other articles about the exact same thing. They all say the same thing like this one in Danish:

    http://www.comon.dk/index.php?page=news:show,id= 12 577

    "The ftp server is usually used by Microsoft's costumers to fetch drivers and updates and to upload files to the company's PSS Security Response Team."

    And comon is nice enough do link to the server in question:

    ftp://ftppss.microsoft.com/

    Granted, The Register's article does use language like "poorly protected server" and "discovered", but I see no problem in using those words, if whoever placed the files there didn't think about using some kind of authentication and directory access for those documents. Then you would still "discover" the files on a "poorly protected server" since it was used for something it was not supposed to be used for.

    So in short - something is amiss, but using "juxtapositioning" in your language, doesn't mean your covering up an illigal act.

    --
    We do not live in the 21st century. We live in the 20 second century.