mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Creating links in the root filesystem
Date: Mon, 21 Jan 2013 10:07:09 +0000	[thread overview]
Message-ID: <eme40360d6-d033-4262-8ce6-c78a44ee464d@nb-mak> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1179 bytes --]

Hello,

I try to put links into the read-only rootfs which should point into a 
RAM filesystem.
For example I want to put the resolv.conf file into the tmpfs which is 
mounted at /tmp that the DHCP client can modify that file at runtime.

I tried to create a link in the projectroot:

cd projectroot/etc
ln -s ../tmp/resolv.conf resolv.conf


But then I get the following error with a "ptx go":

-------------------------------------
target: os-release.targetinstall.post
-------------------------------------

finished target os-release.targetinstall.post
make: *** No rule to make target 
`/home/user/development/bsp/branch2_tx53/projectroot/etc/resolv.conf', 
needed by 
`/home/user/development/bsp/branch2_tx53/platform-optimeas-tx53/state/rootfs.targetinstall'. 
  Stop.

If I create an empty file at projectroot/tmp/resolv.conf the file will 
be copied in the rootfs instead if the link...


What is the right way to create such links?
If I create an own package (in + rule) which creates these links, how 
can I ensure that my package is called as the last package to overwrite 
files from other packages ?


Best regards,

Matthias

[-- Attachment #1.2: Type: text/html, Size: 1988 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2013-01-21 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 10:07 Matthias Klein [this message]
2013-01-21 11:25 ` Michael Olbrich

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=eme40360d6-d033-4262-8ce6-c78a44ee464d@nb-mak \
    --to=matthias.klein@optimeas.de \
    --cc=ptxdist@pengutronix.de \
    /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