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 > some experience working with c

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 libr

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 for my GSOC application. Would > you

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 exercise or shall I work on the pr

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 working towards a thesis > on eBPF which incl

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 identify my strength and > weaknesses : >

Re: GSOC -23 contrubution on gnu hurd

Hello, CHANDRA CHURD BHARATI, le mer. 22 mars 2023 11:52:17 +0530, a ecrit: > 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 ,

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 ones seem like fun to yo

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

Hi, 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] . Can you recommend any other skills

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

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_ideas/tcp_ip_stack

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

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

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 did > (very successfu

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

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

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

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

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

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

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 > should be done by anothe

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 proper

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

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: > I've advanced in several fronts during the l

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

2017-06-27 13:53 GMT+02:00 Joan Lledó : > Hi! > > 2017-06-27 1:19 GMT+02:00 Samuel Thibault : >> 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

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

Hi! 2017-06-27 1:19 GMT+02:00 Samuel Thibault : > 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? :) The l

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

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

Re: [GSoC 2017] Work done so far

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 sockets and I/O operations have been quite > straightfor

Re: GSoC 2017: Porting LwIP to the Hurd

Hi! On Fri, 17 Mar 2017 08:31:37 +0100, Joan Lledó wrote: > My name is Joan Lledó, I'm in the last year of my degree in CS at the > Open University of Catalonia[1]. I'm interested in OS programming and, > for now, I have only read theory and have made university exercises in > ths field. That's w

Re: GSoC 2017: Porting LwIP to the Hurd

Hello, Welcome on board ! That's a very promising project proposal :D Joan Lledó, on ven. 17 mars 2017 08:31:37 +0100, wrote: > I think it's a feasible GSoC project to implement the same > functionality that pfinet ofers now, but I'd like to know your > opinion. Perhaps not everything, but prob

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

issue with the > runtime that occurs, are there any potentials notes on it so far? Is > Ian Lance Taylor still active on the project as well? >   > From: Svante Signell > Sent: Saturday, March 4, 2017 6:52 PM > To: Samuel Thibault; Louis Jenkins > Cc: bug-hurd@gnu.org; summer-o

RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

: bug-hurd@gnu.org<mailto:bug-hurd@gnu.org>; summer-of-c...@gnu.org<mailto:summer-of-c...@gnu.org> Subject: Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns On Sun, 2017-03-05 at 00:44 +0100, Samuel Thibault wrote: > Louis Jenkins, on sam. 04 mars 2017 23:16:30 +,

RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

c...@gnu.org<mailto:summer-of-c...@gnu.org>; bug-hurd@gnu.org<mailto:bug-hurd@gnu.org> Subject: Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns Hello, Louis Jenkins, on sam. 04 mars 2017 22:38:06 +, wrote: > As for Svante Signell, I was googling his name a

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

On Sun, 2017-03-05 at 00:44 +0100, Samuel Thibault wrote: > Louis Jenkins, on sam. 04 mars 2017 23:16:30 +, wrote: > > One more thing: I see it is now CC’d, but would he be able to see > > the previous > > messages, or should I ask directly there? > > Google for "bug-hurd", and you'll find the

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Louis Jenkins, on sam. 04 mars 2017 23:16:30 +, wrote: > One more thing: I see it is now CC’d, but would he be able to see the previous > messages, or should I ask directly there? Google for "bug-hurd", and you'll find the mailing list archives. Samuel

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Hello, Louis Jenkins, on sam. 04 mars 2017 22:38:06 +, wrote: > As for Svante Signell, I was googling his name a bit and the most relevant I > could find was for [1]svante.sign...@gmail.com would that be his appropriate > email address, or is there a way to search or communicate through the ma

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Louis Jenkins, on ven. 03 mars 2017 20:20:20 +, wrote: > However, again, before I delve further I would like to know first if it is > still active, or can potentially be restarted. So, assuming that this is about porting Go to the GNU/Hurd system, you need to be aware that some work has been d

Re: GSoC mentors

