On 10/22/07, Brian A. Seklecki  wrote:

quoted text
> For my bsd-appliance project, I use CF media strictly for booting a MD/RD kernel image.  If you're doing a full-install on the CF card, you've got the wrong approach.  You're going to nuke your CF media with all of that atime update and IO cache flush overhead.

In a word: "bullshit"
In more words: I've been running production devices for 5yrs with CF

mounted rw. I use async and noatime so it feels faster, not prolong

the longevity of the card. A couple of months ago a took an older (ca.

2004) 256M sandisk card, and ran iogen on it for a month; I put

several terabytes through it and the card is just fine. I'm sure it'll

fail catastrophically when all the spare sectors give out, but how is

that different from a spinning magnetic disk?
Try it sometime. CF may still be slow, but it's not unreliable.
> There's no progress(1) in OpenBSD yea, so I'm not sure about the exact speed, but I'm able to un-pax(1) a 20->60 meg kernel image into MFS /usr in about 10 seconds.  ARInfotek AMD-Geode 800 SBC (500MHz)  ~BAS
ftp -Vm -o - file:///path/to/i386/base42.tgz | tar -C /mnt/cfdisk -zxpf -
CK
--

GDB has a 'break' feature; why doesn't it have 'fix' too?