...at least at our house. The old Performa is very happy with Debian, and the Umax dualie is good with NetBSD. And the iBook SE we used to have was mucho smooth under OpenBSD. Which flavor is best for your aged box that's not up to snuff for OS X depends on it's architecture and your needs/experience. Somebody posting about moving their older mac to YDL made me grin.
We'll prolly wait on the 970 before buying another Mac. In the meantime our new cheap Intel mobo tower runs XP and Knoppix on the HD (reiser FS) just fine, on the metal or under VMware.
But we won't be in the market for a new box (prolly laptop for Her Highness:-) until later this year, so we'll see what ends up being out there!
...although the manuals are VERY badly translated from Chinese. Had no trouble with a Buffalo AP with various Windows flavors, Mac OS 9 and X, and Linux/BSD releases...but their Windows config program for their 802.11b Card was very icky (it was much easier to get working under Linux, IIRC it was a standard Lucent chipset:-)
Anyway, 2 years ago their gear was the cheapest 802.11b I found, and worked fine (Windows users deserve their pain, no?)
And the WOPR (sp?) was an Apple II
on
IMSAI Series Two
·
· Score: 1
I remember when I first saw Wargames in the theatre with my friend Ken, when he broke into the WOPR (how's that spelled again? horrible memory for proper names) we busted out laughing, and got "shusshhhed" by everyone, as no one else saw anything remotely funny in the very serious scene onscreen.
We were junior high school 6502 machine coders, and the WOPR was an Apple IIe ROM monitor dump.
I still laugh my ass off every time I've seen that movie, the WOPR is an Apple II!! Oooohhhhhh, the power!
If I'm writing something useful as a general systems tool, i.e. it somehow could advance the art or science of computing, then I request/negotiate that my employer or client open source it/assign me rights, in writing/contractually.
If the code I'm writing is specific to the systems or business of my employer/client, then I would not even consider doing it other than as work for hire.
In the first case, they are paying you to make better tools, usually so you can move on to the second case...building their "house" or software specific to their business and/or industry.
The first case gains me reputation, the second gains them competitive advantage.
That's just how I view things philosophically for myself:-)
Slashdot Mirror
....you just need to:
/usr/ports/editors/emacs21
:-)
# cd
# make
# make install
or you could just be a pansy and use the pkg_add url that someone else posted to grab that yummy emacs21 binary.
But you don't get all of the elisp sources that way...you DO want the elisp sources, don't you?
...was telling the audience (mostly non-technical) about IPv6.
He mentioned how many addresses, and then asked if anyone knew what that meant.
He said that it would mean there would be enough for every frickin appliance, and it could run Java on it, and did anyone know what THAT meant?
Of course no one was supposed to have any answers, it was almost all PHBs there (I got dragged along to man a cursed booth).
So I raised my hand and said "So you can get up in the morning and reboot your toaster?"
EVERYONE burst out laughing!
...at least at our house. The old Performa is very happy with Debian, and the Umax dualie is good with NetBSD. And the iBook SE we used to have was mucho smooth under OpenBSD.
:-) until later this year, so we'll see what ends up being out there!
Which flavor is best for your aged box that's not up to snuff for OS X depends on it's architecture and your needs/experience.
Somebody posting about moving their older mac to YDL made me grin.
We'll prolly wait on the 970 before buying another Mac. In the meantime our new cheap Intel mobo tower runs XP and Knoppix on the HD (reiser FS) just fine, on the metal or under VMware.
But we won't be in the market for a new box (prolly laptop for Her Highness
...although the manuals are VERY badly translated from Chinese. Had no trouble with a Buffalo AP with various Windows flavors, Mac OS 9 and X, and Linux/BSD releases...but their Windows config program for their 802.11b Card was very icky (it was much easier to get working under Linux, IIRC it was a standard Lucent chipset :-)
Anyway, 2 years ago their gear was the cheapest 802.11b I found, and worked fine (Windows users deserve their pain, no?)
I remember when I first saw Wargames in the theatre with my friend Ken, when he broke into the WOPR (how's that spelled again? horrible memory for proper names) we busted out laughing, and got "shusshhhed" by everyone, as no one else saw anything remotely funny in the very serious scene onscreen.
We were junior high school 6502 machine coders, and the WOPR was an Apple IIe ROM monitor dump.
I still laugh my ass off every time I've seen that movie, the WOPR is an Apple II!! Oooohhhhhh,
the power!
If I'm writing something useful as a general systems tool, i.e. it somehow could advance the art or science of computing, then I request/negotiate that my employer or client open source it/assign me rights, in writing/contractually.
:-)
If the code I'm writing is specific to the systems or business of my employer/client, then I would not even consider doing it other than as work for hire.
In the first case, they are paying you to make better tools, usually so you can move on to the second case...building their "house" or software specific to their business and/or industry.
The first case gains me reputation, the second gains them competitive advantage.
That's just how I view things philosophically for myself
I was gonna email you about it, but your address isn't displayed (duh). Drop me a line at slashdot@arkhein.net