From owner-freebsd-alpha Fri Dec 24 12: 9:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id 5936614F94; Fri, 24 Dec 1999 12:09:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA10876; Fri, 24 Dec 1999 12:14:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912242014.MAA10876@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilko Bulte Cc: Mike Smith , FreeBSD-alpha mailing list Subject: Re: diskless boot on Alpha In-reply-to: Your message of "Fri, 24 Dec 1999 17:47:08 +0100." <19991224174708.A63398@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Dec 1999 12:14:16 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I admit not to understand why this is the case. My theory right now is > that the compile of autoconf.c should include opt_nfs.h in addition to > opt_nfsroot.h. The latter is already present. ... > When I add opt_nfs.h to the include files in autoconf.c thing compile like > expected. Can somebody please verify this for me? Sounds about right to me. > When I boot a kernel built with the above patch I get: > > >>## nfsroot before ufs > Mounting root from ufs:192.168.200.22:/usr/sandpiper > Can't allocate root mount for filesystem 'ufs': 19 > Root mount failed: 19 Ugh. > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0s1a > ? List valid disk boot devices > Abort manual input Did you try entering nfs:192.168.200.22:/usr/sandpiper here? > Which I don't understand because vfs_mountroot() should try nfs before > ufs because that is the order in which cpu_rootconf sets up the > rootdevnames ? And in my case the kernel is compiled without > FFS and FFS_ROOT so it should only do NFS. I don't think that it's even getting down to the paths in rootdevnames[], I think it's trying to boot the path from the vfs.root.mountfrom variable which is set by the loader. I'm puzzled as to why it doesn't then move on to the fallbacks. Can you add some debugging to to sys/kern/vfs_conf.c:vfs_mountroot() and see exactly what's going on there? Thanks... > I'm puzzled.. > > NB as the code tells me to use 'loader', how do I set > that up on Alpha? I still need to bootp netboot right? netboot is the loader, it just has the wrong name. One of these days they'll all coalesce back into a single binary. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message