Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.alt.net!not-for-mail From: owl Newsgroups: comp.os.linux.advocacy Subject: Re: fucking firefox Date: Sun, 29 Mar 2015 20:29:46 +0000 (UTC) Organization: ok by me, so long as it doesn't get out of hand Lines: 90 Message-ID: References: NNTP-Posting-Host: boom.rooftop.invalid User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.6.38-16-generic (x86_64)) Xref: csiph.com comp.os.linux.advocacy:286640 Snit wrote: > On 3/29/15, 12:54 PM, in article gbh03fa.3p@rooftop.invalid, "owl" > wrote: >> Snit wrote: >>> On 3/29/15, 12:24 PM, in article gheu0.xxa03@rooftop.invalid, "owl" >>> wrote: >> >>>>>>> Owl... you are really good at making a fool of yourself. >>>>>> >>>>>>> But, yes, Firefox is garbage these days. >>>>>> >>>>>> You just can't help being an idiot, can you? >>>>>> owl@thinkpad:~$ which firefox >>>>>> /usr/bin/firefox >>>>>> owl@thinkpad:~$ which Firefox >>>>>> owl@thinkpad:~$ >>>>>> >>>>> >>>> >>>>> The URL says firefox. >>>>> The name of the program is Firefox. >>>>> On Linux the program file is called firefox >>>>> On Windows the program file is called firefox.exe >>>>> On OS X the program file is called Firefox.app >>>> >>>>> So damned confusing! How can anyone deal with this? >>>> >>>>> LOL! >>>> >>>> It's not confusing at all if you understand that spelling >>>> has consequences. >> >>> It is only a problem for computers which insist on case sensitivity, as YOU >>> provided a great example for. >> >> (see below) >> >>> For HUMANS it is not an issue at all (except when computers fail to account >>> for how humans think). >> >> Tell it to Apple, who are running www.apple.com on top of a case-sensitive >> file system. > As I said, I think Apple is wrong here. We already discussed this. Comes > down to you rehashing stuff instead of just admitting you screwed up again. > :) >> Tell it to Microsoft, whose NTFS file system is fully case- >> sensitive. > It is... under Linux. Not Windows. MS is smart enough to put in the added > work to make sure things are easier for users. No. NTFS is fully case-sensitive period. It is the way in which some Windows subsystems choose to interface with it that makes it appear to be merely case-preserving. As you can see in one of my other posts, installing the services for unix you can open a unix shell under Win 2008 server and have full case-sensitive behavior. This *is* running under Windows when it does that. It requires flipping a registry bit to enable default case-senistive behavior however. But this makes no change whatsoever to the NTFS volume, which is fully case sensitive from the start. > Linux screws things up for the primary users of NTFS systems by not > following the Windows standards, even as an easy to use option: Linux is following the NTFS standard. And since Linux is not Windows, it does not have to play by Windows rules when it interfaces with NTFS. > Put it on youtube. I don't visit hostile sites. > It is likely why Apple uses NTFS as read only. The case issues lead to > problems. But with add-ons OS X works much like Linux... it gets things > wrong for Windows users. It is Windows users that are not taking full advantage of the capabilies of NTFS. >>> You cannot help but self-nuke on this topic over and over. Love it! >> >> So we can add self-nuking to the long list of things you are clueless about. > LOL! Come on... can't you see the humor in your screw ups? Sure. But what does that have to do with this thread?