From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2233] New: Atmel atstk target skeletons have /etc/mtab as a file, not a symlink
Date: Fri, 16 Jul 2010 15:17:15 +0000 (UTC) [thread overview]
Message-ID: <bug-2233-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2233
Summary: Atmel atstk target skeletons have /etc/mtab as a file,
not a symlink
Product: buildroot
Version: 2010.05
Platform: Other
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: nick at leverton.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
/etc/mtab in the target skeleton is supposed to be a symlink to ../proc/mounts,
and most device skeletons have it as such.
However, unless there's something strange with my git installation, the two
Atmel atstk100* skeleton filesystems have /etc/mtab as a regular file
containing the text ../proc/mounts . The files in error are:
target/device/Atmel/atstk1005/target_skeleton/etc/mtab
target/device/Atmel/atstk100x/target_skeleton/etc/mtab
Atmel atngw100 is correct in having a symlink.
Fairly trivial, but things which check for mounted filesystems will fail
(oprofile was what I fell over this with on an atstk1006). I can't supply a
patch as I don't know how to make git cope with the change in filetype - it
seems convinced that I have removed the files :-(
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-07-16 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 15:17 bugzilla at busybox.net [this message]
2010-07-18 20:23 ` [Buildroot] [Bug 2233] Atmel atstk target skeletons have /etc/mtab as a file, not a symlink 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-2233-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 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.