Rust on Hurd GSoC (Was: Prospectives)

Hello Vedant, So the assignment is now official, congrats and welcome! So now begins the bonding period. This is the time to get acquainted with the communication channels of the projects. You should subscribe to the bug-hurd mailing list, and it would be useful that you come to the #hurd channel

Re: Interest in GNU Hurd Project for GSoC 2023

ual memory subsystem > Adding support for new file systems to the Hurd > However, I am open to working on any project that the GNU Hurd team considers > suitable for a GSoC participant. We would welcome help on the rust project https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/ru

Re: GSoC Project Proposal for GNU/Hurd and Rust

April 1, 2023 8:59 PM, "Vedant Tewari" wrote: > Hello, > I am a current potential contributor to GSoC 2023 and am still looking for a > project and would love > to learn about Rust, I am a C Programmer and have worked Unix and Linux > Kernels in the past, I have >

RE: GSoC Project Proposal for GNU/Hurd and Rust

Hello, I am a current potential contributor to GSoC 2023 and am still looking for a project and would love to learn about Rust, I am a C Programmer and have worked Unix and Linux Kernels in the past, I have some experience working with compilers and would love to learn about the dependency and

Re: Interest in GNU Hurd Project for GSoC 2023

Thank you for your response. I'll see you there! On Sat, Apr 1, 2023, 3:51 PM wrote: > March 31, 2023 2:39 PM, "Yasser Cherfaoui" > wrote: > > > Dear GNU Hurd team, > > > > I am writing to express my interest in taking the GNU Hurd project as a >

Re: Interest in GNU Hurd Project for GSoC 2023

March 31, 2023 2:39 PM, "Yasser Cherfaoui" wrote: > Dear GNU Hurd team, > > I am writing to express my interest in taking the GNU Hurd project as a > Google Summer of Code > (GSoC) 2023 project. I am a computer science student with experience in > system programm

Interest in GNU Hurd Project for GSoC 2023

Dear GNU Hurd team, I am writing to express my interest in taking the GNU Hurd project as a Google Summer of Code (GSoC) 2023 project. I am a computer science student with experience in system programming and kernel development, and I have been following the GNU Hurd project for some time now. I

Re: [GSOC ‘23] Interested in working on Porting Rust to GNU/Hurd

Thanks, I will do that. On Thu, Mar 30, 2023 at 4:24 PM wrote: > March 30, 2023 11:01 AM, "Raj Sahu" wrote: > > > Thanks for the links Joshua. I saw the more descriptive problem > statement and goals for the Rust > > porting task and would like to take it up

Re: [GSOC ‘23] Interested in working on Porting Rust to GNU/Hurd

March 30, 2023 11:01 AM, "Raj Sahu" wrote: > Thanks for the links Joshua. I saw the more descriptive problem statement and > goals for the Rust > porting task and would like to take it up for my GSOC application. Would you > suggest me to go with > the bonding exerci

Re: [GSOC ‘23] Interested in working on Porting Rust to GNU/Hurd

Thanks for the links Joshua. I saw the more descriptive problem statement and goals for the Rust porting task and would like to take it up for my GSOC application. Would you suggest me to go with the bonding exercise or shall I work on the proposal right away? Thanks Raj On Thu, 30 Mar 2023 at 10

Re: [GSOC ‘23] Interested in working on Porting Rust to GNU/Hurd

March 30, 2023 1:18 PM, "Raj Sahu" wrote: > Hello > I was going through the list of proposed ideas within GNU for the GSOC'23 and > I wanted to get in > touch with you to discuss more about it. > > I am currently a Master's student at Virginia Tech wor

Re: GSoC applicant

March 30, 2023 12:37 AM, "Khalil Mouawad" wrote: > Dear recipient, > > I just learned about GSoC today and I really don't want to miss this > opportunity to put my > knowledge and skills to practice. > > Here are some information that should help you id

GSoC applicant

Dear recipient, I just learned about GSoC today and I really don't want to miss this opportunity to put my knowledge and skills to practice. Here are some information that should help you identify my strength and weaknesses : - I am a C++ developer - I am confident in my C development abil

Re: GSOC -23 contrubution on gnu hurd

te in gnu hurd , and looking > for some guide . I don't have prior knowledge of open source , if you can help > out . You can take a look at the rust project page: https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ and the hurd contributing page: https://darn

GSOC -23 contrubution on gnu hurd

Respected sir/madam, I am Chandra Churd Bharati currently doing my bachelor's degree in Computer Applications form Institue of Techinical Education and Research in India .I know languages like C and C++ wanted to contribute in gnu hurd , and looking for some guide . I don't have prior knowledge of

Re: GSOC

Hello, Saathvikk M, le lun. 20 mars 2023 13:57:04 +0530, a ecrit: > I am Saathvikk Muthyala. How to register for this specific project through > GSOC? In the GSOC program, the Hurd project is within the GNU organization umbrella. Samuel

Re: GSOC

March 20, 2023 8:16 AM, "Saathvikk M" wrote: > Respected Sir/Madam, > > I am Saathvikk Muthyala. How to register for this specific project through > GSOC? What are you interested in working on? https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/ Which

GSOC

Respected Sir/Madam, I am Saathvikk Muthyala. How to register for this specific project through GSOC?

Re: GSoC'2023: Porting Rust to GNU/Hurd: GNU

Hello, Madhu patel, le sam. 11 mars 2023 17:56:47 +0530, a ecrit: > can you please tell me the number of applicants for this project? We won't know that until the application frontend closes. Samuel

Re: GSoC'2023: Porting Rust to GNU/Hurd: GNU

hi Samuel. I have completed the tasks you mentioned. can you please tell me the number of applicants for this project? and what are my chances of getting selected? Thanks! On Fri, Mar 10, 2023 at 5:29 AM Samuel Thibault wrote: > Hello, > > Madhu patel, le jeu. 09 mars 2023 13:01:51 +0530, a ec

Re: GSoC'2023: Porting Rust to GNU/Hurd: GNU

Hello, Madhu patel, le jeu. 09 mars 2023 13:01:51 +0530, a ecrit: > I have gone through the page, and I meet some requirements as mentioned. I > have > good knowledge of C and am currently in the process of learning Rust. At the > moment, I am working on [1][1]. Can you recommend any other skills

Re: GSoC'2023: Porting Rust to GNU/Hurd: GNU

tial tasks I can work on during the application > period > > and attach them to my application. > > We have posted information on > https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ > > Samuel > [image: Mailtrack] <https://mailtrack.io

Re: GSoC'2023: Porting Rust to GNU/Hurd: GNU

Hello, Madhu patel, le jeu. 09 mars 2023 01:44:50 +0530, a ecrit: > Please suggest a few initial tasks I can work on during the application period > and attach them to my application. We have posted information on https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ Samuel

GSoC'2023: Porting Rust to GNU/Hurd: GNU

Hi, I'm interested in working on the project `Porting Rust to GNU/Hurd` in the GNU organization through GSoC'2023. I am Madhu Patel, a fourth-year B.Tech. student in Computer Science at IGDTUW, with a CGPA of 8.7/10. I have previously interned at Adobe India, Rabvik Innovations, and FM

Re: Applying to GSoC'23 to contribute to GNU/Hurd

p. > > We have collected the pointers on: > https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ > > Samuel >

Re: Applying to GSoC'23 to contribute to GNU/Hurd

Hello, Welcome! Venkaat Balaje, le ven. 03 mars 2023 17:05:25 +0530, a ecrit: >  I would be grateful if you could give me some pointers as to where I can > help. We have collected the pointers on: https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ Samuel

Applying to GSoC'23 to contribute to GNU/Hurd

Hello! My name is Venkaat and I am interested in contributing to GNU/Hurd as a part of GSoC'23 by helping port Rust to GNU/Hurd. I am a competent C Programmer,but I will have to learn Rust along the way. I would be grateful if you could give me some pointers as to where I can help. Venkaat

