From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id d9fcf4ac for ; Thu, 30 May 2019 14:49:15 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 8D9079B84E; Fri, 31 May 2019 00:49:14 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A77F59B7FB; Fri, 31 May 2019 00:49:03 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="F7VXOLCL"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 0EAB19B7FB; Fri, 31 May 2019 00:49:03 +1000 (AEST) Received: from mail-ua1-f49.google.com (mail-ua1-f49.google.com [209.85.222.49]) by minnie.tuhs.org (Postfix) with ESMTPS id 7FCB49B6B2 for ; Fri, 31 May 2019 00:49:02 +1000 (AEST) Received: by mail-ua1-f49.google.com with SMTP id 7so2584527uah.1 for ; Thu, 30 May 2019 07:49:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B62MMCEC8HTXrCfx64YCf/ye8AoWbERoawylKoqWb48=; b=F7VXOLCLlHqr+v9up9WLqUcGgWjj+gICJ18Zpneol+MM5vgi5kAheXzhHgJr9kFftN wkOqa1J20laTwE8DR9OliqY1QPnz75RlWFZE+D5KHPNb7iTKfPolqfc7ElEv8PHkf7Cu LwoiOE9o+de3sx9uS52asjqWOiOBPapjywJXzfT9oxQ1bFOJ/QYn0PVuSNWdP72aOAfv QvDf/0FL8qo64uBssWQ177wr0mj5iR37RT6opOM+XMRwr3vuXeXSbJVZdJnKmXeX2ijQ Yh1ATe0On5cGbwrIhJ7DQnAwpvhEX5wi+9PPTXaOY6wh026gwxVaSEj+Fd33W12Hjh/w 3diA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B62MMCEC8HTXrCfx64YCf/ye8AoWbERoawylKoqWb48=; b=T0/j7cRopEiPtpHZ4T8WNbflqp/S2VOABxvqAgEQiSAqATgpMBrNNZDniYN0ZlleBV CKVF+xrPSNnzVfuDHpW+sHqWmA8bFxAO1oZBeP9ly4kM87JZbfj0DHT+ylhGPQVE3tcA Ek42BwpPZVz43yifPnBUwKga/YfwELLEKjI5OvaP1hzzIiEl7HAwQV8Vh2JIJ3cufV9O w1iPkGORujeAuFhSzU7zVZrXmuJtJvlPD0e0b7/mRz6fYEB/4UAcUuZpUpznOwuWPNyU rQ07z8LCjMFBvEeqfYOJln/IXWM7vBlcs7IsPHfCYEiu8sfSFCFpttoAOEj3mCGZPwS6 rsSQ== X-Gm-Message-State: APjAAAWU6O3tGfYiq4inaEyJTt+12MZmfy/rZ8i/m99hJO8k2c7wVJFA FxhunEhiCApHIPhEbreka9FeR2/m5vv9RhN6zaE= X-Google-Smtp-Source: APXvYqzLkBCbYOxEjXkVS1qUQIDwUbGN6QiYRUDA5+0JmmWgUCKK7X1Cwqd5hH9d3srmBzXxEg7ZfVJsemM0FJ9lRak= X-Received: by 2002:ab0:13ef:: with SMTP id n44mr2029233uae.4.1559227741512; Thu, 30 May 2019 07:49:01 -0700 (PDT) MIME-Version: 1.0 References: <975B93B6-AD7C-41B5-A14D-2DE4FEFAD3A6@kdbarto.org> <20190530143414.GF2751@mit.edu> In-Reply-To: <20190530143414.GF2751@mit.edu> From: "John P. Linderman" Date: Thu, 30 May 2019 10:48:50 -0400 Message-ID: To: "Theodore Ts'o" Content-Type: multipart/alternative; boundary="000000000000a82ac1058a1bffe2" Subject: Re: [TUHS] Quotas - did anyone ever use them? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000a82ac1058a1bffe2 Content-Type: text/plain; charset="UTF-8" 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 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 > --000000000000a82ac1058a1bffe2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 t= o prevent accidents from adversely affecting the user community at large. I= f you knew you were going to need honking amounts of disk, the sysad= mins would raise the quota (probably on a partition dedicated to such activ= ities).

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.=C2=A0 It could be increased by applying to<= br> the user accounts office.=C2=A0 Given that there were roughly 4,000
undergraduates sharing 5 or 6 Vax/750's, it was somewhat understandable= ...

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 - Ted
--000000000000a82ac1058a1bffe2--