From: Samuel Thibault <samuel.thibault@gnu.org>
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>, GNU Hurd <bug-hurd@gnu.org>,
Justus Winter <4winter@informatik.uni-hamburg.de>
Subject: Re: [GSoC] Guix + Hurd continuation
Date: Thu, 2 Jul 2015 15:42:46 +0200 [thread overview]
Message-ID: <20150702134246.GC3985@type.bordeaux.inria.fr> (raw)
In-Reply-To: <CAFtzXzPTSTkB-_ZApS6-02ULpKL5ZAaEGqBKOMV6Vm50-nyyUw@mail.gmail.com>
Manolis Ragkousis, le Thu 02 Jul 2015 16:38:54 +0300, a écrit :
> > 4. Instead of sitting idle watching build logs ;-), it Would Be Nice™
> > to implement the ‘mount’ and ‘umount’ functions for GNU/Hurd in
> > libc, with support for MS_BIND using /hurd/firmlink.
> > Of course libc hacking can be quite involved. So ideally Samuel,
> > Thomas, and others would give you detailed guidance and/or hack
> > power. What do people think?
>
> Yes, I think now it's the right time to start this. Expect questions
> as I work on this. :-)
> Meanwhile if the hurd guys have something to point out, please do. :-)
Note that this is listed on the "contributing" page of the wiki, with a
link to the glibc open_issues page describing a bit more details.
> > Another can of worms I forgot to mention is <hurd/paths.h>, which
> > assumes that translators live in /hurd, whereas we’ll rather have them
> > in /gnu/store/…/hurd.
>
> A question. Isn't it possible, that this will break the Hurd expected
> behavior?
The Hurd is supposed to be flexible, so this is supposed to work. If not
then that needs to be fixed, not the way you're doing things :)
Samuel
prev parent reply other threads:[~2015-07-02 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 9:12 [GSoC] Guix + Hurd continuation Ludovic Courtès
2015-07-02 9:33 ` Ludovic Courtès
2015-07-02 9:57 ` Justus Winter
2015-07-02 12:14 ` Ludovic Courtès
2015-07-02 14:00 ` Justus Winter
2015-07-02 13:38 ` Manolis Ragkousis
2015-07-02 13:42 ` Samuel Thibault [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150702134246.GC3985@type.bordeaux.inria.fr \
--to=samuel.thibault@gnu.org \
--cc=4winter@informatik.uni-hamburg.de \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=manolis837@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).