unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, bug-hurd@gnu.org
Subject: Re: Feeble attempt at using xattr gnu.translator
Date: Mon, 11 May 2020 10:42:08 +0200	[thread overview]
Message-ID: <20200511084208.tnjdat5bofcgsxth@function> (raw)
In-Reply-To: <87zhaej2fi.fsf@gnu.org>

Jan Nieuwenhuizen, le lun. 11 mai 2020 10:33:53 +0200, a ecrit:
>    gnu.translator	empty if no passive translator
> 			translator and arguments: "/hurd/foo\0arg1\0arg2\0"
> 
> ah...so there's a nice hack (way??) to also pass arguments...

? It's not hack, it's how it's passed on the process main() stack anyway.

> diskfs_S_file_set_translator (struct protid *cred,
> [...]
>   if (passivelen && passive[passivelen - 1])
>     return EINVAL;
> 
> hmm; so even when there are no arguments, VALUE must end with 0?!

That

> root@debian:~# setfattr --name=gnu.translator --value='/hurd/pflocal\0' 1
> root@debian:~# showtrans 1
> /hurd/pflocal
> --8<---------------cut here---------------end--------------->8---
> 
> ...so "something" works.

Good :)

> Sadly, this trick does not work on GNU/Linux.  I'm afraid this hasn't
> been upstreamed and we would have to debug linux and/or create a patch
> for setxattr to accept "gnu." on "Hurd" type file systems.  Thoughts?

Well, this has to be done, yes, I don't know what else to add :)

Samuel


  reply	other threads:[~2020-05-11  8:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 19:48 Feeble attempt at using xattr gnu.translator Jan Nieuwenhuizen
2020-05-10 20:05 ` Samuel Thibault
2020-05-11  8:33   ` Jan Nieuwenhuizen
2020-05-11  8:42     ` Samuel Thibault [this message]
2020-05-11  8:46       ` Samuel Thibault
2020-05-11  8:53         ` Jan Nieuwenhuizen
2020-05-11  8:58           ` Samuel Thibault

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=20200511084208.tnjdat5bofcgsxth@function \
    --to=samuel.thibault@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=guix-devel@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 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).