Debian on iPhone UNIX

NAND activity is nowadays semi-reliable (although one has to be VERY heedful not to break in the tactical manoeuvre in the middle of a write operation), but it is decent to have something consanguine to a full-functional OS, supported by non-volatile storage.

Group concerned in the project should be familiar with the myriads of UNIX "distributions" floating around. An in operation system consists of deuce major domains: one is the meat, which is what manages the implements of war, and one is the userland which contains belongings like shells and otherwise UIs, bundle managers, etc. Software system that help users instal and run functional programs. Ubuntu is a democratic spatial arrangement that I run on my syntactic category machine. Humanoid could also be considered a spatial arrangement (though I disbelieve it has no apparently messy meat patches).

I definite that Debian would be an newsworthy thing to try, since we would point instantly have a userland and a pool of ready-compiled applications. Victimisation a slightly datable root filesystem Hera: http://lists.debian.org/debian-arm/2007/01/msg00034.html, a initrd and farther meat configurations were ample to get it to run. Frankincense, we can nowadays compile programs for iPhone UNIX on iPhone UNIX. The process is rather slow right to the business and uneconomical NAND tactical manoeuvre operator (pending a real FTL), but at thing theoretically, iPhone UNIX is nowadays self-hosting.

This should be beautiful little decent for those United Nations agency square measure more than into the userland development side of belongings to come in, possibly victimisation Debian as a base to build thing else (as I disbelieve it is standard enough).

I will be offer manual on how to get this no to work soon. The (restricted for gismo order terminal) rootfs is fairly sizable (around 130 MB), so I'm not sure how we'll handle spatial arrangement of that.

Porting drivers to UNIX

We've ready-made no onward motion on the USB gismo operator for UNIX, and we're nowadays running a varietal wine order gismo for connectedness. This enforcement is influential because USB is nowadays a lot little laggy and belongings like LAN concluded USB, etc., can eventually be founded, relief access.

We've also got beautiful right with porting the NAND operator to UNIX. Least of the read support is nowadays here, and we've sporadic the routines in the iPhone meat where the raw implements of war write occurs. CPICH and c1de0x square measure excavation on reversing it. Hopefully, it will be correspondent decent to reads that it won't take a Brobdingnagian come of time to work out.

This is dissimilar from reversing their FTL, however, which is a complicated slip of collection structures, integrate buffers and otherwise alien algorithms that take care of evenly distributing writes throughout the tactical manoeuvre and also component writes take little time.

I think reversing no of that would take too little time and exertion. Instead, my proposition is to just reverse the implements of war NAND writes. Instead of victimisation a divider, we would have a loop-mounted root filesystem (like to how Wubi is falsification), with the root filesystem organism a file on the Media divider. Since there's a non-empty file at that physical object, the FTL system, some it is, mustiness make a matched mapping from logical sectors to physical NAND pages. We can already read the mapping it creates (we have already converse the read-side FTL encrypt), and so no we have to do to alter the collection is to write to the European pages we would've read from. Of course, this instrumentation that wear-leveling and bad block manipulation is not performed. However, if we use a filesystem that's reminiscent of bad blocks and can wear-level (YAFFS or JFFS2), point it amounts to the European thing. The wear-leveling would point take place concluded the particular physical pages happiness to the rootfs image, rather than the integrality of the NAND. This would make the physical pages happiness to the rootfs image wear out a little faster than the rest of the NAND, but the existent effect of this should be inconsequential.

The additive get of this falsification is that there's no repartitioning mandatory, so falsification is ascertain. See this wiki document for general planned enforcement details.

Debian on iPhone UNIX

NAND activity is nowadays semi-reliable (although one has to be VERY heedful not to break in the tactical manoeuvre in the middle of a write operation), but it is decent to have something consanguine to a full-functional OS, supported by non-volatile storage.

Group concerned in the project should be familiar with the myriads of UNIX "distributions" floating around. An in operation system consists of deuce major domains: one is the meat, which is what manages the implements of war, and one is the userland which contains belongings like shells and otherwise UIs, bundle managers, etc. Software system that help users instal and run functional programs. Ubuntu is a democratic spatial arrangement that I run on my syntactic category machine. Humanoid could also be considered a spatial arrangement (though I disbelieve it has no apparently messy meat patches).

I definite that Debian would be an newsworthy thing to try, since we would point instantly have a userland and a pool of ready-compiled applications. Victimisation a slightly datable root filesystem Hera: http://lists.debian.org/debian-arm/2007/01/msg00034.html, a initrd and farther meat configurations were ample to get it to run. Frankincense, we can nowadays compile programs for iPhone UNIX on iPhone UNIX. The process is rather slow right to the business and uneconomical NAND tactical manoeuvre operator (pending a real FTL), but at thing theoretically, iPhone UNIX is nowadays self-hosting.

This should be beautiful little decent for those United Nations agency square measure more than into the userland development side of belongings to come in, possibly victimisation Debian as a base to build thing else (as I disbelieve it is standard enough).

I will be offer manual on how to get this no to work soon. The (restricted for gismo order terminal) rootfs is fairly sizable (around 130 MB), so I'm not sure how we'll handle spatial arrangement of that.