Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!phaedrus.kralizec.net.au!news.mel.aone.net.au!news.mira.net.au!news.vbc.net!vbcnet-west!samba.rahul.net!rahul.net!a2i!news.pbi.net!news.mathworks.com!news.eecs.umich.edu!life.eecs.umich.edu!not-for-mail
From: pmchen@life.eecs.umich.edu (Peter M. Chen)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: amd broken for 2.2.2?
Date: 20 May 1997 21:18:26 GMT
Organization: University of Michigan EECS
Lines: 23
Message-ID: <5lt4f2$ki$1@news.eecs.umich.edu>
NNTP-Posting-Host: 141.213.8.32
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41302
The amd that's shipped with 2.2.2-RELEASE appears to be broken (or I'm
doing something wrong). It complains about "bad address" when it attempts
a mount; then the mount fails. I'm starting it manually (to test it)
via:
amd /n /etc/amd.map
I tried automounting file systems from a SunOS server and a Digital Unix
server, and both failed.
If I use the amd binary that came with 2.2.0-RELEASE, it works fine on the
machine running 2.2.2. Perhaps it has something to do with the switch to
NFSv3?
Pete
Prof. Peter M. Chen
EECS Department, 2225 EECS
1301 Beal Ave.
University of Michigan
Ann Arbor, MI 48109-2122
(313) 763-4472, fax: (313) 763-4617
pmchen@eecs.umich.edu
http://www.eecs.umich.edu/~pmchen/