From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JbA5D-00076J-A7 for garchives@archives.gentoo.org; Mon, 17 Mar 2008 07:48:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BF90BE04E8; Mon, 17 Mar 2008 07:48:32 +0000 (UTC) Received: from thenybble.de (lvps87-230-95-74.dedicated.hosteurope.de [87.230.95.74]) by pigeon.gentoo.org (Postfix) with ESMTP id 962B0E04E8 for ; Mon, 17 Mar 2008 07:48:32 +0000 (UTC) Received: from mnch-4d04eac5.pool.mediaways.net ([77.4.234.197] helo=localhost) by thenybble.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1JbA59-00022x-IS for gentoo-user@lists.gentoo.org; Mon, 17 Mar 2008 08:48:31 +0100 Date: Mon, 17 Mar 2008 08:47:57 +0100 From: Jan Seeger To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: jffs2 on gentoo Message-ID: <20080317074757.GA7452@venus> References: <20080314135242.2070d995@pascal.spore.ath.cx> <21D3AB88-C36A-4BF1-8FB2-C2F40C3992B5@stellar.eclipse.co.uk> <20080316083804.GA12745@venus> <20080316180311.GA5265@venus> <1205703808.21435.45.camel@bunyip.localdomain> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <1205703808.21435.45.camel@bunyip.localdomain> User-Agent: Mutt/1.5.16 (2007-06-09) X-Archives-Salt: eeb22e4c-0e1c-41db-a1fc-f55076861873 X-Archives-Hash: d83819ac8ecd385d95557dcf3ebcd4b0 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 16. Mar, W.Kenworthy spammed my inbox with=20 > I believe that writing a file to a single location is not the way to do > this: you need to write a byte to the usb key in the same location, but > need to ensure it continually changes: perhaps rotating 1's/0's. > Alternatively, the concern is that the FAT/inode table or the like is > where the most wear will occur - perhaps concentrate there? Yeah, if I have the stick mounted sync and always copy and delete a file, s= ome bytes should get flipped around regularly. *If* there is no internal wear leveling, that is. On USB sticks with internal wear leveling, you will, fro= m a size of about 1 GB upwards, never (Well, perhaps after 10 years...) see a failure due to media wear. For the record: My USB stick has now gone through 78560 read/write cycles a= nd is still happily copying. Regards, Jan --=20 thenybble.de/blog/ -- four bits at a time --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFH3iItMmLQdC6jvocRAq98AJ9cRKEhag+B+UJFjjtqDleMwfWw6gCeNxlC DBDCLEZaPPDM9g/IlOkYERQ= =AE70 -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- -- gentoo-user@lists.gentoo.org mailing list