Re: [gnu-soc] GNU GSOC 2023 application

On Wed, Feb 8, 2023 at 2:45 PM Samuel Thibault wrote: > Actually, no: the rustc compiler itself cross-builds fine, it's libstd > that needs porting, and the gcc front-end uses the rustc libstd too. Is planning to use the upstream libstd, rather. Currently GCC Rust cannot even build libcore yet.

Re: [gnu-soc] GNU GSOC 2023 application

> Jose E. Marchesi, le mer. 08 févr. 2023 12:15:31 +0100, a ecrit: >> As a side note, have you heard of the GCC Rust front-end (under >> development) that has been recently added to GCC? > > Yes. > >> It may be relevant to the Hurd. > > Actually, no: the rustc compiler itself cross-builds fine, i

Re: [gnu-soc] GNU GSOC 2023 application

Jose E. Marchesi, le mer. 08 févr. 2023 12:15:31 +0100, a ecrit: > As a side note, have you heard of the GCC Rust front-end (under > development) that has been recently added to GCC? Yes. > It may be relevant to the Hurd. Actually, no: the rustc compiler itself cross-builds fine, it's libstd tha

Re: [gnu-soc] GNU GSOC 2023 application

then it will be self-hosted on GNU/Hurd. > > - A good level of C programming will be welcome to understand the > questions of ABI and the libc C functions being bound. > > Knowing the Rust language is not required: it can be learnt along the > way, this can be a good occasion. &g

Re: [gnu-soc] GNU GSOC 2023 application

> questions of ABI and the libc C functions being bound. > > Knowing the Rust language is not required: it can be learnt along the > way, this can be a good occasion. > > - [5]bug-hurd@gnu.org > - [6]https://darnassus.sceen.net/~hurd-web/commu

Re: [gnu-soc] GNU GSOC 2023 application

rstand the > questions of ABI and the libc C functions being bound. > > Knowing the Rust language is not required: it can be learnt along the > way, this can be a good occasion. > > - bug-hurd@gnu.org > - https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ > https://www.rust-lang.org/ > https://rustc-dev-guide.rust-lang.org/building/how-to-build-and-run.html > > Samuel > >

Re: [gnu-soc] GNU GSOC 2023 application

ll be welcome to understand the questions of ABI and the libc C functions being bound. Knowing the Rust language is not required: it can be learnt along the way, this can be a good occasion. - bug-hurd@gnu.org - https://darnassus.sceen.net/~hurd-web/community/gsoc/project_ideas/rust/ https://www.rust-lan

Re: [gnu-soc] GSoC org application 2019

Thomas Schwinge writes: > Hi Joan! > > On Wed, 13 Mar 2019 18:41:54 +0100, Joan Lledó > wrote: >> Missatge de Thomas Schwinge del dia dc., 13 >> de març 2019 a les 12:22: >> > Would anybody be available as a mentor for anything related to GNU Hurd, >> >> I'm considering it. > > Oh, great, than

Re: [gnu-soc] GSoC org application 2019

gt; >> > For GNU Hurd, please copy the stanza from >> > <https://www.gnu.org/software/soc-projects/ideas-2017.html>. >> >> How may I do it? I don't see any edit link > > Nothing for you to do there; Giuseppe or another GNU GSoC web pages > maintainer needs to do that. Sorry for the confusion. I've just updated it. Thanks, Giuseppe

Re: [gnu-soc] GSoC org application 2019

://www.gnu.org/software/soc-projects/ideas-2017.html>. > > How may I do it? I don't see any edit link Nothing for you to do there; Giuseppe or another GNU GSoC web pages maintainer needs to do that. Sorry for the confusion. Grüße Thomas

Re: [gnu-soc] GSoC org application 2019

Missatge de Thomas Schwinge del dia dc., 13 de març 2019 a les 19:42: > > https://www.gnu.org/software/soc-projects/ideas.html > > For GNU Hurd, please copy the stanza from > . How may I do it? I don't see any edit link

