<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 12/02/12 06.18, Glenn wrote:
<blockquote cite="mid:4F374BBB.1090605@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
On 12/02/12 00.01, Jack Jones wrote:
<blockquote
cite="mid:1329001318.4291.YahooMailNeo@web120304.mail.ne1.yahoo.com"
type="cite">And Chris you will know the latest 3. kernel uses a
different filesystem strycture--brtfs.<br>
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div dir="ltr"> <font face="Arial" size="2">
<hr size="1"><b><span style="font-weight: bold;"></span></b></font><br>
</div>
</div>
</div>
</blockquote>
<br>
Hi Jack<br>
<br>
Do you mean?:<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://en.wikipedia.org/wiki/Btrfs">http://en.wikipedia.org/wiki/Btrfs</a><br>
<br>
Glenn<br>
</blockquote>
<br>
Btrfs is (almost) to good to be true ;-) :<br>
<br>
<a class="moz-txt-link-freetext"
href="http://en.wikipedia.org/wiki/Btrfs">http://en.wikipedia.org/wiki/Btrfs</a><br>
Quote: "...<br>
is a GPL-licensed copy-on-write file system for Linux. Development
began at Oracle Corporation in 2007.<br>
...<br>
Features<br>
<br>
As of Linux 3.2 (Released January 4, 2012), btrfs implements: [6][7][8]<br>
<br>
* <b>Online defragmentation</b><br>
* <b>Online volume growth and shrinking</b><br>
* Online block device addition and removal<br>
* Online balancing (movement of objects between block devices to
balance load)<br>
* Object-level RAID0, RAID1, and RAID10<br>
* Subvolumes (one or more separately-mountable filesystem roots within
each physical partition)<br>
* Transparent compression (currently zlib and LZO)<br>
* <b>Snapshots</b> (read-only[9] or copy-on-write clones of subvolumes)<br>
* File cloning (copy-on-write on individual files, or byte ranges
thereof)<br>
* Checksums on data and metadata (currently CRC-32C[10])<br>
* <b>In-place conversion (with rollback) from ext3/4 to Btrfs</b>[11]<br>
* <b>File system seeding</b>[12] [Comment: Means you can always roll
back to a stable installation (Maybe with your settings?)!] (Btrfs on
read-only storage used as a copy-on-write backing for a writeable Btrfs)<br>
* Block discard support (reclaims space on some virtualized setups and <b>improves
wear leveling on SSDs</b> by notifying the underlying device that
storage is no longer in use)<br>
..."<br>
<br>
Maybe it would be a nice with a individually pooled subvolumes on
internal flash (stable denominator) and the SDHC-card?<br>
<br>
For testing purposes, you could have an all in one different
"read-only" 2.6.3x variants, in the internal flash? Even with debugging
(slower) kernels?<br>
<br>
E.g. if the variant boots up, but does not receive the "magic" sign
(screen press, aux press), the variant boots the phone back into the
former known good variant.<br>
<br>
It could be combined with Linux-Vserver, so both the work-phone and the
private phone with the same kernel, can be booted simultaneously and
with a little RAM-use overhead.<br>
<br>
-<br>
<br>
Linux-Vserver could include:<br>
* PaX - is a patch for the Linux kernel that implements least privilege
protections for memory pages.<br>
* grsecurity - PaX + Another notable component of grsecurity is that it
provides a full role-based access control (RBAC) system.<br>
<br>
Glenn<br>
<br>
</body>
</html>