On Thu, 16 Nov 2006, Corinna Vinschen wrote:
> On Nov 16 09:27, Igor Peshansky wrote:
>
> [YAFQ]
>
> > On Thu, 16 Nov 2006, Corinna Vinschen wrote:
> > > On Nov 15 06:40, Eric Blake wrote:
> > > > [...] it seems like it might be nicer if cygwin/devices.in were to
> > > > provide them natively for
Corinna Vinschen 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, e
On Nov 16 09:27, Igor Peshansky wrote:
[YAFQ]
> On Thu, 16 Nov 2006, Corinna Vinschen wrote:
> > On Nov 15 06:40, Eric Blake wrote:
> > > [...] it seems like it
> > > might be nicer if cygwin/devices.in were to provide them natively for all
> > > users.
> >
> > Dunno about that. On Linux, /dev/s
On Thu, 16 Nov 2006, Corinna Vinschen wrote:
> On Nov 15 06:40, Eric Blake wrote:
> >
> > I know it is possible to create /dev/std{in,out,err} myself, simply making
> > symlinks to /proc/self/fd/{0,1,2}, once I create an underlying physical
> > /dev directory. But by doing so, I have made it so t
On Nov 15 06:40, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I know it is possible to create /dev/std{in,out,err} myself, simply making
> symlinks to /proc/self/fd/{0,1,2}, once I create an underlying physical
> /dev directory. But by doing so, I have made it so that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know it is possible to create /dev/std{in,out,err} myself, simply making
symlinks to /proc/self/fd/{0,1,2}, once I create an underlying physical
/dev directory. But by doing so, I have made it so that the version of
bash that I compile detects their
6 matches
Mail list logo
