Return to BSD News archive
Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!pascal
From: pascal@netcom.com (Richard Childers)
Subject: Re: Some ideas on the driver interface
Message-ID: <1993Mar10.182912.13643@netcom.com>
Organization: The Free State of Dis
References: <C3MCIF.Iv@sugar.neosoft.com> <1nj0ej$j6s@walt.ee.pdx.edu> <1993Mar10.102342.26886@gmd.de>
Date: Wed, 10 Mar 1993 18:29:12 GMT
Lines: 22
veit@fanoe.gmd.de (Holger Veit) writes:
>may crash. New devs should be mknod'd at bootup of a kernel (e.g.
>automatically by a devfs) or later manually by executing /dev/MAKEDEV.
>I don't see a problem with duplicate info, as long as there is a mechanism
>to distinguish between an old /dev/MAKEDEV and the new one; they must fit
>together.
Or you could rewrite the /dev/MAKEDEV and move the old one to MAKEDEV.old ...
Maybe MAKEDEVs could be paired to kernels, to allow multiple kernels and
their corresponding MAKEDEVs, with a MAKEDEV.GENERIC for problems ?
-- richard
--
"It is obligatory, within the limits of capability, to commend the
good and forbid evil." _Kitab_Adab_al-Muridin_, by Suhrawardi
richard childers pascal@netcom.com