From: Casey Schaufler <casey@schaufler-ca.com>
To: Hgntkwis@vfemail.net, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Where did . come from
Date: Thu, 24 Mar 2016 09:46:42 -0700 [thread overview]
Message-ID: <56F419F2.8030600@schaufler-ca.com> (raw)
In-Reply-To: <20160324002948.7fb87217@ulgy_thing>
On 3/23/2016 9:29 PM, Hgntkwis@vfemail.net wrote:
> Granted, you need something to signify that a file is a dir (remember,
> in linux everything is a file), and what the parent dir is.
> I'm assuming that the kernel folks decided the name, or at least have
> some idea about it.
> I'm not objecting, it's fine, I just want to know this history behind the
> decision to use . instead of say $ or %.
Minimum amount of ink used on a TTY33.
No, I'm not kidding. It dates back to the UNIX systems of the 1970's.
>
> Thanks, David
>
> -------------------------------------------------
>
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
> $24.95 ONETIME Lifetime accounts with Privacy Features!
> 15GB disk! No bandwidth quotas!
> Commercial and Bulk Mail Options!
>
prev parent reply other threads:[~2016-03-24 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 4:29 Where did . come from Hgntkwis
2016-03-24 16:46 ` Casey Schaufler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F419F2.8030600@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=Hgntkwis@vfemail.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.