From owner-freebsd-hackers Mon Oct 14 01:44:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA13413 for hackers-outgoing; Mon, 14 Oct 1996 01:44:00 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA13406 for ; Mon, 14 Oct 1996 01:43:57 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id BAA20822 for ; Mon, 14 Oct 1996 01:43:46 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA12775; Mon, 14 Oct 1996 09:16:02 +0100 From: Luigi Rizzo Message-Id: <199610140816.JAA12775@labinfo.iet.unipi.it> Subject: Re: /sbin/init permission To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 14 Oct 1996 09:16:01 +0100 (MET) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199610122049.WAA10051@uriah.heep.sax.de> from "J Wunsch" at Oct 12, 96 10:49:03 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Luigi Rizzo wrote: > > > Changing permissions to /sbin/init has no > > undesired side effects, so it thought it was a non controversial > > change. Maybe I am wrong ? > > I'm not even sure whether this is a bug in NFS or not. If the file is > executable, this should probably suffice. OTOH, i think with the Don't think it' s a bug. The problem is that /sbin/init is accessed with root ID, and without root=0 the ID is mapped to nobody and access is denied. Besides, I seem to remember that you only need read permissions, not execute, for /sbin/init to be loaded correctly at startup. This probably means that that /sbin/init is loaded as data, not as an executable, by the kernel. > current setup, it's almost impossible to have the root f/s exported > without option root=0. Not impossible, I have done it many times, and have it working here -- a shared, readonly root without option root=0. Except for a small problem with vipw, other things work fine. > > It is my impression that quite a few people are using the diskless > > code -- mostly to administer labs etc. with many machines where > > users have the habit of pushing the reset button when something > > goes wrong. Every people I talked to has developed their own > > solutions. > > > It would be nice if these efforts could be coordinated to produce > > an easy "diskless" setup utility. > > The description in the handbook was sufficient for me to get my own > setup going. However, what i've been missing was a good template that I was talking about a shared root. This is what you need for a lab, you do not want to waste space & maintain directories for every client. Cheers Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ====================================================================