Coherent? As in Coherent OS/32? If so, then they were successful enough to have been used by the TAB (betting agency) here in NZ. I don't know if the TAB still use it. I was a contractor with the TAB writing code to pull files off OS/32 scsi disks onto OS/2 disks (94/95), So I suspect OS/32 was being phased out.
[OT] though it had some problems (namely filename length) the filesystem of OS/32 had some interesting features: fixed length files that you pre-allocated (so they were guaranteed contiguous) and then filled in with two levels of support for dynamic files. A bit clunky, but interesting none-the-less. However, I'm glad I will probably never see one of those disks again:). At least the filesystem internals were documented...
I may have just made a complete feminazi out of myself for this, but oh well.
Not at all (IMHO), for two reasons: you treated the other person with respect and you are after respect as an equal. AIUI, feminazi are not after euality, but rather superiority. Sure, as you said, we all like the fealing of superiority, but a world made up of different equals (ie equal in caliber, but still individuals) would be a much better place. This makes me think of the Ghandi(?) quote someone has here on/. (could be one of the fortunes): imbalance of power corrupts, monopoly of power corrupts absolutely. This applies eqally well to male/female relationships and national/international politics.
That mutual respect is what I was looking for, and found in my wife (though we have some rough edges, mostly my fault as some of my values are incompatable with hers but hers are okay with me).
Will aLinux 3.0 support fault tolerand abacii? This vxab stuff from Stratacus has got my beads in a twist. I've got to merge the beads of two abacii (both of them having been previously used) and the docs are'nt the most informative. Unfortunatly the aLinux HOWTOs don't apply to aFTX. Arg, bloody proprietary abacii and OSs.
What's wrong with hair driers? I use one whenever I defrost the fridge, and it works really well. Other tools in my arsenal include (but is not limited to):
hot water (to provide extra head
screwdriver (I don't have a real ice pick)
towels (to catch the water)
fan (extra air flow)
Don't knock the humble hair dryer, they can do wonders. Hmmm, thinking of the one in the Space Balls movie, that would rip through my fridge right quick, and wouldn't do too bad a job on the mammoth either.
Tripple cool. I remembered the meaning of waimea (it was the name of the schools I went to for 1st and 4th-6th forms (intermediate and college (twas a complicated system in New Zealand at the time, it's now grades)), I understood your intentions, and I like recursive acronyms (though I didn't notice it when I went to your web page).
NOTE: I have one problem. Isn't creating your own encryption algorithm considered unsafe without heaps of peer review? Or is algorithm realy supposed to be protocol, which wouldn't fit?
Interesting choice of names, I believe it's Maori for `little water' (from memory, been a long time). Now what I'm wandering is how a little water would apply to a `stream cipher encryption algorithm'. Hmmm, as I was typing this, I got it: little water -> stream. Clever (I take it this was deliberate).
Ah, now that's a good point. Now we have two free distributions using the two main package managers. This is a Good Thing(tm). Now those that like apt have their free distro (always have, of course) and those that like RPM have theirs.
I like this very much. I'm thinking my next Red Hat upgrade will be RMS Linux (killall -STONE bird:).
Not true at all. I used to get hold of magnesium strips at school (chem class) and light them with a bunsen burner. Way cool. I also used to shave of small chunks from those metal pencil sharpeners (avail here in NZ and AU, don't know about elsewhere) and light those as well. Also, party springlers are mostly magnesium and they shouldn't have any problem lighting a larger chunk of the stuff. I've never dealt with magnesium powder, only solid bits. Are you perhaps thinking of aluminum (or aluminium, depending on your preferred spelling)?
Whan my wife was pregnant with our son (second child), her waters broke at just shy of 26 weeks and he was expected to be delivered shortly. My wife and I were discussing that if he did arrive early, should we allow him to die on his own if that was the way it was going to be (ie, minimal intervention) so that he wouldn't later in life suffer from any disabilities caused by his premature birth. Fortunatly, he held in there (with only bed rest, steroids (for his lungs, just in case) and lots of antibiotics (to prevent infection from the torn sack)) and wasn't born until 4 days before his due date (the sack closed up again). Mind you, he came out backwards, with a knot in his cord (which broke as the doctor was trying to extricate the placenta), and was rather blue (due to the knot), but only needed 6 hours of O2. He's been basicly fine since; if he suffered any brain damage, I'ld hate to see what he would have been like without it. He's a real terror @ 4:), real geek material.
This may be redundant from your POV, but I feel this needs to be stated, at least for others.
I don't know about your percentage there (ie I think 90% is a little high, 70-80%, maybe). Why? DJGPP is quite popular amounst knowledgable dos/windows users, especially the younger ones. Before djgpp got a newsgroup (comp.os.msdos.djgpp IIRC), the mailing list had something like 500 users, and this was in 95. In 97, the newsgroup/mailing list (gatewayed) was producing about 100 messages a day, so I'ld guess that at the time there were about half as many people posting to c.o.m.d. as there are to the current lk list. Many, if not most, of the djgpp users `got' the free software bit, though mainly the beer part and there were plenty of license flamewars in that sub-community. In fact, it was djgpp that got me into linux (in a round about way).
However, you're right that without free tools, there's not a lot of point to free software, but most of the gnu utilitles have been ported to djgpp, so other than the OS itself, dos programming these days is just a free as for Linux, and very easy to install (download several.zip files, unzip, adjust autoexec.bat and off you go). I haven't really used djgpp for about two years now, but that's because I've been using Linux. I'm not sure I'ld have been as comfortable starting out on my Linux adventure if it hadn't been for djgpp as that environment got me used to the tools used in Linux (they're essentially the same).
but as has been discussed in previous articles, it's not particularly valid. Not applying those patches (whether they come as a single bundle or a multitude) is sheer laziness and a poor excuse. I believe that if the same thing happened to the network I look after at work for the same reasons, I would be (justifiably) fired. If not the first time, then definitly if it happened again (ie, I didn't learn from my mistake).
Yes, your right. Maybe I should have said that software wants to be that way. People with their desire for choices (or more changing requirements) pull software into multitudes, while the software itself (via other people) pulls itself back together by merging the good features and dumping the bad. I guess it's really a struggle between many and one. People like one stop shopping, but if it doesn't meet their needs, they will either look elsewhere or create that elsewhere.
BTW, don't get me wrong, I like choice. However, if there's only one `choice' available, at least let it be good.
Ah, but you're forgetting that the old Doom license didn't really allow proprietary changes either. Sure, some groups did something like this, but they couldn't sell the results, and Microsoft certainly couldn't.
Although I agree with you in general about the retroactivity of changing a license, I'm not sure about this case, but it doesn't matter. Many groups will change to the GPL anyway because ``it's the right thing'', and those that don't will either eventually langush while the GPLed versions (version? they might all merge) flourish. The non GPLed versions might eventually be forced to turn GPL as features in the GPLed versions become popular and the non-gpled versions start to incorporate those changes. I expect all versions of doom will eventually merge back into one.
In general, software (open or closed) seems to be much like Highlander: there can be only one.
Slashdot Mirror
[OT] though it had some problems (namely filename length) the filesystem of OS/32 had some interesting features: fixed length files that you pre-allocated (so they were guaranteed contiguous) and then filled in with two levels of support for dynamic files. A bit clunky, but interesting none-the-less. However, I'm glad I will probably never see one of those disks again:). At least the filesystem internals were documented...
That mutual respect is what I was looking for, and found in my wife (though we have some rough edges, mostly my fault as some of my values are incompatable with hers but hers are okay with me).
Sure, but if your operations aren't thread-save, you run the risk of corrupting your beads and threads resulting in a tangles mess.
Will aLinux 3.0 support fault tolerand abacii? This vxab stuff from Stratacus has got my beads in a twist. I've got to merge the beads of two abacii (both of them having been previously used) and the docs are'nt the most informative. Unfortunatly the aLinux HOWTOs don't apply to aFTX. Arg, bloody proprietary abacii and OSs.
- hot water (to provide extra head
- screwdriver (I don't have a real ice pick)
- towels (to catch the water)
- fan (extra air flow)
Don't knock the humble hair dryer, they can do wonders. Hmmm, thinking of the one in the Space Balls movie, that would rip through my fridge right quick, and wouldn't do too bad a job on the mammoth either.I hope that's feirenhight (sp?), a uterus won't work too well when it's boiled.
'Cause we killed the mammoths off in the first place?
should not be there. If it is, that would be the first /. poll that covered all possible choices: just not allowed:)
I think you meant MCP (Master Control Program). But, yeah, cool. Hrmm, all we need now is a Tron level for doom....
Excellent, I hope your algorithm passes muster.
NOTE: I have one problem. Isn't creating your own encryption algorithm considered unsafe without heaps of peer review? Or is algorithm realy supposed to be protocol, which wouldn't fit?
Interesting choice of names, I believe it's Maori for `little water' (from memory, been a long time). Now what I'm wandering is how a little water would apply to a `stream cipher encryption algorithm'. Hmmm, as I was typing this, I got it: little water -> stream. Clever (I take it this was deliberate).
I like this very much. I'm thinking my next Red Hat upgrade will be RMS Linux (killall -STONE bird :).
- They can't include Qt 1.x because it's non-free.
- They can't include KDE stable because it won't run without Qt 1.x.
- There's no point in including Qt 2.x as few if any packages use it yet
Basicly, Qt 2 would be a waste of space until stable versions of KDE start using it.Not true at all. I used to get hold of magnesium strips at school (chem class) and light them with a bunsen burner. Way cool. I also used to shave of small chunks from those metal pencil sharpeners (avail here in NZ and AU, don't know about elsewhere) and light those as well. Also, party springlers are mostly magnesium and they shouldn't have any problem lighting a larger chunk of the stuff. I've never dealt with magnesium powder, only solid bits. Are you perhaps thinking of aluminum (or aluminium, depending on your preferred spelling)?
Ouch, keep away from party sparklers! Mind you, very good for avoiding black hats: Oh oh, here come the MIB... fzzzzFZZZZZZZ. Haha, can't get my data.
- 1 Mile = 1.609344 km (1.6 ok, you're using 1.666...
- 1 metre/sec = 3.6 kph (not 3.9)
- G, otoh, is good enough:)
Using this, I get 1185m. Chucking on the extra 120m from your result would add a nice (though expensive) safety margin.I get 8.9 seconds. 600Mph->960kph->266.67mps. 266.67/30 (3g * 10ms^2)=8.8888.... Still, 8-9 thousand lps of fuel is alot.
Whan my wife was pregnant with our son (second child), her waters broke at just shy of 26 weeks and he was expected to be delivered shortly. My wife and I were discussing that if he did arrive early, should we allow him to die on his own if that was the way it was going to be (ie, minimal intervention) so that he wouldn't later in life suffer from any disabilities caused by his premature birth. Fortunatly, he held in there (with only bed rest, steroids (for his lungs, just in case) and lots of antibiotics (to prevent infection from the torn sack)) and wasn't born until 4 days before his due date (the sack closed up again). Mind you, he came out backwards, with a knot in his cord (which broke as the doctor was trying to extricate the placenta), and was rather blue (due to the knot), but only needed 6 hours of O2. He's been basicly fine since; if he suffered any brain damage, I'ld hate to see what he would have been like without it. He's a real terror @ 4 :), real geek material.
I don't know about your percentage there (ie I think 90% is a little high, 70-80%, maybe). Why? DJGPP is quite popular amounst knowledgable dos/windows users, especially the younger ones. Before djgpp got a newsgroup (comp.os.msdos.djgpp IIRC), the mailing list had something like 500 users, and this was in 95. In 97, the newsgroup/mailing list (gatewayed) was producing about 100 messages a day, so I'ld guess that at the time there were about half as many people posting to c.o.m.d. as there are to the current lk list. Many, if not most, of the djgpp users `got' the free software bit, though mainly the beer part and there were plenty of license flamewars in that sub-community. In fact, it was djgpp that got me into linux (in a round about way).
However, you're right that without free tools, there's not a lot of point to free software, but most of the gnu utilitles have been ported to djgpp, so other than the OS itself, dos programming these days is just a free as for Linux, and very easy to install (download several .zip files, unzip, adjust autoexec.bat and off you go). I haven't really used djgpp for about two years now, but that's because I've been using Linux. I'm not sure I'ld have been as comfortable starting out on my Linux adventure if it hadn't been for djgpp as that environment got me used to the tools used in Linux (they're essentially the same).
but as has been discussed in previous articles, it's not particularly valid. Not applying those patches (whether they come as a single bundle or a multitude) is sheer laziness and a poor excuse. I believe that if the same thing happened to the network I look after at work for the same reasons, I would be (justifiably) fired. If not the first time, then definitly if it happened again (ie, I didn't learn from my mistake).
BTW, don't get me wrong, I like choice. However, if there's only one `choice' available, at least let it be good.
Although I agree with you in general about the retroactivity of changing a license, I'm not sure about this case, but it doesn't matter. Many groups will change to the GPL anyway because ``it's the right thing'', and those that don't will either eventually langush while the GPLed versions (version? they might all merge) flourish. The non GPLed versions might eventually be forced to turn GPL as features in the GPLed versions become popular and the non-gpled versions start to incorporate those changes. I expect all versions of doom will eventually merge back into one.
In general, software (open or closed) seems to be much like Highlander: there can be only one.
*strains of Taps..*
Thanks, I'll look it up. Hmm, the title implies an interesting story line.