Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [News] Linux Got the Directory/File Hierarchy Right

  • Subject: Re: [News] Linux Got the Directory/File Hierarchy Right
  • From: Handover Phist <jason@xxxxxxxxxxxxxxxxxxxxxx>
  • Date: Tue, 14 Nov 2006 21:26:04 GMT
  • Newsgroups: comp.os.linux.advocacy
  • Organization: Shaw Residential Internet
  • References: <1429256.DBdUBT73up@schestowitz.com> <gacpgn5gzhmg$.dlg@funkenbusch.com> <slrnelk4qj.5ii.jason@jason.websterscafe.com> <m7np24-hlm.ln1@sirius.tg00suus7038.net>
  • User-agent: slrn/0.9.8.1pl1 (Debian)
  • Xref: news.mcc.ac.uk comp.os.linux.advocacy:1181974
On 2006-11-14, The Ghost In The Machine <ewill@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> In comp.os.linux.advocacy, Handover Phist
><jason@xxxxxxxxxxxxxxxxxxxxxx>
>  wrote
> on Tue, 14 Nov 2006 19:06:04 GMT
><slrnelk4qj.5ii.jason@xxxxxxxxxxxxxxxxxxxxxx>:
>> On 2006-11-14, Erik Funkenbusch <erik@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>> On Mon, 13 Nov 2006 22:00:59 +0000, Roy Schestowitz wrote:
>>>
>>>> Why is the linux file hierarchy better?
>>>> 
>>>> ,----[ Quote ]
>>>>| There are many articles around the web about the differences between
>>>>| the windows file hierarchy and the linux one. One thing they don't say
>>>>| is which one is better and why. My aim in this article is to show why
>>>>| the linux file hierarchy is a better model.
>>>> `----
>>>> 
>>>> http://blogs.ittoolbox.com/linux/locutus/archives/why-is-the-linux-file-hierarchy-better-12916
>>>> http://tinyurl.com/ylm2ek
>>>
>>> Gah, what a complete load of nonsense.
>>>
>>> "If you try to install it anywhere else you will have problems. This is
>>> because all windows programs assume that windows is in drive C and will
>>> barf if it is not."
>>>
>>> Complete and utter bogus, I've almost never had my windows directory on
>>> drive c.  Not even Windows 95 required this (though you did have to have
>>> msdos.sys and io.sys on c:)
>>>
>>> One thing that pisses me off with the linux filesystem is that there's no
>>> way to assign a label to a path.  Sure, you can create a symlink to ito
>>> somwhere, like your home directory, but you can't assign a global label.
>>> Windows has mappable drive letters, AmigaOS had labels, etc...
>>
>> Eh?
>>
>> export $LABEL='$PATH'
>>
>
> Pedant Point: that should be
>
>     LABEL=$PATH; export LABEL
>
> in classical Bourne;
>
>     export LABEL=$PATH
>
> works in /bin/bash.
>
>     $LABEL=$PATH
>
> might be a form in Perl.

Since, in the pseudocode, the LABEL variable can be anything, I made it
variable :). If you need more than one LABEL, they'll be different, and
therefore $LABELS.

-- 
You!  What PLANET is this!
		-- McCoy, "The City on the Edge of Forever", stardate 3134.0

http://www.websterscafe.com

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index