From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 19:19:26 +0000 [thread overview]
Message-ID: <20190530191926.6n4uvebwill77qzp@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <975B93B6-AD7C-41B5-A14D-2DE4FEFAD3A6@kdbarto.org>
On 30 May 2019 06:49 -0700, from david@kdbarto.org (David):
> 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?
Don't forget probably every ISP under the sun.
My first Internet account in 1995 (or possibly 1996) came with *nix
shell access (please don't ask me what variant; I used it mostly to
run pine, and occasionally pico, and it was dial-up which was charged
per minute by the phone company) and a 4 MB quota, which you could pay
to have increased. That quota covered everything in your $HOME; as I
recall, including e-mail, and definitely including ~/public_html.
These days, it seems that with the exception of _really_ cheap
accounts, web host quotas are big enough that they for all intents and
purposes might as well not be there, even with today's bloated
content. Back then, even 4 MB for everything felt on the tight side,
and you certainly had to think about what you put there.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“The most dangerous thought that you can have as a creative person
is to think you know what you’re doing.” (Bret Victor)
next prev parent reply other threads:[~2019-05-30 19:26 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
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 [this message]
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=20190530191926.6n4uvebwill77qzp@h-174-65.A328.priv.bahnhof.se \
--to=michael@kjorling.se \
--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).