Hi! On Fri, 10 Feb 2017 14:47:31 +0100, Justus Winter wrote: > Thomas Schwinge writes: > > > Who will be available this year as a mentor for GSoC? > > Me. Danke! :-) So, you (as well as everyone else who'd like to be a mentor; but please let us know) please register according to the instruc

Re: GSoC mentors

Thomas Schwinge writes: > Who will be available this year as a mentor for GSoC? Me. Justus signature.asc Description: PGP signature

Re: [GSoC] Porting GuixSD to GNU/Hurd Update

Hello Manolis, Manolis Ragkousis skribis: > On Hurd though, because of the lack of mount(), the above could not > work. But with the help of my libhurdutil library, which I wrote at the > beginning of this project, I created 2 wrappers inside > nix/libutil/call.(hh.cc) for mount() and umount2(),

Re: [GSoC] Implement xattr Support Update

On Fri, Aug 19, 2016 at 11:06:32AM +0800, Shengyu Zhang wrote: > GSoC is coming to an end. It is time to report my work during this summer. I've just completed the evaluation, everything is in order, and we'll have more time in September to really dive into the code, finish the review and merge it

Re: [GSoC] Porting GuixSD to GNU/Hurd Update

Manolis Ragkousis, on Sat 20 Aug 2016 21:31:43 +0300, wrote: > On 08/20/16 20:47, Samuel Thibault wrote: > > Ok, but the Linux part uses glibc 2.22, and you'd rather use it, right? > > Of course :-) Ok, I have pushed it, along the debian glibc 2.22 fixup patches, it seems to be working fine with

Re: [GSoC] Porting GuixSD to GNU/Hurd Update

On 08/20/16 20:47, Samuel Thibault wrote: > Ok, but the Linux part uses glibc 2.22, and you'd rather use it, right? Of course :-)

Re: [GSoC] Porting GuixSD to GNU/Hurd Update

Manolis Ragkousis, on Sat 20 Aug 2016 20:42:25 +0300, wrote: > Actually the Hurd part of Guix uses 2.19 as it is in > ftp://alpha.gnu.org/gnu/hurd/ > > The glibc tarballs use 2.19 as their version, which is the one I am > using as the version in our glibc/hurd recipe. Ok, but the Linux part uses

Re: [GSoC] Porting GuixSD to GNU/Hurd Update

Hey Samuel, Actually the Hurd part of Guix uses 2.19 as it is in ftp://alpha.gnu.org/gnu/hurd/ The glibc tarballs use 2.19 as their version, which is the one I am using as the version in our glibc/hurd recipe. Check (gnu packages base) glibc/hurd. Manolis On 08/20/16 19:24, Samuel Thibault wro

Re: [GSoC] Porting GuixSD to GNU/Hurd Update

Hello, Which glibc version is guix based on? It's very high time we upgrade our glibc repository, because we see people contribute patch against it and it makes use rebase the work in downstreams. I'd thus say we should make our glibc repository based on the minimum version used by the supported

Re: [GSoC] Porting GuixSD to GNU/Hurd Update 1

Hi Manolis! Manolis Ragkousis skribis: > We already knew that the guix-daemon was not working properly on the > Hurd. I looked more into it and I found that if you do a build with > Guix and it fails, and then you retry again, the next one will create a > new build directory in /tmp/ as it shou

Re: GSoC rejection

Hello, Vasantha Ganesh K, on Fri 22 Apr 2016 22:39:00 +0100, wrote: > My proposal for GSoC 2016 got rejected. Can you please tell me why my > proposal got rejected so that I can work on my pitfalls. Thanks in advance. It was not easy to decide. In your case, the valgrind project would be very w

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hi, Quoting Manolis Ragkousis (2016-03-24 14:55:31) > On 03/24/16 15:22, Ludovic Courtès wrote: > >>> The main question is whether you should implement build isolation in > >>> guix-daemon, in which case that would leave little time for the GuixSD > >>> parts. I think I would rather let you focus

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hey On 03/24/16 15:22, Ludovic Courtès wrote: > So, let’s say PID isolation will be optional, and we can always adjust > later on. Sounds good? > > Manolis, make sure to read about how the various Hurd servers provides > these parts of POSIX personality: file systems, UIDs, PIDs, networking, > a

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hi Justus, Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > Quoting Ludovic Courtès (2016-03-23 14:40:38) >> > 2. The Project >> > >> > The project consists of four main stages >> > >> > 1. Modify Guix so it will be able to create and mount the file-system >> > needed to boot into a

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Quoting Manolis Ragkousis (2016-03-24 13:36:04) > > Hmmm, so one still needs a filesystem, right? That's going to be a > > bit tricky too, since whatever tool you use for that purpose, it > > surely does not support creating hurdish passive translator records. > > Without passive translator record

Re: [GSoC] Porting GuixSD to GNU Hurd draft

On 03/24/16 13:38, Justus Winter wrote: > Otoh if we could properly build packages, we could provide the > substitutes, so people could try Guix on the Hurd without going > through the 12h+ bootstrap procedure. Here the problem is not isolation but the fact that we don't have a substitutes server.

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Quoting Manolis Ragkousis (2016-03-24 12:18:25) > >>> The project consists of four main stages > >>> > >>> 1. Modify Guix so it will be able to create and mount the file-system > >>> needed to boot into a system with Hurd at its core. > >>> 2. Modify Guix so it can produce a working image, while

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hello Justus, Hello Ludo On 03/23/16 18:55, Justus Winter wrote: > Quoting Ludovic Courtès (2016-03-23 14:40:38) >>> 2. The Project >>> >>> The project consists of four main stages >>> >>> 1. Modify Guix so it will be able to create and mount the file-system >>> needed to boot into a system with

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hi, Quoting Ludovic Courtès (2016-03-23 14:40:38) > > 2. The Project > > > > The project consists of four main stages > > > > 1. Modify Guix so it will be able to create and mount the file-system > > needed to boot into a system with Hurd at its core. > > 2. Modify Guix so it can produce a worki

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hello! Manolis Ragkousis skribis: > Although I have uploaded and shared my draft to the GSoC website, I am > also resending it to the lists as per Ludovic's instruction. Yeah, the GSoC website makes it possible to provide a link to a text file, so let’s do that instead of using their SaaSS. >

Re: [GSoC] Porting GuixSD to GNU Hurd draft

Hello, Manolis Ragkousis, on Mon 21 Mar 2016 14:09:36 +0200, wrote: > Although I have uploaded and shared my draft to the GSoC website, I am > also resending it to the lists as per Ludovic's instruction. Looks very promising :) Samuel

Re: GSoC 2016 proposal

On Sun, Mar 13, 2016 at 11:40:45AM +, Vasantha Ganesh K wrote: > Hello Braun, >   Thanks for your attention. I'll tone the next draft down and make it a > little more formal. No you didn't get it. I was meaning that your enthusiasm makes you say plain wrong things like "the Hurd can scale wel

Re: GSoC 2016 proposal

On Sat, Mar 12, 2016 at 06:51:40AM +, Vasantha Ganesh K wrote: >   Please review my GSoC proposal that I have attached with this mail. I know > its rough, please send some suggestions. > The fact that GNU Hurd can scale well because of its architecture and its a > part of GNU project serve

Re: GSoC ideas

Manolis Ragkousis skribis: > On 03/02/16 23:31, Ludovic Courtès wrote: [...] >> Other options include calling out to the ‘settrans’ command (inelegant >> IMO), writing Guile bindings for some of the Hurd libraries, and/or some >> sort of a MiG in Scheme (neat but takes some time!). > > We could

Re: GSoC ideas

Hey On 03/02/16 23:31, Ludovic Courtès wrote: > Do you have examples of GNU/Linux uses that would make no sense? > After a quick look in mount's man page I think that maybe Roland was referring to some flags (like relatime for example) that when passed to mount, expect the Linux kernel to handle

Re: GSoC ideas

Ludovic Courtès, on Wed 02 Mar 2016 22:31:41 +0100, wrote: > Samuel Thibault skribis: > > It can both help and hurt. Roland's concern is that we will probably not > > want to provide a mount() that behaves like Linux, because in some cases > > it may just not even make sense. So the "ported" softw

Re: GSoC ideas

Samuel Thibault skribis: > Ludovic Courtès, on Wed 02 Mar 2016 11:09:28 +0100, wrote: >> Manolis Ragkousis skribis: >> > 1) Merge wip-hurd branch. >> > 2) Make the daemon handle chroot builds on the Hurd. >> > Note here that on the Hurd, one does not need to be root to achieve >> > isolation, so

