Don't you know that Steve Gibson, the WORLDS GREATEST HACKER! has decreed that only criminals have need to create their own packets?! For shame!
(yes, this is full of sarcasm and contempt directed towards Steve Gibson. Follow the second link. The man is the Jerry Springer of the Internet.)
If he was acting on his employer's behalf in creating the code, then he was acting on his employer's behalf in accepting the GPL.
But he was, in that instance, acting with authority he didn't have. Similar to, if a company janitor signed a multi-million dollar contract 'on behalf of Company X' with IBM, the contract would be struck down, because he didn't have authority to enter into that contract.
Basically, Tilly commited fraud. I'd hate to be the judge who has to figure out what that means, in this case.:-(
You know, that would be an interesting legal conundrum. I wouldn't be surprised if a court ruled that the derivitive work WASN'T GPL'd, because Tilly didn't have authority to accept the GPL for what was, in fact, his employer's work.
Actually, it's one step beyond that. If he was never authorized to license it out in the first place, then the licence is null and void, and the company can demand that anybody using it stop, and that all copies be destroyed, and that nobody distribute it.
Otherwise, I could hack into Microsoft's SourceSafe repository, snag the Windows 2000 code base, throw in the GPL files, and release it. Nope, that's theft. And according to Tilly's contract, which he read, claimed to understand at the time, and voluntarily signed, what he did can be classified as theft.
As they say above, stuff you do on THEIR time, or stuff you do that THEY TOLD YOU TO, they own. Stuff you do on YOUR time, AND that you do because YOU WANT TO, is yours.
Note that the first is an OR clause, and the second is an AND clause. You can't go writing personal stuff on company time, but most people, for whatever reason, write company stuff on personal time.
Tilly read the contract, agreed to it, then forgot that he did. That's his bad, pure and simple. He even admits it. It wasn't obfuscated, or overly legal-speakified. He ignored something he agreed to, and he got spanked for it.
Do it yourself. It's not all that difficult with pretty much ANY performance monitoring tool to spit out numerical data, then suck it into a spreadsheet.
I built a system like this for an Win2000 network I was on; each server, every 15 minutes, would record performance data. Every day, yesterdays data would be vacu-sucked into a database. Then, at leisure, all sorts of wonderful charts, graphs, maps, trends, anything, really, could be spewed back out.
Makes it bloody easy to track peak hours, faulty apps, and determine when, and how much, new hardware you're going to need.
He advocates incremental fixes as they seem appropriate, as opposed to throwing out all previous work and starting from scratch as the 'this will fix everything' solution.
Re:The original Resident Evil was brilliant
on
Resident Evil
·
· Score: 2
I get that 'squeezing my ribcage' sensation when Xerxes starts calmly informing you exactly how fucked you are. Or some of the ghosts.
I think the most 'frightened/disturbed' I've ever been by a video game was actually a single scene from Phantasmagoria (A Sierra FMV-fest) which involved a haunted crib. Of course, this was seven years ago, so I was a bit younger, too.:-)
Re:Anyone up for Zork: The Movie?
on
Resident Evil
·
· Score: 2
That gives me a great idea for the Zork trailer. all the usual shots, then a fade to black, with the words "On 06/06/2004, you will be eaten by a grue."
Were these PERCs with or without on-card battery backup?
I'll also point out that your UPS really should power your systems down when the UPS is at 25 percent charge, or (average shutdown time, including all services)*2, whichever is longer.
Re:"RE" far from the first
on
Resident Evil
·
· Score: 2
And the new Sonya. In a mud fight. That's the only reason to watch that movie.
Re:Nude Surprise!
on
Resident Evil
·
· Score: 3, Funny
Good old America. Bloody violence and mayhem? Ho-hum. The bodyparts every human being is born with? AAAAAH! MY EYES!
1990's: "Rest assured that moments after the end of the episode, I was on the Internet registering my disgust."
2000's: "Well, Scene 12 is shaping up to be just as bad as Scene 11 was."
Here's the thing.
Film runs at 24 FPS, but film also captures motion over time. Lets say you have film running at 2 FPS. You record a hand waving across a table for one second. Your two frames will show a blur of a hand moving across the table.
Now, make a 3d engine that renders that hand moving across that table for 2 FPS. You'll see a static picture of a hand at one side of the table, then a static picture of the hand at the other side of the table.
In other words, film runs at 24 fps, but it captures more information over time in a single frame. Computers, however, render static images. And therefore you need more static images per unit of time to simulate the 'exposure' quality of film.
This is why 3dfx went for the T-buffer; this would allow for high FPS style imagery with fewer actual FPS.
Ground up rewriting means that you chuck out your old inefficient car and get a new better one.
Also throwing out all the other modifications you've made, detail work, and so on, and then buying a factory car and starting all over again, just because it's newer.
...and suddenly, with a flash of tearing insight, the cracker realized how all of his victims felt when he intruded into THEIR systems through a backdoor.
Yes, from that day forward, he was oVVn3d. In the most terrible way possible.
Refactoring means that when you find a more efficient carburator, you install it in your car and go.
Ground up rewriting means that when you find a more efficient carburator, you throw your old car in the trash, go buy a new one, and install your new carburator in it.
What he's saying is 'If I'm working on Foo.bar, and it's got 10 functions, if I'm in function 1, I might notice a better way to do what function 1 does, so I implement it. Better program.'
What he's railing against is the huge mass of programmers who would say 'Because function 1 is broken, lets rewrite ALL 10 FUNCTIONS because we can.'
Generally, what you do is set up a dedicated loghost, which will accept NO network connections other than incoming syslogs from specific machines. Then, you jigger with your printing software so that only syslog can actually touch it. Then, you put a crazy wicked 24 character completely random password consisting of uppercase, lowercase, punctuation and numbers. (only valid with those UNIXes that pay attention to more than the first 8 characters) and you're pretty good.
And I'm sure if you look hard enough, you can find ways to disable reverse line feed in hardware or software.
Most importantly, though, if you have enough logs going through, anyway, then you're pretty much guarenteed NOT to erase the line in question by inserting a 'rlf' into the stream.
The problem I had last, was that we were trying to transition from an 'anything goes, it's all good' philosophy, to a 'hey, wait, this is actually a business' philosophy. People who are used to having MSIM, AOLIM and ICQ all open, and in chats, aren't happy to have the realities explained to them. For example. Or rampant Napstering. We actually had to get the 'burstable' option taken off of our net pipe, because it was costing us too much money.:-)
Obviously, if the employer has worked out a policy regarding 'non work' access, then all is kosher. But people who assume they have a Divine Right to use company resources as they see fit, even when told that such usage can easily result in damage to company assets, that's a different matter.
You also get the people who'll take a mile when given an inch, and ruin it for everybody. My last job, we almost cut off hotmail access to all, after a CSR just HAD to look at the latest Cute Screensaver in her hotmail account; oh look, a virus.
Of course, that incident also got us the funding to put centrally managed AV software on each desktop, so it's not all bad, I suppose.
Who defines 'significantly?' The person paying, or the person reaping the benefits of?
If it's the former, you have no argument. If it's the latter, I'd like a login to a machine on whatever Internet access you have, please. After all, it's not going to be significantly more than zero, right?
Slashdot Mirror
Don't you know that Steve Gibson, the WORLDS GREATEST HACKER! has decreed that only criminals have need to create their own packets?! For shame! (yes, this is full of sarcasm and contempt directed towards Steve Gibson. Follow the second link. The man is the Jerry Springer of the Internet.)
I'm bad at analogy. My point is that it wasn't his to GPL, and that will be interesting if it ever goes to courts. :-)
You know, that would be an interesting legal conundrum. I wouldn't be surprised if a court ruled that the derivitive work WASN'T GPL'd, because Tilly didn't have authority to accept the GPL for what was, in fact, his employer's work.
Actually, it's one step beyond that. If he was never authorized to license it out in the first place, then the licence is null and void, and the company can demand that anybody using it stop, and that all copies be destroyed, and that nobody distribute it. Otherwise, I could hack into Microsoft's SourceSafe repository, snag the Windows 2000 code base, throw in the GPL files, and release it. Nope, that's theft. And according to Tilly's contract, which he read, claimed to understand at the time, and voluntarily signed, what he did can be classified as theft.
As they say above, stuff you do on THEIR time, or stuff you do that THEY TOLD YOU TO, they own. Stuff you do on YOUR time, AND that you do because YOU WANT TO, is yours. Note that the first is an OR clause, and the second is an AND clause. You can't go writing personal stuff on company time, but most people, for whatever reason, write company stuff on personal time.
Tilly read the contract, agreed to it, then forgot that he did. That's his bad, pure and simple. He even admits it. It wasn't obfuscated, or overly legal-speakified. He ignored something he agreed to, and he got spanked for it.
Do it yourself. It's not all that difficult with pretty much ANY performance monitoring tool to spit out numerical data, then suck it into a spreadsheet. I built a system like this for an Win2000 network I was on; each server, every 15 minutes, would record performance data. Every day, yesterdays data would be vacu-sucked into a database. Then, at leisure, all sorts of wonderful charts, graphs, maps, trends, anything, really, could be spewed back out. Makes it bloody easy to track peak hours, faulty apps, and determine when, and how much, new hardware you're going to need.
Oy! Spivak's not trying to make a new set o' gender pronouns; 'emself's just from London, 'e is.
He advocates incremental fixes as they seem appropriate, as opposed to throwing out all previous work and starting from scratch as the 'this will fix everything' solution.
I get that 'squeezing my ribcage' sensation when Xerxes starts calmly informing you exactly how fucked you are. Or some of the ghosts. I think the most 'frightened/disturbed' I've ever been by a video game was actually a single scene from Phantasmagoria (A Sierra FMV-fest) which involved a haunted crib. Of course, this was seven years ago, so I was a bit younger, too. :-)
That gives me a great idea for the Zork trailer. all the usual shots, then a fade to black, with the words "On 06/06/2004, you will be eaten by a grue."
Were these PERCs with or without on-card battery backup? I'll also point out that your UPS really should power your systems down when the UPS is at 25 percent charge, or (average shutdown time, including all services)*2, whichever is longer.
And the new Sonya. In a mud fight. That's the only reason to watch that movie.
Good old America. Bloody violence and mayhem? Ho-hum. The bodyparts every human being is born with? AAAAAH! MY EYES!
1990's: "Rest assured that moments after the end of the episode, I was on the Internet registering my disgust." 2000's: "Well, Scene 12 is shaping up to be just as bad as Scene 11 was."
Here's the thing. Film runs at 24 FPS, but film also captures motion over time. Lets say you have film running at 2 FPS. You record a hand waving across a table for one second. Your two frames will show a blur of a hand moving across the table. Now, make a 3d engine that renders that hand moving across that table for 2 FPS. You'll see a static picture of a hand at one side of the table, then a static picture of the hand at the other side of the table. In other words, film runs at 24 fps, but it captures more information over time in a single frame. Computers, however, render static images. And therefore you need more static images per unit of time to simulate the 'exposure' quality of film. This is why 3dfx went for the T-buffer; this would allow for high FPS style imagery with fewer actual FPS.
...and suddenly, with a flash of tearing insight, the cracker realized how all of his victims felt when he intruded into THEIR systems through a backdoor. Yes, from that day forward, he was oVVn3d. In the most terrible way possible.
Refactoring means that when you find a more efficient carburator, you install it in your car and go. Ground up rewriting means that when you find a more efficient carburator, you throw your old car in the trash, go buy a new one, and install your new carburator in it.
What he's saying is 'If I'm working on Foo.bar, and it's got 10 functions, if I'm in function 1, I might notice a better way to do what function 1 does, so I implement it. Better program.' What he's railing against is the huge mass of programmers who would say 'Because function 1 is broken, lets rewrite ALL 10 FUNCTIONS because we can.'
Generally, what you do is set up a dedicated loghost, which will accept NO network connections other than incoming syslogs from specific machines. Then, you jigger with your printing software so that only syslog can actually touch it. Then, you put a crazy wicked 24 character completely random password consisting of uppercase, lowercase, punctuation and numbers. (only valid with those UNIXes that pay attention to more than the first 8 characters) and you're pretty good. And I'm sure if you look hard enough, you can find ways to disable reverse line feed in hardware or software. Most importantly, though, if you have enough logs going through, anyway, then you're pretty much guarenteed NOT to erase the line in question by inserting a 'rlf' into the stream.
The problem I had last, was that we were trying to transition from an 'anything goes, it's all good' philosophy, to a 'hey, wait, this is actually a business' philosophy. People who are used to having MSIM, AOLIM and ICQ all open, and in chats, aren't happy to have the realities explained to them. For example. Or rampant Napstering. We actually had to get the 'burstable' option taken off of our net pipe, because it was costing us too much money. :-)
Obviously, if the employer has worked out a policy regarding 'non work' access, then all is kosher. But people who assume they have a Divine Right to use company resources as they see fit, even when told that such usage can easily result in damage to company assets, that's a different matter. You also get the people who'll take a mile when given an inch, and ruin it for everybody. My last job, we almost cut off hotmail access to all, after a CSR just HAD to look at the latest Cute Screensaver in her hotmail account; oh look, a virus. Of course, that incident also got us the funding to put centrally managed AV software on each desktop, so it's not all bad, I suppose.
Who defines 'significantly?' The person paying, or the person reaping the benefits of? If it's the former, you have no argument. If it's the latter, I'd like a login to a machine on whatever Internet access you have, please. After all, it's not going to be significantly more than zero, right?