The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: reed@reedmedia.net
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Fri, 31 May 2019 19:30:13 -0500 (CDT)	[thread overview]
Message-ID: <alpine.NEB.2.21.1905311913470.25930@t1.m.reedmedia.net> (raw)
In-Reply-To: <975B93B6-AD7C-41B5-A14D-2DE4FEFAD3A6@kdbarto.org>

(Sharing some from my book in regards to at Berkeley slowly being 
written ... some questions below too.)

% prior to March 19, 1976 \cite{unix-news-19760319}
In addition to teaching and writing Unix Pascal, Thompson
coded or advised on various other system modifications.
He put in disk space quotas to prevent runaways.\cite{kenthompson1}
% (inode.flags & 060000) == 020000
A special file named ``.q'' would track (in its inode) the
maximum number of blocks that may be used by files in the
directory and its descendents and a count of the number of used blocks.
A new ``quot'' system call was added to make directories with
quotas.
In addition, a modified link(2) allowed quotas to be exceeded 
temporarily
so a move/rename operation could work on a near full
quota.\cite{unix-news-19760319}

% NOTE: cptree source for system call use example

% I cannot find this quot program 

A new quot command was used to define the quotas.
% CITE:
Later, Kurt Shoens, a student in Thompson's
operating systems course\cite{arnold1}, wrote a tool called pq that 
would
search up from your current working directory to find the nearest quota 
file
and display what is used, the defined maximum quota, and its percentage 
used.
% CITE: pq manpage and source
Also a custom ls command identified if an entry was a quota file,
file command could identify quota files,
ex could warn if the ``Quota exceeded'',
and cptree and lntree could copy quota files, 

This quotas implementation was not integrated back into Unix.  So
back to ``threatening messages of the day and personal letters.''
Also a different quot tool was added a couple years later in the
Seventh Edition of Unix (and also shipped with later BSDs) to
display (but not restrict) the disk usage for each
user.\cite{ritchie-7th-edition-setting-up}
(A new quotas implementation was written and introduced to
Berkeley years later. This story is in \autoref{chapter:4BSD}.)

---------------

At first I thought that a side-effect of quotas was that users couldn't 
chown files to others, but wrong since already is documented that chown 
is for super-user only in V6. Any thoughts on that?

What is the unused pw_quota in v7 getpwent? Is that related at all to 
disk quotas.




  parent reply	other threads:[~2019-06-01  1:02 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
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 [this message]
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=alpine.NEB.2.21.1905311913470.25930@t1.m.reedmedia.net \
    --to=reed@reedmedia.net \
    --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).