In article <[EMAIL PROTECTED]>,
"Marty Leisner" <[EMAIL PROTECTED]> writes:
> But its "useful" to change permissions/ownership of the initrd
> files at times...
>
> Since a cpio is just a userspace created string of bits, I suppose
> you can apply a set of ownership/permissions to files IN
Jeffrey Hundstad <[EMAIL PROTECTED]> writes on Tue, 05 Dec 20
06 14:17:22 CST
> You can also use fakeroot(1).
>
> Start fakeroot.
> Change all of your permissions as you see fit.
> make your cpio
> exit fakeroot.
>
>
>
ThanksI got it running on
"Leisner, Martin" <[EMAIL PROTECTED]> writes:
> hmmm...I looked at that -- that's extract and passthrough, but not create...
No, it's copy-out and copy-pass. It does not make sense for copy-in.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5,
ns with no special priveleges...
marty
> -Original Message-
> From: Andreas Schwab [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 05, 2006 3:31 PM
> To: Marty Leisner
> Cc: linux-kernel@vger.kernel.org; bug-cpio@gnu.org; Leisner, Martin
> Subject: Re: ownershi
On Dec 5 2006 14:58, Jeffrey Hundstad wrote:
>
> ...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
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://freshme
> 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.n
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/fake
>> You can also use fakeroot(1).
>
>I think that is a debianism... not here on Fedora.
LKML is (hopefully) distro neutral.
That useless line aside, the linux kernel build process supports
creating a cpio archive with privileged things (devices) as a normal
user.
-`J'
--
-
To
"Marty Leisner" <[EMAIL PROTECTED]> writes:
> Since a cpio is just a userspace created string of bits, I suppose
> you can apply a set of ownership/permissions to files IN the archive
> by playing with the bits...
-R, --owner=[USER][:.][GROUP] Set the ownership of all files created to the
Jeffrey Hundstad <[EMAIL PROTECTED]> wrote:
> You can also use fakeroot(1).
I think that is a debianism... not here on Fedora.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de InformaticaFono: +56 32 2654431
Universidad Tecnica Federico Sa
You can also use fakeroot(1).
Start fakeroot.
Change all of your permissions as you see fit.
make your cpio
exit fakeroot.
Horst H. von Brand wrote:
Marty Leisner <[EMAIL PROTECTED]> wrote:
I'm working on an embedded system with the 2.6 kernel -- cpio
initrd was a new feature I'm looking
Marty Leisner <[EMAIL PROTECTED]> wrote:
> I'm working on an embedded system with the 2.6 kernel -- cpio
> initrd was a new feature I'm looking at (and very welcome).
>
> The major advantage I see is you don't have MAKE a filesystem
> on the build host (doing cross development). So you don't have
I'm working on an embedded system with the 2.6 kernel -- cpio
initrd was a new feature I'm looking at (and very welcome).
The major advantage I see is you don't have MAKE a filesystem
on the build host (doing cross development). So you don't have
to be root.
But its "useful" to change permission
14 matches
Mail list logo