Re: [gnu-soc] GSoC org application 2019

Hi! On Mon, 21 Jan 2019 15:37:33 +0100, Giuseppe Scrivano wrote: > we need to check our ideas page. As a starting point I've used the same > page from the last year, some of them must be dropped. > > Could each project review the ideas page (if you still get 404 give it > some time to the serve

Re: [gnu-soc] GSoC org application 2019

Hello, Joan Lledó, le mer. 13 mars 2019 18:41:54 +0100, a ecrit: > Missatge de Thomas Schwinge del dia dc., 13 > de març 2019 a les 12:22: > > Would anybody be available as a mentor for anything related to GNU Hurd, > > I'm considering it. That'd be great :) > How much time would it take? do y

Re: [gnu-soc] GSoC org application 2019

Hi Joan! On Wed, 13 Mar 2019 18:41:54 +0100, Joan Lledó wrote: > Missatge de Thomas Schwinge del dia dc., 13 > de març 2019 a les 12:22: > > Would anybody be available as a mentor for anything related to GNU Hurd, > > I'm considering it. Oh, great, thanks! I'll thus request a link to our (som

Re: [gnu-soc] GSoC org application 2019

Missatge de Thomas Schwinge del dia dc., 13 de març 2019 a les 12:22: > Would anybody be available as a mentor for anything related to GNU Hurd, I'm considering it. How much time would it take? do you think it's possible to combine it with a full-time job?

Re: [gnu-soc] GSoC org application 2019

Hi! It's that time of the year again, Google Summer of Code: On Mon, 21 Jan 2019 15:37:33 +0100, Giuseppe Scrivano wrote: > jema...@gnu.org (Jose E. Marchesi) writes: > > > GNU is applying as usual this year. > > We will notify here with details. ..., and got accepted:

Re: Fwd: GSoC TCP/IP webpage edit patch

Samuel Thibault writes: > Hello, > > Thanks for the patch, I have pushed it. > > About wireless drivers, there used to be some pcmcia (pc-card) drivers, > but that's very old :) netdde doesn't include the wireless stack (even > if linux 2.6.26 used for netdde did have wireless drivers indeed). >

Re: Fwd: GSoC TCP/IP webpage edit patch

Hello, Thanks for the patch, I have pushed it. About wireless drivers, there used to be some pcmcia (pc-card) drivers, but that's very old :) netdde doesn't include the wireless stack (even if linux 2.6.26 used for netdde did have wireless drivers indeed). Better go with rump anyway. Samuel

Re: Fwd: GSoC TCP/IP webpage edit patch

Joan Lledó writes: > Hello, > >> However, lwip uses the netdde device drivers for wireless chips, >> which are old drivers from an old version of linux > > Does netdde provide drivers for any wireless card? I don't remember. > Anyway, there's no difference between lwip and pfinet here, both need

Fwd: GSoC TCP/IP webpage edit patch

Hello, > However, lwip uses the netdde device drivers for wireless chips, > which are old drivers from an old version of linux Does netdde provide drivers for any wireless card? I don't remember. Anyway, there's no difference between lwip and pfinet here, both need netdde for reaching a NIC, and

Re: GSoC TCP/IP webpage edit patch

>From 4dd72f771e28ce482027a3ff05c0b2a86b3cd7b5 Mon Sep 17 00:00:00 2001 From: Joshua Branson Date: Thu, 3 May 2018 09:53:04 -0400 Subject: [PATCH] * community/gsoc/project_ideas/tcp_ip_stack.mdwn I mentioned that lwip was recently ported to the hurd. --- community/gsoc/project_id

Re: GSoC TCP/IP webpage edit patch

Joan Lledó writes: > Hi, > >> However lwip does not provide device drivers for ethernet or wireless > chips. > > Mmm, that's true for wi-fi, but Ethernet is supported[1] and device drivers > are provided by netdde. Ahh ok. I'll apply a corrected version in a moment. At the moment I can't get i

Re: GSoC TCP/IP webpage edit patch

Hi, > However lwip does not provide device drivers for ethernet or wireless chips. Mmm, that's true for wi-fi, but Ethernet is supported[1] and device drivers are provided by netdde. [1] https://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/lwip/port/netif/hurdethif.c Mis

GSoC TCP/IP webpage edit patch

>From 6fe963a6ed30de1b3162bf4a767478b6a161fb1c Mon Sep 17 00:00:00 2001 From: Joshua Branson Date: Thu, 3 May 2018 09:53:04 -0400 Subject: [PATCH] * community/gsoc/project_ideas/tcp_ip_stack.mdwn I mentioned that lwip was recently ported to the hurd. --- community/gsoc/project_id

Re: I mentioned that lwip was ported to the hurd on the tcp ip gsoc page

On Fri, 2018-05-04 at 17:08 -0400, Joshua Branson wrote: > Hello, > > I noticed that the tcp/ip webpage for the Hurd does not mention that > we > already have a port of the lwip tcp/ip stack. This patch briefly > explains it. Hi, a small typo: pfinit -> pfinet :) and ... device drivers in use

