Hi List, We're now bring up new Intel reference device with Tizen 3.0 mobile, see https://bugs.tizen.org/jira/browse/PTREL-563 if you're interested in.
One major issue we met is that /opt/var bind mount to /var so the files in /var are hidden in the system. In another mean, all files in /var are can not be accessed. This does introduce some problems, for example, rpm doesn't work because it installed its db into /var/lib; Xorg can not launch because no /var/log directory there, maybe more. So these issues make us thinking again about /opt/var VS /var. IIRC, Karol introduced bind mount /opt/var to /var and hope we can finally get a readonly / fs, that's really a fantastic feature of Tizen. We can get a lot from a readonly / fs, e.g. more simple FOTA, factory reset, compressed / and so on. However, the problem here is that there are a lot files installed into /var but /var will be a bind mount point of /opt/var. So I submitted a change for "filesystem" package that https://review.tizen.org/gerrit/#/c/14576/ https://review.tizen.org/gerrit/#/c/14577/ 1. mv /var contents into /opt/var and create 2. create /var as a link to /opt/var So at image creating stage, once filesystem installed, /var is a link to /opt/var, then all the later installed packages which install files into /var in fact lands to /opt/var. What I prefer a link to bind mount is bind mount needs to be done in every system boot, cost boot time but the link doesn't. -- Thanks, Chengwei
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
