Comment Bon voyage! (Score 1) 1521
It's been a long road, good luck on your future endeavors!
Google Mistook Jackson Searches For Net Attack 256
Slatterz writes "Web giant Google has admitted it thought the sudden spike in searches for Michael Jackson on Thursday was a massive, coordinated internet attack, leading it to post an error page on Google News. The company's director of product management, RJ Pittman, explained that search volume began to increase around 2pm PDT on Thursday and 'skyrocketed' by 3pm, finally stabilising at around 8pm. According to Pittman, last week also saw one of the largest mobile search spikes ever seen, with 5 of the top 20 searches about Jackson. Google wasn't the only site caught out by the extraordinary events. The Los Angeles Times web site also crashed soon after it broke the news of Jackson's death."
Comment Re:I almost hate to say it but.... (Score 1) 961
Nothing's wrong with using anime characters. Or any other name for that matter.
I have a small network, like yours (four machines in the local area, one in my office at work, and my brother's machine which seems to have a habit of becoming a part of my network every so often). I find that a naming system works. I know exactly what each machine does based on its name. (I also was able to do this based on 3.5" floppy disks.) I even have my own pet names for servers at work ('starlight' and 'vengeance' are two of my favorites).
I'm kinda locked in this system though because two of my machines are nameservers and changing them isn't *that* easy.
The system we use in the office is that each machine has an identification based on its purpose. It's functional and easy to work with in a professional environment (not to mention more professional than having randomly-named servers), but it's not really as much fun.
For a functional naming system for over 2000 computers, you've got me. The local university uses a scheme which is computer lab ID-computer number (e.g. poe216-0001). However, it's not easy to identify the machine and whether or not its Solaris, NT, Linux, Mac, BeOS, or Dreamcast running NetBSD ( :) ) without either going to look at the machine in the lab or consulting some high-and-mighty chart in a binder somewhere. But, I guess, for scalable naming conventions with many, many hosts, you lose the ability to have completely unique host IDs that can make sense or are readily recognizeable.
I have a small network, like yours (four machines in the local area, one in my office at work, and my brother's machine which seems to have a habit of becoming a part of my network every so often). I find that a naming system works. I know exactly what each machine does based on its name. (I also was able to do this based on 3.5" floppy disks.) I even have my own pet names for servers at work ('starlight' and 'vengeance' are two of my favorites).
I'm kinda locked in this system though because two of my machines are nameservers and changing them isn't *that* easy.
The system we use in the office is that each machine has an identification based on its purpose. It's functional and easy to work with in a professional environment (not to mention more professional than having randomly-named servers), but it's not really as much fun.
For a functional naming system for over 2000 computers, you've got me. The local university uses a scheme which is computer lab ID-computer number (e.g. poe216-0001). However, it's not easy to identify the machine and whether or not its Solaris, NT, Linux, Mac, BeOS, or Dreamcast running NetBSD (
Slashdot Top Deals
Credit ... is the only enduring testimonial to man's confidence in man. -- James Blish
