From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: tuhs-bounces@minnie.tuhs.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.1 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 665e29f9 for ; Sun, 2 Sep 2018 22:31:09 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id CE9A6A1E1F; Mon, 3 Sep 2018 08:31:07 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id BDA6FA1A81; Mon, 3 Sep 2018 08:30:49 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b=pXBkUyjq; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 516EAA1A81; Mon, 3 Sep 2018 08:30:48 +1000 (AEST) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by minnie.tuhs.org (Postfix) with ESMTPS id 97E92A1A66 for ; Mon, 3 Sep 2018 08:30:47 +1000 (AEST) Received: by mail-oi0-f41.google.com with SMTP id p84-v6so30561159oic.4 for ; Sun, 02 Sep 2018 15:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iu4tALLezChdGgPLHXpwG+/03omUGQfkORnsfuT0v9c=; b=pXBkUyjq9ZRKCjYN1lQInZYifvu0ZYrSKPgYDwsb7CMniGT+YO6XiALKYtPr8WRWaM UIBiU5bongA6fszT7eD+7+/xU+eUpKu9wH86iFQzKxAnzy/65YoMo5yWwfVdHBI0Wt32 aXFblilfUMAIhL/CNQHc4BNOanbuBYAnOEXfjLEj87YyUGRVEYSZ8eJ11F10S+7u9yiX dW+hrrErWFNTtreWpqFWNZNVqiMCxkDSGCcJN27Ea16LN4zAODPu4XLPJUgoc3ksr7PJ SOj8KBgh+4700uvgrw968iqOSPmRmGsVU6kJGbNgkpuV9A0Y4mqHd8sIJBqXatjik10J Iyzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iu4tALLezChdGgPLHXpwG+/03omUGQfkORnsfuT0v9c=; b=VtnL7d7g3ldZjtC/oHeu8x5E4zaavJKF5Jn6DbBW2QSOz4hdsdOtRu5ms1Mtsu9bnO p3mDSUgVx6bkyCGmllwEc47gLHctnCevgzT4lDJtn5Ws0TTZvOGN6Chk9HYEUavZGy4K m2q7IR9JcI2mxFSK05p7WPXg3v9DpQCq+BKt7e7+pbjRZrdLlJQHT34wIWQuLcAMpOOo 9t9DcT7bqo9gASGQxGnbC+W2ZiLPQEMXP9f7VB4OkJYDI3tlRahR/o6BZqPo2OZm79jC YZBXlP3eu0lZCQqqoUDjfdNd3hkvsLNuvWqHUT5jxkPzJyXd+cROuQ7AVOIeofUoMHkP JcFA== X-Gm-Message-State: APzg51DviRG5rUeCx2BIFItQ6pwoYamvTY2txFCnaJ/UyfOToX4PrqGS 1yvV20fukdGbmA2BLxUwDjE= X-Google-Smtp-Source: ANB0VdaC592BysNRa8wv90M+cIeuLTD6FEWBIt643Gw9YFgar+z3ZlTN7RgUMjQltXdTAPbk5d/HyQ== X-Received: by 2002:aca:18d:: with SMTP id 135-v6mr15730846oib.2.1535927446910; Sun, 02 Sep 2018 15:30:46 -0700 (PDT) Received: from ?IPv6:2607:fb90:1cd1:d55b:5445:234e:ba99:a9c4? ([2607:fb90:1cd1:d55b:5445:234e:ba99:a9c4]) by smtp.gmail.com with ESMTPSA id v202-v6sm20289423oie.47.2018.09.02.15.30.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Sep 2018 15:30:45 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) From: Will Senn X-Mailer: iPhone Mail (15G77) In-Reply-To: <0D39179A-9133-4388-ABEC-DCD769E9CD24@pobox.com> Date: Sun, 2 Sep 2018 17:30:25 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180901232537.615A418C09E@mercury.lcs.mit.edu> <10B61FE8-1418-4201-A782-76E07BD2D34A@gmail.com> <0D39179A-9133-4388-ABEC-DCD769E9CD24@pobox.com> To: "Jeffrey H. Johnson" Subject: Re: [TUHS] Public access multics X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: tuhs@tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" Nice. I=E2=80=99ve always marveled at how, dare I say it while not doing any= thing about it, badly, dynamic linking has fared in nearly every os I can th= ink of? It is a very convenient feature to have, but the way are implemented= can be a little frustrating to a user who isn=E2=80=99t steeped in the inte= rnals of the implementation. Thanks for the lesson! Sent from my iPhone > On Sep 1, 2018, at 11:25 PM, Jeffrey H. Johnson wrote: >=20 > While the best loved feature is probably the pervasive dynamic linking, wh= ich is still unrivaled, and the security features (ring brackets, AIM (multi= level labeling), and ACLs) which are the most famous, a feature that isn't b= uilt in to Unix and is constantly being reinvented that was available in Mul= tics is the ability to easily set aside a CPU and some memory and disk, whil= e leaving the system in operation, and start another separate instance to do= development work, and then when the work is done, be reconfigured to merge t= he system back into one instance, without disrupting production work. =20 >=20 > That dynamic reconfiguration was one original design specifications of the= system, as opposed to being added later. Much of what makes Multics wonderf= ul to me is just how amazingly sturdily it's engineered and how complete the= implementations of these ideas are. >=20 > Another thing to comes to mind immediately is how hierarchical the system i= s. For example, users are registered on to projects, and a project administr= ator can be delegated the task of registering and deregistering user account= s and managing the system resources such as disk quota and access to printer= s and other physical resources for their project.=20 >=20 > The system administrator can manage the resources assigned to projects, an= d the project administration handles how that's further carved up amongst th= e users. >=20 > You can have similar granularity in assigning the distribution of resource= s such as CPU and memory use, by using the workload management features to e= nsure that high priority tasks/users/projects will always have needed resour= ces available, preempting lower priority tasks if necessary.=20 >=20 > The I/O system, (while not exceedingly elegant - see iox_), far exceeds wh= at is available in Unix today, but by design. >=20 > The reputation of Multics as a 'complex' system is, in my experience, well= deserved, but that complexity does not mean it's a terrible system to use o= r administer. I find it quite refreshing and it almost never feels dated. >=20 > -- Jeff > https://ban.ai/multics >=20 >> On Sep 2, 2018, at 12:05 AM, Will Senn wrote: >>=20 >> On Sep 1, 2018, at 6:25 PM, Noel Chiappa wrote:= >>=20 >>>> From: Will Senn >>>=20 >>>> I was thinking that Multics was a failed predecessor of unix >>>> ... straighten me out :) >>>=20 >>> I'd start with: >>>=20 >>> https://multicians.org/myths.html >>=20 >> Noel, Fascinating read. I must=E2=80=99ve read at least a good handful of= the references leading to the myths described in the writeup. As usual, I c= an trust the folks who lived history to remember it more clearly than many r= evisionists writing about it later. >>=20 >> Thanks for sharing. >>=20 >> Now, I=E2=80=99m wondering what awesome features Multics had that we=E2=80= =99re still lacking in modern *nices... anything as amazing as say, my favor= ite filesystem, ZFS? >>=20 >> Will >=20