Richard Daemon wrote:
I'll have to look at "release".
> ... Never had a problem with any of these systems or the CF cards.
Mine problem with CF is that they are sloooooow to access and worse for
writing.
However regarding the limited read/write cycles, CF are apparently
becoming much more durable than earlier. One thing I note is that the
ones I have all have 5 year warranties and where I am using them it
would troublesome, but not catastrophic, for the CF to be sent back
while under warranty.
> ...
I have both, too, but am considering rolling a second bsd.rd with
non-standard options like SSHd. though I can't quite think of how that
would be useful, since I usually have to have console access anyway if I
mess things up so badly as to require a restoration. Experiments with
/dev usually caused that.
regards,
-Lars
| Chuck Ebbert | Why do so many machines need "noapic"? |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
git: | |
| Corey Minyard | [PATCH 3/3] Convert the UDP hash lock to RCU |
| David Miller | [GIT]: Networking |
| Denys Fedoryshchenko | packetloss, on e1000e worse than r8169? |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
