It does not bloody well make administration easier! If you have say X servers scattered over Y locations, it makes sense to call them:
(site)(os)(function)(number)
i.e.
sydwindb002
meaning sydney windows database 002
as opposed to tauron or frickin picon, or smurf (I'm not kidding you). Best of all though I've seen was server. Just server.
Serving what?? This was in a rack of 27 severs in total.
As a sysad, it shits me when people come up with 'cute' nonsensical names that have no consistency and aren't self explanatory. I mean, good software engineering principles dictate that you use meaningful variable names. Why not server names as well?
To my PHBs it is, because it is more complicated than Word.
In an ideal world, all my users would be using GNUStep on Debian, using mutt for email, and writing their reports in vim, because to me it is not complicated. But for some reason, it all seems too complicated to them, so we have to keep using Windows, Outlook and Word. I just don't know...
Because Mac's implementation of LDAP, and integrating it with NFS/Samba is awesome.
I mean, have you ever actually tried building a network with LDAP/kerberos authenticated file sharing from scratch using BSD? Good luck to ya.
That, and their (albeit proprietary) wiki is WYSIWYG, and doesn't require the knowledge of markup language. It is great for introducing non-tech types to wikis.
Weeeel, technically no. You can just create a dirty bomb that merely turns the plutonium into vapour/dust as opposed to trying to go for a fission reaction.
Ahem, anyway, I do agree with the GP, if you can re-flash it, there is a high probability that you have a working drive, and even if the data is now out of sync, you can do a raw dump and repair the FS using any of the many data recovery tools out there.
Whilst this is an absolutely embarrassing move by Seagate, it isn't ZOMFG we've all lost our dataz.
Hmmm, how about this as a shining example of Microsoft awesome:
"Win32 application programming interfaces (APIs) have a maximum path limit of 260 characters. Applications fail when trying to access a namespace that goes beyond that limit. If the path length of a DFS namespace exceeds the Win32 API limit of 260 characters, users must map part of the namespace to a drive letter and access the longer namespace through the mapped drive letter."
This dumbass limitation has been in windows since the win32 API has been around. Will they fix it? Noooooooooooooo, because it'll break compatibility with old fart software. Can you yourself then fork it and rewrite the offending code? Nooooooooooooo, because the softwre is proprietary.
This problem is the bane of my existence, as NTFS supports 2^32 addressing, but any win32 applications trying to manipulate paths longer than 260 characters suffer an epic fail.
I'm sorry, but such idiotic "features" are unique to Microsoft.
Yes, but all the examples you mentioned are not Operating Systems, so he still has a point.
Leaving legacy kernel/userland code from the NT 3.5 days in Windows 7 for "backwards compatibility" is a terrible for progress. Nothing makes a sysad's life more of a nightmare than dealing with the same bugs (features) in XP, 2003 and Vista that have been around since NT.
Sorry, but R is not relatively new, it's been around for at least 10 years, I was taught how to use R at University back in 2001, and S and later S+ (which R is a FOSS version of) has been around for even longer, since the mid 70's.
I'm not sure I agree. Every mobile interface I've used before wasn't intuitive and felt rushed and unpolished.
The iPhone's interface is nice, so for those who can afford the whopping price tag, and don't mind the stigma of "ooh you've got an iPhone, you must be a Mac guy", it is an nifty phone/pda.
Everything else is either a phone trying to have PDA features (and failing), or uses windows (crash city).
People know not to open executable files (.exe) and even for more obtuse executables (.scr,.cmd) most systems and mail clients are smart enough to warn that it's executable content.
Which people are you referring to then? Surely not the average user.
I strongly agree. I software shop I worked in previously suffered from dumbass graduate developers, who suffered not from lack of ability to write code, but from not being able to comprehend problems, think laterally, and come up with some sort of sane solutions.
Anyone can memorise the syntax of a language. Not everyone can apply it logically.
Slashdot Mirror
It does not bloody well make administration easier! If you have say X servers scattered over Y locations, it makes sense to call them:
(site)(os)(function)(number)
i.e.
sydwindb002
meaning sydney windows database 002
as opposed to tauron or frickin picon, or smurf (I'm not kidding you). Best of all though I've seen was server. Just server.
Serving what?? This was in a rack of 27 severs in total.
As a sysad, it shits me when people come up with 'cute' nonsensical names that have no consistency and aren't self explanatory. I mean, good software engineering principles dictate that you use meaningful variable names. Why not server names as well?
To you and me, no of course it isn't.
To my PHBs it is, because it is more complicated than Word.
In an ideal world, all my users would be using GNUStep on Debian, using mutt for email, and writing their reports in vim, because to me it is not complicated. But for some reason, it all seems too complicated to them, so we have to keep using Windows, Outlook and Word. I just don't know...
Because Mac's implementation of LDAP, and integrating it with NFS/Samba is awesome.
I mean, have you ever actually tried building a network with LDAP/kerberos authenticated file sharing from scratch using BSD? Good luck to ya.
That, and their (albeit proprietary) wiki is WYSIWYG, and doesn't require the knowledge of markup language. It is great for introducing non-tech types to wikis.
Twitter or not, the poster has a point. Most of the spammers use Windows trojan powered botnets.
EPIC_FAIL.exe
Weeeel, technically no. You can just create a dirty bomb that merely turns the plutonium into vapour/dust as opposed to trying to go for a fission reaction.
Dirty Bombs are pretty trivial to make.
Quite possibly:
(Seagate to cut 6 pct of global staff) http://www.fresnobee.com/385/story/1129875.html
Brickety Brick McBrick Brick.
Ahem, anyway, I do agree with the GP, if you can re-flash it, there is a high probability that you have a working drive, and even if the data is now out of sync, you can do a raw dump and repair the FS using any of the many data recovery tools out there.
Whilst this is an absolutely embarrassing move by Seagate, it isn't ZOMFG we've all lost our dataz.
I've heard stories of the pilot station doing constant reboots during missions.
Windows update strikes again.
Press Release: Redmnond announces Windows 7 takes up just 71% of hard drive, hailed as breakthrough!
Yes, unfortunately it does, as windows 7 is a 100% win32 API backwards compatible OS.
Hmmm, how about this as a shining example of Microsoft awesome:
"Win32 application programming interfaces (APIs) have a maximum path limit of 260 characters. Applications fail when trying to access a namespace that goes beyond that limit. If the path length of a DFS namespace exceeds the Win32 API limit of 260 characters, users must map part of the namespace to a drive letter and access the longer namespace through the mapped drive letter."
This dumbass limitation has been in windows since the win32 API has been around. Will they fix it? Noooooooooooooo, because it'll break compatibility with old fart software. Can you yourself then fork it and rewrite the offending code? Nooooooooooooo, because the softwre is proprietary.
This problem is the bane of my existence, as NTFS supports 2^32 addressing, but any win32 applications trying to manipulate paths longer than 260 characters suffer an epic fail.
I'm sorry, but such idiotic "features" are unique to Microsoft.
Yes, but all the examples you mentioned are not Operating Systems, so he still has a point.
Leaving legacy kernel/userland code from the NT 3.5 days in Windows 7 for "backwards compatibility" is a terrible for progress. Nothing makes a sysad's life more of a nightmare than dealing with the same bugs (features) in XP, 2003 and Vista that have been around since NT.
That is the weirdest fetish I've ever heard; having girls shave your. This guy sounds like a complete creep and a pedo.
Sorry, but R is not relatively new, it's been around for at least 10 years, I was taught how to use R at University back in 2001, and S and later S+ (which R is a FOSS version of) has been around for even longer, since the mid 70's.
Some of the more subtle political satire can not really be made into a game, or if it was the game would be really boring.
I'm not sure I agree. Every mobile interface I've used before wasn't intuitive and felt rushed and unpolished.
The iPhone's interface is nice, so for those who can afford the whopping price tag, and don't mind the stigma of "ooh you've got an iPhone, you must be a Mac guy", it is an nifty phone/pda.
Everything else is either a phone trying to have PDA features (and failing), or uses windows (crash city).
so uhm, keep a copy somewhere secure?
That still relies on the average user not being a retard, and having the presence of mind to do so. Sorry, and that ain't happening any time soon.
Remember, the moment you design an idiot proof system, someone invents a better idiot.
It does, here is a RAID 5 example: http://support.microsoft.com/kb/323434
People know not to open executable files (.exe) and even for more obtuse executables (.scr, .cmd) most systems and mail clients are smart enough to warn that it's executable content.
Which people are you referring to then? Surely not the average user.
He did specify .wri attachments you know, but the axe thing is equally good in my books.
I strongly agree. I software shop I worked in previously suffered from dumbass graduate developers, who suffered not from lack of ability to write code, but from not being able to comprehend problems, think laterally, and come up with some sort of sane solutions.
Anyone can memorise the syntax of a language. Not everyone can apply it logically.
Don't worry, it still doesn't. I'm just trying to rationalise the EPIC FAIL of a joke to stop my brain from exploding :)
O_o
*scrabbles for passport*
Only if you pronounce it MySEQUEL.