You likely installed a custom build of OpenSSH at some point in time and now when you run 'ssh' it runs this outdated copy instead of Apple's copy. Outdated here means that it was built against OpenSSL 0.9.4something or 0.9.5something, not the 0.9.6b that is currently provided by Apple.
Run "which ssh" and see what it tells you. If it says "/usr/local/bin/ssh", you may want to remove that copy of ssh so that it uses Apple's version (/usr/bin/ssh).
Just for the record, my problem with Tenon is not Xtools, but the Gimp package they offer for download. I looked inside it, found that it looked very much like it was built with Fink, and contacted Tenon about it. They were very quick to respond and confirmed that they used Fink, forgot to include credits and were in violation of the various licenses by not providing source (GIMP, glib, gtk+, gnome-libs, gettext and some other things included inside the.app bundle are GPL/LGPL). I was told they'd correct the situation in "a few days". That was on September 25, and when I got back to them some weeks later, I was simply told their lead programmer was very ill. Still nothing has happened to date...
Re:What's so special about this distribution?
on
GNU-Darwin Goes Beta
·
· Score: 1
Okay, I give up. If you really, seriously think that this:
cd/usr/bin
mv tar ~
wget http://gnu-darwin.sourceforge.net/packages/tar
chmod 755/usr/bin/tar
is not a serious issue, then there is no point to further discussion.
Re:What's so special about this distribution?
on
GNU-Darwin Goes Beta
·
· Score: 2, Informative
Bad day?
Not at all. I'm just horrified by the scripts that you ask people to execute as root. I'm also defending Fink in the comparison you make. Saying that GNU-Darwin and Fink are the same and the only difference is the number of available packages misses some important differences, and one of them is testing and quality.
None of the above has anything to do with the quality of the distro.
Quite to the contrary, they have very much to say:
install-info and install are on completely different playgrounds. install is an enhanced version of cp/mv with special features for installing executables in their final destination. install-info is used to maintain the 'dir' file of a documentation collection in Info format. There are actually at least two incompatible versions of install-info out there, and the install command is far from a useful substitute./bin/true would be a far better (i.e. less dangerous) "do nothing" replacement. Anyway, this tells me that a) GNU-Darwin doesn't maintain the dir file, and b) you don't even know what install-info is supposed to do.
The only reason I can see to link enlightenment from/bin is because the enlightenment.install script distributed with it is somewhat broken. Instead of fixing the script, you've opted to make a link in an inappropriate directory.
Major revisions of shared libraries are made because there are changes that break binary compatibility. Linking one major revision of libfreetype to another one - instead of looking into the problem and coming up with a real solution - is asking for trouble.
And, well, the version number and the complete lack of sanity checks and error handling in the install script also says a lot about the quality of the distro. Remember, distro = packages + infrastructure + handling scripts.
Re:What's so special about this distribution?
on
GNU-Darwin Goes Beta
·
· Score: 1
GNU-Darwin is like the Fink, except with ten times more software
...at a fraction of the quality. As anyone can see from the shell script mentioned in the story, that applies to both the packages and the scripts that keep the distribution together. Some really funny excerpts:
They are working on rootless X, but I believe it's still in the testing phase.
Correct. As has already been mentioned, rootless support is in the current development versions of XFree86, available from CVS. There are still lots of bugs to sort out, but it's coming along nicely. A first binary test release will be out soon. Watch the web site mentioned below.
There are a lot of gimp people looking into rootless heavily over at Mac Gimp
The people behind MacGimp actually are not participating in the development of Xfree86. They just post news about it and sell it on CDs. Rootless mode is developed mainly by Gregory Parker. More information on the development of XFree86 for Darwin and Mac OS X can be found at http://www.mrcla.com/XonX/.
I know and use Perl, Python and PHP. Altogether I probably know a dozen high-level languages. When I need to, I can learn a new language in maybe one or two weeks.
I looked at Ruby once, but gave up bothering with it fairly soon. I guess the learning curve was just too steep. I couldn't find out what the language's actual paradigm for values / variables / types / objects was. The tutorial was telling me that even integers always were objects and had some quite confusing examples to show just that off. Showing how you still get normal things done first would have been better...
Now that we know all about Apple's codenames for hardware, what about software? I'm sure there are lots of not well known codenames for Mac OS or Quicktime releases, especially for the various Mac OS X builds. Anyone?
Yes, it has been done. I've ported the central parts of GNOME to Darwin for Fink. And actually, it was hard in some places. While Apple has a dlopen() compatibility wrapper in Darwin CVS and it mostly works, they don't ship it. I pulled the code out of CVS, added path searching and packaged it as a library. Speaking of libraries, building shared libraries is also quite different on Darwin.
I like this story. It's another great example of how biology can be hacked.
Really, this is like observing and mimicking the communication in a distributed system (read: computer network). Only that biology uses (and a computer scientist would say: abuses) so many forms of communication that discoveries like this are still possible even today. It even has some kind of hacker spirit - why use a hormone to tell the bone to grow, when the vibration that's there anyway will do?
My opinion on Mac OS X on Intel is simple: it would be nice to have, but it simply won't happen. The reasons for this are not technical - Darwin (the BSD core of Mac OS X, which is open-sourced) runs on x86 hardware, although driver support is extremely limited right now. The issue here is economical. Apple is a hardware company. They make a living selling boxes, not software.
Now even if Apple decided to make x86 boxes of their own, and make them right, i.e. with all the little features and the good stability and support we've come to expect, Apple would still be in deep trouble. They would release a version of Mac OS X that only runs on Apple's x86 hardware, of course. But the core, Darwin, is open-sourced, so it would be a matter of days (or maybe weeks) until someone comes up with drivers to let it run on other hardware. We've seen how much trouble Apple had with clone makers, now think about what would happen if Apple moved to x86...
Anyway, Mac OS X would have a hard time on Intel. If you're used to Linux, compiling and running Unix software on Mac OS X is (excuse the wording) a pain in the ass. I know what I talk about, because I ported GNOME to Mac OS X (see http://fink.sourceforge.net/). Also, there is no Classic environment on Intel. This is a big drawback, because not all applications will be ported to Mac OS X right away, and you won't have the choice of running the classic Mac OS applications of x86 hardware.
Personally, I'll just keep running Mac OS X on my PowerBook G3 and be happy...
Slashdot Mirror
Run "which ssh" and see what it tells you. If it says "/usr/local/bin/ssh", you may want to remove that copy of ssh so that it uses Apple's version (/usr/bin/ssh).
Just for the record, my problem with Tenon is not Xtools, but the Gimp package they offer for download. I looked inside it, found that it looked very much like it was built with Fink, and contacted Tenon about it. They were very quick to respond and confirmed that they used Fink, forgot to include credits and were in violation of the various licenses by not providing source (GIMP, glib, gtk+, gnome-libs, gettext and some other things included inside the .app bundle are GPL/LGPL). I was told they'd correct the situation in "a few days". That was on September 25, and when I got back to them some weeks later, I was simply told their lead programmer was very ill. Still nothing has happened to date...
Okay, I give up. If you really, seriously think that this:
cd /usr/bin /usr/bin/tar
mv tar ~
wget http://gnu-darwin.sourceforge.net/packages/tar
chmod 755
is not a serious issue, then there is no point to further discussion.
Not at all. I'm just horrified by the scripts that you ask people to execute as root. I'm also defending Fink in the comparison you make. Saying that GNU-Darwin and Fink are the same and the only difference is the number of available packages misses some important differences, and one of them is testing and quality.
Quite to the contrary, they have very much to say:
And, well, the version number and the complete lack of sanity checks and error handling in the install script also says a lot about the quality of the distro. Remember, distro = packages + infrastructure + handling scripts.
...at a fraction of the quality. As anyone can see from the shell script mentioned in the story, that applies to both the packages and the scripts that keep the distribution together. Some really funny excerpts:
ln -s /usr/bin/install /usr/bin/install-info /usr/bin/install /usr/local/bin/install-info
/usr/X11R6/bin/enlightenment /bin
/usr/X11R6/lib/libfreetype.7.0.dylib /usr/X11R6/lib/libfreetype.6.dylib
ln -s
ln -s
ln -s
Then there's other fun stuff like replacing /usr/bin/tar the most dangerous way, or the script version number in the comment: 0.0.1a2 (untested)
I really don't know if I should laugh or cry about this...
Correct. As has already been mentioned, rootless support is in the current development versions of XFree86, available from CVS. There are still lots of bugs to sort out, but it's coming along nicely. A first binary test release will be out soon. Watch the web site mentioned below.
The people behind MacGimp actually are not participating in the development of Xfree86. They just post news about it and sell it on CDs. Rootless mode is developed mainly by Gregory Parker. More information on the development of XFree86 for Darwin and Mac OS X can be found at http://www.mrcla.com/XonX/.
I looked at Ruby once, but gave up bothering with it fairly soon. I guess the learning curve was just too steep. I couldn't find out what the language's actual paradigm for values / variables / types / objects was. The tutorial was telling me that even integers always were objects and had some quite confusing examples to show just that off. Showing how you still get normal things done first would have been better...
Just my 2 euro-cents.
Now that we know all about Apple's codenames for hardware, what about software? I'm sure there are lots of not well known codenames for Mac OS or Quicktime releases, especially for the various Mac OS X builds. Anyone?
BTW, Enlightenment is ported, too.
Really, this is like observing and mimicking the communication in a distributed system (read: computer network). Only that biology uses (and a computer scientist would say: abuses) so many forms of communication that discoveries like this are still possible even today. It even has some kind of hacker spirit - why use a hormone to tell the bone to grow, when the vibration that's there anyway will do?
Now even if Apple decided to make x86 boxes of their own, and make them right, i.e. with all the little features and the good stability and support we've come to expect, Apple would still be in deep trouble. They would release a version of Mac OS X that only runs on Apple's x86 hardware, of course. But the core, Darwin, is open-sourced, so it would be a matter of days (or maybe weeks) until someone comes up with drivers to let it run on other hardware. We've seen how much trouble Apple had with clone makers, now think about what would happen if Apple moved to x86...
Anyway, Mac OS X would have a hard time on Intel. If you're used to Linux, compiling and running Unix software on Mac OS X is (excuse the wording) a pain in the ass. I know what I talk about, because I ported GNOME to Mac OS X (see http://fink.sourceforge.net/). Also, there is no Classic environment on Intel. This is a big drawback, because not all applications will be ported to Mac OS X right away, and you won't have the choice of running the classic Mac OS applications of x86 hardware.
Personally, I'll just keep running Mac OS X on my PowerBook G3 and be happy...