Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 9 Nov 2001 10:48:28 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [Q] mknod: function not implemented Message-ID: <20011109104828.R1099@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from coffeenocreamnosugar@hotmail.com on Fri, Nov 09, 2001 at 05:11:55AM +0000 On Fri, Nov 09, 2001 at 05:11:55AM +0000, K ?? wrote: > > Hi > > after using mknod ' mknod -m 0666 /devttyS0 ........ ' > I got this message " mknod: function not implemented " > > Is there anyother way to make device file with cygwin.? > I was porting a device driver.. Cygwin has no idea about device drivers. The /dev devices in Cygwin are just POSIX layer fakes on top of standard Win32 functions. `mknod' doesn't work in Cygwin. If you're really writing a device driver, you have two ways to go: - If it's a device driver for a functionality which is already available using Win32 calls and you just want to use it in Cygwin, look into the Cygwin sources and contribute a new fhandler_dev_foo. - If you're writing a real, low level device driver, you have to use Microsoft's DDK and MSDN to write e.g. a WDM driver. This is completely out of Cygwin's focus. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/