Re: GSoC ideas

Ludovic Courtès, on Wed 02 Mar 2016 11:09:28 +0100, wrote: > Manolis Ragkousis skribis: > > 1) Merge wip-hurd branch. > > 2) Make the daemon handle chroot builds on the Hurd. > > Note here that on the Hurd, one does not need to be root to achieve > > isolation, so I should change the daemon to use

Re: GSoC ideas

Hi! I realize I hadn’t responded to Manolis. Another +1 from me! Some random comments: Manolis Ragkousis skribis: > Before May: > > 1) Merge wip-hurd branch. > 2) Make the daemon handle chroot builds on the Hurd. > Note here that on the Hurd, one does not need to be root to achieve > isolatio

Re: GSoC ideas

On Sun, Feb 28, 2016 at 11:12:25PM +0100, Samuel Thibault wrote: > Just sending my big +1 on this project :) Same here. I'd like to note that I'm personally pushing so that we have less students but with better projects. This one definitely fits. -- Richard Braun

Re: GSoC ideas

Hello, Just sending my big +1 on this project :) Samuel

Re: GSoC ideas

Andreas Enge writes: > On Thu, Feb 11, 2016 at 01:46:30PM +0200, Manolis Ragkousis wrote: >> As I am still a student I would like to suggest continuing the project >> of porting Guix to GNU/Hurd in this GSoC as well, with the objective of >> having a working GuixSD/Hurd by the end of the summer.

Re: GSoC ideas

Manolis Ragkousis writes: > Hello everyone, > > As I am still a student I would like to suggest continuing the project > of porting Guix to GNU/Hurd in this GSoC as well, with the objective of > having a working GuixSD/Hurd by the end of the summer. > > After discussions with Justus and Samuel in

Re: GSoC ideas

On Thu, Feb 11, 2016 at 01:46:30PM +0200, Manolis Ragkousis wrote: > As I am still a student I would like to suggest continuing the project > of porting Guix to GNU/Hurd in this GSoC as well, with the objective of > having a working GuixSD/Hurd by the end of the summer. Sounds great, I hope it wil

Re: GSoC ideas

Hello everyone, As I am still a student I would like to suggest continuing the project of porting Guix to GNU/Hurd in this GSoC as well, with the objective of having a working GuixSD/Hurd by the end of the summer. After discussions with Justus and Samuel in FOSDEM about the Guix-Hurd port I am st

Re: GSoC report: Physical memory management

On Sat, Jan 02, 2016 at 12:01:20AM +0100, Flávio Cruz wrote: > Cool stuff! Can the branch be actively used or is it still too incomplete? It should be usable as it is, but I still have to polish a few things and I'll make a debian package for some stress testing on one of our public virtual machin

  1   2   3   4   5   >