From: David Woodhouse <dwmw2@infradead.org>
To: "Nikolai Vladychevski" <niko@isl.net.mx>
Cc: linux-mtd@lists.infradead.org
Subject: Re: duplicate DoC millenium with dd
Date: Tue, 11 Sep 2001 22:23:46 +0100 [thread overview]
Message-ID: <9772.1000243426@redhat.com> (raw)
In-Reply-To: <20010911201345.19481.qmail@qis>
niko@isl.net.mx said:
> ohh, so bad.... I will have to nftl_format every time I update my
> flash....
Not at all - no more than you need to do a low level format of your hard
drive every time you put a new filesystem on it. Just do the mkcramfs step
again.
> > What are you partitioning it for, btw?
> It's a firewall. I place linuxbios & kernel first, then I nftl_format
> /dev/mtd0 0xFIRST_FREE_BLOCK and place a minimal filesystem (cramfs)
> on the rest of the chip.....
You nftl_format it with the offset, which gives you a block device /dev/
nftla. Then you use sfdisk rather than mkcramfs -o /dev/nftla. If you only
have one partition, then a partition table is just a waste of space.
> since you say nftl_format removes
> original badblocks table M-Systems put on the chip at fabrication
> time, I kinda dislike this util.....
It's now better than it was. And you shouldn't need to use it more than
once, if the total size of your LinuxBIOS and kernel don't change (or if
you left enough space for a little bit of expansion).
> is there any way to avoid nftl_format and boot my cramfs from /dev/
> mtdblockX or /dev/mtd0 with an 0xXXXX offset or something like this?
Not out of the box. It's trivial to do that though, by using the mtd
version of partitions, which makes it look like two (or more) separate MTD
devices.
--
dwmw2
next prev parent reply other threads:[~2001-09-11 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 18:26 duplicate DoC millenium with dd Nikolai Vladychevski
2001-09-11 20:17 ` David Woodhouse
2001-09-11 20:13 ` Nikolai Vladychevski
2001-09-11 21:23 ` David Woodhouse [this message]
2001-09-11 20:58 ` Nikolai Vladychevski
2001-09-11 22:00 ` David Woodhouse
2001-09-11 22:20 ` Nikolai Vladychevski
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=9772.1000243426@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=niko@isl.net.mx \
/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