Linux file system hierarchy
-
@scottalanmiller Based on what? Even manuals as far back as 1984, which I linked, point out it is short for et cetera. If it wasn't short for et cetera, what would it possibly be short for?
/usr is user, I sort of feel like you're being sarcastic now, because /usr was the original location for home directories, like /usr/dmr for Dennis Ritchie. I don't know of early attestments at all that these are anything except abbreviations, the acronyms come much later, seemingly the late 90s and early 2000s is when they were made popular.
If there are attestments that /usr means anything other than user, and /etc means anything other than et cetera prior to 1984, I'd love to see them, and that isn't sarcasm, but it's as far back as I was able to find, granted I didn't look too hard.
I do know people have been saying etsee for a long time, I even said I've heard of people saying it for years, I've never witnessed this myself though at all.
But you mention AIX, so I'm curious now if that has something to do with it at well. We're all saying Unix and even talking about Linux, but I'm starting to wonder if the overall community also has influence on this as well. I'm surprised you've never heard "et cetera" before, even 20 years ago I remember explicitly hearing that, because early on I said "e-t-c", and this was in the Linux community at the time, later on I got heavily involved in FreeBSD and also Sun, but admittedly I didn't have voice discussions about Sun that much, mostly electronic so I can't say with any confidence how people in that community said much of anything.
-
What drives me really crazy is when people are sloppy with SQL. Unlike /etc which has no defining body with authoritative pronunciation decision making power to determine what it must be, SQL, in all cases, does have a current, existing body that determines how it is pronounced in every instance. This is because the pronunciation is determined by the vendors who make the product. There is no ambiguity. Yet, for a series of products where there is no grey area, few things are pronounced more loosely!! In many cases these are commercial product or company names, not subject to personal interpretation.
SQL the language is pronounced "ess cue ell" and is owned and defined by IBM and several standards bodies. The pronunciation guide was built into the spec to make sure no one mistook the intent since SQL replaced the earlier SEQUEL language which, quite obviously, was pronounced "sequel."
MS SQL Server is also pronounced "sequel server" and is owned and defined by Microsoft. This is the only major vendor pronouncing it in this fashion.
MySQL is pronounced "my ess cue ell" and is owned and defined by Oracle.
PostgreSQL is pronounced "Post gress cue ell" and is owned and defined by PostgreSQL itself.
-
@scottalanmiller said:
What drives me really crazy is when people are sloppy with SQL. Unlike /etc which has no defining body with authoritative pronunciation decision making power to determine what it must be, SQL, in all cases, does have a current, existing body that determines how it is pronounced in every instance. This is because the pronunciation is determined by the vendors who make the product. There is no ambiguity. Yet, for a series of products where there is no grey area, few things are pronounced more loosely!! In many cases these are commercial product or company names, not subject to personal interpretation.
SQL the language is pronounced "ess cue ell" and is owned and defined by IBM and several standards bodies. The pronunciation guide was built into the spec to make sure no one mistook the intent since SQL replaced the earlier SEQUEL language which, quite obviously, was pronounced "sequel."
MS SQL Server is also pronounced "sequel server" and is owned and defined by Microsoft. This is the only major vendor pronouncing it in this fashion.
MySQL is pronounced "my ess cue ell" and is owned and defined by Oracle.
PostgreSQL is pronounced "Post gress cue ell" and is owned and defined by PostgreSQL itself.
I remember talking to you about this at Spiceworks meeting and I did research (by that I mean looked it up for once) after we spoke and I saw you were right. I try to say "Sequel" for everything except the name "MySQL" but I sometimes fall back into saying "S-Q-L" for the language, but far less often than I used to. I always said "Sequel" for SQL Server and T-SQL, etc. My main confusion was calling SQL used for MySQL "S-Q-L" as well, not just in the name.
Edit: I'm now confused, are you saying the language is or is not "Sequel" since it replaced "SEQUEL"?
-
@tonyshowoff said:
My main confusion was calling SQL used for MySQL "S-Q-L" as well, not just in the name.
I'm not sure how that is pronounced in that one case. If MySQL is using stock SQL, then the pronunciation would be as defined by the standard. But if they are using their own modification of it, like MS does with T-SQL, then they would need their own name and could define their own pronunciation of it. But as it is, it appears that they use the SQL name from SQL itself so it is just S-Q-L. Which, since they is how they pronounce the product name, it already matches so I am sure that they would want that anyway.
-
@scottalanmiller Well, whatever happens, I'm just glad I'm not one of those gauche people who says "My SEQUEL", curiously I've even heard big-time MySQL people say this, it just sounds weird though.
-
@tonyshowoff said:
@scottalanmiller Well, whatever happens, I'm just glad I'm not one of those gauche people who says "My SEQUEL", curiously I've even heard big-time MySQL people say this, it just sounds weird though.
I know, me too. It always makes me question how much experience they really have if they aren't even aware of the product's name! Even casual users would, one would hope, take the time to ask how it is pronounced. That's very basic. It sounds weird and grating to hear it the wrong way too.
-
You can tell the pure Microsoft folks because they are often unaware that the relational database world is older and and far, far larger than just MS SQL Server. If you look in SW you often see people abbreviating MS SQL Server down to just "SQL" which isn't even the name of the language it uses let alone the product. This can be very confusing since there are tons of "SQL servers" like Oracle, Sybase, Informix, MySQL, MariaDB, PostgreSQL, MS SQL Server, SQLite and on and on. Using "SQL server" as some bizarre term meaning "relational database" is really poor.
-
@scottalanmiller said:
You can tell the pure Microsoft folks because they are often unaware that the relational database world is older and and far, far larger than just MS SQL Server.
Our conversation at Spiceworks on this issue actually began because I had mentioned an IT guy had told me that "Anyone who pronounces MySQL as anything other than My Sequel shows they don't really know anything about Sequel." And he tried to be a condescending smart ass, ironically he didn't even know basic SQL syntax, so I'm not sure what he was on about.
I only say "SQL Server" in the context of Microsoft if that's a part of the discussion, otherwise I do clarify MSSQL or Microsoft SQL Server. I do see people say "SQL Server" as if it's a definable product like Windows, when there are many, many servers which allow SQL. And really Sybase also calls theirs that too, IIRC, I may be wrong about that, it's been nearly 15 years.
-
I'd also like to add to Post 27 that for the most part almost all of the discussions I've had offline about Unix and Linux have been with Europeans, or Americans at conventions like Defcon, Blackhat, and HOPE, and that could also be a major influence on what I've heard as well, not having heard etsee at all prior to that. Additionally in the corporate world, I always heard "e-t-c". Even at large, nation unnamed ISP I worked there were many Unix machines, later replaced mostly by Linux, and in conversations I had with the various sysadmins, they either said "e-t-c" or one person specifically did say "et cetera."
So, perhaps there's a large gap between the European communities, hacker communities, and other corporate communities like with IBM. I'm still curious about any mention of pronunciation or non-abbreviated meaning any old manuals, especially standard setting/referencing ones may have if you know of any, but they're old manuals, and I haven't met many people aside from me that cares to read obsolete material.
-
@tonyshowoff said:
I only say "SQL Server" in the context of Microsoft if that's a part of the discussion, otherwise I do clarify MSSQL or Microsoft SQL Server. I do see people say "SQL Server" as if it's a definable product like Windows, when there are many, many servers which allow SQL. And really Sybase also calls theirs that too, IIRC, I may be wrong about that, it's been nearly 15 years.
In print the capitalization allows you to say simply SQL Server to mean the Microsoft product of that name rather than a generic server that uses SQL which would be a SQL server. Capitalized it is always Microsoft, not capitalized it is always generic. Just like the space does with XenServer. XenServer is a full packaged product based on Xen and CentOS. A Xen server (with a space) is any server built on Xen technology including ones from Ubuntu, Oracle and Suse. XenServer is a Xen server, but so are many other things. MS SQL Server, MySQL, SQLite are all SQL servers.
I normally say "M-S SQL Server" in speech to be clear.
Once upon a time (pre 1997, I think) MS SQL Server and Sybase were the same product. They split at some point. For a long time, MS SQL Server was just Sybase repackaged. To the best of my knowledge, Sybase has not had a product called "SQL Server" for decades. They make things like ASE now.
-
@scottalanmiller said:
Once upon a time (pre 1997, I think) MS SQL Server and Sybase were the same product. They split at some point. For a long time, MS SQL Server was just Sybase repackaged. To the best of my knowledge, Sybase has not had a product called "SQL Server" for decades. They make things like ASE now.
Shows you when the last time I messed around with that
Same company I worked for switched from Sybase, flat files, and some other weird stuff inherited from some acquisitions to Oracle, I guess for a desire to spend even more money on licenses 
-
@tonyshowoff said:
So, perhaps there's a large gap between the European communities, hacker communities, and other corporate communities like with IBM. I'm still curious about any mention of pronunciation or non-abbreviated meaning any old manuals, especially standard setting/referencing ones may have if you know of any, but they're old manuals, and I haven't met many people aside from me that cares to read obsolete material.
IBM had it in the material for the AIX certs circa 2000. So that material almost had to be from 1999 or before, it would have been hard to have produced it more recently than that. Pronunciations for "etc" and "usr" were drilled into us. But it was less corporate and more "UNIX", AIX back then was very, very mainstream and one of the dominant players (this was before the explosion in Linux adoption) and vendors like IBM and Sun calling it "etsee" made for the majority of the industry then.
Since Sun's team and AT&T's Bell Labs team sat together and worked together, I'd be surprised if "etsee" wasn't a direct trickle down from AT&T themselves.
-
@scottalanmiller said:
SQL the language is pronounced "ess cue ell" and is owned and defined by IBM and several standards bodies.
A quick googling says the ISO standard pronounces it "es queue el", although I can't find any original sources. I've always pronounced it (the language) like that, and the products according to how the vendor pronounces them (ie MS sequal server, MyS-Q-L). There seems to be enough ambiguity on the official pronunciation to mean that both are valid.
-
@tonyshowoff said:
@scottalanmiller Well, whatever happens, I'm just glad I'm not one of those gauche people who says "My SEQUEL", curiously I've even heard big-time MySQL people say this, it just sounds weird though.
@scottalanmiller said:
I know, me too. It always makes me question how much experience they really have if they aren't even aware of the product's name! Even casual users would, one would hope, take the time to ask how it is pronounced. That's very basic. It sounds weird and grating to hear it the wrong way too.
I completely disagree with this.
I know exactly how it is pronounced, yet I never say it that way because it is clunky. Very rarely does anyone pronounce the individual letters of ANY acronym when they can be spoken in a more fluid method.
In this case the hard Q is the killer sound that makes it not flow right.
I cannot stand anal people that go off on "correct" when the smoothed pronunciation is a completely accepted standard.
-
@scottalanmiller said:
I know, me too. It always makes me question how much experience they really have if they aren't even aware of the product's name!
As an aside, this makes you sound like a condescending ass. You are assuming someones skill level based on pronunciation.
-
Most of my knowledge comes from the written word (books and forums) rather than the spoken word (classroom training and meeting other IT people) so I don't always get to hear the correct pronounciation.
It was only last week that I learnt FSMO is pronounced Fizz-Mo, I'd have just pronounced it F-S-M-O (and suffered the wrath of @scottalanmiller).
I also pronounce Porche with a silent 'e', even though I know it's wrong, because I think the correct pronunciation sounds a bit crap.
Sequal, S-Q-L - really, who cares?
-
@Carnival-Boy said:
I also pronounce Porche with a silent 'e', even though I know it's wrong, because I think the correct pronunciation sounds a bit crap.
As a German speaker from a very young age, the silent "e" that I (don't) hear from Americans and some English is weird sounding to me, it's simply "Porsha", but I get why it's such a cultural norm, because English spelling is retarded, most languages don't have silent letters or spelling bees, because things are mostly spelled closer to pronunciation than "just because," and more confusing is when people defend the bizarre spelling as a feature which makes English unique, instead of the large vocabulary which is actually what makes English unique, and vocabulary doesn't care how it's spelled, but that's way off topic.
Anyway, I've had similar issue over the years with initialisms and acronyms, FSMO was one, and years ago so was GUI, gif, and a billion others I can't think of but managed to get way wrong for years; you never get the chance to really know how they should be pronounced unless speaking in person or someone happens to be having a conversation like this one. If nothing else, mispronunciation of common acronyms may show more of a lack of AFK-contact with other computer people, rather than lack of knowledge.
-
@tonyshowoff said:
because English spelling is retarded, most languages don't have silent letters or spelling bees, because things are mostly spelled closer to pronunciation than "just because,"
I love Japanese because of this. The language is completely syllabic. Everything written in Hiragana is pronounced exactly like it looks, and every Kanji has a hiragana pronunciation..
Like any language it has quirks, but pronunciation is not one of them.
-
@tonyshowoff said:
If nothing else, mispronunciation of common acronyms may show more of a lack of AFK-contact with other computer people, rather than lack of knowledge.
Quote for effect - that was awesome!
-
@tonyshowoff said:
As a German speaker from a very young age, the silent "e" that I (don't) hear from Americans and some English is weird sounding to me, it's simply "Porsha", but I get why it's such a cultural norm, because English spelling is retarded, most languages don't have silent letters or spelling bees....
I hate spelling bees as English does not have a formal or official spelling and nearly all words have optional spellings. That schools even think that spelling bees are possible shows that the teachers are not aware of the nature of the language.
