Re: Contributing to Hurd
Hi, > Joan, where do think something could be missing? Maybe a good start is to read and understand all the code of the translator and explain what every function does. That could be useful for others who want to contribute to the Hurd, not only on the lwip translator. Back in my GSoC I took some notes about pfinet, lwip, glibc and ip6. Attached are the notes but please Sooraj, take into account these are personal notes, not intended to be published and the statements I make in these documents *may be wrong*. I hope these notes help you to complete your documentation. Another thing you could do as part of your thesis is to make performance tests on both lwip and pfinet translators, to check which is faster and what's the difference. I never tested this, but I remember Justus did some quick tests and said the lwip translator was far slower than pfinet. It would be nice to confirm it and figure out why. >Also, are there perhaps some features that Sooraj could work on? If I remember correctly, poll() and ppoll() on glibc end up calling the io_select operation. Maybe a good exercise would be to add a new 'poll' operation to the pfinet interface, b/c it's not a big change but it requires changes on glibc, the MIG interface and the translator, so it's a nice exercise to have the full picture of how the Hurd works. What do you think?
Re: Contributing to Hurd
Joan Lledó, le dim. 03 mars 2019 17:25:47 +0100, a ecrit: > If I remember correctly, poll() and ppoll() on glibc end up calling > the io_select operation. Maybe a good exercise would be to add a new > 'poll' operation to the pfinet interface, What would be the difference with the io_select operation? The real difference between select() and poll() is the way to express a set of fds, and that does not show up in the RPCs anyway. Samuel
Re: Contributing to Hurd
Missatge de Samuel Thibault del dia dg., 3 de març 2019 a les 17:39: > > What would be the difference with the io_select operation? > The real difference between select() and poll() is the way to express a > set of fds, and that does not show up in the RPCs anyway. Mmm, yeah, that's right. Then I can't think of anything... maybe study the TCP tuning options lwip provides and choose the best values for the Hurd?
Re: Query on ifconfig
Hi, and excuse my delay: Did you got to solve this? How can I reproduce your workaround? El Lunes 18 de febrero de 2019, Vinay M escribió: > Hi Almudena, > > To give some more context, earlier versions of "ifconfig" was working fine. > Recently we upgraded to MAC 10.13.6 and latest inetutils which is causing > this. > Any work around would be greatly appreciated. Thank you. > > > > > > On Fri, Feb 15, 2019 at 2:46 AM Almudena Garcia > wrote: > > > Thanks!! Now I know the command > > > > > > > > El jue., 14 feb. 2019 a las 22:10, Samuel Thibault (< > > samuel.thiba...@gnu.org>) escribió: > > > >> Almudena Garcia, le jeu. 14 févr. 2019 22:01:55 +0100, a ecrit: > >> > > >> > > I have installed this package in my Debian GNU/Hurd installation, > >> but > >> > ifconfig > >> > > appears as "command not found", even as sudo > >> > > >> > Use inetutils-ifconfig. > >> > > >> > This package don't exists in my repositories. > >> > >> I mean the command is called inetutils-ifconfig, not ifconfig. > >> > >> Samuel > >> > > > > -- > Regards, > *Vinay* > -- Enviado desde mi Sailfish OS
Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack
On Fri, 2019-03-01 at 07:04 -0800, Samuel Thibault wrote: > Svante Signell, le lun. 25 févr. 2019 10:25:01 +0100, a ecrit: > > Unfortunately, the situation has not improved with it :( > > > > The SIGILL failures are now SIGABRT and SIGSEGV as they became with the > > SS_DISABLE patch. > > It however seems that the failures are different? > (possibly with much more understandable backtraces) No they are not from a global tests perspective. That requires further investigations. I suspect the problems arise earlier in the backtrace chain. One suspicion is the *context functions. Can they be called more than once without problems? Unfortunately I don't know anything (have forgotten everything) about assembly code... Just a thought!
Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack
Svante Signell, le dim. 03 mars 2019 23:21:55 +0100, a ecrit: > On Fri, 2019-03-01 at 07:04 -0800, Samuel Thibault wrote: > > Svante Signell, le lun. 25 févr. 2019 10:25:01 +0100, a ecrit: > > > Unfortunately, the situation has not improved with it :( > > > > > > The SIGILL failures are now SIGABRT and SIGSEGV as they became with the > > > SS_DISABLE patch. > > > > It however seems that the failures are different? > > (possibly with much more understandable backtraces) > > No they are not from a global tests perspective. Well, some golang packages now do build fine. > That requires further investigations. That's what I meant by mentioning the backtraces. Samuel
Re: Query on ifconfig
Hi Team, I was able to fix this by following - https://medium .com/@david.limkys/permanently-create-an-ifconfig-loopback-alias-macos-b7c93a8b0db Thanks for reply and support. On Sun, Mar 3, 2019 at 11:51 PM Almudena Garcia wrote: > Hi, and excuse my delay: > > Did you got to solve this? > > How can I reproduce your workaround? > > > > El Lunes 18 de febrero de 2019, Vinay M escribió: > > Hi Almudena, > > > > To give some more context, earlier versions of "ifconfig" was working > fine. > > Recently we upgraded to MAC 10.13.6 and latest inetutils which is causing > > this. > > Any work around would be greatly appreciated. Thank you. > > > > > > > > > > > > On Fri, Feb 15, 2019 at 2:46 AM Almudena Garcia < > liberamenso10...@gmail.com> > > wrote: > > > > > Thanks!! Now I know the command > > > > > > > > > > > > El jue., 14 feb. 2019 a las 22:10, Samuel Thibault (< > > > samuel.thiba...@gnu.org>) escribió: > > > > > >> Almudena Garcia, le jeu. 14 févr. 2019 22:01:55 +0100, a ecrit: > > >> > > > >> > > I have installed this package in my Debian GNU/Hurd > installation, > > >> but > > >> > ifconfig > > >> > > appears as "command not found", even as sudo > > >> > > > >> > Use inetutils-ifconfig. > > >> > > > >> > This package don't exists in my repositories. > > >> > > >> I mean the command is called inetutils-ifconfig, not ifconfig. > > >> > > >> Samuel > > >> > > > > > > > -- > > Regards, > > *Vinay* > > > > -- > Enviado desde mi Sailfish OS -- Regards, *Vinay*