Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/pseudo: new package
Date: Thu, 3 Nov 2016 21:41:48 +0100	[thread overview]
Message-ID: <20161103214148.16d86fcd@free-electrons.com> (raw)
In-Reply-To: <05edc0b87e262b290da043479e16dd1b10c0ac70.1477729581.git.yann.morin.1998@free.fr>

Hello,

On Sat, 29 Oct 2016 10:26:41 +0200, Yann E. MORIN wrote:
> Pseudo is a program that can either be used directly or as an
> LD_PRELOAD, which allows these operations to succeed as if the
> user did have system administrator privileges even though they
> are an ordinary user.
> 
> Pseudo has a lot of similarities to fakeroot but is a new
> implementation that improves on the problems seen using fakeroot.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Andrey Yurovsky <yurovsky@gmail.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/pseudo/pseudo.hash |  2 ++
>  package/pseudo/pseudo.mk   | 15 +++++++++++++++
>  2 files changed, 17 insertions(+)
>  create mode 100644 package/pseudo/pseudo.hash
>  create mode 100644 package/pseudo/pseudo.mk

Both patches applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-11-03 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-29  8:26 [Buildroot] [PATCH 0/2] fs: fix fakeroot issue with SElinux contexts Yann E. MORIN
2016-10-29  8:26 ` [Buildroot] [PATCH 1/2] package/pseudo: new package Yann E. MORIN
2016-11-03 20:41   ` Thomas Petazzoni [this message]
2016-10-29  8:26 ` [Buildroot] [PATCH 2/2] fs: use pseudo instead of fakeroot Yann E. MORIN
2016-10-29  8:33 ` [Buildroot] [PATCH 0/2] fs: fix fakeroot issue with SElinux contexts Thomas Petazzoni

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=20161103214148.16d86fcd@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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