Actually, here are some proposed additions for GPL Version 3:
For I testify unto every man that heareth the words of the license of this code, If any man shall add unto these things, RMS shall add unto him the plagues that are written in this license.
And if any man shall take away from the words of the license of this code, RMS shall take away his part out of the license to this code, and out of the open bazaar, and from the things which are written in this license.
NFS may have it's own problems, but the one I'm speaking of is in Appletalk.
I guess this is public information, so I'll post it here.
Many Xinet customers running Mac OSX 10.3 clients have experienced, at one time or another, data loss or errors while saving from OSX-native applications or copying files to the server using the Finder. Though there are several causes of this unexpected data loss, Xinet has tracked the most severe of these cases as Xinet bug #04021. In this bug, files were silently "cross-linking" at time of save or write. That is, the data from a working file might silently overwrite another file on the filesystem. Clients would see the results of this bug when they attempted to open a file and it was empty (zero-length) or when they opened a file and it contained incorrect data. There was no indication to the user that data was written to the wrong place during save, nor were there any errors to indicate that a save had failed. After extensively researching the cause of this error, Xinet has concluded that OSX 10.3 clients are sensitive to a long-standing function of Xinet FullPress/KA-Share: File ID reuse. Our immediate reuse of File IDs causes OSX 10.3 to send data to an incorrect location at time of write.
Alleviating the symptoms of cross-linking files from OSX 10.3 clients has been a very high priority for Xinet engineering. Though we cannot control the client behavior, we have a patch that will remedy the problem as best we can from the server side. This patch adds a delay in File ID reuse. In the past, File IDs were available for reuse immediately after being freed. In this new ksd, File IDs are reserved from reuse for a user-configurable period of time. We have tested this in-house and at selected customer sites, and have found that it significantly reduces errors and silent data loss at time of save from OSX 10.3 client systems. This patch is available for download from our web site.
Bear in mind, this patch reduces the occurrance of errors introduced in OSX 10.3. It will not eliminate all of them, but it will end the catastrophic silent data loss caused by the cross-linking of files at time of save. Xinet has been able to reproduce other incorrect OS 10.3 saving behavior outside a FullPress/KA-Share environment, and some even outside a file sharing environment. For example, occasionally users encounter an error while attempting to save a file from Photoshop. The error may read, "Could not save 'file.psd' because the file is already in use or was left open." Xinet has successfully reproduced this bug while saving a file to the desktop of an OSX 10.3.2 client system with no mounted volumes. Clearly, it is not possible for Xinet to remedy this bug because it can occur even without the presence of a Xinet server.
All users of Xinet products who have OSX clients in their environments should install our patch as soon as possible. The patch is available for download from our website. After installing the patch, if users on OSX clients experience errors while saving files, please report this to Xinet immediately at help@xinet.com.
If you are running OSX already should you upgrade your systems to OSX 10.3.2? With this patch installed, absolutely. Our customers' reports indicate that previous versions of OSX had enough quirks that they were unpredictable in production workflows. We believe OSX 10.3.2 greatly improved the reliability of the operating system overall, and therefore is still the best OSX client thus far. However, OSX 10.3's sensitivity to File ID reuse demands that this patch be installed on the server in any environment running OSX 10.3 clients.
Xinet is committed to doing everything in our power to address the remaining interoperability issues.
Does this stuff get treated like a virus/trojan, rather than legitimate business?
If that Osama Bin Laden AIM virus isn't a virus, then I don't know what is. Yet I don't see news stories about the FBI or SS arresting the people that wrote it, even though they are more or less out in the open.
It seems the rule lately is if you have a commercial intent, then it's OK for you to write viruses and trojans (like weatherbug).
People actually get pissed off when we tell them they can't have weatherbug on their computer.
I don't know about that. Power hammers use.22 sized charges to shoot nails into concrete walls. I'd like to see you hammer a nail into a concrete wall... with one stroke:)
What law would your friend be convicted under? Surely it must have been some state law or local ordinance. Even if the cartoon characters in the porn were supposed to be underage, the supreme court has ruled that simulated kiddy porn is protected under the first amendment.
Nobody's asking Nvidia or ATI to release firmware source or core design documents. You don't have to know how it works to write a driver for it, you only need the documentation on how to interface to it.
Lotusscript was terrible. I spent hours and hours on the phone with their tech support trying to figure out why various parts of the language did not do what they were supposed to do.
Believe it or not, VBA was a much better language.
We still have some databases in lotus right now at work, though we have migrated all documents and spreadsheets over to office.
If you want to save fuel, you don't want to disable overdrive. I think you might not understand what overdrive is. Most likely it is shifting out of overdrive when you go up a hill. This is probably better than your engine stalling or lurching forward.
My advice: Just remember to get a manual transmission next time.
Slashdot Mirror
I think you may be thinking of the recent case where legislation was claimed to be copyrighted.
Or maybe.. once a document is entered into a court record, it may become public.
In any case, I've not heard of any restriction that prevents any sort of legal document from being protected.
Actually, here are some proposed additions for GPL Version 3:
For I testify unto every man that heareth the words of the license of this code, If any man shall add unto these things, RMS shall add unto him the plagues that are written in this license.
And if any man shall take away from the words of the license of this code, RMS shall take away his part out of the license to this code, and out of the open bazaar, and from the things which are written in this license.
Do you think AFS could be prone to this same file ID reuse issue?
That's because it's Gray Eagles, not Grey Eagles.
You know it's fiction, right? You make it sound like it really happened.
If by upfront, you mean buried near the last page of a very long EULA, then yeah, I'm inclined to agree.
I actually read the EULA before I told people we couldn't install it, because I hadn't heard if it before they asked, but it sounded sleezy.
Make sure to see my replies further down in the thread, I posted an email I got from Xinet about this issue, it sounds like exactly your problem.
NFS may have it's own problems, but the one I'm speaking of is in Appletalk.
I guess this is public information, so I'll post it here.
Many Xinet customers running Mac OSX 10.3 clients have experienced, at one time or another, data loss or errors while saving from OSX-native applications or copying files to the server using the Finder. Though there are several causes of this unexpected data loss, Xinet has tracked the most severe of these cases as Xinet bug #04021. In this bug, files were silently "cross-linking" at time of save or write. That is, the data from a working file might silently overwrite another file on the filesystem. Clients would see the results of this bug when they attempted to open a file and it was empty (zero-length) or when they opened a file and it contained incorrect data. There was no indication to the user that data was written to the wrong place during save, nor were there any errors to indicate that a save had failed. After extensively researching the cause of this error, Xinet has concluded that OSX 10.3 clients are sensitive to a long-standing function of Xinet FullPress/KA-Share: File ID reuse. Our immediate reuse of File IDs causes OSX 10.3 to send data to an incorrect location at time of write.
Alleviating the symptoms of cross-linking files from OSX 10.3 clients has been a very high priority for Xinet engineering. Though we cannot control the client behavior, we have a patch that will remedy the problem as best we can from the server side. This patch adds a delay in File ID reuse. In the past, File IDs were available for reuse immediately after being freed. In this new ksd, File IDs are reserved from reuse for a user-configurable period of time. We have tested this in-house and at selected customer sites, and have found that it significantly reduces errors and silent data loss at time of save from OSX 10.3 client systems. This patch is available for download from our web site.
Bear in mind, this patch reduces the occurrance of errors introduced in OSX 10.3. It will not eliminate all of them, but it will end the catastrophic silent data loss caused by the cross-linking of files at time of save. Xinet has been able to reproduce other incorrect OS 10.3 saving behavior outside a FullPress/KA-Share environment, and some even outside a file sharing environment. For example, occasionally users encounter an error while attempting to save a file from Photoshop. The error may read, "Could not save 'file.psd' because the file is already in use or was left open." Xinet has successfully reproduced this bug while saving a file to the desktop of an OSX 10.3.2 client system with no mounted volumes. Clearly, it is not possible for Xinet to remedy this bug because it can occur even without the presence of a Xinet server.
All users of Xinet products who have OSX clients in their environments should install our patch as soon as possible. The patch is available for download from our website. After installing the patch, if users on OSX clients experience errors while saving files, please report this to Xinet immediately at help@xinet.com.
If you are running OSX already should you upgrade your systems to OSX 10.3.2? With this patch installed, absolutely. Our customers' reports indicate that previous versions of OSX had enough quirks that they were unpredictable in production workflows. We believe OSX 10.3.2 greatly improved the reliability of the operating system overall, and therefore is still the best OSX client thus far. However, OSX 10.3's sensitivity to File ID reuse demands that this patch be installed on the server in any environment running OSX 10.3 clients.
Xinet is committed to doing everything in our power to address the remaining interoperability issues.
Scott Seebass
CEO
Xinet
How do you think Outlook displays mail? Last I checked, it embeds the IE control.
Does this stuff get treated like a virus/trojan, rather than legitimate business?
If that Osama Bin Laden AIM virus isn't a virus, then I don't know what is. Yet I don't see news stories about the FBI or SS arresting the people that wrote it, even though they are more or less out in the open.
It seems the rule lately is if you have a commercial intent, then it's OK for you to write viruses and trojans (like weatherbug).
People actually get pissed off when we tell them they can't have weatherbug on their computer.
I don't know about that. Power hammers use .22 sized charges to shoot nails into concrete walls. I'd like to see you hammer a nail into a concrete wall... with one stroke :)
It's not NFS, it's Appletalk.
Heh, I once had a ham radio friend of mine with a 1500 watt microwave setup shoot my callsign into space, for the heck of it.
:)
And for even more kicks, you'll be happy to know this message came to you via a satellite in geostationary orbit.
Yes, the 600ms ping time does suck, but at least I can annoy people on IRC by saying, "GREETINGS FROM OUTER SPACE"!
A few grams of your lifeless body.
:)
It's kinda silly, since we are all on a big satellite right now.
Yeah, but the people that don't survive the breathing difficulty don't post on Slashdot, so there's a big sampling bias. :)
Apparently, they seek to hire people who are good at riddles, regardless of their other abilities.
What law would your friend be convicted under? Surely it must have been some state law or local ordinance. Even if the cartoon characters in the porn were supposed to be underage, the supreme court has ruled that simulated kiddy porn is protected under the first amendment.
Once something is public, it's no longer a trade secret anyway.
I believe the only thing that will apply in this case is plain old copyright law.
This whole thread is bogus. Yes, ignorance isn't usually a defense, but lack of intent usually is.
Most laws contain the word "intentionally"... Go read some laws sometime.
Nobody's asking Nvidia or ATI to release firmware source or core design documents. You don't have to know how it works to write a driver for it, you only need the documentation on how to interface to it.
I think you are talking about Appletalk, not AFS.
If so, I got an email from the CEO of Xinet, who bases their products around appletalk, talking about just that problem.
It's apparently an issue that Appletalk on MacOS X has, and it's a very serious one.
I think the target of the anecdote is more Apple tech support, who are obviously braindead morons.
Lotus started to suck toward the end.
Lotusscript was terrible. I spent hours and hours on the phone with their tech support trying to figure out why various parts of the language did not do what they were supposed to do.
Believe it or not, VBA was a much better language.
We still have some databases in lotus right now at work, though we have migrated all documents and spreadsheets over to office.
Heh, yeah, it was just a cheap jab, sorry :)
But I haven't had any problems with lost cheese lately, even when people move it.
If you want to save fuel, you don't want to disable overdrive. I think you might not understand what overdrive is. Most likely it is shifting out of overdrive when you go up a hill. This is probably better than your engine stalling or lurching forward.
My advice: Just remember to get a manual transmission next time.