HCF? Anything to do with Halon? I don't know what you mean, sorry Rez.
"lp0 on fire!" was a Linux kernel message that was removed sometime in the 2.4.x series. It's historical - and in the Linux FAQ, but still removed because some people thought it was misleading, which in the two times I have witnessed it, indeed was.
I'm sure one day, someone will again suffer a printer fire and instead be informed something along the lines of "check printer connection and power" and I'd rather have had two false alarms and the sense of security rather than nothing;)
Seriously though: the other day my smoke detector just went off in the middle of the day, which is when I would normally be halfway through my eight hour sleep. I was happy for two reasons.
That it just went of for no reason rather than not going off when there was a very good reason.
That I woke, immediately knew what it was, checked that everything was ok and thanked the detector for its vigilance before I took out his battery and sent him along to the dump.
TIA for your (-1, Offtopic)
Funny how reinstalling Windows seems to fix "power supply first, then memory, HD" for another four months or so. I used to keep a copy of '98 installed just so I could play my favourite game once a month or so. Last time it shat itself, the other three OS's the machine booted seemed fine.
Because dodgy hardware doesn't usually even boot, and Win9x getting "really flakey" doesn't often point to bad hardware. And believe me, I've seen plenty of 9x machines since 9x.
Where the hell did you read it was a refuelling station? It's one thing not to read the article, it's another to boldly quote something that was never [printed].
Just because there a few tents something flat enough to land a plane on, doesn't mean mean they want to be in the business of shipping tons (this guy needs 400 litres) of gas, keeping it, and manning the pumps 24/7.
I do, however, see your point about refusing to sell him the fuel. If they change their mind now, it's out in the open, whereas if we weren't hearing about it, they could slip him the gas he needs if he strips down to his socks and runs around the base, or something. For being a dork, and allowing two hours spare fuel, when his destination was thirty hours away.
Funny how/. always links to the most uninformative source, misinterprets it and writes a headline. I think I'll work on a perl script to pipe the front page through. Remove the commentry, show links to comments, articles and all linked to in the comments. Then a quick s/goatse.cx//g, because I know someone will mention that too and bingo!
I can click on the urls in E-term and navigate slashdot with it.
Inevitably, "hacker" will authoritively mean - loosely here - "sneaking into someone else's computer", because that has been common use in the English speaking community. "But we're on slashdot!" I hear [the grandparent] saying - Go screw, we speak English on Slashdot, and just because you and and few million others feel the need to remove the "crackers" from your class, doesn't mean the English speaking community will adopt it.
You'd better get over the hacker/cracker thing sometime soon. The GNU/General Public are always going to call someone who brings down/breaks into computers a Hacker. I should still be round in 30 years if you care to prove me wrong, because you can't currently.
>There is abosolutely _ZERO_TRUST_ in the gentoo system
Don't you mean "total trust" in the system, in that the users "trust" the rsync servers not to be r00t3d, somewhat optimistically?
Before you hit me with a flamebait, _I_ have actually been one of those people, trusting whatever rsync server I hit, and this has been an eye-opener for me.
If I had a nickel for every dupe on slashdot I would be rich!!
Say slashdot runs one dupe a day. I guess a nickel is $0.05, I don't know for sure. 365.25 * 0.05 = $18.25 P.A.
At that rate, you could have saved $100,000 in only 5480 years - by that time the compounding interest on what you had saved so far is bound to have made it up to the $500,000 you require.
I'm sure if you were the first person to ask Malda for a nickel for every dupe, he'd probably agree to it. You ought to go ahead and patent your business model.
Yes, the decibel is a logarithmic scale. No, 40dB is not 10^40 times louder. For a fan to "run a bearing" and make 40dB more noise, I find quite plausible.
Encrypting shouldn't make the resulting code bigger, except for rounding the size up to the next block size of the cypher. Encrypting something over and over with the same algorithm doesn't really have a cryptographic benefit.
Would us sending these slashdot stories to the major cable news outlets make a difference????
Yeah, but you'd have to set your score threshold up higher for any no-tech to take/. seriously. Set it at +4 and all you'll be left with are ASCII cut&pastes of the article and all the "I for one welcome our code-stealing overlords" posts.
I imagine if anything does come of the fiaSCO, it'll be that judges wind up a little more educated about code and IP, and come to the realisation that when one types code, there's actually a pretty good chance that you'll be typing exactly the same instructions as somebody else one day did. If somebody were to knowingly steal code from closed software, would they not have the common sense to at least change variable names, order of instructions etc. so as at least not to be "greppable"?
I imagine the judges know full well that this is a frivolous lawsuit. They also know that it can't be thrown out on those grounds. If somebody has found a loophole in the legal system, they actually have every right to try and exploit it.
Your point about stock fraud is valid, too - and I would imagine that the ex-holders of such would be taking good care to cover their asses, for they surely must know that this is next, all it needs is a complaint.
Okay, so why is MiB the "correct notation" for memory, but the MB, GB etc the "correct notation" for disks?
I agree the manufacturer is not wrong to call an 80 billion byte disk an 80GB disk. I am saying it would be more appropriate to sell it as a 73GiB (or whatever it works out) disk.
Some used a MB to mean 1,024,000 bytes which is not 1MB nor 1MiB. Sorry, but I don't think it's an honest mistake.
"The hard drive manufacturers are not trying to mislead anybody. They are using the correct notation for the capacity of the drive. 1GB is 1,000,000,000 bytes; 1GiB is 1,073,741,824."
Best outcome for the free software guys would be a policy that "If you buy defective software (any SW with any bug), you can return it to your vendor and get your money back.".
Yeah, that'd be great for them. Every single packaged linux dist that sells will inevitibly be refunded at some stage, because at least one package on it will be deemed to have a bug within a few months.
The Classics and SE's were a monitor & computer in one unit with a carry handle built into the top, making them very much like a hammer that would be thrown at the olympics.
The later LC and PowerMacintosh series didn't lend themselves to this activity much; indeed I'd be interested to see anyone lob a 9600 more than 8m.
Your fly is not a moon because you are not a planet, and the fly is not obriting. It's "fly"ing.
Why bother trying to make a definition on something that we really have no idea how to define. Every new star or system we find doesn't usually have much in common with our own, and we'd have to constantly redefine it all the time anyway.
Basically, you can call it a moon or a rock or whatever you like, at the end of the day it's a whopping great big chunk of something and probably doesn't care what you call it.
Slashdot Mirror
And furthermore, is anyone surprised?
As for the sig, I think I'll change that one day soon, I do now and then. I must say I don't get yours though...
~REZ~(630123) Who'd fake being me anyway?
"lp0 on fire!" was a Linux kernel message that was removed sometime in the 2.4.x series. It's historical - and in the Linux FAQ, but still removed because some people thought it was misleading, which in the two times I have witnessed it, indeed was.
I'm sure one day, someone will again suffer a printer fire and instead be informed something along the lines of "check printer connection and power" and I'd rather have had two false alarms and the sense of security rather than nothing ;)
Seriously though: the other day my smoke detector just went off in the middle of the day, which is when I would normally be halfway through my eight hour sleep. I was happy for two reasons.
TIA for your (-1, Offtopic)
Sometimes I'm so drunk I type halt in the wrong xterm. That's worse.
Because dodgy hardware doesn't usually even boot, and Win9x getting "really flakey" doesn't often point to bad hardware. And believe me, I've seen plenty of 9x machines since 9x.
I do, however, see your point about refusing to sell him the fuel. If they change their mind now, it's out in the open, whereas if we weren't hearing about it, they could slip him the gas he needs if he strips down to his socks and runs around the base, or something. For being a dork, and allowing two hours spare fuel, when his destination was thirty hours away.
Just Kiwis and Yanks.
Funny how /. always links to the most uninformative source, misinterprets it and writes a headline. I think I'll work on a perl script to pipe the front page through. Remove the commentry, show links to comments, articles and all linked to in the comments. Then a quick s/goatse.cx//g, because I know someone will mention that too and bingo!
I can click on the urls in E-term and navigate slashdot with it.
Inevitably, "hacker" will authoritively mean - loosely here - "sneaking into someone else's computer", because that has been common use in the English speaking community. "But we're on slashdot!" I hear [the grandparent] saying - Go screw, we speak English on Slashdot, and just because you and and few million others feel the need to remove the "crackers" from your class, doesn't mean the English speaking community will adopt it.
You'd better get over the hacker/cracker thing sometime soon. The GNU/General Public are always going to call someone who brings down/breaks into computers a Hacker. I should still be round in 30 years if you care to prove me wrong, because you can't currently.
Don't you mean "total trust" in the system, in that the users "trust" the rsync servers not to be r00t3d, somewhat optimistically?
Before you hit me with a flamebait, _I_ have actually been one of those people, trusting whatever rsync server I hit, and this has been an eye-opener for me.
Have another $1.00 P.A. for expenses.
If I had a nickel for every dupe on slashdot I would be rich!!
Say slashdot runs one dupe a day. I guess a nickel is $0.05, I don't know for sure. 365.25 * 0.05 = $18.25 P.A.
At that rate, you could have saved $100,000 in only 5480 years - by that time the compounding interest on what you had saved so far is bound to have made it up to the $500,000 you require.
I'm sure if you were the first person to ask Malda for a nickel for every dupe, he'd probably agree to it. You ought to go ahead and patent your business model.
Just keep it to yourself and mod me down thanks.
Umm, call me crazy, but are you new here?
Yes, the decibel is a logarithmic scale. No, 40dB is not 10^40 times louder. For a fan to "run a bearing" and make 40dB more noise, I find quite plausible.
Encrypting shouldn't make the resulting code bigger, except for rounding the size up to the next block size of the cypher. Encrypting something over and over with the same algorithm doesn't really have a cryptographic benefit.
Yeah, but you'd have to set your score threshold up higher for any no-tech to take /. seriously. Set it at +4 and all you'll be left with are ASCII cut&pastes of the article and all the "I for one welcome our code-stealing overlords" posts.
I imagine if anything does come of the fiaSCO, it'll be that judges wind up a little more educated about code and IP, and come to the realisation that when one types code, there's actually a pretty good chance that you'll be typing exactly the same instructions as somebody else one day did. If somebody were to knowingly steal code from closed software, would they not have the common sense to at least change variable names, order of instructions etc. so as at least not to be "greppable"?
I imagine the judges know full well that this is a frivolous lawsuit. They also know that it can't be thrown out on those grounds. If somebody has found a loophole in the legal system, they actually have every right to try and exploit it.
Your point about stock fraud is valid, too - and I would imagine that the ex-holders of such would be taking good care to cover their asses, for they surely must know that this is next, all it needs is a complaint.
or for that matter: /dev/ttyofunsuspectinguser
cat
I agree the manufacturer is not wrong to call an 80 billion byte disk an 80GB disk. I am saying it would be more appropriate to sell it as a 73GiB (or whatever it works out) disk.
Some used a MB to mean 1,024,000 bytes which is not 1MB nor 1MiB. Sorry, but I don't think it's an honest mistake.
Shouldn't the "correct notation" then, be GiB?
Ah, the 32 gig limit. But that's the 32 x 2^30 B and not 30 x 10^6, so you could comfortably fit, oh, say /afiftygigdrive/ in it no worries.
Yeah, that'd be great for them. Every single packaged linux dist that sells will inevitibly be refunded at some stage, because at least one package on it will be deemed to have a bug within a few months.
Yep, best outcome alright.
The Classics and SE's were a monitor & computer in one unit with a carry handle built into the top, making them very much like a hammer that would be thrown at the olympics.
The later LC and PowerMacintosh series didn't lend themselves to this activity much; indeed I'd be interested to see anyone lob a 9600 more than 8m.
Laden or unladen?
Why bother trying to make a definition on something that we really have no idea how to define. Every new star or system we find doesn't usually have much in common with our own, and we'd have to constantly redefine it all the time anyway.
Basically, you can call it a moon or a rock or whatever you like, at the end of the day it's a whopping great big chunk of something and probably doesn't care what you call it.