Slashdot Mirror
Microsoft Services for Unix and OpenBSD
ubiquitin writes "If you use strings on Microsoft's Services for Unix (SFU) interoperability suite which was developed by Interex you find that it is largely composed of source from the OpenBSD 3.0 source tree according to a recent deadly.org article."
The BSD license allows anybody to do this.
Ra!
Thanks, Theo!
Conformity is the jailer of freedom and enemy of growth. -JFK
MS has every right to do this with BSD licensed code. And they do with GPLed code to, but if it was GPLed code then they would have to release the source to the derivative product under the GPL.
Note that I'm not making any statements for or against either license, or for or against MS. I'm just pointing the key the difference in these popular licenses.
Other simple things sorely lacking in MS servers:
Administrator ability to log in as another user, without their password, using their environment.
Ability to easily assign a printer or share you've set up as administrator to all other users of the machine/domain... and don't even mention group policies (what a cluster fuck).
Ability to easily assign drive mappings/printers dependant on what groups a users belongs to (again don't EVEN say you can do thit with group policies).
Windows servers were obviously not designed from the standpoint of an administrator setting resources up for users.
>>>Administrator ability to log in as another user, without their password, using their environment.
/winnt/etc that lets you see, a list of txt configs that control the system? You could back up the configs and know you have a hardcopy of the conf's. Once you're done editing these files, you could re-run the sync program and have it re-populate the registry.
Nope. That one is intentionally NOT in there. Go have a look at OpenVMS, the software from yesteryear that MS built NT. There was supposed to be a form of audit logs that you must either reset their password OR take Control Rights of. Either way, the user is tipped off that admin/root was playing in their acct.
>>>Ability to easily assign a printer or share you've set up as administrator to all other users of the machine/domain... and don't even mention group policies (what a cluster fuck).
It's not that hard. Check the permissions of the local device/directory is. Then control who has access to the share. It's no harder than user/group/everybody along with the NSA patches on Linux.
>>>Ability to easily assign drive mappings/printers dependant on what groups a users belongs to (again don't EVEN say you can do thit with group policies).
Simply done with logon scripts, as the AC said. He IS right, you know..
And if you're going to get pissed off at MS, at least do so with the right reasons. First, there's no way to configure a server decently over a modem line. MS already created edit.com, which is a usable editor. Why not have a SYNC program in
Next bitch is about MS not patching critical software. Here at my work, we were hit with 2 nasty viruses recently. If you say that we should have had them patched you're wrong. The patches themselves have "added functionality" which we could not install on our clients until we determined they were OK to do so. Essentially, a patch is SUPPOSED to fix a wrong, not add extra crap.
Third, is I cannot log in to multiple accounts at once. Exapmle: I can log into my user on my Linux box, and (since I'm in wheel) su to root to get certain root-only things done. With su/sudo/kdesu/gsu, correct attributes with each user are applied properly. In windows, there is no way I can do this (I know xp has it, but It's not a server os). Some of you might say, "Use the RunAs service" (hold down left-shift and left click on program, or called from command line). It doesnt propigate environment varibles correctly, so many programs wont install/run. Heck, even I can run XWindows stuff as multiple users! Why cant windows?
This is why MS hates the Linux, because of the GPL. If MS were to be caught integrating Linux code into MS then they would be violating the GPL. With the BSD license they don't have to worry, they just keep the License in the file. That's why SCO also hates the BPL, beacuse they can't just integrate Linux code into SCO. Hmm but they arlready did that didn't they?
Only 'flamers' flame!
Does slashdot hate my posts?
With cygwin you get true UNIX compatability and hundreds of unilities including ssh and X terminal sessions.
I for one am really glad to see MS grabbing as much OSS code as they can for implementing the more standards compliant portions of their products, if only to see them ship more stable, secure code.
I've a lot more faith in the code they grab from the *BSD trees than in their own internally generated code and, having to run WinXX a lot (my VMWare Workstation currently has 8 open machines in it and 6 of them are WinXX: WinNT (1), Win2K(4) and WinXP(1), two are RH8), I'd rather have the peace of mind.
- Barrie
does this mean Microsoft is dying?
The TCP/IP stack in Windows NT was based on BSD too. The only annoying thing I find about that is that they tore it out and replaced it with a less-capable TCP/IP stack for Windows 2000 (many of the ioctl's such as set receive and send buffer size no longer work... that's progress!)
"Freedom means freedom for everybody" -- Dick Cheney
No, He went down with his ship... and (presumably) was eaten by some fishes
(who were eaten by some fishes
and swallowed by a whale
[[ for those of you who remember 'The Point']])
Free Software: Like love, it grows best when given away.