Yes, I couldn't remember if it was read-write or read-only, so I didn't want to say "fsck -f/", and I didn't want to reboot my machine mid-message to find out.
You're right that most of the time, Jaguar does do a prebinding fixup in the background when it something incorrectly prebound. That assumes that the prebinding isn't so badly hosed that it can't launch, however.
At least in my case, when 10.2.2 (or was it 10.2.3) did this to me (after crashing during optimization), doing an update_prebinding fixed the problem. Whether it will help for the 10.2.8 early adopters or not, of course, is anybody's guess.
As for the exit, updating prebinding does some scary stuff in the VM system. If it were me, I might continue booting, but giving advice to others, rebooting is a good idea.:-)
After you reboot, check in the file/Library/Logs/panic.log and paste a copy of the backtrace here on Slashdot, and I'll see if it's something obvious. No promises, of course.
On the other hand, if they were free, then there would be even more incentive to move away from the rather arcane notion of domain name ownership and towards a more reasonable system, whereby domain names would be shared among multiple companies/groups/people.
For example, you might go do www.apple.com, and the resulting page might ask "Do you want A. Apple Computer, B. Apple Records, C. Apple Growers Association of West Florida" or whatever.
However, because domain names are "owned" these days, there is little incentive to do this.
There are a lot of folks who do music and stuff with the Mac for fun, which was not mentioned. Some folks even do stuff with Photoshop, FC Express, and similar.
I'm in the final stages of production on a CD, and I'm drooling over the Dual G5 because my current G4 system was so inadequate that I had to borrow a faster one just to get through this project. I'm not even using a lot of effects, it's just that the few I am using suck lots of processor power.
The problem is that even for ordinary users, as soon as processor power improves, some company comes along with a new version of some piece of software, some new plug-in, some new video codec, whatever, that requires more horsepower to work reliably.
Marketing features are the great curse of processor performance....
On the other hand, this is the reason I always say that computer error messages should always be carefully screened by non-geeks. In fact, they should be screened by the worst-case end-user, such as someone's grandmother. At some point, it becomes harder to learn new tricks, so to speak, and even tiny little things like this error message can cause confusion. It doesn't make them stupid, just terrified that they'll screw something up.
If the message had read "Press a key to continue", there would be no confusion, even by the most computer illiterate....
Actually, using magnetic induction is much MORE likely to cause damage. Remember all the hoopla about people living under high tension lines and the EM radiation that surrounded those lines?
Microwave RF has little to no measurable effect on the body unless it's right at the natural oscillating frequency of water (about 2.4 GHz), and even then, the effects from such a miniscule amount of energy are minimal.
By contrast, magnetic fields have a very measurable effect on the body. Your blood is composed of about 7-28 umol/L, or if I did the math right, about 1 mg/L. Take a magnet and rub it near a vein sometime. If the field is strong enough, you get reorientation of the red blood cells, and eventually clumping of those cells. In sufficiently concentrated doses, the health effects could be significant.
That's not saying that subjecting oneself to the typical levels of EM fields around you is necessarily dangerous. It probably isn't. But a magnetic radiative transmitter in a wireless headset? I don't bloody think so. Imagine those red blood cells clumping into a clot-like mass in your brain. Happy stroke to you.
The reason so few people use bluetooth headsets is that the reason most people use headsets is to get the transmitter away from their heads. Replacing one transmitter with another is just plain nuts; whether it's bluetooth or magnetic just isn't the issue.
Frankly, I'd much rather see research going into higher density battery technologies like fuel cels rather than reducing energy consumption by shifting from microwave RF to EM. However, if we are moving in this direction, it is vitally important that it go through -extensive- safety testing before it is deployed. The potential for serious injury if the manufacturer doesn't set reasonable limits on EM emissions is too great to ignore without further study.
From what I can find, it launches in 2004, and might be put at 93 degrees W to replace Telstar 6... unless something changes between now and then, of course. It was originally scheduled for launch in 2002, but was reportedly delayed for a bandwidth upgrade.
PHB: First we get a big slingshot. Then we give Asok a small tank of air.
Dilbert: Won't he pop like a baloon a few seconds after he gets up there?
PHB: Will he have time to power-cycle the thingamahoey?
Dilbert: Well, I suppose so, but...
PHB: Will it be operational then?
Dilbert: I think so, but..
PHB: And this will save us how much money?
Dilbert: 25 million a day... look! That's not the point!
Wally: I think it's a brilliant plan, sir. Truly the finest.
Dilbert & Alice: WALLY!?!
Wally: What? I'm just saying....
Three days later
PHB: Okay, we're ready, Asok.
Asok: Are you sure this is such a good idea?
PHB: Perfectly safe. Perfectly safe.
Chunk....whoosh... splut...
(We see Asok's feet sticking out of the side of a building.)
Wait a sec, so you're saying that six years ago, one of the satellites in that family died just as AT&T was selling it to Loral, and now just as Loral is selling it to Intelsat, the same thing happed to another satellite? Yikes! Talk about your pre-sale jitters.
Yeah, and if we can't even agree on how big a billion is, how can we POSSIBLY agree on the definition of giga? I mean, why doesn't someone use saying that "they said it was a billion bytes, but it's really only a milliard"?:-)
I can think of cases where it makes a big difference---possibly more than 33%. It requires a modern interconnect bus like HyperTransport or PCI-X. It also requires a drive with a reasonably large cache, an application that performs multiple single-block reads out of the track(s) stored in the buffer, and an OS that doesn't do any read-ahead/behind.
Assuming you aren't just trolling, they're huge so that they have an extremely large surface area to minimize the airflow needed to get the same level of cooling, and thus minimize fan speed and the noise that accompanies it.
MHz-for-MHz, the G5 is a cooler processor than the G4---reportedly about 20W at 1.2 GHz, compared to 20W for a 1 GHz 7455.
Re:Misconception: Where the heat is comming from
on
G5 PowerBook "Challenge"
·
· Score: 4, Interesting
When people ask me about the temperature of the PowerPC processor, I like to tell them two stories.
#1. Where I work, engineers have a tendency to run their PowerMac machines 24x7 with the side open. No fan cooling the CPU. None. Try that with any PC processor, and it'll be toast (or at least shut itself off).
#2. Where I used to work, every trade show, we'd trot out an embedded PowerPC with... I think a G3 core. Guess what it didn't have on it? Fan? No, try again. Heatsink? Yup. No fan, no heatsink, and it was only slightly warm to the touch. You can probably imagine the shock on people's faces when we invinted them to touch a running CPU, forget the look of sheer confusion when it sat at about 38C.:-)
So yeah, PowerPC processors are not particularly hot, relatively speaking. The northbridge and GPU are both generally far hotter; any heat that you might feel is likely from one of those two.
Well, U.S. law would say "fixed in tangible form". However, it isn't part of the definition of a "copy".
Something I found interesting, in a section called "Scope of exclusive rights in sound recordings", was this:
From Title 17 USC, Chapter 1, Section 114:
The exclusive rights of the owner of copyright in a sound recording under clauses (1) and (2) of section 106 do not extend to the making or duplication of another sound recording that consists entirely of an independent fixation of other sounds, even though such sounds imitate or simulate those in the copyrighted sound recording.
Given that the audio encoding algorithms used in perceptual codecs, by definition don't reproduce the actual sounds, but rather the composition of a series of sinusoidal or similar functions (which, by definition, are distinct sounds unto themselves) that imitate those of the original sound... I think you can see where I'm going with this line of reasoning.
Not that this makes it ethically or morally right, but it is yet another potential hole in the RIAA's case. Now, of course, ASCAP or BMI could still come knocking on your door asking for composer/publisher royalties, but then again, they aren't the ones suing people.... I'd like to think they have more sense than that.
So if we assume that S is nonzero (and it clearly is, since they've already gotten -some- money), then we have
Z = S/(X * Y)
where S is some small constant 0<S<=1 where X and Y are approaching zero, hence (X*Y) is approaching zero, so Z is approaching infinity. It's gonna get ugly. Better pay up for those licenses.... Uh... yeah....
Actually, "rolled back" isn't quite accurate. Through the entire Jan 2003 product cycle, the old model was also available if you clicked on a box to the right that said something like "Mac OS 9 compatible machines: Click here" or in a little box at the bottom of the front page.
I suspect (but am not certain) that it would be more accurate to say that Apple stopped the line that was building the Jan. 2003 models and switched it to build G5s, while continuing the line that was still building the legacy Mac OS 9-compatible version....
Having read the FreeBSD info on this bug, it looks like it isn't possible to exploit it, period.
OpenSSH refuses to allocate a buffer over a certain size, but doesn't set the buffer size value back to its previous value. When this occurs, OpenSSH immediately calls fatal() to clean up and exit. The connection is closed, and the buffer is not reused.
The problem is that the cleanup code will, in some cases, attempt to zero the block at the larger size, resulting in OpenSSH crashing.
Because no data other than zeroes is every written to this buffer after the failed allocation (unless the FreeBSD folks missed something), this bug cannot be exploited except as a denial-of-service attack unless combined with some other exploit that allowed you to overwrite the exception handling vectors and add arbitrary code (in which case, there are probably much easier ways to perform the exploit).
In fairness, a README in an ftp directory is not inherently tied to the README in the distribution, and it's awfully easy to forget that the former is there. Just because it isn't documented very well in a file thrown into the ftp tree doesn't mean it isn't documented well.
Three media giants with the same large corporate agenda shoving crap down our throats and just trying to make it look different on the surface? Umm... we have that in the recording industry today, and look where it has gotten us. No, deregulation is -never- a good idea. If there's one thing we should have learned from the last two decades or so, it is that.
The problem is that the U.S. ALREADY has a tax of sorts to cover that. It's called "Audio CD-R Media". They're more expensive precisely for this reason, in case you don't remember. Your CD burner may also have an added fee to pay for the potential for lost copyright revenue, though I'm not sure whether it falls into the "home audio device" category or not, so it might not.
In any event, if you buy audio CD media and burn your downloads, you've paid for this music once, and now the RIAA is asking you to pay for it again, which would mean that they have no case whatsoever. STOP SETTLING, PEOPLE. Sheesh. The only way this extortion will stop is if someone actually fights it in court.
Slashdot Mirror
You're right that most of the time, Jaguar does do a prebinding fixup in the background when it something incorrectly prebound. That assumes that the prebinding isn't so badly hosed that it can't launch, however.
At least in my case, when 10.2.2 (or was it 10.2.3) did this to me (after crashing during optimization), doing an update_prebinding fixed the problem. Whether it will help for the 10.2.8 early adopters or not, of course, is anybody's guess.
As for the exit, updating prebinding does some scary stuff in the VM system. If it were me, I might continue booting, but giving advice to others, rebooting is a good idea. :-)
If this gives you an error that says that the filesystem is mounted read-only, then do:
Now do:
And the applicaiton launch problems should be gone.
For example, you might go do www.apple.com, and the resulting page might ask "Do you want A. Apple Computer, B. Apple Records, C. Apple Growers Association of West Florida" or whatever.
However, because domain names are "owned" these days, there is little incentive to do this.
I'm in the final stages of production on a CD, and I'm drooling over the Dual G5 because my current G4 system was so inadequate that I had to borrow a faster one just to get through this project. I'm not even using a lot of effects, it's just that the few I am using suck lots of processor power.
The problem is that even for ordinary users, as soon as processor power improves, some company comes along with a new version of some piece of software, some new plug-in, some new video codec, whatever, that requires more horsepower to work reliably.
Marketing features are the great curse of processor performance....
If the message had read "Press a key to continue", there would be no confusion, even by the most computer illiterate....
Microwave RF has little to no measurable effect on the body unless it's right at the natural oscillating frequency of water (about 2.4 GHz), and even then, the effects from such a miniscule amount of energy are minimal.
By contrast, magnetic fields have a very measurable effect on the body. Your blood is composed of about 7-28 umol/L, or if I did the math right, about 1 mg/L. Take a magnet and rub it near a vein sometime. If the field is strong enough, you get reorientation of the red blood cells, and eventually clumping of those cells. In sufficiently concentrated doses, the health effects could be significant.
That's not saying that subjecting oneself to the typical levels of EM fields around you is necessarily dangerous. It probably isn't. But a magnetic radiative transmitter in a wireless headset? I don't bloody think so. Imagine those red blood cells clumping into a clot-like mass in your brain. Happy stroke to you.
The reason so few people use bluetooth headsets is that the reason most people use headsets is to get the transmitter away from their heads. Replacing one transmitter with another is just plain nuts; whether it's bluetooth or magnetic just isn't the issue.
Frankly, I'd much rather see research going into higher density battery technologies like fuel cels rather than reducing energy consumption by shifting from microwave RF to EM. However, if we are moving in this direction, it is vitally important that it go through -extensive- safety testing before it is deployed. The potential for serious injury if the manufacturer doesn't set reasonable limits on EM emissions is too great to ignore without further study.
Dilbert: Won't he pop like a baloon a few seconds after he gets up there?
PHB: Will he have time to power-cycle the thingamahoey?
Dilbert: Well, I suppose so, but...
PHB: Will it be operational then?
Dilbert: I think so, but..
PHB: And this will save us how much money?
Dilbert: 25 million a day... look! That's not the point!
Wally: I think it's a brilliant plan, sir. Truly the finest.
Dilbert & Alice: WALLY!?!
Wally: What? I'm just saying....
Three days later
PHB: Okay, we're ready, Asok.
Asok: Are you sure this is such a good idea?
PHB: Perfectly safe. Perfectly safe.
Chunk....whoosh... splut...
(We see Asok's feet sticking out of the side of a building.)
PHB: For us, anyway.
That having been said, the latest CNN info says it was an electrical short of some kind.
Sorry, I was up until 4 a.m.fixing ftp.mklinux.org, and my parents called me at 8 a.m. with a computer problem.... *snores*
MHz-for-MHz, the G5 is a cooler processor than the G4---reportedly about 20W at 1.2 GHz, compared to 20W for a 1 GHz 7455.
#1. Where I work, engineers have a tendency to run their PowerMac machines 24x7 with the side open. No fan cooling the CPU. None. Try that with any PC processor, and it'll be toast (or at least shut itself off).
#2. Where I used to work, every trade show, we'd trot out an embedded PowerPC with... I think a G3 core. Guess what it didn't have on it? Fan? No, try again. Heatsink? Yup. No fan, no heatsink, and it was only slightly warm to the touch. You can probably imagine the shock on people's faces when we invinted them to touch a running CPU, forget the look of sheer confusion when it sat at about 38C. :-)
So yeah, PowerPC processors are not particularly hot, relatively speaking. The northbridge and GPU are both generally far hotter; any heat that you might feel is likely from one of those two.
Something I found interesting, in a section called "Scope of exclusive rights in sound recordings", was this:
Given that the audio encoding algorithms used in perceptual codecs, by definition don't reproduce the actual sounds, but rather the composition of a series of sinusoidal or similar functions (which, by definition, are distinct sounds unto themselves) that imitate those of the original sound... I think you can see where I'm going with this line of reasoning.Not that this makes it ethically or morally right, but it is yet another potential hole in the RIAA's case. Now, of course, ASCAP or BMI could still come knocking on your door asking for composer/publisher royalties, but then again, they aren't the ones suing people.... I'd like to think they have more sense than that.
Z = S/(X * Y)
where S is some small constant 0<S<=1 where X and Y are approaching zero, hence (X*Y) is approaching zero, so Z is approaching infinity. It's gonna get ugly. Better pay up for those licenses.... Uh... yeah....
I suspect (but am not certain) that it would be more accurate to say that Apple stopped the line that was building the Jan. 2003 models and switched it to build G5s, while continuing the line that was still building the legacy Mac OS 9-compatible version....
OpenSSH refuses to allocate a buffer over a certain size, but doesn't set the buffer size value back to its previous value. When this occurs, OpenSSH immediately calls fatal() to clean up and exit. The connection is closed, and the buffer is not reused.
The problem is that the cleanup code will, in some cases, attempt to zero the block at the larger size, resulting in OpenSSH crashing.
Because no data other than zeroes is every written to this buffer after the failed allocation (unless the FreeBSD folks missed something), this bug cannot be exploited except as a denial-of-service attack unless combined with some other exploit that allowed you to overwrite the exception handling vectors and add arbitrary code (in which case, there are probably much easier ways to perform the exploit).
In any event, if you buy audio CD media and burn your downloads, you've paid for this music once, and now the RIAA is asking you to pay for it again, which would mean that they have no case whatsoever. STOP SETTLING, PEOPLE. Sheesh. The only way this extortion will stop is if someone actually fights it in court.