Archive:Drive Mapping: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
>Malloc
No edit summary
>Malloc
No edit summary
Line 10: Line 10:
Proposal:<br/>
Proposal:<br/>
Q = system<br/>
Q = system<br/>
This is where we install stuff, it never changes (except on update), it's not writable<br/>
This is where we install stuff, it never changes (except on update), it's not writable<br/><br/>
Z = Temporary<br/>
Z = Temporary<br/>
This is where we store file temporarily.  It's not shared between users/instances/runs.  Very volatile.<br/>
This is where we store file temporarily.  It's not shared between users/instances/runs.  Very volatile.<br/><br/>
U = No idea what to call this<br/>
U = No idea what to call this<br/>
Store mutable data here which doesn't belong to any user.  Is there anything we need besides profiles.xml?<br/>
Store mutable data here which doesn't belong to any user.  Is there anything we need besides profiles.xml?<br/><br/>
P = profiles<br/>
P = profiles<br/>
Give some default profile to begin with, can create more profiles.  If some file doesn't exist in here, read from Q.  On write, copy from Q and make changes.<br/>
Give some default profile to begin with, can create more profiles.  If some file doesn't exist in here, read from Q.  On write, copy from Q and make changes.<br/><br/>

Revision as of 22:22, 2 July 2008

Proposed drive mappings

Currently:
U = UserData
Q = System (should not be writable)
P = Profile
Z = Temporary
T = ?

Proposal:
Q = system
This is where we install stuff, it never changes (except on update), it's not writable

Z = Temporary
This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.

U = No idea what to call this
Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml?

P = profiles
Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.