Yep. Look for IBM to just shutdown the division
then instead of selling it. It will cost them
more money, but it will be worth it to remove the
albatross.
If you would have stuck with vulvanism you
could still be correct. Certainly, as a species,
humans are doing many things that could
lead to mass extinction. Ironically, an obsession with
vulvanism is one of them.
Lower Oxygen levels may not kill you, but higher Carbon Dioxide certainly can. The reason has to do with
how lungs function. When you breathe, the partial
pressure of Oxygen in your blood is lower than
that in the atmosphere. Hence, Oxygen flows
from the air you breathe into your blood.
The reverse is true for Carbon Dioxide. It flows
from the blood to the air because the air has a
lower partial pressure of CO2 than the CO2 in the
blood. If the CO2 content in the air is too high,
you can't get rid of the CO2 in your blood.
Eventually, all of your hemoglobin molecules
are useless.
I've seen similar studies that women drivers
are worse in parking lots. Well, it's a meaningless
study because that's where they spend a large
proportion on their time driving.
That is all good and fine, however, you didn't
address the issue of environment variables,
which your testing/QA people are typically
afraid to change (or conversely, they do change and create a mess).
The best approach is to create an environment
variable that defines the development environment,
example DEVENV=DEV, DEVENV=TEST, DEVENV=IT, DEVENV=QA, DEVENV=PROD (or not needed for production at all), and then elsewhere (controlled and basically kept hidden from the testers or users),
other environment variables are set based upon
the value of DEVENV. Examples of these environment
variables would be your PATH variables, ORACLE_SID,
etc.
Then, the final problem is educating the
testers what DEVENV means, and more importantly,
why that one has to be correct and that they
should not mess with any other environment variables.
If the testers can't understand that, you
need smarter testers.
You are quite correct. Not surprisingly, your
post was moderated 'Redundant'. Not surprisingly,
your post was the first to point out the difference
in licenses. Not surprisingly, the astromods are
out in force.
P2P is *NOT* about business. P2P is the antithesis
of a company maintaining a degree of control.
P2P does not exist so companies can exploit it.
P2P is what the Internet is all about.
P2P is UUCP on steroids.
For the hardware manufacturers to seriously address
Linux. Someone (just one to start) needs to build
some hardware that is ready for Linux and makes
the specifications available for free.
And I'm not just talking about handhelds, but
the entire spectrum of hardware. Especially
hardware that is difficult to find Linux drivers for. Video and soft-modem for example.
And obviously, handhelds preloaded with Linux,
or at least easy to install GNU/Linux on them.
Caution on your fix to/etc/shadow. First, it's
much easier to just edit the file and clear the
password field. Secondly, your procedure could
fail to make the shadow file usable (for root)
if in fact the shadow file is not using DES
encryption, but using a modern encryption such
as AES. SuSE-9.2 supports that by default.
So cut-and-pasting a DES password field into
a file expected to contain an AES password is
not going to solve the problem of an unknown password.
One application would
be to donate one to SCO so they can find the
infringing code sooner.
Re:Engineering within limits brings great results
on
Where's My 10 Ghz PC?
·
· Score: 1
Those days are still with us. It just depends
upon where you look.
If you follow the MS philosophy, you keep piling on features (and
other stuff), and you make the users have to
upgrade the machine to faster processors, more ram,
faster disk drives, etc.
If you follow the Linux philosophy, you constantly
strive to make the performance as best as possible,
so that you *can* run it on older hardware.
Slashdot Mirror
If you want to stay clean for Linux, I would not even read about OpenSolaris.
The TPTB want to kill Usenet.
Yep. Look for IBM to just shutdown the division then instead of selling it. It will cost them more money, but it will be worth it to remove the albatross.
What was the question again?
They are just not paying attention.
Nice post.
See this story.
If you would have stuck with vulvanism you could still be correct. Certainly, as a species, humans are doing many things that could lead to mass extinction. Ironically, an obsession with vulvanism is one of them.
Lower Oxygen levels may not kill you, but higher Carbon Dioxide certainly can. The reason has to do with how lungs function. When you breathe, the partial pressure of Oxygen in your blood is lower than that in the atmosphere. Hence, Oxygen flows from the air you breathe into your blood. The reverse is true for Carbon Dioxide. It flows from the blood to the air because the air has a lower partial pressure of CO2 than the CO2 in the blood. If the CO2 content in the air is too high, you can't get rid of the CO2 in your blood. Eventually, all of your hemoglobin molecules are useless.
They were ordered to do so twice but never did. The orders were by this same Judge Wells yet she never enforced her own order!
See how MS (err SCO) was handed a gift in their case with IBM here.
I've seen similar studies that women drivers are worse in parking lots. Well, it's a meaningless study because that's where they spend a large proportion on their time driving.
The best approach is to create an environment variable that defines the development environment, example DEVENV=DEV, DEVENV=TEST, DEVENV=IT, DEVENV=QA, DEVENV=PROD (or not needed for production at all), and then elsewhere (controlled and basically kept hidden from the testers or users), other environment variables are set based upon the value of DEVENV. Examples of these environment variables would be your PATH variables, ORACLE_SID, etc.
Then, the final problem is educating the testers what DEVENV means, and more importantly, why that one has to be correct and that they should not mess with any other environment variables.
If the testers can't understand that, you need smarter testers.
You are quite correct. Not surprisingly, your post was moderated 'Redundant'. Not surprisingly, your post was the first to point out the difference in licenses. Not surprisingly, the astromods are out in force.
Who cares about SVR4 these days anyway?
P2P is *NOT* about business.
P2P is the antithesis of a company maintaining a degree of control.
P2P does not exist so companies can exploit it.
P2P is what the Internet is all about.
P2P is UUCP on steroids.
And I'm not just talking about handhelds, but the entire spectrum of hardware. Especially hardware that is difficult to find Linux drivers for. Video and soft-modem for example.
And obviously, handhelds preloaded with Linux, or at least easy to install GNU/Linux on them.
Or transfer it to a police car.
After you extract the files, there is usually a README file.
Obviously a global wetware malfunction. Usually no one does RTFA.
Caution on your fix to /etc/shadow. First, it's
much easier to just edit the file and clear the
password field. Secondly, your procedure could
fail to make the shadow file usable (for root)
if in fact the shadow file is not using DES
encryption, but using a modern encryption such
as AES. SuSE-9.2 supports that by default.
So cut-and-pasting a DES password field into
a file expected to contain an AES password is
not going to solve the problem of an unknown password.
Rookies.
One application would be to donate one to SCO so they can find the infringing code sooner.
If you follow the MS philosophy, you keep piling on features (and other stuff), and you make the users have to upgrade the machine to faster processors, more ram, faster disk drives, etc.
If you follow the Linux philosophy, you constantly strive to make the performance as best as possible, so that you *can* run it on older hardware.
Parent post qualifies as an excellent example of when to post anonymously.