Samsung Moment - Entire filesystem ported to SD card, EXT3

glitch77

Jr. Member

Cookies: -1
Posts: 55

Entire filesystem ported to SD card, EXT3

« on: December 18, 2009, 01:28:56 AM »

I decided I didn't like RFS so I got rid of it. lol

Code:

mount

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p5 /system ext3 rw,nosuid,nodev,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext3 rw,nosuid,nodev,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,errors=continue,data=ordered 0 0

Code:

df

/dev: 74688K total, 0K used, 74688K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/system: 396623K total, 118736K used, 277887K available (block size 1024)
/data: 396623K total, 24516K used, 372107K available (block size 1024)
/cache: 482214K total, 10532K used, 471682K available (block size 1024)

Just partition the SD card with one primary FAT16 partition, then 3 extended partitions. Dump /dev/stl5 to mmcblk0p5. Change your init.rc as follows for each of /data /cache /system:

mount ext3 /dev/block/mmcblk0p5 /system nosuid nodev
mount ext3 /dev/block/mmcblk0p6 /data nosuid nodev
mount ext3 /dev/block/mmcblk0p7 /cache nosuid nodev

This has no purpose*, and makes the phone pretty darn slow with the stock sd card, but hey, its neat!

*(This does have a purpose, but not for joe user. This is a stepping stone on the way to fixing what Samsung broke.)


« Last Edit: December 18, 2009, 01:37:32 AM by glitch77 »	Logged

linckraker

Newbie

Cookies: 2
Posts: 32

Re: Entire filesystem ported to SD card, EXT3

« Reply #1 on: December 18, 2009, 03:06:45 AM »

Is the speed unbearable? could a faster SD card (a class 6) be fast enough for normal use?

Not that I want to. I'm just curious because the nook also has it's file system on an SD card.


	Logged

glitch77

Jr. Member

Cookies: -1
Posts: 55

Re: Entire filesystem ported to SD card, EXT3

« Reply #2 on: December 18, 2009, 09:28:24 AM »

The speed is right at bearable. There is a noticeable delay when you launch apps or whatnot, but it's workable. Any slower and it would be too much for a daily use phone.

I ordered a class 6 card last night so we shall see soon enough!


	Logged

datajosh

Newbie

Cookies: 0
Posts: 22

Re: Entire filesystem ported to SD card, EXT3

« Reply #3 on: December 18, 2009, 10:52:38 AM »

Quote from: glitch77 on December 18, 2009, 09:28:24 AM

I'll be very interested to see if a Class 6 card makes a noticeable improvement. I'm getting a 16GB Class 6 card for my Moment soon and it's starting to sound like it might be a good time to do so.


	Logged

maxdamage2122

Newbie

Cookies: 0
Posts: 14

Re: Entire filesystem ported to SD card, EXT3

« Reply #4 on: December 18, 2009, 11:42:08 AM »

So what your saying is it runs perfectly well without rfs and yaffs instead? So whats stopping us from partitioning the onenand and using yaffs? Sorry if you guys commented on this already but i've been busy with finals.


« Last Edit: December 18, 2009, 11:44:32 AM by maxdamage2122 »	Logged

peepsalot

Jr. Member

Cookies: 8
Posts: 90

Re: Entire filesystem ported to SD card, EXT3

« Reply #5 on: December 18, 2009, 01:12:33 PM »

Quote from: maxdamage2122 on December 18, 2009, 11:42:08 AM

So what your saying is it runs perfectly well without rfs and yaffs instead?

No one said anything about yaffs, try reading again.

Quote from: maxdamage2122 on December 18, 2009, 11:42:08 AM

So whats stopping us from partitioning the onenand and using yaffs? Sorry if you guys commented on this already but i've been busy with finals.

What's stopping us from using yaffs on OneNAND is the lack of tools, namely MTD. Support for mtd has to be compiled into the kernel, in addition to some binary utilities that must be cross compiled.


	Logged

bpedman

Newbie

Cookies: 0
Posts: 6

Re: Entire filesystem ported to SD card, EXT3

« Reply #6 on: December 18, 2009, 02:23:52 PM »

So, this means we can at least do some changes to the system, e.g. themeing, not upgrading since the kernel probably wouldn't support it

Or am I mistaken and we can already write to /dev/stl5?...probably wouldn't be a good idea while the phone is running though


	Logged

colk

Newbie

Cookies: 0
Posts: 8

Re: Entire filesystem ported to SD card, EXT3

« Reply #7 on: December 18, 2009, 03:00:48 PM »

Dont we have the mtd stuff already built in (at least the source for it in the samsung open source zip


	Logged

peepsalot

Jr. Member

Cookies: 8
Posts: 90

Re: Entire filesystem ported to SD card, EXT3

« Reply #8 on: December 18, 2009, 03:24:02 PM »

Quote from: colk on December 18, 2009, 03:00:48 PM

Dont we have the mtd stuff already built in (at least the source for it in the samsung open source zip

Yes the source is in the kernel tree, but it's not configured to be compiled in.


	Logged

oxsolid

Newbie

Cookies: 1
Posts: 46

Re: Entire filesystem ported to SD card, EXT3

« Reply #9 on: December 18, 2009, 04:24:41 PM »

So, connecting the dots a bit...

A system can run completely off of the SD card (this might mean that we can run any system we want since we can point to a non-standard location)

We hopefully can create a modified kernel to add in yaffs support via MTD (but this is still difficult to do and were not exactly sure the steps to continue)

then we can upload this new kernal, but this isn't foolproof yet, and i believe our recovery method isn't failsafe as well... (this is going to be touchy but not as difficult as creating the new kernal with the MTD)

(we can't mess with the second boot loader at all because were comlpetely in the dark about that)

Once the new kernal is up and running and assuming that we have yaffs support, then we can add new systems to the SD card or the nand, but to be safe we should start with the SD

and after ironing out the bugs a bit then it will just be a matter of porting other phones builds (such a Cyanogen)

and if it works really well and reliably, then we will put it strickly on the nand.... (i'm not sure if there is an issue writing to the nand, so that also may be another hurdle)

now all of this seems waaaaay more optimistic than the earlier talks... and it's clear that we got kindof lucky considering that we have some code to add in yaffs... but it is still going to take someone really smart to get it working properly.

assumming that we can enable the yaffs: everything else should be systematic... tough... but doable

please correct me if i'm off on this assesment, but i think it's close to accurate


« Last Edit: December 18, 2009, 04:28:39 PM by oxsolid »	Logged

Pages: [1]

« previous next »

News: Do you like Samsung Moment?
Scratch-Proof your Samsung Moment Best Price on Sprint Phones Screen Protection	Latest Ringtone for your mobile