As for GPS (the most accurate versions) two appliances at opposite ends of a vessel together with suitable calculations would give you the orientation of the vessel. (I have no idea if this is ever done.)
This is done with gyroscopes at each end of the ship. Inertial navigation is fantastically precise, though it does suffer from slow drift which need periodic corrections.
There will be a 5.5 release once 6.0 is done. It will likely be the last 5.x release, and it will also be the seventh 5.x release. Not too shabby. 6.0 is the start of the 6-STABLE branch. There will be a 6.1 release a few months after 5.5. After that, there will only be 6.x releases until it's time for 7.0. That will be in approximately 2 years.
99'er was the best mag, followed distantly by COMPUTE! Oh, the fond memories of slogging away entering code. And yeah, Parsec was my first cartridge game, and it was awesome. Good times, good times. Don't know about the Franklin Ace. I think I vaguely remember a friend having one, but nothing more than that. Oh, and Never Again Volunteer Yourself;-)
Yeah, I thought it was a fairly uncommon name too until a ran into another Scott Long from a nearby high school in Michigan, and again when I was in the Navy and got misrouted mails to another Scott Long with a similar job title, and again when I started getting colection notices meant for a Scott Long who lives about 20 miles from me. Go figure, small world. Ave!
Sorry, wrong. I challenge you to find any posting that said that 6.0 would be released in June. It was widely publicized that the release process would START in June and hopefully conclude by August. It was also widely publicized that it would be released when it was ready, and not before.
From a TI-99/4A... Interesting, my first home computer was also a TI-99/4A. When you're 10 years old and you have the Speech Synthesizer Module saying curse words on command for all of your friends, you rule!
Saying that the JNI exposes Java to the same C/C++ flaws as.NET/CLR is techinically true, but not very accurate. JNI was added to Java purely to allow the JVM to operate as a browser plugin. It wasn't something that Sun really liked or wanted to do since they really wanted Java to be a better, safer, and portable language. I think that this point was even discussed in some of the early books on JNI.
Microsoft, however, is actively looking to extend the CLR with a JNI-like interface. Why? To make it easier for people to port their legacy C/C++ apps to.NET. If you can keep most of your exsiting codebase untouched and just write.NET wrappers to access it, porting is theoretically easier. Microsoft doesn't care about platform portability (or safety, for that matter), they just want an easy way to get faster adoption.
Looking back at Java, JNI calls are hardly ever used. There are few books on the topic (I think an O'Rielly book on it was supposed to come out years ago on then got mysteriously pulled), and very few Java projects use it. It's a different mindset and a different set of goals between.NET and Java, and I think that Gosling is perfectly justified in pointing out the dangers of the path the Microsoft is taking.
One thing that is being overlooked here in the Windows vs. Mac shareware observation is that it's no longer possible to get a decent Windows development environment at a decent price. There are free or low-cost tools out there, but none have the bredth and depth to allow you to develop a decent app or game. It's not like 10 years ago when you could pick up a $99 copy of Turbo C++ and write a decent win31 program from it. So shareware is dead there because hobbiests can't justify the price tag for Visual Studio. Mac, on the other hand, has a decent environment with decent tools for doing Cocoa apps, and it's all free with the OS. Same goes for things like PalmOS. The tools are priced right to allow access to the hobbiest. That's what keeps shareware alive.
Yes, it's 3.4.2. While 3.4.3 was recently announced by the FSF, there certainly wasn't time to get it tested and properly integrated into 5.3. Anyways, it's one of a couple of typos in the announcement that I fixed in later emails.
[...] possible remake of Logan's Run and I would LOVE to see a version of that story that is filmed competantly.
Thank you for making my day. That story had so much potential but the screenwriter and director seemed to get caught up in the need to cut in 60's psychedelic sequences that really make little sense (at least without chemical assistance, I guess). I still love to watch it, but it's tough explaining to my wife why the scenes with naked hippie chicks are a requirement for good sci-fi.
Most of the bugs in your list are marked closed, and one is for a package that has nothing to do with disks or the OS. That leaves two entries that are relevant. Guessing the geometry is a lot harder than it sounds, especially if you already installed Windows or another boot loader and it guessed the geometry differently (as is the case with at least one of the entries in your list). This is a common problem in Linux, too. Windows is 'immune' to it because it'll choose whatever geometry it wants and leave any previously installed OS's stranded.
One must remember that artists can choose not to distribute their music this way. Notables are easy to recall - Dave Matthews Band, Metallica, Radiohead, The Beatles, etc.
Many artists have no say in how their music is distributed. Take the Beatles for example. A certain accused child molester in California has 50% say in how their recordings are distributed, while the surviving band members slowly grind their teeth and wait for him to go bankrupt.
[...]but what happens now with tons of radioactive wood buried and decomposing into the groundwater.
I wondered about this too, and my initial thought was that it was silly to just cut and bury the entire forest. Then it occurred to me that allowing all of that dead wood to stand would have made it very susecptible to a fire. A fire would re-release all of the absorbed radioactive particles back into the air, and it would have been another disaster down-wind. Since the area is evacuated, there would have been little chance to stop it once it started. So doing what they did was probably the lesser of evils.
4.6.1 never existed. It was going to exist, but some security issues appeared, so it was aborted. But you're right, I forgot about 3.5.1-RELEASE, mostly because it was never tagged in the CVS repository.
FreeBSD 4.1.1 existed also, and was tagged. However, it was a branch off of RELENG_4 instead of RELENG_4_1 and turned into a disaster. But yes, ever since 3.0, we've had few point releases.
As Colin pointed out in a peer post here, 5.2 had quite a long release cycle. If you look at the 5.2 release schedule you'll note that we spent almost 2 months on it. Add in that 5.1 was released in June of 2003, and you have quite a long dev cycle. We did the best that we could to manage risks in the 5.2 cycle, but shortly afterward it became apparent that there were some significant bugs in certain modules that didn't gain much attention until after the release was made.
The parent is absolutely correct. Patent abstracts have about as much bearing on reality as Marketing PowerPoint presentations and/. headlines. In this case, if you actually read the claims, it hints at describing UDF VAT rather than Red Book multi-session and/or ISO-9660. If someone has prior-art information that actually applies to the claims, I'd love to see it (and I'm sure that the Roxio lawyers would like to see it too).
OT: Since this is likely a submarine patent, why did they wait until now to sue Roxio when the stock is in the single digits and Napster 2.0 is flailing? Why didn't they sue several years ago when Roxio was in the high teens and EZCD was actually worth buying?
Slashdot Mirror
This is done with gyroscopes at each end of the ship. Inertial navigation is fantastically precise, though it does suffer from slow drift which need periodic corrections.
There will be a 5.5 release once 6.0 is done. It will likely be the last 5.x release, and it will also be the seventh 5.x release. Not too shabby. 6.0 is the start of the 6-STABLE branch. There will be a 6.1 release a few months after 5.5. After that, there will only be 6.x releases until it's time for 7.0. That will be in approximately 2 years.
99'er was the best mag, followed distantly by COMPUTE! Oh, the fond memories of slogging away entering code. And yeah, Parsec was my first cartridge game, and it was awesome. Good times, good times. Don't know about the Franklin Ace. I think I vaguely remember a friend having one, but nothing more than that. Oh, and Never Again Volunteer Yourself ;-)
Yeah, I thought it was a fairly uncommon name too until a ran into another Scott Long from a nearby high school in Michigan, and again when I was in the Navy and got misrouted mails to another Scott Long with a similar job title, and again when I started getting colection notices meant for a Scott Long who lives about 20 miles from me. Go figure, small world. Ave!
Are you the Scott Long that is overdue on his credit card payments? If so then I have a crapload of mail and phone messages for you =-D
Sorry, wrong. I challenge you to find any posting that said that 6.0 would be released in June. It was widely publicized that the release process would START in June and hopefully conclude by August. It was also widely publicized that it would be released when it was ready, and not before.
Scott Long is dying!!!
No I'm not!!!
From a TI-99/4A ...
Interesting, my first home computer was also a TI-99/4A. When you're 10 years old and you have the Speech Synthesizer Module saying curse words on command for all of your friends, you rule!
Mac OSX, which is very much a *BSD, has significantly higher market penetration than Linux, especially on the desktop.
Nor one who constantly casts Mark Hamill.
Microsoft, however, is actively looking to extend the CLR with a JNI-like interface. Why? To make it easier for people to port their legacy C/C++ apps to .NET. If you can keep most of your exsiting codebase untouched and just write .NET wrappers to access it, porting is theoretically easier. Microsoft doesn't care about platform portability (or safety, for that matter), they just want an easy way to get faster adoption.
Looking back at Java, JNI calls are hardly ever used. There are few books on the topic (I think an O'Rielly book on it was supposed to come out years ago on then got mysteriously pulled), and very few Java projects use it. It's a different mindset and a different set of goals between .NET and Java, and I think that Gosling is perfectly justified in pointing out the dangers of the path the Microsoft is taking.
One thing that is being overlooked here in the Windows vs. Mac shareware observation is that it's no longer possible to get a decent Windows development environment at a decent price. There are free or low-cost tools out there, but none have the bredth and depth to allow you to develop a decent app or game. It's not like 10 years ago when you could pick up a $99 copy of Turbo C++ and write a decent win31 program from it. So shareware is dead there because hobbiests can't justify the price tag for Visual Studio. Mac, on the other hand, has a decent environment with decent tools for doing Cocoa apps, and it's all free with the OS. Same goes for things like PalmOS. The tools are priced right to allow access to the hobbiest. That's what keeps shareware alive.
Why in the world would *BSD developers mention anti-slash?
I didn't. The post was a clever troll.
Yes, it's 3.4.2. While 3.4.3 was recently announced by the FSF, there certainly wasn't time to get it tested and properly integrated into 5.3. Anyways, it's one of a couple of typos in the announcement that I fixed in later emails.
[...] possible remake of Logan's Run and I would LOVE to see a version of that story that is filmed competantly.
Thank you for making my day. That story had so much potential but the screenwriter and director seemed to get caught up in the need to cut in 60's psychedelic sequences that really make little sense (at least without chemical assistance, I guess). I still love to watch it, but it's tough explaining to my wife why the scenes with naked hippie chicks are a requirement for good sci-fi.
Is it just that this list is unmaintained, or is 5.3 going out the door with some of these items left undone?
This is the list of things that will be fixed before 5.3 goes out the door. Releaseing 5.3-BETA3 is not the same as releasing 5.3-RELEASE.
Is this the version of 5.x that is to be considered stable?
That is the intention, yes.
Most of the bugs in your list are marked closed, and one is for a package that has nothing to do with disks or the OS. That leaves two entries that are relevant. Guessing the geometry is a lot harder than it sounds, especially if you already installed Windows or another boot loader and it guessed the geometry differently (as is the case with at least one of the entries in your list). This is a common problem in Linux, too. Windows is 'immune' to it because it'll choose whatever geometry it wants and leave any previously installed OS's stranded.
One must remember that artists can choose not to distribute their music this way. Notables are easy to recall - Dave Matthews Band, Metallica, Radiohead, The Beatles, etc.
Many artists have no say in how their music is distributed. Take the Beatles for example. A certain accused child molester in California has 50% say in how their recordings are distributed, while the surviving band members slowly grind their teeth and wait for him to go bankrupt.
[...]but what happens now with tons of radioactive wood buried and decomposing into the groundwater.
I wondered about this too, and my initial thought was that it was silly to just cut and bury the entire forest. Then it occurred to me that allowing all of that dead wood to stand would have made it very susecptible to a fire. A fire would re-release all of the absorbed radioactive particles back into the air, and it would have been another disaster down-wind. Since the area is evacuated, there would have been little chance to stop it once it started. So doing what they did was probably the lesser of evils.
Selling your books is very short sighted. You need to be thinking more of a long term stategy like giving blood and eating Raman noodles. ;)
Ah, but one must first come up with bus fare in order to get to the blood bank.
4.6.1 never existed. It was going to exist, but some security issues appeared, so it was aborted. But you're right, I forgot about 3.5.1-RELEASE, mostly because it was never tagged in the CVS repository.
FreeBSD 4.1.1 existed also, and was tagged. However, it was a branch off of RELENG_4 instead of RELENG_4_1 and turned into a disaster. But yes, ever since 3.0, we've had few point releases.
Almost seems like 5.2 was a bit of a rush job.
As Colin pointed out in a peer post here, 5.2 had quite a long release cycle. If you look at the 5.2 release schedule you'll note that we spent almost 2 months on it. Add in that 5.1 was released in June of 2003, and you have quite a long dev cycle. We did the best that we could to manage risks in the 5.2 cycle, but shortly afterward it became apparent that there were some significant bugs in certain modules that didn't gain much attention until after the release was made.
Where outside of Ann Arbor did you move? Places like Chelsea have enough big hills that wireless might already exist and be an option.
Excellent! Is this being discussed on any of the OSTA reflectors at all? I'm woefully behind on that email.
Hear! Hear!
/. headlines. In this case, if you actually read the claims, it hints at describing UDF VAT rather than Red Book multi-session and/or ISO-9660. If someone has prior-art information that actually applies to the claims, I'd love to see it (and I'm sure that the Roxio lawyers would like to see it too).
The parent is absolutely correct. Patent abstracts have about as much bearing on reality as Marketing PowerPoint presentations and
OT: Since this is likely a submarine patent, why did they wait until now to sue Roxio when the stock is in the single digits and Napster 2.0 is flailing? Why didn't they sue several years ago when Roxio was in the high teens and EZCD was actually worth buying?