From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1043 invoked by alias); 29 May 2002 22:42:00 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 1020 invoked from network); 29 May 2002 22:41:57 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by sources.redhat.com with SMTP; 29 May 2002 22:41:57 -0000 Received: (qmail 12115 invoked by uid 0); 29 May 2002 22:41:56 -0000 Received: from pd951e90c.dip.t-dialin.net (HELO celeron300a) (217.81.233.12) by mail.gmx.net (mp011-rz3) with SMTP; 29 May 2002 22:41:56 -0000 From: "gmx" To: "Corinna Vinschen" Cc: Subject: AW: mkcramfs porting done - device file issues.... Date: Wed, 29 May 2002 20:42:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-reply-to: <20020529101957.I30892@cygbert.vinschen.de> Importance: Normal X-SW-Source: 2002-05/txt/msg01821.txt.bz2 Hi Corinna, thanks for reply. >minor device numbers is purely internally. What you *can* do is, >create a /dev directory and create (in Windows Explorer) files in >it which are named exactly as the devices known to Cygwin. E. g. regarding this , what's the purpose of mknod.exe in cygwin then ??? >What would be possible is to add only the device nodes. They could >be implemented like symlinks Yes - that's what had come to my mind... >but I'm reluctant to add these to Cygwin as long as there's no mechanism >to actually use them. :((( maybe reading them, ls'ing them, tar'ing them or creating a cramfs from them could be a mechanism, i think.... ;) Though, there may be not many people out there, who actually need such feature. I think it would be nice, if it's "in there" just for "completeness" or "posix compliance".... or, maybe, just to get rid of those annoying: tar: netstation-0.8/pkg-tree/base/dev/console: Cannot mknod: Function not implemented netstation-0.8/pkg-tree/base/dev/md0 tar: netstation-0.8/pkg-tree/base/dev/md0: Cannot mknod: Function not implemented netstation-0.8/pkg-tree/base/dev/mem tar: netstation-0.8/pkg-tree/base/dev/mem: Cannot mknod: Function not implemented netstation-0.8/pkg-tree/base/dev/null..... ;))) i would do that stuff myself,if i could - so it completely depends on the goodwill of some "wizards" like you ... :( regards Roland Cygwin is using major and minor device numbers but there's nothing like a device node in the filesystem. The handling of major and minor device numbers is purely internally. What you *can* do is, create a /dev directory and create (in Windows Explorer) files in it which are named exactly as the devices known to Cygwin. E. g. if you created a file called `st0' - the name of the first tape device in the system - then you can call `ls -l /dev' and you will see: total 0 crw-rw-rw- 1 root root 18, 0 May 29 10:05 st0 The cause is that the handling of devices overrides the path handling. But that's *only* possible for device names known to Cygwin. > >Isn't this "feature" implemented yet and can it be easily implemented ? > > It isn't implemented and it would be difficult to implement. Sorry. We discussed to implement something like loadable device drivers already two years ago and which could be implemented using device nodes. It's not implemented though... no time, no volunteers. What would be possible is to add only the device nodes. They could be implemented like symlinks but I'm reluctant to add these to Cygwin as long as there's no mechanism to actually use them. Corinna -- 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/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1041 invoked by alias); 29 May 2002 22:41:59 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 1031 invoked by uid 9078); 29 May 2002 22:41:58 -0000 Received: (qmail 1019 invoked from network); 29 May 2002 22:41:57 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by sources.redhat.com with SMTP; 29 May 2002 22:41:57 -0000 Received: (qmail 12115 invoked by uid 0); 29 May 2002 22:41:56 -0000 Received: from pd951e90c.dip.t-dialin.net (HELO celeron300a) (217.81.233.12) by mail.gmx.net (mp011-rz3) with SMTP; 29 May 2002 22:41:56 -0000 From: "gmx" To: "Corinna Vinschen" Cc: Subject: AW: mkcramfs porting done - device file issues.... Date: Wed, 29 May 2002 20:55:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-reply-to: <20020529101957.I30892@cygbert.vinschen.de> Importance: Normal X-SW-Source: 2002-05/txt/msg01822.txt.bz2 Message-ID: <20020529205500.OhbrFCOZhsBCtSaOUj__JQvYujIITSmlaF4vct7Y1LI@z> Hi Corinna, thanks for reply. >minor device numbers is purely internally. What you *can* do is, >create a /dev directory and create (in Windows Explorer) files in >it which are named exactly as the devices known to Cygwin. E. g. regarding this , what's the purpose of mknod.exe in cygwin then ??? >What would be possible is to add only the device nodes. They could >be implemented like symlinks Yes - that's what had come to my mind... >but I'm reluctant to add these to Cygwin as long as there's no mechanism >to actually use them. :((( maybe reading them, ls'ing them, tar'ing them or creating a cramfs from them could be a mechanism, i think.... ;) Though, there may be not many people out there, who actually need such feature. I think it would be nice, if it's "in there" just for "completeness" or "posix compliance".... or, maybe, just to get rid of those annoying: tar: netstation-0.8/pkg-tree/base/dev/console: Cannot mknod: Function not implemented netstation-0.8/pkg-tree/base/dev/md0 tar: netstation-0.8/pkg-tree/base/dev/md0: Cannot mknod: Function not implemented netstation-0.8/pkg-tree/base/dev/mem tar: netstation-0.8/pkg-tree/base/dev/mem: Cannot mknod: Function not implemented netstation-0.8/pkg-tree/base/dev/null..... ;))) i would do that stuff myself,if i could - so it completely depends on the goodwill of some "wizards" like you ... :( regards Roland Cygwin is using major and minor device numbers but there's nothing like a device node in the filesystem. The handling of major and minor device numbers is purely internally. What you *can* do is, create a /dev directory and create (in Windows Explorer) files in it which are named exactly as the devices known to Cygwin. E. g. if you created a file called `st0' - the name of the first tape device in the system - then you can call `ls -l /dev' and you will see: total 0 crw-rw-rw- 1 root root 18, 0 May 29 10:05 st0 The cause is that the handling of devices overrides the path handling. But that's *only* possible for device names known to Cygwin. > >Isn't this "feature" implemented yet and can it be easily implemented ? > > It isn't implemented and it would be difficult to implement. Sorry. We discussed to implement something like loadable device drivers already two years ago and which could be implemented using device nodes. It's not implemented though... no time, no volunteers. What would be possible is to add only the device nodes. They could be implemented like symlinks but I'm reluctant to add these to Cygwin as long as there's no mechanism to actually use them. Corinna -- 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/