From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] makedevs and symbolic links
Date: Wed, 6 Feb 2013 17:26:41 +0100 [thread overview]
Message-ID: <20130206172641.4c042f87@skate> (raw)
In-Reply-To: <CAJkQPOn=Pi+NhbRvVG_gk9ccQDaUoUuPH3aEsos032kAv6Y23A@mail.gmail.com>
Dear Aras Vaichas,
On Wed, 6 Feb 2013 16:17:26 +0000, Aras Vaichas wrote:
> I use Buildroot with my own custom root fs skeleton. My skeleton contains a
> few symbolic links that I'd like to move out either into
> the BR2_ROOTFS_POST_BUILD_SCRIPT or somewhere else.
>
> makedevs seemed logical but it doesn't support symbolic link creation.
>
> Is there a reason for this?
>
> Would it be useful to add it?
From my point of view, makedevs is here to do the things you can't do
without being root: create device nodes and adjust ownership.
Symbolic links can be created as non-root in a post-build script for
example, so I'm not sure there's really a need to have support for
symbolic links in makedevs.
Or maybe I'm missing the point?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-06 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:17 [Buildroot] makedevs and symbolic links Aras Vaichas
2013-02-06 16:26 ` Thomas Petazzoni [this message]
2013-02-06 16:50 ` Aras Vaichas
2013-02-06 16:57 ` Thomas Petazzoni
2013-02-07 10:14 ` Aras Vaichas
2013-02-07 10:43 ` Thomas Petazzoni
2013-02-07 17:14 ` Arnout Vandecappelle
2013-02-07 21:58 ` [Buildroot] [PATCH] rootfs-overlay: also exclude .empty files Arnout Vandecappelle
2013-02-08 5:15 ` Samuel Martin
2013-02-08 21:18 ` Peter Korsgaard
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=20130206172641.4c042f87@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.