LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
Marty Leisner <linux@rochester.rr.com>,
linux-kernel@vger.kernel.org, bug-cpio@gnu.org,
martin.leisner@xerox.com
Subject: Re: ownership/permissions of cpio initrd
Date: Tue, 05 Dec 2006 14:58:27 -0600 [thread overview]
Message-ID: <4575DD73.9010008@mnsu.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0612052139180.18570@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>> It appears to not be standard with fedora for sure... but while it origiginally
>> was/is a Debian package it looks like there is source if you'd like to build it
>> on other systems. It was originally designed to tackle the exact problem you
>> are confronting.
>>
>> See:
>> http://freshmeat.net/projects/fakeroot/
>>
>> About:
>> Fakeroot runs a command in an environment were it appears to have root
>> privileges for file manipulation, by setting LD_PRELOAD to a library with
>> alternative versions of getuid(), stat(), etc. This is useful for allowing
>> users to create archives (tar, ar, .deb .rpm etc.) with files in them with root
>> permissions/ownership. Without fakeroot one would have to have root privileges
>> to create the constituent files of the archives with the correct permissions
>> and ownership, and then pack them up, or one would have to construct the
>> archives directly, without using the archiver.
>>
>
> Ugh that sounds even more than a hack. At least for one-user
> archives, I guess nobody at Debian knows that tar has a --user and
> --group option.
>
>
> -`J'
>
...It also let's you mknod and friends, and let's you set permissions to
files to more than just ONE user. The whole point of the commands is to
let you make distribution files without root access. Of course you can
fake all of this with a special archiver command.... I'm just throwing
out options.
$ fakeroot
# mkdir root
# mkdir root/dev/
# mknod root/dev/null c 1 3
# mknod root/dev/sda1 b 8 1
# chown root.disk root/dev/sda1
# cd root
# tar cvf ../root.tar ./
# exit
$ tar tvf root.tar
drwxr-xr-x root/root 0 2006-12-05 14:54 ./
drwxr-xr-x root/root 0 2006-12-05 14:54 ./dev/
crw-r--r-- root/root 1,3 2006-12-05 14:54 ./dev/null
brw-r--r-- root/disk 8,1 2006-12-05 14:54 ./dev/sda1
--
Jeffrey Hundstad
next prev parent reply other threads:[~2006-12-05 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux@rochester.rr.com>
2006-12-05 17:20 ` Marty Leisner
2006-12-05 20:07 ` Horst H. von Brand
2006-12-05 20:17 ` Jeffrey Hundstad
2006-12-05 20:24 ` Horst H. von Brand
2006-12-05 20:32 ` Jan Engelhardt
2006-12-05 20:35 ` Jeffrey Hundstad
2006-12-05 20:39 ` Jan Engelhardt
2006-12-05 20:58 ` Jeffrey Hundstad [this message]
2006-12-05 21:43 ` Jan Engelhardt
2006-12-06 6:54 ` Marty Leisner
2006-12-05 20:30 ` Andreas Schwab
2006-12-05 21:56 ` Leisner, Martin
2006-12-05 22:23 ` Andreas Schwab
2006-12-06 12:17 ` Rainer Bawidamann
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=4575DD73.9010008@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=bug-cpio@gnu.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rochester.rr.com \
--cc=martin.leisner@xerox.com \
--cc=vonbrand@inf.utfsm.cl \
--subject='Re: ownership/permissions of cpio initrd' \
/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
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 NNTP newsgroup(s).