Svante Signell, on mer. 20 sept. 2017 08:46:49 +0200, wrote:
> I changed the patch for __execve() to keep file_name if the path is absolute
> and
> call realpath() for relative paths.
But then if you call a script that looks at $0 from a relative path,
it'll break.
> (I did also a cetcwd() versi
Samuel Thibault, on jeu. 21 sept. 2017 00:24:28 +0200, wrote:
> Riccardo Mottola, on mer. 20 sept. 2017 23:53:17 +0200, wrote:
> > xterm: Error 27, errno 1073741849: Inappropriate ioctl for device
> > Reason: spawn: ioctl() failed on TIOCLSET
>
> There are probably a lot more things like that whic
Hello,
Riccardo Mottola, on mer. 20 sept. 2017 23:53:17 +0200, wrote:
> xterm: Error 27, errno 1073741849: Inappropriate ioctl for device
> Reason: spawn: ioctl() failed on TIOCLSET
Mmm, this is indeed not implemented.
We should probably not expose it in bits/ioctls.h.
There are probably a lot
Hi HURDers,
Both if I start xterm as uxterm, I get these errors:
$ uxterm
xterm: Error 27, errno 1073741849: Inappropriate ioctl for device
Reason: spawn: ioctl() failed on TIOCLSET
$ xterm
xterm: Error 27, errno 1073741849: Inappropriate ioctl for device
Reason: spawn: ioctl() failed on TIOCLS
Ooops!! I forgot that! :)
2017-09-20 20:06 GMT+02:00 James Clarke :
> On 20 Sep 2017, at 11:08, Joan Lledó wrote:
>>
>> ---
>> eth-multiplexer/Makefile | 2 +-
>> eth-multiplexer/device_impl.c | 5 +
>> 2 files changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/eth-multiplexer/Make
On 20 Sep 2017, at 11:08, Joan Lledó wrote:
>
> ---
> eth-multiplexer/Makefile | 2 +-
> eth-multiplexer/device_impl.c | 5 +
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/eth-multiplexer/Makefile b/eth-multiplexer/Makefile
> index cefa0abd..2b19de6d 100644
> --- a/et
---
eth-multiplexer/Makefile | 2 +-
eth-multiplexer/device_impl.c | 5 +
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/eth-multiplexer/Makefile b/eth-multiplexer/Makefile
index cefa0abd..2b19de6d 100644
--- a/eth-multiplexer/Makefile
+++ b/eth-multiplexer/Makefile
@@ -29,
Hello,
One difference between pfinet and lwip translators is that pfinet doesn't
delete interfaces (or I haven't found how to do it) while lwip does. For
instance, if one starts pfinet with:
settrans -fga /servers/socket/2 /hurd/pfinet -i /dev/eth1 -a 192.168.123.178 -m
255.255.255.0 -g 192.16