The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Abhinav Rajagopalan <abhinavrajagopalan@gmail.com>
To: Thomas Paulsen <thomas.paulsen@firemail.de>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] PDP-7 UNIX filesystem
Date: Mon, 21 Oct 2019 19:01:45 +0530	[thread overview]
Message-ID: <CANOZ5rhRWJzLPjR9O2Gu_txdCP67XX1N-HfQ_=FHACOTBXJTpw@mail.gmail.com> (raw)
In-Reply-To: <be9f73c626b3f12da38ab1e59abd96c9@firemail.de>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

Thanks, didn't mean it as a GNU thing at all. Sure, mkdir would've existed
back in research Unix too. My experience has only been limited to the Linux
envs, which is why I was led to attribute mkdir to the evolution in
mknod(), I only know that they all either descended down from SysV or BSD,
those who have used the real Unices would know better. Seeing as I haven't
had the privilege of using any except briefly on an emulator.

On Mon, Oct 21, 2019 at 5:30 PM Thomas Paulsen <thomas.paulsen@firemail.de>
wrote:

>
> > Also, I only now realized that only mknod existed, up until a long time,
> >
> > only later on with the GNU coreutils did mkdir as a command come into
> > existence. Running the PDP-11 v7 on SIMH showed that, gotten so
> accustomed
> >
> > to the Linux env that thinking backwards seemed suddenly arcane.
> >
> that's not true. mkdir isn't a GNU invention. Its much older.
>
> https://en.wikipedia.org/wiki/Mkdir#History
> http://man7.org/linux/man-pages/man2/mknod.2.html
>
>
>

-- 

Abhinav Rajagopalan

[-- Attachment #2: Type: text/html, Size: 2701 bytes --]

  reply	other threads:[~2019-10-21 13:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  6:22 Angelo Papenhoff
2019-10-21 10:43 ` Abhinav Rajagopalan
2019-10-21 11:38   ` Abhinav Rajagopalan
2019-10-21 12:00     ` Thomas Paulsen
2019-10-21 13:31       ` Abhinav Rajagopalan [this message]
2019-10-22 18:07   ` Peter Jeremy
2019-10-23  0:07     ` Mary Ann Horton
2019-10-23  2:02       ` Kurt H Maier
2019-10-23  2:19         ` Larry McVoy
2019-10-23  8:34       ` Thomas Paulsen
2019-10-24  0:06         ` Warner Losh
2019-10-24  2:23           ` Michael Parson
2019-10-25 21:08             ` Michael Kjörling
2019-10-25 21:34               ` Arthur Krewat
2019-10-25 21:50                 ` reed
2019-10-25 22:54                 ` Warner Losh
2019-10-24  2:29   ` Christopher Browne
2019-10-24  8:25     ` Thomas Paulsen
2019-10-21 16:54 ` Angelo Papenhoff
2019-10-23  5:48 ` Lars Brinkhoff
2019-10-21 11:58 Noel Chiappa
2019-10-21 15:44 ` Abhinav Rajagopalan
2019-10-22  2:09 ` Jaap Akkerhuis
2019-10-23  2:00   ` Christopher Browne

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='CANOZ5rhRWJzLPjR9O2Gu_txdCP67XX1N-HfQ_=FHACOTBXJTpw@mail.gmail.com' \
    --to=abhinavrajagopalan@gmail.com \
    --cc=thomas.paulsen@firemail.de \
    --cc=tuhs@tuhs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).