Columbia University Ending the Kermit Project
An anonymous reader writes "Columbia University has announced that the Kermit Project will be ended in July 2011, after more than 30 years in existence. Open Kermit (C-Kermit) will remain available, but without any support or ongoing development. Kermit-95, which cannot be open-sourced, will remain available for license purchases but without support or maintenance."
It's not easy needing green...
Poor Kermit. He was never the same after he got laid off from that theater group. He didnt like the managment choices. Said it was a puppet regime.
------
beware he who would deny you access to information, for in his mind he dreams himself your master
Condolences to Miss Piggy. I bet she will be devastated by the news.
Sad news indeed. Kermit has finally croaked.
I feel as if a movie star I hadn't watched in forever has just passed away. "I didn't know he was still alive?"
This is a boring sig
Kermit was and may still be useful when your connection is terrible. I am willing to bet that today it is used more than zmodem or xmodem.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
More than Duke Nukem or anything else I've heard referenced recently, none have blasted me back to my youth more than hearing the words "kermit" and "zmodem". Right around the same time that you could go down to the local Hacker Shack (later renamed, due to conflicts with Radio Shack) and thumb through thousands of 5.25" floppies organized like mini-albums and you'd pay a buck just for a floppy with a looping black and white video you could watch on your grainy CGA.
God damn, I miss those days. I'm glad the internet is widespread and aiding tens of millions of people in their life on a daily basis, but there was something delightful about being part of a tiny group of weirdos connecting to each other with ATA commands and some guy's hobby board.
Wow, in my college and post college days I used that protocol in so many places and so many ways I can't even begin to count. That was a very conservative protocol that was able to go through almost anything. One time I had it go from a portable computer over a modem connection to an Equinox data switch to an AT&T 3b5 Unix, to a cu back to the Equinox (to change the speed from 300 baud to 9600 baud) to an IBM 7171 protocol converter to an IBM 4361. And it could actually transfer files. Another time I had to stress test a DECNET terminal simulator on a Sun (the old version would fail in the middle of the day on the busiest of days) So I used kermit to connect to host1, then to host 2, back to host 1, back to host 2, I think something like 40 times. Then I did a file transfer through all the connections. It worked.
The company where I worked in college (Digital Techniques Inc. who made a line of touchscreen computers in the early 80s) had an MS-DOS machine that ran on STD-Bus, non-PC compatible... and with the source-code from Columbia (on 9-track tape!) I was able to write a communication driver for the 2661 DUART (same as in the Zenith Z-100, and as compared to the IBM-PC's 8250 UART). Finally we could zap files up to the VAX at a blazing 19,200 baud! Never could iron out all the interrupt issues for even-higher speeds.
A few years later when this Linux thing came along I said, Aha! ... thanks Kermit for being Open before Open was cool.
From the Columbia's web site
"On or before June 30, 2011, there will be Open Source versions of C-Kermit, E-Kermit, and Kermit 95. "
Unless the anonymous reader has some inside information...
Yes, it is used a lot in the embedded world. One of the few tools available to recover a bricked RS232-only based device. Used on things like the gumstix, beagleboard, and lots of other SBC like ARM based embedded devices. If you make/order custom versions or your own shipping product does not contain alternatives like MMC/SD card boot capabilities, c-kermit is one of the few things out there to allow you to boot, load code, and then go to console all from one tool on such devices. Saved my (and my employers) ass many times on bricked or buggy embedded devices.
I miss Kermit like I miss my old Kreidler motobike, found memories but I'd probable wouldn't really like it if I would need it again...
But what I would really appreciate from columbia would be a clear and detailled explanation of what parts or "kind of parts" of kermit-95 and why ? cannot be open sourced ? :-) .. ....
Are there pieces of code written by Open Source adverse copyright holders ?
Or "lost coypright holders" that have rights but cannot be located
Or legally "challenged" copyright holders (childs who are too young to "agree" to anything but are the sole heir of some copyrights ? for example ?)
Backdoors mandated by some three letters authority that cannot be released under an open source licences
code that implement something patented and the patent holders do not authorise the inclusion in open source code
Or contracts with former clients prohibiting "unfair compétition"...
or, or,
I know that the value of an Open Source Kermit-95 would be very law, it might be better on Windows than C-Kermit for some values of "better"...
but it's unlikelly that any futur use would be better served with an update of K95 rather than a modificiation of CK.
But the lesson on "freeing" code would be very interesting, and after all Columbia as a quite proheminent law school... so it would be interesting...
"Kermit" and "stinky" leads to some Miss Piggy jokes you really don't want to hear.
Depends if the box is completely bricked or "bootloader bricked".
If you can't even get a bootloader prompt then JTAG is the only game in town. You use JTAG to flash a bootloader and erase the rest of the flash ROM so the bootloader drops into a command prompt instead of trying to boot a kernel. Once you have a working bootloader, you typically use XMODEM to transfer the kernel and rootfs binaries across. Alternatively you use Ethernet or some other high-speed interface (USB, anyone?)
If you have a working bootloader, then you interrupt it on boot, drop to the command prompt and upload a new, (hopefully) working kernel and rootfs.
JTAG is only really necessary if your bootloader is totally screwed.
Looking over my Mom's shoulder, Kermit gave me my first glimpse of email, my first experience with vi (her preferred email editor), and indirectly I guess, put me on the engineering career path to where I am today... Curse you Kermit!