Mail Archives: djgpp-workers/1999/02/22/14:18:18
Bonjour M. Eli Zaretskii
> > > There's no `chroot' in DJGPP's library. So, to support this
..
> Right. So a library module called `putpath.c' will need to be
> replaced with a custom one as well, and that custom version will need
> to know about the current root. `putpath.c' is the single place used
Ok.
> If you means a simple spawn, then this inheritance of the three
> standard file handles is already done automatically for you.
>
> I mentioned this issue because running a child program asynchronously
> in another DOS box doesn't make it a child program (as far as Windows
> is concerned), and thus the file handles aren't inherited.
To emulate the typical Un*x fork/dup/exec
- I need spawn to set its std{in,out,err} to something else,
so actually in spwan code :
pid_t spawn (const char *path, const int fdlen, const int fdarray[],
const char *argv, const char **envp)
{
...
for (i = 0; i < fdlen; i++)
{
dup2(fdarray[i], i);
}
...
}
BTW, this merely a suggestion, I have no idea how spawn is implemented.
- When I spawn(), the parent goes on to its business right ?
You kinda hinted that It may not be the case witout
something call "start /m".
>
> I don't reboot mine at all ;-).
8-), Well with R. D. libsocket, I've already got the
ftp client working, and getting the rest of the clients should be
a question fo time. I don't know about the servers, to many unknowns.
I don't know if full DJGPP/libsocket support will make it to the
next release of inetutils, since it is a security fix release.
But probably hooks or at least the possibility to compile
some clients, like ftp, will be in.
--
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!
- Raw text -