From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [fyi] lddtree magic
Date: Tue, 9 Apr 2013 23:10:21 -0400 [thread overview]
Message-ID: <201304092310.22152.vapier@gentoo.org> (raw)
In-Reply-To: <51647A62.6020604@flameeyes.eu>
[-- Attachment #1: Type: Text/Plain, Size: 843 bytes --]
On Tuesday 09 April 2013 16:30:26 Diego Elio Pettenò wrote:
> On 09/04/2013 20:31, Mike Frysinger wrote:
> > but things get even crazier with the new --copy-to-tree option (python
> > version only). this is useful for scenarios like kernel initramfs where
> > you want to copy over one or two ELFs and their dependencies w/out
> > resorting to statically linking them. check out the --help text for
> > more details.
>
> Would you mind a "hardlink to tree"? Would be lovely for chroot
> environments as well...
sure, that should be easy to add. i'll add an obligatory warning about the
accidental modification scenario. i know some newer kernel systems (like
yama?) have started disallowing hardlinks to files you don't own (even ones
that aren't setuid). the resulting error is fun & obtuse too like "EPERM".
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-10 3:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 19:31 [gentoo-dev] [fyi] lddtree magic Mike Frysinger
2013-04-09 20:30 ` Diego Elio Pettenò
2013-04-10 3:10 ` Mike Frysinger [this message]
2013-04-10 10:04 ` Fabio Erculiani
2013-04-10 16:33 ` Mike Frysinger
2013-04-10 16:42 ` Fabio Erculiani
2013-04-10 17:32 ` Mike Frysinger
2013-04-10 17:40 ` Fabio Erculiani
2013-04-10 17:56 ` Mike Frysinger
2013-04-09 20:41 ` Samuli Suominen
2013-04-09 20:45 ` Samuli Suominen
2013-04-10 2:30 ` Mike Frysinger
2013-04-09 22:22 ` Samuli Suominen
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=201304092310.22152.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox