From: "John P. Linderman" <jpl.jpl@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 10:48:50 -0400 [thread overview]
Message-ID: <CAC0cEp8hNF7A1yc7TrL56TRWyvbki+9eqgMWCjUdHZVdXsF1GA@mail.gmail.com> (raw)
In-Reply-To: <20190530143414.GF2751@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
We used them in an AT&T Labs research environment. The intent was less to
prevent users from selfishly grabbing (then semi-precious) disk space but
to prevent accidents from adversely affecting the user community at large.
If you *knew* you were going to need honking amounts of disk, the sysadmins
would raise the quota (probably on a partition dedicated to such
activities).
On Thu, May 30, 2019 at 10:40 AM Theodore Ts'o <tytso@mit.edu> wrote:
> On Thu, May 30, 2019 at 06:49:05AM -0700, David wrote:
> > I think it was BSD 4.1 that added quotas to the disk system, and I
> > was just wondering if anyone ever used them, in academia or
> > industry. As a user and an admin I never used this and, while I
> > thought it was interesting, just figured that the users would sort
> > it out amongst themselves. Which they mostly did.
> >
> > So, anyone ever use this feature?
>
> Back when MIT Project Athena was using Vax/750's as time sharing
> machines (before the advent of the MicroVax II workstations and AFS),
> students were assigned to a Vax 750, and were given a quota of I think
> a megabyte, at least initially. It could be increased by applying to
> the user accounts office. Given that there were roughly 4,000
> undergraduates sharing 5 or 6 Vax/750's, it was somewhat understandable...
>
> - Ted
>
[-- Attachment #2: Type: text/html, Size: 1808 bytes --]
next prev parent reply other threads:[~2019-05-30 14:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 13:49 David
2019-05-30 14:23 ` Diomidis Spinellis
2019-05-30 14:26 ` Dan Cross
2019-05-30 14:27 ` Rico Pajarola
2019-05-31 7:16 ` George Ross
2019-05-30 14:29 ` Robert Brockway
2019-05-30 14:34 ` Theodore Ts'o
2019-05-30 14:48 ` John P. Linderman [this message]
2019-05-30 14:57 ` Jim Geist
2019-05-30 14:55 ` Andreas Kusalananda Kähäri
2019-05-30 15:00 ` KatolaZ
2019-05-30 17:28 ` Grant Taylor via TUHS
2019-05-30 19:19 ` Michael Kjörling
2019-05-30 20:42 ` Warner Losh
2019-05-30 22:23 ` George Michaelson
2019-05-31 1:36 ` alan
2019-05-31 19:07 ` Pete Wright
2019-05-31 20:43 ` Grant Taylor via TUHS
2019-05-31 20:59 ` Pete Wright
2019-06-01 0:30 ` reed
2019-06-04 13:50 ` Tony Finch
2019-05-30 16:04 Noel Chiappa
2019-05-30 16:48 ` KatolaZ
2019-05-30 17:42 ` ron
2019-05-31 0:21 Nelson H. F. Beebe
2019-05-31 0:37 ` Larry McVoy
2019-05-31 0:42 ` Arthur Krewat
2019-05-31 15:05 ` Nelson H. F. Beebe
2019-05-31 16:06 ` Michael Kjörling
2019-05-31 16:15 ` Grant Taylor via TUHS
2019-05-31 16:38 ` Michael Kjörling
2019-05-31 15:55 ` Rico Pajarola
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=CAC0cEp8hNF7A1yc7TrL56TRWyvbki+9eqgMWCjUdHZVdXsF1GA@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=tuhs@tuhs.org \
--cc=tytso@mit.edu \
/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).