Package: uswsusp
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Thursday, September 20, 2007, I notified you of the beginning of a review
process
concerning debconf templates for uswsusp.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes are suggested, and if you have any
objections, let me know in the next 3 days.
Please try to avoid uploading uswsusp with these changes right now.
The second phase of this process will begin on Wednesday, October 10, 2007,
when I will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Wednesday, October 31, 2007. Please avoid uploading a package with fixed
or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around <DAY25>, I will contact you again and will send a final patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- uswsusp.old/debian/uswsusp.templates 2007-09-16 22:51:22.504558107
+0200
+++ uswsusp/debian/uswsusp.templates 2007-10-07 08:41:39.765151724 +0200
@@ -1,35 +1,48 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [EMAIL PROTECTED] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: uswsusp/resume_device
Type: select
Choices: ${list}
-_Description: The swap space to resume from:
- To be able to suspend your system, uswsusp needs a swap partition or file
- to write a snapshot of your system to. Provided is a list of suitable swap
- spaces, sorted by size, the largest first.
+_Description: Swap space to resume from:
+ To be able to suspend the system, uswsusp needs a swap partition or file
+ to store a system snapshot. Please choose the device to use, from the
+ list of suitable swap spaces, sorted by size (largest first).
Template: uswsusp/resume_offset
Type: string
Description: Offset of swap file's header:
- When using a swap file for storing the snapshot during suspend, you need to
- specify where the swap file's header is located. This parameter specifies this
- location, in <PAGE_SIZE> units, as the offset from the beginning of the
+ When using a swap file for storing the snapshot during suspend, the
+ location of the swap file's header must be specified. This will be
+ stored in <PAGE_SIZE> units, as the offset from the beginning of the
partition that contains the swap file.
Template: uswsusp/no_swap
Type: error
-_Description: No swap space found; userspace software suspend will not work
- To be able to suspend your system, uswsusp needs a swap partition or file to
- write a snapshot of your system to. Your system doesn't seem to have such a
- space. Please make one, preferably with twice the size of your physical ram.
- Then run dpkg-reconfigure or setup the configuration file yourself.
+_Description: No suitable swap space for software suspend
+ To be able to suspend the system, uswsusp needs a swap partition or file to
+ write a system snapshot to. No such space seems to be available for this.
+ .
+ You should create a swap partition or file, preferably twice the size of the
system's
+ physical RAM.
+ .
+ Then, run 'dpkg-reconfigure uswsusp' or edit the configuration file
+ manually.
Template: uswsusp/no_snapshot
-Type: note
-_Description: Your kernel doesn't support userspace software suspend
- Your kernel doesn't support userspace software suspend. Please reconfigure
- your kernel to include CONFIG_SOFTWARE_SUSPEND=y and recompile.
+Type: error
+_Description: No userspace software suspend support in the kernel
+ The current kernel doesn't support userspace software suspend. Please
+ recompile the kernel with the 'CONFIG_SOFTWARE_SUSPEND=y' option.
Template: uswsusp/continue_without_swap
@@ -37,138 +50,144 @@
Default: true
_Description: Continue without a valid swap space?
The swap file or partition that was found in uswsusp's configuration
- file is not active. In most cases this means userspace software suspend will
- not work for you and you will need to choose (or let uswsusp choose) another
- swap space. In some corner cases however, this can be what you want.
+ file is not active.
+ .
+ In most cases this means userspace software suspend will
+ not work as expected. You should choose another
+ swap space.
+ .
+ However, in some rare cases, this configuration may be intentional.
Template: uswsusp/snapshot_device
Type: string
_Description: The device node through which uswsusp can talk to the kernel:
- If you leave this empty, you will get the hardcoded default, /dev/snapshot.
- This should be OK in almost all cases, don't change this unless you have a
+ If this is empty, the hardcoded default, /dev/snapshot, is used.
+ This should be OK in almost all cases. Don't change this unless there is a
good reason to do so.
Template: uswsusp/image_size
Type: string
_Description: Preferred maximum image size:
- You can specify the preferred maximum image size (in bytes). This is not a
hard
- bound; the uswsusp tool will do its best to limit the image size as specified
- by this parameter, but if that's not possible, it will suspend the system
- anyway with a bigger image. If this value is set to 0, the snapshot image will
- be as small as possible. If you leave it empty you get the hard coded default,
- which is 500MB. The default value you are presented with is 45% of the memory
- available on your system, this is not the maximal size, but some additional
- free memory speeds up the suspend and resume process.
+ Please specify a maximum system snapshot image size (in bytes).
+ .
+ This limit is not strict; the uswsusp does its best to respect it,
+ but will exceed the specified limit if suspend needs a bigger image.
+ .
+ Using 0 here will enforce the use of the smallest possible snapshot
+ image. An empty value will use the hard coded default, which is
+ 500MB. The default value is 45% of the system's memory: this is not
+ the maximal size, but some additional free memory speeds up the
+ suspend and resume process.
Template: uswsusp/suspend_loglevel
Type: string
-_Description: Log level:
- You can specify the kernel console loglevel which the s2disk/s2both and resume
- utilities will use to report progress. On a stock kernel, messages with
- level higher then 7 are usually not shown.
+_Description: Log level for software suspend:
+ Please specify the kernel console log level which the s2disk/s2both
+ and resume utilities will use to report the progress of suspend and
+ resume. On a stock kernel, messages with levels higher than 7 are
+ usually not shown.
Template: uswsusp/max_loglevel
Type: string
_Description: Maximal log level:
- You can specify the kernel console loglevel which the resume utility will use
- in case the resume fails.
+ Please specify the kernel console log level which the resume utility will use
+ if the resume fails.
Template: uswsusp/compute_checksum
Type: boolean
Default: false
_Description: Perform checksum on image?
- Performing a check sum using the MD5 algorithm to verify the image
- integrity is slightly safer, but also takes slightly more time.
-
+ Performing a checksum using the MD5 algorithm to verify the image
+ integrity is slightly safer, but also takes more time.
Template: uswsusp/compress
Type: boolean
Default: true
_Description: Compress image?
- Compressing the image with LZF compression algorithm will result in a
+ Compressing the image with the LZF compression algorithm will result in a
smaller image, which makes it possible to suspend with a smaller swap
- partition. Generally it will also make reading and writing the image faster
+ partition. Generally, it will also make reading and writing the image faster
because there is less to read and write.
-
Template: uswsusp/early_writeout
Type: boolean
Default: true
_Description: Perform early write out?
- uswsusp can start syncing the resume device early in the process of writing
- the image to it. This has been reported to speed up the suspend on some
- boxes and eliminate the "fast progress meter and long fsync wait" effect.
-
+ The synchronization of the resume device can start early in the
+ process of writing the image to it. This has been reported to speed
+ up suspend on some systems and eliminate the 'fast progress meter and
+ long fsync wait' effect.
Template: uswsusp/splash
Type: boolean
Default: true
_Description: Show splash screen?
- Instead of informative output you can enjoy a nice splash screen with progress
- bar during the suspend and resume process. For this to work you will need to
- have the splashy package installed.
-
+ Instead of informative output, a splash screen with progress bar can
+ be shown during the suspend and resume process. This requires the splashy
+ package to be installed.
Template: uswsusp/encrypt
Type: boolean
Default: false
_Description: Encrypt snapshot?
- For added security it is possible to encrypt the snapshot of your system
+ For increased security, it is possible to encrypt the snapshot
that is written to disk during suspend. On resume (and suspend if you don't
- you use an RSA key) you will be asked to provide a passphrase. With encryption
- the suspend and resume process will take significantly more time.
+ use an RSA key), you will be prompted for a passphrase. Encryption
+ adds a significant time to the suspend and resume processes.
Template: uswsusp/RSA_key_file
Type: string
Default: /etc/uswsusp.key
_Description: Path to RSA key file:
- To avoid being prompted for a passphrase during suspend every time, one can
- supply an RSA key which will be used to encrypt the image. This option takes
- the path to that file. The default path will be good for most people. If
- you don't want to use an RSA key, leave this empty.
+ To avoid the need for a passphrase prompt during each suspend, an RSA
+ key can be used to encrypt the image.
+ .
+ Please specify the path to that file. Leave this field empty to
+ not use an RSA key.
Template: uswsusp/create_RSA_key
Type: boolean
Default: false
-_Description: Create RSA key?
- The key necessary for using the RSA encryption scheme can be generated for
you.
+_Description: Create an RSA key?
+ The key necessary for using the RSA encryption scheme can be generated now.
You will be prompted for a passphrase.
Template: uswsusp/RSA_key_bits
Type: string
Default: 1024
-_Description: RSA key bits:
- The number of bits (between 1024 and 4096 inclusive) the RSA key will have.
- The more bits, the more secure, but also slower operation.
+_Description: RSA key size:
+ Please specify the size of the RSA key (number of bits between 1024
+ and 4096). A bigger key increases the encryption strength but slows
+ down the encryption process.
Template: uswsusp/RSA_passphrase
Type: password
_Description: RSA passphrase:
- This is the passphrase you will have to type on every resume to decrypt the
+ Please choose the passphrase to use on every resume to decrypt the
image.
Template: uswsusp/RSA_passphrase_v
Type: password
-_Description: RSA passphrase (again):
- To verify you know what you just typed, type the passphrase again.
+_Description: RSA passphrase confirmation:
Template: uswsusp/shutdown_method
Type: select
-Choices: reboot, platform, poweroff
+__Choices: reboot, platform, poweroff
Default: platform
Description: Shutdown method:
- If the "shutdown method" parameter is set to "reboot", the s2disk utility will
- reboot the machine rather than powering down. This is useful when testing
- repeated benchmarks, such as when checking whether "early writeout" produces a
- speedup or not for your combination of hardware, image size, and s2disk
- parameters.
+ If this parameter is set to 'reboot', the s2disk utility will
+ reboot the machine rather than powering down. This can be useful
+ for testing purposes.
+ .
+ If it is set to 'platform', hardware-specific optimization is used
+ if available.
--- uswsusp.old/debian/control 2007-09-16 22:51:22.504558107 +0200
+++ uswsusp/debian/control 2007-10-04 07:21:26.676993999 +0200
@@ -11,17 +11,17 @@
Recommends: initramfs-tools (>= 0.74), mount (>= 2.12r-17)
Suggests: splashy (>= 0.3)
Description: tools to use userspace software suspend provided by Linux
- uswsusp (also known as µswsusp or simply suspend) contains the programs to
- use the userspace software suspend facility available in Linux kernel
- 2.6.17-rc1 and higher. It enables you to save the state of the whole system
- to disk and power off your system. After restarting your system it will be
- put back in the exact system state you left it (this is sometimes called
- hibernation).
+ This package (also known as µswsusp or simply suspend) contains the
+ programs to use the userspace software suspend facility available in
+ Linux kernels 2.6.17-rc1 and higher. It allows the system to have its
+ state saved to disk and be powered off. On restarting, it will be put
+ back in the state it was left in (this is sometimes called
+ hibernation).
.
- It also includes a program to suspend-to-ram after the state is saved to disk.
- In the suspend-to-ram state the system still uses power, but is faster in
- resuming. In case the battery depletes the state is still on disk and
- resume can continue without data loss.
+ It also includes a program to suspend the system to RAM after the
+ state is saved to disk. In that state, the system still uses power,
+ but resuming is faster. If the battery depletes, the state is
+ resumed from disk without data loss.
.
Optional features include encrypting the system snapshot and a themeable
splash screen during the suspend and resume processes.
