Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Dec 1999 07:48:24 +0100
From:      Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To:        Khetan Gajjar <khetan@os.org.za>
Cc:        current@FreeBSD.ORG
Subject:   Re: mount(2) broken?
Message-ID:  <19991207074824.B16352@daemon.ninth-circle.org>
In-Reply-To: <Pine.BSF.4.10.9912060011410.20655-100000@kg.ops.uunet.co.za>; from khetan@link.freebsd.os.org.za on Mon, Dec 06, 1999 at 12:13:39AM %2B0200
References:  <199912052145.QAA26864@khavrinen.lcs.mit.edu> <Pine.BSF.4.10.9912060011410.20655-100000@kg.ops.uunet.co.za>

next in thread | previous in thread | raw e-mail | index | archive | help
-On [19991206 00:00], Khetan Gajjar (khetan@link.freebsd.os.org.za) wrote:
>On Sun, 5 Dec 1999, Garrett Wollman wrote:
>>* Why isn't MAKEDEV installed by `make install' in a kernel
>>compilation directory?
>
>Afaik, anyone tracking -current either knows to do this or
>uses a tool (like mergemaster) that does it for you (I know
>I do ;-)

Not exactly a relevant answer to the question.  There is no reason that
after a new kernel or make world MAKEDEV shouldn't be upgraded/replaced
by the new one.

>Installing MAKEDEV also won't solve these problems from what
>I understand unless the disk devices are re-made. Is it
>acceptable for MAKEDEV to be installed into /dev
>(at some stage of the make world, rebuild kernel and install
>process) and have it re-make at least the disk devices contained
>in /etc/fstab and /etc/amd.conf ?

I don't think you want to force mknod's automatically for the same
reason you don't want /etc to be overwritten by new files.
Effectively: you want to have the framwork ready yet let the
administrator decide when to remake the devices.

Just my 0.02 Euro.

-- 
Jeroen Ruigrok van der Werven/Asmodai           asmodai@[wxs.nl|bart.nl]
Documentation nutter.          *BSD: Technical excellence at its best...  
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>;
Atone me to my throes curtail...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991207074824.B16352>