[SCM] live-manual branch, debian, updated. debian/2.0_a12-1-52-g54ab401
Ben Armstrong
synrg at debian.org
Sat Dec 11 18:20:00 UTC 2010
The following commit has been merged in the debian branch:
commit 54ab40114eb07dbfd55013f8d80a1843367f4173
Author: Ben Armstrong <synrg at debian.org>
Date: Sat Dec 11 14:19:53 2010 -0400
Removing remaining out of date material, allowing #597057 to be finally closed.
diff --git a/manual/de/live-manual.ssm b/manual/de/live-manual.ssm
index 65fe9b5..b8e4233 100644
--- a/manual/de/live-manual.ssm
+++ b/manual/de/live-manual.ssm
@@ -63,6 +63,3 @@
<< user_examples.ssi
-% << other_faq.ssi
-
-% << other_howtos.ssi
diff --git a/manual/de/other_faq.ssi b/manual/de/other_faq.ssi
deleted file mode 100644
index f754913..0000000
--- a/manual/de/other_faq.ssi
+++ /dev/null
@@ -1,545 +0,0 @@
-B~ Frequently asked questions (FAQ)
-
-1~ Frequently asked questions (FAQ)
-
-Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A:
-See "Copying USB/HDD image to a USB stick" % FIXME: <xref
-linkend="image_copying"/>
-
-Q: How do I log my build? A: You could use script, screen or tee: #{$
-lh_build 2>&1 | tee build.log}#
-
-Q: How can I convert an already installed standard Debian partition into a
-Debian Live system? A: Save the list of installed packages and load it into
-your new Debian Live System. Copy your /etc to config/chroot_local-includes
-
-Q: What does 'losetup: could not find any free loop device' mean and how do
-I fix it? A: Loop devices are used during the build; there probably aren't
-any free if you've aborted several builds. Something like: for l in
-/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6
-/dev/loop7 ; do losetup -d $l ; done should rectify the situation (assuming
-all loop devices in use were created by lh_build; if in doubt, check the
-contents of each loop device before deleting them with losetup -d).
-
-Q: How do I launch an interactive shell during the chroot stage? A: To
-enable interactive shell: #{$ lh_config --interactive shell}# To continue
-the build process: #{# logout}# or #{# exit}# To disable interactive shell,
-set LH_INTERACTIVE to "disabled" in config/chroot.
-
-Q: What is the root /user password? A: The user password for the live user
-is 'live'. By default, there is not any root password. You can switch to
-root with ${sudo -i}# or set a password for root with #{sudo passwd}#
-
-Q: How do I change root or any user password? A: Add a chroot local hook
-script to change root or any user password each time you build an image.
-e.g. config/chroot_local-hooks/01-update_password.sh to set root password to
-"nopasswd"
-
-code{ #!/bin/sh
-
-echo "I: update password" echo "root:nopasswd" | chpasswd
-
-$ chmod +x config/chroot_local-hooks/01-update_password.sh
-
-}code
-
-Note for live user; you need to copy the
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser your build folder:
-
-code{
-
-mkdir -p
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-
-}code
-
-Note: Then edit the
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-and paste in the new user_crypted password that you make with: #{echo
-"newlivepass" | mkpasswd -s}#
-
-Or add an hook file in config/chroot_local-hooks/ with something like the
-below:
-
-code{ #!/bin/sh
-
-# Change the autogenerated user password to "debianlive"
-plain_password="debianlive" password=$(echo "${plain_password}" | mkpasswd
--s)
-
-sed -i -e 's/\(user_crypted=\)\(.*\)\( #.*\)/\1\"'${password}'\"\3/'
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-
-update-initramfs -tu -kall }code
-
-The latter (hook model) could be more future proof than the former solution
-since it modifies just one string selectively but it requires the package
-"whois" to be installed on the target system (for mkpasswd) or that you
-generate the $password string not at build time and include it crypted in
-the above script.
-
-Q: How to disable autologin? A1: use the commandline parameter #{lh config
---bootappend-live "noautologin"}# A2: You need to set boot=noautologin
-noxautologin as described in man live-initramfs If you boot via TFTP you
-want to insert the option to pxelinux.cfg/default
-
-Q: How do I change default hostname or username? A: To change default
-hostname or username: #{$ lh_config --hostname myhostname $ lh_config
---username myusername}#
-
-Q: How do I make the final image smaller? A: Clean orphaned apps/libs:
-Install package "deborphan" and then run 'sudo deborphan -n' . Delete
-unwanted packages. Remove the apt cache. Purge unwanted locales (see
-"localepurge" package).
-
-Q: How do I customize bash-config permanently (aliases, bash-completion
-etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc
-
-Q: How do I disable services permanently? (Be careful!) A: Add a chroot
-local hook script to disable a service each time you build an image:
-e.g. config/chroot_local-hooks/01-disable_service.sh
-
-code{
-
-#!/bin/sh
-
-echo "I: disable service" update-rc.d -f service_name remove
-
-$ chmod +x config/chroot_local-hooks/01-disable_service.sh
-
-}code
-
-Q: How do I enable | disable the md5checksum at the ISO building? A:
-#{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value.
-
-Q: How to disable the generation of the .tar.gz file? A: #{lh_config
---net-tarball none|gzip}# Or change the LH_NET_TARBALL value. (only
-available in snapsshot version at the moment 2008/Feb/28)
-
-Q: How do I "build a new image"? A: Run commands:
-
-code{
-
-$ sudo lh_clean --binary $ sudo lh_build
-
-}code
-
-Hint: If the configuration had changed you should leave "--binary" out. This
-will clean your chroot directory too.
-
-Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages
-you want.
-
-Create /home/$USERNAME/.dmrc file (default username is "user").
-
-code{
-
-$ cat .dmrc [Desktop] Session=fluxbox }code
-
-Note: .dmrc is owned by $USERNAME:$USERNAME.
-
-See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at
-http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD
-
-Q: How do I use custom repositories? A: See
-http://wiki.debian.org/DebianLive/Configuration
-
-Q: How do I customize the artwork for the live CD (grub or syslinux boot
-splash, usplash, etc.)? A: See
-http://wiki.debian.org/DebianLive/Howto/Custom_Artwork
-
-Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look?
-A: Start the live system in qemu:
-
-code{
-
-$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22
-
-}code
-
-Note: the -redir argument must be changed to meet your needs
-
-Q: How do I execute a custom shell script inside the chroot system after the
-chroot stage? A: Add your script in config/chroot_local-hooks.
-
-Q: How do I add a script running immediately after all other scripts when
-the live system boots? A: Add your script in
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99scrip
-
-code{
-
-$ chmod +x
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99script
-
-}code
-
-Note: The hook script must be executable. Do not forget to lh_clean --chroot
-after making this change before you build again.
-
-You must also use the example script
-/usr/share/live-helper/examples/hooks/update-initramfs.sh to ensure your
-script gets built into the initramfs (read the comment header for
-instructions).
-
-Q: How do I add software not in Debian ? A: See Customizing package
-installation % FIXME: <xref linkend="packages"/>
-
-Q: What is the manifest with Ubuntu used for? A: Manifest is just the
-package list, which ubuntu does $something with. Don't worry about it.
-
-Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude.
-
-Q: Do I need to write the image on USB stick to test it? A: you must use
-qemu >= 0.8.
-
-Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs.
-
-Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed
-something else entirely? A: It is not. It is a package list, not a debconf
-preseeding.
-
-Q: What is the difference between standard and minimal? A: standard:
-packages of priority standard and higher; minimal: packages of priority
-essential and higher;
-
-Q: What can the sections be used for? Aren't they BIG? A: Someone maybe
-wants to include packages from contrib or non-free.
-
-Q: memtest86+ ... is that used? A: Yes
-
-Q: How do I build using predefined packages lists? A: e.g. to build using
-standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo
-lh_build}# Note: The packages lists can be found in
-/usr/share/live-helper/lists/ directory.
-
-Q: How do I rebuild without downloading all the packages again? A: All
-packages are cached in cache subdirectory. They remain until a clean purge:
-#{$ sudo lh_clean --purge}# You do not have to do anything to prevent
-packages from being re-downloaded. You need to remember to clean whichever
-stages you want to rebuild first. e.g. to rebuild from the cached bootstrap,
-chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#
-
-Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make
-a boot CD with grub, configured to boot from a debian-live kernel copied on
-the cd structure #{$ mkdir -p iso/boot/grub && cp
-/usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub && cp chroot/boot/*
-iso/boot/}# Create iso/boot/grub/menu.lst:
-
-code{
-
-default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd)
-kernel /boot/vmlinuz boot=live initrd /boot/initrd.img
-
-}code
-
-Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito
--no-emul-boot \ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn
-the image.
-
-Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A:
-If you have a floppy drive, you may be able to use it, otherwise you will
-need to use loadlin/grub4dos/win32-loader. If you have a second system to
-serve up the image over the network, See
-http://wiki.debian.org/DebianLive/Howto/Creating_a_Netboot_Image
-
-Q: The X configuration does not seems to work, the resolution is too
-low. What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend
-xdebconf && lh_config --packages xdebconfigurator}#
-
-Q: Apache has problems with static files A: Sendfile does not work well on
-the unionfs used by Debian Live. Add the following to apache's
-configuration: #{EnableSendfile off}#
-
-Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right
-now the best is to use a script that will populate the fstab when the CD is
-booting. Such a script can be found at
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh.
-A proper solution based on HAL will be described here in a hopefully near
-future. A: Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL,
-debian-storage-policy-fixed-drives.fdi is not available anymore and the
-previous trick that consisted to remove this file to enable automounting of
-fixed drives as a consequence is obsolete. Eventually, it will be possible
-to combine HAL and PolicyKit to enable different permissions and actions to
-achieve advanced (auto)mounting for non-root users. Until then, because the
-live scripts are only touching to the fstab to add a swap partition if
-discovered at boot time, the only way to have fixed drives mounted
-automatically is to use a script that will populate the fstab file at the
-end of the multiuser runlevel. To achieve this, you can do, for example, the
-following: download the
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh
-script Create the chroot_local-includes/sbin directory, and move the script
-inside Make sure the script is executable (chmod +x diskmounter.sh) create
-the chroot_local-includes/etc/rc.local file and call the diskmounter from
-there (see this
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local
-When called correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32,
-HFS+ and NTFS partitions and mount them read-write, except for NTFS. This
-will change soon and an option will be available to use ntfs-3g to mount
-NTFS as read-write. comments, patches and other things about this script and
-issue: http://code.goto10.org/projects/puredyne/ticket/463
-
-Q: Boot fails with panic: can't open /scripts/live A: Add latest
-live-initramfs deb package into config/chroot_local-packages directory and
-rebuild.
-
-Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref
-linkend="internalization"/>
-
-Q: How do I get past boot prompt without a working keyboard? A: See
-Customizing the bootup process % FIXME: <xref linkend="bootup"/> Note: Boot
-from an USB-HDD on an iMac with GRUB did not work.
-
-Q: Can I serve the root image from a web or ftp server? A: Since
-live-initramfs 1.99, it should be possible to use the fetch= argument on the
-kernel command line. You can build a netboot image as usual, and when you
-are done edit the tftpboot/pxelinux.cfg/default file. Remove the references
-to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url
-where you placed the root image>. You have to include wget in the chroot. It
-could work for other boot methods as well. However, I am not sure the live
-scripts configure the network when booting from a CD or USB disk. #{$
-lh_config --packages wget}#
-
-Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you
-are building an etch image (which was the default up to 2007/09/14) you have
-a very old version of casper which does not support quickreboot and possibly
-other boot parameters as well. You could configure your sources to use
-live-backports (see /usr/share/live-helper/examples/sources/live-backports)
-and switch to live-initramfs, or better yet, build a lenny image instead,
-which is the new default. #{$ lh_config --distribution lenny $ lh_config
---initramfs live-initramfs}#
-
-Q: How do I fix "Could not find kernel image" issue with syslinux
-bootloader? A: Add a binary local hook script to fix kernel and initrd path
-each time you build an
-image. e.g. config/binary_local-hooks/01-fix_syslinux.sh
-
-code{
-
-#!/bin/sh
-
-SYSLINUXCFG=`find binary -type f -name syslinux.cfg`
-
-sed -i "s|kernel /vmlinuz|kernel vmlinuz|g" ${SYSLINUXCFG} sed -i
-"s|initrd=/initrd|initrd=initrd|g" ${SYSLINUXCFG}
-
-$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh
-
-}code
-
-Q: How do I use a newer kernel with lenny? A: A build with backports.org
-kernels will fail as that repository lacks the necessary module packages
-(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports
-http://unsupported.debian-maintainers.org/backports-kernel/ The quick way to
-success:
-
-code{
-
-$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6
-squashfs-modules-2.6' $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.chroot $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.binary $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.chroot.gpg $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.binary.gpg $ lh_build }code
-
-Q: How do I use a custom kernel? Is there a nice way of booting debian-live
-with a custom kernel (not in an apt repo)? A: Copy it into
-config/chroot_local-packages and set LH_LINUX_PACKAGES="none" or use lh
-config --linux-packages " " Don't forget to compile your kernel with an
-union filesystem (unionfs or aufs), squashfs modules, and initrd support. I
-can cause the kernel to be installed but it seems this happens later than
-grub/syslinux is configured so it's not listed and casper/ and the menu
-require munging. You need to follow the debian scheme, e.g. placing the
-files in /boot as vmlinuz-$version and initrd.img-$version etc. I personally
-wouldn't go that way which is too much of a hassle, and just use make-kpkg
-to produce custom kernel deb packages. They should integrate nicely if you
-just put them into config/chroot_local-packages and set
-LH_LINUX_PACKAGES="". Hint: to work around an error, which
-lh_binary_syslinux will throw on custom kernels if there is not an 468/686
-in the kernel-name, you need to set CONFIG_LOCALVERSION="-486" or "-686"
-within the kernel configuration (-> General setup -> Local version set
-to -486 or -686) corresponding to LH_LINUX_FLAVOURS="" or "686". this at
-least up till live-helper version 1.0~a40-1 see
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-July/001947.html
-and
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-November/002581.html
-
-Q: How do I create a cross arch live CD image? A: In short: You can't. Read
-on: The procedure to create a live CD is based on creating a chroot that
-contains the files that will be finally available on the live CD. The live
-CD building procedure includes chrooting into the chroot dir and so some
-operations. chrooting means that the terminal you chroot on will behave as a
-different system so your real system and the chroot environment is decoupled
-somehow. Once the live CD scripts chroots into the chroot dir they have some
-operations to do inside that environment and your real system won't be able
-to run them unless you are using the same architecture. So you only are able
-to make live CD for the arch you run on. But this doesn't prevent you run
-qemu or some other machine emulator that make this possible.
-
-Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That
-depends what you've changed between builds If, for example, you've built an
-iso image and you want a usb image, you only need to run #{lh_clean
---binary}# before you run lh_build again. If you've changed anything in the
-chroot, you'll need to cleanup both chroot and binary with #{lh_clean}#
-before continuing
-
-Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in
-config/binary
-
-Q: How do I include different modules to load when the live system boots? A:
-Configure config/chroot_local-includes/etc/initramfs-tools/
-
-The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default
-initramfs.conf "MODULES = most". You may override that by supplying your own
-initramfs.conf, or else just add your own modules, e.g.
-
-code{
-
-mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo "atl2" >>
-config/chroot_local-includes/etc/initramfs-tools/modules
-
-}code
-
-Note: Even though initramfs.conf(5) says "most adds all the framebuffer,
-acpi, file system, ide, sata, scsi and usb drivers", it actually includes
-network drivers as well. See auto_add_modules() in
-/usr/share/initramfs-tools/hook-functions for the complete list.
-
-Q: Can I have a splash screen? A: Yes you can. You will not know what is
-going on when the splash screen is active, it may fail to activate on some
-hardware or break X on other (both usplash and splashy use libdirectfb which
-does some evil voodoo and may break you graphics or input until you
-reboot). However, you can install and activate it just as you would on any
-other Debian system. To use splashy: 1. install splashy and read the README,
-the manpages are useless for setting it up. Add some parameters to your
-kernel command line, such as in your pxelinux configuration or in
-LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792
-splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy,
-#{quiet}# to suppress most kernel messages that you cannot see anyway but
-would scroll past before splashy manages to paint the graphics on your
-screen. You might want to add splashy to the list of packages installed in
-your image: #{echo splashy > config/chroot_local-packageslists/splashy echo
-splashy-themes >> config/chroot_local-packageslists/splashy}# and select a
-theme:
-
-code{
-
-echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s
-debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the
-ramdisk to include the splash screen echo update-initramfs -u -k all >>
-config/chroot_local-hooks/splashy chmod 755
-config/chroot_local-hooks/splashy
-
-}code
-
-After you rebuild your live system you should observe a bluish splash screen
-while booting. Nothing happens while initramfs is running because there is
-no splashy support in initramfs-tools. Once the init starts the progress bar
-should start to fill. If #{vga=something}# sets a mode that your screen
-cannot show or your card cannot do vesa 2.0 (and thus you get plain text
-mode and no splashy) read the splashy faq.
-
-Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the
-firmwares to the initrd image. You need to install the non-free package
-"firmware-bnx2". Uncompress your initrd image, then copy files:
-
-code{
-
-cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw
-/lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw
-${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/
-
-}code
-
-Recompress your initrd image and boot: it works!
-
-Q: X is broken (the system boots, messages scroll by, and then the screen
-goes blank). What do I do? A: On my system starting X completely disables
-graphics so that I do not see anything even after X bails out and I am back
-to the console. To prevent this you can change the driver Xorg uses.
-
-If you have a working splash screen or at least graphical console you can
-use #{live xdriver=fbdev}# when booting the live system (instead of just
-enter). Another driver you might want to try is #{vesa}#. If all fails you
-might try to set xdriver to some wrong value so that Xorg fails to start and
-you can examine the system while you still see something on the
-console. #{live xdriver=none}#
-
-Q: How can I get Debian first stable versions? A: I'm developing software
-and testing it on Live-CD. Thanks for the LiveCD project. To be sure my
-development is fully compatible with the "etch" version, I need the same
-scenario when Debian GNU/Linux 4.0 was published as stable (I believe
-2007.04.08). If there was some bug on 2007.04.08 that was corrected one week
-later, I need to test software foreseeing that scenario without the bug
-solved.
-
-Q: I get "fopen: Permission denied"-warnings from apt on building/at the
-live-system A: That's a harmless bug in apt. However, if you want to get off
-this warnings in the live-system, add a file in chroot_local-hooks with
-follow row:
-
-code{
-
-chown -R man.man /var/cache/man
-
-}code
-
-Q: Why I always fail during "Retrieving Packages" stage when running
-lh_build? I have already set apt-http-proxy and so on. A: lh_build
-retrieves packages via wget, as a result you need to enable the proxy
-settings in /etc/wgetrc before running lh_build.
-
-Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system
-boots, so it's useless to put modifed Xorg.conf in
-config/choort_local-includes/etc/X11, because it will be overwritten during
-boot. However, you can edit /usr/bin/dexconf, which generate xorg.conf
-during boot, so the result will be modified Xorg.conf. The modified dexconf
-has to be put in config/choort_local-includes/usr/bin. e.g.: you can
-configure Xorg.conf for two or more keyboards layouts with alt+shift toggle
-by editing dexconf and replacing the line:
-
-code{
-
-Option "XkbLayout" "$XKB_LAYOUT"
-
-}code
-
-with the lines:
-
-code{
-
-Option "XkbLayout" "us,il" Option "XkbOptions"
-"grp:alt_shift_toggle,grp_led:scroll"
-
-}code
-
-when "us,il" are the wanted keyboard layouts.
-
-You can force default screen resulotion (e.g. 1024*768) by adding the lines:
-
-code{
-
-SubSection "Display"
- Modes "1024x768"
-EndSubSection
-
-}code
-
-between the lines:
-
-code{
-
-Section "Screen"
- Identifier "Default Screen"
- Monitor "Configured Monitor"
-EndSection"
-
-}code
-
-Q: Where are the build parameters for the prebuilt images A: See
-http://live.debian.net/README.images.
diff --git a/manual/de/other_howtos.ssi b/manual/de/other_howtos.ssi
deleted file mode 100644
index 63e84bf..0000000
--- a/manual/de/other_howtos.ssi
+++ /dev/null
@@ -1,118 +0,0 @@
-B~ Howtos
-
-1~ Howtos
-
-2~ ISO
-
-Generating a Debian Live CD is very simple. You need to have live-helper
-(package available in Debian sid and lenny), and Debootstrap (or
-cdebootstrap) from etch or newer.
-
-3~ Install live-helper
-
-#{apt-get install live-helper}#
-
-3~ Configure the current working directory with lh_config
-
-code{
-
-lh_config -b iso -a $ARCH
-
-}code
-
-where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64).
-
-#{-b}# flag is used to be sure to obtain image in ISO format.
-
-3~ Build the image with lh_build:
-
-Execute lh_build as root: #{lh_build}#
-
-The command above will create the basic image, containing just the Debian
-standard system (with no X at all).
-
-If you want to have any of the Desktop environments on your livecd, #{ls
-/usr/share/live-helper/lists}# will show a number of available package Lists
-to choose from, e.g. #{lh_config -p gnome-desktop}#
-
-More examples are listed at DebianLive/Examples.
-
-See packages for help configuring a local Debian Mirror and other aspects of
-the live system. % FIXME: <xref linkend="packages"/>
-
-3~ Test the image
-
-If you have qemu installed, you can boot the image with:
-
-code{
-
-qemu -cdrom binary.iso
-
-}code
-
-If you have also kqemu installed, you can add #{-kernel-kqemu}#
-
-2~ ISO_(multiarch)
-
-Multiple machine boot CDs can be created with the following manual
-procedure. This procedure has been successfully used to create a single CD
-which is bootable on alpha, i386, pmax, and sparc. It should be possible to
-also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x.
-
-To create a CD which is bootable by multiple architectures, use the
-following steps in this order. Please note that the order is critical.
-
-Make sure you have all the required files including the various kernels and
-boot programs listed in the individual machine sections.
-
-Include a directory somewhere in the cdsources directory called mdec.pmax
-and include the pmax bootxx_cd9660 file there. For example,
-/cdsources/usr/mdec.pmax/bootxx_cd9660.
-
-Include a directory somewhere in the cdsources directory called mdec.vax and
-include the vax xxboot file there. For example,
-#{cdsources/usr/mdec.vax/xxboot.}#
-
-Include the macppc ofwboot.xcf bootloader in /cdsources.
-
-Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b
-i386/installation/floppy/boot-big.fs \ -c boot.catalog -l -J -r -L
-/cdsources 2>&1 | tee /tmp/mkisofs.log exit}#
-
-Note: The appearance of the -v flag twice is required. If you are making a
-bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs
--part in the parameters for mkisofs.
-
-Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3
-bootblocks. Alternatively, install the sysutils/mksunbootcd package on your
-favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs
-boot-sun4m.fs boot-sun3.fs}#
-
-Run the installboot(8) program targeted for NetBSD/pmax to install the pmax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-pmax boot block is appended to the end of the ISO file system.
-
-#{installboot -m pmax -v -o append,sunsum output.iso
-/tmp/mdec.pmax/bootxx_cd9660}#
-
-The -o append,sunsum option appends the first stage boot block to the end of
-the ISO file system, and restores the checksum used when booting on a sun.
-
-Run the installboot(8) program targeted for NetBSD/vax to install the vax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-vax boot block is appended to the end of the ISO file system.
-
-installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot
-
-(See the pmax entry above for an explanation of the flags).
-
-Run the installboot(8) program targeted for NetBSD/alpha to install the
-alpha bootblocks.
-
-#{installboot -m alpha -v -o append,sunsum output.iso
-/tmp/mdec.alpha/bootxx_cd9660}#
-
-Note: The alpha installboot must occur after the others, because currently
-it's the only machine dependent back-end for installboot(8) that can
-calculate the alpha checksum. (See the pmax entry above for an explanation
-of the flags).
diff --git a/manual/en/live-manual.ssm b/manual/en/live-manual.ssm
index 2ec9427..60a8440 100644
--- a/manual/en/live-manual.ssm
+++ b/manual/en/live-manual.ssm
@@ -63,6 +63,3 @@
<< user_examples.ssi
-% << other_faq.ssi
-
-% << other_howtos.ssi
diff --git a/manual/en/other_faq.ssi b/manual/en/other_faq.ssi
deleted file mode 100644
index 34ed2f6..0000000
--- a/manual/en/other_faq.ssi
+++ /dev/null
@@ -1,383 +0,0 @@
-B~ Frequently asked questions (FAQ)
-
-1~ Frequently asked questions (FAQ)
-
-Q: I downloaded a prebuilt live image. How do I put it on a USB stick?
-A: See "Copying USB/HDD image to a USB stick"
-% FIXME: <xref linkend="image_copying"/>
-
-Q: How do I log my build?
-A: You could use script, screen or tee: #{$ lh_build 2>&1 | tee build.log}#
-
-Q: How can I convert an already installed standard Debian partition into a Debian Live system?
-A: Save the list of installed packages and load it into your new Debian Live System. Copy your /etc to config/chroot_local-includes
-
-Q: What does 'losetup: could not find any free loop device' mean and how do I fix it?
-A: Loop devices are used during the build; there probably aren't any free if you've aborted several builds. Something like: for l in /dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/loop7 ; do losetup -d $l ; done should rectify the situation (assuming all loop devices in use were created by lh_build; if in doubt, check the contents of each loop device before deleting them with losetup -d).
-
-Q: How do I launch an interactive shell during the chroot stage?
-A: To enable interactive shell: #{$ lh_config --interactive shell}# To continue the build process: #{# logout}# or #{# exit}# To disable interactive shell, set LH_INTERACTIVE to "disabled" in config/chroot.
-
-Q: What is the root /user password?
-A: The user password for the live user is 'live'. By default, there is not any root password. You can switch to root with ${sudo -i}# or set a password for root with #{sudo passwd}#
-
-Q: How do I change root or any user password?
-A: Add a chroot local hook script to change root or any user password each time you build an image.
-e.g. config/chroot_local-hooks/01-update_password.sh to set root password to "nopasswd"
-
-code{
-#!/bin/sh
-
-echo "I: update password"
-echo "root:nopasswd" | chpasswd
-
-$ chmod +x config/chroot_local-hooks/01-update_password.sh
-
-}code
-
-Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/live-bottom/10adduser your build folder:
-
-code{
-
-mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-
-}code
-
-Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/10adduser and paste in the new user_crypted password that you make with: #{echo "newlivepass" | mkpasswd -s}#
-
-Or add an hook file in config/chroot_local-hooks/ with something like the below:
-
-code{
-#!/bin/sh
-
-# Change the autogenerated user password to "debianlive"
-plain_password="debianlive"
-password=$(echo "${plain_password}" | mkpasswd -s)
-
-sed -i -e 's/\(user_crypted=\)\(.*\)\( #.*\)/\1\"'${password}'\"\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser
-
-update-initramfs -tu -kall
-}code
-
-The latter (hook model) could be more future proof than the former solution since it modifies just one string selectively but it requires the package "whois" to be installed on the target system (for mkpasswd) or that you generate the $password string not at build time and include it crypted in the above script.
-
-Q: How to disable autologin?
-A1: use the commandline parameter #{lh config --bootappend-live "noautologin"}#
-A2: You need to set boot=noautologin noxautologin as described in man live-initramfs If you boot via TFTP you want to insert the option to pxelinux.cfg/default
-
-Q: How do I change default hostname or username?
-A: To change default hostname or username: #{$ lh_config --hostname myhostname $ lh_config --username myusername}#
-
-Q: How do I make the final image smaller?
-A: Clean orphaned apps/libs: Install package "deborphan" and then run 'sudo deborphan -n' . Delete unwanted packages. Remove the apt cache. Purge unwanted locales (see "localepurge" package).
-
-Q: How do I customize bash-config permanently (aliases, bash-completion etc.)?
-A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc
-
-Q: How do I disable services permanently? (Be careful!)
-A: Add a chroot local hook script to disable a service each time you build an image:
-e.g. config/chroot_local-hooks/01-disable_service.sh
-
-code{
-
-#!/bin/sh
-
-echo "I: disable service"
-update-rc.d -f service_name remove
-
-$ chmod +x config/chroot_local-hooks/01-disable_service.sh
-
-}code
-
-Q: How do I enable | disable the md5checksum at the ISO building?
-A: #{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value.
-
-Q: How to disable the generation of the .tar.gz file?
-A: #{lh_config --net-tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in snapsshot version at the moment 2008/Feb/28)
-
-Q: How do I "build a new image"?
-A: Run commands:
-
-code{
-
-$ sudo lh_clean --binary
-$ sudo lh_build
-
-}code
-
-Hint: If the configuration had changed you should leave "--binary" out. This will clean your chroot directory too.
-
-Q: How do I use Fluxbox ?
-A: Add a new lists file with the fluxbox packages you want.
-
-Create /home/$USERNAME/.dmrc file (default username is "user").
-
-code{
-
-$ cat .dmrc
-[Desktop]
-Session=fluxbox
-}code
-
-Note: .dmrc is owned by $USERNAME:$USERNAME.
-
-See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD
-
-Q: How do I use custom repositories?
-A: See http://wiki.debian.org/DebianLive/Configuration
-
-Q: How do I customize the artwork for the live CD (grub or syslinux boot splash, usplash, etc.)?
-A: See http://wiki.debian.org/DebianLive/Howto/Custom_Artwork
-
-Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look?
-A: Start the live system in qemu:
-
-code{
-
-$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22
-
-}code
-
-Note: the -redir argument must be changed to meet your needs
-
-Q: How do I execute a custom shell script inside the chroot system after the chroot stage?
-A: Add your script in config/chroot_local-hooks.
-
-Q: How do I add a script running immediately after all other scripts when the live system boots?
-A: Add your script in config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99scrip
-
-code{
-
-$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99script
-
-}code
-
-Note: The hook script must be executable. Do not forget to lh_clean --chroot after making this change before you build again.
-
-You must also use the example script /usr/share/live-helper/examples/hooks/update-initramfs.sh to ensure your script gets built into the initramfs (read the comment header for instructions).
-
-Q: How do I add software not in Debian ?
-A: See Customizing package installation
-% FIXME: <xref linkend="packages"/>
-
-Q: What is the manifest with Ubuntu used for?
-A: Manifest is just the package list, which ubuntu does $something with. Don't worry about it.
-
-Q: What is this {p} syntax with mtools{p} and parted{p}?
-A: That's aptitude.
-
-Q: Do I need to write the image on USB stick to test it?
-A: you must use qemu >= 0.8.
-
-Q: What is /cow?
-A: Copy-on-write, the 'diff' from unionfs.
-
-Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed something else entirely?
-A: It is not. It is a package list, not a debconf preseeding.
-
-Q: What is the difference between standard and minimal?
-A: standard: packages of priority standard and higher; minimal: packages of priority essential and higher;
-
-Q: What can the sections be used for? Aren't they BIG?
-A: Someone maybe wants to include packages from contrib or non-free.
-
-Q: memtest86+ ... is that used?
-A: Yes
-
-Q: How do I build using predefined packages lists?
-A: e.g. to build using standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo lh_build}# Note: The packages lists can be found in /usr/share/live-helper/lists/ directory.
-
-Q: How do I rebuild without downloading all the packages again?
-A: All packages are cached in cache subdirectory. They remain until a clean purge: #{$ sudo lh_clean --purge}# You do not have to do anything to prevent packages from being re-downloaded. You need to remember to clean whichever stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#
-
-Q: How do I boot USB debian-live on systems not supporting USB boot?
-A: Make a boot CD with grub, configured to boot from a debian-live kernel copied on the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/boot/grub/menu.lst:
-
-code{
-
-default 0
-timeout 5
-color cyan/blue white/blue
-title Debian Live root (cd)
-kernel /boot/vmlinuz boot=live
-initrd /boot/initrd.img
-
-}code
-
-Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image.
-
-Q: How do I boot debian-live on systems not supporting CDROM or USB boot?
-A: If you have a floppy drive, you may be able to use it, otherwise you will need to use loadlin/grub4dos/win32-loader. If you have a second system to serve up the image over the network, See http://wiki.debian.org/DebianLive/Howto/Creating_a_Netboot_Image
-
-Q: The X configuration does not seems to work, the resolution is too low. What can I do?
-A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf && lh_config --packages xdebconfigurator}#
-
-Q: Apache has problems with static files
-A: Sendfile does not work well on the unionfs used by Debian Live. Add the following to apache's configuration: #{EnableSendfile off}#
-
-Q: How do I make hard disk partitions auto-mountable?
-A: Short answer: Right now the best is to use a script that will populate the fstab when the CD is booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper solution based on HAL will be described here in a hopefully near future.
-A: Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-policy-fixed-drives.fdi is not available anymore and the previous trick that consisted to remove this file to enable automounting of fixed drives as a consequence is obsolete. Eventually, it will be possible to combine HAL and PolicyKit to enable different permissions and actions to achieve advanced (auto)mounting for non-root users. Until then, because the live scripts are only touching to the fstab to add a swap partition if discovered at boot time, the only way to have fixed drives mounted automatically is to use a script that will populate the fstab file at the end of the multiuser runlevel. To achieve this, you can do, for example, the following: download the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin directory, and move the script inside Make sure the script is executable (chmod +x diskmounter.s
h) create the chroot_local-includes/etc/rc.local file and call the diskmounter from there (see this https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and NTFS partitions and mount them read-write, except for NTFS. This will change soon and an option will be available to use ntfs-3g to mount NTFS as read-write. comments, patches and other things about this script and issue: http://code.goto10.org/projects/puredyne/ticket/463
-
-Q: Boot fails with panic: can't open /scripts/live
-A: Add latest live-initramfs deb package into config/chroot_local-packages directory and rebuild.
-
-Q: How do I configure the locale and the keyboard?
-A: See 10n
-% FIXME: <xref linkend="internalization"/>
-
-Q: How do I get past boot prompt without a working keyboard?
-A: See Customizing the bootup process
-% FIXME: <xref linkend="bootup"/>
-Note: Boot from an USB-HDD on an iMac with GRUB did not work.
-
-Q: Can I serve the root image from a web or ftp server?
-A: Since live-initramfs 1.99, it should be possible to use the fetch= argument on the kernel command line. You can build a netboot image as usual, and when you are done edit the tftpboot/pxelinux.cfg/default file. Remove the references to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url where you placed the root image>. You have to include wget in the chroot. It could work for other boot methods as well. However, I am not sure the live scripts configure the network when booting from a CD or USB disk. #{$ lh_config --packages wget}#
-
-Q: Why doesn't quickreboot (or some other boot parameter) work?
-A: If you are building an etch image (which was the default up to 2007/09/14) you have a very old version of casper which does not support quickreboot and possibly other boot parameters as well. You could configure your sources to use live-backports (see /usr/share/live-helper/examples/sources/live-backports) and switch to live-initramfs, or better yet, build a lenny image instead, which is the new default. #{$ lh_config --distribution lenny $ lh_config --initramfs live-initramfs}#
-
-Q: How do I fix "Could not find kernel image" issue with syslinux bootloader?
-A: Add a binary local hook script to fix kernel and initrd path each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux.sh
-
-code{
-
-#!/bin/sh
-
-SYSLINUXCFG=`find binary -type f -name syslinux.cfg`
-
-sed -i "s|kernel /vmlinuz|kernel vmlinuz|g" ${SYSLINUXCFG}
-sed -i "s|initrd=/initrd|initrd=initrd|g" ${SYSLINUXCFG}
-
-$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh
-
-}code
-
-Q: How do I use a newer kernel with lenny?
-A: A build with backports.org kernels will fail as that repository lacks the necessary module packages (linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://unsupported.debian-maintainers.org/backports-kernel/ The quick way to success:
-
-code{
-
-$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/chroot_sources/backports-kernel.chroot
-$ echo 'deb http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/chroot_sources/backports-kernel.binary
-$ wget http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel.chroot.gpg
-$ wget http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel.binary.gpg
-$ lh_build
-}code
-
-Q: How do I use a custom kernel? Is there a nice way of booting debian-live with a custom kernel (not in an apt repo)?
-A: Copy it into config/chroot_local-packages and set LH_LINUX_PACKAGES="none" or use lh config --linux-packages " " Don't forget to compile your kernel with an union filesystem (unionfs or aufs), squashfs modules, and initrd support. I can cause the kernel to be installed but it seems this happens later than grub/syslinux is configured so it's not listed and casper/ and the menu require munging. You need to follow the debian scheme, e.g. placing the files in /boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't go that way which is too much of a hassle, and just use make-kpkg to produce custom kernel deb packages. They should integrate nicely if you just put them into config/chroot_local-packages and set LH_LINUX_PACKAGES="". Hint: to work around an error, which lh_binary_syslinux will throw on custom kernels if there is not an 468/686 in the kernel-name, you need to set CONFIG_LOCALVERSION="-486" or "-686" within the kernel configuration (-> Genera
l setup -> Local version set to -486 or -686) corresponding to LH_LINUX_FLAVOURS="" or "686". this at least up till live-helper version 1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-November/002581.html
-
-Q: How do I create a cross arch live CD image?
-A: In short: You can't. Read on: The procedure to create a live CD is based on creating a chroot that contains the files that will be finally available on the live CD. The live CD building procedure includes chrooting into the chroot dir and so some operations. chrooting means that the terminal you chroot on will behave as a different system so your real system and the chroot environment is decoupled somehow. Once the live CD scripts chroots into the chroot dir they have some operations to do inside that environment and your real system won't be able to run them unless you are using the same architecture. So you only are able to make live CD for the arch you run on. But this doesn't prevent you run qemu or some other machine emulator that make this possible.
-
-Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/
-A: That depends what you've changed between builds If, for example, you've built an iso image and you want a usb image, you only need to run #{lh_clean --binary}# before you run lh_build again. If you've changed anything in the chroot, you'll need to cleanup both chroot and binary with #{lh_clean}# before continuing
-
-Q: How can i set boot= parameters?
-A: Set LH_BOOTAPPEND_LIVE in config/binary
-
-Q: How do I include different modules to load when the live system boots?
-A: Configure config/chroot_local-includes/etc/initramfs-tools/
-
-The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default initramfs.conf "MODULES = most". You may override that by supplying your own initramfs.conf, or else just add your own modules, e.g.
-
-code{
-
-mkdir -p config/chroot_local-includes/etc/initramfs-tools/
-echo "atl2" >> config/chroot_local-includes/etc/initramfs-tools/modules
-
-}code
-
-Note: Even though initramfs.conf(5) says "most adds all the framebuffer, acpi, file system, ide, sata, scsi and usb drivers", it actually includes network drivers as well. See auto_add_modules() in /usr/share/initramfs-tools/hook-functions for the complete list.
-
-Q: Can I have a splash screen?
-A: Yes you can. You will not know what is going on when the splash screen is active, it may fail to activate on some hardware or break X on other (both usplash and splashy use libdirectfb which does some evil voodoo and may break you graphics or input until you reboot). However, you can install and activate it just as you would on any other Debian system. To use splashy: 1. install splashy and read the README, the manpages are useless for setting it up. Add some parameters to your kernel command line, such as in your pxelinux configuration or in LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, #{quiet}# to suppress most kernel messages that you cannot see anyway but would scroll past before splashy manages to paint the graphics on your screen. You might want to add splashy to the list of packages installed in your image: #{echo splashy > config/chroot_local-packageslists/s
plashy echo splashy-themes >> config/chroot_local-packageslists/splashy}# and select a theme:
-
-code{
-
-echo '#!/bin/sh' > config/chroot_local-hooks/splashy
-echo splashy_config -s debian-moreblue '||' true >> config/chroot_local-hooks/splashy
-# update the ramdisk to include the splash screen
-echo update-initramfs -u -k all >> config/chroot_local-hooks/splashy
-chmod 755 config/chroot_local-hooks/splashy
-
-}code
-
-After you rebuild your live system you should observe a bluish splash screen while booting. Nothing happens while initramfs is running because there is no splashy support in initramfs-tools. Once the init starts the progress bar should start to fill. If #{vga=something}# sets a mode that your screen cannot show or your card cannot do vesa 2.0 (and thus you get plain text mode and no splashy) read the splashy faq.
-
-Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)?
-A: Add the firmwares to the initrd image. You need to install the non-free package "firmware-bnx2". Uncompress your initrd image, then copy files:
-
-code{
-
-cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw ${INITRD}/lib/firmware/
-cp /lib/udev/firmware.agent ${INITRD}/lib/udev/
-
-}code
-
-Recompress your initrd image and boot: it works!
-
-Q: X is broken (the system boots, messages scroll by, and then the screen goes blank). What do I do? A: On my system starting X completely disables graphics so that I do not see anything even after X bails out and I am back to the console. To prevent this you can change the driver Xorg uses.
-
-If you have a working splash screen or at least graphical console you can use #{live xdriver=fbdev}# when booting the live system (instead of just enter). Another driver you might want to try is #{vesa}#. If all fails you might try to set xdriver to some wrong value so that Xorg fails to start and you can examine the system while you still see something on the console. #{live xdriver=none}#
-
-Q: How can I get Debian first stable versions?
-A: I'm developing software and testing it on Live-CD. Thanks for the LiveCD project. To be sure my development is fully compatible with the "etch" version, I need the same scenario when Debian GNU/Linux 4.0 was published as stable (I believe 2007.04.08). If there was some bug on 2007.04.08 that was corrected one week later, I need to test software foreseeing that scenario without the bug solved.
-
-Q: I get "fopen: Permission denied"-warnings from apt on building/at the live-system
-A: That's a harmless bug in apt. However, if you want to get off this warnings in the live-system, add a file in chroot_local-hooks with follow row:
-
-code{
-
-chown -R man.man /var/cache/man
-
-}code
-
-Q: Why I always fail during "Retrieving Packages" stage when running lh_build? I have already set apt-http-proxy and so on.
-A: lh_build retrieves packages via wget, as a result you need to enable the proxy settings in /etc/wgetrc before running lh_build.
-
-Q: How do I edit Xorg.conf?
-A: Xorg.conf is generated every time system boots, so it's useless to put modifed Xorg.conf in config/choort_local-includes/etc/X11, because it will be overwritten during boot. However, you can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the result will be modified Xorg.conf. The modified dexconf has to be put in config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for two or more keyboards layouts with alt+shift toggle by editing dexconf and replacing the line:
-
-code{
-
-Option "XkbLayout" "$XKB_LAYOUT"
-
-}code
-
-with the lines:
-
-code{
-
-Option "XkbLayout" "us,il"
-Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
-
-}code
-
-when "us,il" are the wanted keyboard layouts.
-
-You can force default screen resulotion (e.g. 1024*768) by adding the lines:
-
-code{
-
-SubSection "Display"
- Modes "1024x768"
-EndSubSection
-
-}code
-
-between the lines:
-
-code{
-
-Section "Screen"
- Identifier "Default Screen"
- Monitor "Configured Monitor"
-EndSection"
-
-}code
-
-Q: Where are the build parameters for the prebuilt images
-A: See http://live.debian.net/README.images.
diff --git a/manual/en/other_howtos.ssi b/manual/en/other_howtos.ssi
deleted file mode 100644
index 83bd2d6..0000000
--- a/manual/en/other_howtos.ssi
+++ /dev/null
@@ -1,86 +0,0 @@
-B~ Howtos
-
-1~ Howtos
-
-2~ ISO
-
-Generating a Debian Live CD is very simple. You need to have live-helper (package available in Debian sid and lenny), and Debootstrap (or cdebootstrap) from etch or newer.
-
-3~ Install live-helper
-
-#{apt-get install live-helper}#
-
-3~ Configure the current working directory with lh_config
-
-code{
-
-lh_config -b iso -a $ARCH
-
-}code
-
-where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64).
-
-#{-b}# flag is used to be sure to obtain image in ISO format.
-
-3~ Build the image with lh_build:
-
-Execute lh_build as root: #{lh_build}#
-
-The command above will create the basic image, containing just the Debian standard system (with no X at all).
-
-If you want to have any of the Desktop environments on your livecd, #{ls /usr/share/live-helper/lists}# will show a number of available package Lists to choose from, e.g. #{lh_config -p gnome-desktop}#
-
-More examples are listed at DebianLive/Examples.
-
-See packages for help configuring a local Debian Mirror and other aspects of the live system.
-% FIXME: <xref linkend="packages"/>
-
-3~ Test the image
-
-If you have qemu installed, you can boot the image with:
-
-code{
-
-qemu -cdrom binary.iso
-
-}code
-
-If you have also kqemu installed, you can add #{-kernel-kqemu}#
-
-2~ ISO_(multiarch)
-
-Multiple machine boot CDs can be created with the following manual procedure. This procedure has been successfully used to create a single CD which is bootable on alpha, i386, pmax, and sparc. It should be possible to also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x.
-
-To create a CD which is bootable by multiple architectures, use the following steps in this order. Please note that the order is critical.
-
-Make sure you have all the required files including the various kernels and boot programs listed in the individual machine sections.
-
-Include a directory somewhere in the cdsources directory called mdec.pmax and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/mdec.pmax/bootxx_cd9660.
-
-Include a directory somewhere in the cdsources directory called mdec.vax and include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/xxboot.}#
-
-Include the macppc ofwboot.xcf bootloader in /cdsources.
-
-Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/installation/floppy/boot-big.fs \ -c boot.catalog -l -J -r -L /cdsources 2>&1 | tee /tmp/mkisofs.log exit}#
-
-Note: The appearance of the -v flag twice is required. If you are making a bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -part in the parameters for mkisofs.
-
-Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 bootblocks. Alternatively, install the sysutils/mksunbootcd package on your favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs boot-sun4m.fs boot-sun3.fs}#
-
-Run the installboot(8) program targeted for NetBSD/pmax to install the pmax bootblocks. Note that in order to coexist with other NetBSD boot blocks, the pmax boot block is appended to the end of the ISO file system.
-
-#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/bootxx_cd9660}#
-
-The -o append,sunsum option appends the first stage boot block to the end of the ISO file system, and restores the checksum used when booting on a sun.
-
-Run the installboot(8) program targeted for NetBSD/vax to install the vax bootblocks. Note that in order to coexist with other NetBSD boot blocks, the vax boot block is appended to the end of the ISO file system.
-
-installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot
-
-(See the pmax entry above for an explanation of the flags).
-
-Run the installboot(8) program targeted for NetBSD/alpha to install the alpha bootblocks.
-
-#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/bootxx_cd9660}#
-
-Note: The alpha installboot must occur after the others, because currently it's the only machine dependent back-end for installboot(8) that can calculate the alpha checksum. (See the pmax entry above for an explanation of the flags).
diff --git a/manual/fr/live-manual.ssm b/manual/fr/live-manual.ssm
index 2ec9427..60a8440 100644
--- a/manual/fr/live-manual.ssm
+++ b/manual/fr/live-manual.ssm
@@ -63,6 +63,3 @@
<< user_examples.ssi
-% << other_faq.ssi
-
-% << other_howtos.ssi
diff --git a/manual/fr/other_faq.ssi b/manual/fr/other_faq.ssi
deleted file mode 100644
index f754913..0000000
--- a/manual/fr/other_faq.ssi
+++ /dev/null
@@ -1,545 +0,0 @@
-B~ Frequently asked questions (FAQ)
-
-1~ Frequently asked questions (FAQ)
-
-Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A:
-See "Copying USB/HDD image to a USB stick" % FIXME: <xref
-linkend="image_copying"/>
-
-Q: How do I log my build? A: You could use script, screen or tee: #{$
-lh_build 2>&1 | tee build.log}#
-
-Q: How can I convert an already installed standard Debian partition into a
-Debian Live system? A: Save the list of installed packages and load it into
-your new Debian Live System. Copy your /etc to config/chroot_local-includes
-
-Q: What does 'losetup: could not find any free loop device' mean and how do
-I fix it? A: Loop devices are used during the build; there probably aren't
-any free if you've aborted several builds. Something like: for l in
-/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6
-/dev/loop7 ; do losetup -d $l ; done should rectify the situation (assuming
-all loop devices in use were created by lh_build; if in doubt, check the
-contents of each loop device before deleting them with losetup -d).
-
-Q: How do I launch an interactive shell during the chroot stage? A: To
-enable interactive shell: #{$ lh_config --interactive shell}# To continue
-the build process: #{# logout}# or #{# exit}# To disable interactive shell,
-set LH_INTERACTIVE to "disabled" in config/chroot.
-
-Q: What is the root /user password? A: The user password for the live user
-is 'live'. By default, there is not any root password. You can switch to
-root with ${sudo -i}# or set a password for root with #{sudo passwd}#
-
-Q: How do I change root or any user password? A: Add a chroot local hook
-script to change root or any user password each time you build an image.
-e.g. config/chroot_local-hooks/01-update_password.sh to set root password to
-"nopasswd"
-
-code{ #!/bin/sh
-
-echo "I: update password" echo "root:nopasswd" | chpasswd
-
-$ chmod +x config/chroot_local-hooks/01-update_password.sh
-
-}code
-
-Note for live user; you need to copy the
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser your build folder:
-
-code{
-
-mkdir -p
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-
-}code
-
-Note: Then edit the
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-and paste in the new user_crypted password that you make with: #{echo
-"newlivepass" | mkpasswd -s}#
-
-Or add an hook file in config/chroot_local-hooks/ with something like the
-below:
-
-code{ #!/bin/sh
-
-# Change the autogenerated user password to "debianlive"
-plain_password="debianlive" password=$(echo "${plain_password}" | mkpasswd
--s)
-
-sed -i -e 's/\(user_crypted=\)\(.*\)\( #.*\)/\1\"'${password}'\"\3/'
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-
-update-initramfs -tu -kall }code
-
-The latter (hook model) could be more future proof than the former solution
-since it modifies just one string selectively but it requires the package
-"whois" to be installed on the target system (for mkpasswd) or that you
-generate the $password string not at build time and include it crypted in
-the above script.
-
-Q: How to disable autologin? A1: use the commandline parameter #{lh config
---bootappend-live "noautologin"}# A2: You need to set boot=noautologin
-noxautologin as described in man live-initramfs If you boot via TFTP you
-want to insert the option to pxelinux.cfg/default
-
-Q: How do I change default hostname or username? A: To change default
-hostname or username: #{$ lh_config --hostname myhostname $ lh_config
---username myusername}#
-
-Q: How do I make the final image smaller? A: Clean orphaned apps/libs:
-Install package "deborphan" and then run 'sudo deborphan -n' . Delete
-unwanted packages. Remove the apt cache. Purge unwanted locales (see
-"localepurge" package).
-
-Q: How do I customize bash-config permanently (aliases, bash-completion
-etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc
-
-Q: How do I disable services permanently? (Be careful!) A: Add a chroot
-local hook script to disable a service each time you build an image:
-e.g. config/chroot_local-hooks/01-disable_service.sh
-
-code{
-
-#!/bin/sh
-
-echo "I: disable service" update-rc.d -f service_name remove
-
-$ chmod +x config/chroot_local-hooks/01-disable_service.sh
-
-}code
-
-Q: How do I enable | disable the md5checksum at the ISO building? A:
-#{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value.
-
-Q: How to disable the generation of the .tar.gz file? A: #{lh_config
---net-tarball none|gzip}# Or change the LH_NET_TARBALL value. (only
-available in snapsshot version at the moment 2008/Feb/28)
-
-Q: How do I "build a new image"? A: Run commands:
-
-code{
-
-$ sudo lh_clean --binary $ sudo lh_build
-
-}code
-
-Hint: If the configuration had changed you should leave "--binary" out. This
-will clean your chroot directory too.
-
-Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages
-you want.
-
-Create /home/$USERNAME/.dmrc file (default username is "user").
-
-code{
-
-$ cat .dmrc [Desktop] Session=fluxbox }code
-
-Note: .dmrc is owned by $USERNAME:$USERNAME.
-
-See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at
-http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD
-
-Q: How do I use custom repositories? A: See
-http://wiki.debian.org/DebianLive/Configuration
-
-Q: How do I customize the artwork for the live CD (grub or syslinux boot
-splash, usplash, etc.)? A: See
-http://wiki.debian.org/DebianLive/Howto/Custom_Artwork
-
-Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look?
-A: Start the live system in qemu:
-
-code{
-
-$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22
-
-}code
-
-Note: the -redir argument must be changed to meet your needs
-
-Q: How do I execute a custom shell script inside the chroot system after the
-chroot stage? A: Add your script in config/chroot_local-hooks.
-
-Q: How do I add a script running immediately after all other scripts when
-the live system boots? A: Add your script in
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99scrip
-
-code{
-
-$ chmod +x
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99script
-
-}code
-
-Note: The hook script must be executable. Do not forget to lh_clean --chroot
-after making this change before you build again.
-
-You must also use the example script
-/usr/share/live-helper/examples/hooks/update-initramfs.sh to ensure your
-script gets built into the initramfs (read the comment header for
-instructions).
-
-Q: How do I add software not in Debian ? A: See Customizing package
-installation % FIXME: <xref linkend="packages"/>
-
-Q: What is the manifest with Ubuntu used for? A: Manifest is just the
-package list, which ubuntu does $something with. Don't worry about it.
-
-Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude.
-
-Q: Do I need to write the image on USB stick to test it? A: you must use
-qemu >= 0.8.
-
-Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs.
-
-Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed
-something else entirely? A: It is not. It is a package list, not a debconf
-preseeding.
-
-Q: What is the difference between standard and minimal? A: standard:
-packages of priority standard and higher; minimal: packages of priority
-essential and higher;
-
-Q: What can the sections be used for? Aren't they BIG? A: Someone maybe
-wants to include packages from contrib or non-free.
-
-Q: memtest86+ ... is that used? A: Yes
-
-Q: How do I build using predefined packages lists? A: e.g. to build using
-standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo
-lh_build}# Note: The packages lists can be found in
-/usr/share/live-helper/lists/ directory.
-
-Q: How do I rebuild without downloading all the packages again? A: All
-packages are cached in cache subdirectory. They remain until a clean purge:
-#{$ sudo lh_clean --purge}# You do not have to do anything to prevent
-packages from being re-downloaded. You need to remember to clean whichever
-stages you want to rebuild first. e.g. to rebuild from the cached bootstrap,
-chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#
-
-Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make
-a boot CD with grub, configured to boot from a debian-live kernel copied on
-the cd structure #{$ mkdir -p iso/boot/grub && cp
-/usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub && cp chroot/boot/*
-iso/boot/}# Create iso/boot/grub/menu.lst:
-
-code{
-
-default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd)
-kernel /boot/vmlinuz boot=live initrd /boot/initrd.img
-
-}code
-
-Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito
--no-emul-boot \ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn
-the image.
-
-Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A:
-If you have a floppy drive, you may be able to use it, otherwise you will
-need to use loadlin/grub4dos/win32-loader. If you have a second system to
-serve up the image over the network, See
-http://wiki.debian.org/DebianLive/Howto/Creating_a_Netboot_Image
-
-Q: The X configuration does not seems to work, the resolution is too
-low. What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend
-xdebconf && lh_config --packages xdebconfigurator}#
-
-Q: Apache has problems with static files A: Sendfile does not work well on
-the unionfs used by Debian Live. Add the following to apache's
-configuration: #{EnableSendfile off}#
-
-Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right
-now the best is to use a script that will populate the fstab when the CD is
-booting. Such a script can be found at
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh.
-A proper solution based on HAL will be described here in a hopefully near
-future. A: Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL,
-debian-storage-policy-fixed-drives.fdi is not available anymore and the
-previous trick that consisted to remove this file to enable automounting of
-fixed drives as a consequence is obsolete. Eventually, it will be possible
-to combine HAL and PolicyKit to enable different permissions and actions to
-achieve advanced (auto)mounting for non-root users. Until then, because the
-live scripts are only touching to the fstab to add a swap partition if
-discovered at boot time, the only way to have fixed drives mounted
-automatically is to use a script that will populate the fstab file at the
-end of the multiuser runlevel. To achieve this, you can do, for example, the
-following: download the
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh
-script Create the chroot_local-includes/sbin directory, and move the script
-inside Make sure the script is executable (chmod +x diskmounter.sh) create
-the chroot_local-includes/etc/rc.local file and call the diskmounter from
-there (see this
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local
-When called correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32,
-HFS+ and NTFS partitions and mount them read-write, except for NTFS. This
-will change soon and an option will be available to use ntfs-3g to mount
-NTFS as read-write. comments, patches and other things about this script and
-issue: http://code.goto10.org/projects/puredyne/ticket/463
-
-Q: Boot fails with panic: can't open /scripts/live A: Add latest
-live-initramfs deb package into config/chroot_local-packages directory and
-rebuild.
-
-Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref
-linkend="internalization"/>
-
-Q: How do I get past boot prompt without a working keyboard? A: See
-Customizing the bootup process % FIXME: <xref linkend="bootup"/> Note: Boot
-from an USB-HDD on an iMac with GRUB did not work.
-
-Q: Can I serve the root image from a web or ftp server? A: Since
-live-initramfs 1.99, it should be possible to use the fetch= argument on the
-kernel command line. You can build a netboot image as usual, and when you
-are done edit the tftpboot/pxelinux.cfg/default file. Remove the references
-to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url
-where you placed the root image>. You have to include wget in the chroot. It
-could work for other boot methods as well. However, I am not sure the live
-scripts configure the network when booting from a CD or USB disk. #{$
-lh_config --packages wget}#
-
-Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you
-are building an etch image (which was the default up to 2007/09/14) you have
-a very old version of casper which does not support quickreboot and possibly
-other boot parameters as well. You could configure your sources to use
-live-backports (see /usr/share/live-helper/examples/sources/live-backports)
-and switch to live-initramfs, or better yet, build a lenny image instead,
-which is the new default. #{$ lh_config --distribution lenny $ lh_config
---initramfs live-initramfs}#
-
-Q: How do I fix "Could not find kernel image" issue with syslinux
-bootloader? A: Add a binary local hook script to fix kernel and initrd path
-each time you build an
-image. e.g. config/binary_local-hooks/01-fix_syslinux.sh
-
-code{
-
-#!/bin/sh
-
-SYSLINUXCFG=`find binary -type f -name syslinux.cfg`
-
-sed -i "s|kernel /vmlinuz|kernel vmlinuz|g" ${SYSLINUXCFG} sed -i
-"s|initrd=/initrd|initrd=initrd|g" ${SYSLINUXCFG}
-
-$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh
-
-}code
-
-Q: How do I use a newer kernel with lenny? A: A build with backports.org
-kernels will fail as that repository lacks the necessary module packages
-(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports
-http://unsupported.debian-maintainers.org/backports-kernel/ The quick way to
-success:
-
-code{
-
-$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6
-squashfs-modules-2.6' $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.chroot $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.binary $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.chroot.gpg $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.binary.gpg $ lh_build }code
-
-Q: How do I use a custom kernel? Is there a nice way of booting debian-live
-with a custom kernel (not in an apt repo)? A: Copy it into
-config/chroot_local-packages and set LH_LINUX_PACKAGES="none" or use lh
-config --linux-packages " " Don't forget to compile your kernel with an
-union filesystem (unionfs or aufs), squashfs modules, and initrd support. I
-can cause the kernel to be installed but it seems this happens later than
-grub/syslinux is configured so it's not listed and casper/ and the menu
-require munging. You need to follow the debian scheme, e.g. placing the
-files in /boot as vmlinuz-$version and initrd.img-$version etc. I personally
-wouldn't go that way which is too much of a hassle, and just use make-kpkg
-to produce custom kernel deb packages. They should integrate nicely if you
-just put them into config/chroot_local-packages and set
-LH_LINUX_PACKAGES="". Hint: to work around an error, which
-lh_binary_syslinux will throw on custom kernels if there is not an 468/686
-in the kernel-name, you need to set CONFIG_LOCALVERSION="-486" or "-686"
-within the kernel configuration (-> General setup -> Local version set
-to -486 or -686) corresponding to LH_LINUX_FLAVOURS="" or "686". this at
-least up till live-helper version 1.0~a40-1 see
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-July/001947.html
-and
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-November/002581.html
-
-Q: How do I create a cross arch live CD image? A: In short: You can't. Read
-on: The procedure to create a live CD is based on creating a chroot that
-contains the files that will be finally available on the live CD. The live
-CD building procedure includes chrooting into the chroot dir and so some
-operations. chrooting means that the terminal you chroot on will behave as a
-different system so your real system and the chroot environment is decoupled
-somehow. Once the live CD scripts chroots into the chroot dir they have some
-operations to do inside that environment and your real system won't be able
-to run them unless you are using the same architecture. So you only are able
-to make live CD for the arch you run on. But this doesn't prevent you run
-qemu or some other machine emulator that make this possible.
-
-Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That
-depends what you've changed between builds If, for example, you've built an
-iso image and you want a usb image, you only need to run #{lh_clean
---binary}# before you run lh_build again. If you've changed anything in the
-chroot, you'll need to cleanup both chroot and binary with #{lh_clean}#
-before continuing
-
-Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in
-config/binary
-
-Q: How do I include different modules to load when the live system boots? A:
-Configure config/chroot_local-includes/etc/initramfs-tools/
-
-The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default
-initramfs.conf "MODULES = most". You may override that by supplying your own
-initramfs.conf, or else just add your own modules, e.g.
-
-code{
-
-mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo "atl2" >>
-config/chroot_local-includes/etc/initramfs-tools/modules
-
-}code
-
-Note: Even though initramfs.conf(5) says "most adds all the framebuffer,
-acpi, file system, ide, sata, scsi and usb drivers", it actually includes
-network drivers as well. See auto_add_modules() in
-/usr/share/initramfs-tools/hook-functions for the complete list.
-
-Q: Can I have a splash screen? A: Yes you can. You will not know what is
-going on when the splash screen is active, it may fail to activate on some
-hardware or break X on other (both usplash and splashy use libdirectfb which
-does some evil voodoo and may break you graphics or input until you
-reboot). However, you can install and activate it just as you would on any
-other Debian system. To use splashy: 1. install splashy and read the README,
-the manpages are useless for setting it up. Add some parameters to your
-kernel command line, such as in your pxelinux configuration or in
-LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792
-splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy,
-#{quiet}# to suppress most kernel messages that you cannot see anyway but
-would scroll past before splashy manages to paint the graphics on your
-screen. You might want to add splashy to the list of packages installed in
-your image: #{echo splashy > config/chroot_local-packageslists/splashy echo
-splashy-themes >> config/chroot_local-packageslists/splashy}# and select a
-theme:
-
-code{
-
-echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s
-debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the
-ramdisk to include the splash screen echo update-initramfs -u -k all >>
-config/chroot_local-hooks/splashy chmod 755
-config/chroot_local-hooks/splashy
-
-}code
-
-After you rebuild your live system you should observe a bluish splash screen
-while booting. Nothing happens while initramfs is running because there is
-no splashy support in initramfs-tools. Once the init starts the progress bar
-should start to fill. If #{vga=something}# sets a mode that your screen
-cannot show or your card cannot do vesa 2.0 (and thus you get plain text
-mode and no splashy) read the splashy faq.
-
-Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the
-firmwares to the initrd image. You need to install the non-free package
-"firmware-bnx2". Uncompress your initrd image, then copy files:
-
-code{
-
-cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw
-/lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw
-${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/
-
-}code
-
-Recompress your initrd image and boot: it works!
-
-Q: X is broken (the system boots, messages scroll by, and then the screen
-goes blank). What do I do? A: On my system starting X completely disables
-graphics so that I do not see anything even after X bails out and I am back
-to the console. To prevent this you can change the driver Xorg uses.
-
-If you have a working splash screen or at least graphical console you can
-use #{live xdriver=fbdev}# when booting the live system (instead of just
-enter). Another driver you might want to try is #{vesa}#. If all fails you
-might try to set xdriver to some wrong value so that Xorg fails to start and
-you can examine the system while you still see something on the
-console. #{live xdriver=none}#
-
-Q: How can I get Debian first stable versions? A: I'm developing software
-and testing it on Live-CD. Thanks for the LiveCD project. To be sure my
-development is fully compatible with the "etch" version, I need the same
-scenario when Debian GNU/Linux 4.0 was published as stable (I believe
-2007.04.08). If there was some bug on 2007.04.08 that was corrected one week
-later, I need to test software foreseeing that scenario without the bug
-solved.
-
-Q: I get "fopen: Permission denied"-warnings from apt on building/at the
-live-system A: That's a harmless bug in apt. However, if you want to get off
-this warnings in the live-system, add a file in chroot_local-hooks with
-follow row:
-
-code{
-
-chown -R man.man /var/cache/man
-
-}code
-
-Q: Why I always fail during "Retrieving Packages" stage when running
-lh_build? I have already set apt-http-proxy and so on. A: lh_build
-retrieves packages via wget, as a result you need to enable the proxy
-settings in /etc/wgetrc before running lh_build.
-
-Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system
-boots, so it's useless to put modifed Xorg.conf in
-config/choort_local-includes/etc/X11, because it will be overwritten during
-boot. However, you can edit /usr/bin/dexconf, which generate xorg.conf
-during boot, so the result will be modified Xorg.conf. The modified dexconf
-has to be put in config/choort_local-includes/usr/bin. e.g.: you can
-configure Xorg.conf for two or more keyboards layouts with alt+shift toggle
-by editing dexconf and replacing the line:
-
-code{
-
-Option "XkbLayout" "$XKB_LAYOUT"
-
-}code
-
-with the lines:
-
-code{
-
-Option "XkbLayout" "us,il" Option "XkbOptions"
-"grp:alt_shift_toggle,grp_led:scroll"
-
-}code
-
-when "us,il" are the wanted keyboard layouts.
-
-You can force default screen resulotion (e.g. 1024*768) by adding the lines:
-
-code{
-
-SubSection "Display"
- Modes "1024x768"
-EndSubSection
-
-}code
-
-between the lines:
-
-code{
-
-Section "Screen"
- Identifier "Default Screen"
- Monitor "Configured Monitor"
-EndSection"
-
-}code
-
-Q: Where are the build parameters for the prebuilt images A: See
-http://live.debian.net/README.images.
diff --git a/manual/fr/other_howtos.ssi b/manual/fr/other_howtos.ssi
deleted file mode 100644
index 63e84bf..0000000
--- a/manual/fr/other_howtos.ssi
+++ /dev/null
@@ -1,118 +0,0 @@
-B~ Howtos
-
-1~ Howtos
-
-2~ ISO
-
-Generating a Debian Live CD is very simple. You need to have live-helper
-(package available in Debian sid and lenny), and Debootstrap (or
-cdebootstrap) from etch or newer.
-
-3~ Install live-helper
-
-#{apt-get install live-helper}#
-
-3~ Configure the current working directory with lh_config
-
-code{
-
-lh_config -b iso -a $ARCH
-
-}code
-
-where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64).
-
-#{-b}# flag is used to be sure to obtain image in ISO format.
-
-3~ Build the image with lh_build:
-
-Execute lh_build as root: #{lh_build}#
-
-The command above will create the basic image, containing just the Debian
-standard system (with no X at all).
-
-If you want to have any of the Desktop environments on your livecd, #{ls
-/usr/share/live-helper/lists}# will show a number of available package Lists
-to choose from, e.g. #{lh_config -p gnome-desktop}#
-
-More examples are listed at DebianLive/Examples.
-
-See packages for help configuring a local Debian Mirror and other aspects of
-the live system. % FIXME: <xref linkend="packages"/>
-
-3~ Test the image
-
-If you have qemu installed, you can boot the image with:
-
-code{
-
-qemu -cdrom binary.iso
-
-}code
-
-If you have also kqemu installed, you can add #{-kernel-kqemu}#
-
-2~ ISO_(multiarch)
-
-Multiple machine boot CDs can be created with the following manual
-procedure. This procedure has been successfully used to create a single CD
-which is bootable on alpha, i386, pmax, and sparc. It should be possible to
-also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x.
-
-To create a CD which is bootable by multiple architectures, use the
-following steps in this order. Please note that the order is critical.
-
-Make sure you have all the required files including the various kernels and
-boot programs listed in the individual machine sections.
-
-Include a directory somewhere in the cdsources directory called mdec.pmax
-and include the pmax bootxx_cd9660 file there. For example,
-/cdsources/usr/mdec.pmax/bootxx_cd9660.
-
-Include a directory somewhere in the cdsources directory called mdec.vax and
-include the vax xxboot file there. For example,
-#{cdsources/usr/mdec.vax/xxboot.}#
-
-Include the macppc ofwboot.xcf bootloader in /cdsources.
-
-Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b
-i386/installation/floppy/boot-big.fs \ -c boot.catalog -l -J -r -L
-/cdsources 2>&1 | tee /tmp/mkisofs.log exit}#
-
-Note: The appearance of the -v flag twice is required. If you are making a
-bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs
--part in the parameters for mkisofs.
-
-Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3
-bootblocks. Alternatively, install the sysutils/mksunbootcd package on your
-favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs
-boot-sun4m.fs boot-sun3.fs}#
-
-Run the installboot(8) program targeted for NetBSD/pmax to install the pmax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-pmax boot block is appended to the end of the ISO file system.
-
-#{installboot -m pmax -v -o append,sunsum output.iso
-/tmp/mdec.pmax/bootxx_cd9660}#
-
-The -o append,sunsum option appends the first stage boot block to the end of
-the ISO file system, and restores the checksum used when booting on a sun.
-
-Run the installboot(8) program targeted for NetBSD/vax to install the vax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-vax boot block is appended to the end of the ISO file system.
-
-installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot
-
-(See the pmax entry above for an explanation of the flags).
-
-Run the installboot(8) program targeted for NetBSD/alpha to install the
-alpha bootblocks.
-
-#{installboot -m alpha -v -o append,sunsum output.iso
-/tmp/mdec.alpha/bootxx_cd9660}#
-
-Note: The alpha installboot must occur after the others, because currently
-it's the only machine dependent back-end for installboot(8) that can
-calculate the alpha checksum. (See the pmax entry above for an explanation
-of the flags).
diff --git a/manual/it/live-manual.ssm b/manual/it/live-manual.ssm
index 6ec24b4..0fb5196 100644
--- a/manual/it/live-manual.ssm
+++ b/manual/it/live-manual.ssm
@@ -63,6 +63,3 @@
<< user_examples.ssi
-% << other_faq.ssi
-
-% << other_howtos.ssi
diff --git a/manual/it/other_faq.ssi b/manual/it/other_faq.ssi
deleted file mode 100644
index f754913..0000000
--- a/manual/it/other_faq.ssi
+++ /dev/null
@@ -1,545 +0,0 @@
-B~ Frequently asked questions (FAQ)
-
-1~ Frequently asked questions (FAQ)
-
-Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A:
-See "Copying USB/HDD image to a USB stick" % FIXME: <xref
-linkend="image_copying"/>
-
-Q: How do I log my build? A: You could use script, screen or tee: #{$
-lh_build 2>&1 | tee build.log}#
-
-Q: How can I convert an already installed standard Debian partition into a
-Debian Live system? A: Save the list of installed packages and load it into
-your new Debian Live System. Copy your /etc to config/chroot_local-includes
-
-Q: What does 'losetup: could not find any free loop device' mean and how do
-I fix it? A: Loop devices are used during the build; there probably aren't
-any free if you've aborted several builds. Something like: for l in
-/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6
-/dev/loop7 ; do losetup -d $l ; done should rectify the situation (assuming
-all loop devices in use were created by lh_build; if in doubt, check the
-contents of each loop device before deleting them with losetup -d).
-
-Q: How do I launch an interactive shell during the chroot stage? A: To
-enable interactive shell: #{$ lh_config --interactive shell}# To continue
-the build process: #{# logout}# or #{# exit}# To disable interactive shell,
-set LH_INTERACTIVE to "disabled" in config/chroot.
-
-Q: What is the root /user password? A: The user password for the live user
-is 'live'. By default, there is not any root password. You can switch to
-root with ${sudo -i}# or set a password for root with #{sudo passwd}#
-
-Q: How do I change root or any user password? A: Add a chroot local hook
-script to change root or any user password each time you build an image.
-e.g. config/chroot_local-hooks/01-update_password.sh to set root password to
-"nopasswd"
-
-code{ #!/bin/sh
-
-echo "I: update password" echo "root:nopasswd" | chpasswd
-
-$ chmod +x config/chroot_local-hooks/01-update_password.sh
-
-}code
-
-Note for live user; you need to copy the
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser your build folder:
-
-code{
-
-mkdir -p
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-
-}code
-
-Note: Then edit the
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-and paste in the new user_crypted password that you make with: #{echo
-"newlivepass" | mkpasswd -s}#
-
-Or add an hook file in config/chroot_local-hooks/ with something like the
-below:
-
-code{ #!/bin/sh
-
-# Change the autogenerated user password to "debianlive"
-plain_password="debianlive" password=$(echo "${plain_password}" | mkpasswd
--s)
-
-sed -i -e 's/\(user_crypted=\)\(.*\)\( #.*\)/\1\"'${password}'\"\3/'
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-
-update-initramfs -tu -kall }code
-
-The latter (hook model) could be more future proof than the former solution
-since it modifies just one string selectively but it requires the package
-"whois" to be installed on the target system (for mkpasswd) or that you
-generate the $password string not at build time and include it crypted in
-the above script.
-
-Q: How to disable autologin? A1: use the commandline parameter #{lh config
---bootappend-live "noautologin"}# A2: You need to set boot=noautologin
-noxautologin as described in man live-initramfs If you boot via TFTP you
-want to insert the option to pxelinux.cfg/default
-
-Q: How do I change default hostname or username? A: To change default
-hostname or username: #{$ lh_config --hostname myhostname $ lh_config
---username myusername}#
-
-Q: How do I make the final image smaller? A: Clean orphaned apps/libs:
-Install package "deborphan" and then run 'sudo deborphan -n' . Delete
-unwanted packages. Remove the apt cache. Purge unwanted locales (see
-"localepurge" package).
-
-Q: How do I customize bash-config permanently (aliases, bash-completion
-etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc
-
-Q: How do I disable services permanently? (Be careful!) A: Add a chroot
-local hook script to disable a service each time you build an image:
-e.g. config/chroot_local-hooks/01-disable_service.sh
-
-code{
-
-#!/bin/sh
-
-echo "I: disable service" update-rc.d -f service_name remove
-
-$ chmod +x config/chroot_local-hooks/01-disable_service.sh
-
-}code
-
-Q: How do I enable | disable the md5checksum at the ISO building? A:
-#{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value.
-
-Q: How to disable the generation of the .tar.gz file? A: #{lh_config
---net-tarball none|gzip}# Or change the LH_NET_TARBALL value. (only
-available in snapsshot version at the moment 2008/Feb/28)
-
-Q: How do I "build a new image"? A: Run commands:
-
-code{
-
-$ sudo lh_clean --binary $ sudo lh_build
-
-}code
-
-Hint: If the configuration had changed you should leave "--binary" out. This
-will clean your chroot directory too.
-
-Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages
-you want.
-
-Create /home/$USERNAME/.dmrc file (default username is "user").
-
-code{
-
-$ cat .dmrc [Desktop] Session=fluxbox }code
-
-Note: .dmrc is owned by $USERNAME:$USERNAME.
-
-See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at
-http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD
-
-Q: How do I use custom repositories? A: See
-http://wiki.debian.org/DebianLive/Configuration
-
-Q: How do I customize the artwork for the live CD (grub or syslinux boot
-splash, usplash, etc.)? A: See
-http://wiki.debian.org/DebianLive/Howto/Custom_Artwork
-
-Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look?
-A: Start the live system in qemu:
-
-code{
-
-$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22
-
-}code
-
-Note: the -redir argument must be changed to meet your needs
-
-Q: How do I execute a custom shell script inside the chroot system after the
-chroot stage? A: Add your script in config/chroot_local-hooks.
-
-Q: How do I add a script running immediately after all other scripts when
-the live system boots? A: Add your script in
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99scrip
-
-code{
-
-$ chmod +x
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99script
-
-}code
-
-Note: The hook script must be executable. Do not forget to lh_clean --chroot
-after making this change before you build again.
-
-You must also use the example script
-/usr/share/live-helper/examples/hooks/update-initramfs.sh to ensure your
-script gets built into the initramfs (read the comment header for
-instructions).
-
-Q: How do I add software not in Debian ? A: See Customizing package
-installation % FIXME: <xref linkend="packages"/>
-
-Q: What is the manifest with Ubuntu used for? A: Manifest is just the
-package list, which ubuntu does $something with. Don't worry about it.
-
-Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude.
-
-Q: Do I need to write the image on USB stick to test it? A: you must use
-qemu >= 0.8.
-
-Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs.
-
-Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed
-something else entirely? A: It is not. It is a package list, not a debconf
-preseeding.
-
-Q: What is the difference between standard and minimal? A: standard:
-packages of priority standard and higher; minimal: packages of priority
-essential and higher;
-
-Q: What can the sections be used for? Aren't they BIG? A: Someone maybe
-wants to include packages from contrib or non-free.
-
-Q: memtest86+ ... is that used? A: Yes
-
-Q: How do I build using predefined packages lists? A: e.g. to build using
-standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo
-lh_build}# Note: The packages lists can be found in
-/usr/share/live-helper/lists/ directory.
-
-Q: How do I rebuild without downloading all the packages again? A: All
-packages are cached in cache subdirectory. They remain until a clean purge:
-#{$ sudo lh_clean --purge}# You do not have to do anything to prevent
-packages from being re-downloaded. You need to remember to clean whichever
-stages you want to rebuild first. e.g. to rebuild from the cached bootstrap,
-chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#
-
-Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make
-a boot CD with grub, configured to boot from a debian-live kernel copied on
-the cd structure #{$ mkdir -p iso/boot/grub && cp
-/usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub && cp chroot/boot/*
-iso/boot/}# Create iso/boot/grub/menu.lst:
-
-code{
-
-default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd)
-kernel /boot/vmlinuz boot=live initrd /boot/initrd.img
-
-}code
-
-Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito
--no-emul-boot \ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn
-the image.
-
-Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A:
-If you have a floppy drive, you may be able to use it, otherwise you will
-need to use loadlin/grub4dos/win32-loader. If you have a second system to
-serve up the image over the network, See
-http://wiki.debian.org/DebianLive/Howto/Creating_a_Netboot_Image
-
-Q: The X configuration does not seems to work, the resolution is too
-low. What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend
-xdebconf && lh_config --packages xdebconfigurator}#
-
-Q: Apache has problems with static files A: Sendfile does not work well on
-the unionfs used by Debian Live. Add the following to apache's
-configuration: #{EnableSendfile off}#
-
-Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right
-now the best is to use a script that will populate the fstab when the CD is
-booting. Such a script can be found at
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh.
-A proper solution based on HAL will be described here in a hopefully near
-future. A: Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL,
-debian-storage-policy-fixed-drives.fdi is not available anymore and the
-previous trick that consisted to remove this file to enable automounting of
-fixed drives as a consequence is obsolete. Eventually, it will be possible
-to combine HAL and PolicyKit to enable different permissions and actions to
-achieve advanced (auto)mounting for non-root users. Until then, because the
-live scripts are only touching to the fstab to add a swap partition if
-discovered at boot time, the only way to have fixed drives mounted
-automatically is to use a script that will populate the fstab file at the
-end of the multiuser runlevel. To achieve this, you can do, for example, the
-following: download the
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh
-script Create the chroot_local-includes/sbin directory, and move the script
-inside Make sure the script is executable (chmod +x diskmounter.sh) create
-the chroot_local-includes/etc/rc.local file and call the diskmounter from
-there (see this
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local
-When called correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32,
-HFS+ and NTFS partitions and mount them read-write, except for NTFS. This
-will change soon and an option will be available to use ntfs-3g to mount
-NTFS as read-write. comments, patches and other things about this script and
-issue: http://code.goto10.org/projects/puredyne/ticket/463
-
-Q: Boot fails with panic: can't open /scripts/live A: Add latest
-live-initramfs deb package into config/chroot_local-packages directory and
-rebuild.
-
-Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref
-linkend="internalization"/>
-
-Q: How do I get past boot prompt without a working keyboard? A: See
-Customizing the bootup process % FIXME: <xref linkend="bootup"/> Note: Boot
-from an USB-HDD on an iMac with GRUB did not work.
-
-Q: Can I serve the root image from a web or ftp server? A: Since
-live-initramfs 1.99, it should be possible to use the fetch= argument on the
-kernel command line. You can build a netboot image as usual, and when you
-are done edit the tftpboot/pxelinux.cfg/default file. Remove the references
-to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url
-where you placed the root image>. You have to include wget in the chroot. It
-could work for other boot methods as well. However, I am not sure the live
-scripts configure the network when booting from a CD or USB disk. #{$
-lh_config --packages wget}#
-
-Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you
-are building an etch image (which was the default up to 2007/09/14) you have
-a very old version of casper which does not support quickreboot and possibly
-other boot parameters as well. You could configure your sources to use
-live-backports (see /usr/share/live-helper/examples/sources/live-backports)
-and switch to live-initramfs, or better yet, build a lenny image instead,
-which is the new default. #{$ lh_config --distribution lenny $ lh_config
---initramfs live-initramfs}#
-
-Q: How do I fix "Could not find kernel image" issue with syslinux
-bootloader? A: Add a binary local hook script to fix kernel and initrd path
-each time you build an
-image. e.g. config/binary_local-hooks/01-fix_syslinux.sh
-
-code{
-
-#!/bin/sh
-
-SYSLINUXCFG=`find binary -type f -name syslinux.cfg`
-
-sed -i "s|kernel /vmlinuz|kernel vmlinuz|g" ${SYSLINUXCFG} sed -i
-"s|initrd=/initrd|initrd=initrd|g" ${SYSLINUXCFG}
-
-$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh
-
-}code
-
-Q: How do I use a newer kernel with lenny? A: A build with backports.org
-kernels will fail as that repository lacks the necessary module packages
-(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports
-http://unsupported.debian-maintainers.org/backports-kernel/ The quick way to
-success:
-
-code{
-
-$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6
-squashfs-modules-2.6' $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.chroot $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.binary $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.chroot.gpg $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.binary.gpg $ lh_build }code
-
-Q: How do I use a custom kernel? Is there a nice way of booting debian-live
-with a custom kernel (not in an apt repo)? A: Copy it into
-config/chroot_local-packages and set LH_LINUX_PACKAGES="none" or use lh
-config --linux-packages " " Don't forget to compile your kernel with an
-union filesystem (unionfs or aufs), squashfs modules, and initrd support. I
-can cause the kernel to be installed but it seems this happens later than
-grub/syslinux is configured so it's not listed and casper/ and the menu
-require munging. You need to follow the debian scheme, e.g. placing the
-files in /boot as vmlinuz-$version and initrd.img-$version etc. I personally
-wouldn't go that way which is too much of a hassle, and just use make-kpkg
-to produce custom kernel deb packages. They should integrate nicely if you
-just put them into config/chroot_local-packages and set
-LH_LINUX_PACKAGES="". Hint: to work around an error, which
-lh_binary_syslinux will throw on custom kernels if there is not an 468/686
-in the kernel-name, you need to set CONFIG_LOCALVERSION="-486" or "-686"
-within the kernel configuration (-> General setup -> Local version set
-to -486 or -686) corresponding to LH_LINUX_FLAVOURS="" or "686". this at
-least up till live-helper version 1.0~a40-1 see
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-July/001947.html
-and
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-November/002581.html
-
-Q: How do I create a cross arch live CD image? A: In short: You can't. Read
-on: The procedure to create a live CD is based on creating a chroot that
-contains the files that will be finally available on the live CD. The live
-CD building procedure includes chrooting into the chroot dir and so some
-operations. chrooting means that the terminal you chroot on will behave as a
-different system so your real system and the chroot environment is decoupled
-somehow. Once the live CD scripts chroots into the chroot dir they have some
-operations to do inside that environment and your real system won't be able
-to run them unless you are using the same architecture. So you only are able
-to make live CD for the arch you run on. But this doesn't prevent you run
-qemu or some other machine emulator that make this possible.
-
-Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That
-depends what you've changed between builds If, for example, you've built an
-iso image and you want a usb image, you only need to run #{lh_clean
---binary}# before you run lh_build again. If you've changed anything in the
-chroot, you'll need to cleanup both chroot and binary with #{lh_clean}#
-before continuing
-
-Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in
-config/binary
-
-Q: How do I include different modules to load when the live system boots? A:
-Configure config/chroot_local-includes/etc/initramfs-tools/
-
-The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default
-initramfs.conf "MODULES = most". You may override that by supplying your own
-initramfs.conf, or else just add your own modules, e.g.
-
-code{
-
-mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo "atl2" >>
-config/chroot_local-includes/etc/initramfs-tools/modules
-
-}code
-
-Note: Even though initramfs.conf(5) says "most adds all the framebuffer,
-acpi, file system, ide, sata, scsi and usb drivers", it actually includes
-network drivers as well. See auto_add_modules() in
-/usr/share/initramfs-tools/hook-functions for the complete list.
-
-Q: Can I have a splash screen? A: Yes you can. You will not know what is
-going on when the splash screen is active, it may fail to activate on some
-hardware or break X on other (both usplash and splashy use libdirectfb which
-does some evil voodoo and may break you graphics or input until you
-reboot). However, you can install and activate it just as you would on any
-other Debian system. To use splashy: 1. install splashy and read the README,
-the manpages are useless for setting it up. Add some parameters to your
-kernel command line, such as in your pxelinux configuration or in
-LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792
-splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy,
-#{quiet}# to suppress most kernel messages that you cannot see anyway but
-would scroll past before splashy manages to paint the graphics on your
-screen. You might want to add splashy to the list of packages installed in
-your image: #{echo splashy > config/chroot_local-packageslists/splashy echo
-splashy-themes >> config/chroot_local-packageslists/splashy}# and select a
-theme:
-
-code{
-
-echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s
-debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the
-ramdisk to include the splash screen echo update-initramfs -u -k all >>
-config/chroot_local-hooks/splashy chmod 755
-config/chroot_local-hooks/splashy
-
-}code
-
-After you rebuild your live system you should observe a bluish splash screen
-while booting. Nothing happens while initramfs is running because there is
-no splashy support in initramfs-tools. Once the init starts the progress bar
-should start to fill. If #{vga=something}# sets a mode that your screen
-cannot show or your card cannot do vesa 2.0 (and thus you get plain text
-mode and no splashy) read the splashy faq.
-
-Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the
-firmwares to the initrd image. You need to install the non-free package
-"firmware-bnx2". Uncompress your initrd image, then copy files:
-
-code{
-
-cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw
-/lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw
-${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/
-
-}code
-
-Recompress your initrd image and boot: it works!
-
-Q: X is broken (the system boots, messages scroll by, and then the screen
-goes blank). What do I do? A: On my system starting X completely disables
-graphics so that I do not see anything even after X bails out and I am back
-to the console. To prevent this you can change the driver Xorg uses.
-
-If you have a working splash screen or at least graphical console you can
-use #{live xdriver=fbdev}# when booting the live system (instead of just
-enter). Another driver you might want to try is #{vesa}#. If all fails you
-might try to set xdriver to some wrong value so that Xorg fails to start and
-you can examine the system while you still see something on the
-console. #{live xdriver=none}#
-
-Q: How can I get Debian first stable versions? A: I'm developing software
-and testing it on Live-CD. Thanks for the LiveCD project. To be sure my
-development is fully compatible with the "etch" version, I need the same
-scenario when Debian GNU/Linux 4.0 was published as stable (I believe
-2007.04.08). If there was some bug on 2007.04.08 that was corrected one week
-later, I need to test software foreseeing that scenario without the bug
-solved.
-
-Q: I get "fopen: Permission denied"-warnings from apt on building/at the
-live-system A: That's a harmless bug in apt. However, if you want to get off
-this warnings in the live-system, add a file in chroot_local-hooks with
-follow row:
-
-code{
-
-chown -R man.man /var/cache/man
-
-}code
-
-Q: Why I always fail during "Retrieving Packages" stage when running
-lh_build? I have already set apt-http-proxy and so on. A: lh_build
-retrieves packages via wget, as a result you need to enable the proxy
-settings in /etc/wgetrc before running lh_build.
-
-Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system
-boots, so it's useless to put modifed Xorg.conf in
-config/choort_local-includes/etc/X11, because it will be overwritten during
-boot. However, you can edit /usr/bin/dexconf, which generate xorg.conf
-during boot, so the result will be modified Xorg.conf. The modified dexconf
-has to be put in config/choort_local-includes/usr/bin. e.g.: you can
-configure Xorg.conf for two or more keyboards layouts with alt+shift toggle
-by editing dexconf and replacing the line:
-
-code{
-
-Option "XkbLayout" "$XKB_LAYOUT"
-
-}code
-
-with the lines:
-
-code{
-
-Option "XkbLayout" "us,il" Option "XkbOptions"
-"grp:alt_shift_toggle,grp_led:scroll"
-
-}code
-
-when "us,il" are the wanted keyboard layouts.
-
-You can force default screen resulotion (e.g. 1024*768) by adding the lines:
-
-code{
-
-SubSection "Display"
- Modes "1024x768"
-EndSubSection
-
-}code
-
-between the lines:
-
-code{
-
-Section "Screen"
- Identifier "Default Screen"
- Monitor "Configured Monitor"
-EndSection"
-
-}code
-
-Q: Where are the build parameters for the prebuilt images A: See
-http://live.debian.net/README.images.
diff --git a/manual/it/other_howtos.ssi b/manual/it/other_howtos.ssi
deleted file mode 100644
index 63e84bf..0000000
--- a/manual/it/other_howtos.ssi
+++ /dev/null
@@ -1,118 +0,0 @@
-B~ Howtos
-
-1~ Howtos
-
-2~ ISO
-
-Generating a Debian Live CD is very simple. You need to have live-helper
-(package available in Debian sid and lenny), and Debootstrap (or
-cdebootstrap) from etch or newer.
-
-3~ Install live-helper
-
-#{apt-get install live-helper}#
-
-3~ Configure the current working directory with lh_config
-
-code{
-
-lh_config -b iso -a $ARCH
-
-}code
-
-where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64).
-
-#{-b}# flag is used to be sure to obtain image in ISO format.
-
-3~ Build the image with lh_build:
-
-Execute lh_build as root: #{lh_build}#
-
-The command above will create the basic image, containing just the Debian
-standard system (with no X at all).
-
-If you want to have any of the Desktop environments on your livecd, #{ls
-/usr/share/live-helper/lists}# will show a number of available package Lists
-to choose from, e.g. #{lh_config -p gnome-desktop}#
-
-More examples are listed at DebianLive/Examples.
-
-See packages for help configuring a local Debian Mirror and other aspects of
-the live system. % FIXME: <xref linkend="packages"/>
-
-3~ Test the image
-
-If you have qemu installed, you can boot the image with:
-
-code{
-
-qemu -cdrom binary.iso
-
-}code
-
-If you have also kqemu installed, you can add #{-kernel-kqemu}#
-
-2~ ISO_(multiarch)
-
-Multiple machine boot CDs can be created with the following manual
-procedure. This procedure has been successfully used to create a single CD
-which is bootable on alpha, i386, pmax, and sparc. It should be possible to
-also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x.
-
-To create a CD which is bootable by multiple architectures, use the
-following steps in this order. Please note that the order is critical.
-
-Make sure you have all the required files including the various kernels and
-boot programs listed in the individual machine sections.
-
-Include a directory somewhere in the cdsources directory called mdec.pmax
-and include the pmax bootxx_cd9660 file there. For example,
-/cdsources/usr/mdec.pmax/bootxx_cd9660.
-
-Include a directory somewhere in the cdsources directory called mdec.vax and
-include the vax xxboot file there. For example,
-#{cdsources/usr/mdec.vax/xxboot.}#
-
-Include the macppc ofwboot.xcf bootloader in /cdsources.
-
-Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b
-i386/installation/floppy/boot-big.fs \ -c boot.catalog -l -J -r -L
-/cdsources 2>&1 | tee /tmp/mkisofs.log exit}#
-
-Note: The appearance of the -v flag twice is required. If you are making a
-bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs
--part in the parameters for mkisofs.
-
-Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3
-bootblocks. Alternatively, install the sysutils/mksunbootcd package on your
-favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs
-boot-sun4m.fs boot-sun3.fs}#
-
-Run the installboot(8) program targeted for NetBSD/pmax to install the pmax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-pmax boot block is appended to the end of the ISO file system.
-
-#{installboot -m pmax -v -o append,sunsum output.iso
-/tmp/mdec.pmax/bootxx_cd9660}#
-
-The -o append,sunsum option appends the first stage boot block to the end of
-the ISO file system, and restores the checksum used when booting on a sun.
-
-Run the installboot(8) program targeted for NetBSD/vax to install the vax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-vax boot block is appended to the end of the ISO file system.
-
-installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot
-
-(See the pmax entry above for an explanation of the flags).
-
-Run the installboot(8) program targeted for NetBSD/alpha to install the
-alpha bootblocks.
-
-#{installboot -m alpha -v -o append,sunsum output.iso
-/tmp/mdec.alpha/bootxx_cd9660}#
-
-Note: The alpha installboot must occur after the others, because currently
-it's the only machine dependent back-end for installboot(8) that can
-calculate the alpha checksum. (See the pmax entry above for an explanation
-of the flags).
diff --git a/manual/po/de/live-manual.ssm.po b/manual/po/de/live-manual.ssm.po
index acc09fd..d23f3b8 100644
--- a/manual/po/de/live-manual.ssm.po
+++ b/manual/po/de/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:18-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-10-03 20:30+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -173,13 +173,3 @@ msgstr ""
#: en/live-manual.ssm:65
msgid "<< user_examples.ssi"
msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:67
-msgid "% << other_faq.ssi"
-msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:68
-msgid "% << other_howtos.ssi"
-msgstr ""
diff --git a/manual/po/de/other_faq.ssi.po b/manual/po/de/other_faq.ssi.po
deleted file mode 100644
index 3e14c24..0000000
--- a/manual/po/de/other_faq.ssi.po
+++ /dev/null
@@ -1,1008 +0,0 @@
-# German translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-16 14:45-0200\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: de\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:83 en/about_manual.ssi:91 en/about_manual.ssi:99
-#: en/about_manual.ssi:111 en/about_manual.ssi:124 en/about_manual.ssi:137
-#: en/about_manual.ssi:145 en/about_manual.ssi:153 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_faq.ssi:41 en/other_faq.ssi:83 en/other_faq.ssi:103
-#: en/other_faq.ssi:117 en/other_faq.ssi:137 en/other_faq.ssi:151
-#: en/other_faq.ssi:198 en/other_faq.ssi:245 en/other_faq.ssi:261
-#: en/other_faq.ssi:287 en/other_faq.ssi:299 en/other_faq.ssi:314
-#: en/other_faq.ssi:333 en/other_faq.ssi:345 en/other_faq.ssi:353
-#: en/other_faq.ssi:364 en/other_faq.ssi:374 en/other_howtos.ssi:16
-#: en/other_howtos.ssi:43 en/other_live-environment.ssi:14
-#: en/other_live-environment.ssi:30 en/other_live-environment.ssi:51
-#: en/other_live-environment.ssi:61 en/other_live-environment.ssi:69
-#: en/other_live-environment.ssi:77 en/other_live-environment.ssi:85
-#: en/other_live-environment.ssi:93 en/other_live-environment.ssi:116
-#: en/other_live-environment.ssi:124 en/other_live-environment.ssi:133
-#: en/other_procedures.ssi:12 en/other_procedures.ssi:46
-#: en/other_procedures.ssi:58 en/other_use-cases.ssi:24
-#: en/other_use-cases.ssi:49 en/other_use-cases.ssi:75
-#: en/other_use-cases.ssi:103 en/other_use-cases.ssi:111 en/user_basics.ssi:36
-#: en/user_basics.ssi:48 en/user_basics.ssi:62 en/user_basics.ssi:74
-#: en/user_basics.ssi:86 en/user_basics.ssi:98 en/user_basics.ssi:114
-#: en/user_basics.ssi:122 en/user_basics.ssi:130 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:180 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:212 en/user_basics.ssi:232 en/user_basics.ssi:265
-#: en/user_basics.ssi:281 en/user_basics.ssi:289 en/user_basics.ssi:309
-#: en/user_basics.ssi:334 en/user_customization-contents.ssi:34
-#: en/user_customization-contents.ssi:43 en/user_customization-contents.ssi:66
-#: en/user_customization-internationalization.ssi:10
-#: en/user_customization-internationalization.ssi:18
-#: en/user_customization-internationalization.ssi:26
-#: en/user_customization-internationalization.ssi:38
-#: en/user_customization-packages.ssi:16 en/user_customization-packages.ssi:24
-#: en/user_customization-packages.ssi:36 en/user_customization-packages.ssi:45
-#: en/user_customization-packages.ssi:59 en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:106
-#: en/user_installation.ssi:120 en/user_installation.ssi:137
-#: en/user_managing_a_configuration.ssi:24
-#: en/user_managing_a_configuration.ssi:35
-#: en/user_managing_a_configuration.ssi:47 en/user_overview.ssi:60
-#: en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr ""
-
-#. type: Plain text
-#: en/about_manual.ssi:87 en/about_manual.ssi:95 en/about_manual.ssi:103
-#: en/about_manual.ssi:120 en/about_manual.ssi:133 en/about_manual.ssi:141
-#: en/about_manual.ssi:149 en/about_manual.ssi:157 en/about_manual.ssi:164
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_faq.ssi:37 en/other_faq.ssi:46 en/other_faq.ssi:92
-#: en/other_faq.ssi:108 en/other_faq.ssi:141 en/other_faq.ssi:155
-#: en/other_faq.ssi:207 en/other_faq.ssi:256 en/other_faq.ssi:292
-#: en/other_faq.ssi:307 en/other_faq.ssi:319 en/other_faq.ssi:337
-#: en/other_faq.ssi:349 en/other_faq.ssi:358 en/other_faq.ssi:370
-#: en/other_faq.ssi:381 en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:92
-#: en/user_basics.ssi:104 en/user_basics.ssi:118 en/user_basics.ssi:126
-#: en/user_basics.ssi:134 en/user_basics.ssi:144 en/user_basics.ssi:158
-#: en/user_basics.ssi:168 en/user_basics.ssi:176 en/user_basics.ssi:184
-#: en/user_basics.ssi:198 en/user_basics.ssi:206 en/user_basics.ssi:216
-#: en/user_basics.ssi:257 en/user_basics.ssi:285 en/user_basics.ssi:293
-#: en/user_basics.ssi:320 en/user_basics.ssi:359
-#: en/user_customization-contents.ssi:39 en/user_customization-contents.ssi:54
-#: en/user_customization-contents.ssi:70
-#: en/user_customization-internationalization.ssi:14
-#: en/user_customization-internationalization.ssi:22
-#: en/user_customization-internationalization.ssi:30
-#: en/user_customization-internationalization.ssi:42
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:172
-#: en/user_customization-packages.ssi:182
-#: en/user_customization-packages.ssi:192
-#: en/user_customization-packages.ssi:202 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:88 en/user_installation.ssi:110
-#: en/user_installation.ssi:125 en/user_installation.ssi:140
-#: en/user_managing_a_configuration.ssi:31
-#: en/user_managing_a_configuration.ssi:43
-#: en/user_managing_a_configuration.ssi:52 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:2
-msgid "B~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:4
-msgid "1~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:8
-msgid ""
-"Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A: "
-"See \"Copying USB/HDD image to a USB stick\" % FIXME: <xref linkend="
-"\"image_copying\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:11
-msgid ""
-"Q: How do I log my build? A: You could use script, screen or tee: #{$ "
-"lh_build 2>&1 | tee build.log}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:14
-msgid ""
-"Q: How can I convert an already installed standard Debian partition into a "
-"Debian Live system? A: Save the list of installed packages and load it into "
-"your new Debian Live System. Copy your /etc to config/chroot_local-includes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:17
-msgid ""
-"Q: What does 'losetup: could not find any free loop device' mean and how do "
-"I fix it? A: Loop devices are used during the build; there probably aren't "
-"any free if you've aborted several builds. Something like: for l in /dev/"
-"loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/"
-"loop7 ; do losetup -d $l ; done should rectify the situation (assuming all "
-"loop devices in use were created by lh_build; if in doubt, check the "
-"contents of each loop device before deleting them with losetup -d)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:20
-msgid ""
-"Q: How do I launch an interactive shell during the chroot stage? A: To "
-"enable interactive shell: #{$ lh_config --interactive shell}# To continue "
-"the build process: #{# logout}# or #{# exit}# To disable interactive shell, "
-"set LH_INTERACTIVE to \"disabled\" in config/chroot."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:23
-msgid ""
-"Q: What is the root /user password? A: The user password for the live user "
-"is 'live'. By default, there is not any root password. You can switch to "
-"root with ${sudo -i}# or set a password for root with #{sudo passwd}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:27
-msgid ""
-"Q: How do I change root or any user password? A: Add a chroot local hook "
-"script to change root or any user password each time you build an image. e."
-"g. config/chroot_local-hooks/01-update_password.sh to set root password to "
-"\"nopasswd\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:30 en/other_faq.ssi:53
-msgid "code{ #!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:33
-msgid "echo \"I: update password\" echo \"root:nopasswd\" | chpasswd"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:35
-msgid "$ chmod +x config/chroot_local-hooks/01-update_password.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:39
-msgid ""
-"Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/"
-"live-bottom/10adduser your build folder:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:44
-msgid ""
-"mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-"
-"bottom/ cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/"
-"chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:48
-msgid ""
-"Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/"
-"scripts/live-bottom/10adduser and paste in the new user_crypted password "
-"that you make with: #{echo \"newlivepass\" | mkpasswd -s}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:50
-msgid ""
-"Or add an hook file in config/chroot_local-hooks/ with something like the "
-"below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:57
-msgid ""
-"# Change the autogenerated user password to \"debianlive\" plain_password="
-"\"debianlive\" password=$(echo \"${plain_password}\" | mkpasswd -s)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:59
-msgid ""
-"sed -i -e 's/\\(user_crypted=\\)\\(.*\\)\\( #.*\\)/\\1\\\"'${password}'\\"
-"\"\\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:62
-msgid "update-initramfs -tu -kall }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:64
-msgid ""
-"The latter (hook model) could be more future proof than the former solution "
-"since it modifies just one string selectively but it requires the package "
-"\"whois\" to be installed on the target system (for mkpasswd) or that you "
-"generate the $password string not at build time and include it crypted in "
-"the above script."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:68
-msgid ""
-"Q: How to disable autologin? A1: use the commandline parameter #{lh config --"
-"bootappend-live \"noautologin\"}# A2: You need to set boot=noautologin "
-"noxautologin as described in man live-initramfs If you boot via TFTP you "
-"want to insert the option to pxelinux.cfg/default"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:71
-msgid ""
-"Q: How do I change default hostname or username? A: To change default "
-"hostname or username: #{$ lh_config --hostname myhostname $ lh_config --"
-"username myusername}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:74
-msgid ""
-"Q: How do I make the final image smaller? A: Clean orphaned apps/libs: "
-"Install package \"deborphan\" and then run 'sudo deborphan -n' . Delete "
-"unwanted packages. Remove the apt cache. Purge unwanted locales (see "
-"\"localepurge\" package)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:77
-msgid ""
-"Q: How do I customize bash-config permanently (aliases, bash-completion "
-"etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:81
-msgid ""
-"Q: How do I disable services permanently? (Be careful!) A: Add a chroot "
-"local hook script to disable a service each time you build an image: e.g. "
-"config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:88
-msgid "echo \"I: disable service\" update-rc.d -f service_name remove"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:90
-msgid "$ chmod +x config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:95
-msgid ""
-"Q: How do I enable | disable the md5checksum at the ISO building? A: #"
-"{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:98
-msgid ""
-"Q: How to disable the generation of the .tar.gz file? A: #{lh_config --net-"
-"tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in "
-"snapsshot version at the moment 2008/Feb/28)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:101
-msgid "Q: How do I \"build a new image\"? A: Run commands:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:106
-msgid "$ sudo lh_clean --binary $ sudo lh_build"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:110
-msgid ""
-"Hint: If the configuration had changed you should leave \"--binary\" out. "
-"This will clean your chroot directory too."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:113
-msgid ""
-"Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages "
-"you want."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:115
-msgid "Create /home/$USERNAME/.dmrc file (default username is \"user\")."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:122
-msgid "$ cat .dmrc [Desktop] Session=fluxbox }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:124
-msgid "Note: .dmrc is owned by $USERNAME:$USERNAME."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:126
-msgid ""
-"See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at "
-"http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:129
-msgid ""
-"Q: How do I use custom repositories? A: See http://wiki.debian.org/"
-"DebianLive/Configuration"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:132
-msgid ""
-"Q: How do I customize the artwork for the live CD (grub or syslinux boot "
-"splash, usplash, etc.)? A: See http://wiki.debian.org/DebianLive/Howto/"
-"Custom_Artwork"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:135
-msgid ""
-"Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look? "
-"A: Start the live system in qemu:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:139
-msgid "$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:143
-msgid "Note: the -redir argument must be changed to meet your needs"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:146
-msgid ""
-"Q: How do I execute a custom shell script inside the chroot system after the "
-"chroot stage? A: Add your script in config/chroot_local-hooks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:149
-msgid ""
-"Q: How do I add a script running immediately after all other scripts when "
-"the live system boots? A: Add your script in config/chroot_local-includes/"
-"usr/share/initramfs-tools/scripts/live-bottom/99scrip"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:153
-msgid ""
-"$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/"
-"live-bottom/99script"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:157
-msgid ""
-"Note: The hook script must be executable. Do not forget to lh_clean --chroot "
-"after making this change before you build again."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:159
-msgid ""
-"You must also use the example script /usr/share/live-helper/examples/hooks/"
-"update-initramfs.sh to ensure your script gets built into the initramfs "
-"(read the comment header for instructions)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:163
-msgid ""
-"Q: How do I add software not in Debian ? A: See Customizing package "
-"installation % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:166
-msgid ""
-"Q: What is the manifest with Ubuntu used for? A: Manifest is just the "
-"package list, which ubuntu does $something with. Don't worry about it."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:169
-msgid ""
-"Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:172
-msgid ""
-"Q: Do I need to write the image on USB stick to test it? A: you must use "
-"qemu >= 0.8."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:175
-msgid "Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:178
-msgid ""
-"Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed "
-"something else entirely? A: It is not. It is a package list, not a debconf "
-"preseeding."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:181
-msgid ""
-"Q: What is the difference between standard and minimal? A: standard: "
-"packages of priority standard and higher; minimal: packages of priority "
-"essential and higher;"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:184
-msgid ""
-"Q: What can the sections be used for? Aren't they BIG? A: Someone maybe "
-"wants to include packages from contrib or non-free."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:187
-msgid "Q: memtest86+ ... is that used? A: Yes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:190
-msgid ""
-"Q: How do I build using predefined packages lists? A: e.g. to build using "
-"standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo "
-"lh_build}# Note: The packages lists can be found in /usr/share/live-helper/"
-"lists/ directory."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:193
-msgid ""
-"Q: How do I rebuild without downloading all the packages again? A: All "
-"packages are cached in cache subdirectory. They remain until a clean purge: #"
-"{$ sudo lh_clean --purge}# You do not have to do anything to prevent "
-"packages from being re-downloaded. You need to remember to clean whichever "
-"stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, "
-"chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:196
-msgid ""
-"Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make "
-"a boot CD with grub, configured to boot from a debian-live kernel copied on "
-"the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/"
-"stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/"
-"boot/grub/menu.lst:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:205
-msgid ""
-"default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd) "
-"kernel /boot/vmlinuz boot=live initrd /boot/initrd.img"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:209
-msgid ""
-"Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-"
-"boot \\ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:212
-msgid ""
-"Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A: "
-"If you have a floppy drive, you may be able to use it, otherwise you will "
-"need to use loadlin/grub4dos/win32-loader. If you have a second system to "
-"serve up the image over the network, See http://wiki.debian.org/DebianLive/"
-"Howto/Creating_a_Netboot_Image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:215
-msgid ""
-"Q: The X configuration does not seems to work, the resolution is too low. "
-"What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf "
-"&& lh_config --packages xdebconfigurator}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:218
-msgid ""
-"Q: Apache has problems with static files A: Sendfile does not work well on "
-"the unionfs used by Debian Live. Add the following to apache's "
-"configuration: #{EnableSendfile off}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:222
-msgid ""
-"Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right "
-"now the best is to use a script that will populate the fstab when the CD is "
-"booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/"
-"trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper "
-"solution based on HAL will be described here in a hopefully near future. A: "
-"Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-"
-"policy-fixed-drives.fdi is not available anymore and the previous trick that "
-"consisted to remove this file to enable automounting of fixed drives as a "
-"consequence is obsolete. Eventually, it will be possible to combine HAL and "
-"PolicyKit to enable different permissions and actions to achieve advanced "
-"(auto)mounting for non-root users. Until then, because the live scripts are "
-"only touching to the fstab to add a swap partition if discovered at boot "
-"time, the only way to have fixed drives mounted automatically is to use a "
-"script that will populate the fstab file at the end of the multiuser "
-"runlevel. To achieve this, you can do, for example, the following: download "
-"the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-"
-"includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin "
-"directory, and move the script inside Make sure the script is executable "
-"(chmod +x diskmounter.sh) create the chroot_local-includes/etc/rc.local file "
-"and call the diskmounter from there (see this https://devel.goto10.org/svn/"
-"puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called "
-"correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and "
-"NTFS partitions and mount them read-write, except for NTFS. This will change "
-"soon and an option will be available to use ntfs-3g to mount NTFS as read-"
-"write. comments, patches and other things about this script and issue: "
-"http://code.goto10.org/projects/puredyne/ticket/463"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:225
-msgid ""
-"Q: Boot fails with panic: can't open /scripts/live A: Add latest live-"
-"initramfs deb package into config/chroot_local-packages directory and "
-"rebuild."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:229
-msgid ""
-"Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref "
-"linkend=\"internalization\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:234
-msgid ""
-"Q: How do I get past boot prompt without a working keyboard? A: See "
-"Customizing the bootup process % FIXME: <xref linkend=\"bootup\"/> Note: "
-"Boot from an USB-HDD on an iMac with GRUB did not work."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:237
-msgid ""
-"Q: Can I serve the root image from a web or ftp server? A: Since live-"
-"initramfs 1.99, it should be possible to use the fetch= argument on the "
-"kernel command line. You can build a netboot image as usual, and when you "
-"are done edit the tftpboot/pxelinux.cfg/default file. Remove the references "
-"to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url "
-"where you placed the root image>. You have to include wget in the chroot. It "
-"could work for other boot methods as well. However, I am not sure the live "
-"scripts configure the network when booting from a CD or USB disk. #{$ "
-"lh_config --packages wget}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:240
-msgid ""
-"Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you "
-"are building an etch image (which was the default up to 2007/09/14) you have "
-"a very old version of casper which does not support quickreboot and possibly "
-"other boot parameters as well. You could configure your sources to use live-"
-"backports (see /usr/share/live-helper/examples/sources/live-backports) and "
-"switch to live-initramfs, or better yet, build a lenny image instead, which "
-"is the new default. #{$ lh_config --distribution lenny $ lh_config --"
-"initramfs live-initramfs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:243
-msgid ""
-"Q: How do I fix \"Could not find kernel image\" issue with syslinux "
-"bootloader? A: Add a binary local hook script to fix kernel and initrd path "
-"each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux."
-"sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:249
-msgid "SYSLINUXCFG=`find binary -type f -name syslinux.cfg`"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:252
-msgid ""
-"sed -i \"s|kernel /vmlinuz|kernel vmlinuz|g\" ${SYSLINUXCFG} sed -i \"s|"
-"initrd=/initrd|initrd=initrd|g\" ${SYSLINUXCFG}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:254
-msgid "$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:259
-msgid ""
-"Q: How do I use a newer kernel with lenny? A: A build with backports.org "
-"kernels will fail as that repository lacks the necessary module packages "
-"(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://"
-"unsupported.debian-maintainers.org/backports-kernel/ The quick way to "
-"success:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:268
-msgid ""
-"$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-"
-"modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-"
-"kernel/ ./' > config/chroot_sources/backports-kernel.chroot $ echo 'deb "
-"http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/"
-"chroot_sources/backports-kernel.binary $ wget http://unsupported.debian-"
-"maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/"
-"backports-kernel.chroot.gpg $ wget http://unsupported.debian-maintainers.org/"
-"backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel."
-"binary.gpg $ lh_build }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:271
-msgid ""
-"Q: How do I use a custom kernel? Is there a nice way of booting debian-live "
-"with a custom kernel (not in an apt repo)? A: Copy it into config/"
-"chroot_local-packages and set LH_LINUX_PACKAGES=\"none\" or use lh config --"
-"linux-packages \" \" Don't forget to compile your kernel with an union "
-"filesystem (unionfs or aufs), squashfs modules, and initrd support. I can "
-"cause the kernel to be installed but it seems this happens later than grub/"
-"syslinux is configured so it's not listed and casper/ and the menu require "
-"munging. You need to follow the debian scheme, e.g. placing the files in /"
-"boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't "
-"go that way which is too much of a hassle, and just use make-kpkg to produce "
-"custom kernel deb packages. They should integrate nicely if you just put "
-"them into config/chroot_local-packages and set LH_LINUX_PACKAGES=\"\". Hint: "
-"to work around an error, which lh_binary_syslinux will throw on custom "
-"kernels if there is not an 468/686 in the kernel-name, you need to set "
-"CONFIG_LOCALVERSION=\"-486\" or \"-686\" within the kernel configuration (-"
-"> General setup -> Local version set to -486 or -686) corresponding to "
-"LH_LINUX_FLAVOURS=\"\" or \"686\". this at least up till live-helper version "
-"1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-"
-"devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/"
-"debian-live-devel/2007-November/002581.html"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:274
-msgid ""
-"Q: How do I create a cross arch live CD image? A: In short: You can't. Read "
-"on: The procedure to create a live CD is based on creating a chroot that "
-"contains the files that will be finally available on the live CD. The live "
-"CD building procedure includes chrooting into the chroot dir and so some "
-"operations. chrooting means that the terminal you chroot on will behave as a "
-"different system so your real system and the chroot environment is decoupled "
-"somehow. Once the live CD scripts chroots into the chroot dir they have some "
-"operations to do inside that environment and your real system won't be able "
-"to run them unless you are using the same architecture. So you only are able "
-"to make live CD for the arch you run on. But this doesn't prevent you run "
-"qemu or some other machine emulator that make this possible."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:277
-msgid ""
-"Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That "
-"depends what you've changed between builds If, for example, you've built an "
-"iso image and you want a usb image, you only need to run #{lh_clean --binary}"
-"# before you run lh_build again. If you've changed anything in the chroot, "
-"you'll need to cleanup both chroot and binary with #{lh_clean}# before "
-"continuing"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:280
-msgid ""
-"Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in config/binary"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:283
-msgid ""
-"Q: How do I include different modules to load when the live system boots? A: "
-"Configure config/chroot_local-includes/etc/initramfs-tools/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:285
-msgid ""
-"The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default "
-"initramfs.conf \"MODULES = most\". You may override that by supplying your "
-"own initramfs.conf, or else just add your own modules, e.g."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:290
-msgid ""
-"mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo \"atl2\" >> "
-"config/chroot_local-includes/etc/initramfs-tools/modules"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:294
-msgid ""
-"Note: Even though initramfs.conf(5) says \"most adds all the framebuffer, "
-"acpi, file system, ide, sata, scsi and usb drivers\", it actually includes "
-"network drivers as well. See auto_add_modules() in /usr/share/initramfs-"
-"tools/hook-functions for the complete list."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:297
-msgid ""
-"Q: Can I have a splash screen? A: Yes you can. You will not know what is "
-"going on when the splash screen is active, it may fail to activate on some "
-"hardware or break X on other (both usplash and splashy use libdirectfb which "
-"does some evil voodoo and may break you graphics or input until you reboot). "
-"However, you can install and activate it just as you would on any other "
-"Debian system. To use splashy: 1. install splashy and read the README, the "
-"manpages are useless for setting it up. Add some parameters to your kernel "
-"command line, such as in your pxelinux configuration or in "
-"LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 "
-"splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, "
-"#{quiet}# to suppress most kernel messages that you cannot see anyway but "
-"would scroll past before splashy manages to paint the graphics on your "
-"screen. You might want to add splashy to the list of packages installed in "
-"your image: #{echo splashy > config/chroot_local-packageslists/splashy echo "
-"splashy-themes >> config/chroot_local-packageslists/splashy}# and select a "
-"theme:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:305
-msgid ""
-"echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s "
-"debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the "
-"ramdisk to include the splash screen echo update-initramfs -u -k all >> "
-"config/chroot_local-hooks/splashy chmod 755 config/chroot_local-hooks/splashy"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:309
-msgid ""
-"After you rebuild your live system you should observe a bluish splash screen "
-"while booting. Nothing happens while initramfs is running because there is "
-"no splashy support in initramfs-tools. Once the init starts the progress bar "
-"should start to fill. If #{vga=something}# sets a mode that your screen "
-"cannot show or your card cannot do vesa 2.0 (and thus you get plain text "
-"mode and no splashy) read the splashy faq."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:312
-msgid ""
-"Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the "
-"firmwares to the initrd image. You need to install the non-free package "
-"\"firmware-bnx2\". Uncompress your initrd image, then copy files:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:317
-msgid ""
-"cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /"
-"lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw "
-"${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:321
-msgid "Recompress your initrd image and boot: it works!"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:323
-msgid ""
-"Q: X is broken (the system boots, messages scroll by, and then the screen "
-"goes blank). What do I do? A: On my system starting X completely disables "
-"graphics so that I do not see anything even after X bails out and I am back "
-"to the console. To prevent this you can change the driver Xorg uses."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:325
-msgid ""
-"If you have a working splash screen or at least graphical console you can "
-"use #{live xdriver=fbdev}# when booting the live system (instead of just "
-"enter). Another driver you might want to try is #{vesa}#. If all fails you "
-"might try to set xdriver to some wrong value so that Xorg fails to start and "
-"you can examine the system while you still see something on the console. #"
-"{live xdriver=none}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:328
-msgid ""
-"Q: How can I get Debian first stable versions? A: I'm developing software "
-"and testing it on Live-CD. Thanks for the LiveCD project. To be sure my "
-"development is fully compatible with the \"etch\" version, I need the same "
-"scenario when Debian GNU/Linux 4.0 was published as stable (I believe "
-"2007.04.08). If there was some bug on 2007.04.08 that was corrected one week "
-"later, I need to test software foreseeing that scenario without the bug "
-"solved."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:331
-msgid ""
-"Q: I get \"fopen: Permission denied\"-warnings from apt on building/at the "
-"live-system A: That's a harmless bug in apt. However, if you want to get off "
-"this warnings in the live-system, add a file in chroot_local-hooks with "
-"follow row:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:335
-msgid "chown -R man.man /var/cache/man"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:340
-msgid ""
-"Q: Why I always fail during \"Retrieving Packages\" stage when running "
-"lh_build? I have already set apt-http-proxy and so on. A: lh_build "
-"retrieves packages via wget, as a result you need to enable the proxy "
-"settings in /etc/wgetrc before running lh_build."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:343
-msgid ""
-"Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system "
-"boots, so it's useless to put modifed Xorg.conf in config/choort_local-"
-"includes/etc/X11, because it will be overwritten during boot. However, you "
-"can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the "
-"result will be modified Xorg.conf. The modified dexconf has to be put in "
-"config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for "
-"two or more keyboards layouts with alt+shift toggle by editing dexconf and "
-"replacing the line:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:347
-msgid "Option \"XkbLayout\" \"$XKB_LAYOUT\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:351
-msgid "with the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:356
-msgid ""
-"Option \"XkbLayout\" \"us,il\" Option \"XkbOptions\" \"grp:alt_shift_toggle,"
-"grp_led:scroll\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:360
-msgid "when \"us,il\" are the wanted keyboard layouts."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:362
-msgid ""
-"You can force default screen resulotion (e.g. 1024*768) by adding the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:368
-#, no-wrap
-msgid ""
-"SubSection \"Display\"\n"
-" Modes \"1024x768\"\n"
-"EndSubSection\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:372
-msgid "between the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:379
-#, no-wrap
-msgid ""
-"Section \"Screen\"\n"
-" Identifier \"Default Screen\"\n"
-" Monitor \"Configured Monitor\"\n"
-"EndSection\"\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:383
-msgid ""
-"Q: Where are the build parameters for the prebuilt images A: See http://live."
-"debian.net/README.images."
-msgstr ""
diff --git a/manual/po/de/other_howtos.ssi.po b/manual/po/de/other_howtos.ssi.po
deleted file mode 100644
index e0facd5..0000000
--- a/manual/po/de/other_howtos.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# German translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: de\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr ""
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:2
-msgid "B~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:4
-msgid "1~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:6
-msgid "2~ ISO"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:8
-msgid ""
-"Generating a Debian Live CD is very simple. You need to have live-helper "
-"(package available in Debian sid and lenny), and Debootstrap (or "
-"cdebootstrap) from etch or newer."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:10
-msgid "3~ Install live-helper"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:12
-msgid "#{apt-get install live-helper}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:14
-msgid "3~ Configure the current working directory with lh_config"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:18
-msgid "lh_config -b iso -a $ARCH"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:22
-msgid "where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:24
-msgid "#{-b}# flag is used to be sure to obtain image in ISO format."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:26
-msgid "3~ Build the image with lh_build:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:28
-msgid "Execute lh_build as root: #{lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:30
-msgid ""
-"The command above will create the basic image, containing just the Debian "
-"standard system (with no X at all)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:32
-msgid ""
-"If you want to have any of the Desktop environments on your livecd, #{ls /"
-"usr/share/live-helper/lists}# will show a number of available package Lists "
-"to choose from, e.g. #{lh_config -p gnome-desktop}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:34
-msgid "More examples are listed at DebianLive/Examples."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:37
-msgid ""
-"See packages for help configuring a local Debian Mirror and other aspects of "
-"the live system. % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:39
-msgid "3~ Test the image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:41
-msgid "If you have qemu installed, you can boot the image with:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:45
-msgid "qemu -cdrom binary.iso"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:49
-msgid "If you have also kqemu installed, you can add #{-kernel-kqemu}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:51
-msgid "2~ ISO_(multiarch)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:53
-msgid ""
-"Multiple machine boot CDs can be created with the following manual "
-"procedure. This procedure has been successfully used to create a single CD "
-"which is bootable on alpha, i386, pmax, and sparc. It should be possible to "
-"also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:55
-msgid ""
-"To create a CD which is bootable by multiple architectures, use the "
-"following steps in this order. Please note that the order is critical."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:57
-msgid ""
-"Make sure you have all the required files including the various kernels and "
-"boot programs listed in the individual machine sections."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:59
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.pmax "
-"and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/"
-"mdec.pmax/bootxx_cd9660."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:61
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.vax and "
-"include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/"
-"xxboot.}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:63
-msgid "Include the macppc ofwboot.xcf bootloader in /cdsources."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:65
-msgid ""
-"Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/"
-"installation/floppy/boot-big.fs \\ -c boot.catalog -l -J -r -L /cdsources "
-"2>&1 | tee /tmp/mkisofs.log exit}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:67
-msgid ""
-"Note: The appearance of the -v flag twice is required. If you are making a "
-"bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -"
-"part in the parameters for mkisofs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:69
-msgid ""
-"Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 "
-"bootblocks. Alternatively, install the sysutils/mksunbootcd package on your "
-"favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs "
-"boot-sun4m.fs boot-sun3.fs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:71
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/pmax to install the pmax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"pmax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:73
-msgid ""
-"#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:75
-msgid ""
-"The -o append,sunsum option appends the first stage boot block to the end of "
-"the ISO file system, and restores the checksum used when booting on a sun."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:77
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/vax to install the vax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"vax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:79
-msgid "installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:81
-msgid "(See the pmax entry above for an explanation of the flags)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:83
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/alpha to install the "
-"alpha bootblocks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:85
-msgid ""
-"#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:86
-msgid ""
-"Note: The alpha installboot must occur after the others, because currently "
-"it's the only machine dependent back-end for installboot(8) that can "
-"calculate the alpha checksum. (See the pmax entry above for an explanation "
-"of the flags)."
-msgstr ""
diff --git a/manual/po/de/other_use-cases.ssi.po b/manual/po/de/other_use-cases.ssi.po
deleted file mode 100644
index e92a869..0000000
--- a/manual/po/de/other_use-cases.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# German translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: de\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr ""
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:2
-msgid "B~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:4
-msgid "1~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:6
-msgid "This chapter is for users to document their use cases with Debian Live."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:8
-msgid "2~ VNC Kiosk Client"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:10
-msgid "Create an image with live-helper to boot directly to a VNC server."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:12
-msgid "_* Make a build directory: #{$ mkdir vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:14
-msgid "_* Move to the build directory: #{$ cd vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:16
-msgid ""
-"Example to config the build directory to include gdm metacity "
-"xtightvncviewer: #{$ lh config --packages \"gdm metacity xtightvncviewer\"}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:18
-msgid ""
-"Create a folder /etc/skel folder for a custom .xsession for the default "
-"user: #{$ mkdir -p config/chroot_local-includes/etc/skel}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:20
-msgid ""
-"Create the .xsession for the default user: #{$ touch config/chroot_local-"
-"includes/etc/skel/.xsession}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:22
-msgid ""
-"Edit the .xsession file to launch metacity and start xvncviewer with "
-"something similar to the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:29
-msgid "/usr/bin/metacity & /usr/bin/vncviewer xxx.xxx.xxx.xxx:PORT"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:31
-msgid "exit"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:35
-msgid "_* Build the image: #{# lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:37 en/other_use-cases.ssi:138
-msgid "_* Enjoy."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:39
-msgid "2~ VMWare-Player Sessions"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:41
-msgid ""
-"Create an image with live-helper to boot directly to a specifiv VMWare "
-"session."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:43
-msgid "_* Make a build directory: #{$ mkdir VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:45
-msgid "_* Move to the build directory: #{$ cd VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:47
-msgid ""
-"_* Example to config the build directory to include gdm metacity "
-"xtightvncviewer:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:67
-#, no-wrap
-msgid ""
-"$ lh config --apt apt \\\n"
-" ---apt-recommends disabled \\\n"
-" --archive-areas \"main\" \\\n"
-" --binary-images iso \\\n"
-" --binary-indices none \\\n"
-" --syslinux-menu vesamenu \\\n"
-" ---bootappend-live \"persistent quickreboot\" \\\n"
-" ---bootappend-install \"-- plainroot persistent video=vesa:ywrap,mtrr vga=788 quickreboot quiet live-config\" \\\n"
-" ---debian-installer live \\\n"
-" ---distribution lenny \\\n"
-" ---hostname vmare-player-firmware \\\n"
-" ---includes none \\\n"
-" ---linux-flavours 686 \\\n"
-" ---packages-lists \"gnome-core\" \\\n"
-" ---packages \"gcc gparted linux-headers-2.6-\\${LH_LINUX_FLAVOURS} live-config-staging make metacity rsync wireless-tools\" \\\n"
-" ---repositories live.debian.net \\\n"
-" ---win32-loader disabled\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:71
-msgid ""
-"_* Create the 01-vmware-player hook: #{$ touch config/chroot_local-hooks/01-"
-"vmware-player.sh}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:73
-msgid ""
-"Edit the 01-vmware-player hook to launch the VMWare-Player. The hook should "
-"look something like the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:80
-msgid ""
-"_URL=\"http://archive.debian-maintainers.org/vmware/other/vmware-player/\" "
-"_VMPLAYER_VERSION=\"VMware-Player.i386.bundle\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:83
-msgid "echo \"I: Starting script for install of VMWare Player.\" cd /root"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:86
-msgid ""
-"echo \"I: Beginning download of ${_VMPLAYER_VERSION} from ${_URL} .\" wget "
-"${_URL}${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:89
-msgid ""
-"echo \"I: Starting install of VMWare Player.\" sh /root/${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:92
-msgid ""
-"echo \"I: Cleaning up the VMWare Player download.\" rm /root/"
-"${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:95
-msgid "#echo \"I: Starting interactive shell.\" #bash"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:99
-msgid ""
-"_* Build the image (note that during the build the VMWare-Player will prompt "
-"you to install or cancel): #{#lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:101
-msgid ""
-"_* After the build you will have an image you can boot live or install as "
-"firmware. The package live-config-staging is the package that installs the "
-"ability to utilize the VMWare-Player by calling live-config.vmware-player as "
-"a boot parameter in the following form:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:105
-msgid "live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:109
-msgid "Notes from the 900-vmware-player file are as follows:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:135
-#, no-wrap
-msgid ""
-"# The script tests for boot parameter of\n"
-"# live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME\n"
-"#\n"
-"# ACTION: The operation to perform on the workstation (none|scratch)\n"
-"# IMAGEPATH: The folder path to the VMware image you want to run.\n"
-"# VMXNAME: The name of the VMware image you want to run.\n"
-"#\n"
-"# Notes:To use this file with WMWare images you will need to have a few things\n"
-"# setup:\n"
-"#\n"
-"# 1. The VMware Player needs to be installed in the image.\n"
-"# 2. This script uses (s|h)da1 for writing image data, and is used as a scratch\n"
-"# space. This scratch space should be a file system with linux permissions\n"
-"# such as ext2.\n"
-"# 3. VMware image(s) should be in a mounted folder and setup as follows:\n"
-"# - Image(s) set to snapshot mode.\n"
-"# - For each image, the image folder needs to have a file called\n"
-"# image-release with a variable CRELEASE. An example: CRELEASE=\"1.0.0\"\n"
-"#\n"
-"# The image-release file is used by the image maintainer and this script to tell\n"
-"# workstation(s) using a given image, to erase locally stored vmware image files\n"
-"# and setup with the newly configure image. The operation of erasing locally\n"
-"# stored vmare image files, is referred to as a scratch.\n"
-msgstr ""
diff --git a/manual/po/de/user_examples.ssi.po b/manual/po/de/user_examples.ssi.po
index 7425e97..eb249e4 100644
--- a/manual/po/de/user_examples.ssi.po
+++ b/manual/po/de/user_examples.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:57-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-11-04 16:34-0400\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,13 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/other_faq.ssi:41 en/other_faq.ssi:83
-#: en/other_faq.ssi:103 en/other_faq.ssi:117 en/other_faq.ssi:137
-#: en/other_faq.ssi:151 en/other_faq.ssi:198 en/other_faq.ssi:245
-#: en/other_faq.ssi:261 en/other_faq.ssi:287 en/other_faq.ssi:299
-#: en/other_faq.ssi:314 en/other_faq.ssi:333 en/other_faq.ssi:345
-#: en/other_faq.ssi:353 en/other_faq.ssi:364 en/other_faq.ssi:374
-#: en/other_howtos.ssi:16 en/other_howtos.ssi:43 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:58
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -87,13 +81,7 @@ msgstr ""
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/other_faq.ssi:37 en/other_faq.ssi:46
-#: en/other_faq.ssi:92 en/other_faq.ssi:108 en/other_faq.ssi:141
-#: en/other_faq.ssi:155 en/other_faq.ssi:207 en/other_faq.ssi:256
-#: en/other_faq.ssi:292 en/other_faq.ssi:307 en/other_faq.ssi:319
-#: en/other_faq.ssi:337 en/other_faq.ssi:349 en/other_faq.ssi:358
-#: en/other_faq.ssi:370 en/other_faq.ssi:381 en/other_howtos.ssi:20
-#: en/other_howtos.ssi:47 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:62
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -150,12 +138,6 @@ msgid "}code"
msgstr ""
#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/user_examples.ssi:92
-#: en/user_examples.ssi:141 en/user_examples.ssi:190
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
#: en/user_basics.ssi:44 en/user_basics.ssi:120 en/user_basics.ssi:204
#: en/user_examples.ssi:109 en/user_examples.ssi:156
msgid "# lb build"
@@ -360,6 +342,11 @@ msgid "Edit #{auto/config}# to read as follows:"
msgstr ""
#. type: Plain text
+#: en/user_examples.ssi:92 en/user_examples.ssi:141 en/user_examples.ssi:190
+msgid "#!/bin/sh"
+msgstr ""
+
+#. type: Plain text
#: en/user_examples.ssi:99
#, no-wrap
msgid ""
diff --git a/manual/po/fr/live-manual.ssm.po b/manual/po/fr/live-manual.ssm.po
index 2bc6311..47db95f 100644
--- a/manual/po/fr/live-manual.ssm.po
+++ b/manual/po/fr/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:18-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-10-21 07:06-0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -173,13 +173,3 @@ msgstr ""
#: en/live-manual.ssm:65
msgid "<< user_examples.ssi"
msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:67
-msgid "% << other_faq.ssi"
-msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:68
-msgid "% << other_howtos.ssi"
-msgstr ""
diff --git a/manual/po/fr/other_faq.ssi.po b/manual/po/fr/other_faq.ssi.po
deleted file mode 100644
index 098869d..0000000
--- a/manual/po/fr/other_faq.ssi.po
+++ /dev/null
@@ -1,1008 +0,0 @@
-# French translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-16 14:45-0200\n"
-"PO-Revision-Date: 2010-10-16 14:45-0200\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: fr\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n > 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:83 en/about_manual.ssi:91 en/about_manual.ssi:99
-#: en/about_manual.ssi:111 en/about_manual.ssi:124 en/about_manual.ssi:137
-#: en/about_manual.ssi:145 en/about_manual.ssi:153 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_faq.ssi:41 en/other_faq.ssi:83 en/other_faq.ssi:103
-#: en/other_faq.ssi:117 en/other_faq.ssi:137 en/other_faq.ssi:151
-#: en/other_faq.ssi:198 en/other_faq.ssi:245 en/other_faq.ssi:261
-#: en/other_faq.ssi:287 en/other_faq.ssi:299 en/other_faq.ssi:314
-#: en/other_faq.ssi:333 en/other_faq.ssi:345 en/other_faq.ssi:353
-#: en/other_faq.ssi:364 en/other_faq.ssi:374 en/other_howtos.ssi:16
-#: en/other_howtos.ssi:43 en/other_live-environment.ssi:14
-#: en/other_live-environment.ssi:30 en/other_live-environment.ssi:51
-#: en/other_live-environment.ssi:61 en/other_live-environment.ssi:69
-#: en/other_live-environment.ssi:77 en/other_live-environment.ssi:85
-#: en/other_live-environment.ssi:93 en/other_live-environment.ssi:116
-#: en/other_live-environment.ssi:124 en/other_live-environment.ssi:133
-#: en/other_procedures.ssi:12 en/other_procedures.ssi:46
-#: en/other_procedures.ssi:58 en/other_use-cases.ssi:24
-#: en/other_use-cases.ssi:49 en/other_use-cases.ssi:75
-#: en/other_use-cases.ssi:103 en/other_use-cases.ssi:111 en/user_basics.ssi:36
-#: en/user_basics.ssi:48 en/user_basics.ssi:62 en/user_basics.ssi:74
-#: en/user_basics.ssi:86 en/user_basics.ssi:98 en/user_basics.ssi:114
-#: en/user_basics.ssi:122 en/user_basics.ssi:130 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:180 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:212 en/user_basics.ssi:232 en/user_basics.ssi:265
-#: en/user_basics.ssi:281 en/user_basics.ssi:289 en/user_basics.ssi:309
-#: en/user_basics.ssi:334 en/user_customization-contents.ssi:34
-#: en/user_customization-contents.ssi:43 en/user_customization-contents.ssi:66
-#: en/user_customization-internationalization.ssi:10
-#: en/user_customization-internationalization.ssi:18
-#: en/user_customization-internationalization.ssi:26
-#: en/user_customization-internationalization.ssi:38
-#: en/user_customization-packages.ssi:16 en/user_customization-packages.ssi:24
-#: en/user_customization-packages.ssi:36 en/user_customization-packages.ssi:45
-#: en/user_customization-packages.ssi:59 en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:106
-#: en/user_installation.ssi:120 en/user_installation.ssi:137
-#: en/user_managing_a_configuration.ssi:24
-#: en/user_managing_a_configuration.ssi:35
-#: en/user_managing_a_configuration.ssi:47 en/user_overview.ssi:60
-#: en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:87 en/about_manual.ssi:95 en/about_manual.ssi:103
-#: en/about_manual.ssi:120 en/about_manual.ssi:133 en/about_manual.ssi:141
-#: en/about_manual.ssi:149 en/about_manual.ssi:157 en/about_manual.ssi:164
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_faq.ssi:37 en/other_faq.ssi:46 en/other_faq.ssi:92
-#: en/other_faq.ssi:108 en/other_faq.ssi:141 en/other_faq.ssi:155
-#: en/other_faq.ssi:207 en/other_faq.ssi:256 en/other_faq.ssi:292
-#: en/other_faq.ssi:307 en/other_faq.ssi:319 en/other_faq.ssi:337
-#: en/other_faq.ssi:349 en/other_faq.ssi:358 en/other_faq.ssi:370
-#: en/other_faq.ssi:381 en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:92
-#: en/user_basics.ssi:104 en/user_basics.ssi:118 en/user_basics.ssi:126
-#: en/user_basics.ssi:134 en/user_basics.ssi:144 en/user_basics.ssi:158
-#: en/user_basics.ssi:168 en/user_basics.ssi:176 en/user_basics.ssi:184
-#: en/user_basics.ssi:198 en/user_basics.ssi:206 en/user_basics.ssi:216
-#: en/user_basics.ssi:257 en/user_basics.ssi:285 en/user_basics.ssi:293
-#: en/user_basics.ssi:320 en/user_basics.ssi:359
-#: en/user_customization-contents.ssi:39 en/user_customization-contents.ssi:54
-#: en/user_customization-contents.ssi:70
-#: en/user_customization-internationalization.ssi:14
-#: en/user_customization-internationalization.ssi:22
-#: en/user_customization-internationalization.ssi:30
-#: en/user_customization-internationalization.ssi:42
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:172
-#: en/user_customization-packages.ssi:182
-#: en/user_customization-packages.ssi:192
-#: en/user_customization-packages.ssi:202 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:88 en/user_installation.ssi:110
-#: en/user_installation.ssi:125 en/user_installation.ssi:140
-#: en/user_managing_a_configuration.ssi:31
-#: en/user_managing_a_configuration.ssi:43
-#: en/user_managing_a_configuration.ssi:52 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:2
-msgid "B~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:4
-msgid "1~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:8
-msgid ""
-"Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A: "
-"See \"Copying USB/HDD image to a USB stick\" % FIXME: <xref linkend="
-"\"image_copying\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:11
-msgid ""
-"Q: How do I log my build? A: You could use script, screen or tee: #{$ "
-"lh_build 2>&1 | tee build.log}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:14
-msgid ""
-"Q: How can I convert an already installed standard Debian partition into a "
-"Debian Live system? A: Save the list of installed packages and load it into "
-"your new Debian Live System. Copy your /etc to config/chroot_local-includes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:17
-msgid ""
-"Q: What does 'losetup: could not find any free loop device' mean and how do "
-"I fix it? A: Loop devices are used during the build; there probably aren't "
-"any free if you've aborted several builds. Something like: for l in /dev/"
-"loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/"
-"loop7 ; do losetup -d $l ; done should rectify the situation (assuming all "
-"loop devices in use were created by lh_build; if in doubt, check the "
-"contents of each loop device before deleting them with losetup -d)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:20
-msgid ""
-"Q: How do I launch an interactive shell during the chroot stage? A: To "
-"enable interactive shell: #{$ lh_config --interactive shell}# To continue "
-"the build process: #{# logout}# or #{# exit}# To disable interactive shell, "
-"set LH_INTERACTIVE to \"disabled\" in config/chroot."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:23
-msgid ""
-"Q: What is the root /user password? A: The user password for the live user "
-"is 'live'. By default, there is not any root password. You can switch to "
-"root with ${sudo -i}# or set a password for root with #{sudo passwd}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:27
-msgid ""
-"Q: How do I change root or any user password? A: Add a chroot local hook "
-"script to change root or any user password each time you build an image. e."
-"g. config/chroot_local-hooks/01-update_password.sh to set root password to "
-"\"nopasswd\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:30 en/other_faq.ssi:53
-msgid "code{ #!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:33
-msgid "echo \"I: update password\" echo \"root:nopasswd\" | chpasswd"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:35
-msgid "$ chmod +x config/chroot_local-hooks/01-update_password.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:39
-msgid ""
-"Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/"
-"live-bottom/10adduser your build folder:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:44
-msgid ""
-"mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-"
-"bottom/ cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/"
-"chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:48
-msgid ""
-"Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/"
-"scripts/live-bottom/10adduser and paste in the new user_crypted password "
-"that you make with: #{echo \"newlivepass\" | mkpasswd -s}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:50
-msgid ""
-"Or add an hook file in config/chroot_local-hooks/ with something like the "
-"below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:57
-msgid ""
-"# Change the autogenerated user password to \"debianlive\" plain_password="
-"\"debianlive\" password=$(echo \"${plain_password}\" | mkpasswd -s)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:59
-msgid ""
-"sed -i -e 's/\\(user_crypted=\\)\\(.*\\)\\( #.*\\)/\\1\\\"'${password}'\\"
-"\"\\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:62
-msgid "update-initramfs -tu -kall }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:64
-msgid ""
-"The latter (hook model) could be more future proof than the former solution "
-"since it modifies just one string selectively but it requires the package "
-"\"whois\" to be installed on the target system (for mkpasswd) or that you "
-"generate the $password string not at build time and include it crypted in "
-"the above script."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:68
-msgid ""
-"Q: How to disable autologin? A1: use the commandline parameter #{lh config --"
-"bootappend-live \"noautologin\"}# A2: You need to set boot=noautologin "
-"noxautologin as described in man live-initramfs If you boot via TFTP you "
-"want to insert the option to pxelinux.cfg/default"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:71
-msgid ""
-"Q: How do I change default hostname or username? A: To change default "
-"hostname or username: #{$ lh_config --hostname myhostname $ lh_config --"
-"username myusername}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:74
-msgid ""
-"Q: How do I make the final image smaller? A: Clean orphaned apps/libs: "
-"Install package \"deborphan\" and then run 'sudo deborphan -n' . Delete "
-"unwanted packages. Remove the apt cache. Purge unwanted locales (see "
-"\"localepurge\" package)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:77
-msgid ""
-"Q: How do I customize bash-config permanently (aliases, bash-completion "
-"etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:81
-msgid ""
-"Q: How do I disable services permanently? (Be careful!) A: Add a chroot "
-"local hook script to disable a service each time you build an image: e.g. "
-"config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:88
-msgid "echo \"I: disable service\" update-rc.d -f service_name remove"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:90
-msgid "$ chmod +x config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:95
-msgid ""
-"Q: How do I enable | disable the md5checksum at the ISO building? A: #"
-"{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:98
-msgid ""
-"Q: How to disable the generation of the .tar.gz file? A: #{lh_config --net-"
-"tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in "
-"snapsshot version at the moment 2008/Feb/28)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:101
-msgid "Q: How do I \"build a new image\"? A: Run commands:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:106
-msgid "$ sudo lh_clean --binary $ sudo lh_build"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:110
-msgid ""
-"Hint: If the configuration had changed you should leave \"--binary\" out. "
-"This will clean your chroot directory too."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:113
-msgid ""
-"Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages "
-"you want."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:115
-msgid "Create /home/$USERNAME/.dmrc file (default username is \"user\")."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:122
-msgid "$ cat .dmrc [Desktop] Session=fluxbox }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:124
-msgid "Note: .dmrc is owned by $USERNAME:$USERNAME."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:126
-msgid ""
-"See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at "
-"http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:129
-msgid ""
-"Q: How do I use custom repositories? A: See http://wiki.debian.org/"
-"DebianLive/Configuration"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:132
-msgid ""
-"Q: How do I customize the artwork for the live CD (grub or syslinux boot "
-"splash, usplash, etc.)? A: See http://wiki.debian.org/DebianLive/Howto/"
-"Custom_Artwork"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:135
-msgid ""
-"Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look? "
-"A: Start the live system in qemu:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:139
-msgid "$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:143
-msgid "Note: the -redir argument must be changed to meet your needs"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:146
-msgid ""
-"Q: How do I execute a custom shell script inside the chroot system after the "
-"chroot stage? A: Add your script in config/chroot_local-hooks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:149
-msgid ""
-"Q: How do I add a script running immediately after all other scripts when "
-"the live system boots? A: Add your script in config/chroot_local-includes/"
-"usr/share/initramfs-tools/scripts/live-bottom/99scrip"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:153
-msgid ""
-"$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/"
-"live-bottom/99script"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:157
-msgid ""
-"Note: The hook script must be executable. Do not forget to lh_clean --chroot "
-"after making this change before you build again."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:159
-msgid ""
-"You must also use the example script /usr/share/live-helper/examples/hooks/"
-"update-initramfs.sh to ensure your script gets built into the initramfs "
-"(read the comment header for instructions)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:163
-msgid ""
-"Q: How do I add software not in Debian ? A: See Customizing package "
-"installation % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:166
-msgid ""
-"Q: What is the manifest with Ubuntu used for? A: Manifest is just the "
-"package list, which ubuntu does $something with. Don't worry about it."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:169
-msgid ""
-"Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:172
-msgid ""
-"Q: Do I need to write the image on USB stick to test it? A: you must use "
-"qemu >= 0.8."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:175
-msgid "Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:178
-msgid ""
-"Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed "
-"something else entirely? A: It is not. It is a package list, not a debconf "
-"preseeding."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:181
-msgid ""
-"Q: What is the difference between standard and minimal? A: standard: "
-"packages of priority standard and higher; minimal: packages of priority "
-"essential and higher;"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:184
-msgid ""
-"Q: What can the sections be used for? Aren't they BIG? A: Someone maybe "
-"wants to include packages from contrib or non-free."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:187
-msgid "Q: memtest86+ ... is that used? A: Yes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:190
-msgid ""
-"Q: How do I build using predefined packages lists? A: e.g. to build using "
-"standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo "
-"lh_build}# Note: The packages lists can be found in /usr/share/live-helper/"
-"lists/ directory."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:193
-msgid ""
-"Q: How do I rebuild without downloading all the packages again? A: All "
-"packages are cached in cache subdirectory. They remain until a clean purge: #"
-"{$ sudo lh_clean --purge}# You do not have to do anything to prevent "
-"packages from being re-downloaded. You need to remember to clean whichever "
-"stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, "
-"chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:196
-msgid ""
-"Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make "
-"a boot CD with grub, configured to boot from a debian-live kernel copied on "
-"the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/"
-"stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/"
-"boot/grub/menu.lst:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:205
-msgid ""
-"default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd) "
-"kernel /boot/vmlinuz boot=live initrd /boot/initrd.img"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:209
-msgid ""
-"Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-"
-"boot \\ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:212
-msgid ""
-"Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A: "
-"If you have a floppy drive, you may be able to use it, otherwise you will "
-"need to use loadlin/grub4dos/win32-loader. If you have a second system to "
-"serve up the image over the network, See http://wiki.debian.org/DebianLive/"
-"Howto/Creating_a_Netboot_Image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:215
-msgid ""
-"Q: The X configuration does not seems to work, the resolution is too low. "
-"What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf "
-"&& lh_config --packages xdebconfigurator}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:218
-msgid ""
-"Q: Apache has problems with static files A: Sendfile does not work well on "
-"the unionfs used by Debian Live. Add the following to apache's "
-"configuration: #{EnableSendfile off}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:222
-msgid ""
-"Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right "
-"now the best is to use a script that will populate the fstab when the CD is "
-"booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/"
-"trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper "
-"solution based on HAL will be described here in a hopefully near future. A: "
-"Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-"
-"policy-fixed-drives.fdi is not available anymore and the previous trick that "
-"consisted to remove this file to enable automounting of fixed drives as a "
-"consequence is obsolete. Eventually, it will be possible to combine HAL and "
-"PolicyKit to enable different permissions and actions to achieve advanced "
-"(auto)mounting for non-root users. Until then, because the live scripts are "
-"only touching to the fstab to add a swap partition if discovered at boot "
-"time, the only way to have fixed drives mounted automatically is to use a "
-"script that will populate the fstab file at the end of the multiuser "
-"runlevel. To achieve this, you can do, for example, the following: download "
-"the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-"
-"includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin "
-"directory, and move the script inside Make sure the script is executable "
-"(chmod +x diskmounter.sh) create the chroot_local-includes/etc/rc.local file "
-"and call the diskmounter from there (see this https://devel.goto10.org/svn/"
-"puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called "
-"correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and "
-"NTFS partitions and mount them read-write, except for NTFS. This will change "
-"soon and an option will be available to use ntfs-3g to mount NTFS as read-"
-"write. comments, patches and other things about this script and issue: "
-"http://code.goto10.org/projects/puredyne/ticket/463"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:225
-msgid ""
-"Q: Boot fails with panic: can't open /scripts/live A: Add latest live-"
-"initramfs deb package into config/chroot_local-packages directory and "
-"rebuild."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:229
-msgid ""
-"Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref "
-"linkend=\"internalization\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:234
-msgid ""
-"Q: How do I get past boot prompt without a working keyboard? A: See "
-"Customizing the bootup process % FIXME: <xref linkend=\"bootup\"/> Note: "
-"Boot from an USB-HDD on an iMac with GRUB did not work."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:237
-msgid ""
-"Q: Can I serve the root image from a web or ftp server? A: Since live-"
-"initramfs 1.99, it should be possible to use the fetch= argument on the "
-"kernel command line. You can build a netboot image as usual, and when you "
-"are done edit the tftpboot/pxelinux.cfg/default file. Remove the references "
-"to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url "
-"where you placed the root image>. You have to include wget in the chroot. It "
-"could work for other boot methods as well. However, I am not sure the live "
-"scripts configure the network when booting from a CD or USB disk. #{$ "
-"lh_config --packages wget}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:240
-msgid ""
-"Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you "
-"are building an etch image (which was the default up to 2007/09/14) you have "
-"a very old version of casper which does not support quickreboot and possibly "
-"other boot parameters as well. You could configure your sources to use live-"
-"backports (see /usr/share/live-helper/examples/sources/live-backports) and "
-"switch to live-initramfs, or better yet, build a lenny image instead, which "
-"is the new default. #{$ lh_config --distribution lenny $ lh_config --"
-"initramfs live-initramfs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:243
-msgid ""
-"Q: How do I fix \"Could not find kernel image\" issue with syslinux "
-"bootloader? A: Add a binary local hook script to fix kernel and initrd path "
-"each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux."
-"sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:249
-msgid "SYSLINUXCFG=`find binary -type f -name syslinux.cfg`"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:252
-msgid ""
-"sed -i \"s|kernel /vmlinuz|kernel vmlinuz|g\" ${SYSLINUXCFG} sed -i \"s|"
-"initrd=/initrd|initrd=initrd|g\" ${SYSLINUXCFG}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:254
-msgid "$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:259
-msgid ""
-"Q: How do I use a newer kernel with lenny? A: A build with backports.org "
-"kernels will fail as that repository lacks the necessary module packages "
-"(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://"
-"unsupported.debian-maintainers.org/backports-kernel/ The quick way to "
-"success:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:268
-msgid ""
-"$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-"
-"modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-"
-"kernel/ ./' > config/chroot_sources/backports-kernel.chroot $ echo 'deb "
-"http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/"
-"chroot_sources/backports-kernel.binary $ wget http://unsupported.debian-"
-"maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/"
-"backports-kernel.chroot.gpg $ wget http://unsupported.debian-maintainers.org/"
-"backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel."
-"binary.gpg $ lh_build }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:271
-msgid ""
-"Q: How do I use a custom kernel? Is there a nice way of booting debian-live "
-"with a custom kernel (not in an apt repo)? A: Copy it into config/"
-"chroot_local-packages and set LH_LINUX_PACKAGES=\"none\" or use lh config --"
-"linux-packages \" \" Don't forget to compile your kernel with an union "
-"filesystem (unionfs or aufs), squashfs modules, and initrd support. I can "
-"cause the kernel to be installed but it seems this happens later than grub/"
-"syslinux is configured so it's not listed and casper/ and the menu require "
-"munging. You need to follow the debian scheme, e.g. placing the files in /"
-"boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't "
-"go that way which is too much of a hassle, and just use make-kpkg to produce "
-"custom kernel deb packages. They should integrate nicely if you just put "
-"them into config/chroot_local-packages and set LH_LINUX_PACKAGES=\"\". Hint: "
-"to work around an error, which lh_binary_syslinux will throw on custom "
-"kernels if there is not an 468/686 in the kernel-name, you need to set "
-"CONFIG_LOCALVERSION=\"-486\" or \"-686\" within the kernel configuration (-"
-"> General setup -> Local version set to -486 or -686) corresponding to "
-"LH_LINUX_FLAVOURS=\"\" or \"686\". this at least up till live-helper version "
-"1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-"
-"devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/"
-"debian-live-devel/2007-November/002581.html"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:274
-msgid ""
-"Q: How do I create a cross arch live CD image? A: In short: You can't. Read "
-"on: The procedure to create a live CD is based on creating a chroot that "
-"contains the files that will be finally available on the live CD. The live "
-"CD building procedure includes chrooting into the chroot dir and so some "
-"operations. chrooting means that the terminal you chroot on will behave as a "
-"different system so your real system and the chroot environment is decoupled "
-"somehow. Once the live CD scripts chroots into the chroot dir they have some "
-"operations to do inside that environment and your real system won't be able "
-"to run them unless you are using the same architecture. So you only are able "
-"to make live CD for the arch you run on. But this doesn't prevent you run "
-"qemu or some other machine emulator that make this possible."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:277
-msgid ""
-"Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That "
-"depends what you've changed between builds If, for example, you've built an "
-"iso image and you want a usb image, you only need to run #{lh_clean --binary}"
-"# before you run lh_build again. If you've changed anything in the chroot, "
-"you'll need to cleanup both chroot and binary with #{lh_clean}# before "
-"continuing"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:280
-msgid ""
-"Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in config/binary"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:283
-msgid ""
-"Q: How do I include different modules to load when the live system boots? A: "
-"Configure config/chroot_local-includes/etc/initramfs-tools/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:285
-msgid ""
-"The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default "
-"initramfs.conf \"MODULES = most\". You may override that by supplying your "
-"own initramfs.conf, or else just add your own modules, e.g."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:290
-msgid ""
-"mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo \"atl2\" >> "
-"config/chroot_local-includes/etc/initramfs-tools/modules"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:294
-msgid ""
-"Note: Even though initramfs.conf(5) says \"most adds all the framebuffer, "
-"acpi, file system, ide, sata, scsi and usb drivers\", it actually includes "
-"network drivers as well. See auto_add_modules() in /usr/share/initramfs-"
-"tools/hook-functions for the complete list."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:297
-msgid ""
-"Q: Can I have a splash screen? A: Yes you can. You will not know what is "
-"going on when the splash screen is active, it may fail to activate on some "
-"hardware or break X on other (both usplash and splashy use libdirectfb which "
-"does some evil voodoo and may break you graphics or input until you reboot). "
-"However, you can install and activate it just as you would on any other "
-"Debian system. To use splashy: 1. install splashy and read the README, the "
-"manpages are useless for setting it up. Add some parameters to your kernel "
-"command line, such as in your pxelinux configuration or in "
-"LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 "
-"splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, "
-"#{quiet}# to suppress most kernel messages that you cannot see anyway but "
-"would scroll past before splashy manages to paint the graphics on your "
-"screen. You might want to add splashy to the list of packages installed in "
-"your image: #{echo splashy > config/chroot_local-packageslists/splashy echo "
-"splashy-themes >> config/chroot_local-packageslists/splashy}# and select a "
-"theme:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:305
-msgid ""
-"echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s "
-"debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the "
-"ramdisk to include the splash screen echo update-initramfs -u -k all >> "
-"config/chroot_local-hooks/splashy chmod 755 config/chroot_local-hooks/splashy"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:309
-msgid ""
-"After you rebuild your live system you should observe a bluish splash screen "
-"while booting. Nothing happens while initramfs is running because there is "
-"no splashy support in initramfs-tools. Once the init starts the progress bar "
-"should start to fill. If #{vga=something}# sets a mode that your screen "
-"cannot show or your card cannot do vesa 2.0 (and thus you get plain text "
-"mode and no splashy) read the splashy faq."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:312
-msgid ""
-"Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the "
-"firmwares to the initrd image. You need to install the non-free package "
-"\"firmware-bnx2\". Uncompress your initrd image, then copy files:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:317
-msgid ""
-"cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /"
-"lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw "
-"${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:321
-msgid "Recompress your initrd image and boot: it works!"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:323
-msgid ""
-"Q: X is broken (the system boots, messages scroll by, and then the screen "
-"goes blank). What do I do? A: On my system starting X completely disables "
-"graphics so that I do not see anything even after X bails out and I am back "
-"to the console. To prevent this you can change the driver Xorg uses."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:325
-msgid ""
-"If you have a working splash screen or at least graphical console you can "
-"use #{live xdriver=fbdev}# when booting the live system (instead of just "
-"enter). Another driver you might want to try is #{vesa}#. If all fails you "
-"might try to set xdriver to some wrong value so that Xorg fails to start and "
-"you can examine the system while you still see something on the console. #"
-"{live xdriver=none}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:328
-msgid ""
-"Q: How can I get Debian first stable versions? A: I'm developing software "
-"and testing it on Live-CD. Thanks for the LiveCD project. To be sure my "
-"development is fully compatible with the \"etch\" version, I need the same "
-"scenario when Debian GNU/Linux 4.0 was published as stable (I believe "
-"2007.04.08). If there was some bug on 2007.04.08 that was corrected one week "
-"later, I need to test software foreseeing that scenario without the bug "
-"solved."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:331
-msgid ""
-"Q: I get \"fopen: Permission denied\"-warnings from apt on building/at the "
-"live-system A: That's a harmless bug in apt. However, if you want to get off "
-"this warnings in the live-system, add a file in chroot_local-hooks with "
-"follow row:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:335
-msgid "chown -R man.man /var/cache/man"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:340
-msgid ""
-"Q: Why I always fail during \"Retrieving Packages\" stage when running "
-"lh_build? I have already set apt-http-proxy and so on. A: lh_build "
-"retrieves packages via wget, as a result you need to enable the proxy "
-"settings in /etc/wgetrc before running lh_build."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:343
-msgid ""
-"Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system "
-"boots, so it's useless to put modifed Xorg.conf in config/choort_local-"
-"includes/etc/X11, because it will be overwritten during boot. However, you "
-"can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the "
-"result will be modified Xorg.conf. The modified dexconf has to be put in "
-"config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for "
-"two or more keyboards layouts with alt+shift toggle by editing dexconf and "
-"replacing the line:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:347
-msgid "Option \"XkbLayout\" \"$XKB_LAYOUT\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:351
-msgid "with the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:356
-msgid ""
-"Option \"XkbLayout\" \"us,il\" Option \"XkbOptions\" \"grp:alt_shift_toggle,"
-"grp_led:scroll\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:360
-msgid "when \"us,il\" are the wanted keyboard layouts."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:362
-msgid ""
-"You can force default screen resulotion (e.g. 1024*768) by adding the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:368
-#, no-wrap
-msgid ""
-"SubSection \"Display\"\n"
-" Modes \"1024x768\"\n"
-"EndSubSection\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:372
-msgid "between the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:379
-#, no-wrap
-msgid ""
-"Section \"Screen\"\n"
-" Identifier \"Default Screen\"\n"
-" Monitor \"Configured Monitor\"\n"
-"EndSection\"\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:383
-msgid ""
-"Q: Where are the build parameters for the prebuilt images A: See http://live."
-"debian.net/README.images."
-msgstr ""
diff --git a/manual/po/fr/other_howtos.ssi.po b/manual/po/fr/other_howtos.ssi.po
deleted file mode 100644
index 55bb9ab..0000000
--- a/manual/po/fr/other_howtos.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# French translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: fr\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n > 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_howtos.ssi:2
-msgid "B~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:4
-msgid "1~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:6
-msgid "2~ ISO"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:8
-msgid ""
-"Generating a Debian Live CD is very simple. You need to have live-helper "
-"(package available in Debian sid and lenny), and Debootstrap (or "
-"cdebootstrap) from etch or newer."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:10
-msgid "3~ Install live-helper"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:12
-msgid "#{apt-get install live-helper}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:14
-msgid "3~ Configure the current working directory with lh_config"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:18
-msgid "lh_config -b iso -a $ARCH"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:22
-msgid "where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:24
-msgid "#{-b}# flag is used to be sure to obtain image in ISO format."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:26
-msgid "3~ Build the image with lh_build:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:28
-msgid "Execute lh_build as root: #{lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:30
-msgid ""
-"The command above will create the basic image, containing just the Debian "
-"standard system (with no X at all)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:32
-msgid ""
-"If you want to have any of the Desktop environments on your livecd, #{ls /"
-"usr/share/live-helper/lists}# will show a number of available package Lists "
-"to choose from, e.g. #{lh_config -p gnome-desktop}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:34
-msgid "More examples are listed at DebianLive/Examples."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:37
-msgid ""
-"See packages for help configuring a local Debian Mirror and other aspects of "
-"the live system. % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:39
-msgid "3~ Test the image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:41
-msgid "If you have qemu installed, you can boot the image with:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:45
-msgid "qemu -cdrom binary.iso"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:49
-msgid "If you have also kqemu installed, you can add #{-kernel-kqemu}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:51
-msgid "2~ ISO_(multiarch)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:53
-msgid ""
-"Multiple machine boot CDs can be created with the following manual "
-"procedure. This procedure has been successfully used to create a single CD "
-"which is bootable on alpha, i386, pmax, and sparc. It should be possible to "
-"also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:55
-msgid ""
-"To create a CD which is bootable by multiple architectures, use the "
-"following steps in this order. Please note that the order is critical."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:57
-msgid ""
-"Make sure you have all the required files including the various kernels and "
-"boot programs listed in the individual machine sections."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:59
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.pmax "
-"and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/"
-"mdec.pmax/bootxx_cd9660."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:61
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.vax and "
-"include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/"
-"xxboot.}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:63
-msgid "Include the macppc ofwboot.xcf bootloader in /cdsources."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:65
-msgid ""
-"Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/"
-"installation/floppy/boot-big.fs \\ -c boot.catalog -l -J -r -L /cdsources "
-"2>&1 | tee /tmp/mkisofs.log exit}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:67
-msgid ""
-"Note: The appearance of the -v flag twice is required. If you are making a "
-"bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -"
-"part in the parameters for mkisofs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:69
-msgid ""
-"Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 "
-"bootblocks. Alternatively, install the sysutils/mksunbootcd package on your "
-"favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs "
-"boot-sun4m.fs boot-sun3.fs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:71
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/pmax to install the pmax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"pmax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:73
-msgid ""
-"#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:75
-msgid ""
-"The -o append,sunsum option appends the first stage boot block to the end of "
-"the ISO file system, and restores the checksum used when booting on a sun."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:77
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/vax to install the vax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"vax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:79
-msgid "installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:81
-msgid "(See the pmax entry above for an explanation of the flags)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:83
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/alpha to install the "
-"alpha bootblocks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:85
-msgid ""
-"#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:86
-msgid ""
-"Note: The alpha installboot must occur after the others, because currently "
-"it's the only machine dependent back-end for installboot(8) that can "
-"calculate the alpha checksum. (See the pmax entry above for an explanation "
-"of the flags)."
-msgstr ""
diff --git a/manual/po/fr/other_use-cases.ssi.po b/manual/po/fr/other_use-cases.ssi.po
deleted file mode 100644
index 7fb1186..0000000
--- a/manual/po/fr/other_use-cases.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# French translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: fr\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n > 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:2
-msgid "B~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:4
-msgid "1~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:6
-msgid "This chapter is for users to document their use cases with Debian Live."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:8
-msgid "2~ VNC Kiosk Client"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:10
-msgid "Create an image with live-helper to boot directly to a VNC server."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:12
-msgid "_* Make a build directory: #{$ mkdir vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:14
-msgid "_* Move to the build directory: #{$ cd vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:16
-msgid ""
-"Example to config the build directory to include gdm metacity "
-"xtightvncviewer: #{$ lh config --packages \"gdm metacity xtightvncviewer\"}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:18
-msgid ""
-"Create a folder /etc/skel folder for a custom .xsession for the default "
-"user: #{$ mkdir -p config/chroot_local-includes/etc/skel}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:20
-msgid ""
-"Create the .xsession for the default user: #{$ touch config/chroot_local-"
-"includes/etc/skel/.xsession}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:22
-msgid ""
-"Edit the .xsession file to launch metacity and start xvncviewer with "
-"something similar to the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:29
-msgid "/usr/bin/metacity & /usr/bin/vncviewer xxx.xxx.xxx.xxx:PORT"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:31
-msgid "exit"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:35
-msgid "_* Build the image: #{# lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:37 en/other_use-cases.ssi:138
-msgid "_* Enjoy."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:39
-msgid "2~ VMWare-Player Sessions"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:41
-msgid ""
-"Create an image with live-helper to boot directly to a specifiv VMWare "
-"session."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:43
-msgid "_* Make a build directory: #{$ mkdir VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:45
-msgid "_* Move to the build directory: #{$ cd VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:47
-msgid ""
-"_* Example to config the build directory to include gdm metacity "
-"xtightvncviewer:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:67
-#, no-wrap
-msgid ""
-"$ lh config --apt apt \\\n"
-" ---apt-recommends disabled \\\n"
-" --archive-areas \"main\" \\\n"
-" --binary-images iso \\\n"
-" --binary-indices none \\\n"
-" --syslinux-menu vesamenu \\\n"
-" ---bootappend-live \"persistent quickreboot\" \\\n"
-" ---bootappend-install \"-- plainroot persistent video=vesa:ywrap,mtrr vga=788 quickreboot quiet live-config\" \\\n"
-" ---debian-installer live \\\n"
-" ---distribution lenny \\\n"
-" ---hostname vmare-player-firmware \\\n"
-" ---includes none \\\n"
-" ---linux-flavours 686 \\\n"
-" ---packages-lists \"gnome-core\" \\\n"
-" ---packages \"gcc gparted linux-headers-2.6-\\${LH_LINUX_FLAVOURS} live-config-staging make metacity rsync wireless-tools\" \\\n"
-" ---repositories live.debian.net \\\n"
-" ---win32-loader disabled\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:71
-msgid ""
-"_* Create the 01-vmware-player hook: #{$ touch config/chroot_local-hooks/01-"
-"vmware-player.sh}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:73
-msgid ""
-"Edit the 01-vmware-player hook to launch the VMWare-Player. The hook should "
-"look something like the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:80
-msgid ""
-"_URL=\"http://archive.debian-maintainers.org/vmware/other/vmware-player/\" "
-"_VMPLAYER_VERSION=\"VMware-Player.i386.bundle\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:83
-msgid "echo \"I: Starting script for install of VMWare Player.\" cd /root"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:86
-msgid ""
-"echo \"I: Beginning download of ${_VMPLAYER_VERSION} from ${_URL} .\" wget "
-"${_URL}${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:89
-msgid ""
-"echo \"I: Starting install of VMWare Player.\" sh /root/${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:92
-msgid ""
-"echo \"I: Cleaning up the VMWare Player download.\" rm /root/"
-"${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:95
-msgid "#echo \"I: Starting interactive shell.\" #bash"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:99
-msgid ""
-"_* Build the image (note that during the build the VMWare-Player will prompt "
-"you to install or cancel): #{#lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:101
-msgid ""
-"_* After the build you will have an image you can boot live or install as "
-"firmware. The package live-config-staging is the package that installs the "
-"ability to utilize the VMWare-Player by calling live-config.vmware-player as "
-"a boot parameter in the following form:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:105
-msgid "live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:109
-msgid "Notes from the 900-vmware-player file are as follows:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:135
-#, no-wrap
-msgid ""
-"# The script tests for boot parameter of\n"
-"# live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME\n"
-"#\n"
-"# ACTION: The operation to perform on the workstation (none|scratch)\n"
-"# IMAGEPATH: The folder path to the VMware image you want to run.\n"
-"# VMXNAME: The name of the VMware image you want to run.\n"
-"#\n"
-"# Notes:To use this file with WMWare images you will need to have a few things\n"
-"# setup:\n"
-"#\n"
-"# 1. The VMware Player needs to be installed in the image.\n"
-"# 2. This script uses (s|h)da1 for writing image data, and is used as a scratch\n"
-"# space. This scratch space should be a file system with linux permissions\n"
-"# such as ext2.\n"
-"# 3. VMware image(s) should be in a mounted folder and setup as follows:\n"
-"# - Image(s) set to snapshot mode.\n"
-"# - For each image, the image folder needs to have a file called\n"
-"# image-release with a variable CRELEASE. An example: CRELEASE=\"1.0.0\"\n"
-"#\n"
-"# The image-release file is used by the image maintainer and this script to tell\n"
-"# workstation(s) using a given image, to erase locally stored vmware image files\n"
-"# and setup with the newly configure image. The operation of erasing locally\n"
-"# stored vmare image files, is referred to as a scratch.\n"
-msgstr ""
diff --git a/manual/po/fr/user_examples.ssi.po b/manual/po/fr/user_examples.ssi.po
index a84755f..cc78ab9 100644
--- a/manual/po/fr/user_examples.ssi.po
+++ b/manual/po/fr/user_examples.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:57-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-11-04 16:34-0400\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,13 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/other_faq.ssi:41 en/other_faq.ssi:83
-#: en/other_faq.ssi:103 en/other_faq.ssi:117 en/other_faq.ssi:137
-#: en/other_faq.ssi:151 en/other_faq.ssi:198 en/other_faq.ssi:245
-#: en/other_faq.ssi:261 en/other_faq.ssi:287 en/other_faq.ssi:299
-#: en/other_faq.ssi:314 en/other_faq.ssi:333 en/other_faq.ssi:345
-#: en/other_faq.ssi:353 en/other_faq.ssi:364 en/other_faq.ssi:374
-#: en/other_howtos.ssi:16 en/other_howtos.ssi:43 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:58
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -87,13 +81,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/other_faq.ssi:37 en/other_faq.ssi:46
-#: en/other_faq.ssi:92 en/other_faq.ssi:108 en/other_faq.ssi:141
-#: en/other_faq.ssi:155 en/other_faq.ssi:207 en/other_faq.ssi:256
-#: en/other_faq.ssi:292 en/other_faq.ssi:307 en/other_faq.ssi:319
-#: en/other_faq.ssi:337 en/other_faq.ssi:349 en/other_faq.ssi:358
-#: en/other_faq.ssi:370 en/other_faq.ssi:381 en/other_howtos.ssi:20
-#: en/other_howtos.ssi:47 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:62
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -150,12 +138,6 @@ msgid "}code"
msgstr "}code"
#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/user_examples.ssi:92
-#: en/user_examples.ssi:141 en/user_examples.ssi:190
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
#: en/user_basics.ssi:44 en/user_basics.ssi:120 en/user_basics.ssi:204
#: en/user_examples.ssi:109 en/user_examples.ssi:156
msgid "# lb build"
@@ -360,6 +342,11 @@ msgid "Edit #{auto/config}# to read as follows:"
msgstr ""
#. type: Plain text
+#: en/user_examples.ssi:92 en/user_examples.ssi:141 en/user_examples.ssi:190
+msgid "#!/bin/sh"
+msgstr ""
+
+#. type: Plain text
#: en/user_examples.ssi:99
#, no-wrap
msgid ""
diff --git a/manual/po/it/live-manual.ssm.po b/manual/po/it/live-manual.ssm.po
index 7067def..1e13d51 100644
--- a/manual/po/it/live-manual.ssm.po
+++ b/manual/po/it/live-manual.ssm.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:18-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-12-10 14:10+0100\n"
"Last-Translator: Carlo Stemberger <carlo.stemberger at gmail.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -184,13 +184,3 @@ msgstr ":B~ Esempi ~#"
#: en/live-manual.ssm:65
msgid "<< user_examples.ssi"
msgstr "<< user_examples.ssi"
-
-#. type: Plain text
-#: en/live-manual.ssm:67
-msgid "% << other_faq.ssi"
-msgstr "% << other_faq.ssi"
-
-#. type: Plain text
-#: en/live-manual.ssm:68
-msgid "% << other_howtos.ssi"
-msgstr "% << other_howtos.ssi"
diff --git a/manual/po/it/other_faq.ssi.po b/manual/po/it/other_faq.ssi.po
deleted file mode 100644
index 6dd88a7..0000000
--- a/manual/po/it/other_faq.ssi.po
+++ /dev/null
@@ -1,1008 +0,0 @@
-# Italian translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-10-16 14:45-0200\n"
-"PO-Revision-Date: 2010-10-16 14:45-0200\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: it\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:83 en/about_manual.ssi:91 en/about_manual.ssi:99
-#: en/about_manual.ssi:111 en/about_manual.ssi:124 en/about_manual.ssi:137
-#: en/about_manual.ssi:145 en/about_manual.ssi:153 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_faq.ssi:41 en/other_faq.ssi:83 en/other_faq.ssi:103
-#: en/other_faq.ssi:117 en/other_faq.ssi:137 en/other_faq.ssi:151
-#: en/other_faq.ssi:198 en/other_faq.ssi:245 en/other_faq.ssi:261
-#: en/other_faq.ssi:287 en/other_faq.ssi:299 en/other_faq.ssi:314
-#: en/other_faq.ssi:333 en/other_faq.ssi:345 en/other_faq.ssi:353
-#: en/other_faq.ssi:364 en/other_faq.ssi:374 en/other_howtos.ssi:16
-#: en/other_howtos.ssi:43 en/other_live-environment.ssi:14
-#: en/other_live-environment.ssi:30 en/other_live-environment.ssi:51
-#: en/other_live-environment.ssi:61 en/other_live-environment.ssi:69
-#: en/other_live-environment.ssi:77 en/other_live-environment.ssi:85
-#: en/other_live-environment.ssi:93 en/other_live-environment.ssi:116
-#: en/other_live-environment.ssi:124 en/other_live-environment.ssi:133
-#: en/other_procedures.ssi:12 en/other_procedures.ssi:46
-#: en/other_procedures.ssi:58 en/other_use-cases.ssi:24
-#: en/other_use-cases.ssi:49 en/other_use-cases.ssi:75
-#: en/other_use-cases.ssi:103 en/other_use-cases.ssi:111 en/user_basics.ssi:36
-#: en/user_basics.ssi:48 en/user_basics.ssi:62 en/user_basics.ssi:74
-#: en/user_basics.ssi:86 en/user_basics.ssi:98 en/user_basics.ssi:114
-#: en/user_basics.ssi:122 en/user_basics.ssi:130 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:180 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:212 en/user_basics.ssi:232 en/user_basics.ssi:265
-#: en/user_basics.ssi:281 en/user_basics.ssi:289 en/user_basics.ssi:309
-#: en/user_basics.ssi:334 en/user_customization-contents.ssi:34
-#: en/user_customization-contents.ssi:43 en/user_customization-contents.ssi:66
-#: en/user_customization-internationalization.ssi:10
-#: en/user_customization-internationalization.ssi:18
-#: en/user_customization-internationalization.ssi:26
-#: en/user_customization-internationalization.ssi:38
-#: en/user_customization-packages.ssi:16 en/user_customization-packages.ssi:24
-#: en/user_customization-packages.ssi:36 en/user_customization-packages.ssi:45
-#: en/user_customization-packages.ssi:59 en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:106
-#: en/user_installation.ssi:120 en/user_installation.ssi:137
-#: en/user_managing_a_configuration.ssi:24
-#: en/user_managing_a_configuration.ssi:35
-#: en/user_managing_a_configuration.ssi:47 en/user_overview.ssi:60
-#: en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:87 en/about_manual.ssi:95 en/about_manual.ssi:103
-#: en/about_manual.ssi:120 en/about_manual.ssi:133 en/about_manual.ssi:141
-#: en/about_manual.ssi:149 en/about_manual.ssi:157 en/about_manual.ssi:164
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_faq.ssi:37 en/other_faq.ssi:46 en/other_faq.ssi:92
-#: en/other_faq.ssi:108 en/other_faq.ssi:141 en/other_faq.ssi:155
-#: en/other_faq.ssi:207 en/other_faq.ssi:256 en/other_faq.ssi:292
-#: en/other_faq.ssi:307 en/other_faq.ssi:319 en/other_faq.ssi:337
-#: en/other_faq.ssi:349 en/other_faq.ssi:358 en/other_faq.ssi:370
-#: en/other_faq.ssi:381 en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:92
-#: en/user_basics.ssi:104 en/user_basics.ssi:118 en/user_basics.ssi:126
-#: en/user_basics.ssi:134 en/user_basics.ssi:144 en/user_basics.ssi:158
-#: en/user_basics.ssi:168 en/user_basics.ssi:176 en/user_basics.ssi:184
-#: en/user_basics.ssi:198 en/user_basics.ssi:206 en/user_basics.ssi:216
-#: en/user_basics.ssi:257 en/user_basics.ssi:285 en/user_basics.ssi:293
-#: en/user_basics.ssi:320 en/user_basics.ssi:359
-#: en/user_customization-contents.ssi:39 en/user_customization-contents.ssi:54
-#: en/user_customization-contents.ssi:70
-#: en/user_customization-internationalization.ssi:14
-#: en/user_customization-internationalization.ssi:22
-#: en/user_customization-internationalization.ssi:30
-#: en/user_customization-internationalization.ssi:42
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:172
-#: en/user_customization-packages.ssi:182
-#: en/user_customization-packages.ssi:192
-#: en/user_customization-packages.ssi:202 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:88 en/user_installation.ssi:110
-#: en/user_installation.ssi:125 en/user_installation.ssi:140
-#: en/user_managing_a_configuration.ssi:31
-#: en/user_managing_a_configuration.ssi:43
-#: en/user_managing_a_configuration.ssi:52 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:2
-msgid "B~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:4
-msgid "1~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:8
-msgid ""
-"Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A: "
-"See \"Copying USB/HDD image to a USB stick\" % FIXME: <xref linkend="
-"\"image_copying\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:11
-msgid ""
-"Q: How do I log my build? A: You could use script, screen or tee: #{$ "
-"lh_build 2>&1 | tee build.log}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:14
-msgid ""
-"Q: How can I convert an already installed standard Debian partition into a "
-"Debian Live system? A: Save the list of installed packages and load it into "
-"your new Debian Live System. Copy your /etc to config/chroot_local-includes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:17
-msgid ""
-"Q: What does 'losetup: could not find any free loop device' mean and how do "
-"I fix it? A: Loop devices are used during the build; there probably aren't "
-"any free if you've aborted several builds. Something like: for l in /dev/"
-"loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/"
-"loop7 ; do losetup -d $l ; done should rectify the situation (assuming all "
-"loop devices in use were created by lh_build; if in doubt, check the "
-"contents of each loop device before deleting them with losetup -d)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:20
-msgid ""
-"Q: How do I launch an interactive shell during the chroot stage? A: To "
-"enable interactive shell: #{$ lh_config --interactive shell}# To continue "
-"the build process: #{# logout}# or #{# exit}# To disable interactive shell, "
-"set LH_INTERACTIVE to \"disabled\" in config/chroot."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:23
-msgid ""
-"Q: What is the root /user password? A: The user password for the live user "
-"is 'live'. By default, there is not any root password. You can switch to "
-"root with ${sudo -i}# or set a password for root with #{sudo passwd}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:27
-msgid ""
-"Q: How do I change root or any user password? A: Add a chroot local hook "
-"script to change root or any user password each time you build an image. e."
-"g. config/chroot_local-hooks/01-update_password.sh to set root password to "
-"\"nopasswd\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:30 en/other_faq.ssi:53
-msgid "code{ #!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:33
-msgid "echo \"I: update password\" echo \"root:nopasswd\" | chpasswd"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:35
-msgid "$ chmod +x config/chroot_local-hooks/01-update_password.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:39
-msgid ""
-"Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/"
-"live-bottom/10adduser your build folder:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:44
-msgid ""
-"mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-"
-"bottom/ cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/"
-"chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:48
-msgid ""
-"Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/"
-"scripts/live-bottom/10adduser and paste in the new user_crypted password "
-"that you make with: #{echo \"newlivepass\" | mkpasswd -s}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:50
-msgid ""
-"Or add an hook file in config/chroot_local-hooks/ with something like the "
-"below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:57
-msgid ""
-"# Change the autogenerated user password to \"debianlive\" plain_password="
-"\"debianlive\" password=$(echo \"${plain_password}\" | mkpasswd -s)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:59
-msgid ""
-"sed -i -e 's/\\(user_crypted=\\)\\(.*\\)\\( #.*\\)/\\1\\\"'${password}'\\"
-"\"\\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:62
-msgid "update-initramfs -tu -kall }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:64
-msgid ""
-"The latter (hook model) could be more future proof than the former solution "
-"since it modifies just one string selectively but it requires the package "
-"\"whois\" to be installed on the target system (for mkpasswd) or that you "
-"generate the $password string not at build time and include it crypted in "
-"the above script."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:68
-msgid ""
-"Q: How to disable autologin? A1: use the commandline parameter #{lh config --"
-"bootappend-live \"noautologin\"}# A2: You need to set boot=noautologin "
-"noxautologin as described in man live-initramfs If you boot via TFTP you "
-"want to insert the option to pxelinux.cfg/default"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:71
-msgid ""
-"Q: How do I change default hostname or username? A: To change default "
-"hostname or username: #{$ lh_config --hostname myhostname $ lh_config --"
-"username myusername}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:74
-msgid ""
-"Q: How do I make the final image smaller? A: Clean orphaned apps/libs: "
-"Install package \"deborphan\" and then run 'sudo deborphan -n' . Delete "
-"unwanted packages. Remove the apt cache. Purge unwanted locales (see "
-"\"localepurge\" package)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:77
-msgid ""
-"Q: How do I customize bash-config permanently (aliases, bash-completion "
-"etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:81
-msgid ""
-"Q: How do I disable services permanently? (Be careful!) A: Add a chroot "
-"local hook script to disable a service each time you build an image: e.g. "
-"config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr "#!/bin/sh"
-
-#. type: Plain text
-#: en/other_faq.ssi:88
-msgid "echo \"I: disable service\" update-rc.d -f service_name remove"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:90
-msgid "$ chmod +x config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:95
-msgid ""
-"Q: How do I enable | disable the md5checksum at the ISO building? A: #"
-"{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:98
-msgid ""
-"Q: How to disable the generation of the .tar.gz file? A: #{lh_config --net-"
-"tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in "
-"snapsshot version at the moment 2008/Feb/28)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:101
-msgid "Q: How do I \"build a new image\"? A: Run commands:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:106
-msgid "$ sudo lh_clean --binary $ sudo lh_build"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:110
-msgid ""
-"Hint: If the configuration had changed you should leave \"--binary\" out. "
-"This will clean your chroot directory too."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:113
-msgid ""
-"Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages "
-"you want."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:115
-msgid "Create /home/$USERNAME/.dmrc file (default username is \"user\")."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:122
-msgid "$ cat .dmrc [Desktop] Session=fluxbox }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:124
-msgid "Note: .dmrc is owned by $USERNAME:$USERNAME."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:126
-msgid ""
-"See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at "
-"http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:129
-msgid ""
-"Q: How do I use custom repositories? A: See http://wiki.debian.org/"
-"DebianLive/Configuration"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:132
-msgid ""
-"Q: How do I customize the artwork for the live CD (grub or syslinux boot "
-"splash, usplash, etc.)? A: See http://wiki.debian.org/DebianLive/Howto/"
-"Custom_Artwork"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:135
-msgid ""
-"Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look? "
-"A: Start the live system in qemu:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:139
-msgid "$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:143
-msgid "Note: the -redir argument must be changed to meet your needs"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:146
-msgid ""
-"Q: How do I execute a custom shell script inside the chroot system after the "
-"chroot stage? A: Add your script in config/chroot_local-hooks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:149
-msgid ""
-"Q: How do I add a script running immediately after all other scripts when "
-"the live system boots? A: Add your script in config/chroot_local-includes/"
-"usr/share/initramfs-tools/scripts/live-bottom/99scrip"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:153
-msgid ""
-"$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/"
-"live-bottom/99script"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:157
-msgid ""
-"Note: The hook script must be executable. Do not forget to lh_clean --chroot "
-"after making this change before you build again."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:159
-msgid ""
-"You must also use the example script /usr/share/live-helper/examples/hooks/"
-"update-initramfs.sh to ensure your script gets built into the initramfs "
-"(read the comment header for instructions)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:163
-msgid ""
-"Q: How do I add software not in Debian ? A: See Customizing package "
-"installation % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:166
-msgid ""
-"Q: What is the manifest with Ubuntu used for? A: Manifest is just the "
-"package list, which ubuntu does $something with. Don't worry about it."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:169
-msgid ""
-"Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:172
-msgid ""
-"Q: Do I need to write the image on USB stick to test it? A: you must use "
-"qemu >= 0.8."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:175
-msgid "Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:178
-msgid ""
-"Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed "
-"something else entirely? A: It is not. It is a package list, not a debconf "
-"preseeding."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:181
-msgid ""
-"Q: What is the difference between standard and minimal? A: standard: "
-"packages of priority standard and higher; minimal: packages of priority "
-"essential and higher;"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:184
-msgid ""
-"Q: What can the sections be used for? Aren't they BIG? A: Someone maybe "
-"wants to include packages from contrib or non-free."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:187
-msgid "Q: memtest86+ ... is that used? A: Yes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:190
-msgid ""
-"Q: How do I build using predefined packages lists? A: e.g. to build using "
-"standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo "
-"lh_build}# Note: The packages lists can be found in /usr/share/live-helper/"
-"lists/ directory."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:193
-msgid ""
-"Q: How do I rebuild without downloading all the packages again? A: All "
-"packages are cached in cache subdirectory. They remain until a clean purge: #"
-"{$ sudo lh_clean --purge}# You do not have to do anything to prevent "
-"packages from being re-downloaded. You need to remember to clean whichever "
-"stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, "
-"chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:196
-msgid ""
-"Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make "
-"a boot CD with grub, configured to boot from a debian-live kernel copied on "
-"the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/"
-"stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/"
-"boot/grub/menu.lst:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:205
-msgid ""
-"default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd) "
-"kernel /boot/vmlinuz boot=live initrd /boot/initrd.img"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:209
-msgid ""
-"Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-"
-"boot \\ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:212
-msgid ""
-"Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A: "
-"If you have a floppy drive, you may be able to use it, otherwise you will "
-"need to use loadlin/grub4dos/win32-loader. If you have a second system to "
-"serve up the image over the network, See http://wiki.debian.org/DebianLive/"
-"Howto/Creating_a_Netboot_Image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:215
-msgid ""
-"Q: The X configuration does not seems to work, the resolution is too low. "
-"What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf "
-"&& lh_config --packages xdebconfigurator}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:218
-msgid ""
-"Q: Apache has problems with static files A: Sendfile does not work well on "
-"the unionfs used by Debian Live. Add the following to apache's "
-"configuration: #{EnableSendfile off}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:222
-msgid ""
-"Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right "
-"now the best is to use a script that will populate the fstab when the CD is "
-"booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/"
-"trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper "
-"solution based on HAL will be described here in a hopefully near future. A: "
-"Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-"
-"policy-fixed-drives.fdi is not available anymore and the previous trick that "
-"consisted to remove this file to enable automounting of fixed drives as a "
-"consequence is obsolete. Eventually, it will be possible to combine HAL and "
-"PolicyKit to enable different permissions and actions to achieve advanced "
-"(auto)mounting for non-root users. Until then, because the live scripts are "
-"only touching to the fstab to add a swap partition if discovered at boot "
-"time, the only way to have fixed drives mounted automatically is to use a "
-"script that will populate the fstab file at the end of the multiuser "
-"runlevel. To achieve this, you can do, for example, the following: download "
-"the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-"
-"includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin "
-"directory, and move the script inside Make sure the script is executable "
-"(chmod +x diskmounter.sh) create the chroot_local-includes/etc/rc.local file "
-"and call the diskmounter from there (see this https://devel.goto10.org/svn/"
-"puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called "
-"correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and "
-"NTFS partitions and mount them read-write, except for NTFS. This will change "
-"soon and an option will be available to use ntfs-3g to mount NTFS as read-"
-"write. comments, patches and other things about this script and issue: "
-"http://code.goto10.org/projects/puredyne/ticket/463"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:225
-msgid ""
-"Q: Boot fails with panic: can't open /scripts/live A: Add latest live-"
-"initramfs deb package into config/chroot_local-packages directory and "
-"rebuild."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:229
-msgid ""
-"Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref "
-"linkend=\"internalization\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:234
-msgid ""
-"Q: How do I get past boot prompt without a working keyboard? A: See "
-"Customizing the bootup process % FIXME: <xref linkend=\"bootup\"/> Note: "
-"Boot from an USB-HDD on an iMac with GRUB did not work."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:237
-msgid ""
-"Q: Can I serve the root image from a web or ftp server? A: Since live-"
-"initramfs 1.99, it should be possible to use the fetch= argument on the "
-"kernel command line. You can build a netboot image as usual, and when you "
-"are done edit the tftpboot/pxelinux.cfg/default file. Remove the references "
-"to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url "
-"where you placed the root image>. You have to include wget in the chroot. It "
-"could work for other boot methods as well. However, I am not sure the live "
-"scripts configure the network when booting from a CD or USB disk. #{$ "
-"lh_config --packages wget}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:240
-msgid ""
-"Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you "
-"are building an etch image (which was the default up to 2007/09/14) you have "
-"a very old version of casper which does not support quickreboot and possibly "
-"other boot parameters as well. You could configure your sources to use live-"
-"backports (see /usr/share/live-helper/examples/sources/live-backports) and "
-"switch to live-initramfs, or better yet, build a lenny image instead, which "
-"is the new default. #{$ lh_config --distribution lenny $ lh_config --"
-"initramfs live-initramfs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:243
-msgid ""
-"Q: How do I fix \"Could not find kernel image\" issue with syslinux "
-"bootloader? A: Add a binary local hook script to fix kernel and initrd path "
-"each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux."
-"sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:249
-msgid "SYSLINUXCFG=`find binary -type f -name syslinux.cfg`"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:252
-msgid ""
-"sed -i \"s|kernel /vmlinuz|kernel vmlinuz|g\" ${SYSLINUXCFG} sed -i \"s|"
-"initrd=/initrd|initrd=initrd|g\" ${SYSLINUXCFG}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:254
-msgid "$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:259
-msgid ""
-"Q: How do I use a newer kernel with lenny? A: A build with backports.org "
-"kernels will fail as that repository lacks the necessary module packages "
-"(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://"
-"unsupported.debian-maintainers.org/backports-kernel/ The quick way to "
-"success:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:268
-msgid ""
-"$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-"
-"modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-"
-"kernel/ ./' > config/chroot_sources/backports-kernel.chroot $ echo 'deb "
-"http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/"
-"chroot_sources/backports-kernel.binary $ wget http://unsupported.debian-"
-"maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/"
-"backports-kernel.chroot.gpg $ wget http://unsupported.debian-maintainers.org/"
-"backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel."
-"binary.gpg $ lh_build }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:271
-msgid ""
-"Q: How do I use a custom kernel? Is there a nice way of booting debian-live "
-"with a custom kernel (not in an apt repo)? A: Copy it into config/"
-"chroot_local-packages and set LH_LINUX_PACKAGES=\"none\" or use lh config --"
-"linux-packages \" \" Don't forget to compile your kernel with an union "
-"filesystem (unionfs or aufs), squashfs modules, and initrd support. I can "
-"cause the kernel to be installed but it seems this happens later than grub/"
-"syslinux is configured so it's not listed and casper/ and the menu require "
-"munging. You need to follow the debian scheme, e.g. placing the files in /"
-"boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't "
-"go that way which is too much of a hassle, and just use make-kpkg to produce "
-"custom kernel deb packages. They should integrate nicely if you just put "
-"them into config/chroot_local-packages and set LH_LINUX_PACKAGES=\"\". Hint: "
-"to work around an error, which lh_binary_syslinux will throw on custom "
-"kernels if there is not an 468/686 in the kernel-name, you need to set "
-"CONFIG_LOCALVERSION=\"-486\" or \"-686\" within the kernel configuration (-"
-"> General setup -> Local version set to -486 or -686) corresponding to "
-"LH_LINUX_FLAVOURS=\"\" or \"686\". this at least up till live-helper version "
-"1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-"
-"devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/"
-"debian-live-devel/2007-November/002581.html"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:274
-msgid ""
-"Q: How do I create a cross arch live CD image? A: In short: You can't. Read "
-"on: The procedure to create a live CD is based on creating a chroot that "
-"contains the files that will be finally available on the live CD. The live "
-"CD building procedure includes chrooting into the chroot dir and so some "
-"operations. chrooting means that the terminal you chroot on will behave as a "
-"different system so your real system and the chroot environment is decoupled "
-"somehow. Once the live CD scripts chroots into the chroot dir they have some "
-"operations to do inside that environment and your real system won't be able "
-"to run them unless you are using the same architecture. So you only are able "
-"to make live CD for the arch you run on. But this doesn't prevent you run "
-"qemu or some other machine emulator that make this possible."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:277
-msgid ""
-"Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That "
-"depends what you've changed between builds If, for example, you've built an "
-"iso image and you want a usb image, you only need to run #{lh_clean --binary}"
-"# before you run lh_build again. If you've changed anything in the chroot, "
-"you'll need to cleanup both chroot and binary with #{lh_clean}# before "
-"continuing"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:280
-msgid ""
-"Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in config/binary"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:283
-msgid ""
-"Q: How do I include different modules to load when the live system boots? A: "
-"Configure config/chroot_local-includes/etc/initramfs-tools/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:285
-msgid ""
-"The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default "
-"initramfs.conf \"MODULES = most\". You may override that by supplying your "
-"own initramfs.conf, or else just add your own modules, e.g."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:290
-msgid ""
-"mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo \"atl2\" >> "
-"config/chroot_local-includes/etc/initramfs-tools/modules"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:294
-msgid ""
-"Note: Even though initramfs.conf(5) says \"most adds all the framebuffer, "
-"acpi, file system, ide, sata, scsi and usb drivers\", it actually includes "
-"network drivers as well. See auto_add_modules() in /usr/share/initramfs-"
-"tools/hook-functions for the complete list."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:297
-msgid ""
-"Q: Can I have a splash screen? A: Yes you can. You will not know what is "
-"going on when the splash screen is active, it may fail to activate on some "
-"hardware or break X on other (both usplash and splashy use libdirectfb which "
-"does some evil voodoo and may break you graphics or input until you reboot). "
-"However, you can install and activate it just as you would on any other "
-"Debian system. To use splashy: 1. install splashy and read the README, the "
-"manpages are useless for setting it up. Add some parameters to your kernel "
-"command line, such as in your pxelinux configuration or in "
-"LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 "
-"splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, "
-"#{quiet}# to suppress most kernel messages that you cannot see anyway but "
-"would scroll past before splashy manages to paint the graphics on your "
-"screen. You might want to add splashy to the list of packages installed in "
-"your image: #{echo splashy > config/chroot_local-packageslists/splashy echo "
-"splashy-themes >> config/chroot_local-packageslists/splashy}# and select a "
-"theme:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:305
-msgid ""
-"echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s "
-"debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the "
-"ramdisk to include the splash screen echo update-initramfs -u -k all >> "
-"config/chroot_local-hooks/splashy chmod 755 config/chroot_local-hooks/splashy"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:309
-msgid ""
-"After you rebuild your live system you should observe a bluish splash screen "
-"while booting. Nothing happens while initramfs is running because there is "
-"no splashy support in initramfs-tools. Once the init starts the progress bar "
-"should start to fill. If #{vga=something}# sets a mode that your screen "
-"cannot show or your card cannot do vesa 2.0 (and thus you get plain text "
-"mode and no splashy) read the splashy faq."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:312
-msgid ""
-"Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the "
-"firmwares to the initrd image. You need to install the non-free package "
-"\"firmware-bnx2\". Uncompress your initrd image, then copy files:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:317
-msgid ""
-"cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /"
-"lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw "
-"${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:321
-msgid "Recompress your initrd image and boot: it works!"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:323
-msgid ""
-"Q: X is broken (the system boots, messages scroll by, and then the screen "
-"goes blank). What do I do? A: On my system starting X completely disables "
-"graphics so that I do not see anything even after X bails out and I am back "
-"to the console. To prevent this you can change the driver Xorg uses."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:325
-msgid ""
-"If you have a working splash screen or at least graphical console you can "
-"use #{live xdriver=fbdev}# when booting the live system (instead of just "
-"enter). Another driver you might want to try is #{vesa}#. If all fails you "
-"might try to set xdriver to some wrong value so that Xorg fails to start and "
-"you can examine the system while you still see something on the console. #"
-"{live xdriver=none}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:328
-msgid ""
-"Q: How can I get Debian first stable versions? A: I'm developing software "
-"and testing it on Live-CD. Thanks for the LiveCD project. To be sure my "
-"development is fully compatible with the \"etch\" version, I need the same "
-"scenario when Debian GNU/Linux 4.0 was published as stable (I believe "
-"2007.04.08). If there was some bug on 2007.04.08 that was corrected one week "
-"later, I need to test software foreseeing that scenario without the bug "
-"solved."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:331
-msgid ""
-"Q: I get \"fopen: Permission denied\"-warnings from apt on building/at the "
-"live-system A: That's a harmless bug in apt. However, if you want to get off "
-"this warnings in the live-system, add a file in chroot_local-hooks with "
-"follow row:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:335
-msgid "chown -R man.man /var/cache/man"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:340
-msgid ""
-"Q: Why I always fail during \"Retrieving Packages\" stage when running "
-"lh_build? I have already set apt-http-proxy and so on. A: lh_build "
-"retrieves packages via wget, as a result you need to enable the proxy "
-"settings in /etc/wgetrc before running lh_build."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:343
-msgid ""
-"Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system "
-"boots, so it's useless to put modifed Xorg.conf in config/choort_local-"
-"includes/etc/X11, because it will be overwritten during boot. However, you "
-"can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the "
-"result will be modified Xorg.conf. The modified dexconf has to be put in "
-"config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for "
-"two or more keyboards layouts with alt+shift toggle by editing dexconf and "
-"replacing the line:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:347
-msgid "Option \"XkbLayout\" \"$XKB_LAYOUT\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:351
-msgid "with the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:356
-msgid ""
-"Option \"XkbLayout\" \"us,il\" Option \"XkbOptions\" \"grp:alt_shift_toggle,"
-"grp_led:scroll\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:360
-msgid "when \"us,il\" are the wanted keyboard layouts."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:362
-msgid ""
-"You can force default screen resulotion (e.g. 1024*768) by adding the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:368
-#, no-wrap
-msgid ""
-"SubSection \"Display\"\n"
-" Modes \"1024x768\"\n"
-"EndSubSection\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:372
-msgid "between the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:379
-#, no-wrap
-msgid ""
-"Section \"Screen\"\n"
-" Identifier \"Default Screen\"\n"
-" Monitor \"Configured Monitor\"\n"
-"EndSection\"\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:383
-msgid ""
-"Q: Where are the build parameters for the prebuilt images A: See http://live."
-"debian.net/README.images."
-msgstr ""
diff --git a/manual/po/it/other_howtos.ssi.po b/manual/po/it/other_howtos.ssi.po
deleted file mode 100644
index fb73947..0000000
--- a/manual/po/it/other_howtos.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# Italian translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: it\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_howtos.ssi:2
-msgid "B~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:4
-msgid "1~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:6
-msgid "2~ ISO"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:8
-msgid ""
-"Generating a Debian Live CD is very simple. You need to have live-helper "
-"(package available in Debian sid and lenny), and Debootstrap (or "
-"cdebootstrap) from etch or newer."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:10
-msgid "3~ Install live-helper"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:12
-msgid "#{apt-get install live-helper}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:14
-msgid "3~ Configure the current working directory with lh_config"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:18
-msgid "lh_config -b iso -a $ARCH"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:22
-msgid "where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:24
-msgid "#{-b}# flag is used to be sure to obtain image in ISO format."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:26
-msgid "3~ Build the image with lh_build:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:28
-msgid "Execute lh_build as root: #{lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:30
-msgid ""
-"The command above will create the basic image, containing just the Debian "
-"standard system (with no X at all)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:32
-msgid ""
-"If you want to have any of the Desktop environments on your livecd, #{ls /"
-"usr/share/live-helper/lists}# will show a number of available package Lists "
-"to choose from, e.g. #{lh_config -p gnome-desktop}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:34
-msgid "More examples are listed at DebianLive/Examples."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:37
-msgid ""
-"See packages for help configuring a local Debian Mirror and other aspects of "
-"the live system. % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:39
-msgid "3~ Test the image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:41
-msgid "If you have qemu installed, you can boot the image with:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:45
-msgid "qemu -cdrom binary.iso"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:49
-msgid "If you have also kqemu installed, you can add #{-kernel-kqemu}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:51
-msgid "2~ ISO_(multiarch)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:53
-msgid ""
-"Multiple machine boot CDs can be created with the following manual "
-"procedure. This procedure has been successfully used to create a single CD "
-"which is bootable on alpha, i386, pmax, and sparc. It should be possible to "
-"also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:55
-msgid ""
-"To create a CD which is bootable by multiple architectures, use the "
-"following steps in this order. Please note that the order is critical."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:57
-msgid ""
-"Make sure you have all the required files including the various kernels and "
-"boot programs listed in the individual machine sections."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:59
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.pmax "
-"and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/"
-"mdec.pmax/bootxx_cd9660."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:61
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.vax and "
-"include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/"
-"xxboot.}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:63
-msgid "Include the macppc ofwboot.xcf bootloader in /cdsources."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:65
-msgid ""
-"Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/"
-"installation/floppy/boot-big.fs \\ -c boot.catalog -l -J -r -L /cdsources "
-"2>&1 | tee /tmp/mkisofs.log exit}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:67
-msgid ""
-"Note: The appearance of the -v flag twice is required. If you are making a "
-"bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -"
-"part in the parameters for mkisofs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:69
-msgid ""
-"Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 "
-"bootblocks. Alternatively, install the sysutils/mksunbootcd package on your "
-"favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs "
-"boot-sun4m.fs boot-sun3.fs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:71
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/pmax to install the pmax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"pmax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:73
-msgid ""
-"#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:75
-msgid ""
-"The -o append,sunsum option appends the first stage boot block to the end of "
-"the ISO file system, and restores the checksum used when booting on a sun."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:77
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/vax to install the vax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"vax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:79
-msgid "installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:81
-msgid "(See the pmax entry above for an explanation of the flags)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:83
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/alpha to install the "
-"alpha bootblocks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:85
-msgid ""
-"#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:86
-msgid ""
-"Note: The alpha installboot must occur after the others, because currently "
-"it's the only machine dependent back-end for installboot(8) that can "
-"calculate the alpha checksum. (See the pmax entry above for an explanation "
-"of the flags)."
-msgstr ""
diff --git a/manual/po/it/user_examples.ssi.po b/manual/po/it/user_examples.ssi.po
index b05d8cd..e448baa 100644
--- a/manual/po/it/user_examples.ssi.po
+++ b/manual/po/it/user_examples.ssi.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-12-11 13:57-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-12-09 00:03+0100\n"
"Last-Translator: Carlo Stemberger <carlo.stemberger at gmail.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -21,13 +21,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/other_faq.ssi:41 en/other_faq.ssi:83
-#: en/other_faq.ssi:103 en/other_faq.ssi:117 en/other_faq.ssi:137
-#: en/other_faq.ssi:151 en/other_faq.ssi:198 en/other_faq.ssi:245
-#: en/other_faq.ssi:261 en/other_faq.ssi:287 en/other_faq.ssi:299
-#: en/other_faq.ssi:314 en/other_faq.ssi:333 en/other_faq.ssi:345
-#: en/other_faq.ssi:353 en/other_faq.ssi:364 en/other_faq.ssi:374
-#: en/other_howtos.ssi:16 en/other_howtos.ssi:43 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:58
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -88,13 +82,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/other_faq.ssi:37 en/other_faq.ssi:46
-#: en/other_faq.ssi:92 en/other_faq.ssi:108 en/other_faq.ssi:141
-#: en/other_faq.ssi:155 en/other_faq.ssi:207 en/other_faq.ssi:256
-#: en/other_faq.ssi:292 en/other_faq.ssi:307 en/other_faq.ssi:319
-#: en/other_faq.ssi:337 en/other_faq.ssi:349 en/other_faq.ssi:358
-#: en/other_faq.ssi:370 en/other_faq.ssi:381 en/other_howtos.ssi:20
-#: en/other_howtos.ssi:47 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:62
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -151,12 +139,6 @@ msgid "}code"
msgstr "}code"
#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/user_examples.ssi:92
-#: en/user_examples.ssi:141 en/user_examples.ssi:190
-msgid "#!/bin/sh"
-msgstr "#!/bin/sh"
-
-#. type: Plain text
#: en/user_basics.ssi:44 en/user_basics.ssi:120 en/user_basics.ssi:204
#: en/user_examples.ssi:109 en/user_examples.ssi:156
msgid "# lb build"
@@ -412,6 +394,11 @@ msgid "Edit #{auto/config}# to read as follows:"
msgstr ""
#. type: Plain text
+#: en/user_examples.ssi:92 en/user_examples.ssi:141 en/user_examples.ssi:190
+msgid "#!/bin/sh"
+msgstr "#!/bin/sh"
+
+#. type: Plain text
#: en/user_examples.ssi:99
#, no-wrap
msgid ""
diff --git a/manual/po/pt_BR/live-manual.ssm.po b/manual/po/pt_BR/live-manual.ssm.po
index d398609..0913e56 100644
--- a/manual/po/pt_BR/live-manual.ssm.po
+++ b/manual/po/pt_BR/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:18-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-10-22 07:52-0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -173,13 +173,3 @@ msgstr ""
#: en/live-manual.ssm:65
msgid "<< user_examples.ssi"
msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:67
-msgid "% << other_faq.ssi"
-msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:68
-msgid "% << other_howtos.ssi"
-msgstr ""
diff --git a/manual/po/pt_BR/other_faq.ssi.po b/manual/po/pt_BR/other_faq.ssi.po
deleted file mode 100644
index a6fc8ce..0000000
--- a/manual/po/pt_BR/other_faq.ssi.po
+++ /dev/null
@@ -1,1008 +0,0 @@
-# Portuguese translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-16 14:45-0200\n"
-"PO-Revision-Date: 2010-10-16 14:45-0200\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: pt_BR\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n > 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:83 en/about_manual.ssi:91 en/about_manual.ssi:99
-#: en/about_manual.ssi:111 en/about_manual.ssi:124 en/about_manual.ssi:137
-#: en/about_manual.ssi:145 en/about_manual.ssi:153 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_faq.ssi:41 en/other_faq.ssi:83 en/other_faq.ssi:103
-#: en/other_faq.ssi:117 en/other_faq.ssi:137 en/other_faq.ssi:151
-#: en/other_faq.ssi:198 en/other_faq.ssi:245 en/other_faq.ssi:261
-#: en/other_faq.ssi:287 en/other_faq.ssi:299 en/other_faq.ssi:314
-#: en/other_faq.ssi:333 en/other_faq.ssi:345 en/other_faq.ssi:353
-#: en/other_faq.ssi:364 en/other_faq.ssi:374 en/other_howtos.ssi:16
-#: en/other_howtos.ssi:43 en/other_live-environment.ssi:14
-#: en/other_live-environment.ssi:30 en/other_live-environment.ssi:51
-#: en/other_live-environment.ssi:61 en/other_live-environment.ssi:69
-#: en/other_live-environment.ssi:77 en/other_live-environment.ssi:85
-#: en/other_live-environment.ssi:93 en/other_live-environment.ssi:116
-#: en/other_live-environment.ssi:124 en/other_live-environment.ssi:133
-#: en/other_procedures.ssi:12 en/other_procedures.ssi:46
-#: en/other_procedures.ssi:58 en/other_use-cases.ssi:24
-#: en/other_use-cases.ssi:49 en/other_use-cases.ssi:75
-#: en/other_use-cases.ssi:103 en/other_use-cases.ssi:111 en/user_basics.ssi:36
-#: en/user_basics.ssi:48 en/user_basics.ssi:62 en/user_basics.ssi:74
-#: en/user_basics.ssi:86 en/user_basics.ssi:98 en/user_basics.ssi:114
-#: en/user_basics.ssi:122 en/user_basics.ssi:130 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:180 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:212 en/user_basics.ssi:232 en/user_basics.ssi:265
-#: en/user_basics.ssi:281 en/user_basics.ssi:289 en/user_basics.ssi:309
-#: en/user_basics.ssi:334 en/user_customization-contents.ssi:34
-#: en/user_customization-contents.ssi:43 en/user_customization-contents.ssi:66
-#: en/user_customization-internationalization.ssi:10
-#: en/user_customization-internationalization.ssi:18
-#: en/user_customization-internationalization.ssi:26
-#: en/user_customization-internationalization.ssi:38
-#: en/user_customization-packages.ssi:16 en/user_customization-packages.ssi:24
-#: en/user_customization-packages.ssi:36 en/user_customization-packages.ssi:45
-#: en/user_customization-packages.ssi:59 en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:106
-#: en/user_installation.ssi:120 en/user_installation.ssi:137
-#: en/user_managing_a_configuration.ssi:24
-#: en/user_managing_a_configuration.ssi:35
-#: en/user_managing_a_configuration.ssi:47 en/user_overview.ssi:60
-#: en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:87 en/about_manual.ssi:95 en/about_manual.ssi:103
-#: en/about_manual.ssi:120 en/about_manual.ssi:133 en/about_manual.ssi:141
-#: en/about_manual.ssi:149 en/about_manual.ssi:157 en/about_manual.ssi:164
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_faq.ssi:37 en/other_faq.ssi:46 en/other_faq.ssi:92
-#: en/other_faq.ssi:108 en/other_faq.ssi:141 en/other_faq.ssi:155
-#: en/other_faq.ssi:207 en/other_faq.ssi:256 en/other_faq.ssi:292
-#: en/other_faq.ssi:307 en/other_faq.ssi:319 en/other_faq.ssi:337
-#: en/other_faq.ssi:349 en/other_faq.ssi:358 en/other_faq.ssi:370
-#: en/other_faq.ssi:381 en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:92
-#: en/user_basics.ssi:104 en/user_basics.ssi:118 en/user_basics.ssi:126
-#: en/user_basics.ssi:134 en/user_basics.ssi:144 en/user_basics.ssi:158
-#: en/user_basics.ssi:168 en/user_basics.ssi:176 en/user_basics.ssi:184
-#: en/user_basics.ssi:198 en/user_basics.ssi:206 en/user_basics.ssi:216
-#: en/user_basics.ssi:257 en/user_basics.ssi:285 en/user_basics.ssi:293
-#: en/user_basics.ssi:320 en/user_basics.ssi:359
-#: en/user_customization-contents.ssi:39 en/user_customization-contents.ssi:54
-#: en/user_customization-contents.ssi:70
-#: en/user_customization-internationalization.ssi:14
-#: en/user_customization-internationalization.ssi:22
-#: en/user_customization-internationalization.ssi:30
-#: en/user_customization-internationalization.ssi:42
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:172
-#: en/user_customization-packages.ssi:182
-#: en/user_customization-packages.ssi:192
-#: en/user_customization-packages.ssi:202 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:88 en/user_installation.ssi:110
-#: en/user_installation.ssi:125 en/user_installation.ssi:140
-#: en/user_managing_a_configuration.ssi:31
-#: en/user_managing_a_configuration.ssi:43
-#: en/user_managing_a_configuration.ssi:52 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:2
-msgid "B~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:4
-msgid "1~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:8
-msgid ""
-"Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A: "
-"See \"Copying USB/HDD image to a USB stick\" % FIXME: <xref linkend="
-"\"image_copying\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:11
-msgid ""
-"Q: How do I log my build? A: You could use script, screen or tee: #{$ "
-"lh_build 2>&1 | tee build.log}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:14
-msgid ""
-"Q: How can I convert an already installed standard Debian partition into a "
-"Debian Live system? A: Save the list of installed packages and load it into "
-"your new Debian Live System. Copy your /etc to config/chroot_local-includes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:17
-msgid ""
-"Q: What does 'losetup: could not find any free loop device' mean and how do "
-"I fix it? A: Loop devices are used during the build; there probably aren't "
-"any free if you've aborted several builds. Something like: for l in /dev/"
-"loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/"
-"loop7 ; do losetup -d $l ; done should rectify the situation (assuming all "
-"loop devices in use were created by lh_build; if in doubt, check the "
-"contents of each loop device before deleting them with losetup -d)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:20
-msgid ""
-"Q: How do I launch an interactive shell during the chroot stage? A: To "
-"enable interactive shell: #{$ lh_config --interactive shell}# To continue "
-"the build process: #{# logout}# or #{# exit}# To disable interactive shell, "
-"set LH_INTERACTIVE to \"disabled\" in config/chroot."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:23
-msgid ""
-"Q: What is the root /user password? A: The user password for the live user "
-"is 'live'. By default, there is not any root password. You can switch to "
-"root with ${sudo -i}# or set a password for root with #{sudo passwd}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:27
-msgid ""
-"Q: How do I change root or any user password? A: Add a chroot local hook "
-"script to change root or any user password each time you build an image. e."
-"g. config/chroot_local-hooks/01-update_password.sh to set root password to "
-"\"nopasswd\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:30 en/other_faq.ssi:53
-msgid "code{ #!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:33
-msgid "echo \"I: update password\" echo \"root:nopasswd\" | chpasswd"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:35
-msgid "$ chmod +x config/chroot_local-hooks/01-update_password.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:39
-msgid ""
-"Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/"
-"live-bottom/10adduser your build folder:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:44
-msgid ""
-"mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-"
-"bottom/ cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/"
-"chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:48
-msgid ""
-"Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/"
-"scripts/live-bottom/10adduser and paste in the new user_crypted password "
-"that you make with: #{echo \"newlivepass\" | mkpasswd -s}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:50
-msgid ""
-"Or add an hook file in config/chroot_local-hooks/ with something like the "
-"below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:57
-msgid ""
-"# Change the autogenerated user password to \"debianlive\" plain_password="
-"\"debianlive\" password=$(echo \"${plain_password}\" | mkpasswd -s)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:59
-msgid ""
-"sed -i -e 's/\\(user_crypted=\\)\\(.*\\)\\( #.*\\)/\\1\\\"'${password}'\\"
-"\"\\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:62
-msgid "update-initramfs -tu -kall }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:64
-msgid ""
-"The latter (hook model) could be more future proof than the former solution "
-"since it modifies just one string selectively but it requires the package "
-"\"whois\" to be installed on the target system (for mkpasswd) or that you "
-"generate the $password string not at build time and include it crypted in "
-"the above script."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:68
-msgid ""
-"Q: How to disable autologin? A1: use the commandline parameter #{lh config --"
-"bootappend-live \"noautologin\"}# A2: You need to set boot=noautologin "
-"noxautologin as described in man live-initramfs If you boot via TFTP you "
-"want to insert the option to pxelinux.cfg/default"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:71
-msgid ""
-"Q: How do I change default hostname or username? A: To change default "
-"hostname or username: #{$ lh_config --hostname myhostname $ lh_config --"
-"username myusername}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:74
-msgid ""
-"Q: How do I make the final image smaller? A: Clean orphaned apps/libs: "
-"Install package \"deborphan\" and then run 'sudo deborphan -n' . Delete "
-"unwanted packages. Remove the apt cache. Purge unwanted locales (see "
-"\"localepurge\" package)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:77
-msgid ""
-"Q: How do I customize bash-config permanently (aliases, bash-completion "
-"etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:81
-msgid ""
-"Q: How do I disable services permanently? (Be careful!) A: Add a chroot "
-"local hook script to disable a service each time you build an image: e.g. "
-"config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:88
-msgid "echo \"I: disable service\" update-rc.d -f service_name remove"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:90
-msgid "$ chmod +x config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:95
-msgid ""
-"Q: How do I enable | disable the md5checksum at the ISO building? A: #"
-"{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:98
-msgid ""
-"Q: How to disable the generation of the .tar.gz file? A: #{lh_config --net-"
-"tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in "
-"snapsshot version at the moment 2008/Feb/28)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:101
-msgid "Q: How do I \"build a new image\"? A: Run commands:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:106
-msgid "$ sudo lh_clean --binary $ sudo lh_build"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:110
-msgid ""
-"Hint: If the configuration had changed you should leave \"--binary\" out. "
-"This will clean your chroot directory too."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:113
-msgid ""
-"Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages "
-"you want."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:115
-msgid "Create /home/$USERNAME/.dmrc file (default username is \"user\")."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:122
-msgid "$ cat .dmrc [Desktop] Session=fluxbox }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:124
-msgid "Note: .dmrc is owned by $USERNAME:$USERNAME."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:126
-msgid ""
-"See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at "
-"http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:129
-msgid ""
-"Q: How do I use custom repositories? A: See http://wiki.debian.org/"
-"DebianLive/Configuration"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:132
-msgid ""
-"Q: How do I customize the artwork for the live CD (grub or syslinux boot "
-"splash, usplash, etc.)? A: See http://wiki.debian.org/DebianLive/Howto/"
-"Custom_Artwork"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:135
-msgid ""
-"Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look? "
-"A: Start the live system in qemu:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:139
-msgid "$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:143
-msgid "Note: the -redir argument must be changed to meet your needs"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:146
-msgid ""
-"Q: How do I execute a custom shell script inside the chroot system after the "
-"chroot stage? A: Add your script in config/chroot_local-hooks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:149
-msgid ""
-"Q: How do I add a script running immediately after all other scripts when "
-"the live system boots? A: Add your script in config/chroot_local-includes/"
-"usr/share/initramfs-tools/scripts/live-bottom/99scrip"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:153
-msgid ""
-"$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/"
-"live-bottom/99script"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:157
-msgid ""
-"Note: The hook script must be executable. Do not forget to lh_clean --chroot "
-"after making this change before you build again."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:159
-msgid ""
-"You must also use the example script /usr/share/live-helper/examples/hooks/"
-"update-initramfs.sh to ensure your script gets built into the initramfs "
-"(read the comment header for instructions)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:163
-msgid ""
-"Q: How do I add software not in Debian ? A: See Customizing package "
-"installation % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:166
-msgid ""
-"Q: What is the manifest with Ubuntu used for? A: Manifest is just the "
-"package list, which ubuntu does $something with. Don't worry about it."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:169
-msgid ""
-"Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:172
-msgid ""
-"Q: Do I need to write the image on USB stick to test it? A: you must use "
-"qemu >= 0.8."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:175
-msgid "Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:178
-msgid ""
-"Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed "
-"something else entirely? A: It is not. It is a package list, not a debconf "
-"preseeding."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:181
-msgid ""
-"Q: What is the difference between standard and minimal? A: standard: "
-"packages of priority standard and higher; minimal: packages of priority "
-"essential and higher;"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:184
-msgid ""
-"Q: What can the sections be used for? Aren't they BIG? A: Someone maybe "
-"wants to include packages from contrib or non-free."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:187
-msgid "Q: memtest86+ ... is that used? A: Yes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:190
-msgid ""
-"Q: How do I build using predefined packages lists? A: e.g. to build using "
-"standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo "
-"lh_build}# Note: The packages lists can be found in /usr/share/live-helper/"
-"lists/ directory."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:193
-msgid ""
-"Q: How do I rebuild without downloading all the packages again? A: All "
-"packages are cached in cache subdirectory. They remain until a clean purge: #"
-"{$ sudo lh_clean --purge}# You do not have to do anything to prevent "
-"packages from being re-downloaded. You need to remember to clean whichever "
-"stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, "
-"chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:196
-msgid ""
-"Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make "
-"a boot CD with grub, configured to boot from a debian-live kernel copied on "
-"the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/"
-"stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/"
-"boot/grub/menu.lst:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:205
-msgid ""
-"default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd) "
-"kernel /boot/vmlinuz boot=live initrd /boot/initrd.img"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:209
-msgid ""
-"Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-"
-"boot \\ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:212
-msgid ""
-"Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A: "
-"If you have a floppy drive, you may be able to use it, otherwise you will "
-"need to use loadlin/grub4dos/win32-loader. If you have a second system to "
-"serve up the image over the network, See http://wiki.debian.org/DebianLive/"
-"Howto/Creating_a_Netboot_Image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:215
-msgid ""
-"Q: The X configuration does not seems to work, the resolution is too low. "
-"What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf "
-"&& lh_config --packages xdebconfigurator}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:218
-msgid ""
-"Q: Apache has problems with static files A: Sendfile does not work well on "
-"the unionfs used by Debian Live. Add the following to apache's "
-"configuration: #{EnableSendfile off}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:222
-msgid ""
-"Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right "
-"now the best is to use a script that will populate the fstab when the CD is "
-"booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/"
-"trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper "
-"solution based on HAL will be described here in a hopefully near future. A: "
-"Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-"
-"policy-fixed-drives.fdi is not available anymore and the previous trick that "
-"consisted to remove this file to enable automounting of fixed drives as a "
-"consequence is obsolete. Eventually, it will be possible to combine HAL and "
-"PolicyKit to enable different permissions and actions to achieve advanced "
-"(auto)mounting for non-root users. Until then, because the live scripts are "
-"only touching to the fstab to add a swap partition if discovered at boot "
-"time, the only way to have fixed drives mounted automatically is to use a "
-"script that will populate the fstab file at the end of the multiuser "
-"runlevel. To achieve this, you can do, for example, the following: download "
-"the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-"
-"includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin "
-"directory, and move the script inside Make sure the script is executable "
-"(chmod +x diskmounter.sh) create the chroot_local-includes/etc/rc.local file "
-"and call the diskmounter from there (see this https://devel.goto10.org/svn/"
-"puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called "
-"correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and "
-"NTFS partitions and mount them read-write, except for NTFS. This will change "
-"soon and an option will be available to use ntfs-3g to mount NTFS as read-"
-"write. comments, patches and other things about this script and issue: "
-"http://code.goto10.org/projects/puredyne/ticket/463"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:225
-msgid ""
-"Q: Boot fails with panic: can't open /scripts/live A: Add latest live-"
-"initramfs deb package into config/chroot_local-packages directory and "
-"rebuild."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:229
-msgid ""
-"Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref "
-"linkend=\"internalization\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:234
-msgid ""
-"Q: How do I get past boot prompt without a working keyboard? A: See "
-"Customizing the bootup process % FIXME: <xref linkend=\"bootup\"/> Note: "
-"Boot from an USB-HDD on an iMac with GRUB did not work."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:237
-msgid ""
-"Q: Can I serve the root image from a web or ftp server? A: Since live-"
-"initramfs 1.99, it should be possible to use the fetch= argument on the "
-"kernel command line. You can build a netboot image as usual, and when you "
-"are done edit the tftpboot/pxelinux.cfg/default file. Remove the references "
-"to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url "
-"where you placed the root image>. You have to include wget in the chroot. It "
-"could work for other boot methods as well. However, I am not sure the live "
-"scripts configure the network when booting from a CD or USB disk. #{$ "
-"lh_config --packages wget}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:240
-msgid ""
-"Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you "
-"are building an etch image (which was the default up to 2007/09/14) you have "
-"a very old version of casper which does not support quickreboot and possibly "
-"other boot parameters as well. You could configure your sources to use live-"
-"backports (see /usr/share/live-helper/examples/sources/live-backports) and "
-"switch to live-initramfs, or better yet, build a lenny image instead, which "
-"is the new default. #{$ lh_config --distribution lenny $ lh_config --"
-"initramfs live-initramfs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:243
-msgid ""
-"Q: How do I fix \"Could not find kernel image\" issue with syslinux "
-"bootloader? A: Add a binary local hook script to fix kernel and initrd path "
-"each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux."
-"sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:249
-msgid "SYSLINUXCFG=`find binary -type f -name syslinux.cfg`"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:252
-msgid ""
-"sed -i \"s|kernel /vmlinuz|kernel vmlinuz|g\" ${SYSLINUXCFG} sed -i \"s|"
-"initrd=/initrd|initrd=initrd|g\" ${SYSLINUXCFG}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:254
-msgid "$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:259
-msgid ""
-"Q: How do I use a newer kernel with lenny? A: A build with backports.org "
-"kernels will fail as that repository lacks the necessary module packages "
-"(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://"
-"unsupported.debian-maintainers.org/backports-kernel/ The quick way to "
-"success:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:268
-msgid ""
-"$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-"
-"modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-"
-"kernel/ ./' > config/chroot_sources/backports-kernel.chroot $ echo 'deb "
-"http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/"
-"chroot_sources/backports-kernel.binary $ wget http://unsupported.debian-"
-"maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/"
-"backports-kernel.chroot.gpg $ wget http://unsupported.debian-maintainers.org/"
-"backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel."
-"binary.gpg $ lh_build }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:271
-msgid ""
-"Q: How do I use a custom kernel? Is there a nice way of booting debian-live "
-"with a custom kernel (not in an apt repo)? A: Copy it into config/"
-"chroot_local-packages and set LH_LINUX_PACKAGES=\"none\" or use lh config --"
-"linux-packages \" \" Don't forget to compile your kernel with an union "
-"filesystem (unionfs or aufs), squashfs modules, and initrd support. I can "
-"cause the kernel to be installed but it seems this happens later than grub/"
-"syslinux is configured so it's not listed and casper/ and the menu require "
-"munging. You need to follow the debian scheme, e.g. placing the files in /"
-"boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't "
-"go that way which is too much of a hassle, and just use make-kpkg to produce "
-"custom kernel deb packages. They should integrate nicely if you just put "
-"them into config/chroot_local-packages and set LH_LINUX_PACKAGES=\"\". Hint: "
-"to work around an error, which lh_binary_syslinux will throw on custom "
-"kernels if there is not an 468/686 in the kernel-name, you need to set "
-"CONFIG_LOCALVERSION=\"-486\" or \"-686\" within the kernel configuration (-"
-"> General setup -> Local version set to -486 or -686) corresponding to "
-"LH_LINUX_FLAVOURS=\"\" or \"686\". this at least up till live-helper version "
-"1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-"
-"devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/"
-"debian-live-devel/2007-November/002581.html"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:274
-msgid ""
-"Q: How do I create a cross arch live CD image? A: In short: You can't. Read "
-"on: The procedure to create a live CD is based on creating a chroot that "
-"contains the files that will be finally available on the live CD. The live "
-"CD building procedure includes chrooting into the chroot dir and so some "
-"operations. chrooting means that the terminal you chroot on will behave as a "
-"different system so your real system and the chroot environment is decoupled "
-"somehow. Once the live CD scripts chroots into the chroot dir they have some "
-"operations to do inside that environment and your real system won't be able "
-"to run them unless you are using the same architecture. So you only are able "
-"to make live CD for the arch you run on. But this doesn't prevent you run "
-"qemu or some other machine emulator that make this possible."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:277
-msgid ""
-"Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That "
-"depends what you've changed between builds If, for example, you've built an "
-"iso image and you want a usb image, you only need to run #{lh_clean --binary}"
-"# before you run lh_build again. If you've changed anything in the chroot, "
-"you'll need to cleanup both chroot and binary with #{lh_clean}# before "
-"continuing"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:280
-msgid ""
-"Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in config/binary"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:283
-msgid ""
-"Q: How do I include different modules to load when the live system boots? A: "
-"Configure config/chroot_local-includes/etc/initramfs-tools/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:285
-msgid ""
-"The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default "
-"initramfs.conf \"MODULES = most\". You may override that by supplying your "
-"own initramfs.conf, or else just add your own modules, e.g."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:290
-msgid ""
-"mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo \"atl2\" >> "
-"config/chroot_local-includes/etc/initramfs-tools/modules"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:294
-msgid ""
-"Note: Even though initramfs.conf(5) says \"most adds all the framebuffer, "
-"acpi, file system, ide, sata, scsi and usb drivers\", it actually includes "
-"network drivers as well. See auto_add_modules() in /usr/share/initramfs-"
-"tools/hook-functions for the complete list."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:297
-msgid ""
-"Q: Can I have a splash screen? A: Yes you can. You will not know what is "
-"going on when the splash screen is active, it may fail to activate on some "
-"hardware or break X on other (both usplash and splashy use libdirectfb which "
-"does some evil voodoo and may break you graphics or input until you reboot). "
-"However, you can install and activate it just as you would on any other "
-"Debian system. To use splashy: 1. install splashy and read the README, the "
-"manpages are useless for setting it up. Add some parameters to your kernel "
-"command line, such as in your pxelinux configuration or in "
-"LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 "
-"splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, "
-"#{quiet}# to suppress most kernel messages that you cannot see anyway but "
-"would scroll past before splashy manages to paint the graphics on your "
-"screen. You might want to add splashy to the list of packages installed in "
-"your image: #{echo splashy > config/chroot_local-packageslists/splashy echo "
-"splashy-themes >> config/chroot_local-packageslists/splashy}# and select a "
-"theme:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:305
-msgid ""
-"echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s "
-"debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the "
-"ramdisk to include the splash screen echo update-initramfs -u -k all >> "
-"config/chroot_local-hooks/splashy chmod 755 config/chroot_local-hooks/splashy"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:309
-msgid ""
-"After you rebuild your live system you should observe a bluish splash screen "
-"while booting. Nothing happens while initramfs is running because there is "
-"no splashy support in initramfs-tools. Once the init starts the progress bar "
-"should start to fill. If #{vga=something}# sets a mode that your screen "
-"cannot show or your card cannot do vesa 2.0 (and thus you get plain text "
-"mode and no splashy) read the splashy faq."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:312
-msgid ""
-"Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the "
-"firmwares to the initrd image. You need to install the non-free package "
-"\"firmware-bnx2\". Uncompress your initrd image, then copy files:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:317
-msgid ""
-"cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /"
-"lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw "
-"${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:321
-msgid "Recompress your initrd image and boot: it works!"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:323
-msgid ""
-"Q: X is broken (the system boots, messages scroll by, and then the screen "
-"goes blank). What do I do? A: On my system starting X completely disables "
-"graphics so that I do not see anything even after X bails out and I am back "
-"to the console. To prevent this you can change the driver Xorg uses."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:325
-msgid ""
-"If you have a working splash screen or at least graphical console you can "
-"use #{live xdriver=fbdev}# when booting the live system (instead of just "
-"enter). Another driver you might want to try is #{vesa}#. If all fails you "
-"might try to set xdriver to some wrong value so that Xorg fails to start and "
-"you can examine the system while you still see something on the console. #"
-"{live xdriver=none}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:328
-msgid ""
-"Q: How can I get Debian first stable versions? A: I'm developing software "
-"and testing it on Live-CD. Thanks for the LiveCD project. To be sure my "
-"development is fully compatible with the \"etch\" version, I need the same "
-"scenario when Debian GNU/Linux 4.0 was published as stable (I believe "
-"2007.04.08). If there was some bug on 2007.04.08 that was corrected one week "
-"later, I need to test software foreseeing that scenario without the bug "
-"solved."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:331
-msgid ""
-"Q: I get \"fopen: Permission denied\"-warnings from apt on building/at the "
-"live-system A: That's a harmless bug in apt. However, if you want to get off "
-"this warnings in the live-system, add a file in chroot_local-hooks with "
-"follow row:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:335
-msgid "chown -R man.man /var/cache/man"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:340
-msgid ""
-"Q: Why I always fail during \"Retrieving Packages\" stage when running "
-"lh_build? I have already set apt-http-proxy and so on. A: lh_build "
-"retrieves packages via wget, as a result you need to enable the proxy "
-"settings in /etc/wgetrc before running lh_build."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:343
-msgid ""
-"Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system "
-"boots, so it's useless to put modifed Xorg.conf in config/choort_local-"
-"includes/etc/X11, because it will be overwritten during boot. However, you "
-"can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the "
-"result will be modified Xorg.conf. The modified dexconf has to be put in "
-"config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for "
-"two or more keyboards layouts with alt+shift toggle by editing dexconf and "
-"replacing the line:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:347
-msgid "Option \"XkbLayout\" \"$XKB_LAYOUT\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:351
-msgid "with the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:356
-msgid ""
-"Option \"XkbLayout\" \"us,il\" Option \"XkbOptions\" \"grp:alt_shift_toggle,"
-"grp_led:scroll\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:360
-msgid "when \"us,il\" are the wanted keyboard layouts."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:362
-msgid ""
-"You can force default screen resulotion (e.g. 1024*768) by adding the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:368
-#, no-wrap
-msgid ""
-"SubSection \"Display\"\n"
-" Modes \"1024x768\"\n"
-"EndSubSection\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:372
-msgid "between the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:379
-#, no-wrap
-msgid ""
-"Section \"Screen\"\n"
-" Identifier \"Default Screen\"\n"
-" Monitor \"Configured Monitor\"\n"
-"EndSection\"\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:383
-msgid ""
-"Q: Where are the build parameters for the prebuilt images A: See http://live."
-"debian.net/README.images."
-msgstr ""
diff --git a/manual/po/pt_BR/other_howtos.ssi.po b/manual/po/pt_BR/other_howtos.ssi.po
deleted file mode 100644
index f5530e9..0000000
--- a/manual/po/pt_BR/other_howtos.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# Portuguese translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: pt_BR\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n > 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_howtos.ssi:2
-msgid "B~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:4
-msgid "1~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:6
-msgid "2~ ISO"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:8
-msgid ""
-"Generating a Debian Live CD is very simple. You need to have live-helper "
-"(package available in Debian sid and lenny), and Debootstrap (or "
-"cdebootstrap) from etch or newer."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:10
-msgid "3~ Install live-helper"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:12
-msgid "#{apt-get install live-helper}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:14
-msgid "3~ Configure the current working directory with lh_config"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:18
-msgid "lh_config -b iso -a $ARCH"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:22
-msgid "where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:24
-msgid "#{-b}# flag is used to be sure to obtain image in ISO format."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:26
-msgid "3~ Build the image with lh_build:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:28
-msgid "Execute lh_build as root: #{lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:30
-msgid ""
-"The command above will create the basic image, containing just the Debian "
-"standard system (with no X at all)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:32
-msgid ""
-"If you want to have any of the Desktop environments on your livecd, #{ls /"
-"usr/share/live-helper/lists}# will show a number of available package Lists "
-"to choose from, e.g. #{lh_config -p gnome-desktop}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:34
-msgid "More examples are listed at DebianLive/Examples."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:37
-msgid ""
-"See packages for help configuring a local Debian Mirror and other aspects of "
-"the live system. % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:39
-msgid "3~ Test the image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:41
-msgid "If you have qemu installed, you can boot the image with:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:45
-msgid "qemu -cdrom binary.iso"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:49
-msgid "If you have also kqemu installed, you can add #{-kernel-kqemu}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:51
-msgid "2~ ISO_(multiarch)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:53
-msgid ""
-"Multiple machine boot CDs can be created with the following manual "
-"procedure. This procedure has been successfully used to create a single CD "
-"which is bootable on alpha, i386, pmax, and sparc. It should be possible to "
-"also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:55
-msgid ""
-"To create a CD which is bootable by multiple architectures, use the "
-"following steps in this order. Please note that the order is critical."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:57
-msgid ""
-"Make sure you have all the required files including the various kernels and "
-"boot programs listed in the individual machine sections."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:59
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.pmax "
-"and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/"
-"mdec.pmax/bootxx_cd9660."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:61
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.vax and "
-"include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/"
-"xxboot.}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:63
-msgid "Include the macppc ofwboot.xcf bootloader in /cdsources."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:65
-msgid ""
-"Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/"
-"installation/floppy/boot-big.fs \\ -c boot.catalog -l -J -r -L /cdsources "
-"2>&1 | tee /tmp/mkisofs.log exit}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:67
-msgid ""
-"Note: The appearance of the -v flag twice is required. If you are making a "
-"bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -"
-"part in the parameters for mkisofs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:69
-msgid ""
-"Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 "
-"bootblocks. Alternatively, install the sysutils/mksunbootcd package on your "
-"favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs "
-"boot-sun4m.fs boot-sun3.fs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:71
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/pmax to install the pmax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"pmax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:73
-msgid ""
-"#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:75
-msgid ""
-"The -o append,sunsum option appends the first stage boot block to the end of "
-"the ISO file system, and restores the checksum used when booting on a sun."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:77
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/vax to install the vax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"vax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:79
-msgid "installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:81
-msgid "(See the pmax entry above for an explanation of the flags)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:83
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/alpha to install the "
-"alpha bootblocks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:85
-msgid ""
-"#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:86
-msgid ""
-"Note: The alpha installboot must occur after the others, because currently "
-"it's the only machine dependent back-end for installboot(8) that can "
-"calculate the alpha checksum. (See the pmax entry above for an explanation "
-"of the flags)."
-msgstr ""
diff --git a/manual/po/pt_BR/other_use-cases.ssi.po b/manual/po/pt_BR/other_use-cases.ssi.po
deleted file mode 100644
index f387b0c..0000000
--- a/manual/po/pt_BR/other_use-cases.ssi.po
+++ /dev/null
@@ -1,379 +0,0 @@
-# Portuguese translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: pt_BR\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=2; plural=(n > 1);\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:2
-msgid "B~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:4
-msgid "1~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:6
-msgid "This chapter is for users to document their use cases with Debian Live."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:8
-msgid "2~ VNC Kiosk Client"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:10
-msgid "Create an image with live-helper to boot directly to a VNC server."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:12
-msgid "_* Make a build directory: #{$ mkdir vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:14
-msgid "_* Move to the build directory: #{$ cd vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:16
-msgid ""
-"Example to config the build directory to include gdm metacity "
-"xtightvncviewer: #{$ lh config --packages \"gdm metacity xtightvncviewer\"}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:18
-msgid ""
-"Create a folder /etc/skel folder for a custom .xsession for the default "
-"user: #{$ mkdir -p config/chroot_local-includes/etc/skel}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:20
-msgid ""
-"Create the .xsession for the default user: #{$ touch config/chroot_local-"
-"includes/etc/skel/.xsession}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:22
-msgid ""
-"Edit the .xsession file to launch metacity and start xvncviewer with "
-"something similar to the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:29
-msgid "/usr/bin/metacity & /usr/bin/vncviewer xxx.xxx.xxx.xxx:PORT"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:31
-msgid "exit"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:35
-msgid "_* Build the image: #{# lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:37 en/other_use-cases.ssi:138
-msgid "_* Enjoy."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:39
-msgid "2~ VMWare-Player Sessions"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:41
-msgid ""
-"Create an image with live-helper to boot directly to a specifiv VMWare "
-"session."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:43
-msgid "_* Make a build directory: #{$ mkdir VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:45
-msgid "_* Move to the build directory: #{$ cd VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:47
-msgid ""
-"_* Example to config the build directory to include gdm metacity "
-"xtightvncviewer:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:67
-#, no-wrap
-msgid ""
-"$ lh config --apt apt \\\n"
-" ---apt-recommends disabled \\\n"
-" --archive-areas \"main\" \\\n"
-" --binary-images iso \\\n"
-" --binary-indices none \\\n"
-" --syslinux-menu vesamenu \\\n"
-" ---bootappend-live \"persistent quickreboot\" \\\n"
-" ---bootappend-install \"-- plainroot persistent video=vesa:ywrap,mtrr vga=788 quickreboot quiet live-config\" \\\n"
-" ---debian-installer live \\\n"
-" ---distribution lenny \\\n"
-" ---hostname vmare-player-firmware \\\n"
-" ---includes none \\\n"
-" ---linux-flavours 686 \\\n"
-" ---packages-lists \"gnome-core\" \\\n"
-" ---packages \"gcc gparted linux-headers-2.6-\\${LH_LINUX_FLAVOURS} live-config-staging make metacity rsync wireless-tools\" \\\n"
-" ---repositories live.debian.net \\\n"
-" ---win32-loader disabled\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:71
-msgid ""
-"_* Create the 01-vmware-player hook: #{$ touch config/chroot_local-hooks/01-"
-"vmware-player.sh}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:73
-msgid ""
-"Edit the 01-vmware-player hook to launch the VMWare-Player. The hook should "
-"look something like the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:80
-msgid ""
-"_URL=\"http://archive.debian-maintainers.org/vmware/other/vmware-player/\" "
-"_VMPLAYER_VERSION=\"VMware-Player.i386.bundle\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:83
-msgid "echo \"I: Starting script for install of VMWare Player.\" cd /root"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:86
-msgid ""
-"echo \"I: Beginning download of ${_VMPLAYER_VERSION} from ${_URL} .\" wget "
-"${_URL}${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:89
-msgid ""
-"echo \"I: Starting install of VMWare Player.\" sh /root/${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:92
-msgid ""
-"echo \"I: Cleaning up the VMWare Player download.\" rm /root/"
-"${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:95
-msgid "#echo \"I: Starting interactive shell.\" #bash"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:99
-msgid ""
-"_* Build the image (note that during the build the VMWare-Player will prompt "
-"you to install or cancel): #{#lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:101
-msgid ""
-"_* After the build you will have an image you can boot live or install as "
-"firmware. The package live-config-staging is the package that installs the "
-"ability to utilize the VMWare-Player by calling live-config.vmware-player as "
-"a boot parameter in the following form:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:105
-msgid "live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:109
-msgid "Notes from the 900-vmware-player file are as follows:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:135
-#, no-wrap
-msgid ""
-"# The script tests for boot parameter of\n"
-"# live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME\n"
-"#\n"
-"# ACTION: The operation to perform on the workstation (none|scratch)\n"
-"# IMAGEPATH: The folder path to the VMware image you want to run.\n"
-"# VMXNAME: The name of the VMware image you want to run.\n"
-"#\n"
-"# Notes:To use this file with WMWare images you will need to have a few things\n"
-"# setup:\n"
-"#\n"
-"# 1. The VMware Player needs to be installed in the image.\n"
-"# 2. This script uses (s|h)da1 for writing image data, and is used as a scratch\n"
-"# space. This scratch space should be a file system with linux permissions\n"
-"# such as ext2.\n"
-"# 3. VMware image(s) should be in a mounted folder and setup as follows:\n"
-"# - Image(s) set to snapshot mode.\n"
-"# - For each image, the image folder needs to have a file called\n"
-"# image-release with a variable CRELEASE. An example: CRELEASE=\"1.0.0\"\n"
-"#\n"
-"# The image-release file is used by the image maintainer and this script to tell\n"
-"# workstation(s) using a given image, to erase locally stored vmware image files\n"
-"# and setup with the newly configure image. The operation of erasing locally\n"
-"# stored vmare image files, is referred to as a scratch.\n"
-msgstr ""
diff --git a/manual/po/pt_BR/user_examples.ssi.po b/manual/po/pt_BR/user_examples.ssi.po
index bf485f7..aa75571 100644
--- a/manual/po/pt_BR/user_examples.ssi.po
+++ b/manual/po/pt_BR/user_examples.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:57-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-11-04 16:34-0400\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,13 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/other_faq.ssi:41 en/other_faq.ssi:83
-#: en/other_faq.ssi:103 en/other_faq.ssi:117 en/other_faq.ssi:137
-#: en/other_faq.ssi:151 en/other_faq.ssi:198 en/other_faq.ssi:245
-#: en/other_faq.ssi:261 en/other_faq.ssi:287 en/other_faq.ssi:299
-#: en/other_faq.ssi:314 en/other_faq.ssi:333 en/other_faq.ssi:345
-#: en/other_faq.ssi:353 en/other_faq.ssi:364 en/other_faq.ssi:374
-#: en/other_howtos.ssi:16 en/other_howtos.ssi:43 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:58
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -87,13 +81,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/other_faq.ssi:37 en/other_faq.ssi:46
-#: en/other_faq.ssi:92 en/other_faq.ssi:108 en/other_faq.ssi:141
-#: en/other_faq.ssi:155 en/other_faq.ssi:207 en/other_faq.ssi:256
-#: en/other_faq.ssi:292 en/other_faq.ssi:307 en/other_faq.ssi:319
-#: en/other_faq.ssi:337 en/other_faq.ssi:349 en/other_faq.ssi:358
-#: en/other_faq.ssi:370 en/other_faq.ssi:381 en/other_howtos.ssi:20
-#: en/other_howtos.ssi:47 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:62
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -150,12 +138,6 @@ msgid "}code"
msgstr "}code"
#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/user_examples.ssi:92
-#: en/user_examples.ssi:141 en/user_examples.ssi:190
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
#: en/user_basics.ssi:44 en/user_basics.ssi:120 en/user_basics.ssi:204
#: en/user_examples.ssi:109 en/user_examples.ssi:156
msgid "# lb build"
@@ -360,6 +342,11 @@ msgid "Edit #{auto/config}# to read as follows:"
msgstr ""
#. type: Plain text
+#: en/user_examples.ssi:92 en/user_examples.ssi:141 en/user_examples.ssi:190
+msgid "#!/bin/sh"
+msgstr ""
+
+#. type: Plain text
#: en/user_examples.ssi:99
#, no-wrap
msgid ""
diff --git a/manual/po/ro/live-manual.ssm.po b/manual/po/ro/live-manual.ssm.po
index 4905a46..264af13 100644
--- a/manual/po/ro/live-manual.ssm.po
+++ b/manual/po/ro/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:18-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-10-23 00:04+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -174,13 +174,3 @@ msgstr ""
#: en/live-manual.ssm:65
msgid "<< user_examples.ssi"
msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:67
-msgid "% << other_faq.ssi"
-msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:68
-msgid "% << other_howtos.ssi"
-msgstr ""
diff --git a/manual/po/ro/other_faq.ssi.po b/manual/po/ro/other_faq.ssi.po
deleted file mode 100644
index 01cde86..0000000
--- a/manual/po/ro/other_faq.ssi.po
+++ /dev/null
@@ -1,1009 +0,0 @@
-# Romanian translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-16 14:45-0200\n"
-"PO-Revision-Date: 2010-10-16 14:45-0200\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: ro\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=3; plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < "
-"20)) ? 1 : 2;\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:83 en/about_manual.ssi:91 en/about_manual.ssi:99
-#: en/about_manual.ssi:111 en/about_manual.ssi:124 en/about_manual.ssi:137
-#: en/about_manual.ssi:145 en/about_manual.ssi:153 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_faq.ssi:41 en/other_faq.ssi:83 en/other_faq.ssi:103
-#: en/other_faq.ssi:117 en/other_faq.ssi:137 en/other_faq.ssi:151
-#: en/other_faq.ssi:198 en/other_faq.ssi:245 en/other_faq.ssi:261
-#: en/other_faq.ssi:287 en/other_faq.ssi:299 en/other_faq.ssi:314
-#: en/other_faq.ssi:333 en/other_faq.ssi:345 en/other_faq.ssi:353
-#: en/other_faq.ssi:364 en/other_faq.ssi:374 en/other_howtos.ssi:16
-#: en/other_howtos.ssi:43 en/other_live-environment.ssi:14
-#: en/other_live-environment.ssi:30 en/other_live-environment.ssi:51
-#: en/other_live-environment.ssi:61 en/other_live-environment.ssi:69
-#: en/other_live-environment.ssi:77 en/other_live-environment.ssi:85
-#: en/other_live-environment.ssi:93 en/other_live-environment.ssi:116
-#: en/other_live-environment.ssi:124 en/other_live-environment.ssi:133
-#: en/other_procedures.ssi:12 en/other_procedures.ssi:46
-#: en/other_procedures.ssi:58 en/other_use-cases.ssi:24
-#: en/other_use-cases.ssi:49 en/other_use-cases.ssi:75
-#: en/other_use-cases.ssi:103 en/other_use-cases.ssi:111 en/user_basics.ssi:36
-#: en/user_basics.ssi:48 en/user_basics.ssi:62 en/user_basics.ssi:74
-#: en/user_basics.ssi:86 en/user_basics.ssi:98 en/user_basics.ssi:114
-#: en/user_basics.ssi:122 en/user_basics.ssi:130 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:180 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:212 en/user_basics.ssi:232 en/user_basics.ssi:265
-#: en/user_basics.ssi:281 en/user_basics.ssi:289 en/user_basics.ssi:309
-#: en/user_basics.ssi:334 en/user_customization-contents.ssi:34
-#: en/user_customization-contents.ssi:43 en/user_customization-contents.ssi:66
-#: en/user_customization-internationalization.ssi:10
-#: en/user_customization-internationalization.ssi:18
-#: en/user_customization-internationalization.ssi:26
-#: en/user_customization-internationalization.ssi:38
-#: en/user_customization-packages.ssi:16 en/user_customization-packages.ssi:24
-#: en/user_customization-packages.ssi:36 en/user_customization-packages.ssi:45
-#: en/user_customization-packages.ssi:59 en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:106
-#: en/user_installation.ssi:120 en/user_installation.ssi:137
-#: en/user_managing_a_configuration.ssi:24
-#: en/user_managing_a_configuration.ssi:35
-#: en/user_managing_a_configuration.ssi:47 en/user_overview.ssi:60
-#: en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:87 en/about_manual.ssi:95 en/about_manual.ssi:103
-#: en/about_manual.ssi:120 en/about_manual.ssi:133 en/about_manual.ssi:141
-#: en/about_manual.ssi:149 en/about_manual.ssi:157 en/about_manual.ssi:164
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_faq.ssi:37 en/other_faq.ssi:46 en/other_faq.ssi:92
-#: en/other_faq.ssi:108 en/other_faq.ssi:141 en/other_faq.ssi:155
-#: en/other_faq.ssi:207 en/other_faq.ssi:256 en/other_faq.ssi:292
-#: en/other_faq.ssi:307 en/other_faq.ssi:319 en/other_faq.ssi:337
-#: en/other_faq.ssi:349 en/other_faq.ssi:358 en/other_faq.ssi:370
-#: en/other_faq.ssi:381 en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:92
-#: en/user_basics.ssi:104 en/user_basics.ssi:118 en/user_basics.ssi:126
-#: en/user_basics.ssi:134 en/user_basics.ssi:144 en/user_basics.ssi:158
-#: en/user_basics.ssi:168 en/user_basics.ssi:176 en/user_basics.ssi:184
-#: en/user_basics.ssi:198 en/user_basics.ssi:206 en/user_basics.ssi:216
-#: en/user_basics.ssi:257 en/user_basics.ssi:285 en/user_basics.ssi:293
-#: en/user_basics.ssi:320 en/user_basics.ssi:359
-#: en/user_customization-contents.ssi:39 en/user_customization-contents.ssi:54
-#: en/user_customization-contents.ssi:70
-#: en/user_customization-internationalization.ssi:14
-#: en/user_customization-internationalization.ssi:22
-#: en/user_customization-internationalization.ssi:30
-#: en/user_customization-internationalization.ssi:42
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:172
-#: en/user_customization-packages.ssi:182
-#: en/user_customization-packages.ssi:192
-#: en/user_customization-packages.ssi:202 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:88 en/user_installation.ssi:110
-#: en/user_installation.ssi:125 en/user_installation.ssi:140
-#: en/user_managing_a_configuration.ssi:31
-#: en/user_managing_a_configuration.ssi:43
-#: en/user_managing_a_configuration.ssi:52 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:2
-msgid "B~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:4
-msgid "1~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:8
-msgid ""
-"Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A: "
-"See \"Copying USB/HDD image to a USB stick\" % FIXME: <xref linkend="
-"\"image_copying\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:11
-msgid ""
-"Q: How do I log my build? A: You could use script, screen or tee: #{$ "
-"lh_build 2>&1 | tee build.log}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:14
-msgid ""
-"Q: How can I convert an already installed standard Debian partition into a "
-"Debian Live system? A: Save the list of installed packages and load it into "
-"your new Debian Live System. Copy your /etc to config/chroot_local-includes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:17
-msgid ""
-"Q: What does 'losetup: could not find any free loop device' mean and how do "
-"I fix it? A: Loop devices are used during the build; there probably aren't "
-"any free if you've aborted several builds. Something like: for l in /dev/"
-"loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/"
-"loop7 ; do losetup -d $l ; done should rectify the situation (assuming all "
-"loop devices in use were created by lh_build; if in doubt, check the "
-"contents of each loop device before deleting them with losetup -d)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:20
-msgid ""
-"Q: How do I launch an interactive shell during the chroot stage? A: To "
-"enable interactive shell: #{$ lh_config --interactive shell}# To continue "
-"the build process: #{# logout}# or #{# exit}# To disable interactive shell, "
-"set LH_INTERACTIVE to \"disabled\" in config/chroot."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:23
-msgid ""
-"Q: What is the root /user password? A: The user password for the live user "
-"is 'live'. By default, there is not any root password. You can switch to "
-"root with ${sudo -i}# or set a password for root with #{sudo passwd}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:27
-msgid ""
-"Q: How do I change root or any user password? A: Add a chroot local hook "
-"script to change root or any user password each time you build an image. e."
-"g. config/chroot_local-hooks/01-update_password.sh to set root password to "
-"\"nopasswd\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:30 en/other_faq.ssi:53
-msgid "code{ #!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:33
-msgid "echo \"I: update password\" echo \"root:nopasswd\" | chpasswd"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:35
-msgid "$ chmod +x config/chroot_local-hooks/01-update_password.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:39
-msgid ""
-"Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/"
-"live-bottom/10adduser your build folder:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:44
-msgid ""
-"mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-"
-"bottom/ cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/"
-"chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:48
-msgid ""
-"Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/"
-"scripts/live-bottom/10adduser and paste in the new user_crypted password "
-"that you make with: #{echo \"newlivepass\" | mkpasswd -s}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:50
-msgid ""
-"Or add an hook file in config/chroot_local-hooks/ with something like the "
-"below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:57
-msgid ""
-"# Change the autogenerated user password to \"debianlive\" plain_password="
-"\"debianlive\" password=$(echo \"${plain_password}\" | mkpasswd -s)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:59
-msgid ""
-"sed -i -e 's/\\(user_crypted=\\)\\(.*\\)\\( #.*\\)/\\1\\\"'${password}'\\"
-"\"\\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:62
-msgid "update-initramfs -tu -kall }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:64
-msgid ""
-"The latter (hook model) could be more future proof than the former solution "
-"since it modifies just one string selectively but it requires the package "
-"\"whois\" to be installed on the target system (for mkpasswd) or that you "
-"generate the $password string not at build time and include it crypted in "
-"the above script."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:68
-msgid ""
-"Q: How to disable autologin? A1: use the commandline parameter #{lh config --"
-"bootappend-live \"noautologin\"}# A2: You need to set boot=noautologin "
-"noxautologin as described in man live-initramfs If you boot via TFTP you "
-"want to insert the option to pxelinux.cfg/default"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:71
-msgid ""
-"Q: How do I change default hostname or username? A: To change default "
-"hostname or username: #{$ lh_config --hostname myhostname $ lh_config --"
-"username myusername}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:74
-msgid ""
-"Q: How do I make the final image smaller? A: Clean orphaned apps/libs: "
-"Install package \"deborphan\" and then run 'sudo deborphan -n' . Delete "
-"unwanted packages. Remove the apt cache. Purge unwanted locales (see "
-"\"localepurge\" package)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:77
-msgid ""
-"Q: How do I customize bash-config permanently (aliases, bash-completion "
-"etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:81
-msgid ""
-"Q: How do I disable services permanently? (Be careful!) A: Add a chroot "
-"local hook script to disable a service each time you build an image: e.g. "
-"config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:88
-msgid "echo \"I: disable service\" update-rc.d -f service_name remove"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:90
-msgid "$ chmod +x config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:95
-msgid ""
-"Q: How do I enable | disable the md5checksum at the ISO building? A: #"
-"{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:98
-msgid ""
-"Q: How to disable the generation of the .tar.gz file? A: #{lh_config --net-"
-"tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in "
-"snapsshot version at the moment 2008/Feb/28)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:101
-msgid "Q: How do I \"build a new image\"? A: Run commands:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:106
-msgid "$ sudo lh_clean --binary $ sudo lh_build"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:110
-msgid ""
-"Hint: If the configuration had changed you should leave \"--binary\" out. "
-"This will clean your chroot directory too."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:113
-msgid ""
-"Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages "
-"you want."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:115
-msgid "Create /home/$USERNAME/.dmrc file (default username is \"user\")."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:122
-msgid "$ cat .dmrc [Desktop] Session=fluxbox }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:124
-msgid "Note: .dmrc is owned by $USERNAME:$USERNAME."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:126
-msgid ""
-"See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at "
-"http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:129
-msgid ""
-"Q: How do I use custom repositories? A: See http://wiki.debian.org/"
-"DebianLive/Configuration"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:132
-msgid ""
-"Q: How do I customize the artwork for the live CD (grub or syslinux boot "
-"splash, usplash, etc.)? A: See http://wiki.debian.org/DebianLive/Howto/"
-"Custom_Artwork"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:135
-msgid ""
-"Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look? "
-"A: Start the live system in qemu:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:139
-msgid "$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:143
-msgid "Note: the -redir argument must be changed to meet your needs"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:146
-msgid ""
-"Q: How do I execute a custom shell script inside the chroot system after the "
-"chroot stage? A: Add your script in config/chroot_local-hooks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:149
-msgid ""
-"Q: How do I add a script running immediately after all other scripts when "
-"the live system boots? A: Add your script in config/chroot_local-includes/"
-"usr/share/initramfs-tools/scripts/live-bottom/99scrip"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:153
-msgid ""
-"$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/"
-"live-bottom/99script"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:157
-msgid ""
-"Note: The hook script must be executable. Do not forget to lh_clean --chroot "
-"after making this change before you build again."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:159
-msgid ""
-"You must also use the example script /usr/share/live-helper/examples/hooks/"
-"update-initramfs.sh to ensure your script gets built into the initramfs "
-"(read the comment header for instructions)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:163
-msgid ""
-"Q: How do I add software not in Debian ? A: See Customizing package "
-"installation % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:166
-msgid ""
-"Q: What is the manifest with Ubuntu used for? A: Manifest is just the "
-"package list, which ubuntu does $something with. Don't worry about it."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:169
-msgid ""
-"Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:172
-msgid ""
-"Q: Do I need to write the image on USB stick to test it? A: you must use "
-"qemu >= 0.8."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:175
-msgid "Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:178
-msgid ""
-"Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed "
-"something else entirely? A: It is not. It is a package list, not a debconf "
-"preseeding."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:181
-msgid ""
-"Q: What is the difference between standard and minimal? A: standard: "
-"packages of priority standard and higher; minimal: packages of priority "
-"essential and higher;"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:184
-msgid ""
-"Q: What can the sections be used for? Aren't they BIG? A: Someone maybe "
-"wants to include packages from contrib or non-free."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:187
-msgid "Q: memtest86+ ... is that used? A: Yes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:190
-msgid ""
-"Q: How do I build using predefined packages lists? A: e.g. to build using "
-"standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo "
-"lh_build}# Note: The packages lists can be found in /usr/share/live-helper/"
-"lists/ directory."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:193
-msgid ""
-"Q: How do I rebuild without downloading all the packages again? A: All "
-"packages are cached in cache subdirectory. They remain until a clean purge: #"
-"{$ sudo lh_clean --purge}# You do not have to do anything to prevent "
-"packages from being re-downloaded. You need to remember to clean whichever "
-"stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, "
-"chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:196
-msgid ""
-"Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make "
-"a boot CD with grub, configured to boot from a debian-live kernel copied on "
-"the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/"
-"stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/"
-"boot/grub/menu.lst:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:205
-msgid ""
-"default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd) "
-"kernel /boot/vmlinuz boot=live initrd /boot/initrd.img"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:209
-msgid ""
-"Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-"
-"boot \\ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:212
-msgid ""
-"Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A: "
-"If you have a floppy drive, you may be able to use it, otherwise you will "
-"need to use loadlin/grub4dos/win32-loader. If you have a second system to "
-"serve up the image over the network, See http://wiki.debian.org/DebianLive/"
-"Howto/Creating_a_Netboot_Image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:215
-msgid ""
-"Q: The X configuration does not seems to work, the resolution is too low. "
-"What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf "
-"&& lh_config --packages xdebconfigurator}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:218
-msgid ""
-"Q: Apache has problems with static files A: Sendfile does not work well on "
-"the unionfs used by Debian Live. Add the following to apache's "
-"configuration: #{EnableSendfile off}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:222
-msgid ""
-"Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right "
-"now the best is to use a script that will populate the fstab when the CD is "
-"booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/"
-"trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper "
-"solution based on HAL will be described here in a hopefully near future. A: "
-"Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-"
-"policy-fixed-drives.fdi is not available anymore and the previous trick that "
-"consisted to remove this file to enable automounting of fixed drives as a "
-"consequence is obsolete. Eventually, it will be possible to combine HAL and "
-"PolicyKit to enable different permissions and actions to achieve advanced "
-"(auto)mounting for non-root users. Until then, because the live scripts are "
-"only touching to the fstab to add a swap partition if discovered at boot "
-"time, the only way to have fixed drives mounted automatically is to use a "
-"script that will populate the fstab file at the end of the multiuser "
-"runlevel. To achieve this, you can do, for example, the following: download "
-"the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-"
-"includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin "
-"directory, and move the script inside Make sure the script is executable "
-"(chmod +x diskmounter.sh) create the chroot_local-includes/etc/rc.local file "
-"and call the diskmounter from there (see this https://devel.goto10.org/svn/"
-"puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called "
-"correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and "
-"NTFS partitions and mount them read-write, except for NTFS. This will change "
-"soon and an option will be available to use ntfs-3g to mount NTFS as read-"
-"write. comments, patches and other things about this script and issue: "
-"http://code.goto10.org/projects/puredyne/ticket/463"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:225
-msgid ""
-"Q: Boot fails with panic: can't open /scripts/live A: Add latest live-"
-"initramfs deb package into config/chroot_local-packages directory and "
-"rebuild."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:229
-msgid ""
-"Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref "
-"linkend=\"internalization\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:234
-msgid ""
-"Q: How do I get past boot prompt without a working keyboard? A: See "
-"Customizing the bootup process % FIXME: <xref linkend=\"bootup\"/> Note: "
-"Boot from an USB-HDD on an iMac with GRUB did not work."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:237
-msgid ""
-"Q: Can I serve the root image from a web or ftp server? A: Since live-"
-"initramfs 1.99, it should be possible to use the fetch= argument on the "
-"kernel command line. You can build a netboot image as usual, and when you "
-"are done edit the tftpboot/pxelinux.cfg/default file. Remove the references "
-"to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url "
-"where you placed the root image>. You have to include wget in the chroot. It "
-"could work for other boot methods as well. However, I am not sure the live "
-"scripts configure the network when booting from a CD or USB disk. #{$ "
-"lh_config --packages wget}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:240
-msgid ""
-"Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you "
-"are building an etch image (which was the default up to 2007/09/14) you have "
-"a very old version of casper which does not support quickreboot and possibly "
-"other boot parameters as well. You could configure your sources to use live-"
-"backports (see /usr/share/live-helper/examples/sources/live-backports) and "
-"switch to live-initramfs, or better yet, build a lenny image instead, which "
-"is the new default. #{$ lh_config --distribution lenny $ lh_config --"
-"initramfs live-initramfs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:243
-msgid ""
-"Q: How do I fix \"Could not find kernel image\" issue with syslinux "
-"bootloader? A: Add a binary local hook script to fix kernel and initrd path "
-"each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux."
-"sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:249
-msgid "SYSLINUXCFG=`find binary -type f -name syslinux.cfg`"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:252
-msgid ""
-"sed -i \"s|kernel /vmlinuz|kernel vmlinuz|g\" ${SYSLINUXCFG} sed -i \"s|"
-"initrd=/initrd|initrd=initrd|g\" ${SYSLINUXCFG}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:254
-msgid "$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:259
-msgid ""
-"Q: How do I use a newer kernel with lenny? A: A build with backports.org "
-"kernels will fail as that repository lacks the necessary module packages "
-"(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://"
-"unsupported.debian-maintainers.org/backports-kernel/ The quick way to "
-"success:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:268
-msgid ""
-"$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-"
-"modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-"
-"kernel/ ./' > config/chroot_sources/backports-kernel.chroot $ echo 'deb "
-"http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/"
-"chroot_sources/backports-kernel.binary $ wget http://unsupported.debian-"
-"maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/"
-"backports-kernel.chroot.gpg $ wget http://unsupported.debian-maintainers.org/"
-"backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel."
-"binary.gpg $ lh_build }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:271
-msgid ""
-"Q: How do I use a custom kernel? Is there a nice way of booting debian-live "
-"with a custom kernel (not in an apt repo)? A: Copy it into config/"
-"chroot_local-packages and set LH_LINUX_PACKAGES=\"none\" or use lh config --"
-"linux-packages \" \" Don't forget to compile your kernel with an union "
-"filesystem (unionfs or aufs), squashfs modules, and initrd support. I can "
-"cause the kernel to be installed but it seems this happens later than grub/"
-"syslinux is configured so it's not listed and casper/ and the menu require "
-"munging. You need to follow the debian scheme, e.g. placing the files in /"
-"boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't "
-"go that way which is too much of a hassle, and just use make-kpkg to produce "
-"custom kernel deb packages. They should integrate nicely if you just put "
-"them into config/chroot_local-packages and set LH_LINUX_PACKAGES=\"\". Hint: "
-"to work around an error, which lh_binary_syslinux will throw on custom "
-"kernels if there is not an 468/686 in the kernel-name, you need to set "
-"CONFIG_LOCALVERSION=\"-486\" or \"-686\" within the kernel configuration (-"
-"> General setup -> Local version set to -486 or -686) corresponding to "
-"LH_LINUX_FLAVOURS=\"\" or \"686\". this at least up till live-helper version "
-"1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-"
-"devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/"
-"debian-live-devel/2007-November/002581.html"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:274
-msgid ""
-"Q: How do I create a cross arch live CD image? A: In short: You can't. Read "
-"on: The procedure to create a live CD is based on creating a chroot that "
-"contains the files that will be finally available on the live CD. The live "
-"CD building procedure includes chrooting into the chroot dir and so some "
-"operations. chrooting means that the terminal you chroot on will behave as a "
-"different system so your real system and the chroot environment is decoupled "
-"somehow. Once the live CD scripts chroots into the chroot dir they have some "
-"operations to do inside that environment and your real system won't be able "
-"to run them unless you are using the same architecture. So you only are able "
-"to make live CD for the arch you run on. But this doesn't prevent you run "
-"qemu or some other machine emulator that make this possible."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:277
-msgid ""
-"Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That "
-"depends what you've changed between builds If, for example, you've built an "
-"iso image and you want a usb image, you only need to run #{lh_clean --binary}"
-"# before you run lh_build again. If you've changed anything in the chroot, "
-"you'll need to cleanup both chroot and binary with #{lh_clean}# before "
-"continuing"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:280
-msgid ""
-"Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in config/binary"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:283
-msgid ""
-"Q: How do I include different modules to load when the live system boots? A: "
-"Configure config/chroot_local-includes/etc/initramfs-tools/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:285
-msgid ""
-"The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default "
-"initramfs.conf \"MODULES = most\". You may override that by supplying your "
-"own initramfs.conf, or else just add your own modules, e.g."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:290
-msgid ""
-"mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo \"atl2\" >> "
-"config/chroot_local-includes/etc/initramfs-tools/modules"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:294
-msgid ""
-"Note: Even though initramfs.conf(5) says \"most adds all the framebuffer, "
-"acpi, file system, ide, sata, scsi and usb drivers\", it actually includes "
-"network drivers as well. See auto_add_modules() in /usr/share/initramfs-"
-"tools/hook-functions for the complete list."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:297
-msgid ""
-"Q: Can I have a splash screen? A: Yes you can. You will not know what is "
-"going on when the splash screen is active, it may fail to activate on some "
-"hardware or break X on other (both usplash and splashy use libdirectfb which "
-"does some evil voodoo and may break you graphics or input until you reboot). "
-"However, you can install and activate it just as you would on any other "
-"Debian system. To use splashy: 1. install splashy and read the README, the "
-"manpages are useless for setting it up. Add some parameters to your kernel "
-"command line, such as in your pxelinux configuration or in "
-"LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 "
-"splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, "
-"#{quiet}# to suppress most kernel messages that you cannot see anyway but "
-"would scroll past before splashy manages to paint the graphics on your "
-"screen. You might want to add splashy to the list of packages installed in "
-"your image: #{echo splashy > config/chroot_local-packageslists/splashy echo "
-"splashy-themes >> config/chroot_local-packageslists/splashy}# and select a "
-"theme:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:305
-msgid ""
-"echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s "
-"debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the "
-"ramdisk to include the splash screen echo update-initramfs -u -k all >> "
-"config/chroot_local-hooks/splashy chmod 755 config/chroot_local-hooks/splashy"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:309
-msgid ""
-"After you rebuild your live system you should observe a bluish splash screen "
-"while booting. Nothing happens while initramfs is running because there is "
-"no splashy support in initramfs-tools. Once the init starts the progress bar "
-"should start to fill. If #{vga=something}# sets a mode that your screen "
-"cannot show or your card cannot do vesa 2.0 (and thus you get plain text "
-"mode and no splashy) read the splashy faq."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:312
-msgid ""
-"Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the "
-"firmwares to the initrd image. You need to install the non-free package "
-"\"firmware-bnx2\". Uncompress your initrd image, then copy files:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:317
-msgid ""
-"cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /"
-"lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw "
-"${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:321
-msgid "Recompress your initrd image and boot: it works!"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:323
-msgid ""
-"Q: X is broken (the system boots, messages scroll by, and then the screen "
-"goes blank). What do I do? A: On my system starting X completely disables "
-"graphics so that I do not see anything even after X bails out and I am back "
-"to the console. To prevent this you can change the driver Xorg uses."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:325
-msgid ""
-"If you have a working splash screen or at least graphical console you can "
-"use #{live xdriver=fbdev}# when booting the live system (instead of just "
-"enter). Another driver you might want to try is #{vesa}#. If all fails you "
-"might try to set xdriver to some wrong value so that Xorg fails to start and "
-"you can examine the system while you still see something on the console. #"
-"{live xdriver=none}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:328
-msgid ""
-"Q: How can I get Debian first stable versions? A: I'm developing software "
-"and testing it on Live-CD. Thanks for the LiveCD project. To be sure my "
-"development is fully compatible with the \"etch\" version, I need the same "
-"scenario when Debian GNU/Linux 4.0 was published as stable (I believe "
-"2007.04.08). If there was some bug on 2007.04.08 that was corrected one week "
-"later, I need to test software foreseeing that scenario without the bug "
-"solved."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:331
-msgid ""
-"Q: I get \"fopen: Permission denied\"-warnings from apt on building/at the "
-"live-system A: That's a harmless bug in apt. However, if you want to get off "
-"this warnings in the live-system, add a file in chroot_local-hooks with "
-"follow row:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:335
-msgid "chown -R man.man /var/cache/man"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:340
-msgid ""
-"Q: Why I always fail during \"Retrieving Packages\" stage when running "
-"lh_build? I have already set apt-http-proxy and so on. A: lh_build "
-"retrieves packages via wget, as a result you need to enable the proxy "
-"settings in /etc/wgetrc before running lh_build."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:343
-msgid ""
-"Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system "
-"boots, so it's useless to put modifed Xorg.conf in config/choort_local-"
-"includes/etc/X11, because it will be overwritten during boot. However, you "
-"can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the "
-"result will be modified Xorg.conf. The modified dexconf has to be put in "
-"config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for "
-"two or more keyboards layouts with alt+shift toggle by editing dexconf and "
-"replacing the line:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:347
-msgid "Option \"XkbLayout\" \"$XKB_LAYOUT\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:351
-msgid "with the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:356
-msgid ""
-"Option \"XkbLayout\" \"us,il\" Option \"XkbOptions\" \"grp:alt_shift_toggle,"
-"grp_led:scroll\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:360
-msgid "when \"us,il\" are the wanted keyboard layouts."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:362
-msgid ""
-"You can force default screen resulotion (e.g. 1024*768) by adding the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:368
-#, no-wrap
-msgid ""
-"SubSection \"Display\"\n"
-" Modes \"1024x768\"\n"
-"EndSubSection\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:372
-msgid "between the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:379
-#, no-wrap
-msgid ""
-"Section \"Screen\"\n"
-" Identifier \"Default Screen\"\n"
-" Monitor \"Configured Monitor\"\n"
-"EndSection\"\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:383
-msgid ""
-"Q: Where are the build parameters for the prebuilt images A: See http://live."
-"debian.net/README.images."
-msgstr ""
diff --git a/manual/po/ro/other_howtos.ssi.po b/manual/po/ro/other_howtos.ssi.po
deleted file mode 100644
index 8bdc4fd..0000000
--- a/manual/po/ro/other_howtos.ssi.po
+++ /dev/null
@@ -1,380 +0,0 @@
-# Romanian translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: ro\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=3; plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < "
-"20)) ? 1 : 2;\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_howtos.ssi:2
-msgid "B~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:4
-msgid "1~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:6
-msgid "2~ ISO"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:8
-msgid ""
-"Generating a Debian Live CD is very simple. You need to have live-helper "
-"(package available in Debian sid and lenny), and Debootstrap (or "
-"cdebootstrap) from etch or newer."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:10
-msgid "3~ Install live-helper"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:12
-msgid "#{apt-get install live-helper}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:14
-msgid "3~ Configure the current working directory with lh_config"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:18
-msgid "lh_config -b iso -a $ARCH"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:22
-msgid "where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:24
-msgid "#{-b}# flag is used to be sure to obtain image in ISO format."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:26
-msgid "3~ Build the image with lh_build:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:28
-msgid "Execute lh_build as root: #{lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:30
-msgid ""
-"The command above will create the basic image, containing just the Debian "
-"standard system (with no X at all)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:32
-msgid ""
-"If you want to have any of the Desktop environments on your livecd, #{ls /"
-"usr/share/live-helper/lists}# will show a number of available package Lists "
-"to choose from, e.g. #{lh_config -p gnome-desktop}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:34
-msgid "More examples are listed at DebianLive/Examples."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:37
-msgid ""
-"See packages for help configuring a local Debian Mirror and other aspects of "
-"the live system. % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:39
-msgid "3~ Test the image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:41
-msgid "If you have qemu installed, you can boot the image with:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:45
-msgid "qemu -cdrom binary.iso"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:49
-msgid "If you have also kqemu installed, you can add #{-kernel-kqemu}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:51
-msgid "2~ ISO_(multiarch)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:53
-msgid ""
-"Multiple machine boot CDs can be created with the following manual "
-"procedure. This procedure has been successfully used to create a single CD "
-"which is bootable on alpha, i386, pmax, and sparc. It should be possible to "
-"also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:55
-msgid ""
-"To create a CD which is bootable by multiple architectures, use the "
-"following steps in this order. Please note that the order is critical."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:57
-msgid ""
-"Make sure you have all the required files including the various kernels and "
-"boot programs listed in the individual machine sections."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:59
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.pmax "
-"and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/"
-"mdec.pmax/bootxx_cd9660."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:61
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.vax and "
-"include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/"
-"xxboot.}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:63
-msgid "Include the macppc ofwboot.xcf bootloader in /cdsources."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:65
-msgid ""
-"Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/"
-"installation/floppy/boot-big.fs \\ -c boot.catalog -l -J -r -L /cdsources "
-"2>&1 | tee /tmp/mkisofs.log exit}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:67
-msgid ""
-"Note: The appearance of the -v flag twice is required. If you are making a "
-"bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -"
-"part in the parameters for mkisofs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:69
-msgid ""
-"Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 "
-"bootblocks. Alternatively, install the sysutils/mksunbootcd package on your "
-"favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs "
-"boot-sun4m.fs boot-sun3.fs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:71
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/pmax to install the pmax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"pmax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:73
-msgid ""
-"#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:75
-msgid ""
-"The -o append,sunsum option appends the first stage boot block to the end of "
-"the ISO file system, and restores the checksum used when booting on a sun."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:77
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/vax to install the vax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"vax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:79
-msgid "installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:81
-msgid "(See the pmax entry above for an explanation of the flags)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:83
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/alpha to install the "
-"alpha bootblocks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:85
-msgid ""
-"#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:86
-msgid ""
-"Note: The alpha installboot must occur after the others, because currently "
-"it's the only machine dependent back-end for installboot(8) that can "
-"calculate the alpha checksum. (See the pmax entry above for an explanation "
-"of the flags)."
-msgstr ""
diff --git a/manual/po/ro/other_use-cases.ssi.po b/manual/po/ro/other_use-cases.ssi.po
deleted file mode 100644
index 38b1704..0000000
--- a/manual/po/ro/other_use-cases.ssi.po
+++ /dev/null
@@ -1,380 +0,0 @@
-# Romanian translations for live-manual package
-# Copyright (C) 2010 Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# Automatically generated, 2010.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: 2010-10-03 20:30+0300\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"Language: ro\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Plural-Forms: nplurals=3; plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < "
-"20)) ? 1 : 2;\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr "code{"
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr "}code"
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:2
-msgid "B~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:4
-msgid "1~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:6
-msgid "This chapter is for users to document their use cases with Debian Live."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:8
-msgid "2~ VNC Kiosk Client"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:10
-msgid "Create an image with live-helper to boot directly to a VNC server."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:12
-msgid "_* Make a build directory: #{$ mkdir vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:14
-msgid "_* Move to the build directory: #{$ cd vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:16
-msgid ""
-"Example to config the build directory to include gdm metacity "
-"xtightvncviewer: #{$ lh config --packages \"gdm metacity xtightvncviewer\"}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:18
-msgid ""
-"Create a folder /etc/skel folder for a custom .xsession for the default "
-"user: #{$ mkdir -p config/chroot_local-includes/etc/skel}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:20
-msgid ""
-"Create the .xsession for the default user: #{$ touch config/chroot_local-"
-"includes/etc/skel/.xsession}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:22
-msgid ""
-"Edit the .xsession file to launch metacity and start xvncviewer with "
-"something similar to the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:29
-msgid "/usr/bin/metacity & /usr/bin/vncviewer xxx.xxx.xxx.xxx:PORT"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:31
-msgid "exit"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:35
-msgid "_* Build the image: #{# lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:37 en/other_use-cases.ssi:138
-msgid "_* Enjoy."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:39
-msgid "2~ VMWare-Player Sessions"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:41
-msgid ""
-"Create an image with live-helper to boot directly to a specifiv VMWare "
-"session."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:43
-msgid "_* Make a build directory: #{$ mkdir VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:45
-msgid "_* Move to the build directory: #{$ cd VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:47
-msgid ""
-"_* Example to config the build directory to include gdm metacity "
-"xtightvncviewer:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:67
-#, no-wrap
-msgid ""
-"$ lh config --apt apt \\\n"
-" ---apt-recommends disabled \\\n"
-" --archive-areas \"main\" \\\n"
-" --binary-images iso \\\n"
-" --binary-indices none \\\n"
-" --syslinux-menu vesamenu \\\n"
-" ---bootappend-live \"persistent quickreboot\" \\\n"
-" ---bootappend-install \"-- plainroot persistent video=vesa:ywrap,mtrr vga=788 quickreboot quiet live-config\" \\\n"
-" ---debian-installer live \\\n"
-" ---distribution lenny \\\n"
-" ---hostname vmare-player-firmware \\\n"
-" ---includes none \\\n"
-" ---linux-flavours 686 \\\n"
-" ---packages-lists \"gnome-core\" \\\n"
-" ---packages \"gcc gparted linux-headers-2.6-\\${LH_LINUX_FLAVOURS} live-config-staging make metacity rsync wireless-tools\" \\\n"
-" ---repositories live.debian.net \\\n"
-" ---win32-loader disabled\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:71
-msgid ""
-"_* Create the 01-vmware-player hook: #{$ touch config/chroot_local-hooks/01-"
-"vmware-player.sh}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:73
-msgid ""
-"Edit the 01-vmware-player hook to launch the VMWare-Player. The hook should "
-"look something like the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:80
-msgid ""
-"_URL=\"http://archive.debian-maintainers.org/vmware/other/vmware-player/\" "
-"_VMPLAYER_VERSION=\"VMware-Player.i386.bundle\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:83
-msgid "echo \"I: Starting script for install of VMWare Player.\" cd /root"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:86
-msgid ""
-"echo \"I: Beginning download of ${_VMPLAYER_VERSION} from ${_URL} .\" wget "
-"${_URL}${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:89
-msgid ""
-"echo \"I: Starting install of VMWare Player.\" sh /root/${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:92
-msgid ""
-"echo \"I: Cleaning up the VMWare Player download.\" rm /root/"
-"${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:95
-msgid "#echo \"I: Starting interactive shell.\" #bash"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:99
-msgid ""
-"_* Build the image (note that during the build the VMWare-Player will prompt "
-"you to install or cancel): #{#lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:101
-msgid ""
-"_* After the build you will have an image you can boot live or install as "
-"firmware. The package live-config-staging is the package that installs the "
-"ability to utilize the VMWare-Player by calling live-config.vmware-player as "
-"a boot parameter in the following form:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:105
-msgid "live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:109
-msgid "Notes from the 900-vmware-player file are as follows:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:135
-#, no-wrap
-msgid ""
-"# The script tests for boot parameter of\n"
-"# live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME\n"
-"#\n"
-"# ACTION: The operation to perform on the workstation (none|scratch)\n"
-"# IMAGEPATH: The folder path to the VMware image you want to run.\n"
-"# VMXNAME: The name of the VMware image you want to run.\n"
-"#\n"
-"# Notes:To use this file with WMWare images you will need to have a few things\n"
-"# setup:\n"
-"#\n"
-"# 1. The VMware Player needs to be installed in the image.\n"
-"# 2. This script uses (s|h)da1 for writing image data, and is used as a scratch\n"
-"# space. This scratch space should be a file system with linux permissions\n"
-"# such as ext2.\n"
-"# 3. VMware image(s) should be in a mounted folder and setup as follows:\n"
-"# - Image(s) set to snapshot mode.\n"
-"# - For each image, the image folder needs to have a file called\n"
-"# image-release with a variable CRELEASE. An example: CRELEASE=\"1.0.0\"\n"
-"#\n"
-"# The image-release file is used by the image maintainer and this script to tell\n"
-"# workstation(s) using a given image, to erase locally stored vmware image files\n"
-"# and setup with the newly configure image. The operation of erasing locally\n"
-"# stored vmare image files, is referred to as a scratch.\n"
-msgstr ""
diff --git a/manual/po/ro/user_examples.ssi.po b/manual/po/ro/user_examples.ssi.po
index 0f61294..fab2eda 100644
--- a/manual/po/ro/user_examples.ssi.po
+++ b/manual/po/ro/user_examples.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0~a12\n"
-"POT-Creation-Date: 2010-12-11 13:57-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: 2010-11-04 16:34-0400\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,13 +21,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/other_faq.ssi:41 en/other_faq.ssi:83
-#: en/other_faq.ssi:103 en/other_faq.ssi:117 en/other_faq.ssi:137
-#: en/other_faq.ssi:151 en/other_faq.ssi:198 en/other_faq.ssi:245
-#: en/other_faq.ssi:261 en/other_faq.ssi:287 en/other_faq.ssi:299
-#: en/other_faq.ssi:314 en/other_faq.ssi:333 en/other_faq.ssi:345
-#: en/other_faq.ssi:353 en/other_faq.ssi:364 en/other_faq.ssi:374
-#: en/other_howtos.ssi:16 en/other_howtos.ssi:43 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:58
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -88,13 +82,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/other_faq.ssi:37 en/other_faq.ssi:46
-#: en/other_faq.ssi:92 en/other_faq.ssi:108 en/other_faq.ssi:141
-#: en/other_faq.ssi:155 en/other_faq.ssi:207 en/other_faq.ssi:256
-#: en/other_faq.ssi:292 en/other_faq.ssi:307 en/other_faq.ssi:319
-#: en/other_faq.ssi:337 en/other_faq.ssi:349 en/other_faq.ssi:358
-#: en/other_faq.ssi:370 en/other_faq.ssi:381 en/other_howtos.ssi:20
-#: en/other_howtos.ssi:47 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:62
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -151,12 +139,6 @@ msgid "}code"
msgstr "}code"
#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/user_examples.ssi:92
-#: en/user_examples.ssi:141 en/user_examples.ssi:190
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
#: en/user_basics.ssi:44 en/user_basics.ssi:120 en/user_basics.ssi:204
#: en/user_examples.ssi:109 en/user_examples.ssi:156
msgid "# lb build"
@@ -361,6 +343,11 @@ msgid "Edit #{auto/config}# to read as follows:"
msgstr ""
#. type: Plain text
+#: en/user_examples.ssi:92 en/user_examples.ssi:141 en/user_examples.ssi:190
+msgid "#!/bin/sh"
+msgstr ""
+
+#. type: Plain text
#: en/user_examples.ssi:99
#, no-wrap
msgid ""
diff --git a/manual/po4a.cfg b/manual/po4a.cfg
index 44c60df..b604d99 100644
--- a/manual/po4a.cfg
+++ b/manual/po4a.cfg
@@ -3,8 +3,6 @@
[type: text] en/live-manual.ssm $lang:$lang/live-manual.ssm
[type: text] en/about_manual.ssi $lang:$lang/about_manual.ssi
[type: text] en/about_project.ssi $lang:$lang/about_project.ssi
-[type: text] en/other_faq.ssi $lang:$lang/other_faq.ssi
-[type: text] en/other_howtos.ssi $lang:$lang/other_howtos.ssi
[type: text] en/project_bugs.ssi $lang:$lang/project_bugs.ssi
[type: text] en/project_coding-style.ssi $lang:$lang/project_coding-style.ssi
[type: text] en/project_procedures.ssi $lang:$lang/project_procedures.ssi
diff --git a/manual/pot/live-manual.ssm.pot b/manual/pot/live-manual.ssm.pot
index bde87bb..b310ebb 100644
--- a/manual/pot/live-manual.ssm.pot
+++ b/manual/pot/live-manual.ssm.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-12-11 13:18-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -173,13 +173,3 @@ msgstr ""
#: en/live-manual.ssm:65
msgid "<< user_examples.ssi"
msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:67
-msgid "% << other_faq.ssi"
-msgstr ""
-
-#. type: Plain text
-#: en/live-manual.ssm:68
-msgid "% << other_howtos.ssi"
-msgstr ""
diff --git a/manual/pot/other_faq.ssi.pot b/manual/pot/other_faq.ssi.pot
deleted file mode 100644
index 1c5305d..0000000
--- a/manual/pot/other_faq.ssi.pot
+++ /dev/null
@@ -1,1008 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-10-16 14:45-0200\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
-"Language: \n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:83 en/about_manual.ssi:91 en/about_manual.ssi:99
-#: en/about_manual.ssi:111 en/about_manual.ssi:124 en/about_manual.ssi:137
-#: en/about_manual.ssi:145 en/about_manual.ssi:153 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_faq.ssi:41 en/other_faq.ssi:83 en/other_faq.ssi:103
-#: en/other_faq.ssi:117 en/other_faq.ssi:137 en/other_faq.ssi:151
-#: en/other_faq.ssi:198 en/other_faq.ssi:245 en/other_faq.ssi:261
-#: en/other_faq.ssi:287 en/other_faq.ssi:299 en/other_faq.ssi:314
-#: en/other_faq.ssi:333 en/other_faq.ssi:345 en/other_faq.ssi:353
-#: en/other_faq.ssi:364 en/other_faq.ssi:374 en/other_howtos.ssi:16
-#: en/other_howtos.ssi:43 en/other_live-environment.ssi:14
-#: en/other_live-environment.ssi:30 en/other_live-environment.ssi:51
-#: en/other_live-environment.ssi:61 en/other_live-environment.ssi:69
-#: en/other_live-environment.ssi:77 en/other_live-environment.ssi:85
-#: en/other_live-environment.ssi:93 en/other_live-environment.ssi:116
-#: en/other_live-environment.ssi:124 en/other_live-environment.ssi:133
-#: en/other_procedures.ssi:12 en/other_procedures.ssi:46
-#: en/other_procedures.ssi:58 en/other_use-cases.ssi:24
-#: en/other_use-cases.ssi:49 en/other_use-cases.ssi:75
-#: en/other_use-cases.ssi:103 en/other_use-cases.ssi:111 en/user_basics.ssi:36
-#: en/user_basics.ssi:48 en/user_basics.ssi:62 en/user_basics.ssi:74
-#: en/user_basics.ssi:86 en/user_basics.ssi:98 en/user_basics.ssi:114
-#: en/user_basics.ssi:122 en/user_basics.ssi:130 en/user_basics.ssi:140
-#: en/user_basics.ssi:152 en/user_basics.ssi:164 en/user_basics.ssi:172
-#: en/user_basics.ssi:180 en/user_basics.ssi:194 en/user_basics.ssi:202
-#: en/user_basics.ssi:212 en/user_basics.ssi:232 en/user_basics.ssi:265
-#: en/user_basics.ssi:281 en/user_basics.ssi:289 en/user_basics.ssi:309
-#: en/user_basics.ssi:334 en/user_customization-contents.ssi:34
-#: en/user_customization-contents.ssi:43 en/user_customization-contents.ssi:66
-#: en/user_customization-internationalization.ssi:10
-#: en/user_customization-internationalization.ssi:18
-#: en/user_customization-internationalization.ssi:26
-#: en/user_customization-internationalization.ssi:38
-#: en/user_customization-packages.ssi:16 en/user_customization-packages.ssi:24
-#: en/user_customization-packages.ssi:36 en/user_customization-packages.ssi:45
-#: en/user_customization-packages.ssi:59 en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:106
-#: en/user_installation.ssi:120 en/user_installation.ssi:137
-#: en/user_managing_a_configuration.ssi:24
-#: en/user_managing_a_configuration.ssi:35
-#: en/user_managing_a_configuration.ssi:47 en/user_overview.ssi:60
-#: en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr ""
-
-#. type: Plain text
-#: en/about_manual.ssi:87 en/about_manual.ssi:95 en/about_manual.ssi:103
-#: en/about_manual.ssi:120 en/about_manual.ssi:133 en/about_manual.ssi:141
-#: en/about_manual.ssi:149 en/about_manual.ssi:157 en/about_manual.ssi:164
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_faq.ssi:37 en/other_faq.ssi:46 en/other_faq.ssi:92
-#: en/other_faq.ssi:108 en/other_faq.ssi:141 en/other_faq.ssi:155
-#: en/other_faq.ssi:207 en/other_faq.ssi:256 en/other_faq.ssi:292
-#: en/other_faq.ssi:307 en/other_faq.ssi:319 en/other_faq.ssi:337
-#: en/other_faq.ssi:349 en/other_faq.ssi:358 en/other_faq.ssi:370
-#: en/other_faq.ssi:381 en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:92
-#: en/user_basics.ssi:104 en/user_basics.ssi:118 en/user_basics.ssi:126
-#: en/user_basics.ssi:134 en/user_basics.ssi:144 en/user_basics.ssi:158
-#: en/user_basics.ssi:168 en/user_basics.ssi:176 en/user_basics.ssi:184
-#: en/user_basics.ssi:198 en/user_basics.ssi:206 en/user_basics.ssi:216
-#: en/user_basics.ssi:257 en/user_basics.ssi:285 en/user_basics.ssi:293
-#: en/user_basics.ssi:320 en/user_basics.ssi:359
-#: en/user_customization-contents.ssi:39 en/user_customization-contents.ssi:54
-#: en/user_customization-contents.ssi:70
-#: en/user_customization-internationalization.ssi:14
-#: en/user_customization-internationalization.ssi:22
-#: en/user_customization-internationalization.ssi:30
-#: en/user_customization-internationalization.ssi:42
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:172
-#: en/user_customization-packages.ssi:182
-#: en/user_customization-packages.ssi:192
-#: en/user_customization-packages.ssi:202 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:88 en/user_installation.ssi:110
-#: en/user_installation.ssi:125 en/user_installation.ssi:140
-#: en/user_managing_a_configuration.ssi:31
-#: en/user_managing_a_configuration.ssi:43
-#: en/user_managing_a_configuration.ssi:52 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:2
-msgid "B~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:4
-msgid "1~ Frequently asked questions (FAQ)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:8
-msgid ""
-"Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A: "
-"See \"Copying USB/HDD image to a USB stick\" % FIXME: <xref linkend="
-"\"image_copying\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:11
-msgid ""
-"Q: How do I log my build? A: You could use script, screen or tee: #{$ "
-"lh_build 2>&1 | tee build.log}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:14
-msgid ""
-"Q: How can I convert an already installed standard Debian partition into a "
-"Debian Live system? A: Save the list of installed packages and load it into "
-"your new Debian Live System. Copy your /etc to config/chroot_local-includes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:17
-msgid ""
-"Q: What does 'losetup: could not find any free loop device' mean and how do "
-"I fix it? A: Loop devices are used during the build; there probably aren't "
-"any free if you've aborted several builds. Something like: for l in /dev/"
-"loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/"
-"loop7 ; do losetup -d $l ; done should rectify the situation (assuming all "
-"loop devices in use were created by lh_build; if in doubt, check the "
-"contents of each loop device before deleting them with losetup -d)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:20
-msgid ""
-"Q: How do I launch an interactive shell during the chroot stage? A: To "
-"enable interactive shell: #{$ lh_config --interactive shell}# To continue "
-"the build process: #{# logout}# or #{# exit}# To disable interactive shell, "
-"set LH_INTERACTIVE to \"disabled\" in config/chroot."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:23
-msgid ""
-"Q: What is the root /user password? A: The user password for the live user "
-"is 'live'. By default, there is not any root password. You can switch to "
-"root with ${sudo -i}# or set a password for root with #{sudo passwd}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:27
-msgid ""
-"Q: How do I change root or any user password? A: Add a chroot local hook "
-"script to change root or any user password each time you build an image. e."
-"g. config/chroot_local-hooks/01-update_password.sh to set root password to "
-"\"nopasswd\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:30 en/other_faq.ssi:53
-msgid "code{ #!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:33
-msgid "echo \"I: update password\" echo \"root:nopasswd\" | chpasswd"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:35
-msgid "$ chmod +x config/chroot_local-hooks/01-update_password.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:39
-msgid ""
-"Note for live user; you need to copy the /usr/share/initramfs-tools/scripts/"
-"live-bottom/10adduser your build folder:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:44
-msgid ""
-"mkdir -p config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-"
-"bottom/ cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser config/"
-"chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:48
-msgid ""
-"Note: Then edit the config/chroot_local-includes/usr/share/initramfs-tools/"
-"scripts/live-bottom/10adduser and paste in the new user_crypted password "
-"that you make with: #{echo \"newlivepass\" | mkpasswd -s}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:50
-msgid ""
-"Or add an hook file in config/chroot_local-hooks/ with something like the "
-"below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:57
-msgid ""
-"# Change the autogenerated user password to \"debianlive\" plain_password="
-"\"debianlive\" password=$(echo \"${plain_password}\" | mkpasswd -s)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:59
-msgid ""
-"sed -i -e 's/\\(user_crypted=\\)\\(.*\\)\\( #.*\\)/\\1\\\"'${password}'\\"
-"\"\\3/' /usr/share/initramfs-tools/scripts/live-bottom/10adduser"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:62
-msgid "update-initramfs -tu -kall }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:64
-msgid ""
-"The latter (hook model) could be more future proof than the former solution "
-"since it modifies just one string selectively but it requires the package "
-"\"whois\" to be installed on the target system (for mkpasswd) or that you "
-"generate the $password string not at build time and include it crypted in "
-"the above script."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:68
-msgid ""
-"Q: How to disable autologin? A1: use the commandline parameter #{lh config --"
-"bootappend-live \"noautologin\"}# A2: You need to set boot=noautologin "
-"noxautologin as described in man live-initramfs If you boot via TFTP you "
-"want to insert the option to pxelinux.cfg/default"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:71
-msgid ""
-"Q: How do I change default hostname or username? A: To change default "
-"hostname or username: #{$ lh_config --hostname myhostname $ lh_config --"
-"username myusername}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:74
-msgid ""
-"Q: How do I make the final image smaller? A: Clean orphaned apps/libs: "
-"Install package \"deborphan\" and then run 'sudo deborphan -n' . Delete "
-"unwanted packages. Remove the apt cache. Purge unwanted locales (see "
-"\"localepurge\" package)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:77
-msgid ""
-"Q: How do I customize bash-config permanently (aliases, bash-completion "
-"etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:81
-msgid ""
-"Q: How do I disable services permanently? (Be careful!) A: Add a chroot "
-"local hook script to disable a service each time you build an image: e.g. "
-"config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:88
-msgid "echo \"I: disable service\" update-rc.d -f service_name remove"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:90
-msgid "$ chmod +x config/chroot_local-hooks/01-disable_service.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:95
-msgid ""
-"Q: How do I enable | disable the md5checksum at the ISO building? A: #"
-"{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:98
-msgid ""
-"Q: How to disable the generation of the .tar.gz file? A: #{lh_config --net-"
-"tarball none|gzip}# Or change the LH_NET_TARBALL value. (only available in "
-"snapsshot version at the moment 2008/Feb/28)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:101
-msgid "Q: How do I \"build a new image\"? A: Run commands:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:106
-msgid "$ sudo lh_clean --binary $ sudo lh_build"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:110
-msgid ""
-"Hint: If the configuration had changed you should leave \"--binary\" out. "
-"This will clean your chroot directory too."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:113
-msgid ""
-"Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages "
-"you want."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:115
-msgid "Create /home/$USERNAME/.dmrc file (default username is \"user\")."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:122
-msgid "$ cat .dmrc [Desktop] Session=fluxbox }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:124
-msgid "Note: .dmrc is owned by $USERNAME:$USERNAME."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:126
-msgid ""
-"See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at "
-"http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:129
-msgid ""
-"Q: How do I use custom repositories? A: See http://wiki.debian.org/"
-"DebianLive/Configuration"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:132
-msgid ""
-"Q: How do I customize the artwork for the live CD (grub or syslinux boot "
-"splash, usplash, etc.)? A: See http://wiki.debian.org/DebianLive/Howto/"
-"Custom_Artwork"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:135
-msgid ""
-"Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look? "
-"A: Start the live system in qemu:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:139
-msgid "$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:143
-msgid "Note: the -redir argument must be changed to meet your needs"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:146
-msgid ""
-"Q: How do I execute a custom shell script inside the chroot system after the "
-"chroot stage? A: Add your script in config/chroot_local-hooks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:149
-msgid ""
-"Q: How do I add a script running immediately after all other scripts when "
-"the live system boots? A: Add your script in config/chroot_local-includes/"
-"usr/share/initramfs-tools/scripts/live-bottom/99scrip"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:153
-msgid ""
-"$ chmod +x config/chroot_local-includes/usr/share/initramfs-tools/scripts/"
-"live-bottom/99script"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:157
-msgid ""
-"Note: The hook script must be executable. Do not forget to lh_clean --chroot "
-"after making this change before you build again."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:159
-msgid ""
-"You must also use the example script /usr/share/live-helper/examples/hooks/"
-"update-initramfs.sh to ensure your script gets built into the initramfs "
-"(read the comment header for instructions)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:163
-msgid ""
-"Q: How do I add software not in Debian ? A: See Customizing package "
-"installation % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:166
-msgid ""
-"Q: What is the manifest with Ubuntu used for? A: Manifest is just the "
-"package list, which ubuntu does $something with. Don't worry about it."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:169
-msgid ""
-"Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:172
-msgid ""
-"Q: Do I need to write the image on USB stick to test it? A: you must use "
-"qemu >= 0.8."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:175
-msgid "Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:178
-msgid ""
-"Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed "
-"something else entirely? A: It is not. It is a package list, not a debconf "
-"preseeding."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:181
-msgid ""
-"Q: What is the difference between standard and minimal? A: standard: "
-"packages of priority standard and higher; minimal: packages of priority "
-"essential and higher;"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:184
-msgid ""
-"Q: What can the sections be used for? Aren't they BIG? A: Someone maybe "
-"wants to include packages from contrib or non-free."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:187
-msgid "Q: memtest86+ ... is that used? A: Yes"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:190
-msgid ""
-"Q: How do I build using predefined packages lists? A: e.g. to build using "
-"standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo "
-"lh_build}# Note: The packages lists can be found in /usr/share/live-helper/"
-"lists/ directory."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:193
-msgid ""
-"Q: How do I rebuild without downloading all the packages again? A: All "
-"packages are cached in cache subdirectory. They remain until a clean purge: #"
-"{$ sudo lh_clean --purge}# You do not have to do anything to prevent "
-"packages from being re-downloaded. You need to remember to clean whichever "
-"stages you want to rebuild first. e.g. to rebuild from the cached bootstrap, "
-"chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:196
-msgid ""
-"Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make "
-"a boot CD with grub, configured to boot from a debian-live kernel copied on "
-"the cd structure #{$ mkdir -p iso/boot/grub && cp /usr/lib/grub/i386-pc/"
-"stage2_eltorito iso/boot/grub && cp chroot/boot/* iso/boot/}# Create iso/"
-"boot/grub/menu.lst:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:205
-msgid ""
-"default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd) "
-"kernel /boot/vmlinuz boot=live initrd /boot/initrd.img"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:209
-msgid ""
-"Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-"
-"boot \\ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn the image."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:212
-msgid ""
-"Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A: "
-"If you have a floppy drive, you may be able to use it, otherwise you will "
-"need to use loadlin/grub4dos/win32-loader. If you have a second system to "
-"serve up the image over the network, See http://wiki.debian.org/DebianLive/"
-"Howto/Creating_a_Netboot_Image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:215
-msgid ""
-"Q: The X configuration does not seems to work, the resolution is too low. "
-"What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend xdebconf "
-"&& lh_config --packages xdebconfigurator}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:218
-msgid ""
-"Q: Apache has problems with static files A: Sendfile does not work well on "
-"the unionfs used by Debian Live. Add the following to apache's "
-"configuration: #{EnableSendfile off}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:222
-msgid ""
-"Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right "
-"now the best is to use a script that will populate the fstab when the CD is "
-"booting. Such a script can be found at https://devel.goto10.org/svn/puredyne/"
-"trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh. A proper "
-"solution based on HAL will be described here in a hopefully near future. A: "
-"Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL, debian-storage-"
-"policy-fixed-drives.fdi is not available anymore and the previous trick that "
-"consisted to remove this file to enable automounting of fixed drives as a "
-"consequence is obsolete. Eventually, it will be possible to combine HAL and "
-"PolicyKit to enable different permissions and actions to achieve advanced "
-"(auto)mounting for non-root users. Until then, because the live scripts are "
-"only touching to the fstab to add a swap partition if discovered at boot "
-"time, the only way to have fixed drives mounted automatically is to use a "
-"script that will populate the fstab file at the end of the multiuser "
-"runlevel. To achieve this, you can do, for example, the following: download "
-"the https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-"
-"includes/sbin/diskmounter.sh script Create the chroot_local-includes/sbin "
-"directory, and move the script inside Make sure the script is executable "
-"(chmod +x diskmounter.sh) create the chroot_local-includes/etc/rc.local file "
-"and call the diskmounter from there (see this https://devel.goto10.org/svn/"
-"puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local When called "
-"correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32, HFS+ and "
-"NTFS partitions and mount them read-write, except for NTFS. This will change "
-"soon and an option will be available to use ntfs-3g to mount NTFS as read-"
-"write. comments, patches and other things about this script and issue: "
-"http://code.goto10.org/projects/puredyne/ticket/463"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:225
-msgid ""
-"Q: Boot fails with panic: can't open /scripts/live A: Add latest live-"
-"initramfs deb package into config/chroot_local-packages directory and "
-"rebuild."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:229
-msgid ""
-"Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref "
-"linkend=\"internalization\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:234
-msgid ""
-"Q: How do I get past boot prompt without a working keyboard? A: See "
-"Customizing the bootup process % FIXME: <xref linkend=\"bootup\"/> Note: "
-"Boot from an USB-HDD on an iMac with GRUB did not work."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:237
-msgid ""
-"Q: Can I serve the root image from a web or ftp server? A: Since live-"
-"initramfs 1.99, it should be possible to use the fetch= argument on the "
-"kernel command line. You can build a netboot image as usual, and when you "
-"are done edit the tftpboot/pxelinux.cfg/default file. Remove the references "
-"to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url "
-"where you placed the root image>. You have to include wget in the chroot. It "
-"could work for other boot methods as well. However, I am not sure the live "
-"scripts configure the network when booting from a CD or USB disk. #{$ "
-"lh_config --packages wget}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:240
-msgid ""
-"Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you "
-"are building an etch image (which was the default up to 2007/09/14) you have "
-"a very old version of casper which does not support quickreboot and possibly "
-"other boot parameters as well. You could configure your sources to use live-"
-"backports (see /usr/share/live-helper/examples/sources/live-backports) and "
-"switch to live-initramfs, or better yet, build a lenny image instead, which "
-"is the new default. #{$ lh_config --distribution lenny $ lh_config --"
-"initramfs live-initramfs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:243
-msgid ""
-"Q: How do I fix \"Could not find kernel image\" issue with syslinux "
-"bootloader? A: Add a binary local hook script to fix kernel and initrd path "
-"each time you build an image. e.g. config/binary_local-hooks/01-fix_syslinux."
-"sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:249
-msgid "SYSLINUXCFG=`find binary -type f -name syslinux.cfg`"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:252
-msgid ""
-"sed -i \"s|kernel /vmlinuz|kernel vmlinuz|g\" ${SYSLINUXCFG} sed -i \"s|"
-"initrd=/initrd|initrd=initrd|g\" ${SYSLINUXCFG}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:254
-msgid "$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:259
-msgid ""
-"Q: How do I use a newer kernel with lenny? A: A build with backports.org "
-"kernels will fail as that repository lacks the necessary module packages "
-"(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports http://"
-"unsupported.debian-maintainers.org/backports-kernel/ The quick way to "
-"success:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:268
-msgid ""
-"$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-"
-"modules-2.6' $ echo 'deb http://unsupported.debian-maintainers.org/backports-"
-"kernel/ ./' > config/chroot_sources/backports-kernel.chroot $ echo 'deb "
-"http://unsupported.debian-maintainers.org/backports-kernel/ ./' > config/"
-"chroot_sources/backports-kernel.binary $ wget http://unsupported.debian-"
-"maintainers.org/backports-kernel/archive-key.asc -O config/chroot_sources/"
-"backports-kernel.chroot.gpg $ wget http://unsupported.debian-maintainers.org/"
-"backports-kernel/archive-key.asc -O config/chroot_sources/backports-kernel."
-"binary.gpg $ lh_build }code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:271
-msgid ""
-"Q: How do I use a custom kernel? Is there a nice way of booting debian-live "
-"with a custom kernel (not in an apt repo)? A: Copy it into config/"
-"chroot_local-packages and set LH_LINUX_PACKAGES=\"none\" or use lh config --"
-"linux-packages \" \" Don't forget to compile your kernel with an union "
-"filesystem (unionfs or aufs), squashfs modules, and initrd support. I can "
-"cause the kernel to be installed but it seems this happens later than grub/"
-"syslinux is configured so it's not listed and casper/ and the menu require "
-"munging. You need to follow the debian scheme, e.g. placing the files in /"
-"boot as vmlinuz-$version and initrd.img-$version etc. I personally wouldn't "
-"go that way which is too much of a hassle, and just use make-kpkg to produce "
-"custom kernel deb packages. They should integrate nicely if you just put "
-"them into config/chroot_local-packages and set LH_LINUX_PACKAGES=\"\". Hint: "
-"to work around an error, which lh_binary_syslinux will throw on custom "
-"kernels if there is not an 468/686 in the kernel-name, you need to set "
-"CONFIG_LOCALVERSION=\"-486\" or \"-686\" within the kernel configuration (-"
-"> General setup -> Local version set to -486 or -686) corresponding to "
-"LH_LINUX_FLAVOURS=\"\" or \"686\". this at least up till live-helper version "
-"1.0~a40-1 see http://lists.alioth.debian.org/pipermail/debian-live-"
-"devel/2007-July/001947.html and http://lists.alioth.debian.org/pipermail/"
-"debian-live-devel/2007-November/002581.html"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:274
-msgid ""
-"Q: How do I create a cross arch live CD image? A: In short: You can't. Read "
-"on: The procedure to create a live CD is based on creating a chroot that "
-"contains the files that will be finally available on the live CD. The live "
-"CD building procedure includes chrooting into the chroot dir and so some "
-"operations. chrooting means that the terminal you chroot on will behave as a "
-"different system so your real system and the chroot environment is decoupled "
-"somehow. Once the live CD scripts chroots into the chroot dir they have some "
-"operations to do inside that environment and your real system won't be able "
-"to run them unless you are using the same architecture. So you only are able "
-"to make live CD for the arch you run on. But this doesn't prevent you run "
-"qemu or some other machine emulator that make this possible."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:277
-msgid ""
-"Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That "
-"depends what you've changed between builds If, for example, you've built an "
-"iso image and you want a usb image, you only need to run #{lh_clean --binary}"
-"# before you run lh_build again. If you've changed anything in the chroot, "
-"you'll need to cleanup both chroot and binary with #{lh_clean}# before "
-"continuing"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:280
-msgid ""
-"Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in config/binary"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:283
-msgid ""
-"Q: How do I include different modules to load when the live system boots? A: "
-"Configure config/chroot_local-includes/etc/initramfs-tools/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:285
-msgid ""
-"The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default "
-"initramfs.conf \"MODULES = most\". You may override that by supplying your "
-"own initramfs.conf, or else just add your own modules, e.g."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:290
-msgid ""
-"mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo \"atl2\" >> "
-"config/chroot_local-includes/etc/initramfs-tools/modules"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:294
-msgid ""
-"Note: Even though initramfs.conf(5) says \"most adds all the framebuffer, "
-"acpi, file system, ide, sata, scsi and usb drivers\", it actually includes "
-"network drivers as well. See auto_add_modules() in /usr/share/initramfs-"
-"tools/hook-functions for the complete list."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:297
-msgid ""
-"Q: Can I have a splash screen? A: Yes you can. You will not know what is "
-"going on when the splash screen is active, it may fail to activate on some "
-"hardware or break X on other (both usplash and splashy use libdirectfb which "
-"does some evil voodoo and may break you graphics or input until you reboot). "
-"However, you can install and activate it just as you would on any other "
-"Debian system. To use splashy: 1. install splashy and read the README, the "
-"manpages are useless for setting it up. Add some parameters to your kernel "
-"command line, such as in your pxelinux configuration or in "
-"LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792 "
-"splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy, "
-"#{quiet}# to suppress most kernel messages that you cannot see anyway but "
-"would scroll past before splashy manages to paint the graphics on your "
-"screen. You might want to add splashy to the list of packages installed in "
-"your image: #{echo splashy > config/chroot_local-packageslists/splashy echo "
-"splashy-themes >> config/chroot_local-packageslists/splashy}# and select a "
-"theme:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:305
-msgid ""
-"echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s "
-"debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the "
-"ramdisk to include the splash screen echo update-initramfs -u -k all >> "
-"config/chroot_local-hooks/splashy chmod 755 config/chroot_local-hooks/splashy"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:309
-msgid ""
-"After you rebuild your live system you should observe a bluish splash screen "
-"while booting. Nothing happens while initramfs is running because there is "
-"no splashy support in initramfs-tools. Once the init starts the progress bar "
-"should start to fill. If #{vga=something}# sets a mode that your screen "
-"cannot show or your card cannot do vesa 2.0 (and thus you get plain text "
-"mode and no splashy) read the splashy faq."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:312
-msgid ""
-"Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the "
-"firmwares to the initrd image. You need to install the non-free package "
-"\"firmware-bnx2\". Uncompress your initrd image, then copy files:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:317
-msgid ""
-"cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw /"
-"lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw "
-"${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:321
-msgid "Recompress your initrd image and boot: it works!"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:323
-msgid ""
-"Q: X is broken (the system boots, messages scroll by, and then the screen "
-"goes blank). What do I do? A: On my system starting X completely disables "
-"graphics so that I do not see anything even after X bails out and I am back "
-"to the console. To prevent this you can change the driver Xorg uses."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:325
-msgid ""
-"If you have a working splash screen or at least graphical console you can "
-"use #{live xdriver=fbdev}# when booting the live system (instead of just "
-"enter). Another driver you might want to try is #{vesa}#. If all fails you "
-"might try to set xdriver to some wrong value so that Xorg fails to start and "
-"you can examine the system while you still see something on the console. #"
-"{live xdriver=none}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:328
-msgid ""
-"Q: How can I get Debian first stable versions? A: I'm developing software "
-"and testing it on Live-CD. Thanks for the LiveCD project. To be sure my "
-"development is fully compatible with the \"etch\" version, I need the same "
-"scenario when Debian GNU/Linux 4.0 was published as stable (I believe "
-"2007.04.08). If there was some bug on 2007.04.08 that was corrected one week "
-"later, I need to test software foreseeing that scenario without the bug "
-"solved."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:331
-msgid ""
-"Q: I get \"fopen: Permission denied\"-warnings from apt on building/at the "
-"live-system A: That's a harmless bug in apt. However, if you want to get off "
-"this warnings in the live-system, add a file in chroot_local-hooks with "
-"follow row:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:335
-msgid "chown -R man.man /var/cache/man"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:340
-msgid ""
-"Q: Why I always fail during \"Retrieving Packages\" stage when running "
-"lh_build? I have already set apt-http-proxy and so on. A: lh_build "
-"retrieves packages via wget, as a result you need to enable the proxy "
-"settings in /etc/wgetrc before running lh_build."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:343
-msgid ""
-"Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system "
-"boots, so it's useless to put modifed Xorg.conf in config/choort_local-"
-"includes/etc/X11, because it will be overwritten during boot. However, you "
-"can edit /usr/bin/dexconf, which generate xorg.conf during boot, so the "
-"result will be modified Xorg.conf. The modified dexconf has to be put in "
-"config/choort_local-includes/usr/bin. e.g.: you can configure Xorg.conf for "
-"two or more keyboards layouts with alt+shift toggle by editing dexconf and "
-"replacing the line:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:347
-msgid "Option \"XkbLayout\" \"$XKB_LAYOUT\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:351
-msgid "with the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:356
-msgid ""
-"Option \"XkbLayout\" \"us,il\" Option \"XkbOptions\" \"grp:alt_shift_toggle,"
-"grp_led:scroll\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:360
-msgid "when \"us,il\" are the wanted keyboard layouts."
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:362
-msgid ""
-"You can force default screen resulotion (e.g. 1024*768) by adding the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:368
-#, no-wrap
-msgid ""
-"SubSection \"Display\"\n"
-" Modes \"1024x768\"\n"
-"EndSubSection\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:372
-msgid "between the lines:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:379
-#, no-wrap
-msgid ""
-"Section \"Screen\"\n"
-" Identifier \"Default Screen\"\n"
-" Monitor \"Configured Monitor\"\n"
-"EndSection\"\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:383
-msgid ""
-"Q: Where are the build parameters for the prebuilt images A: See http://live."
-"debian.net/README.images."
-msgstr ""
diff --git a/manual/pot/other_howtos.ssi.pot b/manual/pot/other_howtos.ssi.pot
deleted file mode 100644
index aff720e..0000000
--- a/manual/pot/other_howtos.ssi.pot
+++ /dev/null
@@ -1,379 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
-"Language: \n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr ""
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:2
-msgid "B~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:4
-msgid "1~ Howtos"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:6
-msgid "2~ ISO"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:8
-msgid ""
-"Generating a Debian Live CD is very simple. You need to have live-helper "
-"(package available in Debian sid and lenny), and Debootstrap (or "
-"cdebootstrap) from etch or newer."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:10
-msgid "3~ Install live-helper"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:12
-msgid "#{apt-get install live-helper}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:14
-msgid "3~ Configure the current working directory with lh_config"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:18
-msgid "lh_config -b iso -a $ARCH"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:22
-msgid "where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:24
-msgid "#{-b}# flag is used to be sure to obtain image in ISO format."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:26
-msgid "3~ Build the image with lh_build:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:28
-msgid "Execute lh_build as root: #{lh_build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:30
-msgid ""
-"The command above will create the basic image, containing just the Debian "
-"standard system (with no X at all)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:32
-msgid ""
-"If you want to have any of the Desktop environments on your livecd, #{ls /"
-"usr/share/live-helper/lists}# will show a number of available package Lists "
-"to choose from, e.g. #{lh_config -p gnome-desktop}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:34
-msgid "More examples are listed at DebianLive/Examples."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:37
-msgid ""
-"See packages for help configuring a local Debian Mirror and other aspects of "
-"the live system. % FIXME: <xref linkend=\"packages\"/>"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:39
-msgid "3~ Test the image"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:41
-msgid "If you have qemu installed, you can boot the image with:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:45
-msgid "qemu -cdrom binary.iso"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:49
-msgid "If you have also kqemu installed, you can add #{-kernel-kqemu}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:51
-msgid "2~ ISO_(multiarch)"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:53
-msgid ""
-"Multiple machine boot CDs can be created with the following manual "
-"procedure. This procedure has been successfully used to create a single CD "
-"which is bootable on alpha, i386, pmax, and sparc. It should be possible to "
-"also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:55
-msgid ""
-"To create a CD which is bootable by multiple architectures, use the "
-"following steps in this order. Please note that the order is critical."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:57
-msgid ""
-"Make sure you have all the required files including the various kernels and "
-"boot programs listed in the individual machine sections."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:59
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.pmax "
-"and include the pmax bootxx_cd9660 file there. For example, /cdsources/usr/"
-"mdec.pmax/bootxx_cd9660."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:61
-msgid ""
-"Include a directory somewhere in the cdsources directory called mdec.vax and "
-"include the vax xxboot file there. For example, #{cdsources/usr/mdec.vax/"
-"xxboot.}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:63
-msgid "Include the macppc ofwboot.xcf bootloader in /cdsources."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:65
-msgid ""
-"Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b i386/"
-"installation/floppy/boot-big.fs \\ -c boot.catalog -l -J -r -L /cdsources "
-"2>&1 | tee /tmp/mkisofs.log exit}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:67
-msgid ""
-"Note: The appearance of the -v flag twice is required. If you are making a "
-"bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs -"
-"part in the parameters for mkisofs."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:69
-msgid ""
-"Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3 "
-"bootblocks. Alternatively, install the sysutils/mksunbootcd package on your "
-"favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs "
-"boot-sun4m.fs boot-sun3.fs}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:71
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/pmax to install the pmax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"pmax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:73
-msgid ""
-"#{installboot -m pmax -v -o append,sunsum output.iso /tmp/mdec.pmax/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:75
-msgid ""
-"The -o append,sunsum option appends the first stage boot block to the end of "
-"the ISO file system, and restores the checksum used when booting on a sun."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:77
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/vax to install the vax "
-"bootblocks. Note that in order to coexist with other NetBSD boot blocks, the "
-"vax boot block is appended to the end of the ISO file system."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:79
-msgid "installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:81
-msgid "(See the pmax entry above for an explanation of the flags)."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:83
-msgid ""
-"Run the installboot(8) program targeted for NetBSD/alpha to install the "
-"alpha bootblocks."
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:85
-msgid ""
-"#{installboot -m alpha -v -o append,sunsum output.iso /tmp/mdec.alpha/"
-"bootxx_cd9660}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_howtos.ssi:86
-msgid ""
-"Note: The alpha installboot must occur after the others, because currently "
-"it's the only machine dependent back-end for installboot(8) that can "
-"calculate the alpha checksum. (See the pmax entry above for an explanation "
-"of the flags)."
-msgstr ""
diff --git a/manual/pot/other_use-cases.ssi.pot b/manual/pot/other_use-cases.ssi.pot
deleted file mode 100644
index 1b83eac..0000000
--- a/manual/pot/other_use-cases.ssi.pot
+++ /dev/null
@@ -1,379 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the live-manual package.
-# FIRST AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-10-03 20:30+0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
-"Language-Team: LANGUAGE <LL at li.org>\n"
-"Language: \n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=CHARSET\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. type: Plain text
-#: en/about_manual.ssi:82 en/about_manual.ssi:90 en/about_manual.ssi:98
-#: en/about_manual.ssi:110 en/about_manual.ssi:121 en/about_manual.ssi:134
-#: en/about_manual.ssi:142 en/about_manual.ssi:150 en/about_manual.ssi:158
-#: en/other_coding-style.ssi:28 en/other_coding-style.ssi:38
-#: en/other_coding-style.ssi:51 en/other_coding-style.ssi:61
-#: en/other_coding-style.ssi:88 en/other_coding-style.ssi:96
-#: en/other_coding-style.ssi:106 en/other_coding-style.ssi:117
-#: en/other_common-tasks.ssi:32 en/other_customization-backports.ssi:8
-#: en/other_customization-bootup.ssi:30 en/other_customization-bootup.ssi:39
-#: en/other_customization-internationalization.ssi:10
-#: en/other_customization-internationalization.ssi:18
-#: en/other_customization-internationalization.ssi:26
-#: en/other_customization-internationalization.ssi:34
-#: en/other_customization-internationalization.ssi:46 en/other_faq.ssi:41
-#: en/other_faq.ssi:83 en/other_faq.ssi:103 en/other_faq.ssi:117
-#: en/other_faq.ssi:137 en/other_faq.ssi:151 en/other_faq.ssi:198
-#: en/other_faq.ssi:245 en/other_faq.ssi:261 en/other_faq.ssi:287
-#: en/other_faq.ssi:299 en/other_faq.ssi:314 en/other_faq.ssi:333
-#: en/other_faq.ssi:345 en/other_faq.ssi:353 en/other_faq.ssi:364
-#: en/other_faq.ssi:374 en/other_howtos.ssi:16 en/other_howtos.ssi:43
-#: en/other_live-environment.ssi:14 en/other_live-environment.ssi:30
-#: en/other_live-environment.ssi:51 en/other_live-environment.ssi:61
-#: en/other_live-environment.ssi:69 en/other_live-environment.ssi:77
-#: en/other_live-environment.ssi:85 en/other_live-environment.ssi:93
-#: en/other_live-environment.ssi:116 en/other_live-environment.ssi:124
-#: en/other_live-environment.ssi:133 en/other_procedures.ssi:12
-#: en/other_procedures.ssi:46 en/other_procedures.ssi:58
-#: en/other_use-cases.ssi:24 en/other_use-cases.ssi:49
-#: en/other_use-cases.ssi:75 en/other_use-cases.ssi:103
-#: en/other_use-cases.ssi:111 en/user_basics.ssi:36 en/user_basics.ssi:48
-#: en/user_basics.ssi:62 en/user_basics.ssi:74 en/user_basics.ssi:88
-#: en/user_basics.ssi:104 en/user_basics.ssi:112 en/user_basics.ssi:120
-#: en/user_basics.ssi:130 en/user_basics.ssi:142 en/user_basics.ssi:154
-#: en/user_basics.ssi:162 en/user_basics.ssi:170 en/user_basics.ssi:184
-#: en/user_basics.ssi:192 en/user_basics.ssi:202 en/user_basics.ssi:222
-#: en/user_basics.ssi:255 en/user_basics.ssi:271 en/user_basics.ssi:279
-#: en/user_basics.ssi:299 en/user_basics.ssi:324
-#: en/user_customization-contents.ssi:34 en/user_customization-contents.ssi:43
-#: en/user_customization-contents.ssi:66 en/user_customization-packages.ssi:16
-#: en/user_customization-packages.ssi:24 en/user_customization-packages.ssi:36
-#: en/user_customization-packages.ssi:45 en/user_customization-packages.ssi:59
-#: en/user_customization-packages.ssi:73
-#: en/user_customization-packages.ssi:103
-#: en/user_customization-packages.ssi:111
-#: en/user_customization-packages.ssi:131
-#: en/user_customization-packages.ssi:160
-#: en/user_customization-packages.ssi:170
-#: en/user_customization-packages.ssi:180
-#: en/user_customization-packages.ssi:190 en/user_installation.ssi:38
-#: en/user_installation.ssi:46 en/user_installation.ssi:56
-#: en/user_installation.ssi:64 en/user_installation.ssi:76
-#: en/user_installation.ssi:84 en/user_installation.ssi:105
-#: en/user_installation.ssi:119 en/user_installation.ssi:136
-#: en/user_overview.ssi:60 en/user_overview.ssi:104 en/user_overview.ssi:112
-msgid "code{"
-msgstr ""
-
-#. type: Plain text
-#: en/about_manual.ssi:86 en/about_manual.ssi:94 en/about_manual.ssi:102
-#: en/about_manual.ssi:117 en/about_manual.ssi:130 en/about_manual.ssi:138
-#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:161
-#: en/other_coding-style.ssi:34 en/other_coding-style.ssi:45
-#: en/other_coding-style.ssi:57 en/other_coding-style.ssi:68
-#: en/other_coding-style.ssi:92 en/other_coding-style.ssi:100
-#: en/other_coding-style.ssi:113 en/other_coding-style.ssi:124
-#: en/other_common-tasks.ssi:36 en/other_customization-backports.ssi:16
-#: en/other_customization-bootup.ssi:35 en/other_customization-bootup.ssi:48
-#: en/other_customization-internationalization.ssi:14
-#: en/other_customization-internationalization.ssi:22
-#: en/other_customization-internationalization.ssi:30
-#: en/other_customization-internationalization.ssi:38
-#: en/other_customization-internationalization.ssi:50 en/other_faq.ssi:37
-#: en/other_faq.ssi:46 en/other_faq.ssi:92 en/other_faq.ssi:108
-#: en/other_faq.ssi:141 en/other_faq.ssi:155 en/other_faq.ssi:207
-#: en/other_faq.ssi:256 en/other_faq.ssi:292 en/other_faq.ssi:307
-#: en/other_faq.ssi:319 en/other_faq.ssi:337 en/other_faq.ssi:349
-#: en/other_faq.ssi:358 en/other_faq.ssi:370 en/other_faq.ssi:381
-#: en/other_howtos.ssi:20 en/other_howtos.ssi:47
-#: en/other_live-environment.ssi:18 en/other_live-environment.ssi:34
-#: en/other_live-environment.ssi:55 en/other_live-environment.ssi:65
-#: en/other_live-environment.ssi:73 en/other_live-environment.ssi:81
-#: en/other_live-environment.ssi:89 en/other_live-environment.ssi:97
-#: en/other_live-environment.ssi:120 en/other_live-environment.ssi:129
-#: en/other_live-environment.ssi:138 en/other_procedures.ssi:16
-#: en/other_procedures.ssi:54 en/other_procedures.ssi:131
-#: en/other_use-cases.ssi:33 en/other_use-cases.ssi:69
-#: en/other_use-cases.ssi:97 en/other_use-cases.ssi:107
-#: en/other_use-cases.ssi:137 en/user_basics.ssi:40 en/user_basics.ssi:52
-#: en/user_basics.ssi:68 en/user_basics.ssi:78 en/user_basics.ssi:94
-#: en/user_basics.ssi:108 en/user_basics.ssi:116 en/user_basics.ssi:124
-#: en/user_basics.ssi:134 en/user_basics.ssi:148 en/user_basics.ssi:158
-#: en/user_basics.ssi:166 en/user_basics.ssi:174 en/user_basics.ssi:188
-#: en/user_basics.ssi:196 en/user_basics.ssi:206 en/user_basics.ssi:247
-#: en/user_basics.ssi:275 en/user_basics.ssi:283 en/user_basics.ssi:310
-#: en/user_basics.ssi:349 en/user_customization-contents.ssi:39
-#: en/user_customization-contents.ssi:54 en/user_customization-contents.ssi:70
-#: en/user_customization-packages.ssi:20 en/user_customization-packages.ssi:28
-#: en/user_customization-packages.ssi:41 en/user_customization-packages.ssi:49
-#: en/user_customization-packages.ssi:63 en/user_customization-packages.ssi:77
-#: en/user_customization-packages.ssi:107
-#: en/user_customization-packages.ssi:115
-#: en/user_customization-packages.ssi:135
-#: en/user_customization-packages.ssi:166
-#: en/user_customization-packages.ssi:176
-#: en/user_customization-packages.ssi:186
-#: en/user_customization-packages.ssi:196 en/user_installation.ssi:42
-#: en/user_installation.ssi:50 en/user_installation.ssi:60
-#: en/user_installation.ssi:72 en/user_installation.ssi:80
-#: en/user_installation.ssi:109 en/user_installation.ssi:124
-#: en/user_installation.ssi:139 en/user_overview.ssi:98
-#: en/user_overview.ssi:108 en/user_overview.ssi:116
-msgid "}code"
-msgstr ""
-
-#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/other_use-cases.ssi:26
-#: en/other_use-cases.ssi:77
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:2
-msgid "B~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:4
-msgid "1~ Use Cases"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:6
-msgid "This chapter is for users to document their use cases with Debian Live."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:8
-msgid "2~ VNC Kiosk Client"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:10
-msgid "Create an image with live-helper to boot directly to a VNC server."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:12
-msgid "_* Make a build directory: #{$ mkdir vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:14
-msgid "_* Move to the build directory: #{$ cd vncBuild}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:16
-msgid ""
-"Example to config the build directory to include gdm metacity "
-"xtightvncviewer: #{$ lh config --packages \"gdm metacity xtightvncviewer\"}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:18
-msgid ""
-"Create a folder /etc/skel folder for a custom .xsession for the default "
-"user: #{$ mkdir -p config/chroot_local-includes/etc/skel}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:20
-msgid ""
-"Create the .xsession for the default user: #{$ touch config/chroot_local-"
-"includes/etc/skel/.xsession}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:22
-msgid ""
-"Edit the .xsession file to launch metacity and start xvncviewer with "
-"something similar to the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:29
-msgid "/usr/bin/metacity & /usr/bin/vncviewer xxx.xxx.xxx.xxx:PORT"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:31
-msgid "exit"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:35
-msgid "_* Build the image: #{# lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:37 en/other_use-cases.ssi:138
-msgid "_* Enjoy."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:39
-msgid "2~ VMWare-Player Sessions"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:41
-msgid ""
-"Create an image with live-helper to boot directly to a specifiv VMWare "
-"session."
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:43
-msgid "_* Make a build directory: #{$ mkdir VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:45
-msgid "_* Move to the build directory: #{$ cd VMWare-Player}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:47
-msgid ""
-"_* Example to config the build directory to include gdm metacity "
-"xtightvncviewer:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:67
-#, no-wrap
-msgid ""
-"$ lh config --apt apt \\\n"
-" ---apt-recommends disabled \\\n"
-" --archive-areas \"main\" \\\n"
-" --binary-images iso \\\n"
-" --binary-indices none \\\n"
-" --syslinux-menu vesamenu \\\n"
-" ---bootappend-live \"persistent quickreboot\" \\\n"
-" ---bootappend-install \"-- plainroot persistent video=vesa:ywrap,mtrr vga=788 quickreboot quiet live-config\" \\\n"
-" ---debian-installer live \\\n"
-" ---distribution lenny \\\n"
-" ---hostname vmare-player-firmware \\\n"
-" ---includes none \\\n"
-" ---linux-flavours 686 \\\n"
-" ---packages-lists \"gnome-core\" \\\n"
-" ---packages \"gcc gparted linux-headers-2.6-\\${LH_LINUX_FLAVOURS} live-config-staging make metacity rsync wireless-tools\" \\\n"
-" ---repositories live.debian.net \\\n"
-" ---win32-loader disabled\n"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:71
-msgid ""
-"_* Create the 01-vmware-player hook: #{$ touch config/chroot_local-hooks/01-"
-"vmware-player.sh}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:73
-msgid ""
-"Edit the 01-vmware-player hook to launch the VMWare-Player. The hook should "
-"look something like the below:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:80
-msgid ""
-"_URL=\"http://archive.debian-maintainers.org/vmware/other/vmware-player/\" "
-"_VMPLAYER_VERSION=\"VMware-Player.i386.bundle\""
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:83
-msgid "echo \"I: Starting script for install of VMWare Player.\" cd /root"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:86
-msgid ""
-"echo \"I: Beginning download of ${_VMPLAYER_VERSION} from ${_URL} .\" wget "
-"${_URL}${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:89
-msgid ""
-"echo \"I: Starting install of VMWare Player.\" sh /root/${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:92
-msgid ""
-"echo \"I: Cleaning up the VMWare Player download.\" rm /root/"
-"${_VMPLAYER_VERSION}"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:95
-msgid "#echo \"I: Starting interactive shell.\" #bash"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:99
-msgid ""
-"_* Build the image (note that during the build the VMWare-Player will prompt "
-"you to install or cancel): #{#lh build}#"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:101
-msgid ""
-"_* After the build you will have an image you can boot live or install as "
-"firmware. The package live-config-staging is the package that installs the "
-"ability to utilize the VMWare-Player by calling live-config.vmware-player as "
-"a boot parameter in the following form:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:105
-msgid "live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:109
-msgid "Notes from the 900-vmware-player file are as follows:"
-msgstr ""
-
-#. type: Plain text
-#: en/other_use-cases.ssi:135
-#, no-wrap
-msgid ""
-"# The script tests for boot parameter of\n"
-"# live-config.vmware-player=ACTION:IMAGEPATH:VMXNAME\n"
-"#\n"
-"# ACTION: The operation to perform on the workstation (none|scratch)\n"
-"# IMAGEPATH: The folder path to the VMware image you want to run.\n"
-"# VMXNAME: The name of the VMware image you want to run.\n"
-"#\n"
-"# Notes:To use this file with WMWare images you will need to have a few things\n"
-"# setup:\n"
-"#\n"
-"# 1. The VMware Player needs to be installed in the image.\n"
-"# 2. This script uses (s|h)da1 for writing image data, and is used as a scratch\n"
-"# space. This scratch space should be a file system with linux permissions\n"
-"# such as ext2.\n"
-"# 3. VMware image(s) should be in a mounted folder and setup as follows:\n"
-"# - Image(s) set to snapshot mode.\n"
-"# - For each image, the image folder needs to have a file called\n"
-"# image-release with a variable CRELEASE. An example: CRELEASE=\"1.0.0\"\n"
-"#\n"
-"# The image-release file is used by the image maintainer and this script to tell\n"
-"# workstation(s) using a given image, to erase locally stored vmware image files\n"
-"# and setup with the newly configure image. The operation of erasing locally\n"
-"# stored vmare image files, is referred to as a scratch.\n"
-msgstr ""
diff --git a/manual/pot/user_examples.ssi.pot b/manual/pot/user_examples.ssi.pot
index 10c6941..37d04f9 100644
--- a/manual/pot/user_examples.ssi.pot
+++ b/manual/pot/user_examples.ssi.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-12-11 13:57-0400\n"
+"POT-Creation-Date: 2010-12-11 14:12-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -20,13 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/other_faq.ssi:41 en/other_faq.ssi:83
-#: en/other_faq.ssi:103 en/other_faq.ssi:117 en/other_faq.ssi:137
-#: en/other_faq.ssi:151 en/other_faq.ssi:198 en/other_faq.ssi:245
-#: en/other_faq.ssi:261 en/other_faq.ssi:287 en/other_faq.ssi:299
-#: en/other_faq.ssi:314 en/other_faq.ssi:333 en/other_faq.ssi:345
-#: en/other_faq.ssi:353 en/other_faq.ssi:364 en/other_faq.ssi:374
-#: en/other_howtos.ssi:16 en/other_howtos.ssi:43 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:58
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -87,13 +81,7 @@ msgstr ""
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/other_faq.ssi:37 en/other_faq.ssi:46
-#: en/other_faq.ssi:92 en/other_faq.ssi:108 en/other_faq.ssi:141
-#: en/other_faq.ssi:155 en/other_faq.ssi:207 en/other_faq.ssi:256
-#: en/other_faq.ssi:292 en/other_faq.ssi:307 en/other_faq.ssi:319
-#: en/other_faq.ssi:337 en/other_faq.ssi:349 en/other_faq.ssi:358
-#: en/other_faq.ssi:370 en/other_faq.ssi:381 en/other_howtos.ssi:20
-#: en/other_howtos.ssi:47 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:62
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -150,12 +138,6 @@ msgid "}code"
msgstr ""
#. type: Plain text
-#: en/other_faq.ssi:85 en/other_faq.ssi:247 en/user_examples.ssi:92
-#: en/user_examples.ssi:141 en/user_examples.ssi:190
-msgid "#!/bin/sh"
-msgstr ""
-
-#. type: Plain text
#: en/user_basics.ssi:44 en/user_basics.ssi:120 en/user_basics.ssi:204
#: en/user_examples.ssi:109 en/user_examples.ssi:156
msgid "# lb build"
@@ -360,6 +342,11 @@ msgid "Edit #{auto/config}# to read as follows:"
msgstr ""
#. type: Plain text
+#: en/user_examples.ssi:92 en/user_examples.ssi:141 en/user_examples.ssi:190
+msgid "#!/bin/sh"
+msgstr ""
+
+#. type: Plain text
#: en/user_examples.ssi:99
#, no-wrap
msgid ""
diff --git a/manual/pt_BR/live-manual.ssm b/manual/pt_BR/live-manual.ssm
index 2ec9427..60a8440 100644
--- a/manual/pt_BR/live-manual.ssm
+++ b/manual/pt_BR/live-manual.ssm
@@ -63,6 +63,3 @@
<< user_examples.ssi
-% << other_faq.ssi
-
-% << other_howtos.ssi
diff --git a/manual/pt_BR/other_faq.ssi b/manual/pt_BR/other_faq.ssi
deleted file mode 100644
index f754913..0000000
--- a/manual/pt_BR/other_faq.ssi
+++ /dev/null
@@ -1,545 +0,0 @@
-B~ Frequently asked questions (FAQ)
-
-1~ Frequently asked questions (FAQ)
-
-Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A:
-See "Copying USB/HDD image to a USB stick" % FIXME: <xref
-linkend="image_copying"/>
-
-Q: How do I log my build? A: You could use script, screen or tee: #{$
-lh_build 2>&1 | tee build.log}#
-
-Q: How can I convert an already installed standard Debian partition into a
-Debian Live system? A: Save the list of installed packages and load it into
-your new Debian Live System. Copy your /etc to config/chroot_local-includes
-
-Q: What does 'losetup: could not find any free loop device' mean and how do
-I fix it? A: Loop devices are used during the build; there probably aren't
-any free if you've aborted several builds. Something like: for l in
-/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6
-/dev/loop7 ; do losetup -d $l ; done should rectify the situation (assuming
-all loop devices in use were created by lh_build; if in doubt, check the
-contents of each loop device before deleting them with losetup -d).
-
-Q: How do I launch an interactive shell during the chroot stage? A: To
-enable interactive shell: #{$ lh_config --interactive shell}# To continue
-the build process: #{# logout}# or #{# exit}# To disable interactive shell,
-set LH_INTERACTIVE to "disabled" in config/chroot.
-
-Q: What is the root /user password? A: The user password for the live user
-is 'live'. By default, there is not any root password. You can switch to
-root with ${sudo -i}# or set a password for root with #{sudo passwd}#
-
-Q: How do I change root or any user password? A: Add a chroot local hook
-script to change root or any user password each time you build an image.
-e.g. config/chroot_local-hooks/01-update_password.sh to set root password to
-"nopasswd"
-
-code{ #!/bin/sh
-
-echo "I: update password" echo "root:nopasswd" | chpasswd
-
-$ chmod +x config/chroot_local-hooks/01-update_password.sh
-
-}code
-
-Note for live user; you need to copy the
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser your build folder:
-
-code{
-
-mkdir -p
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-
-}code
-
-Note: Then edit the
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-and paste in the new user_crypted password that you make with: #{echo
-"newlivepass" | mkpasswd -s}#
-
-Or add an hook file in config/chroot_local-hooks/ with something like the
-below:
-
-code{ #!/bin/sh
-
-# Change the autogenerated user password to "debianlive"
-plain_password="debianlive" password=$(echo "${plain_password}" | mkpasswd
--s)
-
-sed -i -e 's/\(user_crypted=\)\(.*\)\( #.*\)/\1\"'${password}'\"\3/'
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-
-update-initramfs -tu -kall }code
-
-The latter (hook model) could be more future proof than the former solution
-since it modifies just one string selectively but it requires the package
-"whois" to be installed on the target system (for mkpasswd) or that you
-generate the $password string not at build time and include it crypted in
-the above script.
-
-Q: How to disable autologin? A1: use the commandline parameter #{lh config
---bootappend-live "noautologin"}# A2: You need to set boot=noautologin
-noxautologin as described in man live-initramfs If you boot via TFTP you
-want to insert the option to pxelinux.cfg/default
-
-Q: How do I change default hostname or username? A: To change default
-hostname or username: #{$ lh_config --hostname myhostname $ lh_config
---username myusername}#
-
-Q: How do I make the final image smaller? A: Clean orphaned apps/libs:
-Install package "deborphan" and then run 'sudo deborphan -n' . Delete
-unwanted packages. Remove the apt cache. Purge unwanted locales (see
-"localepurge" package).
-
-Q: How do I customize bash-config permanently (aliases, bash-completion
-etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc
-
-Q: How do I disable services permanently? (Be careful!) A: Add a chroot
-local hook script to disable a service each time you build an image:
-e.g. config/chroot_local-hooks/01-disable_service.sh
-
-code{
-
-#!/bin/sh
-
-echo "I: disable service" update-rc.d -f service_name remove
-
-$ chmod +x config/chroot_local-hooks/01-disable_service.sh
-
-}code
-
-Q: How do I enable | disable the md5checksum at the ISO building? A:
-#{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value.
-
-Q: How to disable the generation of the .tar.gz file? A: #{lh_config
---net-tarball none|gzip}# Or change the LH_NET_TARBALL value. (only
-available in snapsshot version at the moment 2008/Feb/28)
-
-Q: How do I "build a new image"? A: Run commands:
-
-code{
-
-$ sudo lh_clean --binary $ sudo lh_build
-
-}code
-
-Hint: If the configuration had changed you should leave "--binary" out. This
-will clean your chroot directory too.
-
-Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages
-you want.
-
-Create /home/$USERNAME/.dmrc file (default username is "user").
-
-code{
-
-$ cat .dmrc [Desktop] Session=fluxbox }code
-
-Note: .dmrc is owned by $USERNAME:$USERNAME.
-
-See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at
-http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD
-
-Q: How do I use custom repositories? A: See
-http://wiki.debian.org/DebianLive/Configuration
-
-Q: How do I customize the artwork for the live CD (grub or syslinux boot
-splash, usplash, etc.)? A: See
-http://wiki.debian.org/DebianLive/Howto/Custom_Artwork
-
-Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look?
-A: Start the live system in qemu:
-
-code{
-
-$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22
-
-}code
-
-Note: the -redir argument must be changed to meet your needs
-
-Q: How do I execute a custom shell script inside the chroot system after the
-chroot stage? A: Add your script in config/chroot_local-hooks.
-
-Q: How do I add a script running immediately after all other scripts when
-the live system boots? A: Add your script in
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99scrip
-
-code{
-
-$ chmod +x
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99script
-
-}code
-
-Note: The hook script must be executable. Do not forget to lh_clean --chroot
-after making this change before you build again.
-
-You must also use the example script
-/usr/share/live-helper/examples/hooks/update-initramfs.sh to ensure your
-script gets built into the initramfs (read the comment header for
-instructions).
-
-Q: How do I add software not in Debian ? A: See Customizing package
-installation % FIXME: <xref linkend="packages"/>
-
-Q: What is the manifest with Ubuntu used for? A: Manifest is just the
-package list, which ubuntu does $something with. Don't worry about it.
-
-Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude.
-
-Q: Do I need to write the image on USB stick to test it? A: you must use
-qemu >= 0.8.
-
-Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs.
-
-Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed
-something else entirely? A: It is not. It is a package list, not a debconf
-preseeding.
-
-Q: What is the difference between standard and minimal? A: standard:
-packages of priority standard and higher; minimal: packages of priority
-essential and higher;
-
-Q: What can the sections be used for? Aren't they BIG? A: Someone maybe
-wants to include packages from contrib or non-free.
-
-Q: memtest86+ ... is that used? A: Yes
-
-Q: How do I build using predefined packages lists? A: e.g. to build using
-standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo
-lh_build}# Note: The packages lists can be found in
-/usr/share/live-helper/lists/ directory.
-
-Q: How do I rebuild without downloading all the packages again? A: All
-packages are cached in cache subdirectory. They remain until a clean purge:
-#{$ sudo lh_clean --purge}# You do not have to do anything to prevent
-packages from being re-downloaded. You need to remember to clean whichever
-stages you want to rebuild first. e.g. to rebuild from the cached bootstrap,
-chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#
-
-Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make
-a boot CD with grub, configured to boot from a debian-live kernel copied on
-the cd structure #{$ mkdir -p iso/boot/grub && cp
-/usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub && cp chroot/boot/*
-iso/boot/}# Create iso/boot/grub/menu.lst:
-
-code{
-
-default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd)
-kernel /boot/vmlinuz boot=live initrd /boot/initrd.img
-
-}code
-
-Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito
--no-emul-boot \ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn
-the image.
-
-Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A:
-If you have a floppy drive, you may be able to use it, otherwise you will
-need to use loadlin/grub4dos/win32-loader. If you have a second system to
-serve up the image over the network, See
-http://wiki.debian.org/DebianLive/Howto/Creating_a_Netboot_Image
-
-Q: The X configuration does not seems to work, the resolution is too
-low. What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend
-xdebconf && lh_config --packages xdebconfigurator}#
-
-Q: Apache has problems with static files A: Sendfile does not work well on
-the unionfs used by Debian Live. Add the following to apache's
-configuration: #{EnableSendfile off}#
-
-Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right
-now the best is to use a script that will populate the fstab when the CD is
-booting. Such a script can be found at
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh.
-A proper solution based on HAL will be described here in a hopefully near
-future. A: Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL,
-debian-storage-policy-fixed-drives.fdi is not available anymore and the
-previous trick that consisted to remove this file to enable automounting of
-fixed drives as a consequence is obsolete. Eventually, it will be possible
-to combine HAL and PolicyKit to enable different permissions and actions to
-achieve advanced (auto)mounting for non-root users. Until then, because the
-live scripts are only touching to the fstab to add a swap partition if
-discovered at boot time, the only way to have fixed drives mounted
-automatically is to use a script that will populate the fstab file at the
-end of the multiuser runlevel. To achieve this, you can do, for example, the
-following: download the
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh
-script Create the chroot_local-includes/sbin directory, and move the script
-inside Make sure the script is executable (chmod +x diskmounter.sh) create
-the chroot_local-includes/etc/rc.local file and call the diskmounter from
-there (see this
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local
-When called correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32,
-HFS+ and NTFS partitions and mount them read-write, except for NTFS. This
-will change soon and an option will be available to use ntfs-3g to mount
-NTFS as read-write. comments, patches and other things about this script and
-issue: http://code.goto10.org/projects/puredyne/ticket/463
-
-Q: Boot fails with panic: can't open /scripts/live A: Add latest
-live-initramfs deb package into config/chroot_local-packages directory and
-rebuild.
-
-Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref
-linkend="internalization"/>
-
-Q: How do I get past boot prompt without a working keyboard? A: See
-Customizing the bootup process % FIXME: <xref linkend="bootup"/> Note: Boot
-from an USB-HDD on an iMac with GRUB did not work.
-
-Q: Can I serve the root image from a web or ftp server? A: Since
-live-initramfs 1.99, it should be possible to use the fetch= argument on the
-kernel command line. You can build a netboot image as usual, and when you
-are done edit the tftpboot/pxelinux.cfg/default file. Remove the references
-to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url
-where you placed the root image>. You have to include wget in the chroot. It
-could work for other boot methods as well. However, I am not sure the live
-scripts configure the network when booting from a CD or USB disk. #{$
-lh_config --packages wget}#
-
-Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you
-are building an etch image (which was the default up to 2007/09/14) you have
-a very old version of casper which does not support quickreboot and possibly
-other boot parameters as well. You could configure your sources to use
-live-backports (see /usr/share/live-helper/examples/sources/live-backports)
-and switch to live-initramfs, or better yet, build a lenny image instead,
-which is the new default. #{$ lh_config --distribution lenny $ lh_config
---initramfs live-initramfs}#
-
-Q: How do I fix "Could not find kernel image" issue with syslinux
-bootloader? A: Add a binary local hook script to fix kernel and initrd path
-each time you build an
-image. e.g. config/binary_local-hooks/01-fix_syslinux.sh
-
-code{
-
-#!/bin/sh
-
-SYSLINUXCFG=`find binary -type f -name syslinux.cfg`
-
-sed -i "s|kernel /vmlinuz|kernel vmlinuz|g" ${SYSLINUXCFG} sed -i
-"s|initrd=/initrd|initrd=initrd|g" ${SYSLINUXCFG}
-
-$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh
-
-}code
-
-Q: How do I use a newer kernel with lenny? A: A build with backports.org
-kernels will fail as that repository lacks the necessary module packages
-(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports
-http://unsupported.debian-maintainers.org/backports-kernel/ The quick way to
-success:
-
-code{
-
-$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6
-squashfs-modules-2.6' $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.chroot $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.binary $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.chroot.gpg $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.binary.gpg $ lh_build }code
-
-Q: How do I use a custom kernel? Is there a nice way of booting debian-live
-with a custom kernel (not in an apt repo)? A: Copy it into
-config/chroot_local-packages and set LH_LINUX_PACKAGES="none" or use lh
-config --linux-packages " " Don't forget to compile your kernel with an
-union filesystem (unionfs or aufs), squashfs modules, and initrd support. I
-can cause the kernel to be installed but it seems this happens later than
-grub/syslinux is configured so it's not listed and casper/ and the menu
-require munging. You need to follow the debian scheme, e.g. placing the
-files in /boot as vmlinuz-$version and initrd.img-$version etc. I personally
-wouldn't go that way which is too much of a hassle, and just use make-kpkg
-to produce custom kernel deb packages. They should integrate nicely if you
-just put them into config/chroot_local-packages and set
-LH_LINUX_PACKAGES="". Hint: to work around an error, which
-lh_binary_syslinux will throw on custom kernels if there is not an 468/686
-in the kernel-name, you need to set CONFIG_LOCALVERSION="-486" or "-686"
-within the kernel configuration (-> General setup -> Local version set
-to -486 or -686) corresponding to LH_LINUX_FLAVOURS="" or "686". this at
-least up till live-helper version 1.0~a40-1 see
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-July/001947.html
-and
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-November/002581.html
-
-Q: How do I create a cross arch live CD image? A: In short: You can't. Read
-on: The procedure to create a live CD is based on creating a chroot that
-contains the files that will be finally available on the live CD. The live
-CD building procedure includes chrooting into the chroot dir and so some
-operations. chrooting means that the terminal you chroot on will behave as a
-different system so your real system and the chroot environment is decoupled
-somehow. Once the live CD scripts chroots into the chroot dir they have some
-operations to do inside that environment and your real system won't be able
-to run them unless you are using the same architecture. So you only are able
-to make live CD for the arch you run on. But this doesn't prevent you run
-qemu or some other machine emulator that make this possible.
-
-Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That
-depends what you've changed between builds If, for example, you've built an
-iso image and you want a usb image, you only need to run #{lh_clean
---binary}# before you run lh_build again. If you've changed anything in the
-chroot, you'll need to cleanup both chroot and binary with #{lh_clean}#
-before continuing
-
-Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in
-config/binary
-
-Q: How do I include different modules to load when the live system boots? A:
-Configure config/chroot_local-includes/etc/initramfs-tools/
-
-The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default
-initramfs.conf "MODULES = most". You may override that by supplying your own
-initramfs.conf, or else just add your own modules, e.g.
-
-code{
-
-mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo "atl2" >>
-config/chroot_local-includes/etc/initramfs-tools/modules
-
-}code
-
-Note: Even though initramfs.conf(5) says "most adds all the framebuffer,
-acpi, file system, ide, sata, scsi and usb drivers", it actually includes
-network drivers as well. See auto_add_modules() in
-/usr/share/initramfs-tools/hook-functions for the complete list.
-
-Q: Can I have a splash screen? A: Yes you can. You will not know what is
-going on when the splash screen is active, it may fail to activate on some
-hardware or break X on other (both usplash and splashy use libdirectfb which
-does some evil voodoo and may break you graphics or input until you
-reboot). However, you can install and activate it just as you would on any
-other Debian system. To use splashy: 1. install splashy and read the README,
-the manpages are useless for setting it up. Add some parameters to your
-kernel command line, such as in your pxelinux configuration or in
-LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792
-splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy,
-#{quiet}# to suppress most kernel messages that you cannot see anyway but
-would scroll past before splashy manages to paint the graphics on your
-screen. You might want to add splashy to the list of packages installed in
-your image: #{echo splashy > config/chroot_local-packageslists/splashy echo
-splashy-themes >> config/chroot_local-packageslists/splashy}# and select a
-theme:
-
-code{
-
-echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s
-debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the
-ramdisk to include the splash screen echo update-initramfs -u -k all >>
-config/chroot_local-hooks/splashy chmod 755
-config/chroot_local-hooks/splashy
-
-}code
-
-After you rebuild your live system you should observe a bluish splash screen
-while booting. Nothing happens while initramfs is running because there is
-no splashy support in initramfs-tools. Once the init starts the progress bar
-should start to fill. If #{vga=something}# sets a mode that your screen
-cannot show or your card cannot do vesa 2.0 (and thus you get plain text
-mode and no splashy) read the splashy faq.
-
-Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the
-firmwares to the initrd image. You need to install the non-free package
-"firmware-bnx2". Uncompress your initrd image, then copy files:
-
-code{
-
-cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw
-/lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw
-${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/
-
-}code
-
-Recompress your initrd image and boot: it works!
-
-Q: X is broken (the system boots, messages scroll by, and then the screen
-goes blank). What do I do? A: On my system starting X completely disables
-graphics so that I do not see anything even after X bails out and I am back
-to the console. To prevent this you can change the driver Xorg uses.
-
-If you have a working splash screen or at least graphical console you can
-use #{live xdriver=fbdev}# when booting the live system (instead of just
-enter). Another driver you might want to try is #{vesa}#. If all fails you
-might try to set xdriver to some wrong value so that Xorg fails to start and
-you can examine the system while you still see something on the
-console. #{live xdriver=none}#
-
-Q: How can I get Debian first stable versions? A: I'm developing software
-and testing it on Live-CD. Thanks for the LiveCD project. To be sure my
-development is fully compatible with the "etch" version, I need the same
-scenario when Debian GNU/Linux 4.0 was published as stable (I believe
-2007.04.08). If there was some bug on 2007.04.08 that was corrected one week
-later, I need to test software foreseeing that scenario without the bug
-solved.
-
-Q: I get "fopen: Permission denied"-warnings from apt on building/at the
-live-system A: That's a harmless bug in apt. However, if you want to get off
-this warnings in the live-system, add a file in chroot_local-hooks with
-follow row:
-
-code{
-
-chown -R man.man /var/cache/man
-
-}code
-
-Q: Why I always fail during "Retrieving Packages" stage when running
-lh_build? I have already set apt-http-proxy and so on. A: lh_build
-retrieves packages via wget, as a result you need to enable the proxy
-settings in /etc/wgetrc before running lh_build.
-
-Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system
-boots, so it's useless to put modifed Xorg.conf in
-config/choort_local-includes/etc/X11, because it will be overwritten during
-boot. However, you can edit /usr/bin/dexconf, which generate xorg.conf
-during boot, so the result will be modified Xorg.conf. The modified dexconf
-has to be put in config/choort_local-includes/usr/bin. e.g.: you can
-configure Xorg.conf for two or more keyboards layouts with alt+shift toggle
-by editing dexconf and replacing the line:
-
-code{
-
-Option "XkbLayout" "$XKB_LAYOUT"
-
-}code
-
-with the lines:
-
-code{
-
-Option "XkbLayout" "us,il" Option "XkbOptions"
-"grp:alt_shift_toggle,grp_led:scroll"
-
-}code
-
-when "us,il" are the wanted keyboard layouts.
-
-You can force default screen resulotion (e.g. 1024*768) by adding the lines:
-
-code{
-
-SubSection "Display"
- Modes "1024x768"
-EndSubSection
-
-}code
-
-between the lines:
-
-code{
-
-Section "Screen"
- Identifier "Default Screen"
- Monitor "Configured Monitor"
-EndSection"
-
-}code
-
-Q: Where are the build parameters for the prebuilt images A: See
-http://live.debian.net/README.images.
diff --git a/manual/pt_BR/other_howtos.ssi b/manual/pt_BR/other_howtos.ssi
deleted file mode 100644
index 63e84bf..0000000
--- a/manual/pt_BR/other_howtos.ssi
+++ /dev/null
@@ -1,118 +0,0 @@
-B~ Howtos
-
-1~ Howtos
-
-2~ ISO
-
-Generating a Debian Live CD is very simple. You need to have live-helper
-(package available in Debian sid and lenny), and Debootstrap (or
-cdebootstrap) from etch or newer.
-
-3~ Install live-helper
-
-#{apt-get install live-helper}#
-
-3~ Configure the current working directory with lh_config
-
-code{
-
-lh_config -b iso -a $ARCH
-
-}code
-
-where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64).
-
-#{-b}# flag is used to be sure to obtain image in ISO format.
-
-3~ Build the image with lh_build:
-
-Execute lh_build as root: #{lh_build}#
-
-The command above will create the basic image, containing just the Debian
-standard system (with no X at all).
-
-If you want to have any of the Desktop environments on your livecd, #{ls
-/usr/share/live-helper/lists}# will show a number of available package Lists
-to choose from, e.g. #{lh_config -p gnome-desktop}#
-
-More examples are listed at DebianLive/Examples.
-
-See packages for help configuring a local Debian Mirror and other aspects of
-the live system. % FIXME: <xref linkend="packages"/>
-
-3~ Test the image
-
-If you have qemu installed, you can boot the image with:
-
-code{
-
-qemu -cdrom binary.iso
-
-}code
-
-If you have also kqemu installed, you can add #{-kernel-kqemu}#
-
-2~ ISO_(multiarch)
-
-Multiple machine boot CDs can be created with the following manual
-procedure. This procedure has been successfully used to create a single CD
-which is bootable on alpha, i386, pmax, and sparc. It should be possible to
-also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x.
-
-To create a CD which is bootable by multiple architectures, use the
-following steps in this order. Please note that the order is critical.
-
-Make sure you have all the required files including the various kernels and
-boot programs listed in the individual machine sections.
-
-Include a directory somewhere in the cdsources directory called mdec.pmax
-and include the pmax bootxx_cd9660 file there. For example,
-/cdsources/usr/mdec.pmax/bootxx_cd9660.
-
-Include a directory somewhere in the cdsources directory called mdec.vax and
-include the vax xxboot file there. For example,
-#{cdsources/usr/mdec.vax/xxboot.}#
-
-Include the macppc ofwboot.xcf bootloader in /cdsources.
-
-Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b
-i386/installation/floppy/boot-big.fs \ -c boot.catalog -l -J -r -L
-/cdsources 2>&1 | tee /tmp/mkisofs.log exit}#
-
-Note: The appearance of the -v flag twice is required. If you are making a
-bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs
--part in the parameters for mkisofs.
-
-Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3
-bootblocks. Alternatively, install the sysutils/mksunbootcd package on your
-favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs
-boot-sun4m.fs boot-sun3.fs}#
-
-Run the installboot(8) program targeted for NetBSD/pmax to install the pmax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-pmax boot block is appended to the end of the ISO file system.
-
-#{installboot -m pmax -v -o append,sunsum output.iso
-/tmp/mdec.pmax/bootxx_cd9660}#
-
-The -o append,sunsum option appends the first stage boot block to the end of
-the ISO file system, and restores the checksum used when booting on a sun.
-
-Run the installboot(8) program targeted for NetBSD/vax to install the vax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-vax boot block is appended to the end of the ISO file system.
-
-installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot
-
-(See the pmax entry above for an explanation of the flags).
-
-Run the installboot(8) program targeted for NetBSD/alpha to install the
-alpha bootblocks.
-
-#{installboot -m alpha -v -o append,sunsum output.iso
-/tmp/mdec.alpha/bootxx_cd9660}#
-
-Note: The alpha installboot must occur after the others, because currently
-it's the only machine dependent back-end for installboot(8) that can
-calculate the alpha checksum. (See the pmax entry above for an explanation
-of the flags).
diff --git a/manual/ro/live-manual.ssm b/manual/ro/live-manual.ssm
index 2ec9427..60a8440 100644
--- a/manual/ro/live-manual.ssm
+++ b/manual/ro/live-manual.ssm
@@ -63,6 +63,3 @@
<< user_examples.ssi
-% << other_faq.ssi
-
-% << other_howtos.ssi
diff --git a/manual/ro/other_faq.ssi b/manual/ro/other_faq.ssi
deleted file mode 100644
index f754913..0000000
--- a/manual/ro/other_faq.ssi
+++ /dev/null
@@ -1,545 +0,0 @@
-B~ Frequently asked questions (FAQ)
-
-1~ Frequently asked questions (FAQ)
-
-Q: I downloaded a prebuilt live image. How do I put it on a USB stick? A:
-See "Copying USB/HDD image to a USB stick" % FIXME: <xref
-linkend="image_copying"/>
-
-Q: How do I log my build? A: You could use script, screen or tee: #{$
-lh_build 2>&1 | tee build.log}#
-
-Q: How can I convert an already installed standard Debian partition into a
-Debian Live system? A: Save the list of installed packages and load it into
-your new Debian Live System. Copy your /etc to config/chroot_local-includes
-
-Q: What does 'losetup: could not find any free loop device' mean and how do
-I fix it? A: Loop devices are used during the build; there probably aren't
-any free if you've aborted several builds. Something like: for l in
-/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6
-/dev/loop7 ; do losetup -d $l ; done should rectify the situation (assuming
-all loop devices in use were created by lh_build; if in doubt, check the
-contents of each loop device before deleting them with losetup -d).
-
-Q: How do I launch an interactive shell during the chroot stage? A: To
-enable interactive shell: #{$ lh_config --interactive shell}# To continue
-the build process: #{# logout}# or #{# exit}# To disable interactive shell,
-set LH_INTERACTIVE to "disabled" in config/chroot.
-
-Q: What is the root /user password? A: The user password for the live user
-is 'live'. By default, there is not any root password. You can switch to
-root with ${sudo -i}# or set a password for root with #{sudo passwd}#
-
-Q: How do I change root or any user password? A: Add a chroot local hook
-script to change root or any user password each time you build an image.
-e.g. config/chroot_local-hooks/01-update_password.sh to set root password to
-"nopasswd"
-
-code{ #!/bin/sh
-
-echo "I: update password" echo "root:nopasswd" | chpasswd
-
-$ chmod +x config/chroot_local-hooks/01-update_password.sh
-
-}code
-
-Note for live user; you need to copy the
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser your build folder:
-
-code{
-
-mkdir -p
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-cp /usr/share/initramfs-tools/scripts/live-bottom/10adduser
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/
-
-}code
-
-Note: Then edit the
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-and paste in the new user_crypted password that you make with: #{echo
-"newlivepass" | mkpasswd -s}#
-
-Or add an hook file in config/chroot_local-hooks/ with something like the
-below:
-
-code{ #!/bin/sh
-
-# Change the autogenerated user password to "debianlive"
-plain_password="debianlive" password=$(echo "${plain_password}" | mkpasswd
--s)
-
-sed -i -e 's/\(user_crypted=\)\(.*\)\( #.*\)/\1\"'${password}'\"\3/'
-/usr/share/initramfs-tools/scripts/live-bottom/10adduser
-
-update-initramfs -tu -kall }code
-
-The latter (hook model) could be more future proof than the former solution
-since it modifies just one string selectively but it requires the package
-"whois" to be installed on the target system (for mkpasswd) or that you
-generate the $password string not at build time and include it crypted in
-the above script.
-
-Q: How to disable autologin? A1: use the commandline parameter #{lh config
---bootappend-live "noautologin"}# A2: You need to set boot=noautologin
-noxautologin as described in man live-initramfs If you boot via TFTP you
-want to insert the option to pxelinux.cfg/default
-
-Q: How do I change default hostname or username? A: To change default
-hostname or username: #{$ lh_config --hostname myhostname $ lh_config
---username myusername}#
-
-Q: How do I make the final image smaller? A: Clean orphaned apps/libs:
-Install package "deborphan" and then run 'sudo deborphan -n' . Delete
-unwanted packages. Remove the apt cache. Purge unwanted locales (see
-"localepurge" package).
-
-Q: How do I customize bash-config permanently (aliases, bash-completion
-etc.)? A: Add your own .bashrc config/chroot_local-includes/etc/skel/.bashrc
-
-Q: How do I disable services permanently? (Be careful!) A: Add a chroot
-local hook script to disable a service each time you build an image:
-e.g. config/chroot_local-hooks/01-disable_service.sh
-
-code{
-
-#!/bin/sh
-
-echo "I: disable service" update-rc.d -f service_name remove
-
-$ chmod +x config/chroot_local-hooks/01-disable_service.sh
-
-}code
-
-Q: How do I enable | disable the md5checksum at the ISO building? A:
-#{lh_config --checksums enabled|disabled}# Or change the LH_CHECKSUMS value.
-
-Q: How to disable the generation of the .tar.gz file? A: #{lh_config
---net-tarball none|gzip}# Or change the LH_NET_TARBALL value. (only
-available in snapsshot version at the moment 2008/Feb/28)
-
-Q: How do I "build a new image"? A: Run commands:
-
-code{
-
-$ sudo lh_clean --binary $ sudo lh_build
-
-}code
-
-Hint: If the configuration had changed you should leave "--binary" out. This
-will clean your chroot directory too.
-
-Q: How do I use Fluxbox ? A: Add a new lists file with the fluxbox packages
-you want.
-
-Create /home/$USERNAME/.dmrc file (default username is "user").
-
-code{
-
-$ cat .dmrc [Desktop] Session=fluxbox }code
-
-Note: .dmrc is owned by $USERNAME:$USERNAME.
-
-See also http://wiki.debian.org/Fluxbox/ A short HOWTO can be found at
-http://wiki.debian.org/MichaelAblassmeier/CustomLiveCD
-
-Q: How do I use custom repositories? A: See
-http://wiki.debian.org/DebianLive/Configuration
-
-Q: How do I customize the artwork for the live CD (grub or syslinux boot
-splash, usplash, etc.)? A: See
-http://wiki.debian.org/DebianLive/Howto/Custom_Artwork
-
-Q: How do I customize desktop environment (KDE, GNOME, XFCE, etc...) look?
-A: Start the live system in qemu:
-
-code{
-
-$ qemu -m 256 -cdrom binary.iso -boot d -redir tcp:4222:10.0.2.15:22
-
-}code
-
-Note: the -redir argument must be changed to meet your needs
-
-Q: How do I execute a custom shell script inside the chroot system after the
-chroot stage? A: Add your script in config/chroot_local-hooks.
-
-Q: How do I add a script running immediately after all other scripts when
-the live system boots? A: Add your script in
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99scrip
-
-code{
-
-$ chmod +x
-config/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/99script
-
-}code
-
-Note: The hook script must be executable. Do not forget to lh_clean --chroot
-after making this change before you build again.
-
-You must also use the example script
-/usr/share/live-helper/examples/hooks/update-initramfs.sh to ensure your
-script gets built into the initramfs (read the comment header for
-instructions).
-
-Q: How do I add software not in Debian ? A: See Customizing package
-installation % FIXME: <xref linkend="packages"/>
-
-Q: What is the manifest with Ubuntu used for? A: Manifest is just the
-package list, which ubuntu does $something with. Don't worry about it.
-
-Q: What is this {p} syntax with mtools{p} and parted{p}? A: That's aptitude.
-
-Q: Do I need to write the image on USB stick to test it? A: you must use
-qemu >= 0.8.
-
-Q: What is /cow? A: Copy-on-write, the 'diff' from unionfs.
-
-Q: Is /usr/share/live-helper/lists/standard-x11 like preseed or is preseed
-something else entirely? A: It is not. It is a package list, not a debconf
-preseeding.
-
-Q: What is the difference between standard and minimal? A: standard:
-packages of priority standard and higher; minimal: packages of priority
-essential and higher;
-
-Q: What can the sections be used for? Aren't they BIG? A: Someone maybe
-wants to include packages from contrib or non-free.
-
-Q: memtest86+ ... is that used? A: Yes
-
-Q: How do I build using predefined packages lists? A: e.g. to build using
-standard-x11 packages list: #{$ sudo lh_config -p standard-x11 && sudo
-lh_build}# Note: The packages lists can be found in
-/usr/share/live-helper/lists/ directory.
-
-Q: How do I rebuild without downloading all the packages again? A: All
-packages are cached in cache subdirectory. They remain until a clean purge:
-#{$ sudo lh_clean --purge}# You do not have to do anything to prevent
-packages from being re-downloaded. You need to remember to clean whichever
-stages you want to rebuild first. e.g. to rebuild from the cached bootstrap,
-chroot packages and build a new image. #{$ sudo lh_clean && sudo lh_build}#
-
-Q: How do I boot USB debian-live on systems not supporting USB boot? A: Make
-a boot CD with grub, configured to boot from a debian-live kernel copied on
-the cd structure #{$ mkdir -p iso/boot/grub && cp
-/usr/lib/grub/i386-pc/stage2_eltorito iso/boot/grub && cp chroot/boot/*
-iso/boot/}# Create iso/boot/grub/menu.lst:
-
-code{
-
-default 0 timeout 5 color cyan/blue white/blue title Debian Live root (cd)
-kernel /boot/vmlinuz boot=live initrd /boot/initrd.img
-
-}code
-
-Create the iso image #{$ mkisofs -R -b boot/grub/stage2_eltorito
--no-emul-boot \ -boot-load-size 4 -boot-info-table -o grub.iso iso}# Burn
-the image.
-
-Q: How do I boot debian-live on systems not supporting CDROM or USB boot? A:
-If you have a floppy drive, you may be able to use it, otherwise you will
-need to use loadlin/grub4dos/win32-loader. If you have a second system to
-serve up the image over the network, See
-http://wiki.debian.org/DebianLive/Howto/Creating_a_Netboot_Image
-
-Q: The X configuration does not seems to work, the resolution is too
-low. What can I do? A: Use xdebconfigurator #{$ lh_config --bootappend
-xdebconf && lh_config --packages xdebconfigurator}#
-
-Q: Apache has problems with static files A: Sendfile does not work well on
-the unionfs used by Debian Live. Add the following to apache's
-configuration: #{EnableSendfile off}#
-
-Q: How do I make hard disk partitions auto-mountable? A: Short answer: Right
-now the best is to use a script that will populate the fstab when the CD is
-booting. Such a script can be found at
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh.
-A proper solution based on HAL will be described here in a hopefully near
-future. A: Long Answer: Since 55_nonpolkit-mount-policy.patch in HAL,
-debian-storage-policy-fixed-drives.fdi is not available anymore and the
-previous trick that consisted to remove this file to enable automounting of
-fixed drives as a consequence is obsolete. Eventually, it will be possible
-to combine HAL and PolicyKit to enable different permissions and actions to
-achieve advanced (auto)mounting for non-root users. Until then, because the
-live scripts are only touching to the fstab to add a swap partition if
-discovered at boot time, the only way to have fixed drives mounted
-automatically is to use a script that will populate the fstab file at the
-end of the multiuser runlevel. To achieve this, you can do, for example, the
-following: download the
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/sbin/diskmounter.sh
-script Create the chroot_local-includes/sbin directory, and move the script
-inside Make sure the script is executable (chmod +x diskmounter.sh) create
-the chroot_local-includes/etc/rc.local file and call the diskmounter from
-there (see this
-https://devel.goto10.org/svn/puredyne/trunk/broth/stock/chroot_local-includes/etc/rc.local
-When called correctly, the script detects ext2, ext3, reiserfs, xfs, FAT32,
-HFS+ and NTFS partitions and mount them read-write, except for NTFS. This
-will change soon and an option will be available to use ntfs-3g to mount
-NTFS as read-write. comments, patches and other things about this script and
-issue: http://code.goto10.org/projects/puredyne/ticket/463
-
-Q: Boot fails with panic: can't open /scripts/live A: Add latest
-live-initramfs deb package into config/chroot_local-packages directory and
-rebuild.
-
-Q: How do I configure the locale and the keyboard? A: See 10n % FIXME: <xref
-linkend="internalization"/>
-
-Q: How do I get past boot prompt without a working keyboard? A: See
-Customizing the bootup process % FIXME: <xref linkend="bootup"/> Note: Boot
-from an USB-HDD on an iMac with GRUB did not work.
-
-Q: Can I serve the root image from a web or ftp server? A: Since
-live-initramfs 1.99, it should be possible to use the fetch= argument on the
-kernel command line. You can build a netboot image as usual, and when you
-are done edit the tftpboot/pxelinux.cfg/default file. Remove the references
-to network boot (netboot, nfsroot, nfsopts), and replace with fetch= <url
-where you placed the root image>. You have to include wget in the chroot. It
-could work for other boot methods as well. However, I am not sure the live
-scripts configure the network when booting from a CD or USB disk. #{$
-lh_config --packages wget}#
-
-Q: Why doesn't quickreboot (or some other boot parameter) work? A: If you
-are building an etch image (which was the default up to 2007/09/14) you have
-a very old version of casper which does not support quickreboot and possibly
-other boot parameters as well. You could configure your sources to use
-live-backports (see /usr/share/live-helper/examples/sources/live-backports)
-and switch to live-initramfs, or better yet, build a lenny image instead,
-which is the new default. #{$ lh_config --distribution lenny $ lh_config
---initramfs live-initramfs}#
-
-Q: How do I fix "Could not find kernel image" issue with syslinux
-bootloader? A: Add a binary local hook script to fix kernel and initrd path
-each time you build an
-image. e.g. config/binary_local-hooks/01-fix_syslinux.sh
-
-code{
-
-#!/bin/sh
-
-SYSLINUXCFG=`find binary -type f -name syslinux.cfg`
-
-sed -i "s|kernel /vmlinuz|kernel vmlinuz|g" ${SYSLINUXCFG} sed -i
-"s|initrd=/initrd|initrd=initrd|g" ${SYSLINUXCFG}
-
-$ chmod +x config/binary_local-hooks/01-fix_syslinux.sh
-
-}code
-
-Q: How do I use a newer kernel with lenny? A: A build with backports.org
-kernels will fail as that repository lacks the necessary module packages
-(linux-modules-extra-2.6, aufs, etc.). Use the kernel backports
-http://unsupported.debian-maintainers.org/backports-kernel/ The quick way to
-success:
-
-code{
-
-$ lh_config --linux-packages 'linux-image-2.6 aufs-modules-2.6
-squashfs-modules-2.6' $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.chroot $ echo 'deb
-http://unsupported.debian-maintainers.org/backports-kernel/ ./' >
-config/chroot_sources/backports-kernel.binary $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.chroot.gpg $ wget
-http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc
--O config/chroot_sources/backports-kernel.binary.gpg $ lh_build }code
-
-Q: How do I use a custom kernel? Is there a nice way of booting debian-live
-with a custom kernel (not in an apt repo)? A: Copy it into
-config/chroot_local-packages and set LH_LINUX_PACKAGES="none" or use lh
-config --linux-packages " " Don't forget to compile your kernel with an
-union filesystem (unionfs or aufs), squashfs modules, and initrd support. I
-can cause the kernel to be installed but it seems this happens later than
-grub/syslinux is configured so it's not listed and casper/ and the menu
-require munging. You need to follow the debian scheme, e.g. placing the
-files in /boot as vmlinuz-$version and initrd.img-$version etc. I personally
-wouldn't go that way which is too much of a hassle, and just use make-kpkg
-to produce custom kernel deb packages. They should integrate nicely if you
-just put them into config/chroot_local-packages and set
-LH_LINUX_PACKAGES="". Hint: to work around an error, which
-lh_binary_syslinux will throw on custom kernels if there is not an 468/686
-in the kernel-name, you need to set CONFIG_LOCALVERSION="-486" or "-686"
-within the kernel configuration (-> General setup -> Local version set
-to -486 or -686) corresponding to LH_LINUX_FLAVOURS="" or "686". this at
-least up till live-helper version 1.0~a40-1 see
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-July/001947.html
-and
-http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-November/002581.html
-
-Q: How do I create a cross arch live CD image? A: In short: You can't. Read
-on: The procedure to create a live CD is based on creating a chroot that
-contains the files that will be finally available on the live CD. The live
-CD building procedure includes chrooting into the chroot dir and so some
-operations. chrooting means that the terminal you chroot on will behave as a
-different system so your real system and the chroot environment is decoupled
-somehow. Once the live CD scripts chroots into the chroot dir they have some
-operations to do inside that environment and your real system won't be able
-to run them unless you are using the same architecture. So you only are able
-to make live CD for the arch you run on. But this doesn't prevent you run
-qemu or some other machine emulator that make this possible.
-
-Q: When is a lh_clean necessary? lh_clean is a script in /usr/bin/ A: That
-depends what you've changed between builds If, for example, you've built an
-iso image and you want a usb image, you only need to run #{lh_clean
---binary}# before you run lh_build again. If you've changed anything in the
-chroot, you'll need to cleanup both chroot and binary with #{lh_clean}#
-before continuing
-
-Q: How can i set boot= parameters? A: Set LH_BOOTAPPEND_LIVE in
-config/binary
-
-Q: How do I include different modules to load when the live system boots? A:
-Configure config/chroot_local-includes/etc/initramfs-tools/
-
-The lh_chroot_hacks helper rebuilds the live/initrd1.img using the default
-initramfs.conf "MODULES = most". You may override that by supplying your own
-initramfs.conf, or else just add your own modules, e.g.
-
-code{
-
-mkdir -p config/chroot_local-includes/etc/initramfs-tools/ echo "atl2" >>
-config/chroot_local-includes/etc/initramfs-tools/modules
-
-}code
-
-Note: Even though initramfs.conf(5) says "most adds all the framebuffer,
-acpi, file system, ide, sata, scsi and usb drivers", it actually includes
-network drivers as well. See auto_add_modules() in
-/usr/share/initramfs-tools/hook-functions for the complete list.
-
-Q: Can I have a splash screen? A: Yes you can. You will not know what is
-going on when the splash screen is active, it may fail to activate on some
-hardware or break X on other (both usplash and splashy use libdirectfb which
-does some evil voodoo and may break you graphics or input until you
-reboot). However, you can install and activate it just as you would on any
-other Debian system. To use splashy: 1. install splashy and read the README,
-the manpages are useless for setting it up. Add some parameters to your
-kernel command line, such as in your pxelinux configuration or in
-LH_BOOTAPPEND_LIVE in config/binary in debian-live configuration: #{vga=792
-splash quiet}# #{vga}# to select video mode, #{splash}# to activate splashy,
-#{quiet}# to suppress most kernel messages that you cannot see anyway but
-would scroll past before splashy manages to paint the graphics on your
-screen. You might want to add splashy to the list of packages installed in
-your image: #{echo splashy > config/chroot_local-packageslists/splashy echo
-splashy-themes >> config/chroot_local-packageslists/splashy}# and select a
-theme:
-
-code{
-
-echo '#!/bin/sh' > config/chroot_local-hooks/splashy echo splashy_config -s
-debian-moreblue '||' true >> config/chroot_local-hooks/splashy # update the
-ramdisk to include the splash screen echo update-initramfs -u -k all >>
-config/chroot_local-hooks/splashy chmod 755
-config/chroot_local-hooks/splashy
-
-}code
-
-After you rebuild your live system you should observe a bluish splash screen
-while booting. Nothing happens while initramfs is running because there is
-no splashy support in initramfs-tools. Once the init starts the progress bar
-should start to fill. If #{vga=something}# sets a mode that your screen
-cannot show or your card cannot do vesa 2.0 (and thus you get plain text
-mode and no splashy) read the splashy faq.
-
-Q: Howto use my Broadcom eXtrem 2 network card (module bnx2)? A: Add the
-firmwares to the initrd image. You need to install the non-free package
-"firmware-bnx2". Uncompress your initrd image, then copy files:
-
-code{
-
-cp /lib/firmware/bnx2x-e1-4.8.53.0.fw /lib/firmware/bnx2x-e1-5.0.21.0.fw
-/lib/firmware/bnx2x-e1h-4.8.53.0.fw /lib/firmware/bnx2x-e1h-5.0.21.0.fw
-${INITRD}/lib/firmware/ cp /lib/udev/firmware.agent ${INITRD}/lib/udev/
-
-}code
-
-Recompress your initrd image and boot: it works!
-
-Q: X is broken (the system boots, messages scroll by, and then the screen
-goes blank). What do I do? A: On my system starting X completely disables
-graphics so that I do not see anything even after X bails out and I am back
-to the console. To prevent this you can change the driver Xorg uses.
-
-If you have a working splash screen or at least graphical console you can
-use #{live xdriver=fbdev}# when booting the live system (instead of just
-enter). Another driver you might want to try is #{vesa}#. If all fails you
-might try to set xdriver to some wrong value so that Xorg fails to start and
-you can examine the system while you still see something on the
-console. #{live xdriver=none}#
-
-Q: How can I get Debian first stable versions? A: I'm developing software
-and testing it on Live-CD. Thanks for the LiveCD project. To be sure my
-development is fully compatible with the "etch" version, I need the same
-scenario when Debian GNU/Linux 4.0 was published as stable (I believe
-2007.04.08). If there was some bug on 2007.04.08 that was corrected one week
-later, I need to test software foreseeing that scenario without the bug
-solved.
-
-Q: I get "fopen: Permission denied"-warnings from apt on building/at the
-live-system A: That's a harmless bug in apt. However, if you want to get off
-this warnings in the live-system, add a file in chroot_local-hooks with
-follow row:
-
-code{
-
-chown -R man.man /var/cache/man
-
-}code
-
-Q: Why I always fail during "Retrieving Packages" stage when running
-lh_build? I have already set apt-http-proxy and so on. A: lh_build
-retrieves packages via wget, as a result you need to enable the proxy
-settings in /etc/wgetrc before running lh_build.
-
-Q: How do I edit Xorg.conf? A: Xorg.conf is generated every time system
-boots, so it's useless to put modifed Xorg.conf in
-config/choort_local-includes/etc/X11, because it will be overwritten during
-boot. However, you can edit /usr/bin/dexconf, which generate xorg.conf
-during boot, so the result will be modified Xorg.conf. The modified dexconf
-has to be put in config/choort_local-includes/usr/bin. e.g.: you can
-configure Xorg.conf for two or more keyboards layouts with alt+shift toggle
-by editing dexconf and replacing the line:
-
-code{
-
-Option "XkbLayout" "$XKB_LAYOUT"
-
-}code
-
-with the lines:
-
-code{
-
-Option "XkbLayout" "us,il" Option "XkbOptions"
-"grp:alt_shift_toggle,grp_led:scroll"
-
-}code
-
-when "us,il" are the wanted keyboard layouts.
-
-You can force default screen resulotion (e.g. 1024*768) by adding the lines:
-
-code{
-
-SubSection "Display"
- Modes "1024x768"
-EndSubSection
-
-}code
-
-between the lines:
-
-code{
-
-Section "Screen"
- Identifier "Default Screen"
- Monitor "Configured Monitor"
-EndSection"
-
-}code
-
-Q: Where are the build parameters for the prebuilt images A: See
-http://live.debian.net/README.images.
diff --git a/manual/ro/other_howtos.ssi b/manual/ro/other_howtos.ssi
deleted file mode 100644
index 63e84bf..0000000
--- a/manual/ro/other_howtos.ssi
+++ /dev/null
@@ -1,118 +0,0 @@
-B~ Howtos
-
-1~ Howtos
-
-2~ ISO
-
-Generating a Debian Live CD is very simple. You need to have live-helper
-(package available in Debian sid and lenny), and Debootstrap (or
-cdebootstrap) from etch or newer.
-
-3~ Install live-helper
-
-#{apt-get install live-helper}#
-
-3~ Configure the current working directory with lh_config
-
-code{
-
-lh_config -b iso -a $ARCH
-
-}code
-
-where #{$ARCH}# is the intended architecture (i.e. - i386 or amd64).
-
-#{-b}# flag is used to be sure to obtain image in ISO format.
-
-3~ Build the image with lh_build:
-
-Execute lh_build as root: #{lh_build}#
-
-The command above will create the basic image, containing just the Debian
-standard system (with no X at all).
-
-If you want to have any of the Desktop environments on your livecd, #{ls
-/usr/share/live-helper/lists}# will show a number of available package Lists
-to choose from, e.g. #{lh_config -p gnome-desktop}#
-
-More examples are listed at DebianLive/Examples.
-
-See packages for help configuring a local Debian Mirror and other aspects of
-the live system. % FIXME: <xref linkend="packages"/>
-
-3~ Test the image
-
-If you have qemu installed, you can boot the image with:
-
-code{
-
-qemu -cdrom binary.iso
-
-}code
-
-If you have also kqemu installed, you can add #{-kernel-kqemu}#
-
-2~ ISO_(multiarch)
-
-Multiple machine boot CDs can be created with the following manual
-procedure. This procedure has been successfully used to create a single CD
-which is bootable on alpha, i386, pmax, and sparc. It should be possible to
-also make the CD bootable on macppc, vax and on sun2, sun3 and sun3x.
-
-To create a CD which is bootable by multiple architectures, use the
-following steps in this order. Please note that the order is critical.
-
-Make sure you have all the required files including the various kernels and
-boot programs listed in the individual machine sections.
-
-Include a directory somewhere in the cdsources directory called mdec.pmax
-and include the pmax bootxx_cd9660 file there. For example,
-/cdsources/usr/mdec.pmax/bootxx_cd9660.
-
-Include a directory somewhere in the cdsources directory called mdec.vax and
-include the vax xxboot file there. For example,
-#{cdsources/usr/mdec.vax/xxboot.}#
-
-Include the macppc ofwboot.xcf bootloader in /cdsources.
-
-Create an i386 bootable image. #{sh mkisofs -v -v -o output.iso -b
-i386/installation/floppy/boot-big.fs \ -c boot.catalog -l -J -r -L
-/cdsources 2>&1 | tee /tmp/mkisofs.log exit}#
-
-Note: The appearance of the -v flag twice is required. If you are making a
-bootable CD for an Open Firmware 3 macppc model, make sure to include -hfs
--part in the parameters for mkisofs.
-
-Run mksunbootcd on a NetBSD/sparc machine to install sparc and sun2/sun3
-bootblocks. Alternatively, install the sysutils/mksunbootcd package on your
-favorite NetBSD machine. #{mksunbootcd output.iso boot-sun4.fs boot-sun4c.fs
-boot-sun4m.fs boot-sun3.fs}#
-
-Run the installboot(8) program targeted for NetBSD/pmax to install the pmax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-pmax boot block is appended to the end of the ISO file system.
-
-#{installboot -m pmax -v -o append,sunsum output.iso
-/tmp/mdec.pmax/bootxx_cd9660}#
-
-The -o append,sunsum option appends the first stage boot block to the end of
-the ISO file system, and restores the checksum used when booting on a sun.
-
-Run the installboot(8) program targeted for NetBSD/vax to install the vax
-bootblocks. Note that in order to coexist with other NetBSD boot blocks, the
-vax boot block is appended to the end of the ISO file system.
-
-installboot -m vax -v -o append,sunsum output.iso /tmp/mdec.vax/xxboot
-
-(See the pmax entry above for an explanation of the flags).
-
-Run the installboot(8) program targeted for NetBSD/alpha to install the
-alpha bootblocks.
-
-#{installboot -m alpha -v -o append,sunsum output.iso
-/tmp/mdec.alpha/bootxx_cd9660}#
-
-Note: The alpha installboot must occur after the others, because currently
-it's the only machine dependent back-end for installboot(8) that can
-calculate the alpha checksum. (See the pmax entry above for an explanation
-of the flags).
--
live-manual
More information about the debian-live-changes
mailing list