I mentioned that lwip was ported to the hurd on the tcp ip gsoc page

400 Subject: [PATCH] * community/gsoc/project_ideas/tcp_ip_stack.mdwn I mentioned that lwip was recently ported to the hurd. --- community/gsoc/project_ideas/tcp_ip_stack.mdwn | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/commun

Re: GSoC 2018

Hi! On Wed, 28 Feb 2018 12:39:15 +0100, I wrote: > I did register with GNU to be a mentor so that I get access > to the GSoC web page, and I'll check from time to time if any > Hurd-related applications come in. There are none. Grüße Thomas

GSoC 2018 (was: GSoC 2018: Microkernel devroom)

Hi! On Tue, 9 Jan 2018 22:59:46 +0100, Samuel Thibault wrote: > Jakub Jermář, on ven. 05 janv. 2018 08:57:02 +0100, wrote: > > another year of GSoC started and the mentor organization application > > period is on until January 23 [0]. The question on the table is: would &

Re: GSoC 2018: Microkernel devroom

Hello, Jakub Jermář, on ven. 05 janv. 2018 08:57:02 +0100, wrote: > another year of GSoC started and the mentor organization application > period is on until January 23 [0]. The question on the table is: would > Hurd like to participate under the Microkernel devroom [1] as it di

GSoC 2018: Microkernel devroom

Dear Hurd developers, another year of GSoC started and the mentor organization application period is on until January 23 [0]. The question on the table is: would Hurd like to participate under the Microkernel devroom [1] as it did (very successfully) last year? Jakub [0] https

Re: [GSoC 2017] LwIP translator

On Sat, Aug 26, 2017 at 09:38:39AM +0200, Joan Lledó wrote: > The Google Summer of Code is about to end and it is time to summarize my work > on the lwip translator. Excellent work, one of the best GSoC projects I've seen. -- Richard Braun

[GSoC 2017] LwIP translator

: http://darnassus.sceen.net/~jlledom/en/ Finally, I would like to Thank Justus and all the Hurd developers for their help and feedback during my GSoC. It has been an enriching experience by which I learnt a lot about networking and OS programming, and I'll be glad to continue to work on f

Re: [GSoC 2017] Number fo sockets

> Instead of a linked list, how about using a dynamic array? > > https://en.wikipedia.org/wiki/Dynamic_array > > This would give you constant-time lookups, amortized constant time > insertions and deletions, and better data locality and cache behavior. > > What do you think? It's a good idea, in

Re: [GSoC 2017] Number fo sockets

Hi, Joan Lledó writes: > As I mentioned in my previous post about ioctl operations[1], LwIP > establishes a maximum limit of sockets, which is a big problem for a > system like the Hurd. Now I've finished all tasks in my initial > proposal, I thought it was a good idea to spend some time studyin

Re: [GSoC 2017] Number fo sockets

