Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #286414 > unrolled thread
| Started by | owl <owl@rooftop.invalid> |
|---|---|
| First post | 2015-03-27 22:46 +0000 |
| Last post | 2015-03-29 12:57 +0000 |
| Articles | 20 on this page of 54 — 7 participants |
Back to article view | Back to comp.os.linux.advocacy
NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-27 22:46 +0000
Re: NTFS is case-sensitive Slimer <slvrslmr@lv.c> - 2015-03-27 19:29 -0400
Re: NTFS is case-sensitive John Gohde <john.h.gohde@gmail.com> - 2015-03-28 08:45 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 16:00 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 16:26 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 12:56 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 17:06 +0000
Re: NTFS is case-sensitive John Gohde <john.h.gohde@gmail.com> - 2015-03-28 10:32 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-28 13:08 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 22:22 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-28 21:40 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-28 22:23 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-29 11:06 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-29 15:12 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-29 21:22 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-29 23:08 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-29 09:18 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-29 21:22 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-29 18:27 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-30 02:16 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 09:49 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 08:24 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-30 17:06 +0000
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 12:19 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-30 23:54 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-31 00:06 +0000
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 17:12 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 17:41 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 17:15 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-31 01:07 +0000
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 18:21 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 12:24 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 20:46 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-31 01:52 +0000
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 19:10 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 11:35 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 23:09 -0400
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 22:01 -0700
NTFS is not the best filesystem taka0038@gmail.com - 2015-03-31 18:52 -0700
Re: NTFS is not the best filesystem Slimer <slvrslmr@lv.c> - 2015-03-31 22:51 -0400
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 09:48 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 08:44 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 09:37 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 20:50 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 19:14 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-28 17:09 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-29 00:24 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 22:26 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 16:09 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 13:06 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 17:15 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 17:28 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 18:35 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-29 12:57 +0000
Page 2 of 3 — ← Prev page 1 [2] 3 Next page →
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2015-03-30 09:49 -0400 |
| Message-ID | <mfbk7j$4fp$3@dont-email.me> |
| In reply to | #286667 |
On 3/29/2015 10:16 PM, owl wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 3/29/15, 6:22 PM, in article mfa8fq$7c6$3@dont-email.me, "DFS" >> <nospam@dfs.com> wrote: > >>> On 3/29/2015 12:18 PM, Snit wrote: >>>> On 3/29/15, 8:06 AM, in article mf94c6$s6t$1@dont-email.me, "DFS" >>>> <nospam@dfs.com> wrote: >>>> >>>>>>> pwnage earned by changing the case of one letter? Epic! >>>>>>> >>>>>>> owl is a tricky bastard and it's hard to get one by him. >>>>>>> >>>>>>> Congrats! >>>>>> >>>>>> Thanks. Wish I could say it was fully on purpose. :) >>>>> >>>>> >>>>> The plot thickens... you spelled it Owl by accident? >>>>> >>>>> That would change it from Snit pwnage to owl self-nuke, and your trophy >>>>> must be returned. >>>> >>>> Fair enough. I humbly return the trophy... and grant Owl the mushroom cloud >>>> reward. :) >>> >>> It's good you came clean - 5 months later - but an 'honest and >>> honorable' man would've never let my assumption stand in the first >>> place. I always figured you intentionally wrote 'Owl' to try and trick >>> him, since you were in the middle of a case-sensitivity debate. >>> >>> Instead of admitting it right then, you took credit for it several times >>> when I brought it up as pwnage, and said "That was fun". >>> >>> Why did you finally admit it wasn't intentional? > >> It was fun to see him self-nuke. Never implied it was intentional. > > In your deranged minds it is a self-nuke for me to correct your > misspelling of my name when you are using that misspelled name to address > me in conversation, as determined circumstantially by the fact that it > was used in a sentence where one would normally expect to find himself > being addressed. "Hey, jOe, where you going with that gun in your hand?" > > Somehow in your (French-influenced?) mush-heads, not continuing > on as if the misspelling were without consequence, i.e. in the way > that a case-insensitive file system would react, is evidence of my > own case-insensitivity, and therefore worthy of a self-nuke award. Yes, lamer. Exactly. A case-sensitive filesystem or programming language or gibbon wouldn't have recognized Owl as your name. You did. Normally not worth noting, except this time you did it while in the middle of arguing FOR case-sensitivity. epic self-nuke! > Since exactly the opposite is true, and the misspelling was detected, > not overlooked, I can only say that you both have my pity for having > such broken reasoning skills. :) Learn some humility, boy. Accept your self-wrought defeat.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 08:24 -0700 |
| Message-ID | <D13EB8B0.4945B%usenet@gallopinginsanity.com> |
| In reply to | #286716 |
On 3/30/15, 6:49 AM, in article mfbk7j$4fp$3@dont-email.me, "DFS" <nospam@dfs.com> wrote: ... >>> It was fun to see him self-nuke. Never implied it was intentional. >> >> In your deranged minds it is a self-nuke for me to correct your >> misspelling of my name when you are using that misspelled name to address >> me in conversation, as determined circumstantially by the fact that it >> was used in a sentence where one would normally expect to find himself >> being addressed. "Hey, jOe, where you going with that gun in your hand?" >> >> Somehow in your (French-influenced?) mush-heads, not continuing >> on as if the misspelling were without consequence, i.e. in the way >> that a case-insensitive file system would react, is evidence of my >> own case-insensitivity, and therefore worthy of a self-nuke award. > > Yes, lamer. Exactly. > > A case-sensitive filesystem or programming language or gibbon wouldn't > have recognized Owl as your name. You did. Normally not worth noting, > except this time you did it while in the middle of arguing FOR > case-sensitivity. > > epic self-nuke! And he keeps doing it. Look at his complaints about firefox. I mean Firefox. LOL! He ended up having to resort to the idea that the name of the program and the name of the executable are different and this is NOT a problem as a defense for why his goof on the capitalization did not matter. His argument is like saying I can make a product and call it "ubuntu" or "linux" and that is fine because it will not cause any confusion with those looking for "Ubuntu" or "Linux". >> Since exactly the opposite is true, and the misspelling was detected, >> not overlooked, I can only say that you both have my pity for having >> such broken reasoning skills. :) > > Learn some humility, boy. Accept your self-wrought defeat. Exactly. He goofed. At the very least you would think he would focus on the rare edge cases where case sensitivity is an actual advantage - such as having a folder with dictionary terms and wanting to have proper and common nouns. -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-03-30 17:06 +0000 |
| Message-ID | <shfu30.3e@rooftop.invalid> |
| In reply to | #286716 |
DFS <nospam@dfs.com> wrote: > On 3/29/2015 10:16 PM, owl wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 3/29/15, 6:22 PM, in article mfa8fq$7c6$3@dont-email.me, "DFS" >>> <nospam@dfs.com> wrote: >> >>>> On 3/29/2015 12:18 PM, Snit wrote: >>>>> On 3/29/15, 8:06 AM, in article mf94c6$s6t$1@dont-email.me, "DFS" >>>>> <nospam@dfs.com> wrote: >>>>> >>>>>>>> pwnage earned by changing the case of one letter? Epic! >>>>>>>> >>>>>>>> owl is a tricky bastard and it's hard to get one by him. >>>>>>>> >>>>>>>> Congrats! >>>>>>> >>>>>>> Thanks. Wish I could say it was fully on purpose. :) >>>>>> >>>>>> >>>>>> The plot thickens... you spelled it Owl by accident? >>>>>> >>>>>> That would change it from Snit pwnage to owl self-nuke, and your trophy >>>>>> must be returned. >>>>> >>>>> Fair enough. I humbly return the trophy... and grant Owl the mushroom cloud >>>>> reward. :) >>>> >>>> It's good you came clean - 5 months later - but an 'honest and >>>> honorable' man would've never let my assumption stand in the first >>>> place. I always figured you intentionally wrote 'Owl' to try and trick >>>> him, since you were in the middle of a case-sensitivity debate. >>>> >>>> Instead of admitting it right then, you took credit for it several times >>>> when I brought it up as pwnage, and said "That was fun". >>>> >>>> Why did you finally admit it wasn't intentional? >> >>> It was fun to see him self-nuke. Never implied it was intentional. >> >> In your deranged minds it is a self-nuke for me to correct your >> misspelling of my name when you are using that misspelled name to address >> me in conversation, as determined circumstantially by the fact that it >> was used in a sentence where one would normally expect to find himself >> being addressed. "Hey, jOe, where you going with that gun in your hand?" >> >> Somehow in your (French-influenced?) mush-heads, not continuing >> on as if the misspelling were without consequence, i.e. in the way >> that a case-insensitive file system would react, is evidence of my >> own case-insensitivity, and therefore worthy of a self-nuke award. > Yes, lamer. Exactly. > A case-sensitive filesystem or programming language or gibbon wouldn't > have recognized Owl as your name. You did. Normally not worth noting, > except this time you did it while in the middle of arguing FOR > case-sensitivity. > epic self-nuke! So if he had addressed me as "Bob" in a direct reply to my post, and I had corrected him that "Bob" is not my name, that would also have been a self-nuke?
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 12:19 -0700 |
| Message-ID | <D13EEFD4.494C4%usenet@gallopinginsanity.com> |
| In reply to | #286757 |
On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: >>> In your deranged minds it is a self-nuke for me to correct your >>> misspelling of my name when you are using that misspelled name to address >>> me in conversation, as determined circumstantially by the fact that it >>> was used in a sentence where one would normally expect to find himself >>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>> >>> Somehow in your (French-influenced?) mush-heads, not continuing >>> on as if the misspelling were without consequence, i.e. in the way >>> that a case-insensitive file system would react, is evidence of my >>> own case-insensitivity, and therefore worthy of a self-nuke award. > >> Yes, lamer. Exactly. > >> A case-sensitive filesystem or programming language or gibbon wouldn't >> have recognized Owl as your name. You did. Normally not worth noting, >> except this time you did it while in the middle of arguing FOR >> case-sensitivity. > >> epic self-nuke! > > So if he had addressed me as "Bob" in a direct reply to my post, > and I had corrected him that "Bob" is not my name, that would > also have been a self-nuke? How about your self-nuke of referring to the program Firefox as "firefox", and then your effort to save yourself by noting he executable file is called "firefox" and not "Firefox", even though the program is. It is largely of the inherent challenges of using a case sensitive file system that they use all lower case letters in program names in Linux (or at least generally recommend people to). On OS X which does not have that challenge the mozilla team calls the program bundle itself "Firefox". -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-03-30 23:54 +0000 |
| Message-ID | <bvhe03fa.p3@rooftop.invalid> |
| In reply to | #286803 |
Snit <usenet@gallopinginsanity.com> wrote: > On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >>>> In your deranged minds it is a self-nuke for me to correct your >>>> misspelling of my name when you are using that misspelled name to address >>>> me in conversation, as determined circumstantially by the fact that it >>>> was used in a sentence where one would normally expect to find himself >>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>>> >>>> Somehow in your (French-influenced?) mush-heads, not continuing >>>> on as if the misspelling were without consequence, i.e. in the way >>>> that a case-insensitive file system would react, is evidence of my >>>> own case-insensitivity, and therefore worthy of a self-nuke award. >> >>> Yes, lamer. Exactly. >> >>> A case-sensitive filesystem or programming language or gibbon wouldn't >>> have recognized Owl as your name. You did. Normally not worth noting, >>> except this time you did it while in the middle of arguing FOR >>> case-sensitivity. >> >>> epic self-nuke! >> >> So if he had addressed me as "Bob" in a direct reply to my post, >> and I had corrected him that "Bob" is not my name, that would >> also have been a self-nuke? > How about your self-nuke of referring to the program Firefox as "firefox", > and then your effort to save yourself by noting he executable file is called > "firefox" and not "Firefox", even though the program is. The name of the file is "firefox." You know, a file, like might sit on the file system NTFS, the subject of this thread. Try to keep up. > It is largely of the inherent challenges of using a case sensitive file > system that they use all lower case letters in program names in Linux (or at > least generally recommend people to). On OS X which does not have that > challenge the mozilla team calls the program bundle itself "Firefox". That's irrelevant, but out of curiosity what is the executable called?
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-03-31 00:06 +0000 |
| Message-ID | <bhvh3e9.a3f0@rooftop.invalid> |
| In reply to | #286856 |
owl <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: >>>>> In your deranged minds it is a self-nuke for me to correct your >>>>> misspelling of my name when you are using that misspelled name to address >>>>> me in conversation, as determined circumstantially by the fact that it >>>>> was used in a sentence where one would normally expect to find himself >>>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>>>> >>>>> Somehow in your (French-influenced?) mush-heads, not continuing >>>>> on as if the misspelling were without consequence, i.e. in the way >>>>> that a case-insensitive file system would react, is evidence of my >>>>> own case-insensitivity, and therefore worthy of a self-nuke award. >>> >>>> Yes, lamer. Exactly. >>> >>>> A case-sensitive filesystem or programming language or gibbon wouldn't >>>> have recognized Owl as your name. You did. Normally not worth noting, >>>> except this time you did it while in the middle of arguing FOR >>>> case-sensitivity. >>> >>>> epic self-nuke! >>> >>> So if he had addressed me as "Bob" in a direct reply to my post, >>> and I had corrected him that "Bob" is not my name, that would >>> also have been a self-nuke? >> How about your self-nuke of referring to the program Firefox as "firefox", >> and then your effort to save yourself by noting he executable file is called >> "firefox" and not "Firefox", even though the program is. > The name of the file is "firefox." You know, a file, like might sit > on the file system NTFS, the subject of this thread. Try to keep up. >> It is largely of the inherent challenges of using a case sensitive file >> system that they use all lower case letters in program names in Linux (or at >> least generally recommend people to). On OS X which does not have that >> challenge the mozilla team calls the program bundle itself "Firefox". > That's irrelevant, but out of curiosity what is the executable called? Nevermind. Apparently it's "firefox" :) root@thinkpad:/tmp/macfire/Firefox.app/Contents/MacOS# ls crashreporter.app libmozglue.dylib libsoftokn3.dylib firefox libnss3.dylib plugin-container.app firefox-bin libnssckbi.dylib updater.app libfreebl3.dylib libnssdbm3.dylib XUL libmozalloc.dylib libplugin_child_interpose.dylib root@thinkpad:/tmp/macfire/Firefox.app/Contents/MacOS#
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2015-03-30 17:12 -0700 |
| Message-ID | <8a725478-8d1a-4d5e-9c46-63dd30ccf6dd@googlegroups.com> |
| In reply to | #286864 |
On Monday, March 30, 2015 at 6:06:38 PM UTC-6, owl wrote: > owl <owl@rooftop.invalid> wrote: > > Snit <usenet@gallopinginsanity.com> wrote: > >> On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" > >> <owl@rooftop.invalid> wrote: > > >>>>> In your deranged minds it is a self-nuke for me to correct your > >>>>> misspelling of my name when you are using that misspelled name to address > >>>>> me in conversation, as determined circumstantially by the fact that it > >>>>> was used in a sentence where one would normally expect to find himself > >>>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" > >>>>> > >>>>> Somehow in your (French-influenced?) mush-heads, not continuing > >>>>> on as if the misspelling were without consequence, i.e. in the way > >>>>> that a case-insensitive file system would react, is evidence of my > >>>>> own case-insensitivity, and therefore worthy of a self-nuke award. > >>> > >>>> Yes, lamer. Exactly. > >>> > >>>> A case-sensitive filesystem or programming language or gibbon wouldn't > >>>> have recognized Owl as your name. You did. Normally not worth noting, > >>>> except this time you did it while in the middle of arguing FOR > >>>> case-sensitivity. > >>> > >>>> epic self-nuke! > >>> > >>> So if he had addressed me as "Bob" in a direct reply to my post, > >>> and I had corrected him that "Bob" is not my name, that would > >>> also have been a self-nuke? > > >> How about your self-nuke of referring to the program Firefox as "firefox", > >> and then your effort to save yourself by noting he executable file is called > >> "firefox" and not "Firefox", even though the program is. > > > The name of the file is "firefox." You know, a file, like might sit > > on the file system NTFS, the subject of this thread. Try to keep up. > > >> It is largely of the inherent challenges of using a case sensitive file > >> system that they use all lower case letters in program names in Linux (or at > >> least generally recommend people to). On OS X which does not have that > >> challenge the mozilla team calls the program bundle itself "Firefox". > > > That's irrelevant, but out of curiosity what is the executable called? > > Nevermind. Apparently it's "firefox" :) > > root@thinkpad:/tmp/macfire/Firefox.app/Contents/MacOS# ls > crashreporter.app libmozglue.dylib libsoftokn3.dylib > firefox libnss3.dylib plugin-container.app > firefox-bin libnssckbi.dylib updater.app > libfreebl3.dylib libnssdbm3.dylib XUL > libmozalloc.dylib libplugin_child_interpose.dylib > root@thinkpad:/tmp/macfire/Firefox.app/Contents/MacOS# But XUL is where all the magic happens ;)
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 17:41 -0700 |
| Message-ID | <D13F3B5E.4951F%usenet@gallopinginsanity.com> |
| In reply to | #286864 |
On 3/30/15, 5:06 PM, in article bhvh3e9.a3f0@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > owl <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: > >>>>>> In your deranged minds it is a self-nuke for me to correct your >>>>>> misspelling of my name when you are using that misspelled name to address >>>>>> me in conversation, as determined circumstantially by the fact that it >>>>>> was used in a sentence where one would normally expect to find himself >>>>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>>>>> >>>>>> Somehow in your (French-influenced?) mush-heads, not continuing >>>>>> on as if the misspelling were without consequence, i.e. in the way >>>>>> that a case-insensitive file system would react, is evidence of my >>>>>> own case-insensitivity, and therefore worthy of a self-nuke award. >>>> >>>>> Yes, lamer. Exactly. >>>> >>>>> A case-sensitive filesystem or programming language or gibbon wouldn't >>>>> have recognized Owl as your name. You did. Normally not worth noting, >>>>> except this time you did it while in the middle of arguing FOR >>>>> case-sensitivity. >>>> >>>>> epic self-nuke! >>>> >>>> So if he had addressed me as "Bob" in a direct reply to my post, >>>> and I had corrected him that "Bob" is not my name, that would >>>> also have been a self-nuke? > >>> How about your self-nuke of referring to the program Firefox as "firefox", >>> and then your effort to save yourself by noting he executable file is called >>> "firefox" and not "Firefox", even though the program is. > >> The name of the file is "firefox." You know, a file, like might sit >> on the file system NTFS, the subject of this thread. Try to keep up. > >>> It is largely of the inherent challenges of using a case sensitive file >>> system that they use all lower case letters in program names in Linux (or at >>> least generally recommend people to). On OS X which does not have that >>> challenge the mozilla team calls the program bundle itself "Firefox". > >> That's irrelevant, but out of curiosity what is the executable called? > > Nevermind. Apparently it's "firefox" :) Which I already told you. :) > root@thinkpad:/tmp/macfire/Firefox.app/Contents/MacOS# ls > crashreporter.app libmozglue.dylib libsoftokn3.dylib > firefox libnss3.dylib plugin-container.app > firefox-bin libnssckbi.dylib updater.app > libfreebl3.dylib libnssdbm3.dylib XUL > libmozalloc.dylib libplugin_child_interpose.dylib > root@thinkpad:/tmp/macfire/Firefox.app/Contents/MacOS# Oh no! "Contents"... "MacOS"... how can we deal with this?!?!?! The horror! LOL! -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 17:15 -0700 |
| Message-ID | <D13F3528.49512%usenet@gallopinginsanity.com> |
| In reply to | #286856 |
On 3/30/15, 4:54 PM, in article bvhe03fa.p3@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >>>>> In your deranged minds it is a self-nuke for me to correct your >>>>> misspelling of my name when you are using that misspelled name to address >>>>> me in conversation, as determined circumstantially by the fact that it >>>>> was used in a sentence where one would normally expect to find himself >>>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>>>> >>>>> Somehow in your (French-influenced?) mush-heads, not continuing >>>>> on as if the misspelling were without consequence, i.e. in the way >>>>> that a case-insensitive file system would react, is evidence of my >>>>> own case-insensitivity, and therefore worthy of a self-nuke award. >>> >>>> Yes, lamer. Exactly. >>> >>>> A case-sensitive filesystem or programming language or gibbon wouldn't >>>> have recognized Owl as your name. You did. Normally not worth noting, >>>> except this time you did it while in the middle of arguing FOR >>>> case-sensitivity. >>> >>>> epic self-nuke! >>> >>> So if he had addressed me as "Bob" in a direct reply to my post, >>> and I had corrected him that "Bob" is not my name, that would >>> also have been a self-nuke? > >> How about your self-nuke of referring to the program Firefox as "firefox", >> and then your effort to save yourself by noting he executable file is called >> "firefox" and not "Firefox", even though the program is. > > The name of the file is "firefox." You know, a file, like might sit > on the file system NTFS, the subject of this thread. Try to keep up. You spoke of the program. The program is called Firefox. You goofed and swapped the two. And the primary reason the Firefox file is called firefox is because of the programming convention to use lower case names on files to avoid the challenges of dealing with a case sensitive system. The name on OS X for the Firefox bundle is, as one would expect, Firefox. No need to have to change the case just to fit the standards of a less friendly system. >> It is largely of the inherent challenges of using a case sensitive file >> system that they use all lower case letters in program names in Linux (or at >> least generally recommend people to). On OS X which does not have that >> challenge the mozilla team calls the program bundle itself "Firefox". > > That's irrelevant, but out of curiosity what is the executable called? The process name listed in the Activity Monitor is "Firefox", but if you open the "Contents" folder in the bundle "Firefox.app" you can get to the executable file... the full path on most systems is: /Applications/Firefox.app/Contents/MacOS/firefox OH NO! Look at the mix of cases. SOOOOO confusing! LOL! On Linux they tend not to do that because of the higher risk of confusion. -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-03-31 01:07 +0000 |
| Message-ID | <bbvh03.aw03@rooftop.invalid> |
| In reply to | #286872 |
Snit <usenet@gallopinginsanity.com> wrote: > On 3/30/15, 4:54 PM, in article bvhe03fa.p3@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>>>>> In your deranged minds it is a self-nuke for me to correct your >>>>>> misspelling of my name when you are using that misspelled name to address >>>>>> me in conversation, as determined circumstantially by the fact that it >>>>>> was used in a sentence where one would normally expect to find himself >>>>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>>>>> >>>>>> Somehow in your (French-influenced?) mush-heads, not continuing >>>>>> on as if the misspelling were without consequence, i.e. in the way >>>>>> that a case-insensitive file system would react, is evidence of my >>>>>> own case-insensitivity, and therefore worthy of a self-nuke award. >>>> >>>>> Yes, lamer. Exactly. >>>> >>>>> A case-sensitive filesystem or programming language or gibbon wouldn't >>>>> have recognized Owl as your name. You did. Normally not worth noting, >>>>> except this time you did it while in the middle of arguing FOR >>>>> case-sensitivity. >>>> >>>>> epic self-nuke! >>>> >>>> So if he had addressed me as "Bob" in a direct reply to my post, >>>> and I had corrected him that "Bob" is not my name, that would >>>> also have been a self-nuke? >> >>> How about your self-nuke of referring to the program Firefox as "firefox", >>> and then your effort to save yourself by noting he executable file is called >>> "firefox" and not "Firefox", even though the program is. >> >> The name of the file is "firefox." You know, a file, like might sit >> on the file system NTFS, the subject of this thread. Try to keep up. > You spoke of the program. The program is called Firefox. The name of the program is "firefox." The executable file *is* the program. What's written on the website, or splash screen, or an application bundle is irrelevant. When it's run, argv[0] is "firefox." That's its name. Get over it. > You goofed and > swapped the two. And the primary reason the Firefox file is called firefox > is because of the programming convention to use lower case names on files to > avoid the challenges of dealing with a case sensitive system. > The name on OS X for the Firefox bundle is, as one would expect, Firefox. No > need to have to change the case just to fit the standards of a less friendly > system. There is no requirement that the binary be called "firefox." They could call it "Firefox" if they wanted.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 18:21 -0700 |
| Message-ID | <D13F44A8.49537%usenet@gallopinginsanity.com> |
| In reply to | #286895 |
On 3/30/15, 6:07 PM, in article bbvh03.aw03@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: ... >>> The name of the file is "firefox." You know, a file, like might sit >>> on the file system NTFS, the subject of this thread. Try to keep up. > >> You spoke of the program. The program is called Firefox. > > The name of the program is "firefox." Nope. The name of the executable file is firefox. The program is Firefox. Really. Launch it. Look at the splash screen. Look at the "about" section. Look at all the branding. The program is called "Firefox". You goofed again. > The executable file *is* the program. > What's written on the website, or splash screen, or an application bundle > is irrelevant. When it's run, argv[0] is "firefox." That's its name. > Get over it. LOL! So mozilla got the name of their own program wrong. Love how you screw yourself over with your arguments so quickly! ... -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 12:24 -0700 |
| Message-ID | <D13EF116.494C6%usenet@gallopinginsanity.com> |
| In reply to | #286757 |
On 3/30/15, 10:06 AM, in article shfu30.3e@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: >>> In your deranged minds it is a self-nuke for me to correct your >>> misspelling of my name when you are using that misspelled name to address >>> me in conversation, as determined circumstantially by the fact that it >>> was used in a sentence where one would normally expect to find himself >>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>> >>> Somehow in your (French-influenced?) mush-heads, not continuing >>> on as if the misspelling were without consequence, i.e. in the way >>> that a case-insensitive file system would react, is evidence of my >>> own case-insensitivity, and therefore worthy of a self-nuke award. > >> Yes, lamer. Exactly. > >> A case-sensitive filesystem or programming language or gibbon wouldn't >> have recognized Owl as your name. You did. Normally not worth noting, >> except this time you did it while in the middle of arguing FOR >> case-sensitivity. > >> epic self-nuke! > > So if he had addressed me as "Bob" in a direct reply to my post, > and I had corrected him that "Bob" is not my name, that would > also have been a self-nuke? Here was an even better example of you completely ripping apart your own claims... along with my replies. It was quite funny: -------------------------------------------------------- On 3/29/15, 6:24 AM, in article bbvh3e9.a3e3@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: ... > ANyway, Not a word. How can anyone understand that? LOL! > every time I shut down firefox What the hell is firefox? LOL! Of course I and everyone else knows what it is. Just another fine example of you self-nuking. > with the "X marks the spot" button, after about a minute i'll get > this nag about firefox More about this "firefox" thing. LOL! > has "crashed" for some reason. No, you DUMBASSES Oh no. All caps. How can anyone read that? > it did not crashed - i i? LOL! > shut it down. DAMN LINUX GET YOUR SHIT TOGETHER! > :) Owl... you are really good at making a fool of yourself. But, yes, Firefox is garbage these days. -------------------------------------------------------- You repeatedly mixed up cases... "i" for "I" at least twice, "firefox" for "Firefox" which you then had to run to the executable name to try to defend... not showing any sign of getting that the program name and the executable name use different cases which shoots down your own claims. It really was funny! -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2015-03-30 20:46 -0400 |
| Message-ID | <mfcqo6$5iv$3@dont-email.me> |
| In reply to | #286757 |
On 3/30/2015 1:06 PM, owl wrote: > DFS <nospam@dfs.com> wrote: >> On 3/29/2015 10:16 PM, owl wrote: >>> Snit <usenet@gallopinginsanity.com> wrote: >>>> On 3/29/15, 6:22 PM, in article mfa8fq$7c6$3@dont-email.me, "DFS" >>>> <nospam@dfs.com> wrote: >>> >>>>> On 3/29/2015 12:18 PM, Snit wrote: >>>>>> On 3/29/15, 8:06 AM, in article mf94c6$s6t$1@dont-email.me, "DFS" >>>>>> <nospam@dfs.com> wrote: >>>>>> >>>>>>>>> pwnage earned by changing the case of one letter? Epic! >>>>>>>>> >>>>>>>>> owl is a tricky bastard and it's hard to get one by him. >>>>>>>>> >>>>>>>>> Congrats! >>>>>>>> >>>>>>>> Thanks. Wish I could say it was fully on purpose. :) >>>>>>> >>>>>>> >>>>>>> The plot thickens... you spelled it Owl by accident? >>>>>>> >>>>>>> That would change it from Snit pwnage to owl self-nuke, and your trophy >>>>>>> must be returned. >>>>>> >>>>>> Fair enough. I humbly return the trophy... and grant Owl the mushroom cloud >>>>>> reward. :) >>>>> >>>>> It's good you came clean - 5 months later - but an 'honest and >>>>> honorable' man would've never let my assumption stand in the first >>>>> place. I always figured you intentionally wrote 'Owl' to try and trick >>>>> him, since you were in the middle of a case-sensitivity debate. >>>>> >>>>> Instead of admitting it right then, you took credit for it several times >>>>> when I brought it up as pwnage, and said "That was fun". >>>>> >>>>> Why did you finally admit it wasn't intentional? >>> >>>> It was fun to see him self-nuke. Never implied it was intentional. >>> >>> In your deranged minds it is a self-nuke for me to correct your >>> misspelling of my name when you are using that misspelled name to address >>> me in conversation, as determined circumstantially by the fact that it >>> was used in a sentence where one would normally expect to find himself >>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>> >>> Somehow in your (French-influenced?) mush-heads, not continuing >>> on as if the misspelling were without consequence, i.e. in the way >>> that a case-insensitive file system would react, is evidence of my >>> own case-insensitivity, and therefore worthy of a self-nuke award. > >> Yes, lamer. Exactly. > >> A case-sensitive filesystem or programming language or gibbon wouldn't >> have recognized Owl as your name. You did. Normally not worth noting, >> except this time you did it while in the middle of arguing FOR >> case-sensitivity. > >> epic self-nuke! > > So if he had addressed me as "Bob" in a direct reply to my post, > and I had corrected him that "Bob" is not my name, that would > also have been a self-nuke? wtf do I have to explain your self-nuke 20000x for? This is the last time: You didn't say "'Owl' is not my name." You said "There's no "O" in my name." You recognized 'Owl' as your name (even with the capital O), just like a case-insensitive filesystem would. But earlier that day you were screeching "The computer should accommodate my need for a case-sensitive filesystem." s to the e to the l to the f to the - to the n to the u to the k to the e!
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-03-31 01:52 +0000 |
| Message-ID | <bvh9.a40e2@rooftop.invalid> |
| In reply to | #286884 |
DFS <nospam@dfs.com> wrote: > On 3/30/2015 1:06 PM, owl wrote: >> DFS <nospam@dfs.com> wrote: >>> On 3/29/2015 10:16 PM, owl wrote: >>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>> On 3/29/15, 6:22 PM, in article mfa8fq$7c6$3@dont-email.me, "DFS" >>>>> <nospam@dfs.com> wrote: >>>> >>>>>> On 3/29/2015 12:18 PM, Snit wrote: >>>>>>> On 3/29/15, 8:06 AM, in article mf94c6$s6t$1@dont-email.me, "DFS" >>>>>>> <nospam@dfs.com> wrote: >>>>>>> >>>>>>>>>> pwnage earned by changing the case of one letter? Epic! >>>>>>>>>> >>>>>>>>>> owl is a tricky bastard and it's hard to get one by him. >>>>>>>>>> >>>>>>>>>> Congrats! >>>>>>>>> >>>>>>>>> Thanks. Wish I could say it was fully on purpose. :) >>>>>>>> >>>>>>>> >>>>>>>> The plot thickens... you spelled it Owl by accident? >>>>>>>> >>>>>>>> That would change it from Snit pwnage to owl self-nuke, and your trophy >>>>>>>> must be returned. >>>>>>> >>>>>>> Fair enough. I humbly return the trophy... and grant Owl the mushroom cloud >>>>>>> reward. :) >>>>>> >>>>>> It's good you came clean - 5 months later - but an 'honest and >>>>>> honorable' man would've never let my assumption stand in the first >>>>>> place. I always figured you intentionally wrote 'Owl' to try and trick >>>>>> him, since you were in the middle of a case-sensitivity debate. >>>>>> >>>>>> Instead of admitting it right then, you took credit for it several times >>>>>> when I brought it up as pwnage, and said "That was fun". >>>>>> >>>>>> Why did you finally admit it wasn't intentional? >>>> >>>>> It was fun to see him self-nuke. Never implied it was intentional. >>>> >>>> In your deranged minds it is a self-nuke for me to correct your >>>> misspelling of my name when you are using that misspelled name to address >>>> me in conversation, as determined circumstantially by the fact that it >>>> was used in a sentence where one would normally expect to find himself >>>> being addressed. "Hey, jOe, where you going with that gun in your hand?" >>>> >>>> Somehow in your (French-influenced?) mush-heads, not continuing >>>> on as if the misspelling were without consequence, i.e. in the way >>>> that a case-insensitive file system would react, is evidence of my >>>> own case-insensitivity, and therefore worthy of a self-nuke award. >> >>> Yes, lamer. Exactly. >> >>> A case-sensitive filesystem or programming language or gibbon wouldn't >>> have recognized Owl as your name. You did. Normally not worth noting, >>> except this time you did it while in the middle of arguing FOR >>> case-sensitivity. >> >>> epic self-nuke! >> >> So if he had addressed me as "Bob" in a direct reply to my post, >> and I had corrected him that "Bob" is not my name, that would >> also have been a self-nuke? > wtf do I have to explain your self-nuke 20000x for? > This is the last time: > You didn't say "'Owl' is not my name." > You said "There's no "O" in my name." If he had addressed me as "Bob," I would have said, "There's no 'B' in my name. And you also left out the 'w' and the 'l'." > You recognized 'Owl' as your name (even with the capital O), just like a > case-insensitive filesystem would. But earlier that day you were > screeching "The computer should accommodate my need for a case-sensitive > filesystem." Nope. I generated an error message. Just like a case-sensitive filesystem would: owl@thinkpad:~$ ls owl owl owl@thinkpad:~$ ls Owl ls: cannot access Owl: No such file or directory owl@thinkpad:~$ > s to the e to the l to the f to the - to the n to the u to the k to the e! n to the o to the p to the e to the . to the to the l to the o to the l!
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-03-30 19:10 -0700 |
| Message-ID | <D13F5021.4953D%usenet@gallopinginsanity.com> |
| In reply to | #286884 |
On 3/30/15, 5:46 PM, in article mfcqo6$5iv$3@dont-email.me, "DFS" <nospam@dfs.com> wrote: >> So if he had addressed me as "Bob" in a direct reply to my post, >> and I had corrected him that "Bob" is not my name, that would >> also have been a self-nuke? > > > wtf do I have to explain your self-nuke 20000x for? > > This is the last time: > > You didn't say "'Owl' is not my name." > > You said "There's no "O" in my name." > > You recognized 'Owl' as your name (even with the capital O), just like a > case-insensitive filesystem would. But earlier that day you were > screeching "The computer should accommodate my need for a case-sensitive > filesystem." > > s to the e to the l to the f to the - to the n to the u to the k to the e! His Firefox screwup was even more amusing I think. :) -- * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mavericks / Pages 5.1: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2015-03-30 11:35 -0700 |
| Message-ID | <fa167a7e-3c05-4b48-aec3-bc0332c29beb@googlegroups.com> |
| In reply to | #286716 |
On Monday, March 30, 2015 at 7:49:30 AM UTC-6, DFS wrote: > On 3/29/2015 10:16 PM, owl wrote: > > Snit <usenet@gallopinginsanity.com> wrote: > >> On 3/29/15, 6:22 PM, in article mfa8fq$7c6$3@dont-email.me, "DFS" > >> <nospam@dfs.com> wrote: > > > >>> On 3/29/2015 12:18 PM, Snit wrote: > >>>> On 3/29/15, 8:06 AM, in article mf94c6$s6t$1@dont-email.me, "DFS" > >>>> <nospam@dfs.com> wrote: > >>>> > >>>>>>> pwnage earned by changing the case of one letter? Epic! > >>>>>>> > >>>>>>> owl is a tricky bastard and it's hard to get one by him. > >>>>>>> > >>>>>>> Congrats! > >>>>>> > >>>>>> Thanks. Wish I could say it was fully on purpose. :) > >>>>> > >>>>> > >>>>> The plot thickens... you spelled it Owl by accident? > >>>>> > >>>>> That would change it from Snit pwnage to owl self-nuke, and your trophy > >>>>> must be returned. > >>>> > >>>> Fair enough. I humbly return the trophy... and grant Owl the mushroom cloud > >>>> reward. :) > >>> > >>> It's good you came clean - 5 months later - but an 'honest and > >>> honorable' man would've never let my assumption stand in the first > >>> place. I always figured you intentionally wrote 'Owl' to try and trick > >>> him, since you were in the middle of a case-sensitivity debate. > >>> > >>> Instead of admitting it right then, you took credit for it several times > >>> when I brought it up as pwnage, and said "That was fun". > >>> > >>> Why did you finally admit it wasn't intentional? > > > >> It was fun to see him self-nuke. Never implied it was intentional. > > > > In your deranged minds it is a self-nuke for me to correct your > > misspelling of my name when you are using that misspelled name to address > > me in conversation, as determined circumstantially by the fact that it > > was used in a sentence where one would normally expect to find himself > > being addressed. "Hey, jOe, where you going with that gun in your hand?" > > > > Somehow in your (French-influenced?) mush-heads, not continuing > > on as if the misspelling were without consequence, i.e. in the way > > that a case-insensitive file system would react, is evidence of my > > own case-insensitivity, and therefore worthy of a self-nuke award. > > Yes, lamer. Exactly. > > A case-sensitive filesystem or programming language or gibbon wouldn't > have recognized Owl as your name. You did. Normally not worth noting, > except this time you did it while in the middle of arguing FOR > case-sensitivity. > > epic self-nuke! Nah, he merely recognized Snit was "referencing" him in that post. Don't forget what Snit asked: "What made you think I was referencing you?" And the answer is simple... https://groups.google.com/forum/#!original/comp.os.linux.advocacy/uPMC4QazReY/2TkK7iwGDcoJ > > Since exactly the opposite is true, and the misspelling was detected, > > not overlooked, I can only say that you both have my pity for having > > such broken reasoning skills. :) > > Learn some humility, boy. Accept your self-wrought defeat. LOL! Sorry, he owns you two on this one.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2015-03-30 23:09 -0400 |
| Message-ID | <mfd34r$o97$2@dont-email.me> |
| In reply to | #286785 |
On 3/30/2015 2:35 PM, Steve Carroll wrote: > On Monday, March 30, 2015 at 7:49:30 AM UTC-6, DFS wrote: >> On 3/29/2015 10:16 PM, owl wrote: >>> Snit <usenet@gallopinginsanity.com> wrote: >>>> On 3/29/15, 6:22 PM, in article mfa8fq$7c6$3@dont-email.me, >>>> "DFS" <nospam@dfs.com> wrote: >>> >>>>> On 3/29/2015 12:18 PM, Snit wrote: >>>>>> On 3/29/15, 8:06 AM, in article mf94c6$s6t$1@dont-email.me, >>>>>> "DFS" <nospam@dfs.com> wrote: >>>>>> >>>>>>>>> pwnage earned by changing the case of one letter? >>>>>>>>> Epic! >>>>>>>>> >>>>>>>>> owl is a tricky bastard and it's hard to get one by >>>>>>>>> him. >>>>>>>>> >>>>>>>>> Congrats! >>>>>>>> >>>>>>>> Thanks. Wish I could say it was fully on purpose. :) >>>>>>> >>>>>>> >>>>>>> The plot thickens... you spelled it Owl by accident? >>>>>>> >>>>>>> That would change it from Snit pwnage to owl self-nuke, >>>>>>> and your trophy must be returned. >>>>>> >>>>>> Fair enough. I humbly return the trophy... and grant Owl >>>>>> the mushroom cloud reward. :) >>>>> >>>>> It's good you came clean - 5 months later - but an 'honest >>>>> and honorable' man would've never let my assumption stand in >>>>> the first place. I always figured you intentionally wrote >>>>> 'Owl' to try and trick him, since you were in the middle of a >>>>> case-sensitivity debate. >>>>> >>>>> Instead of admitting it right then, you took credit for it >>>>> several times when I brought it up as pwnage, and said "That >>>>> was fun". >>>>> >>>>> Why did you finally admit it wasn't intentional? >>> >>>> It was fun to see him self-nuke. Never implied it was >>>> intentional. >>> >>> In your deranged minds it is a self-nuke for me to correct your >>> misspelling of my name when you are using that misspelled name to >>> address me in conversation, as determined circumstantially by the >>> fact that it was used in a sentence where one would normally >>> expect to find himself being addressed. "Hey, jOe, where you >>> going with that gun in your hand?" >>> >>> Somehow in your (French-influenced?) mush-heads, not continuing >>> on as if the misspelling were without consequence, i.e. in the >>> way that a case-insensitive file system would react, is evidence >>> of my own case-insensitivity, and therefore worthy of a self-nuke >>> award. >> >> Yes, lamer. Exactly. >> >> A case-sensitive filesystem or programming language or gibbon >> wouldn't have recognized Owl as your name. You did. Normally not >> worth noting, except this time you did it while in the middle of >> arguing FOR case-sensitivity. >> >> epic self-nuke! > > Nah, he merely recognized Snit was "referencing" him in that post. That's a different issue, and in fact it's irrelevant. Whether owl was replying to a post directed to him or to someone else, he recognized his name even though it was spelled Owl (a case change in one letter). owl: "There's no 'O' in my name." A case-sensitive filesystem wouldn't recognize it at all, but a case-insensitive filesystem would. Clear and huge self-nuke, because owl was ranting (not to mention lying) about needing a case-sensitive filesystem. Too bad it was inadvertent on Snit's part; epic pwnage is better than epic self-nuke. > Don't forget what Snit asked: > "What made you think I was referencing you?" That came later. > And the answer is simple... > > https://groups.google.com/forum/#!original/comp.os.linux.advocacy/uPMC4QazReY/2TkK7iwGDcoJ > > > >>> Since exactly the opposite is true, and the misspelling was >>> detected, not overlooked, I can only say that you both have my >>> pity for having such broken reasoning skills. :) >> >> Learn some humility, boy. Accept your self-wrought defeat. > > LOL! Sorry, he owns you two on this one. Wrong. And you're self-nuking by siding with the nukee.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2015-03-30 22:01 -0700 |
| Message-ID | <bdf082e5-eeb4-48fe-a938-0447e06f9964@googlegroups.com> |
| In reply to | #286908 |
On Monday, March 30, 2015 at 9:10:10 PM UTC-6, DFS wrote: > > LOL! Sorry, he owns you two on this one. > > Wrong. And you're self-nuking by siding with the nukee. https://www.youtube.com/watch?v=HYMla7qlBsg
[toc] | [prev] | [next] | [standalone]
| From | taka0038@gmail.com |
|---|---|
| Date | 2015-03-31 18:52 -0700 |
| Subject | NTFS is not the best filesystem |
| Message-ID | <8bd64386-a013-4d23-80e5-c3041b2afc0b@googlegroups.com> |
| In reply to | #286920 |
The winner is ... http://en.wikipedia.org/wiki/ZFS Cannot find any "missing" feature in it. Taka
[toc] | [prev] | [next] | [standalone]
| From | Slimer <slvrslmr@lv.c> |
|---|---|
| Date | 2015-03-31 22:51 -0400 |
| Subject | Re: NTFS is not the best filesystem |
| Message-ID | <mffmd0$tos$1@dont-email.me> |
| In reply to | #287104 |
On 2015-03-31 9:52 PM, taka0038@gmail.com wrote: > The winner is ... http://en.wikipedia.org/wiki/ZFS > > Cannot find any "missing" feature in it. Taka And you're likely right. Not one Windows user will ever be dumb enough to tell you that it's the _best_ filesystem. It is, nonetheless, a lot more important and useful than anything attached to Linsux. -- Slimer OpenMedia, GreenPeace Supporter & SPCA Paw Partner Encrypt.
[toc] | [prev] | [next] | [standalone]
Page 2 of 3 — ← Prev page 1 [2] 3 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web