I believe (my company does this but I don't set it up) that on z/OS you can run z/VM, a virtualization product and within z/VM you can run SuSE Enterprise Linux or RedHat Enterprise Linux. In fact, we just bought a new z10 which is supposed to be optimized for virtualization. We're eliminating a few thousand mostly intel servers and consolidating applications and virtualizing on SLES under z/VM.
CPU is definitely bounded - though governed, just like other mainframe stuff - and is a precious resource on these behemoths, but I/O *screams*.
If SCO is under bankruptcy protection (which I think they are?) then if the decision in this case goes against them will they have to pay any money or will Novell be spending attorney fees for bragging rights alone?
I don't normally comment, but I have to on this one. Normally I'd agree - on first thought you're right; we've messed with Mother Nature far too much already - driven countless species to extinction or near so, eliminated millions of miles of forest globally, and not to mention we've indirectly given her Al Gore as an official spokesperson. We've seriously harmed our environment due to our direct actions.
But I don't think anyone would be against research or trying to redirect the next Hurricane Katrina. And what if one day we have the capability of stopping or redirecting a tsunami far before it kills hundreds, thousands, or hundreds of thousands of people.
Just like in IT - typically solving a major problem always ends up with spinoff challenges to address.
When it comes to direcly saving lives, I think we face those challenges as they arise. But that's just me.
The number of times I've had someone think that Calc was windows calculator replacement, rather than a spreadsheet is far too high I hear OO.o Base comes with a default query for them courtesy of ThinkGeek:
The code in question (see the PDF attached to the Geronimo-mailing-list) involves extensions to another ASF project, Log4J, founded by Ceki Gulcu.
Here are his findings about the code snippets in question. In short, he notes that the code is actually his IP (the second example from the PDF is actually a user-contributed piece to log4j that predates the jboss examples in jboss' own cvs repository), example code he wrote as part of the log4j distribution and donated directly to the ASF and hence part of ASF (at most, his copyright first) before JBoss, LLC released it under the LGPL.
Well I normally don't post, but I couldn't resist this one.
One of the greatest learning experiences of my life was my first brief experience as a full-time developer. My first job out of college. 21 years old. Telecom (CLEC, at that), in 2001.
Lessons learned:
1) never stop looking at the job market. Ever. Full time job, salary, great people you work with - doesn't matter. Keep looking.
2) Warning signs - group meetings with the CEO that talk about conserving cash. Memos about "helping out around the office" like not printing out all your e-mail in the morning. 'Cause a few reams of paper is gonna save any employee...
3) Don't think you are being cut just because you are the new guy. In my experience, the highest and lowest paid employees were canned. Subsequent lunches with the remaining developers revealed that they were forced to work brutal 100+ hour weeks to make up for the missing edges of the payroll bell curve.
I had about the opposite of the above poster:
1) Early in the day, but late in the week (friday morning). Rumors had been flying for about two weeks. Unfortunately, monday thru thursday the developers had to watch all the analysts and other less-technical IT workers walk out with boxes. Thursday evening, as we all went home, we couldnt help but start believing that last little hope that the company truly couldn't afford to get rid of us... we're developers and we're already swamped! Not so. Friday morning, the last day of November. Suddenly the thought of the next few weeks of Christmas shopping with the newly-acquired steady cash-flow turned to fears about bills.
2) Late in the month.
3) What some would classify as fair (but still not all that helpful) severance.
4) Oh and I almost forgot! They actually invited us into one of their satellite offices "to use their computers to look for jobs." Gee, thanks. I got a kick out of the lady in said satellite office who made the comment the following monday I visited, "Wow, the XYZ system is so fast today!" (XYZ system was a single windows server running a single license of a telecom solutions app that everyone in the company had desktop shortcuts which launched either a Citrix or Terminal Services login to the machine because the company didnt want to install the app on all their workstations)
When the user count drops from 400+ to just over 100, those things tend to happen:)
I doubt it's Comdex alone that caused key3media to lose their money... I went to Networld-Interop in Atlanta this year. It was more fun walking through the food court in the CNN building than the show itself. It too offered free passes if registering through the Net...and it was a huge building for a rather small exhibitor pool...That just reeks of net loss, if you ask me.
Slashdot Mirror
Would something like this actually work? You have to believe there's a lot readily available in the SE. http://www.wimp.com/solutionoil/
I believe (my company does this but I don't set it up) that on z/OS you can run z/VM, a virtualization product and within z/VM you can run SuSE Enterprise Linux or RedHat Enterprise Linux. In fact, we just bought a new z10 which is supposed to be optimized for virtualization. We're eliminating a few thousand mostly intel servers and consolidating applications and virtualizing on SLES under z/VM. CPU is definitely bounded - though governed, just like other mainframe stuff - and is a precious resource on these behemoths, but I/O *screams*.
In real jail, your inbox is crammed full of unsolicited male.
Actually, I believe it's your outbox.
IANAL - this is an ignorant question -
If SCO is under bankruptcy protection (which I think they are?) then if the decision in this case goes against them will they have to pay any money or will Novell be spending attorney fees for bragging rights alone?
Thanks in advance to whomever answers.
I don't normally comment, but I have to on this one. Normally I'd agree - on first thought you're right; we've messed with Mother Nature far too much already - driven countless species to extinction or near so, eliminated millions of miles of forest globally, and not to mention we've indirectly given her Al Gore as an official spokesperson. We've seriously harmed our environment due to our direct actions.
But I don't think anyone would be against research or trying to redirect the next Hurricane Katrina. And what if one day we have the capability of stopping or redirecting a tsunami far before it kills hundreds, thousands, or hundreds of thousands of people.
Just like in IT - typically solving a major problem always ends up with spinoff challenges to address.
When it comes to direcly saving lives, I think we face those challenges as they arise. But that's just me.
select * from users where clue > 0
configured to run under an administrative privilege level'
/yawn. Next article: "MS Patents Buffer Overflow"
The assumption:
"Protocol XYZ specifies this data sent to our software will only be 32k. If the other program sends more, it's their bug!"
The Result
The code in question (see the PDF attached to the Geronimo-mailing-list) involves extensions to another ASF project, Log4J, founded by Ceki Gulcu.
Here are his findings about the code snippets in question. In short, he notes that the code is actually his IP (the second example from the PDF is actually a user-contributed piece to log4j that predates the jboss examples in jboss' own cvs repository), example code he wrote as part of the log4j distribution and donated directly to the ASF and hence part of ASF (at most, his copyright first) before JBoss, LLC released it under the LGPL.
http://www.qos.ch/logging/jboss.html
Well I normally don't post, but I couldn't resist this one.
:)
One of the greatest learning experiences of my life was my first brief experience as a full-time developer. My first job out of college. 21 years old. Telecom (CLEC, at that), in 2001.
Lessons learned:
1) never stop looking at the job market. Ever. Full time job, salary, great people you work with - doesn't matter. Keep looking.
2) Warning signs - group meetings with the CEO that talk about conserving cash. Memos about "helping out around the office" like not printing out all your e-mail in the morning. 'Cause a few reams of paper is gonna save any employee...
3) Don't think you are being cut just because you are the new guy. In my experience, the highest and lowest paid employees were canned. Subsequent lunches with the remaining developers revealed that they were forced to work brutal 100+ hour weeks to make up for the missing edges of the payroll bell curve.
I had about the opposite of the above poster:
1) Early in the day, but late in the week (friday morning). Rumors had been flying for about two weeks. Unfortunately, monday thru thursday the developers had to watch all the analysts and other less-technical IT workers walk out with boxes. Thursday evening, as we all went home, we couldnt help but start believing that last little hope that the company truly couldn't afford to get rid of us... we're developers and we're already swamped! Not so. Friday morning, the last day of November. Suddenly the thought of the next few weeks of Christmas shopping with the newly-acquired steady cash-flow turned to fears about bills.
2) Late in the month.
3) What some would classify as fair (but still not all that helpful) severance.
4) Oh and I almost forgot! They actually invited us into one of their satellite offices "to use their computers to look for jobs." Gee, thanks. I got a kick out of the lady in said satellite office who made the comment the following monday I visited, "Wow, the XYZ system is so fast today!" (XYZ system was a single windows server running a single license of a telecom solutions app that everyone in the company had desktop shortcuts which launched either a Citrix or Terminal Services login to the machine because the company didnt want to install the app on all their workstations)
When the user count drops from 400+ to just over 100, those things tend to happen
Can we believe a post from the Iraqi Info Minister?
"There are no Bots in in IRC. Never!"
I doubt it's Comdex alone that caused key3media to lose their money...
I went to Networld-Interop in Atlanta this year. It was more fun walking through the food court in the CNN building than the show itself. It too offered free passes if registering through the Net...and it was a huge building for a rather small exhibitor pool...That just reeks of net loss, if you ask me.