Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Strange MTD problem (ARM)
Date: Mon, 07 Dec 2009 09:34:25 +0100	[thread overview]
Message-ID: <873a3nqj1q.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <op.u4j7ikxlyqa4qb@jap> (Joachim Pihl's message of "Mon, 7 Dec 2009 09:36:15 +0100")

>>>>> "Joachim" == Joachim Pihl <jpihl@nevion.com> writes:

 Joachim> This may not be related to Buildroot, but I am completely stumped:

I take it that this is with busybox cp and not coreutils? You might have
better luck asking on the busybox list.

 Joachim> # cp mtdblock2 /dev/mtdblock2

So you want cp to detect that the target is a special file and not
unlink it, but instead do something like cat mtdblock2 >/dev/mtdblock2 ?

Why not simply use cat instead?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-07  8:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  8:36 [Buildroot] Strange MTD problem (ARM) Joachim Pihl
2009-12-07  8:34 ` Peter Korsgaard [this message]
2009-12-07  8:52   ` Joachim Pihl
2009-12-07  8:57     ` Peter Korsgaard
2009-12-07  9:17       ` Joachim Pihl
2009-12-07  9:28         ` 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=873a3nqj1q.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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