all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Jan \(janneke\) Nieuwenhuizen" <janneke@gnu.org>
Cc: 41855@debbugs.gnu.org
Subject: bug#41855: [PATCH 2/2] hurd-boot: Use 'setxattr' instead of invoking settrans.
Date: Mon, 15 Jun 2020 22:00:49 +0200	[thread overview]
Message-ID: <87a714yu8e.fsf@gnu.org> (raw)
In-Reply-To: <20200614165649.3496-2-janneke@gnu.org> (Jan Nieuwenhuizen's message of "Sun, 14 Jun 2020 18:56:49 +0200")

"Jan (janneke) Nieuwenhuizen" <janneke@gnu.org> skribis:

> Note: Using `getxattr' on the Hurd instead of running showtrans does not
> work (yet?).

How does it not work?  :-)

> * gnu/build/hurd-boot.scm (setup-translator): Use 'setxattr' instead of
> invoking settrans.
> * gnu/system.scm (hurd-multiboot-modules): Add --x-xattr-translator-records to
> enable xattr-embebbing of translators.
                   ^
Typo.

Otherwise LGTM!

Ludo’.




  reply	other threads:[~2020-06-15 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14 16:54 bug#41855: [PATCH 0/2] hurd-boot: Cleanups: Remove MAKEDEV, then use setxattr (on the Hurd) Jan (janneke) Nieuwenhuizen
2020-06-14 16:56 ` bug#41855: [PATCH 1/2] hurd-boot: Create individual translators instead of running MAKEDEV Jan (janneke) Nieuwenhuizen
2020-06-14 16:56   ` bug#41855: [PATCH 2/2] hurd-boot: Use 'setxattr' instead of invoking settrans Jan (janneke) Nieuwenhuizen
2020-06-15 20:00     ` Ludovic Courtès [this message]
2020-06-16 21:12       ` [bug#41855] " Jan Nieuwenhuizen
2020-06-15 19:54   ` bug#41855: [PATCH 1/2] hurd-boot: Create individual translators instead of running MAKEDEV Ludovic Courtès
2020-06-16 21:15     ` [bug#41855] " Jan Nieuwenhuizen
2020-06-19  8:03       ` Ludovic Courtès
2020-06-19  8:44         ` bug#41855: " Jan Nieuwenhuizen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a714yu8e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41855@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.