A book on how not to smash the SCO box in the next room with an axe whenever I type in a command that is supposed to be there, that there is a man page for, yet the command comes up not found.
That's easy to fix. Here's assuming you're using ksh:
$ q
ksh: q: not found
$ alias q=echo 'ksh: q: found'
$ q
ksh: q: found
$
Seriously, though, I have the same problem on Linux...
It's tongue in cheek. See where they talk about how having more little black things on the green makes it have more dimensions (slide 8 or 9, I think)?
You'd have to nail it high up for there to be any "damage". If you sever it at the bottom, you wind up with a free floating base that you can reattach. The point is that the entire elevator is in stable geosync orbit (actually, it's CM is in geosync), so that if the base is snapped, it doesn't fall.
I did. Snail mail. Before 9/11, so it should have been read. I even used the magic words "voting constituent". No response whatsoever. And no, it was a lot more literate than this post.
At my previous job, we used SCO ranging from Xenix SysV/286 (2.3.2) through ODT2 and ODT3 through OSR 5.0.2.
OSR5 had ELF and Shared Library support. And, I know it's popular to bash SCO here (almost as popular as MS bashing), but for us, it Just Worked(tm).
It was incredibly stable on a 286 (uptimes of about 6 months, and then only shut down for plant holidays). Uptimes of over a year on a 486/33 and P5-90.
Don't forget that the RPFJ allows MS to selectively release info, based on whether MS believes somebody's "business model" is worthwhile. Since MS has made its feelings about Open Source business models well known (through Mr. Mundie and Mr. Allchin), what are the odds that MS will use this loophole to deny information to OSS developers?
Slashdot Mirror
I still have my Windows 1.03 disks. It came on 5 360K floppies (plus one more for Windows Write).
You could either install to floppy or hard disk. It used a tiled window interface (instead of overlapping windows).
A book on how not to smash the SCO box in the next room with an axe whenever I type in a command that is supposed to be there, that there is a man page for, yet the command comes up not found.
That's easy to fix. Here's assuming you're using ksh:
$ q
ksh: q: not found
$ alias q=echo 'ksh: q: found'
$ q
ksh: q: found
$
Seriously, though, I have the same problem on Linux...
Personally, I just want a full tower, in the dimensions 1 x 4 x 9 (x 16 x 25..), painted black, that makes no sound.
Yeah, but what will you do when it starts eating Jupiter?
It's tongue in cheek. See where they talk about how having more little black things on the green makes it have more dimensions (slide 8 or 9, I think)?
That comment really is there in the old V6 source. I went looking for it.
I'm not sure Miguel *CAN* tell RMS to fuck off. Doesn't RMS hold the trademark on "GNU"?
Did Miguel really think that RMS would ignore the fact that a project, possibly the "showcase" project for GNU is going in this direction?
:)
He's on worse crack than the moderators
Geocities has no honor! We should kill them where they stand!
Oh My God, you killed the site! You Bastards!
The site has exceeded it's data limit, according to GeoCities!
You'd have to nail it high up for there to be any "damage". If you sever it at the bottom, you wind up with a free floating base that you can reattach. The point is that the entire elevator is in stable geosync orbit (actually, it's CM is in geosync), so that if the base is snapped, it doesn't fall.
Shit. I forgot to put the afteer the first "Fibre Channel". Next time I'll remember to use the "preview" button!
You've just stumbled across one of the main concepts behind the Storage Area Network [snia.org]. The biggest problem you have is bandwidth.
Dude, that's why most SANs are made out of Fibre Channel. FC is a 1GB transport that has a SCSI protocol on top (FCP-SCSI). 2GB FibreChannel is available, and work is currently under way on 10GB. In addition, FC is full duplex.
[I still need a versioning filesystem, like VMS though.]
I hate to say it, but SCO (yes, SCO) had a versioning filesystem in OSR5. HTFS (High Througput File System) had versioning support.
Are you certain about that?
I did. Snail mail. Before 9/11, so it should have been read. I even used the magic words "voting constituent". No response whatsoever. And no, it was a lot more literate than this post.
I know it's redundant and karma-whoring, but don't put spam in all caps when referring to UCE.
"SPAM"(tm) in all caps is a trademark of Hormel, who has good humor and grace regarding the term used for bulk-email.
My favorite part was where they said the Yamhill guys are working to ensure compatibility with AMD's 64-bit vision!
He didn't ask anyone for machines. He had bought a '386, and wasn't happy with what was out there, so he wrote his own.
At the risk of sounding like an AOL'er ... ME TOO.
At my previous job, we used SCO ranging from Xenix SysV/286 (2.3.2) through ODT2 and ODT3 through OSR 5.0.2.
OSR5 had ELF and Shared Library support. And, I know it's popular to bash SCO here (almost as popular as MS bashing), but for us, it Just Worked(tm).
It was incredibly stable on a 286 (uptimes of about 6 months, and then only shut down for plant holidays). Uptimes of over a year on a 486/33 and P5-90.
I looked for (and found) the infamous comment in V6...
"You are not expected to understand this".
It's there!
They're private. They don't have to put out a quarterly report.
Don't forget that the RPFJ allows MS to selectively release info, based on whether MS believes somebody's "business model" is worthwhile. Since MS has made its feelings about Open Source business models well known (through Mr. Mundie and Mr. Allchin), what are the odds that MS will use this loophole to deny information to OSS developers?
What do you get when you mulitply nine by six? 42.
It works in base 13.
Dude, the OP asked for DUAL proc mobos. K7T266A is for a uniprocessor system.
It would have been much more fun if the title had been:
"Robert Love, Preemptible Kernel Maintainer Interview" (no -ed).
Then we would have had three different parsings:
Robert Love, (Preemptible Kernel) Maintainer Interview
Robert Love, Preemptible (Kernel Maintainer) Interview
Robert Love, Preemptible (Kernel Maintainer Interview)
OK, so I have waaaaay too much time on my hands.