From: David Wuertele <dave-gnus@bfnet.com>
To: linux-mtd@lists.infradead.org
Subject: Re: in situ MTD upgrade from userspace (kernel, CRAMFS, YAFFS)
Date: Fri, 05 Nov 2004 14:59:11 -0800 [thread overview]
Message-ID: <m3wtwznbr4.fsf@bfnet.com> (raw)
In-Reply-To: m33bzonifa.fsf@bfnet.com
> 1. There are many other processes running at the time of the upgrade.
> They are running out of CRAMFS. As I overwrite the CRAMFS
> partition, is it possible that my write could get corrupted?
> Perhaps by crashing programs that inadvertently do weird syscalls?
Corollary question:
As my own userspace process overwrites the CRAMFS block that
contains that process's program, how can I ensure that the process
doesn't get hosed until after it has a chance to reboot the system?
next prev parent reply other threads:[~2004-11-05 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 20:35 in situ MTD upgrade from userspace (kernel, CRAMFS, YAFFS) David Wuertele
2004-11-05 22:59 ` David Wuertele [this message]
2004-11-08 12:58 ` Josh Boyer
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=m3wtwznbr4.fsf@bfnet.com \
--to=dave-gnus@bfnet.com \
--cc=linux-mtd@lists.infradead.org \
/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.