Again, if nobody's started doing a black-box implementation of the suspect code
How would you propose that this is done? Last I saw, SCO wouldn't tell what the suspect code is. Yes, they have shown one function (which may or may not belong to them), but that is all. Unless you black-box rewrite the entire kernel, you can't be sure to get the parts they claim as their own.
Remember, you can't trust backups if you've been compromised. How long ago was the system compromised without somebody noticing? How many compromised packages have you been backing up?
So even if they did have full backups of the FTP site, they still need to verify that the files are correct. Unless they have backups reaching to the beginning of the archive, they can never be 100% sure that the correct files are online.
Looks like this one does MP3s as well, so you don't have to worry about MP3s you already have. Of course you could convert them, but you lose more quality (lossy-to-lossy conversion loses more than either original encoding).
History has shown that, even with the current management, space flight is safe. It has a fairly low accident rate compared with other industries. However, when the do have an accident, it is large and spectacular; everybody sees it, so everybody wants change.
That said, they have identified procedural problems that caused risks. Learn from your mistakes, and move on. You don't need a huge overhaul in management before you can listen to your engineers say "Hey, I think something's wrong here". You listen to your people, and act on their advice.
Do you know who was the corporate counsel for the company? If so, have your lawyer contact them. If not, your lawyer may be able to discover who it was. Also, your lawyer may already know the answer, or be able to get in touch with someone who does.
Maybe forcibly use larger fonts -- not all users will be savvy enough to increase the size of their default fonts.
So you'd rather alienate those who do know how to increase their default font size.
Perhaps increase the font size, but allow the user's preferences to override them. CSS allows for this.
Also, make use of the <link> tag in page headers, to link to the index, table of contents, and previous/next pages. Some browsers, such as Mozilla, give access to these links in a navigation toolbar.
Adobe is much more likely to issue a linux port of their code.
Why would they bother? Obviously, their current (Windows) version already works just fine in Linux, so why would they waste their time and effort to write and debug a new port?
Also, since gcc itself is GPLed, you'll have to be making an error-free compiler all-by-yourself.
Actually, the point of this discussion is that you wouldn't need to write your own compiler. Use GCC, but don't distribute your changed binaries. If you don't distribute the GCC binaries, you don't need to distribute the changed source.
then Broadcom would have to release their changes.
Yes, Broadcom would have to release their changes. But not to the general public. The source only has to be released to the same organizations to whom the binaries were released - in this case, Linksys. If Broadcom gave you a copy of their modified GCC, they'd also have to give you a copy of their source.
The "obvious" change is that the configuration files are in a different-than-standard location for Zebra. However, there are two problems with this:
Zebra has a commercial port by the primary developers, which may be modified by license
./configure --prefix=whatever --sysconfdir=xxx allows you to change file locations before compiling, without changing the source.
The article also states that LinkSys is using a modified GCC. So what? They aren't distributing a modified GCC, so they are not bound to distribute sources.
Damn, it must be nice to be able to get "talking with the boss" out of the way. I have this problem that mine comes over every hour to ask "how's it going?". Usually when I can least afford the distraction.
Take a look at the headers of a news message some time. You'll see a list of every news server it passed through, in the order that they saw the message. So you can find out what ISP the message was sent from (possibly what user IP sent it), or the server that erased the Received: headers.
Yes, receiving anonymously is fairly easy (if you use a server that doesn't keep download records), but sending anonymously is somewhat more difficult.
This involves launching robotic searches across the internet, on all major peer-to-peer networks, in 65,000 newsgroups, FTP sites, Internet Relay chat channels and auction and retail sites.
Newsgroups are extremely non-private. You put the files on your ISP's server, which broadcasts to (almost) every other ISP in the world.
The ISP was the target of the subpoena. The RIAA gets the user's contact info from the ISP, then sends a cease-and-desist to the user. Ms. Boggs is one step ahead of them, by complying to the C&D before it's sent.
No, but if somebody identified your vehicle, you'd probably get a visit from the police. In the same way, the owners of these computers are getting subpoenaed. It allows the RIAA to use their computers as a starting point in their investigation.
Slashdot Mirror
Happy hacking, TAH.
Need I say more?
Just some idle curiosity - if the earth is flat, how would you dig to China? Wouldn't you fall straight through?
So even if they did have full backups of the FTP site, they still need to verify that the files are correct. Unless they have backups reaching to the beginning of the archive, they can never be 100% sure that the correct files are online.
Looks like this one does MP3s as well, so you don't have to worry about MP3s you already have. Of course you could convert them, but you lose more quality (lossy-to-lossy conversion loses more than either original encoding).
That said, they have identified procedural problems that caused risks. Learn from your mistakes, and move on. You don't need a huge overhaul in management before you can listen to your engineers say "Hey, I think something's wrong here". You listen to your people, and act on their advice.
What if you're working on something, and somebody comes along and hits the reset button? Yet nothing in the OS prevents this from happening.
Because it's being developed in the USA.
In short, contact a lawyer
Perhaps increase the font size, but allow the user's preferences to override them. CSS allows for this.
Also, make use of the <link> tag in page headers, to link to the index, table of contents, and previous/next pages. Some browsers, such as Mozilla, give access to these links in a navigation toolbar.
But Linksys didn't distribute the GCC binaries. So they are not required to distribute the GCC sources.
The article also states that LinkSys is using a modified GCC. So what? They aren't distributing a modified GCC, so they are not bound to distribute sources.
Damn, it must be nice to be able to get "talking with the boss" out of the way. I have this problem that mine comes over every hour to ask "how's it going?". Usually when I can least afford the distraction.
Yes, receiving anonymously is fairly easy (if you use a server that doesn't keep download records), but sending anonymously is somewhat more difficult.
My ISP has several alt.binaries.* groups. I don't know if it's all of them, but there are a lot of them.
The ISP was the target of the subpoena. The RIAA gets the user's contact info from the ISP, then sends a cease-and-desist to the user. Ms. Boggs is one step ahead of them, by complying to the C&D before it's sent.
No, but if somebody identified your vehicle, you'd probably get a visit from the police. In the same way, the owners of these computers are getting subpoenaed. It allows the RIAA to use their computers as a starting point in their investigation.