Domain: interopsystems.com
Stories and comments across the archive that link to interopsystems.com.
Comments · 26
-
Re:Sounds Great!
I use Interix (see http://interopsystems.com/ for more info) on Windows. It uses POSIX compatibility built into the NT kernel, reducing the levels of indirection. Most CLI apps work fine, although you'll need to compile anything the (rather limited) repository doesn't have. However, since GCC and the general build tools are included, this is pretty easy. Simple X apps, such as gvim or fvwm, also work well (an X server is included with the software bundle). Konsole... I don't know about that. QT is in the repo, but you'd have to compile the core of KDE from scratch.
You can, however, use a Windows CLI window running bash (or an Xterm if you prefer). If it's the shell you want, that works quite well.
-
Re:No myth here
-
Re:WowI use Interix (the Unix-like "OS" taht runs in the NT kernel's POSIX subsystem) almost every day. I've got everything from vi (came with it), to ssh and sshd (installed binaries from Interop systems), to programs like sox - I needed it for something a while ago - that I compiled myself, using (a modified, and redistributed with source from Microsoft, version of) the GNU build toolchain.
To those who ask "Why?" and point out that I could just use Linux/Cygwin, there's a couple of noteworthy points here:- I do use Linux, but I don't always want to reboot just to run a bash script or compile a tarball that requires a Unix-like environment.
- I can, from the shell (bash, though I have a few others as well), run Win32 programs as well, including piping or redirecting their output. This even works with popen() or system() calls.
- It's native to the system, and probably runs faster that cygwin (no syscall interpretation layer).
There's probably a few other issues, both good and bad. I've not used Cygwin enough to know, for example, how it works with limited accounts (on XP, or using UAC on Vista); Interix handles it quite nicely including the use of su and sudo (in Vista, su to "root" will require enabling the full Administrator account, however... note that this should be password protected even if disabled since it gets enabled if the computer is booted to Safe Mode). Interix does not come with an X server, but it does come with the X client libraries; I use Xming (a port of the freedesktop.org X server to win32) for an X server when I need it.
The only real problems are that you can't get block device access to hard drives, etc. and you can't use Linux-specific code or libraries (syscalls or things like the varius Linux-only ioctl tricks). Some programs won't compile because of this. It also uses Windows PE format executables, not ELF binaries (although it does have .so libraries) so it isn't binary-compatible with non-Interix compilations even if it has the needed libraries. -
UNIX Subsytem for NT/2k/XP/2k3/Vista
For 2000 and XP, you want Windows Services for Unix or SFU. The download includes a complete - though basic - POSIX environment, a working GNU build toolchain (and yes, sources for all GPL code), and NFS server and client abilities. You shouldn't need to do anything except run the self-extracting download archive and run setup.exe. The installer will provide options to enable setuid and case-sensitive behaviors in the filesystem used within the subsystem, which should be used as a number of programs need them. The version of Perl included with the installer is obsolete and probably not worth installing; I'll get to that in a sec.
For Server 2003 and Vista, you must first enable the Windows component called the Subsystem for Unix Applications (SUA). This can be done by going to the (Add/Remove) Programs control panel - there's an option on the side for enabling Windows components. In Vista at least, you can also enable NFS and Unix-style printer connectivity here. You will then need to install the Utilities and SDK for the SUA, which is available for Vista/Longhorn and for Server 2003. On Vista there will be an additional install option to enable su-to-root behavior, required for programs like sudo - this option is important because by default, the Administrator account is disabled in Vista and privilege escalation is achieved through UAC. Although UAC can be used to start a Unix shell as root/admin, it cannot be used to change a shell's permissions while it runs. If you install sudo this becomes possible.
In all cases, you will get two Unix shells, the Korn shell and the C shell, in your start menu. Either one will start the subsystem and run a login process that creates the necessary environment variables and such. However, there are a few notable lacks. One of them is that while x11r5 and x11r6 client libraries are installed (with the r6 libraries used by default), there is no X server. Thus far I haven't managed to port x.org to Interix (the name of the subsystem "OS") so I use a win32 X server, specifically xming which runs on everything including Vista. The second major lack is a package manager or any software beyond the most basic requirements. For resolving this issue there are a couple options; the two I have tried are InteropSystems and NetBSD pkgsrc.
Both provide a good number of commonly used programs, and support the Interix platform. However, there are some major differences: InteropSystems primarily distributes binaries, with an eye to very easy package management and rapid usability. It also integrates better with Windows, doing things like adding a Start menu link for the Bash shell if you install their package. There is a fairly good forum for assistance and mostly it's a very easy out-of-box experience. However, their package tree is somewhat limited, and installing older versions of some libraries is trickier than it might be. They suuport all versions of Interix, from 3.5 (XP-era SFU) up to 6.0 (Vista's SUA). NetBSD's pkgsrc, on the other hand, is mostly source-based (although there are some pre-built packages for Interix; roughly as many as InteropSystems has, in fact). It takes longer to compile from source, and the initial download is hefty. However, a much wider selection of packages is available (although there's no guarantee they'll all work; indeed some, such as the X server, are flagged to not even attempt to build in Interix) and the packages are presumably optimized at least somewhat for your system during compilation. It's harder to find the right packages at times, though, and I have yet to get even the source-based boo -
Re:Microsoft should worry until...When you ask the NT kernel to open any object, including a file, the default is to be case-sensitive with the name lookup. There is a flag you can specify (OBJ_CASE_INSENSITIVE) to make it insensitive. NTFS supports it both ways. Win32 always specifies this flag, unless you pass FILE_FLAG_POSIX_SEMANTICS to CreateFile. Most Win32 programs don't do that, so end up asking the filesystem for case-insensitive handling. Since the topic was how case-insensitivity was hurting Java, the question is why isn't the Java runtime passing that flag to get the case-sensitivity it wants?
SFU doesn't use Win32, and never uses OBJ_CASE_INSENSITIVE AFAIK. It's true that a lot of Win32 apps will choke at the sight of two filenames differing only in case, but then there are a lot of things that most of them don't do properly, like LUA. I agree that Win32 is an ugly mess, that plenty of software built on it is as bad, and that it should all go away... but one of Microsoft's biggest claims to fame is that mass of software built on that interface. They're not about to give it up. Just don't confuse Win32 with the kernel or NTFS.Yep, that's one bang up set of tools. Not even SSH. Telnet. Yep, keeping up with the times. Real UNIX integration there.
It's too bad Microsoft doesn't include more standard tools, but that's what interopsystems.com is for. Most UNIXy software will compile directly or with minor modifications, and they offer binaries for SSH, Apache, bash, and lots of others.But who runs this?
I do, FWIW. There aren't a ton of users, but the number may grow more now that SFU is being included in 2003 R2 and business versions of Vista. It's targeted towards users with old apps running on an ancient commercial UNIX more than modern Linux and *BSD users.Either way, that article is virtually irrelevant to today's systems other than to point out the pThread issue, and that MySQL does/did have issues on OSX.
Lock contention will always be a problem for hardware multithreading, regardless of architecture. I'm not saying that it's a problem that can't be fixed. Windows NT had some awful scaling problems as recently as NT4, when it used to struggle to scale past 4 CPUs executing heavy IO. Linux used the global-kernel-lock arch in 2.0, and wasn't preemptible until 2.6. I'm just saying that last I checked, OSX isn't ready for >4 heavy SMP yet.
For comparison, it would be hard to test OSX with a lot of CPUs because the most you can get with Apple hardware is what, 4? Why doesn't Apple have a high-end server model with a lot more? -
Install SFU
Or whatever it is renamed!
In Vista, it will ship as a regular component of the Pro and Enterprise versions.
http://www.microsoft.com/technet/interopmigration/ unix/sfu/default.mspx
http://www.microsoft.com/downloads/details.aspx?Fa milyID=896c9688-601b-44f1-81a4-02878ff11778&Displa yLang=en
Get Bash, OpenSSH, BSD pkg_tools and the GNU toolchain here:
http://www.interopsystems.com/tools/warehouse.htm
Oh, and if you want MS's fast compiler, as opposed to GNU's portable one - then this is free. Add an environment variable, and cc calls this:
http://msdn.microsoft.com/vstudio/express/visualC/ default.aspx -
Re:SFU was only good for one thing
What makes Cygwin better is the ample userland where wider and better supported range of 3rd party program packages built into the default install than SFU.
Now if pkgsrc fixes that issue, I might switch over more.
I expect you haven't visited The Interix Tools site then http://www.interopsystems.com/tools/. We use pkg_add (it's BSD based) for a load of additional utilities and libraries for Interix. These are binary packages BTW. So no futtzing with an builds. Packages include bash, openssh, zsh, BIND9, etc. -
Re:The full story
Hardly shocking information since it was announced back on April, 26, 2005 in the Interix Forums (http://www.interopsystems.com/tools/forum). So this has been known *publicly* for over 4 months now with a lot more detail than is in the other articles. The link is http://www.interopsystems.com/tools/forum/tm.aspx
? m=5623The real story is not that SFU is ending, but rather that it is becoming part of the regular distribution. Since January, 2004 SFU version 3.5 has been available as a free download from Microsoft (http://www.microsoft.com/windows/sfu) with no restrictions, etc. So this change has been expected for some time.
Complaints in other posting about "missing" applications are pretty hollow: two compilers are available (gcc 3.3 and MSVC {a free version of MSVC is available}, OpenSSH, bash, zsh, etc. They can be picked up freely from the Interix Tools site http://www.interopsystems.com/tools.
-
Re:The full story
Hardly shocking information since it was announced back on April, 26, 2005 in the Interix Forums (http://www.interopsystems.com/tools/forum). So this has been known *publicly* for over 4 months now with a lot more detail than is in the other articles. The link is http://www.interopsystems.com/tools/forum/tm.aspx
? m=5623The real story is not that SFU is ending, but rather that it is becoming part of the regular distribution. Since January, 2004 SFU version 3.5 has been available as a free download from Microsoft (http://www.microsoft.com/windows/sfu) with no restrictions, etc. So this change has been expected for some time.
Complaints in other posting about "missing" applications are pretty hollow: two compilers are available (gcc 3.3 and MSVC {a free version of MSVC is available}, OpenSSH, bash, zsh, etc. They can be picked up freely from the Interix Tools site http://www.interopsystems.com/tools.
-
Re:The full story
Hardly shocking information since it was announced back on April, 26, 2005 in the Interix Forums (http://www.interopsystems.com/tools/forum). So this has been known *publicly* for over 4 months now with a lot more detail than is in the other articles. The link is http://www.interopsystems.com/tools/forum/tm.aspx
? m=5623The real story is not that SFU is ending, but rather that it is becoming part of the regular distribution. Since January, 2004 SFU version 3.5 has been available as a free download from Microsoft (http://www.microsoft.com/windows/sfu) with no restrictions, etc. So this change has been expected for some time.
Complaints in other posting about "missing" applications are pretty hollow: two compilers are available (gcc 3.3 and MSVC {a free version of MSVC is available}, OpenSSH, bash, zsh, etc. They can be picked up freely from the Interix Tools site http://www.interopsystems.com/tools.
-
Re:The petty annoyancesUNIX utilities as first-class members of the OS and not something that clings to life within the system. Yeah I'm looking at you Cygwin!
I love my Mac at work, but I use Win2k at home. Have you tried Windows Services for UNIX? Intertix used alot of OpenBSD code in SFU, and they say it runs natively rather than through a system call emulator. However, there are not as many UNIX utilities available for SFU as for cygwin. Some additional tools are available in the Tool Warehouse
Everything supports save as PDF through printing interface. No need to use Acrobat.
I love being able to save anything to PDF, but it bugs me that Preview doesn't seem to let you fill in PDF forms. Also, you can't edit PDFs in Preview; but hey, I guess it's "free".
-
Re:Windows... let's lock 'em out.
You can run BIND 9 as the DNS on Windows machines instead of using the Windows DNS. Then you can run your DNS just like you do on Unix machines. Then the Windows DNS problem is solved. The faith in the BIND 9 DNS is a lot higher than the Windows DNS. And if there is a problem with BIND 9 I'm sure that a fix is going to be made available a *lot* faster and will be installable on older Windows OS's too.
You can run BIND 9 on Windows using Interix (part of SFU): a BIND 9 binary package is available at http://www.interopsystems.com/tools/
There's likely a cygwin port of BIND 9 too.
-
Re:If you put a pig in a dress
If you go to http://www.interopsystems.com you can download GIMP for MS's Services for Unix. It's not a Win32 port, but POSIX on the NT kernel is close enough.
-
Re:But what about Debian/NT?
That's why SFU isn't built on top of Win32, but the kernel's native API, which does fork() just fine. So does SFU; it uses the native API.
The NT kernel was designed from the beginning to support different environments, including POSIX and Win32. Each environment subsystem consists of a server process that maintains common state specific to the environment, and a set of client libraries that translate the environment's API to the native API and calls to the server. Win32 is an environment subsystem and so is SFU.
For some reason, cygwin (which debian-win32 uses) insists on using only Win32, so they have to resort to kludges to make certain things like fork() work.
Now that SFU is free, I don't see why debian-win32 couldn't use that instead of cygwin.
As it stands, Interop Systems has the best collection of packages for SFU. Most of the essential stuff is there, but it's still a far cry from Debian's library. -
Re:Still no SSH
Install Windows Services for Unix and OpenSSH SFU is a POSIX layer that runs on top of the kernel at the same level as Win32. Cygwin runs on top of Win32. More software has been already been ported to Cygwin, but I find that ssh works better with SFU.
-
Re:On the list of changes:
doesn't bash also run under Windows?
Dunno if there's a native port, but I've been using it under Interix (aka Microsoft StFU). But I'll probably be lazy and wait for Interop Systems to do their thing, since they don't seem to target it directly. -
Re:An important difference
So use the services for unix download and install bash.. Bash Shell
-
Re:Bsd is dying :PAre you trying to get BSDers to attack you buy calling them flamebaitable?
;)BTW, the Windows crowd might not be as clueless about BSD as some think: Windows Services for UNIX (SFU) 3.5. Apparently it is based on BSD (OpenBSD according to this OSNews.com thread). Its free now, and in some ways I like it a bit better than Cygwin. When I need to be on a Windows box, I tend to install either SFU or Cygwin. SFU is very handy once you get some of the stuff from the Interop UNIX tools warehouse installed.
-
Re:Open FormatsWell, not the standard shell interface, but it's available
... -
Re:Open FormatsWell, not the standard shell interface, but it's available
... -
Re:Despairing for a native Win32 PostgreSQL....
Try http://www.interopsystems.com/tools/warehouse.htm
. Not only PostgreSQL, but a load of other stuff too! -
Re:GPL == Communism, and I like it that wayHi,
Heard about this Redmond, WA based software company called 'Microsoft'? Heard it's been doing well lately, which is why I'm mentioning it here.
You see, among its many different offerings, it sells (yes, you read that right, sells) this thing called Services for UNIX for US$99. For US$20 more, you can order the source code for the program as well.
They decided to improve upon an existing GPL-ed product (with wide acclaim incidentally), and yet are making money out of selling it. A novel concept, don't ya think?
-
Re:What's your point?
> Microsoft never said that open source was the end of freedom. They said that about the GPL, but not BSD.
Which is probably why they distribute ao. gcc in one of their products and nicely distribute the source code on cd (for a fee) and on their site (for free) ? -
They use it themselves
-
Re:Has anybody considered
-
$20 for source?The windows/sfu URL links to this site with a link labeled "GPL Source" or something like that.
Well, the Interop Store will sell you a CD containing the source code... for $20!
First, props to MS for putting the source code out there, available even to those who have not purchased the binary software.
But second, $20? This seems to fail section 3b of the GPL:... for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange
...
$20 is pretty high for the cost of physically performing source distribution, isn't it? Unless when you buy the "regular" version of the software and it comes with the source code on the CD, of which there is no mention that I can see... this seems pretty fishy to me.