Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!uunet!amdahl!JUTS!cd.amdahl.com!gab10 From: gab10@cd.amdahl.com (Gary A Browning) Newsgroups: comp.os.386bsd.development Subject: Re: Some ideas on the driver interface (was: Re: Release of drivers etc.) Message-ID: <5a0H02vf3aM801@JUTS.ccc.amdahl.com> Date: 12 Mar 93 07:09:26 GMT References: <C3MCIF.Iv@sugar.neosoft.com> <1nj0ej$j6s@walt.ee.pdx.edu> <0bcN02Do3ab301@JUTS.ccc.amdahl.com> <1nmh05INNt7c@life.ai.mit.edu> Sender: netnews@ccc.amdahl.com Organization: Amdahl Corporation Lines: 28 In article <1nmh05INNt7c@life.ai.mit.edu>, mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes: > > In article <0bcN02Do3ab301@JUTS.ccc.amdahl.com> gab10@cd.amdahl.com > (Gary A Browning) writes: > > > > Shouldn't /dev/MAKEDEV be built by the kernel building process? > > Maybe by config. [ deleted ] > `config' should NEVER, EVER, EVER, EVER, EVER, EVER, EVER modify > ANYTHING outside of the /sys/compile/FOOBAR directory. NEVER!! > > If it builds a MAKEDEV script in /sys/compile/FOOBAR, that's fine. Sorry, I should be more careful with my writing. The concept was that a MAKEDEV script be created during the configuration process and associated with the created kernel. During the kernel installation process (which is currently just a 'cp') the MAKEDEV script associated with the kernel be installed in /dev. /dev should then be cleared and the script run to create the devices configured into the kernel. Of course, you may not want to even move the MAKEDEV to /dev. You may just want to leave it in the config directory. -- Gary Browning | Exhilaration is that feeling you get just after a gab10@cd.amdahl.com | great idea hits you, and just before you realize | what is wrong with it.