Most production work will remain at java 6 for a while, until everyone makes their versions of java 7 available, Apple and IBM in particular. RHEL doesn't ship with the openjdk-1.7.0 yet. It's just not available in enough places to be worth developing against yet. Oracle knows that Apache is one of the major reasons that java is a popular as it is. They did give the Apache foundation, all of OpenOffice you know. Some idiot made a bad call and told management, that the error was just a corner case, and management said were not going to miss our deadline for a corner case. Oracle knows that the enterprise market will buy Oracle and Oracle services. It's not worried about software that's not in its market space.
:) I don't even begin to think we are a really high traffic site. But we do fall into the category of I/O bound vs. space. SSDs have enabled us to keep up with our demand while keeping our infrastructure costs down. As well as the amount of infrastructure we have is able to be smaller as well, which means the number of staff required is smaller.
Why wouldn't you run with DB2 on all of that IBM equipment?
Having finished an upgrade to SSD's for our website and esp or DB servers several months ago. One of the things I found that has really made a difference, is in the ability of RAID controllers to use and understand a mix of SSD and HDD drives. LSI makes a nice controller that will move frequently used files to the SSD drives. We didn't go this route however. We found that we could replace 14 raid 10 HDD drives with 4 raid 10 SDD drives. The power saving are amazing, the heat differences are great, and the speed is __amazing__. Our queries run about 1000 times faster. We've always had too much active data to just be able to throw pure memory at it. It's also been a balanced mix of random and sequential access needs. SSDs fit our needs perfectly. Now we're just going to have to see what the reliability is like. So far so good.... We're also fairly high traffic at 5.6 queries/sec avg. and about 8.6 inserts/sec avg.
You find that most of the free GPL lawyers are too busy to help. If it really matter to you, borrow the cash for an IP lawyer. You WILL NOT WIN if you don't have proof that your company in an signed document said it was OK to GPL the code. If you have that, then just run with your fork and call it a day, and wait until they come after you. As long as you were an employee (W-2) of theirs, even if you worked at home, that code is theirs. If it was legally GPL'd then it is everyone's, and this discussion is pointless. If your were a contractor for them (W-9?). Then it depends on the terms of your contract, . Don't expect to pay less than $10,000 for a decent IP lawyer if there is any conflict between you and the ex-company. Chances are you're going to have to take your lumps and walk away, but IANAL. I just know that I JUST finished paying my lawyer, and my employer and I have a GOOD relationship. It took 2+ years, but now I have a decent contract with them that clearly states what I own, and what they do. Also remember, you can always start from scratch, and if you haven't rewritten your code for the first time, you probably need to anyway, regardless of the legal situation.:)
No shit! Where the hell is every one. As an American it's my right to have someone else picket and be arrested for my freedoms. On a more serious note, we need an organization and a website to coordinate pickets and non violent (refusing to be scanned/groped) protests.
Publicity stunt or not, perhaps we should just protest. get together 20 - 40 people have them all book short flights at the same time, then just flat out refuse any screening except a metal detector. 20+ ppl refusing at a major airport, will get some news, and delay a large number of flights due to everyone else waiting for them. We could cause millions of dollars worth of damage very quickly by simply refusing to be scanned or groped.
"ban the sale of any animal that walks, flies, swims, crawls or slithers" buy kangaroos, frogs and maybe those trans-dimensional beings from the Hitch Hiker's Guide.
I think you're absolutely right. I drove across Texas last fall, and completely forgot about it. It amazing how something SO BIG can take up so little room in my head. It must have a hell of a compression ratio.
According to the second article (haveit), they see a use for this being during "monotonous driving" times such as "exceedingly speed limited" sections of roads. I can only assume they mean the US interstate system. I think what's going to happen is that people are going to start taking naps when driving across Kansas and eastern Colorado.
If I remember correctly Mitnick was not a very nice guy, and a bit of a poser. Most of his hacks were based off of other peoples (LOD) and not his own. I didn't really care for him as a person or hacker, but I did feel he got the short end of the stick. LulzSec reminds me a bit of Mitnick from a personality point of view, and a simplicity of attack point of view. There's doing it because it's fun and interesting, and then there's doing it because you think you're cool and need to brag about how l33t you are. A collection of script kiddies will always be a collection of script kiddies, no matter how big a news splash they make.
I agree, just takes time that's all. And I guess I've seen 500 as a fundamental constant in the universe, so when it get's changed I'm not really sure yet, what the ramifications could be.
NO, there's absolutely a way to deal with this, things are just going to have be changed is all. And that takes time and attention to detail. It's all part of the job, but it's one more thing none the less. SELinux is finally settled down, and now we've got systemd, and base UID changes, as we'll as virtualization and significantly heavier use of kernel cgroups. I'm just saying it's one more thing on the list to deal with in an already complicated and busy few years. The amount of effort required to go from RHEL4 to RHEL6 and still maintain PCI-DSS compliance and configuration standards is pretty rough at the moment. As Linux and the big distributions continue move away from traditional UNIX ways of doing things there are lot more potential ways to make mistakes, and far less people who understand the security implications, and where the pitfalls are.
Not to mention the security implications of this. Tripwire, and I'm sure a number of other policy auditing systems, expect user accounts to start at 500, and do system wide permissions checking, and user_id -> service based auditing on this. Including running processes etc. This won't be too much of a pain to fix, but it will have to be fixed none the less. Oh well, C'est la vie.
I generally change the minor number when something important has happened, but this are still compatible. And after all of the effort that they've gone through to finally remove the Big Kernel Lock, I think they deserve a new minor version number. It really is a very different architecture inside the kernel now as compared to the start of the 2.5 series.
They're sure trying in the mobile space though. :)
Most production work will remain at java 6 for a while, until everyone makes their versions of java 7 available, Apple and IBM in particular. RHEL doesn't ship with the openjdk-1.7.0 yet. It's just not available in enough places to be worth developing against yet. Oracle knows that Apache is one of the major reasons that java is a popular as it is. They did give the Apache foundation, all of OpenOffice you know. Some idiot made a bad call and told management, that the error was just a corner case, and management said were not going to miss our deadline for a corner case. Oracle knows that the enterprise market will buy Oracle and Oracle services. It's not worried about software that's not in its market space.
:) I don't even begin to think we are a really high traffic site. But we do fall into the category of I/O bound vs. space. SSDs have enabled us to keep up with our demand while keeping our infrastructure costs down. As well as the amount of infrastructure we have is able to be smaller as well, which means the number of staff required is smaller.
Why wouldn't you run with DB2 on all of that IBM equipment?
Having finished an upgrade to SSD's for our website and esp or DB servers several months ago. One of the things I found that has really made a difference, is in the ability of RAID controllers to use and understand a mix of SSD and HDD drives. LSI makes a nice controller that will move frequently used files to the SSD drives. We didn't go this route however. We found that we could replace 14 raid 10 HDD drives with 4 raid 10 SDD drives. The power saving are amazing, the heat differences are great, and the speed is __amazing__. Our queries run about 1000 times faster. We've always had too much active data to just be able to throw pure memory at it. It's also been a balanced mix of random and sequential access needs. SSDs fit our needs perfectly. Now we're just going to have to see what the reliability is like. So far so good.... We're also fairly high traffic at 5.6 queries/sec avg. and about 8.6 inserts/sec avg.
good for you, I'm maxed out a 1.5Mbps/768k. I can't imagine what I'd do with 20/20Mbps.
You know that at some point there's going to be a whole rule 34 meets Robert Heinlein kinda thing going on here.
WOW, that's just awesome.
You find that most of the free GPL lawyers are too busy to help. If it really matter to you, borrow the cash for an IP lawyer. You WILL NOT WIN if you don't have proof that your company in an signed document said it was OK to GPL the code. If you have that, then just run with your fork and call it a day, and wait until they come after you. As long as you were an employee (W-2) of theirs, even if you worked at home, that code is theirs. If it was legally GPL'd then it is everyone's, and this discussion is pointless. If your were a contractor for them (W-9?). Then it depends on the terms of your contract, . Don't expect to pay less than $10,000 for a decent IP lawyer if there is any conflict between you and the ex-company. Chances are you're going to have to take your lumps and walk away, but IANAL. I just know that I JUST finished paying my lawyer, and my employer and I have a GOOD relationship. It took 2+ years, but now I have a decent contract with them that clearly states what I own, and what they do. Also remember, you can always start from scratch, and if you haven't rewritten your code for the first time, you probably need to anyway, regardless of the legal situation. :)
People still use Bing? I guess IE must point there by default....
I see you missed the sarcasm.
I guess that's why I keep coming here, as opposed to switching to reddit.
No shit! Where the hell is every one. As an American it's my right to have someone else picket and be arrested for my freedoms. On a more serious note, we need an organization and a website to coordinate pickets and non violent (refusing to be scanned/groped) protests.
Publicity stunt or not, perhaps we should just protest. get together 20 - 40 people have them all book short flights at the same time, then just flat out refuse any screening except a metal detector. 20+ ppl refusing at a major airport, will get some news, and delay a large number of flights due to everyone else waiting for them. We could cause millions of dollars worth of damage very quickly by simply refusing to be scanned or groped.
I've been waiting to find out WTF the three sea shells is all about for years now!
"ban the sale of any animal that walks, flies, swims, crawls or slithers"
buy kangaroos, frogs and maybe those trans-dimensional beings from the Hitch Hiker's Guide.
On the flip side, this may not be a problem at all, and more of a feature.
I think you're absolutely right. I drove across Texas last fall, and completely forgot about it. It amazing how something SO BIG can take up so little room in my head. It must have a hell of a compression ratio.
According to the second article (haveit), they see a use for this being during "monotonous driving" times such as "exceedingly speed limited" sections of roads. I can only assume they mean the US interstate system. I think what's going to happen is that people are going to start taking naps when driving across Kansas and eastern Colorado.
If I remember correctly Mitnick was not a very nice guy, and a bit of a poser. Most of his hacks were based off of other peoples (LOD) and not his own. I didn't really care for him as a person or hacker, but I did feel he got the short end of the stick. LulzSec reminds me a bit of Mitnick from a personality point of view, and a simplicity of attack point of view. There's doing it because it's fun and interesting, and then there's doing it because you think you're cool and need to brag about how l33t you are. A collection of script kiddies will always be a collection of script kiddies, no matter how big a news splash they make.
I agree, just takes time that's all. And I guess I've seen 500 as a fundamental constant in the universe, so when it get's changed I'm not really sure yet, what the ramifications could be.
NO, there's absolutely a way to deal with this, things are just going to have be changed is all. And that takes time and attention to detail. It's all part of the job, but it's one more thing none the less. SELinux is finally settled down, and now we've got systemd, and base UID changes, as we'll as virtualization and significantly heavier use of kernel cgroups. I'm just saying it's one more thing on the list to deal with in an already complicated and busy few years. The amount of effort required to go from RHEL4 to RHEL6 and still maintain PCI-DSS compliance and configuration standards is pretty rough at the moment. As Linux and the big distributions continue move away from traditional UNIX ways of doing things there are lot more potential ways to make mistakes, and far less people who understand the security implications, and where the pitfalls are.
Not to mention the security implications of this. Tripwire, and I'm sure a number of other policy auditing systems, expect user accounts to start at 500, and do system wide permissions checking, and user_id -> service based auditing on this. Including running processes etc. This won't be too much of a pain to fix, but it will have to be fixed none the less. Oh well, C'est la vie.
cool, thanks for the extra info.
doh! it's obviously after 5 pm here. That should read 'start of the 2.6 series.' oh well.... need beer....
I generally change the minor number when something important has happened, but this are still compatible. And after all of the effort that they've gone through to finally remove the Big Kernel Lock, I think they deserve a new minor version number. It really is a very different architecture inside the kernel now as compared to the start of the 2.5 series.