Date: Wed, 5 Sep 2001 16:47:07 -0300 From: Fernan Aguero <fernan@iib.unsam.edu.ar> To: questions@FreeBSD.ORG Cc: kris@obsecurity.org, banksw@fang.cs.sunyit.edu Subject: Re: to MAKEDEV or not to MAKEDEV, that is my question Message-ID: <20010905164707.A1031@iib005.iib.unsam.edu.ar> In-Reply-To: <20010905120614.D76765@xor.obsecurity.org>; from kris@obsecurity.org on Wed, Sep 05, 2001 at 12:06:14PM -0700 References: <Pine.BSF.4.21.0109050939290.18902-100000@fang.cs.sunyit.edu> <20010905120614.D76765@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
+----[ Kris Kennaway dijo sobre "Re: to MAKEDEV or not to MAKEDEV, | that is my question": | | If that hardware uses devices, and when you try and access the | hardware the devices for it don't exist, you need to MAKEDEV them. | | That's really about as difficult as it gets. | | Kris | +----] The difficulty arises when you don't know _what_ to make. Quoting the Handbook: " Suppose you add the IDE CD-ROM support to the kernel. The line to add " is: " " device acd0 " " ... " " ... change to the /dev directory and type: " " sh MAKEDEV acd0 " " ... " " For sound cards the following command creates the appropriate " entries: " " sh MAKEDEV snd0 I needed sound so I added a 'device pcm' line to my kernel config file. Now why is it so _obvious_ that I should do a sh MAKEDEV snd0 (from the handbook) and not sh MAKEDEV pcm or sh MAKEDEV sound or sh MAKEDEV dsp sh MAKEDEV audio etc It's like saying something like "I want to list the contents of a directory, but I don't know the command to do it ...". Clearly, unless you know it beforehand, it is not intuitive that you should type "ls". You have to ask somebody or read several pages of a book before getting to know that. Fernan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010905164707.A1031>