On Thu, Jan 09, 2014 at 08:12:59AM +0200, Ylinen, Mikko wrote: > > > > On Thu, Jan 9, 2014 at 1:58 AM, Yang Chengwei <[email protected]> wrote: > > On Wed, Jan 08, 2014 at 07:34:55AM -0800, Thiago Macieira wrote: > > On quarta-feira, 8 de janeiro de 2014 15:57:48, Dominig ar Foll wrote: > > > >> First thing first, do we still need the read-only / feature? Do we > > > >> have this feature requirement in Tizen 3.0? > > > > > > Having / as read only is a common and logical requirement for embedded > > > system. > > > I do not see why Tizen 3 would remove that requirement. > > > > But since /var must be writable, then /var must be a mount (either of a > > device, sub-volume or bind/move mount). > > > > I guess Chengwei's original problem can be solved by having nothing on > the > > root mount's var subdir. It should be simply empty. All data that needs > to be > > seen during runtime needs to come from the actual var mount. > > Yes, the /opt is a separate filesystem in Tizen, which as I know is > target to store user data, apps, apps data and etc. > > > I think we'd need to revisit the usage of /opt in 3.0 and put the patch on > hold > for a while. > > For example, the multiuser support will move user data under $HOME.
Could you point me where can I find the latest document about this proposal? -- Thanks, Chengwei > > -- Mikko
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
