From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Dataflash rootfs problems (still)
Date: Wed, 24 Oct 2007 21:34:50 +0300 [thread overview]
Message-ID: <471F904A.5050206@promwad.com> (raw)
In-Reply-To: <6090c5eb0710240954q368b3409k282c02a5e2fcbef4@mail.gmail.com>
>
> During the 1st boot, Dropbear creates and "writes" the generated keys, maybe
> is this *write* operation the one screwing up the dataflash?
>
We have similar problems with Dataflash&RM9200
*write* operation is unreliable - we had corrupted filesystem after reboot.
Our solution was to use r/o only on dataflash.
Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-10-24 18:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:20 [Buildroot] Dataflash rootfs problems (still) Jorge S.
2007-10-24 16:33 ` Ulf Samuelsson
2007-10-24 16:54 ` Jorge S.
2007-10-24 18:34 ` Ivan Kuten [this message]
2007-10-24 22:57 ` Ulf Samuelsson
2007-10-25 9:08 ` Jorge S.
2007-10-25 16:17 ` Jorge S.
2007-10-25 16:30 ` Ulf Samuelsson
2007-10-25 16:46 ` Jorge S.
2007-10-25 16:51 ` Ulf Samuelsson
2007-10-25 18:48 ` Ivan Kuten
2007-10-25 17:58 ` Jorge S.
2007-10-25 19:09 ` Ivan Kuten
2007-10-25 18:11 ` Jorge S.
2007-10-25 19:20 ` Ivan Kuten
2007-10-24 22:49 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2007-10-24 18:37 Michael Trimarchi
2007-10-24 18:54 ` Jorge S.
2007-10-24 18:59 ` Jorge S.
2007-10-24 19:06 Michael Trimarchi
2007-10-24 19:40 ` Jorge S.
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=471F904A.5050206@promwad.com \
--to=ivan.kuten@promwad.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox