The fs2ram package introduced new or modified debconf templates. This is often a good moment for a review to help the package maintainer following the general suggested writing style and track down typos and errors in the use of English language. A bug report has been sent against the package: 679869 If someone wants to pick up this review, please answer to this mail, in the mailing list, with an [ITR] (Intent To Review) label. The templates file is attached. To propose the file you reviewed for peer review, please send a [RFR] (Request For Review) mail with the reviewed file attached...then a few days later, when no more contributions come, a summary mail with a [LCFC] (Last Chance For Comments) label. These RFR and LCFC mails should CC the opened bug report. Finally, after no more comments coming to the LCFC mail, you can send the reviewed templates file in the bug report. Then, please notify the list with a last mail using a [BTS] label with the bug number. Helping the package maintainer to deal with induced translation updates at that moment will be nice. If you're not comfortable with that part of the process, please hand it off to a translator. --
Template: fs2ram/main_install_type
Type: select
__Choices: Content-preserving, Structure-preserving, Unconfigured
Default: Content-preserving
_Description: fs2ram configuration
Please select the fs2ram configuration that best meets your needs.
.
* Content-preserving: /var/tmp, /var/cache, and /var/log will be in
RAM, reducing writes to the hard drive, and fs2ram will preserve the
contents of these file systems across reboots.
* Structure-preserving: /var/tmp, /var/cache, and /var/log will be in
RAM, but fs2ram will only preserve their directory structures across
reboots, not their (potentially private) contents.
* Unconfigured: the fs2ram configuration file will be left empty and
must be filled manually.
Template: fs2ram/rcs_enforce_ramtmp_configuration
Type: boolean
Default: true
_Description: Make /tmp into RAM file systems?
Please choose whether /tmp should be converted into tmpfs
mountpoints. This is not the default for fresh installs of Debian.
Template: fs2ram/rcs_enforce_ramlock_configuration
Type: boolean
Default: true
_Description: Make /var/lock into RAM file systems?
Please choose whether /var/lock should be converted into tmpfs
mountpoints. This is the default for fresh installs of Debian.
Source: fs2ram
Section: admin
Priority: optional
Maintainer: Philippe Le Brouster <plb@nebkha.net>
Build-Depends: debhelper (>= 9~)
Standards-Version: 3.9.3
DM-Upload-Allowed: yes
Package: fs2ram
Architecture: all
Depends: ${misc:Depends}, ucf
Description: tools to preserve tmpfs contents across reboots
fs2ram manages temporary file systems across reboots. Each tmpfs mountpoint
can be associated with a pre-mount script, which is executed by fs2ram at
each shutdown/reboot before the file system is unmounted. The pre-unmount
script must print a post-mount script on standard output, which is saved and
then run at boot time after fs2ram mounts the corresponding file system.
.
This package provides two pre-unmount scripts designed to preserve folder
structure and file permissions across reboots: this is needed to allow
hierarchies suc as /var/cache or /var/log to be mounted as tmpfs.
Attachment:
signature.asc
Description: Digital signature