From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9826] New: post-build scritp - symlinks created in post-build script are overwritten after exit of the script
Date: Thu, 20 Apr 2017 09:35:50 +0000 [thread overview]
Message-ID: <bug-9826-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9826
Bug ID: 9826
Summary: post-build scritp - symlinks created in post-build
script are overwritten after exit of the script
Product: buildroot
Version: 2017.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: timo.valimaki at sensoan.com
CC: buildroot at uclibc.org
Target Milestone: ---
I'm trying to symlink /etc/group, /etc/passwd and /etc/shadow to RW partition,
in my case to /data/etc (rootfs-overlay).
I created a post-build that moves above files to /data/etc/ directory and
creates symlinks pointing to the moved files. When I'm pausing my post-build
script just before the exit everything is looking fine.
/output/target:
lrwxrwxrwx 1 timo timo 17 huhti 20 12:24 group -> ../data/etc/group
lrwxrwxrwx 1 timo timo 18 huhti 20 12:24 passwd -> ../data/etc/passwd
lrwxrwxrwx 1 timo timo 18 huhti 20 12:24 shadow -> ../data/etc/shadow
But when the Buildroot build is finished the above symlinks are overwritten
-rw-r--r-- 1 timo timo 320 huhti 20 12:29 group
-rw-r--r-- 1 timo timo 389 huhti 20 12:29 passwd
-rw------- 1 timo timo 291 huhti 20 12:29 shadow
Q: Is this as specified or a bug?
Q: If as specified, what is correct way to symlink above files?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-04-20 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 9:35 bugzilla at busybox.net [this message]
2017-04-20 20:15 ` [Buildroot] [Bug 9826] post-build scritp - symlinks created in post-build script are overwritten after exit of the script bugzilla at busybox.net
2017-04-20 21:37 ` bugzilla at busybox.net
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=bug-9826-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox