From: Warner Losh <imp@bsdimp.com>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: steve@quintile.net, TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] /home
Date: Thu, 27 Sep 2018 18:19:51 -0600 [thread overview]
Message-ID: <CANCZdfrUNH3RoAcA7_26ms=ymDv2H5ywiyxjWagRSqvR8N5i4w@mail.gmail.com> (raw)
In-Reply-To: <20180928001409.GH75165@eureka.lemis.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Thu, Sep 27, 2018 at 6:14 PM Greg 'groggy' Lehey <grog@lemis.com> wrote:
> On Thursday, 27 September 2018 at 21:50:58 +0100, Steve Simon wrote:
> >
> > At college we had /h but that may be an interdata/edition7
> > thing. mine was /h/beng4/ssimon.
>
> This sounds like a workaround for short pathname limits, particularly
> with System V. I had a file system mounted on /S for the same reason
> decades ago.
At Solboure, we had /h/admin /o/os /o/home /x/build /x/home /x/prod etc.
The reason for this was the SunOS automounter and bugs it had that required
each machine to have a different top level directory. Luckily we only had
like 4 servers... This was to prevent hanging /h mounts when the /x machine
would go away and someone would do an ls in that directory. That bug got
fixed in the 4.0 -> 4.1 transition, but we none-the-less kept the structure
because it was too painful to transition...
Warner
[-- Attachment #2: Type: text/html, Size: 1244 bytes --]
prev parent reply other threads:[~2018-09-28 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 20:50 Steve Simon
2018-09-27 22:09 ` Clem Cole
2018-09-28 0:14 ` Greg 'groggy' Lehey
2018-09-28 0:19 ` Warner Losh [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='CANCZdfrUNH3RoAcA7_26ms=ymDv2H5ywiyxjWagRSqvR8N5i4w@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=grog@lemis.com \
--cc=steve@quintile.net \
--cc=tuhs@minnie.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).