Linux Container Development
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: util-linux-ng@vger.kernel.org, akpm@linux-foundation.org,
	hch@infradead.org, serue@us.ibm.com, viro@ftp.linux.org.uk,
	ebiederm@xmission.com, kzak@redhat.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	containers@lists.osdl.org
Subject: Re: util-linux-ng: unprivileged mounts support
Date: Tue, 8 Jan 2008 10:31:04 -0500	[thread overview]
Message-ID: <200801081031.06826.vapier@gentoo.org> (raw)
In-Reply-To: <E1JCCyk-0002pY-AM@pomaz-ex.szeredi.hu>

[-- Attachment #1: Type: text/plain, Size: 667 bytes --]

On Tuesday 08 January 2008, Miklos Szeredi wrote:
> --- util-linux-ng.orig/configure.ac	2008-01-07 21:40:22.000000000 +0100
> +++ util-linux-ng/configure.ac	2008-01-07 21:40:50.000000000 +0100
> @@ -91,6 +92,11 @@ fi
>  UTIL_CHECK_LIB(util, openpty)
>  UTIL_CHECK_LIB(termcap, tgetnum)
>
> +UTIL_CHECK_LIB(cap, cap_get_proc)
> +if test $have_cap = no; then
> +   AC_MSG_ERROR([libcap is required for mount]);
> +fi

this should be optional and it should be controlled with an AC_ARG_WITH()

with all the non-linux changes that have gone in, does there need to be header 
checks here and then have mount.c key off of them ?  i'm thinking so ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2008-01-08 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 11:50 util-linux-ng: unprivileged mounts support Miklos Szeredi
2008-01-08 15:31 ` Mike Frysinger [this message]
2008-01-08 15:47   ` 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

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

  git send-email \
    --in-reply-to=200801081031.06826.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=hch@infradead.org \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=serue@us.ibm.com \
    --cc=util-linux-ng@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox