I think she sent you the wrong form response. What's amusing is that if she's against government regulation of the Internet, then undoubtedly she should oppose the PROTECT-IP Bill.
When is it OK to drink them? Easy to remember answer: Never.
The problem is not that it's "never" okay to have a sugary drink, the problem is that it's a part of many people's everyday diet. A sugary drink should be a treat - something you have every once in a while not for legitimate sustenance, but to taste something (which to some people may be) pleasant.
Life is short, and none of us are getting out alive. A root beer every now and then may be better for the soul than it is bad for the kidneys.
...they get you in the door for the interview. You're at the interview in part because you have something to prove to your prospective employer, not because you're entitled to the job. If you were truthful on your resume and are confident in your ability, I would imagine a short quiz would be a great opportunity to wow them with your knowledge, which shouldn't be difficult given how many people in this industry don't know dick.
The difference is that it would be an option in the configuration gui for the daemon, as opposed to having to have the knowledge that you need to remove this package that was installed on the system by default in order to prevent your BIND configuration from getting automatically borked in the future.
What you're missing is that I was talking about what Red Hat should do to prevent this problem in the future, not what sysadmins should do to wise up to it. I know that talk of idiot-proofing the OS isn't too popular around here, at least not with the hardcore Linux geeks. But I've never heard Red Hat Linux be accused of being for hardcore Linux geeks.
I see your point. But the fact is that BIND and caching-nameserver can coexist on the same box (obviously, because caching-nameserver is dependent on BIND). Red Hat would save themselves some trouble by just correcting this on their end (perhaps something in system-config-bind for toggling between serving records and just caching...similar to the "switchmail" app for toggling between Sendmail and Postfix). If the flag for serving records is checked, then the system will protect named.conf regardless of whether caching-nameserver is installed.
I suspect this would serve Red Hat better than just hoping sysadmins miraculously become smarter.
It's difficult being a male looking for a new car these days.
-If you purchase a large sedan, you're old.
-If you purchase a small sedan, you're gay.
-If you purchase a minivan, you're whipped.
-If you purchase either a sports car, SUV, or large pickup truck, you have a small penis.
I'm not much for conspiracy theories, but say these record companies give this pay-for-online-music thing a half-assed effort. Say it does indeed flop, miserably. They can then come back and say:
"See! If we were to change our business model to accomodate the changes in technology, our industry will collapse! Senator Hollings, your thoughts?.."
And don't forget the *speed*. Developers are so concerned with having players move at a realistic speed, that they forget that it's fun to whiz around a level at a pace faster than your mind can think.
Dozens of monsters swarming you all at once
Aye! The one current game I can think of that offers this is Serious Sam 2 (I'm sure the original does, as well, but I've yet to play it). An arcade-style romp that you don't need 53 fingers to play.
Slashdot Mirror
It was disguised as an IBM copy machine in order to sneak it into the casino after hours.
..so that's what they look like.
I think she sent you the wrong form response. What's amusing is that if she's against government regulation of the Internet, then undoubtedly she should oppose the PROTECT-IP Bill.
I'm guessing that's not the case.
When is it OK to drink them? Easy to remember answer: Never.
The problem is not that it's "never" okay to have a sugary drink, the problem is that it's a part of many people's everyday diet. A sugary drink should be a treat - something you have every once in a while not for legitimate sustenance, but to taste something (which to some people may be) pleasant.
Life is short, and none of us are getting out alive. A root beer every now and then may be better for the soul than it is bad for the kidneys.
...they get you in the door for the interview. You're at the interview in part because you have something to prove to your prospective employer, not because you're entitled to the job. If you were truthful on your resume and are confident in your ability, I would imagine a short quiz would be a great opportunity to wow them with your knowledge, which shouldn't be difficult given how many people in this industry don't know dick.
The difference is that it would be an option in the configuration gui for the daemon, as opposed to having to have the knowledge that you need to remove this package that was installed on the system by default in order to prevent your BIND configuration from getting automatically borked in the future.
What you're missing is that I was talking about what Red Hat should do to prevent this problem in the future, not what sysadmins should do to wise up to it. I know that talk of idiot-proofing the OS isn't too popular around here, at least not with the hardcore Linux geeks. But I've never heard Red Hat Linux be accused of being for hardcore Linux geeks.
I see your point. But the fact is that BIND and caching-nameserver can coexist on the same box (obviously, because caching-nameserver is dependent on BIND). Red Hat would save themselves some trouble by just correcting this on their end (perhaps something in system-config-bind for toggling between serving records and just caching...similar to the "switchmail" app for toggling between Sendmail and Postfix). If the flag for serving records is checked, then the system will protect named.conf regardless of whether caching-nameserver is installed. I suspect this would serve Red Hat better than just hoping sysadmins miraculously become smarter.
You have a point. You also need to get real. It is a bug when an update overwrites your configuration file.
It would have been more effective had the voice been GladOS.
Maybe this is what Miss Teen South Carolina was talking about?
I wonder if they left in the scene where a Storm Trooper bumps his head while going through a door...
It's difficult being a male looking for a new car these days.
-If you purchase a large sedan, you're old.
-If you purchase a small sedan, you're gay.
-If you purchase a minivan, you're whipped.
-If you purchase either a sports car, SUV, or large pickup truck, you have a small penis.
What does that leave? A Schwinn?
Now we can liberate the Martians.
I just made a Klingon battle cruiser out of an old Zip® disk. Picture below:
Woops. I guess it's cloaked.
You don't need to get a different box to play Q3 on Linux.
Just download the Linux binary from ID, and pull the pak0.pk3 file off the CD of the Windows version.
I'm not much for conspiracy theories, but say these record companies give this pay-for-online-music thing a half-assed effort. Say it does indeed flop, miserably. They can then come back and say: "See! If we were to change our business model to accomodate the changes in technology, our industry will collapse! Senator Hollings, your thoughts? .."
And don't forget the *speed*. Developers are so concerned with having players move at a realistic speed, that they forget that it's fun to whiz around a level at a pace faster than your mind can think.
Dozens of monsters swarming you all at once
Aye! The one current game I can think of that offers this is Serious Sam 2 (I'm sure the original does, as well, but I've yet to play it). An arcade-style romp that you don't need 53 fingers to play.
Freud would be proud.
You knuckleheads act as if Lucas is supposed to be Jesus. He's a filmmaker, people. Films are his business. Get off his ass.
Code Monkey: "Hello, I am calling to speak to you about the infinite possibilities Red Hat Linux offers your company."
IT Manager: "Oh? What are they?"
Code Monkey: "RTFM!"
*click*