Joan Lledó writes: > They are using the 2-clause BSD license, is OK to apply the patch with > that license? The 2-clause BSD license is OK for my lwip_poll patches. I would prefer that you squash the bug fixes into the original patch. pgpqvTWEQkK0K.pgp Description: PGP signature

Re: [GSoC 2017] Number fo sockets

> > I meant the S_io_select and S_io_select_timeout functions should > be able to return without replying to the RPC, if the socket is > not immediately ready. They would instead put the RPC in a > queue, and if the socket later becomes ready, another thread > would remove the RPC from the queue a

Re: [GSoC 2017] Number fo sockets

Joan Lledó writes: > I've got a question about your patch. Why did you say io_select > without a thread per socket would require a > different solution? I'm studying the patch b/c I'd like to send it to > lwip maintainers, and don't find the problem. I meant the S_io_select and S_io_select_timeo

Re: [GSoC 2017] Number fo sockets

Hello again Kalle, I've got a question about your patch. Why did you say io_select without a thread per socket would require a different solution? I'm studying the patch b/c I'd like to send it to lwip maintainers, and don't find the problem. 2017-08-15 9:50 GMT+02:00 Joan Lledó : > Hello Kalle,

Re: [GSoC 2017] Number fo sockets

Hello Kalle, I've applied and tested your patches and seem to be working fine. The translator is now using lwip_poll() instead of lwip_select(). I've pushed the changes to github. Thank you very much.

Re: [GSoC 2017] Number fo sockets

Joan Lledó writes: > About your patches, which lwip version are you using? Commit b82396f361ec9ce45cf0e997eb7ee5cc5aac12ec from your lwip-hurd repository. (I noticed the CRLFs because they ended up in the diff.) > Will you send them to the lwip patch tracker? I don't intend to, because I have

Re: [GSoC 2017] Number fo sockets

> Too bad there is no lwip_poll function. > Might the LwIP folks be amenable to adding one? Yes, they talked about that in their mailing list[1]. > Your size calculations seem wrong. > glibc defines fd_mask = __fd_mask = long int. > FD_SETSIZE is the number of bits that fit in fd_set. > But then

Re: [GSoC 2017] Number for sockets

