From: Clem Cole <clemc@ccc.com>
To: Steve Simon <steve@quintile.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] /home
Date: Thu, 27 Sep 2018 18:09:09 -0400 [thread overview]
Message-ID: <CAC20D2OvBQO1+fbiFpBmj0nVBTKHu4z-BWqj+cXF2-EDezqSVg@mail.gmail.com> (raw)
In-Reply-To: <A1A27D12-7A36-4507-9CB4-C73F0B5AE84A@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
Right... was how quotas were done before FFS and 4.2 and very typical of a
university set up
ᐧ
On Thu, Sep 27, 2018 at 4:51 PM Steve Simon <steve@quintile.net> wrote:
>
> At college we had /h but that may be an interdata/edition7 thing. mine was
> /h/beng4/ssimon.
>
> each course/year was in a separate disk partition - if group filled their
> partition other groups could still work.
>
> -Steve
>
[-- Attachment #2: Type: text/html, Size: 1035 bytes --]
next prev parent reply other threads:[~2018-09-27 22:09 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 [this message]
2018-09-28 0:14 ` Greg 'groggy' Lehey
2018-09-28 0:19 ` Warner Losh
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=CAC20D2OvBQO1+fbiFpBmj0nVBTKHu4z-BWqj+cXF2-EDezqSVg@mail.gmail.com \
--to=clemc@ccc.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).