Differences between revisions 7 and 8
Revision 7 as of 2009-03-16 03:35:05
Size: 1890
Editor: anonymous
Comment: converted to 1.6 markup
Revision 8 as of 2010-08-27 15:43:13
Size: 1969
Comment: + it link + minor fixes
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
||<tablestyle="width: 100%;" style="border: 0px hidden">~-Translation(s): none-~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]|| ||<tablestyle="width: 100%;" style="border: 0px hidden">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[it/RescuingSystemWithDamagedVarFilesystem|Italiano]]-~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]||
Line 13: Line 13:
Because the /var directory contains regularly updated data, it is more susceptible of corruption than filesystems containing fixed data, such as /usr. It is recommended that /var is placed into its own filesystem, to minimise damage in the event of a filesystem problem. If disaster happens, it may be necessary to rebuild the /var directory to rescue your Debian system. Because the {{{/var}}} directory contains regularly updated data, it is more susceptible of corruption than filesystems containing fixed data, such as {{{/usr}}}. It is recommended that {{{/var}}} is placed into its own filesystem, to minimise damage in the event of a filesystem problem. If disaster happens, it may be necessary to rebuild the {{{/var}}} directory to rescue your Debian system.
Line 17: Line 17:
Obtain the skeleton content of the /var directory from a minimum working Debian system based on the same or older Debian version. Now run [[dselect]], and this will hopefully provide a working system. Obtain the skeleton content of the {{{/var}}} directory from a minimum working Debian system based on the same or older Debian version. Now run [[dselect]].

Translation(s): English - Italiano

(!) ?Discussion


Rescuing a system with a damaged /var filesystem

Because the /var directory contains regularly updated data, it is more susceptible of corruption than filesystems containing fixed data, such as /usr. It is recommended that /var is placed into its own filesystem, to minimise damage in the event of a filesystem problem. If disaster happens, it may be necessary to rebuild the /var directory to rescue your Debian system.

Use a skeleton from a minimum working system

Obtain the skeleton content of the /var directory from a minimum working Debian system based on the same or older Debian version. Now run dselect.

This should provide a working system.

Obtaining a list of already installed packages

Following restore of the Debian system, the Package Database may not have the correct information about which packages are already installed. However, because each currently installed package has documentation installed in /usr/share/doc, it is possible to use this list to populate the list of packages to be installed by the package mananger:

 ls -1 /usr/share/doc | \
 # Ignore the texmf document tree and debian utilities/keyrings
 sed -e '/^texmf$/d' -e '/^debian$/d' -e 's/.*/\0 install/' | \
 dpkg --set-selections

The dselect tool can now be used to install the selected packages.


CategorySystemRescue