Hi,
I would like to know if there is a special procedure to install geeXbox 3 on a flash module, in order to limit write access?
My module is seen as a standard HDD (no TRIM feature)…
Thanks.
PS: is there a huge benefit to install a amd64 version on a Athlon 64 X2 proc, or is a i386 version enough? I have often read that i386 versions (not only for geeXboX) are more stable…
better to use native build for your cpu …
regarding your disk, boot with “elevator=noop” ?
that’s the default option for panda on sd-card
What is elevator=noop option for?
As far as I understand, this will boost up I/O access, but I didn’t read anything about limiting unecessary write access…
I was more thinking about a solution like for booting from USB key, but I don’t know if it will work with the automatic installer (as my flash module is not USB).
How can I achieve the same kind of installation manually?
hum, one solution is maybe external-ersistent …..
mount disk on initrd, read , data, umount it, store the system in ram, store data on disk when shutting down the system
it was used for ntfs partitons , but why not for you ?
Contact me via mail for this. it need a little efforts
BR
Tom
Mmm, I don’t like the fact that you write back persistent data only when shuting down. This means that you loose everything when you have to reset system (which occurs often, I will open a new thread soon).