Kalle Olavi Niemitalo writes: > The following builds OK (also with LWIP_POLL=1 if you add > #include to cc.h) but I have not run it. Fixed a couple of bugs. Still not run. commit a5b178d9111d8bbc34f9a820cda56e20343fb2b0 Author: Kalle Olavi Niemitalo AuthorDate: 2017-08-13 14:43:29 +0300

Re: [GSoC 2017] Number fo sockets

The handling of LWIP_SOCKET_OFFSET looks inconsistent. Suppose LWIP_SOCKET_OFFSET is 100 and LWIP_SOCKET_OPEN_COUNT is defined. The first alloc_socket call sets newsock->count = 100 and returns 100. However, if get_socket(100) is then called, it first subtracts LWIP_SOCKET_OFFSET from s, resultin

Re: [GSoC 2017] Number fo sockets

Kalle Olavi Niemitalo writes: > I wonder how hard it would be to implement those select ops in > the translator without hogging a thread for each. To clarify: if one thread in a program calls select on an fd_set that lists ten sockets, then glibc sends ten io_select requests before it waits for

Re: [GSoC 2017] Number for sockets

Kalle Olavi Niemitalo writes: > The implementation effort might be 4 hours, not including testing > and publication. That was very accurate. The following builds OK (also with LWIP_POLL=1 if you add #include to cc.h) but I have not run it. Why do the files have CRLF in the lwip-hurd repositor

Re: [GSoC 2017] Number for sockets

Svante Signell writes: > How much effort is it to implement lwip_poll? lwip_select constructs a struct lwip_select_cb on the stack and adds that to the global linked list select_cb_list. event_callback searches the list for structures that relate to a particular socket, and wakes up the correspo

Re: [GSoC 2017] Number for sockets

On Sat, 2017-08-12 at 19:24 +0300, Kalle Olavi Niemitalo wrote: > Joan Lledó writes: > > > Since Glibc calls the io_select() operation each time the user > > calls send() or recv(), in practice such sockets are just > > unusable. > > Too bad there is no lwip_poll function. > Might the LwIP folks

Re: [GSoC 2017] Number fo sockets

Joan Lledó writes: > Since Glibc calls the io_select() operation each time the user > calls send() or recv(), in practice such sockets are just > unusable. Too bad there is no lwip_poll function. Might the LwIP folks be amenable to adding one? > [3] > https://github.com/jlledom/lwip-hurd/commi

[GSoC 2017] Number fo sockets

As I mentioned in my previous post about ioctl operations[1], LwIP establishes a maximum limit of sockets, which is a big problem for a system like the Hurd. Now I've finished all tasks in my initial proposal, I thought it was a good idea to spend some time studying this issue and trying to find a

Re: [GSoC 2017] Point-to-point

Hello, Congrats on the continuous good work :) Joan Lledó, on dim. 06 août 2017 09:22:49 +0200, wrote: > Currently, when the > user adds --peer option to the command line, pfinet just assigns its > value to an internal variable in the given interface, but it doesn't > seem to be using it afterwar

Re: [GSoC 2017] Point-to-point

2017-08-06 19:03 GMT+02:00 Justus Winter : > Joan Lledó writes: > >> The last item in my initial TODO list was implementing the --peer >> option available in pfinet. This week I've been working on it and it's >> now done, so I can say the LwIP translator is now able to replace >> pfinet. > > And i

Re: [GSoC 2017] Point-to-point

Joan Lledó writes: > The last item in my initial TODO list was implementing the --peer > option available in pfinet. This week I've been working on it and it's > now done, so I can say the LwIP translator is now able to replace > pfinet. And indeed, I'm using lwip on my development box right now

[GSoC 2017] Point-to-point

The last item in my initial TODO list was implementing the --peer option available in pfinet. This week I've been working on it and it's now done, so I can say the LwIP translator is now able to replace pfinet. The --peer option is provided by pfinet for setting the peer's address in a point-to-po

[GSoC 2017] Misc

At this time, the only functionality provided by pfinet and pending to be implemented in the LwIP translator is the --peer options, everything else is done. From now on, most of the work will consist on polishing and fixing bugs, so I'll probably talk about many different topics in each post. The

[GSoC 2017] Ifupdown

When we tried to configure the stack with ifupdown during the boot we found two problems. Fist, the system failed to find the loopback interface to give it an address, and second, the DHCP client wasn't able to get the MAC address of the interfaces it was trying to configure. For doing these action

Re: [GSoC 2017] ioctl operations

Joan Lledó, on sam. 15 juil. 2017 19:23:53 +0200, wrote: > installed on. Thus, pfinet was returning EPERM because it was > installed on /servers/socket/2, where my user wasn't the owner, while > lwip was installed on a file in my home. Heh, yes, that's one of the "surprising" advantages of running

[GSoC 2017] ioctl operations

One of the pending tasks in my TODO since the beginning of the project was implementing the operations of the iioctl interface and other interfaces if needed. The iioctl interface is the responsible for servicing the ioctl requests[1] that have a socket as first parameter. Besides, pfinet also impl

Re: [GSoC 2017] Multithreading

Hello, Joan Lledó, on dim. 09 juil. 2017 22:18:05 +0200, wrote: > After finishing with IPv6, I spent the last week fixing some bugs, > mainly those related with multithreading. Nice work, hoping you didn't get too much headache with debugging multithreading issues :) Samuel

Re: [GSoC 2017] Multithreading

2017-07-10 10:30 GMT+02:00 Richard Braun : > On Sun, Jul 09, 2017 at 10:18:05PM +0200, Joan Lledó wrote: >> However, after all the pending threads still were not being canceled. >> The problem here was that the standard function where the threads >> where blocked on, pthread_cond_wait(), didn't res

Re: [GSoC 2017] Multithreading

On Sun, Jul 09, 2017 at 10:18:05PM +0200, Joan Lledó wrote: > However, after all the pending threads still were not being canceled. > The problem here was that the standard function where the threads > where blocked on, pthread_cond_wait(), didn't respond to cancel > requests from hurd_thread_cance

[GSoC 2017] Multithreading

After finishing with IPv6, I spent the last week fixing some bugs, mainly those related with multithreading. This is an issue I never thought on until now, and turned up to be a real mess. I shall give you a summary. First, LwIP has a main thread called "tcpip_thread" where the stack is actually r

Re: [GSoC 2017] IPv6

On 07/07/17 03:19, Samuel Thibault wrote: Hello, Nice progress :) Joan Lledó, on dim. 02 juil. 2017 10:29:33 +0200, wrote: the stack offers the option of using DAD[2] to check if the address is already in use. This isn't likely to happen, since the interface identifier is based on the link add

