lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56F419F2.8030600@schaufler-ca.com>
Date:	Thu, 24 Mar 2016 09:46:42 -0700
From:	Casey Schaufler <casey@...aufler-ca.com>
To:	Hgntkwis@...mail.net, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Where did . come from

On 3/23/2016 9:29 PM, Hgntkwis@...mail.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!  
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