From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] The origin of /home
Date: Fri, 28 Sep 2018 15:07:34 -0600 [thread overview]
Message-ID: <68a3b1e2-41d0-e807-2eb6-eaafdcd47e95@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAJfiPzyUto=7HBYsPh9RGe8xDxnDRszQmYnMpo=7quGQT0B-xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On 09/28/2018 02:00 PM, Nemo wrote:
> From
> https://docs.oracle.com/cd/E26505_01/html/E29492/userconcept-36940.html#userconcept-6
> :
>
> A home directory can be located either on the user's local system or on
> a remote file server. In either case, by convention the home directory
> should be created as /export/home/username. For a large site, you should
> store home directories on a server. Use a separate file system for each
> /export/homen directory to facilitate backing up and restoring home
> directories. For example, /export/home1, /export/home2.
>
> Regardless of where their home directory is located, users usually access
> their home directories through a mount point named /home/username. When
> AutoFS is used to mount home directories, you are not permitted to create
> any directories under the /home mount point on any system. The system
> recognizes the special status of /home when AutoFS is active.
Yep, that jives with what I thought.
"… by convention the home directory should be created as
/export/home/username … users usually access their home directories
through a mount point named /home/username …"
Yep, that jives with my experience and my understanding.
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3982 bytes --]
next prev parent reply other threads:[~2018-09-28 21:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 12:08 Cág
2018-09-27 12:30 ` Alec Muffett
2018-09-27 12:58 ` Donald ODona
2018-09-27 13:54 ` John P. Linderman
2018-09-27 14:09 ` Ronald Natalie
2018-09-27 14:18 ` Jon Forrest
2018-09-27 14:28 ` Arrigo Triulzi
2018-09-27 15:36 ` Jon Forrest
2018-09-27 15:54 ` Arrigo Triulzi
2018-09-27 18:49 ` Jon Forrest
2018-09-28 0:50 ` Theodore Y. Ts'o
2018-10-01 1:52 ` Lyndon Nerenberg
2018-10-10 2:38 ` Dave Horsfall
2018-10-10 3:07 ` Grant Taylor via TUHS
2018-09-27 17:33 ` Donald ODona
2018-09-27 14:47 ` Dan Cross
2018-09-27 17:20 ` arnold
2018-09-27 20:42 ` Cág
2018-09-27 21:07 ` Dan Cross
2018-09-27 22:04 ` Clem Cole
2018-09-27 22:18 ` Henry Bent
2018-09-28 8:33 ` Tony Finch
2018-09-28 18:23 ` Jeremy C. Reed
2018-09-28 16:02 ` Nemo
2018-09-28 16:15 ` Grant Taylor via TUHS
2018-09-28 17:28 ` Arthur Krewat
2018-09-28 19:38 ` Grant Taylor via TUHS
2018-09-28 19:47 ` Grant Taylor via TUHS
2018-09-28 20:30 ` Arthur Krewat
2018-09-28 20:00 ` Nemo
2018-09-28 21:07 ` Grant Taylor via TUHS [this message]
2018-09-27 14:31 Noel Chiappa
2018-09-27 15:33 Noel Chiappa
2018-09-27 20:15 ` Dan Cross
2018-09-27 23:14 Noel Chiappa
2018-09-28 5:27 ` Lars Brinkhoff
2018-09-28 2:39 Doug McIlroy
2018-10-10 14:43 Norman Wilson
2018-10-10 16:26 ` arnold
2018-10-11 19:10 ` Lyndon Nerenberg
2018-10-10 17:08 ` Grant Taylor via TUHS
2018-10-11 0:22 ` Steve Nickolas
2018-10-11 2:33 ` David Arnold
2018-10-10 15:26 Noel Chiappa
2018-10-10 15:45 ` Clem Cole
2018-10-10 15:48 ` David
2018-10-13 6:58 ` Michael Kjörling
2018-10-12 0:15 ` Dave Horsfall
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=68a3b1e2-41d0-e807-2eb6-eaafdcd47e95@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).