This shows you the differences between two versions of the page.
Owl:disk-partitions [2011/05/22 03:23] solar added two more examples |
Owl:disk-partitions [2011/05/24 14:35] (current) solar re-ordered the shell commands sequence that moves stuff under /space (the old sequence was buggy) |
||
---|---|---|---|
Line 14: | Line 14: | ||
We use the ''/space'' filesystem to reduce the size of and number of writes onto the boot and root filesystem (thereby improving its reliability). Here's an example of what may be moved onto ''/space'' (right after initial installation): | We use the ''/space'' filesystem to reduce the size of and number of writes onto the boot and root filesystem (thereby improving its reliability). Here's an example of what may be moved onto ''/space'' (right after initial installation): | ||
- | cd / | ||
- | mv home space/ && ln -s space/home | ||
- | mv vz space/ && ln -s space/vz # unless a separate filesystem was created for /vz | ||
- | cd /usr | ||
- | mv src ../space/ && ln -s ../space/src # in case you intend to do any builds from source under /usr/src or /usr/src/world | ||
service syslog stop; service postfix stop # if these were started already | service syslog stop; service postfix stop # if these were started already | ||
cd /var | cd /var | ||
mv account log run spool ../space/ | mv account log run spool ../space/ | ||
ln -s ../space/* . | ln -s ../space/* . | ||
+ | cd /usr | ||
+ | mv src ../space/ && ln -s ../space/src # in case you intend to do any builds from source under /usr/src or /usr/src/world | ||
+ | |||
+ | cd / | ||
+ | mv home space/ && ln -s space/home # unless a separate filesystem was created for /home | ||
+ | |||
+ | cd / | ||
+ | mv vz space/ && ln -s space/vz # unless a separate filesystem was created for /vz | ||
Any additional software installs are typically done into OpenVZ containers, not onto the host system, which is why we're able to keep the root filesystem small (only leaving some room for upgrades to future versions of Owl itself). In fact, the OpenVZ security model assumes that the host system is only used to control the containers, not to run any services not essential to that purpose. | Any additional software installs are typically done into OpenVZ containers, not onto the host system, which is why we're able to keep the root filesystem small (only leaving some room for upgrades to future versions of Owl itself). In fact, the OpenVZ security model assumes that the host system is only used to control the containers, not to run any services not essential to that purpose. |