Bug 11618 - /net references generate errors
/net references generate errors
Product: Red Hat Linux
Classification: Retired
Component: am-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Vrabec
Depends On:
  Show dependency treegraph
Reported: 2000-05-23 18:06 EDT by Jeff Blaine
Modified: 2007-04-18 12:27 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-28 07:21:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Blaine 2000-05-23 18:06:15 EDT
Referencing /net/SOME_HOSTNAME (as /net is meant to be used)
generates the following message from amd:

No fs type specified (key = "/defaults", map = ""root"")

It has been doing this since....hmmm...I think even as far back
as Red Hat 4.2.
Comment 1 Nalin Dahyabhai 2000-07-10 13:35:07 EDT
This works correctly here, both with the version from 6.2 and Raw Hide
(ftp://ftp.redhat.com/rawhide/).  Is your DNS set up correct.y?
Comment 2 Jeff Blaine 2000-07-10 14:23:41 EDT
It works, but the error still gets generated.  This has been happening since at least as far back as 4.2
DNS is set up correctly.

% uname -a
Linux aclient.mitre.org 2.2.14-5.1 #1 Tue May 9 09:20:06 EDT 2000 i686 unknown
% cat /etc/redhat-release 
Red Hat Linux release 6.2 (Zoot)
% ls /net/ourserver
export/  usr/  va/  vb/

[ in syslog ]:
Jul 10 14:07:41 ramet amd[755]: No fs type specified (key = "/defaults", map = ""root"")

jblaine : ramet > nslookup ourserver
Server:  linus.mitre.org

Name:    ourserver.mitre.org

Comment 3 Cristian Gafton 2000-08-08 22:45:40 EDT
assigned to nalin
Comment 4 Peter Vrabec 2005-09-28 07:21:40 EDT
I replaced type option to /default in /etc/amd.net, which helps.

/defaults fs:=${autodir}/${rhost}/root/${rfs};type:=host;opts:=nosuid,nodev
*         rhost:=${key};rfs:=/

Note You need to log in before you can comment on or make changes to this bug.