From: ludo@gnu.org (Ludovic Courtès)
To: YOANN P <yoann_mac_donald@hotmail.com>
Cc: "30768@debbugs.gnu.org" <30768@debbugs.gnu.org>
Subject: bug#30768: Gettext : test-copy-file-1.sh fail if --with-store-dir=/var/tmp/xxxxx/gnu/store
Date: Wed, 14 Mar 2018 10:33:51 +0100 [thread overview]
Message-ID: <87bmfrypa8.fsf@gnu.org> (raw)
In-Reply-To: <DB6P18901MB002263FBD187F96096018C7CDBD20@DB6P18901MB0022.EURP189.PROD.OUTLOOK.COM> (YOANN P.'s message of "Tue, 13 Mar 2018 23:48:54 +0000")
Hello,
YOANN P <yoann_mac_donald@hotmail.com> skribis:
>>YOANN P <yoann_mac_donald@hotmail.com> skribis:
[...]
>>> Even if i was aware of it after reading Pjotrp notes, i've never found a
>>> clear limit after my readings on the web. If Guix Team has an idea of
>>> the store path limit lenght, it could be a great idea to add it to the docs
>>> or did i missed it ?
>>
>From m4/guix.m4:
>>
>>--8<---------------cut here---------------start------------->8---
>>dnl 'BINPRM_BUF_SIZE' constant in Linux (we leave room for the trailing zero.)
>>dnl The Hurd has a limit of about a page (see exec/hashexec.c.)
>>m4_define([LINUX_HASH_BANG_LIMIT], 127)
>>
>>dnl Hardcoded 'sun_path' length in <sys/un.h>.
>>m4_define([SOCKET_FILE_NAME_LIMIT], 108)
>>--8<---------------cut here---------------end--------------->8---
>>
>
> Hum, i'm not sure this part of code answer my question :)
> Are we agreed than LINUX_HASH_BANG_LIMIT is the max number of char for a
> shebang and SOCKET_FILE_NAME_LIMIT is only the limit for the socket file name ?
Yes.
> What i was asking is the maximum lenght for the store path regarding the fact
> (if i am not wrong) than a shebang inside guix is compose like this :
The only limit here is PATH_MAX.
>>Are you in a situation where user namespaces are unavailable? HPC?
>
> Not at all, i was just playing with Guix to see if it can fulfill my long desires to have
> an easy unprivileged portable environment due to old habits to intervene into some
> hostiles environments in my previous job.
Then I strongly recommend using it as documented, i.e., using /gnu/store
as the store and running guix-daemon as root.
You can’t really get around it:
https://guix-hpc.bordeaux.inria.fr/blog/2017/09/reproducibility-and-root-privileges/
Thanks,
Ludo’.
prev parent reply other threads:[~2018-03-14 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 16:08 bug#30768: Gettext : test-copy-file-1.sh fail if --with-store-dir=/var/tmp/xxxxx/gnu/store YOANN P
2018-03-11 20:01 ` YOANN P
2018-03-12 13:47 ` Ludovic Courtès
2018-03-12 19:18 ` YOANN P
2018-03-12 21:08 ` Ludovic Courtès
2018-03-13 23:48 ` YOANN P
2018-03-14 9:33 ` Ludovic Courtès [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=87bmfrypa8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30768@debbugs.gnu.org \
--cc=yoann_mac_donald@hotmail.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).