Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uwm.edu!math.ohio-state.edu!cs.utexas.edu!news.ti.com!sislnews.csc.ti.com!usenet From: pf@elissa.hc.ti.com (Paul Fuqua) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: amd: now you see it, now you don't (solved) Date: 14 Jul 1995 17:43:11 GMT Organization: Texas Instruments Lines: 18 Distribution: world Message-ID: <PF.95Jul14124311@elissa.hc.ti.com> References: <PF.95Jul8005835@elissa.hc.ti.com> NNTP-Posting-Host: elissa.hc.ti.com In-reply-to: pf@elissa.hc.ti.com's message of 08 Jul 1995 05:58:35 GMT Date: 08 Jul 1995 05:58:35 GMT From: pf@elissa.hc.ti.com (Paul Fuqua) Jul 6 20:01:13 rolery amd[168]: /net: mount: Operation not supported by device Following up my own post, with the answer. Amd can't start up a potential NFS automount unless NFS is in the kernel. Since I'm using FreeBSD on a laptop, I have a stripped-down kernel without NFS. When I first started playing with amd, I had earlier NFS-mounted another directory and thus caused NFS to be auto-modloaded into the kernel. When I rebooted, NFS was absent again, so amd errored as shown above; I guess whatever it does isn't sufficient to cause the auto-modload. I built another kernel that included NFS and everything works now. Paul Fuqua Texas Instruments, Dallas, Texas pf@hc.ti.com