Slashdot Mirror


New Sidekick Will Run NetBSD, Not Windows CE

jschauma writes "Many sites are reporting that the next Sidekick LX 2009/Blade, from Danger (acquired by Microsoft early in 2008), is going to run NetBSD as their operating system, causing Microsoft's recruiters to look for NetBSD developers."

262 comments

  1. Is a 'Holy Fuck' in order? by ushering05401 · · Score: 2, Insightful

    Just asking.

    1. Re:Is a 'Holy Fuck' in order? by dotancohen · · Score: 0, Flamebait

      Of course no. Hotmail run Apache on Linux :)

      --
      It is dangerous to be right when the government is wrong.
    2. Re:Is a 'Holy Fuck' in order? by ushering05401 · · Score: 1

      That is interesting, but I was more referring to the fact that MS will be distributing this product.

      Most users will never know that Hotmail and Apache are running on Linux.

      Thanks for the info, though ;)

    3. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 2, Funny

      Wait, now that you REPEATED that I realize the significance...

      Serving Hotmail with Apache on a dinky little SIDEKICK? That's fuckin AWESOME!

      No wonder MS is the best company ever.

    4. Re:Is a 'Holy Fuck' in order? by MichaelSmith · · Score: 4, Insightful

      I feel so torn. On one had here is a chance to be paid to work on netbsd. On the other hand the job is with Microsoft.

    5. Re:Is a 'Holy Fuck' in order? by ushering05401 · · Score: 0, Redundant

      C'mon, Taco, leave him alone.

    6. Re:Is a 'Holy Fuck' in order? by carlzum · · Score: 4, Informative

      That was always one of my favorite MS facts, unfortunately they switched to IIS a few years ago. Netcraft confirmed it :)

    7. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      -5, Taco? I was being serious.

    8. Re:Is a 'Holy Fuck' in order? by PixetaledPikachu · · Score: 1

      Of course no. Hotmail run Apache on Linux :)

      you mean used to?

    9. Re:Is a 'Holy Fuck' in order? by kestasjk · · Score: 3, Insightful

      I love that this story comes out just after the latest NetBSD came out and everyone was leaving cynical "why do they still bother" comments. :-)

      --
      // MD_Update(&m,buf,j);
    10. Re:Is a 'Holy Fuck' in order? by X0563511 · · Score: 1

      I hear Microsoft is good to work for.

      Why not, if you are going to be doing NetBSD work? It's not like you would be going in to code the next Microsoft Useless Widget 2.0.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    11. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      05401 is a code for troll accounts.

      Stop feeding him.

    12. Re:Is a 'Holy Fuck' in order? by hhw · · Score: 5, Informative

      You mean, Hotmail used to run FreeBSD before Microsoft bought it, and for the 4+ years it took them to migrate it over to Windows without failing?

      Hotmail itself has never run on Linux. It may however have some of its content delivered by Akamai's CDN, which does run Linux (but not Apache).

      --
      http://astutehosting.com/
    13. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 1, Insightful

      It's not like you would be going in to code the next Microsoft Useless Widget 2.0.

      Right. You'll just be porting Microsoft Useless Widget from Windows CE to NetBSD.

    14. Re:Is a 'Holy Fuck' in order? by Snowblindeye · · Score: 4, Informative

      Of course no. Hotmail run Apache on Linux :)

      Hotmail never ran on Linux. Originally, before Microsoft bought it, it was running on FreeBSD with Apache, with some backend servers running Solaris.

      Microsoft had a lot of trouble switching to Windows, and even after they claimed they had migrated, they had to admit that some things were still running on BSD.

      However, by now I'm sure they've had enough time to finish that switch.

    15. Re:Is a 'Holy Fuck' in order? by gweihir · · Score: 1

      Personally I think the switchover was too fast. I suspect they just simulate an IIS (which Apache easily allows).

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    16. Re:Is a 'Holy Fuck' in order? by Mikeytsi · · Score: 0, Redundant

      Hotmail has never run on Linux. It USED to run on Solaris (which was the platform it was originally developed on before Microsoft purchased it). It was then converted to IIS over Windows Server for the front-end and Solaris for the Backend mail storage, and is now fully Windows Server based.

      --
      I've been called a "Fucking Dick" by better people than you.
    17. Re:Is a 'Holy Fuck' in order? by crazybit · · Score: 0

      be careful, you can end up programming closed source programs that run on top of a NetBSD kernel.

      --
      - Human knowledge belongs to the world
    18. Re:Is a 'Holy Fuck' in order? by cbhacking · · Score: 4, Informative

      Incorrect; Hotmail never ran on Linux. It did continue to use Apache for some time, however.

      Hotmail, when originally purchased, ran on FreeBSD and Solaris. Portions of it were moved to NT, running on Apache in the POSIX subsystem of the NT kernel (at the time, Apache for Win32 was not available, and Apache was miles ahead of IIS). This is one of the few cases I know of where the POSIX subsystem was used internally by Microsoft, although it is still under development and available in recent NT-based operating systems (some editions of Vista and Win7, and their server equivalents).

      --
      There's no place I could be, since I've found Serenity...
    19. Re:Is a 'Holy Fuck' in order? by NoMaster · · Score: 1

      And there's a problem with that?

      Even if a closed-source app statically links *BSD libs it's not a problem. That's the fundamental point of difference between the GPL & BSD licences.

      --
      What part of "a well regulated militia" do you not understand?
    20. Re:Is a 'Holy Fuck' in order? by arogier · · Score: 1

      Too bad the sidekick is probably still going to be locked into that awful Danger hell. Still I might try the NetBSD version to see what hacks can be done. The sidekick has a nice keyboard for a command line. Then there's filling that screen with the greatest UI for that form factor. # This is going to be great fun or horribly underwhelming.

    21. Re:Is a 'Holy Fuck' in order? by unleashedgamers · · Score: 1

      Well, not just Solaris but both FreeBSD and Solaris 2.6 for Hotmail in the past.

    22. Re:Is a 'Holy Fuck' in order? by calmofthestorm · · Score: 1

      Better than the other way around. That would be like digging your own grave or training your successor after being given notice.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    23. Re:Is a 'Holy Fuck' in order? by Architect_sasyr · · Score: 3, Informative
      My tests are quick and dirty and I don't have a full environment to work with, but I think you might be right:

      lg:~ root# nmap -sV -O -p 25,80,443 -PN -n www.hotmail.com

      Starting Nmap 4.76 ( http://nmap.org/ ) at 2009-02-[snip]
      Warning: Hostname www.hotmail.com resolves to 12 IPs. Using 64.4.38.249.
      Interesting ports on 64.4.38.249:
      PORT STATE SERVICE VERSION
      25/tcp filtered smtp
      80/tcp open http Microsoft IIS webserver 6.0
      443/tcp filtered https
      Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
      Device type: general purpose
      Running (JUST GUESSING) : FreeBSD 6.X (85%)
      Aggressive OS guesses: FreeBSD 6.2-RELEASE (85%)
      No exact OS matches for host (test conditions non-ideal).
      Service Info: OS: Windows

      OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
      Nmap done: 1 IP address (1 host up) scanned in 15.76 seconds
      lg:~ root# nmap -sV -O -p 80 -PN -n xxx.xxx.xxx.xxx

      Starting Nmap 4.76 ( http://nmap.org/ ) at 2009-02-[snip]
      Interesting ports on xxx.xxx.xxx.xxx:
      PORT STATE SERVICE VERSION
      80/tcp open http Microsoft IIS webserver 6.0
      Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
      Device type: general purpose
      Running: Microsoft Windows 2003
      OS details: Microsoft Windows Server 2003 SP1 or SP2
      Service Info: OS: Windows

      OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
      Nmap done: 1 IP address (1 host up) scanned in 8.46 seconds
      lg:~ root#

      The second server is obviously a known IIS/Win2003 box.

      --
      Me failed English...
      FreeBSD over Linux. If my comments seem odd, this may explain...
    24. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      Jokes aside, that's how I started working at MS. Grew up hating them, took a temp job there working with Apache, and accidentally backed into a good job as a dev working on Windows. :)

    25. Re:Is a 'Holy Fuck' in order? by 0xygen · · Score: 1

      Presumably you understand that most of the OS type guessing in nmap uses quirks in the TCP stacks to determine which OS it is.

      So if the "first" box you talk to exhibits FreeBSD quirks, ie the load balancer / cache, no matter what is behind it, it will be identified as FreeBSD, right?

    26. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      Actually it was just an RC, Release is still not here...

    27. Re:Is a 'Holy Fuck' in order? by hattig · · Score: 1

      Didn't they initially just switch the front-end web servers to IIS, keeping the FreeBSD and Solaris backend?

      I wonder how long it took them to complete the migration of the backend? I'm sure they must have done that by now.

    28. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      And there's a problem with that?

      Even if a closed-source app statically links *BSD libs it's not a problem. That's the fundamental point of difference between the GPL & BSD licences.

      A non compete clause in your contract perhaps? The obligation to never, ever, code anything for NetBSD that looks even slightly remotely similar to what you did at work so that Microsoft won't sue you for copyright infringement, and win?

      But I think the grand parent meant that you wouldn't end up actually being paid to work on netbsd, but on some random proprietary user interface.

      I don't think each and every discussion has to be about the fundamental point of difference between the GPL & BSD licenses. I'm actually tired of it.

    29. Re:Is a 'Holy Fuck' in order? by Architect_sasyr · · Score: 1

      Actually the second server is sitting behind a NAT box running FreeBSD 6.4-STABLE - whether that affects it or not. Perhaps if the box in front was doing TCP Proxying rather than, say, NAT?

      --
      Me failed English...
      FreeBSD over Linux. If my comments seem odd, this may explain...
    30. Re:Is a 'Holy Fuck' in order? by SL+Baur · · Score: 1

      I hear Microsoft is good to work for.

      Why not, if you are going to be doing NetBSD work?

      Perhaps, but do they force you to use a Microsoft Windows box to do your work? That would be a show stopper for me.

      Maybe 6.0/6.1 is better, but I did try out Microsoft Windows XP for awhile for educational purposes on a work machine and the only moments I truly enjoyed the experience were when I was turning the machine off and later installing RHEL over XP at the end of the time.

      Mac OS X is not too bad, not great, but nothing beats KDE 3.5 for ease of use and development.

    31. Re:Is a 'Holy Fuck' in order? by stevey · · Score: 1

      Here's the paper covering the migration of hotmail over to Windows 2000.

      Interesting reading if you have the time for it.

    32. Re:Is a 'Holy Fuck' in order? by jggimi · · Score: 2, Informative

      Most users will never know that Hotmail and Apache are running on Linux.

      BSD is not Linux.

    33. Re:Is a 'Holy Fuck' in order? by claytonjr · · Score: 2, Informative

      Hotmail is/was powered by a mixture of FreeBSD and Solaris. NOT Linux. Get it right.

      http://en.wikipedia.org/wiki/Hotmail

    34. Re:Is a 'Holy Fuck' in order? by torstenvl · · Score: 1

      "A non compete clause in your contract perhaps ... so that Microsoft [could] sue you for copyright infringement, and win?"

      Um. Not even wrong. Non-competes have absolutely nothing to do with copyright.

    35. Re:Is a 'Holy Fuck' in order? by jc42 · · Score: 1

      Hotmail is/was powered by a mixture of FreeBSD and Solaris. NOT Linux.

      Hmmm ... I decided to check. A few probes of hotmail.com turned up only headers like:

      HTTP/1.1 302 Redirected
      Connection: close
      Date: Tue, 03 Feb 2009 14:10:32 GMT
      Server: Microsoft-IIS/6.0
      Location: http://lc2.bay0.hotmail.passport.com/cgi-bin/login
      HTTP/1.1 302 Found
      Date: Tue, 03 Feb 2009 14:10:33 GMT
      Server: Microsoft-IIS/6.0
      P3P: CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"
      xxn:28
      MSNSERVER: H: BAY124-W28 V: 13.2.260.1209 D: 2008-12-09T21:13:20 ...

      So where are the signs of any *BSD or Solaris system here? It looks very much like a typical Windows server running IIS.

      This isn't to say that they aren't also running Solaris or FreeBSD servers. But my probes didn't turn up any evidence of such systems during this brief time window.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    36. Re:Is a 'Holy Fuck' in order? by spud603 · · Score: 1

      I suspect that Microsoft's whole "passport" multisite authentication runs on Windows/IIS. Notice the TLD you're hitting: passport.com.
      Try logging in and probing the servers that actually dish out the mail application.

    37. Re:Is a 'Holy Fuck' in order? by Ninnle+Linux · · Score: 1
      He wasn't talking about copyright in the first place. If read the post again, you'd notice that. Here I'll even point out the relevant section:

      But I think the grand parent meant that you wouldn't end up actually being paid to work on netbsd, but on some random proprietary user interface. I don't think each and every discussion has to be about the fundamental point of difference between the GPL & BSD licenses. I'm actually tired of it.

    38. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      GPL/BSD discussion and copyright discussion are not coextensive, you fucking idiot

    39. Re:Is a 'Holy Fuck' in order? by bastafidli · · Score: 1

      Hotmail was migrated from FreeBSD to IIS few years ago. It originally run on FreeBSD when Microsoft purchased it.

    40. Re:Is a 'Holy Fuck' in order? by OneFix · · Score: 1

      Actually, it's a known fact that Microsoft will commonly put up a BSD server and tweak Apache's response headers to report it as IIS. They have actually been caught doing it a few times. It would look kind of bad if Microsoft doesn't use their own product.

    41. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      Incorrect. In actual fact, Hotmail used to run on six 128MB flashdrives, an old AM/FM radio and a few potatoes.

    42. Re:Is a 'Holy Fuck' in order? by Hucko · · Score: 1

      I'd dunno... at least KDE understands how to use blockquote tags.

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
    43. Re:Is a 'Holy Fuck' in order? by Anonymous Coward · · Score: 0

      "It would look kind of bad if Microsoft doesn't use their own product."

      Commonly translated as eat your own dog food.

    44. Re:Is a 'Holy Fuck' in order? by Sinning · · Score: 0

      Was MacGuyver the server admin?

  2. Quite a loaded summary there by gcnaddict · · Score: 0, Flamebait

    Loaded with links, that is.

    Really? Did we need 5 links in one sentence to convey a message which would've sufficed with at least two less links?

    --
    Viable Slashdot alternatives: https://pipedot.org/ and http://soylentnews.org/
    1. Re:Quite a loaded summary there by Anonymous Coward · · Score: 0

      Which ones would you keep? I personally didn't know what "many", "sites", "reporting", "NetBSD" and "developers" meant, so I was happy to see them all hyperlinked.

  3. I never thought I'd see the day. by jadedoto · · Score: 0, Troll

    Heaven forbid we use the GPL. Let's go for the BSD license! It's worse!

    Go Microsoft, you're finally growing up!

    1. Re:I never thought I'd see the day. by flyingfsck · · Score: 2, Informative

      BSD is the only licence that is compatible with MS business practice.

      MS is no stranger to Unix, they wrote Xenix long ago.

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    2. Re:I never thought I'd see the day. by jadedoto · · Score: 1

      About it being the only compatible free license, this is, unfortunately, very true. It's the only reason why I don't like using it. I don't think it's right to suck up code. Then again, recycling code... Gah, I don't know. BSD license makes me feel all conflicted inside!

    3. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 1, Insightful

      If you don't *like* the ramifications of the license, don't *use* it. Many are fine with the implications of the BSD license.

    4. Re:I never thought I'd see the day. by MichaelSmith · · Score: 4, Funny

      BSD is the only licence that is compatible with MS business practice.

      So can I get windows and word with a BSD license?

    5. Re:I never thought I'd see the day. by palegray.net · · Score: 1, Offtopic

      Look, BSD licensing allows the end user to do whatever their want with the code in question, as long as they follow the attribution requirements outlined in the licensing. How can you possibly make code more free than that?

      Yes, I'm posting this from an Ubuntu laptop, while performing maintenance on a couple of Debian servers, and poking around at a CentOS server running several variants of Linux in virtual machines. So, yeah, I enjoy using GPL products. It doesn't mean the GPL bestows more freedoms on the end user, as it certainly contains more constraints than BSD licensing.

    6. Re:I never thought I'd see the day. by PenguSven · · Score: 1

      MS is no stranger to Unix, they wrote Xenix long ago

      no, they licensed it from AT&T. It later became SCO UNIX

      --
      What is...?
    7. Re:I never thought I'd see the day. by H3g3m0n · · Score: 2, Interesting

      No but windows does have BSD code in it. Specifically ftp.exe and some zlib code.

      --
      cat /dev/urandom > .sig
    8. Re:I never thought I'd see the day. by Hal_Porter · · Score: 1

      MS is no stranger to Unix, they wrote Xenix long ago.

      Oh my God, is that an ASCII RickRoll?

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    9. Re:I never thought I'd see the day. by LUH+3418 · · Score: 0, Redundant

      Some people just completely reject the idea of closed source software. Since BSD allows open source software to be modified into closed source software, they view it as a bad thing.

      The GPL forces everyone to make their contributions open, which does have some nice benefits when it comes to encouraging improvement of software... However, it's often incompatible with the way many companies develop software.

      Many large software development companies would never want to open source their software. They believe it would allow people to steal their trade secrets. To these companies, the BSD license is a viable option, but not the GPL.

      I personally think it would be nice if everything was completely open, but I think that's the kind of utopic vision the world is not ready for.

    10. Re:I never thought I'd see the day. by Corporate+Troll · · Score: 1

      They licensed Xenix. I wouldn't call that "wrote".

    11. Re:I never thought I'd see the day. by Knuckles · · Score: 2

      What are the constraints that GPL bestows on the end user? Right, none at all.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    12. Re:I never thought I'd see the day. by palegray.net · · Score: 2, Insightful

      I personally think it would be nice if everything was completely open, but I think that's the kind of utopic vision the world is not ready for.

      I wish for the same thing, and look forward to the day when economic scarcity is no longer human concern.

    13. Re:I never thought I'd see the day. by Kjella · · Score: 4, Insightful

      Look, BSD licensing allows the end user to do whatever their want with the code in question

      End users do not use source. End users use binaries. Granted, they can compile from source if they have it. GPL binaries come with source. BSD-based binaries in general don't. It can be 99% BSD code, 1% special closed source driver code but the whole comes without source and it does me fuck all good that it's 99% BSD. BSD is ultimate freedom for the ones with the source, GPL is a little less freemdom what you can do with the source, but it makes sure I will have the source in the first place.

      Unless you limit yourself to pure BSD you as an end user have absolutely nothing, no more than if it was through and through proprietary. The freedome that you could try to figure to what bits and pieces of BSD they used, how they put them together and add the secret source yourself is illusory at best, possibly plain out illegal through patent law at worst. Maybe it could help some developer make a similar product, but as user of a closed-source derivative you have no ability to make small changes to improve or fix anything. You are at the vendor's mercy, you have the same lock-in issues, you have the same "embrace, extend, extinguish", they support only the platforms they choose and end support when they choose. "BSD based" means nothing to the end user except maybe that it was slightly cheaper to produce rather than reinvent the wheel.

      Of course you can just stay with pure BSD. But then you're fighting a million companies that want to kill off the userbase that actually could improve that code by making them use properietary "value-added" versions instead. Let me take an example:

      Linux user use Konqueror, finds bug in engine, patches source, has better Konqueror instantly, sends fix upstream, everyone gets a better Konqueror.
      Mac user use Safari, finds bug, can't compile Safari but has to compile Webkit engine by itself, sends fix upstream, someday get an improved Safari.

      The last is much, much more unlikely because it doesn't fix the end user's problem. The far more likely story is that he'd file a bug with Apple that may or may not do anything about it but then you're right back to classic "report error to vendor, wait for fix" just as if you reported an IE bug to Microsoft. I just don't see the appeal of "based on open source" because it is not anywhere near "open source". And the only advantage of the BSD over the GPL is to make products "based on open source".

      --
      Live today, because you never know what tomorrow brings
    14. Re:I never thought I'd see the day. by palegray.net · · Score: 1

      You're right, none at all. Until you decide to change the code and redistribute it. Oops.

    15. Re:I never thought I'd see the day. by MichaelSmith · · Score: 2, Insightful

      The makers of this device have taken a free operating system and used it to build their product, from which they will make money. I don't see anything wrong with requiring them to release changes they have made, so that others can benefit.

    16. Re:I never thought I'd see the day. by Enleth · · Score: 0, Redundant

      Actually, both licenses are as free for the end user of the code as they could possibly get. The point is that for BSD, "end user of the code" == "a developer using *the code* as in getting the source into his work", whereas for GPL "end user of the code" == "a computer user running the code in an executable form". See? That's what most people bashing themselves up over this can't (or don't want to) realize. And it seems that having both kinds of "end user" granted maximum freedoms by a single license is impossible because those freedoms conflict - certainly, no license like that exists right now. Now, it's up to you to decide which kind of the "end user" you like more and want to give more freedoms to.

      --
      This is Slashdot. Common sense is futile. You will be modded down.
    17. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 4, Insightful

      What are the constraints that GPL bestows on the end user? Right, none at all.

      You're right, none at all. Until you decide to change the code and redistribute it. Oops.

      What part of the term "end user" confuses you?

    18. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 0

      That's good. BSD code helped make the OS 90% of people use a better one. Even if I don't like it that's not a bad thing.

      The TCP/IP stack too comes from BSD sphere.

    19. Re:I never thought I'd see the day. by Jurily · · Score: 4, Insightful

      No but windows does have BSD code in it. Specifically ftp.exe and some zlib code.

      Which is exactly the reason for all the BSD vs GPL holy wars.

      GPL is about the freedom of the code: "I've shown you the code, if you use it, show your code to anyone who wants it". BSD is about the freedom of the software: "Hey, I wrote this. Use it."

      Regarding Windows:

      GPL: "Oh noes! They closed the source!"
      BSD: "Cool, they're using my stuff! At least they got *that* part right."

    20. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 0

      The TCP/IP stack too comes from BSD sphere.

      Nope. I don't know where this myth came from.

    21. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 0

      Redistribute? That doesn't make you a non-end user?

    22. Re:I never thought I'd see the day. by SL+Baur · · Score: 3, Informative

      MS is no stranger to Unix, they wrote Xenix long ago.

      True except that they did not "write" Xenix. Xenix was a licensed fork from AT & T source code.

      In another lifetime I once thought Microsoft was showing promise by bringing a Unix-like interface to PC DOS 2.0. Most of the code was half-assed and broken and I guess they kind of just left it that way.

      Oh and for the folks whining about 6.1 aka Microsoft Windows 7 being a paid-for bug fix release over the previous one, that's really old news because PC DOS 2.1 was the same thing over 20 years ago. That was as much abuse as I could take from a company, but I guess others have different tolerances for pain.

    23. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 0

      End users and developers sets have a non nil intersection.

    24. Re:I never thought I'd see the day. by richlv · · Score: 2, Informative

      "I've shown you the code, if you use it, show your code to anyone who wants it".
      a bit wrong.
      if you use it, nobody cares. if you modify and then give somebody else, you have to give them code of the modfications as well.
      distribution, as opposed to use.

      --
      Rich
    25. Re:I never thought I'd see the day. by icebraining · · Score: 1

      Offtopic? He's talking about the usage of BSD licensed code by Microsoft, how is this offtopic?

    26. Re:I never thought I'd see the day. by thePowerOfGrayskull · · Score: 1

      Xenix? Wait, is that the Unix used by Xena, Warrior Princess?

    27. Re:I never thought I'd see the day. by icebraining · · Score: 1

      I, as an end user, like the possibility to adjust the software to my needs even if I never redistribute it. How can a developer using the code in his work be an "end user"? That's not the "end", the end is the people is sells/gives the code to.

    28. Re:I never thought I'd see the day. by torstenvl · · Score: 1

      Very poor moderation. MichaelSmith, we salute you for your non-offtopic comment.

    29. Re:I never thought I'd see the day. by Jah-Wren+Ryel · · Score: 3, Insightful

      Regarding Windows:

      GPL: "Oh noes! They closed the source!"
      BSD: "Cool, they're using my stuff! At least they got *that* part right."

      Or rather:

      GPL: "Oh noes! They closed the source!"
      BSD: "Shit, they added bugs to my perfect code and the billions of users can't do a thing to fix it."

      --
      When information is power, privacy is freedom.
    30. Re:I never thought I'd see the day. by Jurily · · Score: 1

      Well, the thread is about a commercial OS containing open source code, so I guess we can assume distribution.

      +1 Pedant, though

    31. Re:I never thought I'd see the day. by jabberw0k · · Score: 1

      Amen to that! PC-DOS 2.0 on 180K floppy disks seemed like a step in the right direction. Why, there was even support for those fancy double-sided floppies! Subdirectories! Pipes (of a mangled sort)! Redirection! There was even a way to set your command-switch character to '-' instead of '/'! Yes, you could type: 'dir -w' for a wide listing... But then they never went any further, never changed the underlying CP/M-ness of the thing... I had almost forgotten.

    32. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 0
      The OS X end user can replace the standard webkit with their own version (or one of the nightly builds).

      PS - the konquorer engine is now WebKit.

    33. Re:I never thought I'd see the day. by Tiber · · Score: 1

      Ever boot an SCO box?

      "Portions copyright Microsoft yadda yadda yadda".

    34. Re:I never thought I'd see the day. by Hatta · · Score: 1

      BSD: "Cool, they're using my stuff! At least they got *that* part right."

      Unless "they" happens to be a Linux distribution.

      --
      Give me Classic Slashdot or give me death!
    35. Re:I never thought I'd see the day. by Ibn+al-Hazardous · · Score: 1

      Probably from the fact that the TCP/IP driver used to say it did. It was under BSD license with the advertizing clause.

      I'm not sure exactly when they wrote their own, but I think it was after Win2k. So, I would think Vista or Server 2k3 might be it. (Gut feeling says Vista - but I haven't used Windows after 2k, so I haven't checked.)

      --
      Yes, I am a biological organism. All rumors to the contrary are just that, rumors.
    36. Re:I never thought I'd see the day. by pseudonomous · · Score: 2, Insightful

      The way I see it, the BSD and GPL and Proprietary licenses are best understood be an analogy to the prisoners dilemma:

      -BSD is always cooperate

      -GPL is an eye for an eye

      -Proprietary is always defect

    37. Re:I never thought I'd see the day. by bsDaemon · · Score: 1

      That's because that's the they that killed Kenny, and they're bastards.

    38. Re:I never thought I'd see the day. by palegray.net · · Score: 1

      Only on Slashdot will you see a comment on BSD licensing, in a story about NetBSD, get modded offtopic. All hail the glorious GPL, I guess.

    39. Re:I never thought I'd see the day. by Knuckles · · Score: 1

      As the ACs have said.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    40. Re:I never thought I'd see the day. by rbanffy · · Score: 1

      Isn'z zlib LGPL?

    41. Re:I never thought I'd see the day. by Anonymous Coward · · Score: 0

      No, it's because some guy found a BSD message in a couple of internet-related command line utilities and thus the myth was started.

      The TCP/IP stack in Windows 2000 came from Intel, for what it's worth.

    42. Re:I never thought I'd see the day. by SL+Baur · · Score: 1

      Pipes (of a mangled sort)! Redirection! There was even a way to set your command-switch character to '-' instead of '/'! Yes, you could type: 'dir -w' for a wide listing... But then they never went any further, never changed the underlying CP/M-ness of the thing...

      Indeed and the system calls introduced in 2.0 all had Unix style semantics. Sadly, 2.0 had a lot of bugs in that new code that made them barely usable.

      But just to name one bug I found in DOS 2.0, if you descended into a subdirectory that textually was close to their fixed sized limit (128 I think) and tried to to `cd ..' the system would take a text string (saved as the current directory) and append `/..' to it and do unexpected things.

      The way COMMAND.COM dealt with pipelines was more remeniscent of VMS DCL than anything else. When did the VMS guys go to Microsoft? 1982 sounds way too soon.

      COMMAND.COM also supported /dev/ as a prefix for DOS devices ...

      EVERYBODY who was somebody in those days was a Unix guy, so I wonder why they backtracked. Microsoft in my book went from the company that produced Apple Soft Basic (which was quite decent) to something that was buggy as hell and you had to pay for the bug fix release AND forego the developmental manuals that came with 2.0. Sleazy. Elune be praised that it was my work and roommate not me who paid for the only PC DOS pcs I ever had to use.

    43. Re:I never thought I'd see the day. by richlv · · Score: 1

      heh. well, i think it is important to be precise regarding licensing issues.
      besides, a commercial os that would be modified inhouse wouldn't have to release the changes, so gpl applies to everybody equally. even if the said os is distributed, i think it is important to fully understand what exactly does gpl require.

      --
      Rich
    44. Re:I never thought I'd see the day. by ivan256 · · Score: 1

      GPL is about the freedom of the code: "I've shown you the code, if you use it, show your code to anyone who wants it". BSD is about the freedom of the software: "Hey, I wrote this. Use it."

      GPL is more about the rights of the upstream developer, and BSD is more about the rights of the downstream developer. They both are "more free" to one of the two parties, and "less free" to the other.

      In my experience, no matter what the FSF's initial intentions, authors of GPL software are generally more concerned about reserving rights for themselves than preserving freedom for others. (That rule has plenty of exceptions.)

    45. Re:I never thought I'd see the day. by bsDaemon · · Score: 1

      The construct of "end users" separate from people who are in some way contributors in the foss world is a somewhat new one.

    46. Re:I never thought I'd see the day. by badkarmadayaccount · · Score: 1

      Uhhh, how about CDDL, maybe with a LGPLesque clause?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    47. Re:I never thought I'd see the day. by badkarmadayaccount · · Score: 1

      Actually, DEC programmers were/are on the NT team, You can even see it in some file system quirks. But I don't recall any earlier transfers. *shrug* Guess M$ isn't just crappyly reimplementing UNIX. They are also crappyly reimplementing OpenVMS.

      My $0.02.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    48. Re:I never thought I'd see the day. by Knuckles · · Score: 1

      The same people have different roles depending on their actions. The moment I redistribute something I cease to be an "end user", unless you claim that this term has no meaning whatsoever.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    49. Re:I never thought I'd see the day. by Fujisawa+Sensei · · Score: 1

      Actually, DEC programmers were/are on the NT team, You can even see it in some file system quirks. But I don't recall any earlier transfers. *shrug* Guess M$ isn't just crappyly reimplementing UNIX. They are also crappyly reimplementing OpenVMS.

      My $0.02.

      VMS and Windows were the two reasons I learned UNIX.

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
  4. Embrace. by palegray.net · · Score: 3, Informative

    This isn't exactly the first time Microsoft has leveraged BSD code in a product... cough, TCP stack, cough...

    1. Re:Embrace. by Svartalf · · Score: 4, Insightful

      It might be "embrace", but you can't do any more than "extend" there. As long as the *BSD crowd's interested it'll be around. Much like Linux will be.

      No, this is notable because it's an open admission that WinCE can't cut it .

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    2. Re:Embrace. by timmarhy · · Score: 1, Insightful
      apple can join that list as well. in fact everyone can. BSD is an awesome software model, and is truly free, unlike the GPL pretenders.

      i also agree this is admitted winCE is crap. we have ruggised hardware at work that uses it and i fucking hate it. activesync is the worse idea evar.

      --
      If you mod me down, I will become more powerful than you can imagine....
    3. Re:Embrace. by palegray.net · · Score: 1

      It might be "embrace", but you can't do any more than "extend" there.

      This is actually one of the things I admire about developers in a position to release their code under BSD licenses. The end user is free to do anything they please with the code, including rolling it into a proprietary product, as long as they follow the attribution requirements. As for myself, most of my public code is licensed under the GPL, for various reasons (some being financially related). No one can reasonably argue that BSD-licensed code isn't truly free.

    4. Re:Embrace. by qw0ntum · · Score: 5, Insightful

      Is there a problem with Microsoft using BSD code in their proprietary products? The developers clearly understood that was a potential outcome when they placed their code under a BSD license. As a result, they probably don't mind

      That said, would it be nice to have seen MS contribute some code back? Yes, but that was not required by the license so there is no problem. That is the whole point of the BSD-style licenses: you can take my code and do whatever you want with it; you are under no further obligation to me.

      --
      'Every story, if continued long enough, ends in death.' --Ernest Hemingway
    5. Re:Embrace. by MichaelSmith · · Score: 2, Interesting

      No, this is notable because it's an open admission that WinCE can't cut it .

      At least in the short term. MSFT appear to have bought this product from elsewhere. To keep it alive they need to get a release out the door. Maybe in parallel they are porting the software to run on WinCE.

    6. Re:Embrace. by despisethesun · · Score: 5, Insightful

      No, this is notable because it's an open admission that WinCE can't cut it .

      Not really. Someone can feel free to correct me if I'm wrong, but from what I understand, development was well underway when Danger got bought by MS. That means it was likely cheaper to just continue doing what they were doing rather than scrap the work and start again using Microsoft's stuff. Not to say that something like that would have been unheard of, but it would have delayed a product that they wanted to get out the door. The real test will be whether the next iteration of this hardware runs this same OS or whether it comes with WinMo/WinCE.

      --
      This poo is cold.
    7. Re:Embrace. by Anonymous Coward · · Score: 0

      And somehow using the TCP stack was an example of EEE?

      My god people! Stop touting EEE. There have been no real examples for ages.

      (and for the oldies, the HTML EEE isn't a legit example since *everyone* did it)

    8. Re:Embrace. by palegray.net · · Score: 4, Insightful

      Dear Lord, thank you. A post on Slashdot that mirrors the easily understandable fact that BSD licensed code is, in fact, free.

    9. Re:Embrace. by palegray.net · · Score: 1

      As you'll note from my previous reply, I take no issue whatsoever with Microsoft using a BSD base for a product. I hope you didn't infer that from my GP post.

    10. Re:Embrace. by palegray.net · · Score: 1

      I didn't imply EEE with my post, only "E." Why do people continue to attach ulterior motives to that post? Can I please have something taken in a purely literal sense for once?

    11. Re:Embrace. by MichaelSmith · · Score: 0

      If netbsd was gpl licensed I would be Free to compile my own version of the OS to run on the Sidekick. As it stands there is nothing to make them release the source code to drivers they have written.

      From my POV netbsd is less free.

    12. Re:Embrace. by palegray.net · · Score: 4, Insightful

      As it stands there is nothing to make them release the source code to drivers they have written.

      I don't think you get it. You consider "freedom" to be the ability to force other people to release their own code under terms you find favorable? Wow, dude. That's awesome.

      You're still free to download any BSD distribution you like, in its entirety, and do whatever you please with it. Stop whining about the fact that the developers of that codebase made a personal decision that they don't care what others do with their code. What's that, you feel you have the right to make that decision for them? Wow.

    13. Re:Embrace. by Ralish · · Score: 0, Redundant

      No, the derivative works from the original BSD-licensed code are "less free". The original BSD licensed code the work was based off is more free.

      This is the distinction, GPL places greater emphasis on ensuring that derivative works from the original codebase remain free, BSD doesn't.

      The end result is GPL is ideologically less free, but perhaps, more free practically due to the fairly solid guarantee provided that the code and future changes to it will remain free.

    14. Re:Embrace. by timmarhy · · Score: 4, Insightful

      forget it dude, you are arguing against a mind set that has attempted to redefine free. but it's very nature it can't understand free.

      --
      If you mod me down, I will become more powerful than you can imagine....
    15. Re:Embrace. by amirulbahr · · Score: 3, Informative

      NetBSD is not less free. The drivers that they have written are. I don't understand why people try to confuse matters.

      The BSD license is more free for users and distributors. Derived works /may or may not/ be released under a BSD license. This has NO BEARING on the original work.

    16. Re:Embrace. by timmarhy · · Score: 0, Redundant
      i don't see it, the GPL doesn't demand you contribute anything back to the project, merely that you provide source code to everyone you distribute your changes to.

      you can take a GPL product, modify the hell out of it and if you only distribute it internally amongst your company the community will never see it. granted BSD doesn't improve on this situation, but atleast you don't waste energy worrying about licensing issues.

      --
      If you mod me down, I will become more powerful than you can imagine....
    17. Re:Embrace. by JPortal · · Score: 1

      Less free to whom? BSD license has less restrictions, period.

    18. Re:Embrace. by Anonymous Coward · · Score: 0

      Its never a problem to use BSD code in a non-BSD project. Thats what the licence is designed to allow!

      Except if you want to use BSD code in, say, a GPL project like the Linux kernel. Then it becomes a major problem.

    19. Re:Embrace. by vux984 · · Score: 0

      Less free to whom? BSD license has less restrictions, period.

      Essentially, the BSD is great if you actually have something with a BSD license. The trouble with the BSD license is that by the time BSD derived software gets to you, there is no guarantee it will be BSD, or anything remotely resembling free.

      The matrix quote "what good is a phone call if you cannot speak." comes to mind. Oh sure, the BSD license is great, look at all this freedom the BSD gives you, if you had it... too bad the derivative you are working with isn't BSD anymore.

    20. Re:Embrace. by Stormwatch · · Score: 1, Flamebait

      As it stands there is nothing to make them release the source code to drivers they have written.

      I don't think you get it. You consider "freedom" to be the ability to force other people to release their own code under terms you find favorable?

      The question here is, whose freedom?

      The BSD license gives freedom to the developer; the GNU license gives freedom to the code itself.

      That is: with BSD, you can take code from the community, do work on top of theirs, and keep it for yourself. In a sense, you can take free code and turn it into non-free code. With GNU, you can take code from the community, and do work on top of theirs; then, you are obliged to share back. The code was free, the code stays free. If you use my shovel to build your playground, you damn better let me play too.

    21. Re:Embrace. by jabithew · · Score: 3, Insightful

      you are arguing against a mind set that has attempted to redefine free.

      As though 'Free' didn't have enough definitions already.

      --
      All intents and purposes. Not intensive purposes.
    22. Re:Embrace. by Urkki · · Score: 1

      If netbsd was gpl licensed I would be Free to compile my own version of the OS to run on the Sidekick. As it stands there is nothing to make them release the source code to drivers they have written.

      From my POV netbsd is less free.

      No, only the derived, unpublished code could be considered less free. The original NetBSD code is more free, easily demonstrated by the fact that it was able to be combined with other Microsoft code. If it was GPL code, it would have been locked out of this particular product. Ie. GPL makes to code more limited, less free.

      GPL is good though if you ask me. It enforces limitations, which I as a programmer often want to put on my code. It's good for this purpose precisely because it limits the freedom of the code in a way that I agree with (usually). Using the BSD license would make the code more free, more available for everyone, more compatible with different licenses and other external requirements. But I don't want that (usually), I rather want exchange of code enforces by GPL limitations.

    23. Re:Embrace. by maxwell+demon · · Score: 3, Insightful

      The BSD license gives freedom to the developer; the GNU license gives freedom to the code itself.

      No. Code cannot be free. Only people can be free.

      Actually, BSD and GPL give exactly the same rights to the developers who get the licensed code. However, the GPL restricts the rights of distributors (not all developers distribute the code they develop; as long as they don't, the restrictions of the GPL don't apply; OTOH the restrictions do apply even if you distribute the unmodified code).

      The BSD is designed to maximize the freedom immediate receivers of the licensed code get, while the GPL is designed to maximize the freedom any receiver of the licensed code get, even if they get it indirectly and/or in modified form. In order to achieve the freedom for non-immediate receivers, it restricts the freedom of distributors by forcing them to pass on those freedoms to anyone they give the code.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    24. Re:Embrace. by Ed+Avis · · Score: 1

      If netbsd was gpl licensed I would be Free to compile my own version of the OS to run on the Sidekick.

      Yeah, but you probably wouldn't be able to install it on your device, which makes it kind of pointless. (Unless it were GPL3, which does guarantee you that right.)

      --
      -- Ed Avis ed@membled.com
    25. Re:Embrace. by Anonymous Coward · · Score: 0

      Yes, this is often a problem with GPL freeriders.
      They tell you hey, the code is free, but when you ask if they can give it back in the original license, they say, oh, but Microsoft doesn't contribute back either.
      That's not the point, or rather yes. Do you feel fuzzy inside because you finally were equal to Windows in regards to something? Congratulations.

      They didn't choose FreeBSD because:
      1- Probably doesn't support the hardware
      2- It is unfree with GPL, Sun and binary blob code, and who knows what other weird shit.

      This doesn't mean NetBSD isn't going to die soon.

    26. Re:Embrace. by Renegade88 · · Score: 3, Informative

      Why should you have access to the playground? You still have your shovel. Nobody took that from you.

      Straight up, anybody that declares a BSD-licensed project to be "less free" than a GPL-licenses project is either intellectually dishonest, confused, or an imbecile. (I apologize in advance if anybody falls into category 1 or 3)

    27. Re:Embrace. by Anonymous Coward · · Score: 1, Interesting

      The problem is not that the code is used and locked away from the original developers. The problem is how the GPL crowd is acting to those original developers. The major problems are:

      - GPL fanatics always talk about slavery and morality and stuff, but act just like those they pretend to oppose.

      - Often enough the companies contribute to BSD projects because they know it is cheaper for them to do that instead of constant merging. The GNU just wants to own it all because it is their moral obligation.

      - The misconception of most GPL developers that you can do anything to BSD licensed code, including releasing it under the GPL license. That is not true, you are not allowed to replace the license. You are allowed to release the combined work under any license you want, but if you release the source the original code still must be BSD licensed.

      So in general the problem is that the loud GPL crowd is seen as fundamentalists by the BSD crowd. And we don't like fundamentalists. Sometimes it feels like they only add GPL code to BSD projects because they want to prove their point, making time and effort for everyone higher without any real benefit other than stimulating their egos.

    28. Re:Embrace. by Anonymous Coward · · Score: 0

      Dear Lord, thank you. A post on Slashdot that mirrors the easily understandable fact that BSD licensed code is, in fact, free.

      The Microsoft EULA on that BSD licensed code disagrees with you.

    29. Re:Embrace. by Anonymous Coward · · Score: 0

      You consider "freedom" to be the ability to force other people to release their own code under terms you find favorable?

      As nobody is 'forced' to use other people's GPL code (which they have freely chosen to license in this way) in their product, no-one is 'forced' to release their own code.

      Surely it's quite simple? A person writes some code. They freely chose to license it as BSD, GPL, whatever. Another person freely chooses to use their code and and so freely chooses to accept any license that may come with it.

    30. Re:Embrace. by Anonymous Coward · · Score: 0

      The only problem is ethical not legal. If MS contributed back the code it would be finer. But now it is fine-legal. NetBSD needs more hands and it threw away the opportunity, even the opportunity to create the new Windows8.

    31. Re:Embrace. by Anonymous Coward · · Score: 0

      You are right but not making a point. The original dispute was about "BSD is less free". So GPL is more free because you can choose to not use it? Well, you can do the same with BSD.

      Please point out where BSD License is less free then GPL. And better let it not be the point that you just argued about.

    32. Re:Embrace. by yttrstein · · Score: 2, Insightful

      There's BSD code in every version of windows going back to NT 4.0. BSD developers know this, and that's part of the point. If I may:

      "I don't use *BSD because I hate Microsoft, I use it because I love unix"

      That's the whole of the point. It doesn't matter who uses the code; there's no sense of "being ripped off" in the BSD world. You develop it because you love it, and because you want to make things (all things) work better. Not because you want to kick Microsoft (or anyone else) in the teeth.

    33. Re:Embrace. by Anonymous Coward · · Score: 0

      The developers clearly understood that was a potential outcome when they placed their code under a BSD license. As a result, they probably don't mind

      Not only do they not mind, they planned it that way. That's part of the BSD-style philosophy. It's not like anyone can "steal" BSD code -- once it's out there, it's out there forever.

    34. Re:Embrace. by Anonymous Coward · · Score: 0

      I personally prefer the BSD license because I rate voluntary contribution higher than enforced code exchange.

      But you are the kind of person I would not argue with. You have your preference, I have mine, and we happen to disagree. And that is fine, because you don't argue that everyones elses opinion is inferior, unethical or imoral.

    35. Re:Embrace. by domatic · · Score: 1

      Why should you have access to the playground? You still have your shovel. Nobody took that from you.

      You should if that was a condition for loaning the shovel. Using the shovel anyway then complaining about the GPL kids "forcing" you is lame especially since one can borrow the BSD shovel.

      If you want to argue that the GPL imposes more conditions than the BSD license then I'll agree with you though I'd just as soon stay away from semantic games around the word "free". I do find both licenses fair and will happily use software licensed under either.

    36. Re:Embrace. by Svartalf · · Score: 3, Interesting

      Actually, for the longest time, MS was going to move the Sidekick over to WinCE- they were even gearing up for it. Unfortunately, after many months of this (A year ago, in reality...), they have announced that they're doing it with a *BSD core and they're HIRING *BSD devs for it.

      If you're doing what you're claiming, you don't spend 12 months doing it that way and then gear up for the other OS that you don't sell...doesn't look good to investors to spend 225 billion or so on someone to do something like this. ;-)

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    37. Re:Embrace. by icebraining · · Score: 1

      BSD code license is truly free, but GPL makes other code free as well. They are saying "if you don't want to give your users the freedom we think they deserve, you shouldn't use other people work to gain profit".

    38. Re:Embrace. by icebraining · · Score: 1

      GPL doesn't force anyone to give away their source code. If you don't want to give your code, well, maybe you should code it yourself instead of using other people's code.

    39. Re:Embrace. by icebraining · · Score: 1

      This deserves 5, Insightful. No biased view, just a good explanation.

    40. Re:Embrace. by icebraining · · Score: 1

      Entity A makes open source code, using BSD license. Entity B makes a close product based on that code. I, as a consumer of that product, don't have the freedom to adjust B's code to my needs as I would have if the original code was GPL.
      On the other hand, Entity B is more free than if the code was GPL.

      The question is, what freedom is more important? Anyone would codes should choose on their own. No need to argue about which is better.

    41. Re:Embrace. by jc42 · · Score: 1

      No. Code cannot be free. Only people can be free.

      No, lots of other things can be free. I have several gigabytes of free space on this machine's disk. That doesn't mean that you can use it. And my saying that you can't use it doesn't mean that it isn't "free" in the sense that anyone would have understood when they read my second sentence.

      As someone said a few messages higher on my screen, "As though 'Free' didn't have enough definitions already." The English language has some serious bugs, and one of them that keeps biting us is that the word "free" has several radically different meanings. Those meanings have a small common core, true, but it can take a bit of etymological digging to extract that core meaning.

      The word "free" is routinely applied to physical objects. Ask your local marketing people about how they use the word. They like to advertise things as "free" when you have to pay money to get them.

      So no, you don't have the right (or even the ability) to restrict the meaning an English word to a single meaning that you like. Nobody else will honor your restricted definition. They'll just continue to (mis)use the word in all the different senses that they've learned. Yes, this does cause (mis)communication problems. That's what happens when you use a human-generated language. They're all sloppy, inconsistent, and self-contradictory. There's not much you or I can do about it (except maybe to rant a bit). Lots of people have suggested that we replace one meaning of "free" with a word like "gratis", as other languages have done. So far, such suggestions have failed totally.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    42. Re:Embrace. by larry+bagina · · Score: 2, Insightful

      Linux is GPL licensed. But you're not free to compile your own version to run on a tivo.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    43. Re:Embrace. by Bill_the_Engineer · · Score: 1

      The BSD license gives freedom to the developer; the GNU license gives freedom to the code itself.

      As far as I know, Code has no free will. Therefore, code can not experience freedom.

      Hyperbole aside, You can think of GPL as FORCING the developer to participate in a community process and BSD as INVITING the developer to participate in a community process. BTW, It is my understanding that FreeBSD (and the other BSD) actually do get contributions back from some of the corporations that use their code.

      Anyhow, I agree with the GP that there are some redefining of the word 'free' being done. In fact, I believe when people try to attribute freedom to a piece of code they really mean public and use freedom to invoke some emotion.

      For example, your quote:

      ...with BSD, you can take code from the community, do work on top of theirs, and keep it for yourself. In a sense, you can take free code and turn it into non-free code. With GNU, you can take code from the community, and do work on top of theirs; then, you are obliged to share back. The code was free, the code stays free...

      Make more sense as:

      with BSD, you can take code from the community, do work on top of theirs, and keep it for yourself. In a sense, you can take public code and turn it into private code. With GNU, you can take code from the community, and do work on top of theirs; then, you are obliged to share back. The code was public, the code stays public.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    44. Re:Embrace. by Bert64 · · Score: 2, Insightful

      If you give people too much freedom, then they will use that freedom to take yours away...

      If you let people run wild with no rules, then the strongest will become dictators and everyone else will be subjugated or killed.

      BSD gives people too much freedom, because they can now take the free bsd code and close it up...
      GPL ensures that the code will remain at a constant level of freedom.

      Society is the same, we are not free to go around killing people or forcing others to be our slaves, we sacrifice some of this freedom to ensure that everyone gets the same slightly reduced level of freedom.

      Complete freedom only benefits the very few who can take advantage of the system at the expense of the rest.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    45. Re:Embrace. by TheRaven64 · · Score: 3, Insightful

      BSD code license is truly free, but GPL makes other code free as well

      That's good. So, I can download the GoogleFS code that is linked into Linux? Oh, they don't distribute it? I guess I can't then.

      More often recently the GPL has made other code not exist rather than be free. Take a look at the huge (BSDL) contributions Apple has made to LLVM, for example, because GCC GPL'd and so they can't use it for syntax highlighting in XCode.

      --
      I am TheRaven on Soylent News
    46. Re:Embrace. by Anonymous Coward · · Score: 0

      I don't think you get it. You consider "freedom" to be the ability to force other people to release their own code under terms you find favorable? Wow, dude. That's awesome.

      Well, it's pretty clear that you don't get it. If the code they picked up wasn't written by them then it isn't their code. If they picked up the code accepting the terms of the license then they are not forced to do anything at all.

      And while we are at it, picking someone else's code and trying to pass it off as it's own is not awesome, nor is it awesome to force out every single user out there to not touch the code that isn't theirs to begin with.

      You're still free to download any BSD distribution you like, in its entirety, and do whatever you please with it.

      Including running it in that particular device? I don't believe it's possible.

    47. Re:Embrace. by Anonymous Coward · · Score: 0

      And the product of entity A less free because you can't modify the product of entity B which happens to be based on the former one?

      That doesn't sound silly to you? In 100 years your copyright will mean nothing. You will be dead and your copyright will have vanished (hopefully). Everyone could create non-free software with your code.

      Does unlimited copyright duration make your code more free?

    48. Re:Embrace. by Hatta · · Score: 1

      Not only do they not mind, they planned it that way.

      Unless they're Theo de Raat.

      --
      Give me Classic Slashdot or give me death!
    49. Re:Embrace. by tedu_again · · Score: 1

      Except that's not BSD licensed code.

    50. Re:Embrace. by gad_zuki! · · Score: 1

      Yep, this is exactly what they did with hotmail. They bought it and ran the BSD servers for years. Eventually they switched to Win2k. If its cost-effective to stay with the old setup, then they will stay with the old setup. When its time for a major rewrite they'll just migrate to MS tools.

    51. Re:Embrace. by Binestar · · Score: 1

      Linux is GPL licensed. But you're not free to compile your own version to run on a tivo.

      Sure you can, the TiVo just isn't obligated to run it. Sucks, but there you go.

      --
      Do you Gentoo!?
    52. Re:Embrace. by Anonymous Coward · · Score: 0

      GPL gives the freedom to the original developers, BSD gives the freedom to the final developers.

    53. Re:Embrace. by DrgnDancer · · Score: 1

      Ok, I use lots of GPL software, and almost no BSD software (at least not explicitly, there's a fair amount of BSD code in OS X I realize), so I'm hardly a Zealot of the BSD cause, but:

      "The BSD license gives freedom to the developer; the GNU license gives freedom to the code itself."

      I've seen this sentiment before and I don't get it. Developers are people, hence they can have, use, and value freedom. Code is an object. It's not even a physical object. It's a collection of bits ordered in such a way as to (hopefully) do something in a computer's logic system. Who cares if it has freedom? I've heard that the GPL protects the end user's freedom, and that makes some sense (Not so much that I plan to run out and join the FSF, but some sense), but the CODE'S freedom? I'm more interested in the rights of Central Park pigeons than in the rights of a piece of code. At least the pigeons are sentient.

      --
      I don't need a million points of light, just two points of multi-mode fiber and a 10 Gig-E router.
    54. Re:Embrace. by ion.simon.c · · Score: 1

      because GCC GPL'd and so they can't use it for syntax highlighting in XCode.

      Rubbish. Apple can create a GCC-based syntax highlighter that communicates with XCode through sockets. Licensing problem solved.

    55. Re:Embrace. by Anonymous Coward · · Score: 0

      The thing is, nobody forces anybody else to incorporate or use GPL code, there is no forcing. If you don't want to participate, then don't use it. What's so hard about that?

      It all stems from developers wanting to reuse code without consideration to the original authors. You are either okay with that or you're not.

    56. Re:Embrace. by drinkypoo · · Score: 1

      More often recently the GPL has made other code not exist rather than be free. Take a look at the huge (BSDL) contributions Apple has made to LLVM, for example, because GCC GPL'd and so they can't use it for syntax highlighting in XCode.

      "Young man, it appears you still don't understand."

      All Apple has to do is GPL Xcode.

      They give it away for free, so it's not clear what they would be losing.

      If they don't want to do this, then they don't need to have syntax highlighting with GCC. (And you should know damned well that this doesn't prevent them. They would have to use another method.)

      I'm not sure why you think that it's better for corporations to be able to profit from someone's work without giving back, but that's up to the authors anyway. People who actually create things and genuinely give back have overwhelmingly voted for a model in which someone else can't just grab your code and run.

      Apple can either do the work themselves, or give back to the community. The only reason to keep Xcode closed is to prevent it from being run places other than OSX. It's the Citadel and the Bazaar all over again.

      Are you an anti-GPL zealot, or an Apple fanboy?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    57. Re:Embrace. by poot_rootbeer · · Score: 1

      If you use my shovel to build your playground, you damn better let me play too.

      Oh wow. This is one of the worst free software metaphors I've seen in a long time.

      BSD: A man puts a shovel out by the curb with a note that says 'free'. His neighbor comes along and takes the shovel, uses it to build a playground. The first man has no claim on the playground.

      GPL: A man offers to let his neighbor use his shovel, as long as certain conditions are met. If the playground is open to the public, the neighbor has to put up a sign that says "Built with Joe's Shovel", and offer copies of the blueprints and loan out the shovel to anybody who requests them. If the playground is private, it would be nice of the neighbor to share his work with everyone else, especially the shovel owner, but he is under no obligation to.

      Even then, the distinction between tools and building materials is poorly made, but let's save that for the GPL vs. LGPL flamewar taking place over in another thread.

    58. Re:Embrace. by Anonymous Coward · · Score: 1, Interesting

      Rubbish. Apple can create a GCC-based syntax highlighter that communicates with XCode through sockets. Licensing problem solved.

      Actually, linking two programs via sockets is a legal gray area with the GPL, and I'm not sure it's even allowed in GPL 3.0.

      Note that this wouldn't apply to a Internet-based server communicating via open standards, where any conforming client could connect, but it would apply to two programs coupled together so tightly that they can't operate without each other, in which case the socket is considered linking, and thus the GPL applies.

    59. Re:Embrace. by Wordsmith · · Score: 1

      Who says that's "trouble?" That's exactly what those who release their code uder the BSD license choose to allow. The BSD code is wholly free. Its derivatives may or may not be. There's no stealing/pilfering going on -- those making the derivatives have permission to close off their versions of the work.

    60. Re:Embrace. by TheRaven64 · · Score: 4, Informative

      I'm not sure why you think that it's better for corporations to be able to profit from someone's work without giving back, but that's up to the authors anyway

      Who said anything about not giving back? Apple have made a lot of improvements to GCC and to a number of other projects, including several BSDL ones where they were not required to release their changes. They have released a number of new projects under permissive licenses, such as Launchd and the clang front end to LLVM.

      People who actually create things and genuinely give back have overwhelmingly voted for a model in which someone else can't just grab your code and run.

      Did they? Most of the code on my system is not GPL'd. A fair bit is LGPL'd, but huge amounts are under BSD, Apache, and similar licenses. This includes a lot of well-known projects, like *BSD, Perl, LLVM, subversion, PostgreSQL, Lighttpd (or Apache, if you prefer), Squeak, X.org, and so on. The only bits of GPL'd software I use regularly are bash, gcc, and vim. Of these, gcc is slowly being replaced by llvm/clang and the others are hardly the 'overwhelming' majority of the code I run.

      According to Ohloh.net, I have released around 150,000 lines of code, putting me well into the top 2000 open source developers, and all of this has been under BSD-style licenses. I wonder where you are on this list.

      Are you an anti-GPL zealot, or an Apple fanboy?

      No, I'm a pragmatist. I want contributions from companies and from individuals. I'm more interested in the contributions companies do make than they don't. If Apple, Sun, IBM, or Google releases something under an open license, I prefer to count this as a positive, rather than count the number of lines of code in products they didn't release. I look at gcc and llvm/clang (which, by the way, I've contributed a fair bit of code to that isn't counted by Ohloh since I don't have commit access there) and I see a lot of the companies that used to contribute code to gcc are now backing llvm because of the license.

      When Apple released a new ARM back end for LLVM to use as the iPhone compiler, I chose to be happy that LLVM had been improved, rather than complain that the iPhone was not open. I can choose not to buy an iPhone because it is not open (and did) and still benefit from the improvements in LLVM for other ARM-based devices I own.

      The same is true of a lot of corporate contributions. When Yahoo! releases improvements to FreeBSD, I am happy that the operating system on my ThinkPad gets better, I don't complain that they didn't also open source their search engine.

      In the modern world of interconnected systems, the GPL's distinction between what code you do need to release and what you don't is quite arbitrary.

      --
      I am TheRaven on Soylent News
    61. Re:Embrace. by sjames · · Score: 1

      There is absolutely nothing wrong with MS choosing to use BSD code. It's explicitly permitted.

      It is, however, interesting in that it demonstrates just how much of their FUD they really believe. That is, A is bad unless we get to use A for free, then it's good. But it';s still bad if you get to use it for free, so pay us for B. Please ignore the A behind the curtain.

    62. Re:Embrace. by vux984 · · Score: 2, Insightful

      Who says that's "trouble?"

      Anyone who discovers that the product they are using and need to bug fix or update is 99% BSD code, and yet they have zero freedom, because BSD didn't extend freedom downstream, so while the original authors said the code was free, and some developers along the way got some of that goodness, by the time the end users got it the freedom was gone.

      Look, I get it, this is the point of the BSD, and nobody did anything 'wrong' in the above scenario. But that's what the criticism with the BSD is: while it starts out free, it doesn't necessarily stay free, and that's its drawback.

      With BSD often the best version of a product isn't BSD. Or it can happen that the original BSD code has been abandoned and has become obsolete, while its surviving offspring are awesome... but no longer free. That is the drawback with BSD.

      GPL conversely does preserve that freedom, so the best derivative is as free as the original. That's not to say the GPL doesn't have drawbacks to it, it can't be mixed with code from incompatible licenses - of which there are several.

      It also dictates that the derivate work must continue to be under the GPL. That's not really a drawback though, just a limitation. Its a drawback in the sense that it limits the author of the derivative work, but at the same time is its strength because it ensures the user of that derivative work has freedom, so that limitation is precisely its reason for being.

      Between the two I prefer GPL, because I buy into the idea of preserving freedom downstream, but neither license is perfect.

    63. Re:Embrace. by harry666t · · Score: 1

      > No one can reasonably argue that BSD-licensed code isn't truly free.

      I wouldn't like to start another holy war, but my POV is that it's MIT/BSD that is "more free" (AFAIK you can even relicense your derived work under L?GPL), while the GPL family is "less free", but takes away some of the freedom in order to protect the rest of it.

      I think the choice of license depends on what you're licensing. If you're afraid of competition taking away and closing your code, go GPL/LGPL. If you're afraid of competition building proprietary extensions, use GPL. If you're hacking up a small and convenient library or Python module or alike, it'd be cool to release it under BSD, just so that the text of the license isn't longer than the source code itself. Hell, you can even build a proprietary app, and/or reuse some BSD licensed stuff. I prefer GPL2+ personally, but use whatever seems to be the best (most convenient) choice for a given piece of code. Hell, as I think of it, I wouldn't mind releasing a big project under the BSD. What could possibly go wrong. If some downstream #@$% (I mean, developer) chooses to fork and close the source, let it be his own problem to maintain it.

    64. Re:Embrace. by sjames · · Score: 1

      It's a question of WHOSE freedom. BSD maximizes the freedom of the first person to download and use the code. GPL maximizes the freedom of the next guy who wants to use the derived work. It's just that simple.

      Which is best is a matter of personal taste and anyone is free to make that choice for their own software.

    65. Re:Embrace. by Anonymous Coward · · Score: 0

      If the original developers chose to license their code under the BSD license, I don't think they mind. The GPL fanatics, on the other hand, seem to get butthurt that the developers don't seem to mind. GPL fanatics demand everyone buys into their groupthink or else.

    66. Re:Embrace. by rbanffy · · Score: 1

      "BSD licensed code is, in fact, free."

      It's just that it doesn't remain so for long ;-)

    67. Re:Embrace. by Anonymous Coward · · Score: 0

      "Actually, BSD and GPL give exactly the same rights to the developers who get the licensed code. However, the GPL restricts the rights of distributors . . ."

      Not really.

      Absent an EULA that is upheld by the courts, if you're not copying / distributing, then doctrine of first sale should allow you to do whatever you want with the code, including running, modifying, marking up comments in the margins, etc.

    68. Re:Embrace. by Anonymous Coward · · Score: 0

      It remains so forever. Once the license is granted not even the copyright owner can say "Just kidding, you actually don't have any permissions anymore."

      Please stop spreading this FUD. I wished people would stay honest with that. What you mean is "But the code others write could be non-free.".

    69. Re:Embrace. by ion.simon.c · · Score: 1

      You can speak HTTP over a UNIX socket just as easily as you can over a network socket.

      WRT Licensing:
      http://www.gnu.org/licenses/gpl-faq.html#MereAggregation

      "By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program."

      It would seem that GPLv3 doesn't change the landscape for this sort of thing. Also, I would wonder if publishing your communication protocol (maybe along with a liberally licensed, actively maintained client and server) would cause the FSF to look more favourably at your closed-source app.

      Regardless. Wouldn't Apple be using GCC to merely generate an AST of some source code? I can't possibly see how *that* would qualify as a complex internal data structure. :)

    70. Re:Embrace. by snaz555 · · Score: 1

      This is actually one of the things I admire about developers in a position to release their code under BSD licenses. The end user is free to do anything they please with the code, including rolling it into a proprietary product, as long as they follow the attribution requirements. As for myself, most of my public code is licensed under the GPL, for various reasons (some being financially related). No one can reasonably argue that BSD-licensed code isn't truly free.

      I couldn't agree more. For something of limited commercial value I'll GPL it. That way others can enhance and work on it, and it might bring some value back to me. Or it might give it sufficient exposure to permit a separate commercial license of a private branch; one with only my parts in it. Or it might bring in consulting work - lots of good reasons. If I release it under the BSD license I'm much less likely to benefit financially; it might end up used more, but I'm not convinced it will bring a corresponding bump in contract work. I take pride in crafting good software, and the better it's designed the easier it is for a more junior developer to pick it up and run with it, and this works against a BSD license but for a GPL-with-commercial-on-the-side setup. Of course, in the other direction I love the BSD license and public domain since I can use those for product work. But so can anyone else, so the value add is the value of my enhancements. For trivial changes I'll just submit it for consideration by the maintainers, but often it's such a specialized one-off that they're not interested. The big value is in not having to roll the same basic infrastructure and plumbing stuff from scratch - usually pretty easy stuff but tedious and time consuming to retype and get right. Again. Like say sha1 - just grab the public domain Reid version.

      I don't consider the GPL as free as BSD for my own code - that's why I use it!

    71. Re:Embrace. by snaz555 · · Score: 1

      The real test will be whether the next iteration of this hardware runs this same OS or whether it comes with WinMo/WinCE.

      Note to interested applicants: dead-end job. You will soon become a legacy department. You. Alone. Ask yourself what a single product iteration with NetBSD will do for your resume - very little!

      Do yourself a favor and find an embedded Linux job instead...

    72. Re:Embrace. by snaz555 · · Score: 1

      Is there a problem with Microsoft using BSD code in their proprietary products?

      No! Especially if they use BSD networking components - because that will mean their stuff will work well enough while staying compatible with the rest of the world. We all know what happens when MS goes off to invent a "better" way...

    73. Re:Embrace. by Stormwatch · · Score: 1

      Okay, the shovel thing was a bit simplistic. I guess it's more like this:

      I have these blueprints for a nice, complete playground. You come to me and ask, can I borrow your blueprints to build my playground? Sure, here ya go.

      Now, after you're done, I see you did not follow the plans strictly: you added a cool new toy. I ask, can I borrow the blueprint for new toy? And you just say no.

    74. Re:Embrace. by ivan256 · · Score: 1

      I posting mostly just to concur with what you've said.

      For the past 10 years, I've been a professional open-source software developer. For the first half of my career, I did a lot of GPL work (buzzword compliance always outweighs legal concerns). Now, however, most companies avoid GPL projects like the plague and stick with BSD-like licenses. If a BSD licensed project solves a problem, companies will use it, enhance it, and re-contribute code upstream (to reduce maintenance costs, usually). Their developers participate extensively in developer communities, etc.. If a GPL project is the only existing code that solves the problem, they're most likely to start from scratch and keep the code closed.

      The GPL is seen to be a liability. If you use GPLd components, you must GPL your product or use elaborate, inefficient, and as you say, arbitrary techniques to keep the code separate. That's a huge disadvantage to a commercial development company. As it turns out, it's a huge disadvantage to the prospective GPL'd projects that would have otherwise been used too. Those projects typically wouldn't really be interested in the business logic of some commercial product anyway, and have lost out on well-financed developer backing.

    75. Re:Embrace. by Anonymous Coward · · Score: 0

      TCP stack? How does MS "leverage" an open protocol standard that emerged as the de facto protocol for the Internet?

    76. Re:Embrace. by rbanffy · · Score: 1

      I am quite sure the BSD code in Microsoft FTP.EXE program is not exactly free anymore.

    77. Re:Embrace. by Raenex · · Score: 1

      If you let people run wild with no rules, then the strongest will become dictators and everyone else will be subjugated or killed.

      You're comparing killing somebody vs not giving them source code.

      we sacrifice some of this freedom to ensure that everyone gets the same slightly reduced level of freedom

      I'll pass on sacrificing my freedom for Stallman's ideals.

    78. Re:Embrace. by Bill_the_Engineer · · Score: 1

      The thing is, nobody forces anybody else to incorporate or use GPL code, there is no forcing. If you don't want to participate, then don't use it. What's so hard about that?

      The fact that no one is being forced to use GPL isn't a factor. I was discussing the use of the word freedom as a synonym for publicly accessable source code.

      Personally, I'm okay with the GPL. But I have to point out that the "no one is forcing you..." tact has the same effectiveness as "No one held a gun to your head and made you use Windows."

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  5. Just in time! by fahrbot-bot · · Score: 3, Funny

    My NetBSD toaster was lonely. Getting him a friend will be nice.

    --
    It must have been something you assimilated. . . .
    1. Re:Just in time! by palegray.net · · Score: 1

      I am in awe of your culinary browning device. My sonic toothbrush years for the day its pulses may be measured in megahertz.

  6. In other news by MichaelSmith · · Score: 5, Funny
    • The Secret Service hires Pakistani dudes to guard the president.
    • Boeing outsources all aircraft construction to Toulouse.
    1. Re:In other news by cerberusss · · Score: 1

      • Boeing outsources all aircraft construction to Toulouse.

      Yes I know this country. It's next to the country of Amsterdam, yeah? :D

      --
      8 of 13 people found this answer helpful. Did you?
    2. Re:In other news by Anonymous Coward · · Score: 0

      • Boeing outsources all aircraft construction to Toulouse.

      Yes I know this country. It's next to the country of Amsterdam, yeah? :D

      At least they've got nothing Tolouse.

    3. Re:In other news by MichaelSmith · · Score: 1

      If you outsource it to France the work will be done in Toulouse.

    4. Re:In other news by cicuz · · Score: 1

      movie at 11

  7. Try try again. by LostCluster · · Score: 2, Insightful

    This reminds me of the Hotmail Unix to Windows conversion a few years back. They failed the first time. But eventually got it right.

    1. Re:Try try again. by Bert64 · · Score: 1

      "right" is doubtful, "working" is more accurate...
      they spent a lot of time on the conversion, had to use considerably more hardware to achieve a similar level of performance, and the leaked internal report indicated that from a financial and technical perspective it wasn't a viable move, even considering they didn't pay for any of the software and had the highest levels of support also available for free... the conversion was entirely politically driven.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    2. Re:Try try again. by TheRaven64 · · Score: 3, Funny

      But eventually got it right.

      No they didn't, they made it run on Windows.

      --
      I am TheRaven on Soylent News
    3. Re:Try try again. by Anonymous Coward · · Score: 0

      I'd say they never "got it right", but I guess that's depends on POV.

  8. Even better... by bofh29a · · Score: 3, Interesting

    Microsoft's own Exchange servers have Postfix on their spam filtering boxen front-end. Not exactly eating their own dog food, when they have their own Forefront Security for Exchange.

    This is the Postfix program at host mailxxx-xxx-R.bigfish.com.
    I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

    For further assistance, please send mail to

    If you do so, please include this problem report. You can delete your own text from the attached returned message.

    The Postfix program

    : host xxxxx-xxxx-mail5.customer.frontbridge.com[131.107.115.214] said: 550 5.7.1

    $whois frontbridge.com,

    Domain Name: FRONTBRIDGE.COM Registrar of Record: Corporate Domains, Inc. Administrative Contact: Microsoft Corporation Domain Administrator One Microsoft Way Redmond, WA 98052 US domains@microsoft.com +1.4258828080 Fax: +1.4259367329

    $whois bigfish.com ,
    Domain Name: BIGFISH.COM Registrar of Record: Corporate Domains, Inc. Administrative Contact: Microsoft Corporation Domain Administrator One Microsoft Way Redmond, WA 98052 US domains@microsoft.com +1.4258828080 Fax: +1.4259367329

    1. Re:Even better... by MichaelSmith · · Score: 1

      Its like for version control they use perforce, while MSFT fans are stuck using visual source safe.

    2. Re:Even better... by Hal_Porter · · Score: 1

      Its like for version control they use perforce, while MSFT fans are stuck using visual source safe.

      Outside of one tiny (and fucked) company I had the misfortune of working at, I've never seen anyone use Visual SourceSafe.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    3. Re:Even better... by MichaelSmith · · Score: 1

      Its like for version control they use perforce, while MSFT fans are stuck using visual source safe.

      Outside of one tiny (and fucked) company I had the misfortune of working at, I've never seen anyone use Visual SourceSafe.

      Our Indian contractor apparently uses it as their standard source control tool.

    4. Re:Even better... by Hal_Porter · · Score: 2, Interesting

      I once worked with an Indian consultancy company. They were working on software for a mobile phone and were using ClearCase. Now ClearCase is expensive, but it does the job. A colleague and I were writing code to test the peripherals on the baseband chips. Now one of the Indian managers said that the project was stalled because the I2S controller didn't support some mode.

      Since we had code that tested the I2S controller, we were drafted in to help them. We asked for a config spec. It looked like this

      foo.c@\main\1212
      bar.c@\main\1254

      and so on, for thousands of files. Even worse if you emailed a few different people, you'd get slightly different config specs, but always of this form

      Now normally in Clearcase you develop on a branch and then merge to a release branch. So the development config spec will be something like this

      element * CHECKEDOUT
      element * .../developers_branch/LATEST
      element -file * RELEASE_LABEL_1 -mkbranch developers_branch

      What this means is take the checked out file if if exists, otherwise look for the one on my branch, otherwise look for the released version

      and a release one will be like this. Once you're done developing you merge your branch back and label the result with a new release label. Then the config spec looks like this.

      element -file * RELEASED_LABEL_2 -nocheckout

      Of course for this to happen you need to have a management structure that makes sure people get things right before they merge them back, and if two teams of people are fighting that things get resolved. Otherwise you end up with a minority report situation where different bits of the team end up working on different baselines.

      The worst case of this would be where everyone picked a set of last known good versions that were different. Which is exactly the situation these guys were in.

      Now you can see that the spec they sent us showed that something was very wrong.

      We managed to get it to build but some things didn't work, actually the things we wanted to check. So we asked them and they said something like "ask Raj, he's go a fix for that". The fix was one file, which he emailed you. You checked the file out and overwrote it with the one in the email.

      At this point, it was clear that the I2S settings were totally wrong. We fixed those and managed to punt the whole thing back. Given the chaos the project was in, I didn't really expect it to ever work properly.

      It was the most amazing misuse of a version control system I have ever seen. What was odd about it was the individual developers seemed to me to be ok, the problem was the shitty consultancy company was loading them down with work without setting up things like version control properly. Actually I always suspected that the project we saw had been put together in a few hours by some very smart people, who had then billed my client for a shitload of hours which hadn't been worked. Then after that they handed over the whole mess to some much less experienced developers who were basically too timid to realise that they needed to do a drastic set of module tests, merges, system tests, bug fixes and so on until they had a stable baseline to work from, because the alternative would be that the project would crash and burn.

      Still I'd never trust one of those big Indian outsourcing companies to do software after that. And as I said, it's a problem of the company, not the developers. With one decent manager, the project I saw would probably have not got to this dire state. Actually with one decent manager they could probably have pulled themselves back from the brink given a month or so.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    5. Re:Even better... by MichaelSmith · · Score: 1

      Thank you for your informative and scary message. My company is currently migrating from cvs to clearcase, and from inhouse development to partly outsourced to india. ClearCase multi site will be used to integrate with the contractor.

      I pushed a DSCM solution (mercurial, git, bitkeeper) but I couldn't get people to listen and now I am out of that job.

      I don't plan to be around to see it work (or not as the case may be).

    6. Re:Even better... by Tellarin · · Score: 1

      I used to work in an environment using ClearCase in multi site (7); including sites in the US, India, Brazil, and Russia. Everything worked fine.

      ClearCase is a monster and not my preferential choice for lots of scenarios, but it does the job fine. The problem the GP was talking about is purely configuration management not being done at all.

    7. Re:Even better... by Hal_Porter · · Score: 1

      I think in a well managed company Clearcase is brilliant. You can have people working all around the world, dropping code onto branches to be merged later. Unfortunately very few companies are well managed like this. Maybe you can get people at one site working in a structured way, but you most likely can't get two sites to do it without the whole thing turning into chaos and blamemongering.

      In a very real sense Clearcase is more scalable than most management techniques. I like the merge tool though, it beats the pants off things like cvs. And config specs, automerges the like allow for all sorts of complicated multi level branching strategies.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    8. Re:Even better... by Tellarin · · Score: 1

      The one thing I miss from ClearCase is config specs. :-/

  9. Re:Go NetBSD! by H3g3m0n · · Score: 0, Redundant

    So submit a patch.

    How many people are going to be developing on non-x86 systems anyway?

    --
    cat /dev/urandom > .sig
  10. Just a minor note by Anonymous Coward · · Score: 0

    Perhaps they did, perhaps they didn't. I know nothing at all about servers but wouldn't it be possible to just put some IIS server between the Linux server and the WWW to make it look like IIS to the outside? Or even configure the Linux+Apache like that directly? Yeah, it's a shame we lost the "Hehe, look at that" because there is no way to prove any of this. However, Netcraft saying they switched over a few years ago doesn't necessarily mean they did... I think.

    1. Re:Just a minor note by Skreems · · Score: 1

      More likely is that it never ran on Linux in the first place. It's pretty common for industrial VIP systems to use Linux under the hood while the back-end systems run something completely different. For example, check Netcraft's entries for Live Search. It claims that's running Linux to this day, which I know for a fact is not true.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    2. Re:Just a minor note by Mikeytsi · · Score: 1

      It ran on Solaris, not Linux. It is Windows Server end-to-end now.

      --
      I've been called a "Fucking Dick" by better people than you.
    3. Re:Just a minor note by unleashedgamers · · Score: 1

      Last I knew (couple months ago) they used F5 BIG-IP. F5 BIG-IP runs a variant of Linux, although F5 BIG-IP did used to use NetBSD back around '04 (When it was clamed that Microsoft used NetBSD).

      I'm positive they run IIS 6.0 in emulation.

    4. Re:Just a minor note by Mikeytsi · · Score: 2, Insightful

      No, you don't know what the hell you're talking about. The F5 BigIP does load-balancing and traffic management, it's not used for content delivery.

      --
      I've been called a "Fucking Dick" by better people than you.
    5. Re:Just a minor note by unleashedgamers · · Score: 0

      They also provide powerful suite of storage management with data migration, storage tiering, data replication, and storage load balancing.

    6. Re:Just a minor note by Mikeytsi · · Score: 2, Insightful

      Which isn't what the BigIP does. F5 is a company, BigIP is a hardware load-balancing and traffic-management system. I've seen 'em, I know what they do.

      --
      I've been called a "Fucking Dick" by better people than you.
    7. Re:Just a minor note by unleashedgamers · · Score: 1

      Well... I need a mod down... Somehow I was brilliant enough to mix up the ARX and BIG IP

      GG me...

    8. Re:Just a minor note by Mikeytsi · · Score: 1

      No worries, we all get stuff mixed up from time to time.

      --
      I've been called a "Fucking Dick" by better people than you.
    9. Re:Just a minor note by 0xygen · · Score: 2, Interesting

      It's actually the other way around - they used to show up in Netcraft as Linux servers even though they were IIS on Windows Server 2003 for a long time.

      This is because the server version reported was actually Akamai's balancing and caching infrastructure in front of the Hotmail servers.

    10. Re:Just a minor note by Anonymous Coward · · Score: 0

      would be really cool though if they STILL have to run FreeBSD load-balancers :)
      Once upon a time all of hotmail ran under FreeBSD and for some years after the aquire Microsoft tried to switch everything over to their platform but failed for long in the loadbalancers ... never heard about a final switch, so it would be awesome in a way (at least for a FreeBSD fan) that they still have to keep those :)

    11. Re:Just a minor note by hattig · · Score: 1

      What? "No worries"? No, he was wrong! That means GEEK PUNISHMENT.

      *gets the Windows ME powered Pentium 75 box*

    12. Re:Just a minor note by SolitaryMan · · Score: 1

      It claims that's running Linux to this day, which I know for a fact is not true.

      If Netcraft says it, it is true by the very definition of truth!

      --
      May Peace Prevail On Earth
    13. Re:Just a minor note by ArhcAngel · · Score: 1
      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    14. Re:Just a minor note by Iceykitsune · · Score: 1

      Apparently you have never heard of sarcasm.

      --
      GENERATION 24: The first time you see this, copy it into your sig on any forum and add 1 to the generation. Social exper
    15. Re:Just a minor note by Skreems · · Score: 1

      Eh, not really. Microsoft doesn't have a load balancer product. All the commercial ones out there are based on Linux or FreeBSD. Hell, MS uses some front-end caching proxies from commercial services that are really just Linux running Squid under the hood. They're buying very expensive special purpose machines from 3rd party companies, not running *nix "by choice", exactly.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    16. Re:Just a minor note by Dibblah · · Score: 2, Informative
    17. Re:Just a minor note by Skreems · · Score: 1

      Ok, Microsoft doesn't have an enterprise-level load balancer product. :-P

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
  11. They ported Sidekick to NetBSD? by rrohbeck · · Score: 1

    Cool. Somebody tell Borland!

    1. Re:They ported Sidekick to NetBSD? by MichaelSmith · · Score: 1

      Cool. Somebody tell Borland!

      But the calendar only went up to 1999.

  12. So what? Danger will still lock it out. by Chas · · Score: 1

    This is why the developer community for the SK imploded. While there's still a core of hard-core SK developers out there, the majority of them moved on to greener pastures after the whole fiasco with Danger and their multiple personality disorder with regards to developers.

    This, and their shit hardware QC, are why the Sidekick stopped being a real, going concern several years ago.

    --


    Chas - The one, the only.
    THANK GOD!!!
  13. Re:Go NetBSD! by Anonymous Coward · · Score: 0

    Is Android itself x86?

  14. wow! Does this mean that there might be... by rivaldufus · · Score: 5, Informative
    more than one open source operating system out there? Will Slashdot survive? It cracks me up that a bunch of posts talked about how hotmail once ran on "linux" and qmail. Can't even say the name, "FreeBSD."

    Seriously, this isn't surprising... NetBSD runs on everything. The NetBSD team spends a significant amount of time supporting a large number of platforms - be it a modern X86 server or a sun pizza box.
    You'll notice that commercial entities like the BSD license (see: OS X) And, I don't think that the NetBSD developers will suddenly panic: "Someone's going to steal our code!" Contrary to what some here might feel, there is room for more than one open source operating system and, believe it or not, more than one license.
    Back in the old days, slashdot had the BSD link right on the front page.

    1. Re:wow! Does this mean that there might be... by TheRaven64 · · Score: 2, Informative

      The NetBSD team spends a significant amount of time supporting a large number of platforms

      Actually, they don't anymore. What they do spend a lot of time doing is ensuring that there are very clean abstraction layers throughout the kernel so that porting to a new platform can be as little as a weekend's work if the compiler already exists. You need to initialize the CPU and provide MMU functions, which is typically a few hundred lines of code, and write a driver for the bus controller. From then on you can use all of the existing drivers unmodified.

      --
      I am TheRaven on Soylent News
  15. What about the Microsoft Xenix Sale Agreements? by NZheretic · · Score: 3, Interesting

    When Microsoft sold Xenix to the Santa Cruz Operation ( Not the current SCO Group ), wasn't there a Non-compete clause in the agreement? I thought that Microsoft was not allowed to sell any Unix based operating system - and that would include any NetBSD derivative.

    1. Re:What about the Microsoft Xenix Sale Agreements? by Svartalf · · Score: 2, Interesting

      They're not selling the OS. They're selling the phones which use an OS.

      Doesn't breach their non-competes with SCO, sorry.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    2. Re:What about the Microsoft Xenix Sale Agreements? by fm6 · · Score: 1

      Santa Cruz Operation ( Not the current SCO Group )

      Incorporation wise, it's not the same company, but productwise it is. Caldera didn't just buy the name, they bought all the Unix technology. (Yes, they litigate over it instead of developing it, but still.) The original SCO renamed itself Tarantella and abandoned the OS business. Eventually Sun bought them for their "thin client" ("fat terminal" is more accurate) technology.

    3. Re:What about the Microsoft Xenix Sale Agreements? by stefancaunter · · Score: 1

      And didn't Xenix have a lovely networking setup too... MSNet anyone? It is great to see NetBSD being recognized. Small fast slim and powerful, you have to know vi, and put on your own perl. What's not to like?

  16. Not surprising really by Anonymous Coward · · Score: 2, Insightful

    Microsoft have woken up to the fact that the only way to defeat Linux and the GPL is to support the BSD type licensed software.

    What's the problem with that?

    Every system has to have a basic set of rules. That basic set of rules is there to ensure that the system itself will continue to exist.

    So for instance, democracy won't last very long if you allow a simple majority of voters to vote democracy out of existence. The dim witted might say that makes it more democratic to allow it, but the more thoughtful will see that if you allow the voters to put an end to their democratic rights, it actually becomes less democratic - less free.

    We call those basic rules which protect our democratic rights a 'constitution' and the exact nature of the constitution determine exactly how free we will be.

    Hitler was voted into power democratically, and then went to the people again to have them vote him dictatorial powers. Once it's done, it's awfully difficult to get it back. Look what it took to get democracy running again in Germany.

    There is a similar situation with software licences. The GPL has its constitution built in. It says that the software it covers has been produced communally, and that if you wish to redistribute it, you must include the source code and the same license ( i.e. the same freedoms ) which existed with that code when you got hold of it.

    The BSD license does not have such guarantees built in. Anyone can take that code, ignore the communal effort which went into producing it, close source the code and their own additions and benefit off the backs of the work of others.

    The BSD license is not about freedom. It is about encouraging closed source monopolies with some free help, and this is an example of that happening.

    Don't confuse open source with freedom. It'll soon all be gone if you do.

    1. Re:Not surprising really by argent · · Score: 4, Insightful

      Anyone can take that code, ignore the communal effort which went into producing it, close source the code and their own additions and benefit off the backs of the work of others.

      You mean like the way Linus Torvalds did when he used the work that everyone from Thompson and Ritchie to Allman and McKusick had done in designing the system he cloned?

      I'm not criticizing Linus, writing open source code to open systems APIs is a Good Thing. My point is that EVERYTHING we do is done on the back of others.

      And if this is another step in Microsoft's slow and reluctant journey from proprietary APIs back to open ones, that's good too.

    2. Re:Not surprising really by argent · · Score: 1

      I didn't say he took code, I said he built on the work of others, and I CERTAINLY have no objection to him doing so... we both clearly agree that everything we do is built on the work of others, so I'm a little confused as to the source of your obvious anger over such a quotidian truism.

      As for zealots, I think anyone comparing the tone of your comment to mine will have no difficulty deciding which of us suffers from that complaint. :)

    3. Re:Not surprising really by Anonymous Coward · · Score: 0

      Linus closed the source !?!

    4. Re:Not surprising really by Anonymous Coward · · Score: 0

      Oh why yes, you're totally innocent. Just made a totally innocent comment with no negative connotations implied whatsoever.

      Yes, you do look ridiculous trying to stay up there on your high horse. Funny, though.

    5. Re:Not surprising really by Anonymous Coward · · Score: 0

      linus didn't close the source.

    6. Re:Not surprising really by Anonymous Coward · · Score: 0

      Not the same thing, and you know it. The OP is talking about somebody straight taking the code and making it their own. Linus wrote his own, INSPIRED by others. I mean, how literal do you want to get with it. Should we also give props to the guy who discovered fire while we're at it? At the risk of also being classified a zealot, you know damn well Microsoft got some of their early code by shady means.

  17. Hey Microsoft recruiters! Pick me! by martin-boundary · · Score: 2, Funny

    Sidekick? I can totally do this! I still have some old TSR code lying around...

  18. Re:Go NetBSD! by reiisi · · Score: 1

    fedora on ppc? Or ubuntu?

    --
    Computer memory is just fancy paper, CPUs just fancy pens with fancy erasers; the 'net is just a fancy backyard fence.
  19. NinnleBSD! by Anonymous Coward · · Score: 0

    Ninnle Labs already working on the port for this.

  20. Re:vFailzor5?! by pleappleappleap · · Score: 1

    If you're going to try to goatse us, you should at least try to hide the link.

  21. Borland by SgtChaireBourne · · Score: 0, Troll

    It's not like you would be going in to code the next Microsoft Useless Widget 2.0.

    Right. You'll just be porting Microsoft Useless Widget from Windows CE to NetBSD.

    Or, M$ is hoping enough NetBSD developers, or potential developers, are naive or weak enough to turn quisling. NetBSD is small enough that it is comparable in size to small companies, and taking out enough developers to sink the project is a realistic goal.

    It happened to Borland and others. Of the FOSS distros, NetBSD the lowest hanging fruit for such a tactic. Larger distros require other tactics.

    Even if the offer is legit, which it probably, isn't, just wasting invaluable developer resources porting Microsoft Useless Widget from Windows CE to NetBSD is a human resources denial of service attack taking developer time away from something useful.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  22. Locked down platform? by GreatBunzinni · · Score: 3, Insightful

    I find it strange that until now there isn't a single comment on the open-ness of that platform. Yes, it may run a BSD flavour. Nonetheless, is the platform locked down? Is it possible for any end-user to reinstall the OS without the need of circumvention tools and hard hacks?

    That, as I see it, is the single most interesting aspect of this article. After all, if the sidekick platform is locked down then it doesn't really matter it is running a BSD flavour. Moreover, it would once again emphasize the need for the legal constructs added to the GPL in the form of GPLv3.

    So, is it locked down? Can it run linux?

    --
    Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
  23. Well shit by RazzleDazzle · · Score: 1

    Now I don't know if I am supposed to hate Microsoft still. Where are we on the hate-o-meter for MS? Surely this drops the needle down from Blazing Fury of a Million Suns to maybe Mildly Atrocious or American Idol or something. This is so hard to figure out.

    Oh wait does "BSD is dyin" come into play here or not?

    --
    ZERO ZERO ONE ZERO ONE ZERO ONE ONE! Just brushing up for my next big invention: Ethernet over Voice (EoV)
  24. Next big MSFT OS? by kneemoe · · Score: 1

    Could this be their big long-term plan? http://www.informationweek.com/blog/main/archives/2009/01/microsoft_paten_1.html

    Just an idea, Apple basically did this with OS X, only they put it on the desktop first, MSFT will just go in the other direction here

    It's certainly worked for Apple in the last 5+ years.

    --
    My Sig Sucks
  25. NetBSD by udippel · · Score: 0, Troll

    Isn't it ... ? Wasn't it ... ? Wasn't it already ... ?
    Oh no, nevermind!

  26. Patches upstream? by Anonymous Coward · · Score: 0

    could their patches get upstream product of bug fixing? will they sign an NDA?

  27. netcraft confirms by portscan · · Score: 1

    Windows CE is dying

  28. sorry, you're making too much sense by toby · · Score: 2, Insightful

    development was well underway when Danger got bought by MS. That means it was likely cheaper to just continue doing what they were doing rather than scrap the work and start again using Microsoft's stuff.

    Hm, if only it worked that way. But out there in Biznis land that kind of rationality rarely prevails in my experience. The "NIH" and "OMG ITZ NOT MS" factors rank higher than "faster, better, cheaper" (i.e. anything not MS).

    Plus, executives are, often, ah, "incented" to choose the Microsoft solution in the face of any technical or common sense objection. (See: Windows 4 Warships, etc, etc, etc, etc, etc)

    --
    you had me at #!
  29. Relax by toby · · Score: 1

    Microsoft is still evil.

    --
    you had me at #!
  30. 05401 by djdavetrouble · · Score: 1

    Pardon me, but why is the zip code for Burlington, VT a secret troll code?
    Just curious and stuff.

    --
    music lover since 1969
    1. Re:05401 by Facetious · · Score: 2, Funny

      One can only assume a disproportionate number of bridges there.

      --
      Let us not become the evil that we deplore.
  31. Atleast we don't have the BSD is dying guy lurking by johnnnyboy · · Score: 1

    This is great a BSD post on slashdot and no BSD is dying post.
    So It's official BSD in NOT dying netcraft confirms it.

    --
    "If a show of teeth is not enough, bite ... but bite hard!"
  32. But the real question is by Anonymous Coward · · Score: 0

    ... does it run Linux?

  33. Holy fuck by msimm · · Score: 1

    Would you fucking morons ALL get off your high-horses? Freedom is being able to CHOOSE between any fucking license that suites your personal/business/religous/world view. Therefore: BSD == free, GPL == free and it's perfectly OKAY that BSD != GPL. Like one and not the other? Great, shut-up about it and use what you like.

    Personally, I'm a big fan of both. Ifuckingmagine that.

    --
    Quack, quack.
  34. Heh.. by Anonymous Coward · · Score: 0

    I take it back after reading the rest of the posts.

    Linux kids: read more (BSD kids, don't be like them).

  35. zlib by kybred · · Score: 1

    Isn'z zlib LGPL?

    No

  36. wow by Anonymous Coward · · Score: 0

    a post on /. about netbsd and 99% of the comments are about licensing crap instead of an interesting technical discussion... color me surprised...
    aren't ya'll tired of repeating the same stuff over and over again?

  37. WinMo 7 is delayed after all by MobyTurbo · · Score: 1

    Actually, for the longest time, MS was going to move the Sidekick over to WinCE- they were even gearing up for it. Unfortunately, after many months of this (A year ago, in reality...), they have announced that they're doing it with a *BSD core and they're HIRING *BSD devs for it.

    If you're doing what you're claiming, you don't spend 12 months doing it that way and then gear up for the other OS that you don't sell...doesn't look good to investors to spend 225 billion or so on someone to do something like this. ;-)

    That's not all that looks bad for investors. WinMo 7 is coming out in 2010, a year behind schedule, which is an eternity with the Palm Pre coming out in 2009, Android gaining traction, and of course the iPhone and Blackberry all out-selling it with next-generation smartphones that are either iPhone-like or otherwise more stable and powerful devices than WinMo/WinCE.

  38. Sidekick is gone, time to move on... by SgtChaireBourne · · Score: 1

    I feel so torn. On one had here is a chance to be paid to work on netbsd. On the other hand the job is with Microsoft.

    Time to stick a fork in it, it's done. Sidekick is gone and it's time to move on. Sure it could linger on and slowing languish taking a few good developers with it on the decent into obscurity. But face it, it's owned by MS and the official policy is to stomp anything that does not promote lock-in to Windows/Office. Look at the warning example of Foxpro and see what happens to a good product that MS can't compete with on quality but was too popular to shutdown outright.

    Even if the offer is legit, which it probably, isn't, just wasting invaluable developer resources porting Microsoft Useless Widget from Windows CE to NetBSD is a human resources denial of service attack taking developer time away from something useful. An extreme version of that tactic was used against Borland and others. NetBSD is small enough that it is comparable in size to small companies, and taking out enough developers to sink the project is a realistic goal if some NetBSD developers, or potential developers, are naive or weak enough to turn quisling.

    Face it. Sidekick is gone, M$ has it, and its now time to finish your mourning, face reality and move on. Start a new company.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.