From: "Jan (janneke) Nieuwenhuizen" <janneke@gnu.org>
To: 41855@debbugs.gnu.org
Subject: bug#41855: [PATCH 0/2] hurd-boot: Cleanups: Remove MAKEDEV, then use setxattr (on the Hurd).
Date: Sun, 14 Jun 2020 18:54:30 +0200 [thread overview]
Message-ID: <20200614165430.3411-1-janneke@gnu.org> (raw)
From: Jan Nieuwenhuizen <janneke@gnu.org>
Hi!
Several variants of these patches were present on wip-hurd-vm before.
Currently, we are running MAKEDEV from activation, and thus need hurd, bash,
coreutils and sed in PATH.
The first patch replaces that with scheme code, which seems a no-brainer to
me. Then we only need hurd in PATH for settrans and gettrans.
The second patch then switches to using setxattr instead of settrans; alas we
still need gettrans as getxattr behaves "funny" on translated nodes. I
suppose that would be a question for the bug-hurd?
Greetings,
Janneke
Jan (janneke) Nieuwenhuizen (2):
hurd-boot: Create individual translators instead of running MAKEDEV.
hurd-boot: Use 'setxattr' instead of invoking settrans.
gnu/build/hurd-boot.scm | 172 +++++++++++++++++++++++++++++-----------
gnu/system.scm | 1 +
2 files changed, 126 insertions(+), 47 deletions(-)
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next reply other threads:[~2020-06-14 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 16:54 Jan (janneke) Nieuwenhuizen [this message]
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
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=20200614165430.3411-1-janneke@gnu.org \
--to=janneke@gnu.org \
--cc=41855@debbugs.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.