On Tuesday, April 17, 2012 10:57:11 AM UTC-4, Glenn Kasten wrote:
>
> One solution I've seen for this kind of problem is to have a separate
> 'factory' filesystem
> which is mounted read/write during factory provisioning, but then is
> mounted read-only
> during normal operation. This is also
Sorry, creating Linux filesystems are not my area of expertise.
I suggest asking about this on either android-kernel group, or your
question might
not be specific to Android so you could do a web search for "Linux
filesystems".
Once you have a filesystem in place, you'll need to mount it,
typicall
Hi gkasten,
Thanks you for your information..
could you brief about your solution? how can i create factory file system?
how can i provide access to android application?
Thanks & Regards
Garimella Srinivasu
On Tue, Apr 17, 2012 at 8:27 PM, Glenn Kasten wrote:
> One solution I've seen for this
One solution I've seen for this kind of problem is to have a separate
'factory' filesystem
which is mounted read/write during factory provisioning, but then is
mounted read-only
during normal operation. This is also a good place to store
information such as camera calibration data.
On Apr 16, 9:
Hi gsksten,
Thank you for your reply..
My requirement as below..
At the time of verry first boot, factory people should select branding of
my device(we are supporting multiple types of branding) and based on this
selection second time onwords device will boot with respective
Brands(different Bra
The root file system / is typically a small read-only RAM filesystem
which is just used as a place to mount the other filesystems such as /
system and /data, to hold special filesystems like /proc and /sys, and
to store the init executable and startup scripts such as init.rc. It's
not intended or s
