Jacek Bukarewicz summarized all issues till now in 
https://bugs.tizen.org/jira/browse/PTREL-156. 

Some important changes about fixing filesystem, which is merged on 7th but 
still SR is not raised by maintainer
https://review.tizen.org/gerrit/#/c/11478/
I think Jinkun or Praj can raise the SR for this. Let's do it asap and do not 
delay it further. 

Lukasz is working on fstab issue and he has requested one package in git 
profile/mobile/setup-mobile
Concerned please check this JIRA: https://bugs.tizen.org/jira/browse/TINF-353
Again, I think in this case Jinkun & Praj make it fast. 

Let's work on this issue collectively and make RD-PQ bootable at the earliest. 

BR, 
Anuj
------- Original Message -------
Sender : Artem Bityutskiy<[email protected]>
Date : Nov 13, 2013 01:23 (GMT+09:00)
Title : Re: [Dev] RD-PQ tizen.org image status

On Tue, 2013-11-12 at 16:38 +0100, ?ukasz Stelmach wrote:
> > Indeed, you can always re-run the script and as part of a recovery
> > procedure.
> 
> Good idea. Where is the environment saved?

It is not saved at the moment, but could be saved. Also, the MIC
environment and run-time one may be different, so a recovery script/tool
could need to amend it.

For example, in recovery environment your rootfs may be on a little
rescue ramdisk, and the real root may be at '/mnt/root', then your
INSTALLERFW_MOUNT_PREFIX will be '/mnt/root', while it is '/' in MIC
environment.

> The fstab script indeed may be generic enough to make it part of the
> platform/upstream/setup[1]
> 
> [1] https://review.tizen.org/git/?p=platform/upstream/setup.git;a=summary

Not sure. In mobile you may want to refer partitions as /dev/mmcblockX,
or by File-system UUID. In IVI we now use PARTUUID (partition UUID),
tomorrow we may need something else. So the fstab one really sounds like
profile-specific.

But other scripts, if we get more of them, could co to setup.git,
probably. I cannot come up with an example though.

-- 
Best Regards,
Artem Bityutskiy

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to