From: Lars Brinkhoff <lars@nocrew.org>
To: Angelo Papenhoff <aap@papnet.eu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] PDP-7 UNIX filesystem
Date: Wed, 23 Oct 2019 05:48:04 +0000 [thread overview]
Message-ID: <7wpnioc8rv.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20191021062242.GA91599@indra.papnet.eu> (Angelo Papenhoff's message of "Mon, 21 Oct 2019 08:22:42 +0200")
Does anyone have any input for Angelo? I think the questions he asks
are interesting. Please note he's asking about PDP-7 Unix, not the
unrelated "dd" command and how "." and ".." work in later Unix versions.
Angelo Papenhoff wrote:
> you cannot execute a program if you're in a directory you can't write into.
>
> I asked Warren about this when I first tried pdp7 unix and he
> explained it to me: the shell creates a link to the binary and executes
> it. If it can't write into the current directory, it fails to create the
> link and hence can't execute the program.
> How was this handled in practice? did users have write
> permissions on all directories? did you just stay in your directory all
> the time?
> . and ..
This part is apparently resolved.
next prev parent reply other threads:[~2019-10-23 5:48 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
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 [this message]
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=7wpnioc8rv.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=aap@papnet.eu \
--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).