From: <ron@ronnatalie.com>
To: "'KatolaZ'" <katolaz@freaknet.org>, <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 13:42:49 -0400 [thread overview]
Message-ID: <015701d5170f$19b44310$4d1cc930$@ronnatalie.com> (raw)
In-Reply-To: <20190530164821.qzbgduu27ktxmkpa@katolaz.homeunix.net>
Hopkins had a 11/45 system with several RK05's (2.4M). One was / and /usr,
one was /sys1 (one set of users) and the other /sys2 (the other users).
My initial quota for class was 8 blocks and that went up to 30 when I went
on staff there.
We also had two additional RK05 drives and I thought I was in fat city when
I invested $65 in my own cartridge for that.
Before that, I had spent a few bucks on DecTapes.
The system swapped on an RF11 disk (1024 blocks).
> -----Original Message-----
> From: TUHS <tuhs-bounces@minnie.tuhs.org> On Behalf Of KatolaZ
> Sent: Thursday, May 30, 2019 12:48 PM
> To: tuhs@minnie.tuhs.org
> Subject: Re: [TUHS] Quotas - did anyone ever use them?
>
> On Thu, May 30, 2019 at 12:04:49PM -0400, Noel Chiappa wrote:
> > > From: KatolaZ
> >
> > > I remember a 5MB quota at uni when I was an undergrad, and I
> definitely
> > > remember when it was increased to 10MB :)
> >
> > Light your cigar with disk blocks!
> >
> > When I was in high school, I had an account on the school's computer,
> > a
> > PDP-11/20 running RSTS, with a single RF11 disk (well, technically, an
> > RS11 drive on an RF11 controller). For those whose jaw didn't bounce
> > off the floor, reading that, the RS11 was a fixed-head disk with a
> > total capacity of 512KB
> > (1024 512-byte blocks).
> >
> > IIRC, my disk quota was 5 blocks. :-)
>
> Yep, I am not that "experienced" ;P
>
> HND
>
> --
> [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ]
> [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ]
> [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ]
> [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ]
> [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ]
next prev parent reply other threads:[~2019-05-30 17:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:04 Noel Chiappa
2019-05-30 16:48 ` KatolaZ
2019-05-30 17:42 ` ron [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
2019-06-04 13:50 ` Tony Finch
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='015701d5170f$19b44310$4d1cc930$@ronnatalie.com' \
--to=ron@ronnatalie.com \
--cc=katolaz@freaknet.org \
--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).