Re: [GSoC 2017] IPv6

Hello, Nice progress :) Joan Lledó, on dim. 02 juil. 2017 10:29:33 +0200, wrote: > the stack offers the option of > using DAD[2] to check if the address is already in use. This isn't > likely to happen, since the interface identifier is based on the link > address, which should be unique, but I l

[GSoC 2017] IPv6

Adding support for IPv6 has took most of my time this week, and part of the previous one, but it's done and now I can say the LwIP server supports IPv6 :). Specifically, these items are implemented: - Automatic assignation of link-local addresses. - Automatic auto-configuration with SLAAC. - Manua

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

On Thu, Jun 29, 2017 at 7:13 AM, Joan Lledó wrote: > Hello Brent, > > Thanks for your interest in my GSoC. I didn't know the tools you > propose and think that everything that moves us towards using > standards is good. What I believe is that probably such a development

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

Hello Brent, Thanks for your interest in my GSoC. I didn't know the tools you propose and think that everything that moves us towards using standards is good. What I believe is that probably such a development should be done by another developer more experienced than me, besides, until the p

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

"Brent W. Baccala" writes: > Joan - > > Thank you for your work on this. I haven't commented on it until now, > partly because of some email problems, and partly because I haven't been > working on Hurd for the last six months or so. > > On Mon, Jun 26, 2017 at 7:28 AM, Joan Lledó > wrote: > >>

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

Implementing this is a lot of work, and I'm not suggesting it for part of this GSoC project, but I want to document and discuss what kind of API our network translators should ultimately support. Our options, as I see it, are: 1. some kind of non-standard, Hurd-specific API t

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

0.0.0/0 is really not a common thing :) >> >>> It's interesting to note that the example code[2] LwIP maintainers >>> provide is wrong as well. >> >> It'll probably be useful to them to at least report the issue or even a >> fix :) > > I know, an

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

ing :) > >> It's interesting to note that the example code[2] LwIP maintainers >> provide is wrong as well. > > It'll probably be useful to them to at least report the issue or even a > fix :) I know, and this is not the first issue I find, but I wouldn&#

Re: [GSoC 2017] Support for fsysopts and multiple interfaces

Hello, Joan Lledó, on lun. 26 juin 2017 13:28:47 +0200, wrote: > As a curious factor, it's worth mentioning that pfinet had > a memory leak that I could manage to fix. Could you provide a patch so we can benefit from it already? :) > Once the configuration from the command line is added, I check

[GSoC 2017] Support for fsysopts and multiple interfaces

all the work I've been able to do in the first week, when I still had to combine my GSoC with my exams for the UOC. Fortunately, from June 19th I'm working full-time on this project. I started this last week adding support for fsysopts, that mainly consisted on making some changes in the

Re: [GSoC 2017] Work done so far

2017-06-06 19:23 GMT+02:00 Justus Winter : > Hi :) > > Joan Lledó writes: > >> It's useful to make a review of the work done in the last months and >> list some of the problems arisen during this period. > > Thank you for your nice writeups, they are appreciated :) > >> The process of writing the

  1   2   3   4   5   6   7   8   >