all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Manolis Ragkousis <manolis837@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Build sandbox support etc. unconditionally on Linux.
Date: Wed, 10 Aug 2016 22:07:21 +0300	[thread overview]
Message-ID: <d3217310-7097-261f-d2cc-9c15e5458d86@gmail.com> (raw)
In-Reply-To: <87bn10wmka.fsf@netris.org>

Hello Mark,

On 08/10/16 20:39, Mark H Weaver wrote:
>
> I'm very reluctant to apply this patch.  In general, it's preferable to
> rely on autoconf to test for individual features, rather than testing
> for particular kernels by name.  It seems to me that this patch will
> hinder portability to other kernels.
>
> I'd be inclined to return to the approach you were proposing before
> discovering this upstream patch.  I'll take a look at it soon.
>
> What do you think?

Well the other solution will be to break the CHROOT_ENABLED into smaller
macros, depending on what we check.  If you think this is a better
solution then okay with me.

Locally I broke CHROOT_ENABLED into

#define CHROOT_ENABLED HAVE_CHROOT && HAVE_SYS_MOUNT_H &&
defined(MS_BIND) && defined(MS_PRIVATE)
#define CLONE_ENABLED defined(CLONE_NEWNS)
#if defined(SYS_pivot_root)
#define pivot_root(new_root, put_old) (syscall(SYS_pivot_root, new_root,
put_old))
#endif

And maybe we should rename CHROOT_ENABLED into SANDBOX_ENABLED or
something similar to better describe its purpose.

WDYT?

Thank you for looking into it,
Manolis

  reply	other threads:[~2016-08-10 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 16:53 [PATCH] Build sandbox support etc. unconditionally on Linux Manolis Ragkousis
2016-08-10 17:39 ` Mark H Weaver
2016-08-10 19:07   ` Manolis Ragkousis [this message]
2016-09-07  8:14     ` Ludovic Courtès

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=d3217310-7097-261f-d2cc-9c15e5458d86@gmail.com \
    --to=manolis837@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.