Slashdot Mirror
Sun Says Project Indiana is Not a Linux Copy
eldavojohn writes "Ian Murdock (Debian author & Sun's OS Chief) made some comments about Project Indiana that many have said is an attempt to make Solaris simply "more Linux-like." But Murdock quashes any concerns that this is just another Linux clone — muddying up the waters of distribution selection. He says that it's more a 'best of both worlds' attempt to make an OS that appeals to a broader audience. From the article, "Project Indiana will include a revamped package management system, which should prove popular with developers unaccustomed to Solaris. The OS has some clunky, archaic aspects, and Murdock thinks the new package system will modernize Solaris.""
Yes you are indeed a troll. But mostly because you are talking out your ass.
In 1996, Bruce Perens replaced Ian Murdock as the project leader.
Money is the root of all evil?
Not much longer than 10 years ago, most people in the world were asking the same question in reverse. Solaris is hardly a "new player" - lest we forget that Bill Joy, co-founder of SUN and designer of the SPARC, was the original BSD developer as well. Solaris is as real as it gets.
Productivity improvements might be determined by how badly you need Dtrace functionality: http://www.opensolaris.org/os/community/dtrace/
I'm not confident that a clone will make it into Linux any time soon.
In audience terms, I'm thinking that the limiter is still hardware support. I don't get much time to look at OpenSolaris, so I could be in left field.
What you do with a computer does not constitute the whole of computing.
Download the free developer edition. It's included.
Care about electronic freedom? Consider donating to the EFF!
The plagues called Java and C# are their fault, but I don't think that's the reason.
Regarding Unix, Sun was Unix in the 1980s to the mid-1990s, at least for many of us. High-resolution, diskless workstations, networking, all the cool free software availableI feel personally indebted to SunOS and Solaris -- I might have been running Windows right now, if we didn't have such a great Solaris environment at University and my first few jobs!
Solaris is a pretty nice system overall. Sun's biggest failing from a user experience is their adherence to obsolete versions of the standard *NIX applications. Most of the stuff in /bin has none of the useful features added by POSIX. The POSIX stuff is all sequestered in /usr/xpg4/bin. This is a PITA when you want to write portable shell scripts that aren't restricted to a 25-year old subset of UNIX.
I am becoming gerund, destroyer of verbs.
I remember reading a discussion by the Opensolaris folks claiming how much better their tools were than the Gnu tools. They were singling out Solaris TAR and saying what a mess the Gnu version is. As a user, Solaris TAR is crap to use compared to GnuTAR. It can't even handle tar files over 2GB, for example, and I've had several tar files it can't handle that GnuTAR can. I also like the built-in support for bzip2 and gzip in GnuTAR. Now granted, I haven't tried Solaris 10, but I suspect the problems remain. That isn't to say that GnuTAR is perfect... I was running an older version that would truncate some filenames.
Another one that caused me endless frustration was Solaris newgrp did not allow you to specify a command line like the Linux one did. I ended up porting over the Gnu version just so I could do my job without having to manually type in a command as part of a build procedure.
At my job I've been maintaining KDE for Solaris for a bunch of Sun users. When I migrated my desktop to Linux I'm still having to support KDE for them (and that's not my job, I'm not in IT). None of the developers like Sun's Gnome 2.0 that's included with Solaris 9, and newer versions have problems compiling because Sun still does not support the X render extension (on Sparc). Trying to compile KDE was difficult, since Sun's libraries and tools are often broken or so out of date. I also have had to compile GCC for Solaris to do it, since Sun's C++ compiler we have barfs on a lot of open source packages. I've also hit a number of problems because numerous features are missing in Sun's libc, even though they've been part of the posix or ISO standard for many years (i.e. missing stdint.h), including some parts of stdio.h. (stdint.h is part of the ISO C99 standard, well before Solaris 9 came out).
I remember having tons of problems with Sun's sed because it would silently truncate after 4-8KB of input.
-Aaron
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
- Much finer grain security (RBAC principles in Solaris are much better handled than in grsecurity for GNU/Linux).
/usr/sfw, all BSD tools in /usr/ucb, plus all of Solaris' goodness.
- ZFS is now bootable (ZFS is now bootable)
- DTrace is much more powerful than strace (a number I read in one of the Sun DTrace presentation stated ~40000 probe points in Solaris to ~40 in GNU/Linux).
- All the p* tools on Solaris are much more powerful (and in some instances, there are no equivalents in GNU/Linux requiring users to have to code their own inotify CLI program)
- Service management is also much better taken care of with SMF than anything else I've seen in any of the BSDs or GNU/Linux as of late.
- Project Athena (used for handling massive users+groups / computers invented by MIT) runs with SunOS (and I believe Solaris as well))
- All GNU tools are available in
- Unlike GNU/Linux, Solaris adheres more strictly to standards much better and so if you have to write programs that are to be cross platform... developing them on Solaris will probably be your best bet of seeing if it works on other platforms.
- Another thing (that is if this matters to you), it's the only open source Sys V UNIX available.
Eh, maybe a working web site? Nexenta's site has been down for three days now.
You have it backwards. The scripts you are talking about use non-standard extenstions to the Bourne (POSIX) shell because they were probably written under Linux without any thought to portability.
If you want to use bash for shell scripts, just put
(Now, if you want to talk about Solaris' ksh, that's another story.)