Jump to: navigation, search

Restorer v2

61 bytes added, 16:38, 23 July 2020
Grammar fix.
The current way of restoring from images is quite straightforward -- we just fork the necessary amount of tasks, then each of them starts "dressing" itself based on the data from image files. Sometimes shared resources appear, e.g. files inherited or sessions inherited on fork, or CLONE_XXX objects. With these we write code, that handles only this type of resources -- files a are sent to co-owners via unix sockets, CLONE_XXX stuff is pre-created on fork stage. Sometimes more interesting dependencies arise, for example -- [[invisible files]]. These are also special-cared.
All this is not nice. We believe, that the restoring process can (and should) look better. Like this.
FORK: {T(..)(.*)} -> {T\1N\2}|{N\1} // T forks N
EXIT: {I(..)(.*)}(.*){X(..)(.*)} -> {I\1\2\5}\3 // X exits and all its kids are reparented to I (init)
SETSID: {S(.)(.)(.*)} -> {SSS\11S\3} // S becomes a new session leaderSETPGID(0): {P(.)(.)(.*)} -> {PPP\1P2\3} // P becomes a new group leaderSETPGID(G): {GGGS(.*)G}(.*)}{P(.)S(.*)} -> {GGS\1}\2{PGS\4} {P(.)S(.*)}(.*){GGS(.*)} -> {G\1GPGS\2}\3{P\4GGGS\64} // P joins session group of alive G
[[Category: Plans]]
[[Category: Thinkers]]

Navigation menu