From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: jffs2 on gentoo
Date: Tue, 18 Mar 2008 11:33:13 +0100 [thread overview]
Message-ID: <1205836393.5566.67.camel@NOTE_GENTOO64.PHHEIMNETZ> (raw)
In-Reply-To: <C7503BCD-1FAB-41C0-B9EB-6F82303764B5@stellar.eclipse.co.uk>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Tue, 2008-03-18 at 01:47 +0000, Stroller wrote:
> On 17 Mar 2008, at 18:10, James wrote:
> > ...
> > Wear leveling is *probably* built into the IDE to CF converter
> > carrier board?
>
> Almost certainly not, I'd have thought. Aren't those boards just dumb
> pin-convertors? CF cards "talk" IDE.
>
> Stroller.
Yes they are.
Another thought crossed my mind today: Does wear leveling work if I
create loopback devices (ext2-formatted) on FAT32?
By the way: Why is wear leveling filesystem-dependent anyway? I would
have thought it were working on blocks (like device mapper, cryptsetup,
lvm and so on) and not on files.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-18 10:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 18:27 [gentoo-user] jffs2 on gentoo James
2008-03-14 18:52 ` Dan Farrell
2008-03-15 20:08 ` [gentoo-user] " James
2008-03-15 23:14 ` Stroller
2008-03-16 8:38 ` Jan Seeger
2008-03-16 9:46 ` Alan McKinnon
2008-03-16 18:03 ` Jan Seeger
2008-03-16 21:43 ` W.Kenworthy
2008-03-16 21:52 ` Neil Bothwick
2008-03-17 7:47 ` Jan Seeger
2008-03-15 10:50 ` [gentoo-user] " Florian Philipp
2008-03-15 19:38 ` dexters84
2008-03-15 20:17 ` [gentoo-user] " James
2008-03-15 23:19 ` Stroller
2008-03-16 0:08 ` dexters84
2008-03-17 18:10 ` James
2008-03-18 1:47 ` Stroller
2008-03-18 10:33 ` Florian Philipp [this message]
2008-03-18 13:47 ` Stroller
2008-03-18 19:02 ` dexters84
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=1205836393.5566.67.camel@NOTE_GENTOO64.PHHEIMNETZ \
--to=lists@f_philipp.fastmail.net \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox