Mail Archives: cygwin/2006/11/20/09:02:13
On Nov 16 16:25, Eric Blake wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>
> > > > So what we should do here IMO is to augment the base-files package
> > > > to create a /dev directory and create a couple of standard symlinks
> > > > in it, which are not covered automatically by the Cygwin DLL.
> > >
> > > There already was some discussion, ending in
> > > <http://cygwin.com/ml/cygwin-developers/2005-02/msg00010.html>, which
> > > never got a reply...
> >
> > Isn't your create_devices script adding all the devices handled by
> > Cygwin? The idea here is slightly different in that the script should
> > only create symlinks in /dev. Device nodes for the exising Cygwin
> > devices are not actually necessary so we should be careful with them,
> > maybe.
>
> One of my concerns is that readdir() on /dev works nicely, integrating both
> symlinks and actual cygwin devices. Right now, the benefit of Igor's script
> creating placeholders even for actual devices is that readdir() (and thus
> ls /dev, or even tab completion when you type /dev/<TAB>) can see all devices
> and not just symlinks like /dev/stdin.
Yeah, right. I'm thinking along the same lines. Consider the situation
that /dev/ is handled automatically at one point in aa udev sort of way.
In that case static device nodes would be in the way. Or, hmm, maybe not.
But that's why I suggested to be careful for now.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -