From owner-freebsd-current Tue Mar 11 6:15: 3 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CD1837B401 for ; Tue, 11 Mar 2003 06:15:01 -0800 (PST) Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C61043FCB for ; Tue, 11 Mar 2003 06:15:00 -0800 (PST) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from edda.physik.uni-mainz.de (edda.Physik.Uni-Mainz.DE [134.93.180.218]) by klima.physik.uni-mainz.de (8.12.6/8.12.5) with ESMTP id h2BEExUb033406 for ; Tue, 11 Mar 2003 15:14:59 +0100 (CET) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Tue, 11 Mar 2003 15:14:58 +0100 (CET) From: "Hartmann, O." X-X-Sender: ohartman@edda.physik.uni-mainz.de To: freebsd-current@freebsd.org Subject: 5.0-CURRENT diskless boot recognition Message-ID: <20030311150056.K12960@edda.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello. As I posted prior to this question, I have problems in getting diskless started with 5.0-Current as cvsupdated today. The problem is still the same and after a night of hairloosing work I think I got closer to the problem. We use PXE as bootstrap environment, isc-dhcp and a read-only disk partition /usr/diskless conatining for each architecture we boot diskless its appropriate directory. The diskless kernels are compiled with individual 'ident Marker', have options NFS_ROOT, MD_ROOT, UNIONFS, PSEUDOFS and device md. The whole setup is as described in /etc/rc.d/initdiskless with special /conf-dir entries and this scheme works perfect under FreeBSD 4.7. FreeBSD 5.0-CURRENT seems to have problems within its bootstrap process to recognize that it is a diskless system. After the diskless station got its IP, loaded and booted the kernel I see this on screen: Mounting root from nfs: NF ROOT: MY.IP : /usr/diskless/xterm Loading configuration files. Starting file system checks: mount: / : unknown special file or filesystem Mounting NFS file system:. eval: /etc/rc.d/cleanvar: Permission denied. . . . After the last message a lot of deny error occur. I modified all the diskless-scripts in rc.d with my own echo commands to check which one gets involved, but none of them get touched! The above process looks identical of what a normal standalone machine does when booting. No wonder when diskless does not work when the init process does not recognize that it is booting diskless. We do not use BOOTP and I do not know whether FBSD 5.X does only support this scheme. We would like to stay with the NFS process. But I think technically this can not be the problem, because after the station has already booted the kernel it doesnt care what mechanism it booted from. NFS is the dominating facility and I could see, the root partition got mounted as expected. Can anyone help? Do I mark each kernel with 'ident DISKLESS' to give the init process any idea what it should do? If you need more informations about my configuration, please contact me. If someone could provide me with further informations how a init process or init scripts figures out whether it configures a diskless kernel or not, please let me know it. thanks in advance, Oliver -- MfG O. Hartmann ohartman@mail.physik.uni-mainz.de ------------------------------------------------------------------ Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) ------------------------------------------------------------------ Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message