DISTROS&&CLONIN Merge PDF

FAI - Fully Automatic Installation
fai-project.org/
FAI - Fully Automatic Installation

FAI is a non-interactive system to install, customize and manage Linux systems and
software configurations on computers as well as virtual machines and chroot environments,
from small networks to large-scale infrastructures like clusters and cloud environments.
It's a tool for unattended mass deployment of Linux. You can take one or more virgin PC's,
turn on the power, and after a few minutes, the systems are installed, and completely
configured to your exact needs, without any interaction necessary.
FAI ISO (1012 MB)
Motto: Plan your installation, and FAI installs your plan.
NEWS
[July/August] I will be at DebConf 18 in Taiwan from july 22th to aug 5th
[4 June 2018] FAI 5.7 released and new ISO images available
[16-20 May 2018] Thomas was at the MiniDebConf Hamburg and gave a talk
[13 Mar 2018] FAI.me can now create cloud images, blog post
Thomas gave a talk (video) at the Chemnitzer Linuxtage, slides (in german)
I announced the FAI.me service
[18 Oct 2017] We had a great Debian cloud sprint in Seattle/Bellevue. We've created
a
FAI config space for GCE, Azure, EC2 and Openstack cloud images
[6 Oct 2017] Video of creating a cross architecture disk image for ARM64
[14 Oct 2016] FAI 5.2 is going to the cloud
Features
1/2
Installs and updates Debian, Ubuntu, CentOS, RHEL, SUSE, ...
Centralized deployment and configuration management
Installs virtual machines using KVM, XEN or VirtualBox and Vserver
Easy set up of software RAID and LVM
Full remote control via ssh during installation
Integrated disaster recovery system
Every stage can be customized via hooks
FAI is free software, distributed under the terms of the GNU GPL, version 2 or any
later version.
2/2
Home  Fedora Installation Guide  Book Information
 Fedora Release Notes

 Fedora Installation Guide
Book Information
Preface
Introduction
Downloading Fedora
 Installing Fedora
 Advanced Installation Options
 Technical Appendixes
Revision History
 Fedora System
Administration Guide
Installation Guide
Installing Fedora 27 on 32 and 64-bit AMD and Intel
This manual explains how to boot the Fedora installation program, Anaconda, and
how to install Fedora 27 on 32 and 64-bit AMD and Intel systems. It also covers
advanced installation methods such as automated Kickstart installations, booting
the installation from a network location, remote access to the installation system
using VNC, and system upgrades from previous versions of Fedora. It also describes
common post-installation tasks and explains how to troubleshoot common issues
related to the installation.
Copyright 2017 Red Hat, Inc. and others.
The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-
BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors
of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for
purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an
adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to
assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the
Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States
and other countries.
For guidelines on the permitted uses of the Fedora trademarks, refer to

https://fedoraproject.org/wiki/Legal:Trademark_guidelines.
Linux ® is the registered trademark of Linus Torvalds in the United States and other
countries.
Java ® is a registered trademark of Oracle and/or its affiliates.
XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the

United States and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union
and other countries.
All other trademarks are the property of their respective owners.
Fedora Documentation Project
ABOUT
Get Fedora
Sponsors
Fedora Magazine
Legal
SUPPORT
Get Help
Ask Fedora
Common Bugs
Fedora Developer
Portal
COMMUNITY
Join Fedora
About Fedora
Planet Fedora
Fedora Account
System
  
© 2018 Red Hat, Inc. and others.
Please send any comments or corrections to the documentation team
Fedora is sponsored by Red Hat.

Learn more about the relationship between Red Hat and Fedora »
Homepage Forums Manual Quick Start Disk Partitioning LVM Guide
Cheap
Linux
SYSTEM RESCUE CD HOMEPAGE
DVD
SystemRescue
OpenSUSE
Ubuntu
Fedora
CentOS
About SystemRescueCd
DebianDescription: SystemRescueCd is a Linux system rescue disk available as a bootable CD-ROM or USB stick for administrating or
Linux repairing your system and data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as
Mint creating and editing the hard disk partitions. It comes with a lot of Linux system utilities such as GParted, fsarchiver, filesystem
tools and basic tools (editors, midnight commander, network tools). It can be used for both Linux and windows computers, and
Knoppix
on desktops as well as servers. This rescue system requires no installation as it can be booted from a CD/DVD drive or USB stick,
but it can be installed on the hard disk if you wish. The kernel supports all important file systems (ext3/ext4, xfs, btrfs, reiserfs,
Site jfs, vfat, ntfs), as well as network filesystems such as Samba and NFS.
map
System
Homepage and Networking Guides
Download
In addition to the Quick Start Guide and SystemRescueCd documentation here are other guides:
ChangeLog
System Disk Partitioning: Introduction, Attributes, Tools, GPT Disks, How Grub boots, How to repair Grub
LVM Volume-Manager: Overview, How it works, Booting, Rootfs on LVM, Snapshots and Backups
tools
Networking on Linux: network configuration, advanced routing, dport routing, load balancing
Bootable
USB Project documentation
Beta
This project comes with good documentation. Here are the most important pages:
versions
Package
For the impatient:
list
Quick start guide: please read this if this is the first time you are using this system recovery cd.
Screenshots
Customization
Chapters about basic usage: Docum
Kernel
Overview of the livecd Manua
Modules
Downloading and burning LVM G
FAQ Booting SystemRescueCd (kernels and boot options) Disk p
How to install SystemRescueCd on an USB-stick
DocumentationStarting to use the system Netwo
Manua
Manual (EN)Network: configuration and programs
System software
LVM Guide
Mounting an NTFS partition with full Read-Write support Relate
Disk partitioning
System boot floppy disks
Sourc
Networking
Chapters about advanced usage: FSArc
Manual (FR)
How to customize SystemRescueCd
Installing SystemRescueCd on the disk
Creating a backing-store to keep your modifications
PXE network booting with SystemRescueCd
Run your own scripts at start-up with autorun
Build a SystemRescueCd with your own kernel
How to burn a DVD with SystemRescueCd
Secure Deletion of Data
Manage remote servers using SystemRescueCd
Backup data from an unbootable Windows computer
Backup and transfer your data using rsync
System tools included

GNU Parted: creates, resizes, moves, copies partitions, and filesystems (and more).
GParted: GUI implementation using the GNU Parted library.
FSArchiver: flexible archiver that can be used as both system and data recovery software
Partimage: popular opensource disk image software which works at the disk block level
ddrescue : Attempts to make a copy of a partition or floppy/Hard Disk/CD/DVD that has hardware errors, optionally filling
corresponding bad spots in input with user defined pattern in the copy.
File systems tools (for Linux and Windows filesystems): format, resize, and debug an existing partition of a hard disk
Ntfs3g: enables read/write access to MS Windows NTFS partitions.
sfdisk saves and restores partition tables.
Test-disk : tool to check and undelete partition, supports reiserfs, ntfs, fat32, ext3/ext4 and many others
Memtest: to test the memory of your computer (first thing to test when you have a crash or unexpected problems)
Rsync: very-efficient and reliable program that can be used for remote backups.
Network tools (Samba, NFS, ping, nslookup, …): to backup your data across the network
Browse the short system tools page for more details about the most important software included.
Browse the detailed package list for a full list of the packages.
Advanced uses
SystemRescueCd is available for blind people. Now, the linux speakup screen reader is working well, and the speakup keymap is
installed. This feature was tested by Gregory Nowak. Notes specific to using speakup in SystemRescueCD are available on the
speakup info page
It is possible to make customized versions of the system. For example, you can add your own scripts, make an automatic
restoration of the system. It is also possible to burn a customized DVD, with SystemRescueCd and 4GB for your data (backup
for example). Read the manual for more details.
You can use SystemRescueCd to backup data from an unbootable Windows computer, if you want to backup the data stored
on a Windows computer that cannot boot any more.
It is very easy to install SystemRescueCd on a USB stick. That is very useful in case you cannot boot from the CD drive. You
just have to copy several files to the stick and run syslinux. The install process can be done from Linux or Windows. Follow
instructions from the manual for more details.
More information about this project

Please, ask questions and report bugs in the Forums. We will not answer emails about personal situations by email.
SystemRescueCd is licensed under the GPL-2 license. You can contact us but please use the Forums for technical and general
questions.
Clonezilla
The Free and Open Source Software for Disk Imaging and Cloning
About
News
Create Clonezilla live from scratch
Screenshots
Live CD/USB
This doc is about creating Clonezilla live 2.x.
Live Docs
Server Edition
Download 1. Find a machine with memory size larger than 1 GB.
CD/USB key vendors 2. Download Clonezilla live 2.5.0-25 amd64 version.
DRBL-winroll
3. Follow this doc to create a bootable Clonezilla live boot media, then boot it on an x86 machine. After language and
Related LiveCD
Testimonials keyboard are selected, choose "Start_Clonezilla" -> "device-image", then mount a working directory, the space should
Lecture Materials large enough to put the live CD and some temp files. It's recommended to choose local_dev to mount local partition as
Related Articles
/home/partimag, since live-build will use some low level commands and it might fail in network-based directory. Also make
Partners
FAQ/Q&A sure the partition is the filesystem of Linux, like ext4 or reiserfs, _NOT_ FAT or NTFS filesystem, because they do not
Forum support some file types in Linux.
Mailing Lists
4. When Clonezilla live asks you to choose save or restore disk/partition, choose "exit" to enter command line prompt.
Developers
Contributors 5. Run "sudo -i" or "sudo su -" to become root.
Related links 6. Run "ocs-live-netcfg" to configure the network so that we can access Debian repository later.
Local communities
7. Modify /etc/apt/sources.list if you want to assign different apt repository.
Custom Search
8. cd /home/partimag/
9. If the available space in dir /tmp/ is less than 500 MB, tune it to be larger than 500 MB. You can make it by the commands
like:
mount -t tmpfs -o "nosuid,size=60%,mode=1777" tmpfs /tmp
Or
mount -t tmpfs -o "nosuid,size=524288000,mode=1777" tmpfs /tmp
10. apt-get purge drbl clonezilla
11. apt-get update
12. Do NOT run "apt-get dist-upgrade" or "apt-get upgrade" to upgrade any packages, otherwise this will break the rest of
procedure.
13. apt-get -y install drbl clonezilla
14. If you want to add more packages in Clonezilla live, and you are sure the packages are included in Debian repository, e.g.
ncpfs, you can edit /etc/drbl/drbl.conf, append ncpfs in variable PKG_FROM_DBN_WHICH_OCS_LIVE_NEED.
15. apt-get -y install live-build=4.0.5-1.drbl3 debootstrap genisoimage
16. If you want to use Debian Sid as the running OS of Clonezilla live, use the experimental drbl live repository (-l e), and
unstable drbl repository (-b unstable), you can run it as:
create-debian-live -l unstable -b unstable -d sid -i customized
For more options about create-debian-live, you can run "create-debian-live --help".
More examples, like:
create-debian-live -o -bt debootstrap -a 'firmware-linux-free live-boot=4.0.2-1.drbl14 live-boot-initramfs-tools=4.0.2-
1.drbl14 live-config=4.0.4-1.drbl7 live-config-systemd=4.0.4-1.drbl7 live-tools syslinux=3:6.03+dfsg-14
extlinux=3:6.03+dfsg-14 syslinux-common=3:6.03+dfsg-14 cryptsetup' -f amd64 -l unstable -b unstable -d sid -m
http://free.nchc.org.tw/debian -s http://free.nchc.org.tw/debian-security -g http://free.nchc.org.tw/drbl-core -k 4.9.0-2 -i
2.5.0-25-amd64
(//NOTE// Since Debian Sid repository changes everyday, the above command might have to be modified so it can
work with Debian Sid.)
Other examples:
If you want some special kernel version, and you are sure it exists in your Debian repository, e.g. kernel 3.11-2, you
can make Clonezilla live by:
create-debian-live -l e -b unstable -k 3.11-2 -i customized
("-l e" means to use the live-experimental branch in drbl respository, this also means packages from live-stable, live-
testing or live-unstable can be used. "-b unstable" means to use the unstable branch of drbl.). You can refer to this
URL to check the packages in DRBL repository http://free.nchc.org.tw/drbl-core/pool/drbl/).
If everything runs smooth, you will get a Debian live with file name "debian-live-for-ocs-customized.iso". Later we will
use this Debian live as a template for Clonezilla live.
17. Run:
ocs-iso -s --extra-boot-param "quiet" -j debian-live-for-ocs-customized.iso -i customized
ocs-live-dev -c -s --extra-boot-param "quiet" -j debian-live-for-ocs-customized.iso -i customized
then 2 files, clonezilla-live-customized.iso and clonezilla-live-customized.zip will be created, respectively.
grml-live(8)
grml.org/grml-live/
1. Name
grml-live - build framework based on FAI for generating a Grml and Debian based Linux
Live system (CD/ISO)
2. Synopsis
grml-live [-a <architecture>] [-c <classe[s]>] [-C <configfile>] [ -e <extract_iso_name>] [-g
<grml_name>] [-i <iso_name>] [ -o <output_directory>] [-r <release_name>] [-s <suite>] [ -t
<template_directory>] [-v <version_number>] [-U <username>] [ -w <date>] [-
AbBFnNqQuVz]
3. Description
grml-live provides the build system for creating a Grml and Debian based Linux Live-CD.
The build system is based on FAI (Fully Automatic Installation). grml-live uses the "fai
dirinstall" feature to generate a chroot system based on the class concept of FAI (see later
sections for further details) and provides the framework to be able to generate a full-
featured ISO. It does not use all the FAI features by default though and you don’t have to
know FAI to be able to use it.
The use of FAI gives you the flexibility to choose the packages you would like to include on
your very own Linux Live-CD without having to deal with all the details of a build process.
grml-live does not use /etc/fai for configuration but instead (unless overridden using the '-
D' option). This ensures that it does not clash with default FAI configuration and packages,
so you can use grml-live and FAI completely independent at the same time!
Please notice that you should have a fast network connection as all the Debian packages
will be downloaded and installed via network. If you want to use a local mirror (strongly
recommended if you plan to use grml-live more than once) checkout mkdebmirror (see
/usr/share/doc/grml-live/examples/mkdebmirror), debmirror(1), reprepro(1) (see
/usr/share/doc/grml-live/examples/reprepro/ for a sample configuration), apt-cacher(1) and
approx(8). To avoid downloading the base system again and again check out the base
tar.gz feature.
4. Options
-A
Clean up all output directories before running the build process. After finishing, clean up the
Chroot target and Build target directories.
-a ARCHITECTURE
Use the specified architecture instead of the currently running one. This allows building a
1/14
32bit system on a 64bit host (though you can’t build a 64bit system on a 32bit
system/kernel of course). Please notice that real crosscompiling (like building a ppc system
on x86) isn’t possible due to the nature and the need of working in a chroot. Currently
supported values: i386 and amd64.
-b
Build the ISO without updating the chroot via FAI. This option is useful for example when
working on stable releases: if you have a working base system/chroot and do not want to
execute any further updates (via "-u" option) but intend to only build the ISO.
-B
Build the ISO without touching the chroot at all. This option is useful if you modified
anything that FAI or grml-live might adjust via Grml’s FAI scripts. It’s like the -b option but
even more advanced. Use only if you really know that you do not want to update the chroot.
-c CLASSES
Specify the CLASSES to be used for building the ISO via FAI. By default only the classes
GRMLBASE, GRML_FULL and I386/AMD64 (depending on system architecture) are
assumed, resulting in a base system of about 350MB total ISO size. If using a non-I386
system (like AMD64) you should specify the appropriate architecture as well. Additionally
you can specify a class providing a grml-kernel (see the CLASSES section in this document
for details about available classes). So instead of GRML_FULL you can also use
GRML_SMALL and GRML_FULL.
All class names should be written in uppercase letters. Do not use a dash, use an
underscore. So do not use "amd64" but "AMD64", do not use "FOO BAR" but
"FOO_BAR".
-C CONFIGURATION_FILE
The specified file is used as configuration file for grml-live. By default /etc/grml/grml-
live.conf is used as default configuration. If a file named /etc/grml/grml-live.local exists it is
used as well (sourced after reading /etc/grml/grml-live.conf meant as main file for local
configuration). As a last option the specified configuration file is sourced so it is possible to
override settings of /etc/grml/grml-live.conf as well as of /etc/grml/grml-live.local. Please
notice that all configuration files have to be adjusted during execution of grml-live, so
please make sure you use /etc/grml/grml-live.conf as a base for your own configuration file
(usually /etc/grml/grml-live.local). Please also notice that the configuration file specified via
this option is not (yet) /etc/grml/grml-live.local for configuration stuff used inside
-d DATE
Use specified date as build date information on the ISO instead of the default. The default
is the date when grml-live is being executed (retrieved via executing date +%Y-%m-%d).
The information is stored inside the file /GRML/grml-version on the ISO, /etc/grml_version
in the squashfs file and in all the bootsplash related files. This option is useful if you want to
provide an ISO with release information for a specific date but have to build it in advance.
Usage example: -d 2009-10-30
-D CONFIGURATION_DIRECTORY
The specified directory is used as configuration directory for grml-live and its FAI. By
2/14
default /etc/grml/fai is used as default configuration directory. If you want to have different
configuration scripts, package definitions, etc. with without messing with the global
configuration under /etc/grml/fai provided by grml-live this option provides you the option to
use your own configuration throughout this documentation.
-e EXTRACT_ISO_NAME
The squashfs inside the specified ISO will be extracted and used as the chroot. This option
is useful for remastering, in combination with -A and -b or -u.
-F
Force execution and do not prompt for acknowledgment of configuration.
-g GRML_NAME
Set the grml flavour name. Common usage examples: grml, grml-small, grml64. Please do
NOT use blanks and any special characters like /, ; inside GRML_NAME, otherwise you
might notice problems while booting.
-h
Display short usage information and exit.
-i ISO_NAME
Specify name of ISO which will be available inside $OUTPUT_DIRECTORY/grml_isos by
default.
-I CHROOT_INSTALL
Specify name of source directory which provides files that should become part of the
chroot/ISO. Not enabled by default. Note: the files are installed under / in the chroot so you
have to create the rootfs structure on your own.
-n
Skip creation of the ISO file. This option is useful if you want to build/update the chroot
and/or recreate the squashfs file without building an ISO file.
-N
Bootstrap the chroot without building bootloader, squashfs, or finalizing the ISO. Use this
option if installation of some packages fails, you want to run custom commands or similar.
The main use of this option is to save time by skipping stages which aren’t necessary for
bootstrapping the chroot and which would get executed more than once when iterating
through the initial bootstrapping. Alternatively, use this option as a test run of grml-live.
Once you are satisfied with the state of your grml_chroot, use grml-live -u to build the
remaining stages and finalize the ISO.
-o OUTPUT_DIRECTORY
Main output directory of the build process of FAI. Some directories are created inside this
target directory, being: grml_cd (where the files for creating the ISO are located, including
the compressed squashfs file), grml_chroot (the chroot system) and grml_isos (where the
resulting ISO is stored).
-q
3/14
Build the ISO without (re-)creating the squashfs compressed file using mksquashfs. This
option is useful if you just want to update parts outside the chroot in the ISO. Consider
combining this option with the build-only option -b.
-Q
Build the ISO without generating a netboot package.
-r RELEASENAME
Specify name of the release.
-s SUITE
Specify the Debian suite you want to use for your live-system. If unset defaults to "testing".
Supported values are: stable, testing, unstable (or their corresponding release names like
"jessie"). Please be aware that recent Debian suites might require a recent base.tgz
debootstrap.
-t TEMPLATE_DIRECTORY
Specify place of the templates used for building the ISO. By default (and if not manually
specified) this is /usr/share/grml-live/templates/.
-u
Update existing chroot instead of rebuilding it from scratch. This option is based on the
softupdate feature of FAI.
-U USERNAME
Sets ownership of all build output files to specified username before exiting.
-v VERSION_NUMBER
Specify version number of the release.
-V
Increase verbosity in the build process.
-w DATE
The wayback machine. Build the system using Debian archives from the specified date.
Valid date formats are yyyymmddThhmmssZ or simply yyyymmdd. To learn which
snapshots exist, i.e. which date strings are valid, simply browse the lists on
http://snapshot.debian.org/. If there is no import at the exact time you specified you will get
the latest available timestamp which is before the time you specified. This option is useful
especially for release and debugging builds - for example if you know that the Debian
archive was in a good state on a specific date but you want to build it on another day in the
future, where the archive might not be as needed anymore. Please be aware that this is
restricted to the plain Debian repositories only, as referred to in
/etc/apt/sources.list.d/debian.list (so neither the Grml repositories nor any further custom
ones are affected by the wayback machine).
-z
Use ZLIB instead of LZMA/XZ compression in mksquashfs part of the build process.
5. Usage examples
4/14
5. Usage examples
To get a Debian-stable and Grml-based Live-CD using /grml/grml-live as build and output
directory just run:
# grml-live
To get a 64bit Debian-testing and grml-small based Live-CD using /srv/grml-live as build
and output directory use the following command line on your amd64 system:
# grml-live -s testing -c GRMLBASE,GRML_SMALL,AMD64 -o /srv/grml-live
If you have enough RAM, just run "mount -t tmpfs none /media/ramdisk" to get a tmpfs
("RAMDISK"), and use /media/ramdisk as build and output directory - this results in a very
fast build process. Note that these files will be gone when rebooting.
6. Main features of grml-live

create a Grml-/Debian-based Linux Live-CD with one single command
class based concept, providing a maximum of flexibility
supports integration of own hooks, scripts and configuration
supports use and integration of own Software and/or Kernels via simple use of
Debian repositories
native support of FAI features
7. The class concept

grml-live uses FAI and its class based concept for adjusting configuration and setup
according to your needs. This gives you flexibility and strength without losing the simplicity
in the build process.
The main and base class provided by grml-live is named GRMLBASE. It’s strongly
recommended to always use the class GRMLBASE when building an ISO using grml-live,
as well as the architecture dependent class which provides the kernel (being I386 for
x86_32 and AMD64 for x86_64) and a GRML_* class (like GRML_SMALL or
GRML_FULL). The following files and directories are relevant for class GRMLBASE by
default:
${GRML_FAI_CONFIG}/config/scripts/GRMLBASE/
${GRML_FAI_CONFIG}/config/debconf/GRMLBASE
${GRML_FAI_CONFIG}/config/class/GRMLBASE.var
${GRML_FAI_CONFIG}/config/hooks/instsoft.GRMLBASE
${GRML_FAI_CONFIG}/config/package_config/GRMLBASE
Take a look at the next section for information about the concept of those files/directories.
If you want to use your own configuration, extend an existing configuration and/or add
additional packages to your ISO just invent a new class (or extend an existing one). For
example if you want to use your own class named "FOOBAR" just set
5/14
CLASSES="GRMLBASE,GRML_SMALL,AMD64,FOOBAR" inside /etc/grml/grml-live.local
or invoke grml-live using the classes option: "grml-live -c
GRMLBASE,GRML_SMALL,AMD64,FOOBAR …".
More details regarding the class concept can be found in the documentation of FAI itself
(being available at /usr/share/doc/fai-doc/).
8. Available classes
The package selection part of the classes can be found in selected. The following classes
are predefined:
DEBORPHAN: get rid of all packages listed in output of deborphan
FRESHCLAM: execute freshclam (if it’s present) to update clamav definitions

(increases resulting ISO size ~70MB). By default it’s skipped to avoid bigger ISO
size.
GRMLBASE: the main class responsible for getting a minimal subset of what’s
defining a Grml system. Important parts of the buildprocess are specified in this class
as well, so unless you have a really good reason you should always use this class.
GRML_FULL: full featured Grml, also known as the "normal", full grml as introduced
in December 2011 (~460MB ISO size).
GRML_SMALL: minimum sized Grml version, known as grml-small (~230MB ISO

size).
LATEX: LaTeX(-related) packages like auctex, texlive,… (which used to be shipped

by grml before the LaTeX removal)
LATEX_CLEANUP: get rid of several very large LaTeX directories (like some
/usr/share/doc/texlive-*, /usr/share/doc/texmf,…)
LOCALES: use full featured locales setup (see /etc/locale.gen.grml). This avoids to
get rid of /usr/share/locale - which happens by default otherwise - as well.
NO_ONLINE: do not run scripts during the chroot build process which require a
network connection
RELEASE: run some specific scripts and commands to provide the workflow for an
official grml release
REMOVE_DOCS: get rid of documentation directories (like /usr/share/doc,

/usr/share/man/, /usr/share/info,…)
SOURCES: retrieve Debian source packages after installation. Files will be placed in
the output directory under grml_sources.
XORG: providing important packages for use with a base grml-featured X.org setup
6/14
9. Files
Notice that grml-live ships FAI configuration files that do not use the same namespace as
the FAI packages itself. This ensures that grml-live does not clash with your usual FAI
configuration, so instead of /etc/fai/fai.conf (package below. To get an idea how another
configuration or example files could look like check out /usr/share/doc/fai-
doc/examples/simple/ (provided by Debian package fai-doc). Furthermore
/usr/share/doc/fai-doc/fai-guide.html/ch-config.html provides documentation regarding
configuration possibilities.
/usr/sbin/grml-live
Script for the main build process. Requires root permissions for execution.
/etc/grml/grml-live.conf
Main configuration file for grml-live which should be considered as a reference configuration
file only. Please use /etc/grml/grml-live.local for local configuration instead.
/etc/grml/grml-live.local
All the local configuration should go to this file. This file overrides any defaults of grml-live.
Configurations via /etc/grml/grml-live.local are preferred over the ones from /etc/grml/grml-
live.conf. If you want to override settings from /etc/grml/grml-live.local as well you have to
specify them on the grml-live commandline.
${GRML_FAI_CONFIG}/fai.conf
Main configuration file for FAI which specifies where all the configuration files and scripts for
FAI/grml-live can be found. By default the configuration variables are
FAI_CONFIG_SRC=file:///etc/grml/fai/config and GRML_FAI_CONFIG=/etc/grml/fai/config -
both pointing to a directory shipped by grml-live out-of-the-box so you shouldn’t have to
configure anything in this file.
${GRML_FAI_CONFIG}/config/
The main directory for configuration of FAI/grml-live. More details below.
${GRML_FAI_CONFIG}/config/class/
This directory contains files which specify main configuration variables for the FAI classes.
${GRML_FAI_CONFIG}/config/debconf/
This directory provides the files for preseeding/configuration of debconf through files.
${GRML_FAI_CONFIG}/config/hooks/
This directory provides files for customising the build process through hooks. Hooks are
user defined programs or scripts, which are called during the installation process.
${GRML_FAI_CONFIG}/config/package_config/
Directory with lists of software packages to be installed or removed. The different classes
7/14
describe what should find its way to your ISO. When running "grml-live -c
GRMLBASE,GRML_SMALL,AMD64 …" only the configuration of GRMLBASE,
GRML_SMALL and and AMD64 will be taken. If you use grml-live -c
GRMLBASE,GRML_SMALL,AMD64,FOOBAR … then the files of GRMLBASE,
GRML_SMALL, AMD64 plus the files from FOOBAR will be taken. So just create a new
class to adjust the package selection according to your needs. Please notice that the
directory GRMLBASE contains a package list defining a minimum but still reasonable
package configuration.
${GRML_FAI_CONFIG}/config/scripts/
Scripts for customising the ISO within the build process.
${GRML_FAI_CONFIG}/live-initramfs/
This directory provides the files used for building the initramfs/initrd via live-initramfs(8).
10. Available log files

Starting with grml-live version 0.17.0 you should find log files in a directory named
grml_logs in the output directory (next to grml_isos, grml_chroot,…).
grml-live versions before 0.17.0 used to log into /var/log/grml-live.log and /var/log/fai/grml.
11. Requirements for the build system

any Debian based system should be sufficient (if it doesn’t work it’s a bug, please
send us a bug report then). Check out How do I deploy grml-live on a plain Debian
installation for details how to set up grml-live on a plain, original Debian system.
enough free disk space; at least 800MB are required for a minimal grml-live run
(~400MB for the chroot [$CHROOT_OUTPUT], ~150MB for the build target
[$BUILD_OUTPUT] and \~150MB for the resulting ISO [$ISO_OUTPUT] plus some
temporary files), if you plan to use GRML_FULL you should have at least 4GB of total
free disk space
fast network access for retrieving the Debian packages used for creating the chroot
(check out "local mirror" to workaround this problem as far as possible)
For further information see next section.
12. Current state of grml-live with squashfs-tools and kernel

Use squashfs-tools >=4.2-1 to build Grml (based) ISOs featuring kernel version 2.6.38-
grml[64] or newer.
13. FAQ
13.1. How do I deploy grml-live on a plain Debian installation?

8/14
The easiest way to get a running grml-live setup is to just use Grml. Of course using grml-
live on a plain, original Debian installation is supported as well. So there we go.
What we have: plain, original Debian jessie (8.x).
What we want: build a Grml ISO based on Debian/jessie for the amd64 architecture using
grml-live.
13.1.1. Instructions
# adjust sources.list:
cat >> /etc/apt/sources.list << EOF
# grml stable repository:

deb http://deb.grml.org/ grml-stable main
# deb-src http://deb.grml.org/ grml-stable main
# grml testing/development repository:

deb http://deb.grml.org/ grml-testing main
# deb-src http://deb.grml.org/ grml-testing main
EOF
# get keyring for apt:

apt-get update
apt-get --allow-unauthenticated install grml-debian-keyring
# optionally(!) install basefile so we don't have to build basic

# chroot from scratch, grab from http://daily.grml.org/
# mkdir -p /etc/grml/fai/config/basefiles/
# mv I386.tar.gz /etc/grml/fai/config/basefiles/
# mv AMD64.tar.gz /etc/grml/fai/config/basefiles/
# install relevant tools

apt-get --no-install-recommends install grml-live
# adjust grml-live configuration for our needs:

cat > /etc/grml/grml-live.local << EOF
## want a faster build process and don't need smaller ISOs?
## if so use zlib compression
# SQUASHFS_OPTIONS="-comp gzip -b 256k"
## want to use a specific squashfs binary?
# SQUASHFS_BINARY='/usr/bin/mksquashfs'
## install local files into the chroot
# CHROOT_INSTALL="/etc/grml/fai/chroot_install"
## adjust if necessary (defaults to /grml/grml-live):
## OUTPUT="/srv/grml-live"
FAI_DEBOOTSTRAP="jessie http://ftp.debian.org/debian/"
# ARCH="amd64"
CLASSES="GRMLBASE,GRML_FULL,AMD64"
EOF
# just optional(!) - upgrade FAI to latest available version:

cat >> /etc/apt/sources.list.d/fai.list << EOF
deb http://jenkins.grml.org/debian fai main
deb-src http://jenkins.grml.org/debian fai main
EOF
9/14
# get gpg key of FAI repos and install current FAI version:
wget -O - http://jenkins.grml.org/debian/C525F56752D4A654.asc | sudo apt-key add -
apt-get update
apt-get install fai-client fai-server fai-doc
That’s it. Now invoking grml-live -V should build the ISO. If everything worked as expected
the last line of the shell output should look like:
[*] Successfully finished execution of grml-live [running 687 seconds]
and the ISO can be found inside /grml-live/grml-live/grml_isos/ then.
13.2. What is $GRML_FAI_CONFIG?

The variable $GRML_FAI_CONFIG is pointing to the directory /etc/grml/fai by default. To
provide you a maximum of flexibility you can set up your own configuration directory (e.g.
based on /etc/grml/fai) and use this directory running grml-live with the -D <config_dir>
option. Now $GRML_FAI_CONFIG points to the specified directory instead of using
/etc/grml/fai and all the configuration files, scripts and hooks will be taken from your
$GRML_FAI_CONFIG directory.
13.3. I’ve problems with the build process. How to start debugging?
Check out the logs inside the directory grml_logs next to your grml_chroot, grml_isos,…
directories.
If you need help with grml-live or would like to see new features as part of grml-live you can
get commercial support via Grml Solutions.
13.4. How do I install further files into the chroot/ISO?

Just point the configuration variable CHROOT_INSTALL to the directory which provides the
files you would like to install. Note that the files are installed under / in the chroot - so you
have to create the rootfs structure on your own. Usage example:
echo "CHROOT_INSTALL=\$GRML_FAI_CONFIG/chroot_install" >> /etc/grml/grml-live.local

mkdir -p /etc/grml/fai/chroot_install/usr/src/
wget example.org/foo.tar.gz
mv foo.tar.gz /etc/grml/fai/chroot_install/usr/src/
grml-live ...
13.5. Can I use my own (local) Debian mirror?

Yes. Set up an according sources.list configuration as class file in FAI_DEBOOTSTRAP (if
not already using a base.tgz) inside /etc/grml/grml-live.conf[.local]. If you’re setting up your
own class file don’t forget to include the class name in the class list (grml-live -c …).
If you want to use a local (for example NFS mount) mirror additionally then adjust
MIRROR_DIRECTORY in /etc/grml/grml-live.conf[.local] as well.
If you want to use a HTTP Proxy (like apt-cacher-ng), set APT_PROXY. Example:
APT_PROXY="http://localhost:3142/"
10/14
13.6. How do I add additional Debian package(s) to my CD/ISO?
Just create a new class (using the package_config directory):
# cat > /etc/grml/fai/config/package_config/MIKA << EOF

PACKAGES aptitude
vim
another_name_of_a_debian_package
and_another_one
EOF
and specify it when invoking grml-live then:
# grml-live -c GRMLBASE,GRML_SMALL,AMD64,MIKA
13.7. I fscked up my grml-live configuration. How do I reset it to the

defaults?
Notice: this deletes all your grml-live configuration files. If that’s really what you are
searching for just run:
rm -rf /etc/grml/fai /etc/grml/grml-live.conf

dpkg -i --force-confnew --force-confmiss /path/to/grml-live_..._all.deb
13.8. Set up apt-cacher-ng for use with grml-live

Make sure /etc/grml/grml-live.local provides according APT_PROXY and
FAI_DEBOOTSTRAP:
# cat /etc/grml/grml-live.local
[...]
[...]
FAI_DEBOOTSTRAP="jessie http://localhost:3142/ftp.debian.org/debian jessie main
contrib non-free"
Make sure apt-cacher-ng is running (/etc/init.d/apt-cacher-ng restart). That’s it. All

downloaded files will be cached in /var/cache/apt-cacher-ng then.
13.9. How do I revert the manifold feature from an ISO?

The so called manifold feature Grml ISOs use by default allows one to use the same ISO
for CD boot and USB boot. If you notice any problems when booting just revert the manifold
feature running:
% dd if=/dev/zero of=grml.iso bs=512 count=1 conv=notrunc
To switch from manifold to isohybrid mode (an alternative approach provided by syslinux)
then just execute:
% isohybrid grml.iso
13.10. How do I create a base tar.gz (I386.tar.gz or AMD64.tar.gz)

First of all create the chroot using debootstrap (requires root):
11/14
BASECHROOT='/tmp/basefile' # path where the chroot gets generated
SUITE='jessie' # using the current stable release should always work
debootstrap --exclude=info,tasksel,tasksel-data "$SUITE" "$BASECHROOT"
http://ftp.debian.org/debian
tar -C "$BASECHROOT" --exclude='var/cache/apt/archives/*.deb' -zcf "${SUITE}".tar.gz
./
By default debootstrap builds a chroot matching the architecture of the running host
system. If you’re using an amd64 system and want to build an i386 base.tgz then invoke
debootstrap using the --arch i386 option. Disclaimer: building an AMD64 base.tgz won’t
work if you are using a 32bit kernel system of course.
Finally place the generated tarball in /etc/grml/fai/config/basefiles/ (note that it needs to be

uppercase letters matching the class names, so: e.g. AMD64.tar.gz for amd64 and
I386.tar.gz for i386).
Then executing grml-live should use this file as base system instead of executing
debootstrap. Check out the output for something like:
[...]
ftar: extracting //etc/grml/fai/config/basefiles///AMD64.tar.gz to
/srv/grml64_testing/grml_chroot//
[...]
13.11. How to use your own local repository

Let’s assume you have Debian package(s) in your filesystem inside /home/foobar/local-
packages and want to provide them to your grml-live build. This can be achieved either 1)
through a bind mount (using the MIRROR_DIRECTORY configuration) or 2) by serving a
repository via HTTP.
13.11.1. Serving via bind mount / MIRROR_DIRECTORY
Make sure to create an according sources.list configuration file, e.g. using your own class
name CUSTOM :
# cat > /etc/grml/fai/config/files/etc/apt/sources.list.d/local-packages.list/CUSTOM

<< EOF
deb file:///home/foobar/local-packages ./
EOF
Add the according MIRROR_DIRECTORY configuration to your grml-live configuration:
# echo "MIRROR_DIRECTORY='/home/foobar/packages'" >> /etc/grml/grml-live.local
Make sure the local directory looks like a mirror:
% cd /home/foobar/packages
% dpkg-scanpackages . /dev/null | gzip > Packages.gz
Finally invoke grml-live with your class name ( CUSTOM in this example) added to the list of
classes on the command line (see grml-live option -c ).
13.11.2. Serving a repository via HTTP

12/14
name CUSTOM :

<< EOF
deb http://127.0.0.1:8000/ ./
EOF
Make sure the local directory is served via HTTP on the according IP address and port. For
the http://127.0.0.1:8000/ example from above it should be enough to just invoke:
% python -m SimpleHTTPServer 8000
Of course you can also use a real Debian repository setup using tools like reprepro(1)
and/or using a real web server, though for quick debugging sessions python’s
SimpleHTTPServer in combination with dpkg-scanpackages from package dpkg-dev is a
simple and easy approach.
14. Download / install grml-live as a Debian package

Stable Debian packages are available through the grml-repository at deb.grml.org and the
latest Git commits are available as Debian packages from jenkins.grml.org. If you want to
build a Debian package on your own (using for example a specific version or the current
development tree), just execute:
git clone git://git.grml.org/grml-live

cd grml-live
debuild -us -uc
15. Run grml-live directly from git

In case you want to run grml-live directly from the git repository checkout (after making sure
all dependencies are installed), you should set GRML_FAI_CONFIG so that a) it finds the
according FAI configuration files and b) does not use the config files of an possibly installed
grml-live package. Usage example:
# export GRML_FAI_CONFIG=$(pwd)/etc/grml/fai
# export SCRIPTS_DIRECTORY=$(pwd)/scripts
# ./grml-live -s sid -a amd64 -c GRMLBASE,GRML_FULL,AMD64
16. Source
The source of grml-live is available at https://github.com/grml/grml-live/
17. Bugs
Please report feedback, bugreports and wishes to the Grml team!
13/14
19. Authors
Michael Prokop <mika@grml.org>
14/14
grml-live(8)
grml.org/grml-live/
1. Name
grml-live - build framework based on FAI for generating a Grml and Debian based Linux
Live system (CD/ISO)
2. Synopsis
grml-live [-a <architecture>] [-c <classe[s]>] [-C <configfile>] [ -e <extract_iso_name>] [-g
<grml_name>] [-i <iso_name>] [ -o <output_directory>] [-r <release_name>] [-s <suite>] [ -t
<template_directory>] [-v <version_number>] [-U <username>] [ -w <date>] [-
AbBFnNqQuVz]
3. Description
grml-live provides the build system for creating a Grml and Debian based Linux Live-CD.
The build system is based on FAI (Fully Automatic Installation). grml-live uses the "fai
dirinstall" feature to generate a chroot system based on the class concept of FAI (see later
sections for further details) and provides the framework to be able to generate a full-
featured ISO. It does not use all the FAI features by default though and you don’t have to
know FAI to be able to use it.
The use of FAI gives you the flexibility to choose the packages you would like to include on
your very own Linux Live-CD without having to deal with all the details of a build process.
grml-live does not use /etc/fai for configuration but instead (unless overridden using the '-
D' option). This ensures that it does not clash with default FAI configuration and packages,
so you can use grml-live and FAI completely independent at the same time!
Please notice that you should have a fast network connection as all the Debian packages
will be downloaded and installed via network. If you want to use a local mirror (strongly
recommended if you plan to use grml-live more than once) checkout mkdebmirror (see
/usr/share/doc/grml-live/examples/mkdebmirror), debmirror(1), reprepro(1) (see
/usr/share/doc/grml-live/examples/reprepro/ for a sample configuration), apt-cacher(1) and
approx(8). To avoid downloading the base system again and again check out the base
tar.gz feature.
4. Options
-A
Clean up all output directories before running the build process. After finishing, clean up the
Chroot target and Build target directories.
-a ARCHITECTURE
Use the specified architecture instead of the currently running one. This allows building a
1/14
32bit system on a 64bit host (though you can’t build a 64bit system on a 32bit
system/kernel of course). Please notice that real crosscompiling (like building a ppc system
on x86) isn’t possible due to the nature and the need of working in a chroot. Currently
supported values: i386 and amd64.
-b
Build the ISO without updating the chroot via FAI. This option is useful for example when
working on stable releases: if you have a working base system/chroot and do not want to
execute any further updates (via "-u" option) but intend to only build the ISO.
-B
Build the ISO without touching the chroot at all. This option is useful if you modified
anything that FAI or grml-live might adjust via Grml’s FAI scripts. It’s like the -b option but
even more advanced. Use only if you really know that you do not want to update the chroot.
-c CLASSES
Specify the CLASSES to be used for building the ISO via FAI. By default only the classes
GRMLBASE, GRML_FULL and I386/AMD64 (depending on system architecture) are
assumed, resulting in a base system of about 350MB total ISO size. If using a non-I386
system (like AMD64) you should specify the appropriate architecture as well. Additionally
you can specify a class providing a grml-kernel (see the CLASSES section in this document
for details about available classes). So instead of GRML_FULL you can also use
GRML_SMALL and GRML_FULL.
All class names should be written in uppercase letters. Do not use a dash, use an
underscore. So do not use "amd64" but "AMD64", do not use "FOO BAR" but
"FOO_BAR".
-C CONFIGURATION_FILE
The specified file is used as configuration file for grml-live. By default /etc/grml/grml-
live.conf is used as default configuration. If a file named /etc/grml/grml-live.local exists it is
used as well (sourced after reading /etc/grml/grml-live.conf meant as main file for local
configuration). As a last option the specified configuration file is sourced so it is possible to
override settings of /etc/grml/grml-live.conf as well as of /etc/grml/grml-live.local. Please
notice that all configuration files have to be adjusted during execution of grml-live, so
please make sure you use /etc/grml/grml-live.conf as a base for your own configuration file
(usually /etc/grml/grml-live.local). Please also notice that the configuration file specified via
this option is not (yet) /etc/grml/grml-live.local for configuration stuff used inside
-d DATE
Use specified date as build date information on the ISO instead of the default. The default
is the date when grml-live is being executed (retrieved via executing date +%Y-%m-%d).
The information is stored inside the file /GRML/grml-version on the ISO, /etc/grml_version
in the squashfs file and in all the bootsplash related files. This option is useful if you want to
provide an ISO with release information for a specific date but have to build it in advance.
Usage example: -d 2009-10-30
-D CONFIGURATION_DIRECTORY
The specified directory is used as configuration directory for grml-live and its FAI. By
2/14
default /etc/grml/fai is used as default configuration directory. If you want to have different
configuration scripts, package definitions, etc. with without messing with the global
configuration under /etc/grml/fai provided by grml-live this option provides you the option to
use your own configuration throughout this documentation.
-e EXTRACT_ISO_NAME
The squashfs inside the specified ISO will be extracted and used as the chroot. This option
is useful for remastering, in combination with -A and -b or -u.
-F
Force execution and do not prompt for acknowledgment of configuration.
-g GRML_NAME
Set the grml flavour name. Common usage examples: grml, grml-small, grml64. Please do
NOT use blanks and any special characters like /, ; inside GRML_NAME, otherwise you
might notice problems while booting.
-h
Display short usage information and exit.
-i ISO_NAME
Specify name of ISO which will be available inside $OUTPUT_DIRECTORY/grml_isos by
default.
-I CHROOT_INSTALL
Specify name of source directory which provides files that should become part of the
chroot/ISO. Not enabled by default. Note: the files are installed under / in the chroot so you
have to create the rootfs structure on your own.
-n
Skip creation of the ISO file. This option is useful if you want to build/update the chroot
and/or recreate the squashfs file without building an ISO file.
-N
Bootstrap the chroot without building bootloader, squashfs, or finalizing the ISO. Use this
option if installation of some packages fails, you want to run custom commands or similar.
The main use of this option is to save time by skipping stages which aren’t necessary for
bootstrapping the chroot and which would get executed more than once when iterating
through the initial bootstrapping. Alternatively, use this option as a test run of grml-live.
Once you are satisfied with the state of your grml_chroot, use grml-live -u to build the
remaining stages and finalize the ISO.
-o OUTPUT_DIRECTORY
Main output directory of the build process of FAI. Some directories are created inside this
target directory, being: grml_cd (where the files for creating the ISO are located, including
the compressed squashfs file), grml_chroot (the chroot system) and grml_isos (where the
resulting ISO is stored).
-q
3/14
Build the ISO without (re-)creating the squashfs compressed file using mksquashfs. This
option is useful if you just want to update parts outside the chroot in the ISO. Consider
combining this option with the build-only option -b.
-Q
Build the ISO without generating a netboot package.
-r RELEASENAME
Specify name of the release.
-s SUITE
Specify the Debian suite you want to use for your live-system. If unset defaults to "testing".
Supported values are: stable, testing, unstable (or their corresponding release names like
"jessie"). Please be aware that recent Debian suites might require a recent base.tgz
debootstrap.
-t TEMPLATE_DIRECTORY
Specify place of the templates used for building the ISO. By default (and if not manually
specified) this is /usr/share/grml-live/templates/.
-u
Update existing chroot instead of rebuilding it from scratch. This option is based on the
softupdate feature of FAI.
-U USERNAME
Sets ownership of all build output files to specified username before exiting.
-v VERSION_NUMBER
Specify version number of the release.
-V
Increase verbosity in the build process.
-w DATE
The wayback machine. Build the system using Debian archives from the specified date.
Valid date formats are yyyymmddThhmmssZ or simply yyyymmdd. To learn which
snapshots exist, i.e. which date strings are valid, simply browse the lists on
http://snapshot.debian.org/. If there is no import at the exact time you specified you will get
the latest available timestamp which is before the time you specified. This option is useful
especially for release and debugging builds - for example if you know that the Debian
archive was in a good state on a specific date but you want to build it on another day in the
future, where the archive might not be as needed anymore. Please be aware that this is
restricted to the plain Debian repositories only, as referred to in
/etc/apt/sources.list.d/debian.list (so neither the Grml repositories nor any further custom
ones are affected by the wayback machine).
-z
Use ZLIB instead of LZMA/XZ compression in mksquashfs part of the build process.
5. Usage examples
4/14
5. Usage examples
To get a Debian-stable and Grml-based Live-CD using /grml/grml-live as build and output
directory just run:
# grml-live
To get a 64bit Debian-testing and grml-small based Live-CD using /srv/grml-live as build
and output directory use the following command line on your amd64 system:
# grml-live -s testing -c GRMLBASE,GRML_SMALL,AMD64 -o /srv/grml-live
If you have enough RAM, just run "mount -t tmpfs none /media/ramdisk" to get a tmpfs
("RAMDISK"), and use /media/ramdisk as build and output directory - this results in a very
fast build process. Note that these files will be gone when rebooting.
6. Main features of grml-live

create a Grml-/Debian-based Linux Live-CD with one single command
class based concept, providing a maximum of flexibility
supports integration of own hooks, scripts and configuration
supports use and integration of own Software and/or Kernels via simple use of
Debian repositories
native support of FAI features
7. The class concept

grml-live uses FAI and its class based concept for adjusting configuration and setup
according to your needs. This gives you flexibility and strength without losing the simplicity
in the build process.
The main and base class provided by grml-live is named GRMLBASE. It’s strongly
recommended to always use the class GRMLBASE when building an ISO using grml-live,
as well as the architecture dependent class which provides the kernel (being I386 for
x86_32 and AMD64 for x86_64) and a GRML_* class (like GRML_SMALL or
GRML_FULL). The following files and directories are relevant for class GRMLBASE by
default:
${GRML_FAI_CONFIG}/config/scripts/GRMLBASE/
${GRML_FAI_CONFIG}/config/debconf/GRMLBASE
${GRML_FAI_CONFIG}/config/class/GRMLBASE.var
${GRML_FAI_CONFIG}/config/hooks/instsoft.GRMLBASE
${GRML_FAI_CONFIG}/config/package_config/GRMLBASE
Take a look at the next section for information about the concept of those files/directories.
If you want to use your own configuration, extend an existing configuration and/or add
additional packages to your ISO just invent a new class (or extend an existing one). For
example if you want to use your own class named "FOOBAR" just set
5/14
CLASSES="GRMLBASE,GRML_SMALL,AMD64,FOOBAR" inside /etc/grml/grml-live.local
or invoke grml-live using the classes option: "grml-live -c
GRMLBASE,GRML_SMALL,AMD64,FOOBAR …".
More details regarding the class concept can be found in the documentation of FAI itself
(being available at /usr/share/doc/fai-doc/).
8. Available classes
The package selection part of the classes can be found in selected. The following classes
are predefined:
DEBORPHAN: get rid of all packages listed in output of deborphan
FRESHCLAM: execute freshclam (if it’s present) to update clamav definitions

(increases resulting ISO size ~70MB). By default it’s skipped to avoid bigger ISO
size.
GRMLBASE: the main class responsible for getting a minimal subset of what’s
defining a Grml system. Important parts of the buildprocess are specified in this class
as well, so unless you have a really good reason you should always use this class.
GRML_FULL: full featured Grml, also known as the "normal", full grml as introduced
in December 2011 (~460MB ISO size).
GRML_SMALL: minimum sized Grml version, known as grml-small (~230MB ISO

size).
LATEX: LaTeX(-related) packages like auctex, texlive,… (which used to be shipped

by grml before the LaTeX removal)
LATEX_CLEANUP: get rid of several very large LaTeX directories (like some
/usr/share/doc/texlive-*, /usr/share/doc/texmf,…)
LOCALES: use full featured locales setup (see /etc/locale.gen.grml). This avoids to
get rid of /usr/share/locale - which happens by default otherwise - as well.
NO_ONLINE: do not run scripts during the chroot build process which require a
network connection
RELEASE: run some specific scripts and commands to provide the workflow for an
official grml release
REMOVE_DOCS: get rid of documentation directories (like /usr/share/doc,

/usr/share/man/, /usr/share/info,…)
SOURCES: retrieve Debian source packages after installation. Files will be placed in
the output directory under grml_sources.
XORG: providing important packages for use with a base grml-featured X.org setup
6/14
9. Files
Notice that grml-live ships FAI configuration files that do not use the same namespace as
the FAI packages itself. This ensures that grml-live does not clash with your usual FAI
configuration, so instead of /etc/fai/fai.conf (package below. To get an idea how another
configuration or example files could look like check out /usr/share/doc/fai-
doc/examples/simple/ (provided by Debian package fai-doc). Furthermore
/usr/share/doc/fai-doc/fai-guide.html/ch-config.html provides documentation regarding
configuration possibilities.
/usr/sbin/grml-live
Script for the main build process. Requires root permissions for execution.
/etc/grml/grml-live.conf
Main configuration file for grml-live which should be considered as a reference configuration
file only. Please use /etc/grml/grml-live.local for local configuration instead.
/etc/grml/grml-live.local
All the local configuration should go to this file. This file overrides any defaults of grml-live.
Configurations via /etc/grml/grml-live.local are preferred over the ones from /etc/grml/grml-
live.conf. If you want to override settings from /etc/grml/grml-live.local as well you have to
specify them on the grml-live commandline.
${GRML_FAI_CONFIG}/fai.conf
Main configuration file for FAI which specifies where all the configuration files and scripts for
FAI/grml-live can be found. By default the configuration variables are
FAI_CONFIG_SRC=file:///etc/grml/fai/config and GRML_FAI_CONFIG=/etc/grml/fai/config -
both pointing to a directory shipped by grml-live out-of-the-box so you shouldn’t have to
configure anything in this file.
${GRML_FAI_CONFIG}/config/
The main directory for configuration of FAI/grml-live. More details below.
${GRML_FAI_CONFIG}/config/class/
This directory contains files which specify main configuration variables for the FAI classes.
${GRML_FAI_CONFIG}/config/debconf/
This directory provides the files for preseeding/configuration of debconf through files.
${GRML_FAI_CONFIG}/config/hooks/
This directory provides files for customising the build process through hooks. Hooks are
user defined programs or scripts, which are called during the installation process.
${GRML_FAI_CONFIG}/config/package_config/
Directory with lists of software packages to be installed or removed. The different classes
7/14
describe what should find its way to your ISO. When running "grml-live -c
GRMLBASE,GRML_SMALL,AMD64 …" only the configuration of GRMLBASE,
GRML_SMALL and and AMD64 will be taken. If you use grml-live -c
GRMLBASE,GRML_SMALL,AMD64,FOOBAR … then the files of GRMLBASE,
GRML_SMALL, AMD64 plus the files from FOOBAR will be taken. So just create a new
class to adjust the package selection according to your needs. Please notice that the
directory GRMLBASE contains a package list defining a minimum but still reasonable
package configuration.
${GRML_FAI_CONFIG}/config/scripts/
Scripts for customising the ISO within the build process.
${GRML_FAI_CONFIG}/live-initramfs/
This directory provides the files used for building the initramfs/initrd via live-initramfs(8).
10. Available log files

Starting with grml-live version 0.17.0 you should find log files in a directory named
grml_logs in the output directory (next to grml_isos, grml_chroot,…).
grml-live versions before 0.17.0 used to log into /var/log/grml-live.log and /var/log/fai/grml.
11. Requirements for the build system

any Debian based system should be sufficient (if it doesn’t work it’s a bug, please
send us a bug report then). Check out How do I deploy grml-live on a plain Debian
installation for details how to set up grml-live on a plain, original Debian system.
enough free disk space; at least 800MB are required for a minimal grml-live run
(~400MB for the chroot [$CHROOT_OUTPUT], ~150MB for the build target
[$BUILD_OUTPUT] and \~150MB for the resulting ISO [$ISO_OUTPUT] plus some
temporary files), if you plan to use GRML_FULL you should have at least 4GB of total
free disk space
fast network access for retrieving the Debian packages used for creating the chroot
(check out "local mirror" to workaround this problem as far as possible)
For further information see next section.
12. Current state of grml-live with squashfs-tools and kernel

Use squashfs-tools >=4.2-1 to build Grml (based) ISOs featuring kernel version 2.6.38-
grml[64] or newer.
13. FAQ
13.1. How do I deploy grml-live on a plain Debian installation?

8/14
The easiest way to get a running grml-live setup is to just use Grml. Of course using grml-
live on a plain, original Debian installation is supported as well. So there we go.
What we have: plain, original Debian jessie (8.x).
What we want: build a Grml ISO based on Debian/jessie for the amd64 architecture using
grml-live.
13.1.1. Instructions
# adjust sources.list:
cat >> /etc/apt/sources.list << EOF
# grml stable repository:

deb http://deb.grml.org/ grml-stable main
# deb-src http://deb.grml.org/ grml-stable main
# grml testing/development repository:

deb http://deb.grml.org/ grml-testing main
# deb-src http://deb.grml.org/ grml-testing main
EOF
# get keyring for apt:

apt-get update
apt-get --allow-unauthenticated install grml-debian-keyring
# optionally(!) install basefile so we don't have to build basic

# chroot from scratch, grab from http://daily.grml.org/
# mkdir -p /etc/grml/fai/config/basefiles/
# mv I386.tar.gz /etc/grml/fai/config/basefiles/
# mv AMD64.tar.gz /etc/grml/fai/config/basefiles/
# install relevant tools

apt-get --no-install-recommends install grml-live
# adjust grml-live configuration for our needs:

cat > /etc/grml/grml-live.local << EOF
## want a faster build process and don't need smaller ISOs?
## if so use zlib compression
# SQUASHFS_OPTIONS="-comp gzip -b 256k"
## want to use a specific squashfs binary?
# SQUASHFS_BINARY='/usr/bin/mksquashfs'
## install local files into the chroot
# CHROOT_INSTALL="/etc/grml/fai/chroot_install"
## adjust if necessary (defaults to /grml/grml-live):
## OUTPUT="/srv/grml-live"
FAI_DEBOOTSTRAP="jessie http://ftp.debian.org/debian/"
# ARCH="amd64"
CLASSES="GRMLBASE,GRML_FULL,AMD64"
EOF
# just optional(!) - upgrade FAI to latest available version:

cat >> /etc/apt/sources.list.d/fai.list << EOF
deb http://jenkins.grml.org/debian fai main
deb-src http://jenkins.grml.org/debian fai main
EOF
9/14
# get gpg key of FAI repos and install current FAI version:
wget -O - http://jenkins.grml.org/debian/C525F56752D4A654.asc | sudo apt-key add -
apt-get update
apt-get install fai-client fai-server fai-doc
That’s it. Now invoking grml-live -V should build the ISO. If everything worked as expected
the last line of the shell output should look like:
[*] Successfully finished execution of grml-live [running 687 seconds]
and the ISO can be found inside /grml-live/grml-live/grml_isos/ then.
13.2. What is $GRML_FAI_CONFIG?

The variable $GRML_FAI_CONFIG is pointing to the directory /etc/grml/fai by default. To
provide you a maximum of flexibility you can set up your own configuration directory (e.g.
based on /etc/grml/fai) and use this directory running grml-live with the -D <config_dir>
option. Now $GRML_FAI_CONFIG points to the specified directory instead of using
/etc/grml/fai and all the configuration files, scripts and hooks will be taken from your
$GRML_FAI_CONFIG directory.
13.3. I’ve problems with the build process. How to start debugging?
Check out the logs inside the directory grml_logs next to your grml_chroot, grml_isos,…
directories.
If you need help with grml-live or would like to see new features as part of grml-live you can
get commercial support via Grml Solutions.
13.4. How do I install further files into the chroot/ISO?

Just point the configuration variable CHROOT_INSTALL to the directory which provides the
files you would like to install. Note that the files are installed under / in the chroot - so you
have to create the rootfs structure on your own. Usage example:
echo "CHROOT_INSTALL=\$GRML_FAI_CONFIG/chroot_install" >> /etc/grml/grml-live.local

mkdir -p /etc/grml/fai/chroot_install/usr/src/
wget example.org/foo.tar.gz
mv foo.tar.gz /etc/grml/fai/chroot_install/usr/src/
grml-live ...
13.5. Can I use my own (local) Debian mirror?

Yes. Set up an according sources.list configuration as class file in FAI_DEBOOTSTRAP (if
not already using a base.tgz) inside /etc/grml/grml-live.conf[.local]. If you’re setting up your
own class file don’t forget to include the class name in the class list (grml-live -c …).
If you want to use a local (for example NFS mount) mirror additionally then adjust
MIRROR_DIRECTORY in /etc/grml/grml-live.conf[.local] as well.
If you want to use a HTTP Proxy (like apt-cacher-ng), set APT_PROXY. Example:
10/14
13.6. How do I add additional Debian package(s) to my CD/ISO?
Just create a new class (using the package_config directory):
# cat > /etc/grml/fai/config/package_config/MIKA << EOF

PACKAGES aptitude
vim
another_name_of_a_debian_package
and_another_one
EOF
and specify it when invoking grml-live then:
# grml-live -c GRMLBASE,GRML_SMALL,AMD64,MIKA
13.7. I fscked up my grml-live configuration. How do I reset it to the

defaults?
Notice: this deletes all your grml-live configuration files. If that’s really what you are
searching for just run:
rm -rf /etc/grml/fai /etc/grml/grml-live.conf

dpkg -i --force-confnew --force-confmiss /path/to/grml-live_..._all.deb
13.8. Set up apt-cacher-ng for use with grml-live

Make sure /etc/grml/grml-live.local provides according APT_PROXY and
FAI_DEBOOTSTRAP:
# cat /etc/grml/grml-live.local
[...]
[...]
FAI_DEBOOTSTRAP="jessie http://localhost:3142/ftp.debian.org/debian jessie main
contrib non-free"
Make sure apt-cacher-ng is running (/etc/init.d/apt-cacher-ng restart). That’s it. All

downloaded files will be cached in /var/cache/apt-cacher-ng then.
13.9. How do I revert the manifold feature from an ISO?

The so called manifold feature Grml ISOs use by default allows one to use the same ISO
for CD boot and USB boot. If you notice any problems when booting just revert the manifold
feature running:
% dd if=/dev/zero of=grml.iso bs=512 count=1 conv=notrunc
To switch from manifold to isohybrid mode (an alternative approach provided by syslinux)
then just execute:
% isohybrid grml.iso
13.10. How do I create a base tar.gz (I386.tar.gz or AMD64.tar.gz)

First of all create the chroot using debootstrap (requires root):
11/14
BASECHROOT='/tmp/basefile' # path where the chroot gets generated
SUITE='jessie' # using the current stable release should always work
debootstrap --exclude=info,tasksel,tasksel-data "$SUITE" "$BASECHROOT"
http://ftp.debian.org/debian
tar -C "$BASECHROOT" --exclude='var/cache/apt/archives/*.deb' -zcf "${SUITE}".tar.gz
./
By default debootstrap builds a chroot matching the architecture of the running host
system. If you’re using an amd64 system and want to build an i386 base.tgz then invoke
debootstrap using the --arch i386 option. Disclaimer: building an AMD64 base.tgz won’t
work if you are using a 32bit kernel system of course.
Finally place the generated tarball in /etc/grml/fai/config/basefiles/ (note that it needs to be

uppercase letters matching the class names, so: e.g. AMD64.tar.gz for amd64 and
I386.tar.gz for i386).
Then executing grml-live should use this file as base system instead of executing
debootstrap. Check out the output for something like:
[...]
ftar: extracting //etc/grml/fai/config/basefiles///AMD64.tar.gz to
/srv/grml64_testing/grml_chroot//
[...]
13.11. How to use your own local repository

Let’s assume you have Debian package(s) in your filesystem inside /home/foobar/local-
packages and want to provide them to your grml-live build. This can be achieved either 1)
through a bind mount (using the MIRROR_DIRECTORY configuration) or 2) by serving a
repository via HTTP.
13.11.1. Serving via bind mount / MIRROR_DIRECTORY
name CUSTOM :

<< EOF
deb file:///home/foobar/local-packages ./
EOF
Add the according MIRROR_DIRECTORY configuration to your grml-live configuration:
# echo "MIRROR_DIRECTORY='/home/foobar/packages'" >> /etc/grml/grml-live.local
Make sure the local directory looks like a mirror:
13.11.2. Serving a repository via HTTP

12/14
name CUSTOM :

<< EOF
deb http://127.0.0.1:8000/ ./
EOF
Make sure the local directory is served via HTTP on the according IP address and port. For
the http://127.0.0.1:8000/ example from above it should be enough to just invoke:
% python -m SimpleHTTPServer 8000
Of course you can also use a real Debian repository setup using tools like reprepro(1)
and/or using a real web server, though for quick debugging sessions python’s
SimpleHTTPServer in combination with dpkg-scanpackages from package dpkg-dev is a
simple and easy approach.
14. Download / install grml-live as a Debian package

Stable Debian packages are available through the grml-repository at deb.grml.org and the
latest Git commits are available as Debian packages from jenkins.grml.org. If you want to
build a Debian package on your own (using for example a specific version or the current
development tree), just execute:
git clone git://git.grml.org/grml-live

cd grml-live
debuild -us -uc
15. Run grml-live directly from git

In case you want to run grml-live directly from the git repository checkout (after making sure
all dependencies are installed), you should set GRML_FAI_CONFIG so that a) it finds the
according FAI configuration files and b) does not use the config files of an possibly installed
grml-live package. Usage example:
# export GRML_FAI_CONFIG=$(pwd)/etc/grml/fai
# export SCRIPTS_DIRECTORY=$(pwd)/scripts
# ./grml-live -s sid -a amd64 -c GRMLBASE,GRML_FULL,AMD64
16. Source
The source of grml-live is available at https://github.com/grml/grml-live/
17. Bugs
Please report feedback, bugreports and wishes to the Grml team!
13/14
19. Authors
14/14
Search Fedora Project Wiki  Links Subprojects Log In
Livecd-iso-to-disk
Page Discussion History View source View
livecd-iso-to-disk.sh is a Bash shell script from livecd-tools, https://github.com/livecd-tools/livecd-tools/blob/master/tools/livecd-iso-to-

disk.sh
Note: There are some variations of the script for different versions of Fedora (see livecd-tools All branches ).
Before Fedora 24 the script was usually available in the installation disc's filesystem at /LiveOS/livecd-iso-to-disk . From a
booted LiveOS filesystem, the outer USB/SD/CD/DVD device filesystem is mounted on the /run/initramfs/live/ mount point (or at
/mnt/live/ on Fedora 16 and earlier).
Usage is documented
in the first 270 or so lines of the the script,

in https://github.com/livecd-tools/livecd-tools/blob/master/docs/livecd-iso-to-disk.pod ,
and is accessible with the livecd-iso-to-disk --help command.
Category: LiveMedia
Copyright © 2018 Red Hat, Inc. and others. All Rights Reserved. For comments or queries, please contact us.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for
content.
This page was last edited on 16 July 2018, at 01:57. Content is available under Attribution-Share Alike 3.0 Unported unless otherwise noted.
Privacy policy About Fedora Project Wiki Disclaimers Sponsors Legal Trademark Guidelines
Homepage Forums Manual Quick Start Disk Partitioning LVM Guide
Cheap
Linux
INSTALLING SYSTEMRESCUECD ON THE DISK
DVD
SystemRescue
OpenSUSE
Ubuntu
Fedora
CentOS
Introduction
DebianThere is an easy way to boot SystemRescueCd from the harddisk. It can be convenient if you often want to boot on
Linux SystemRescueCd as it will be faster and there is no need to insert any media before you restart your computer. This method
Mint allows to use SystemRescueCd as you do with the CDRom version. It also allows to boot SystemRescueCd if you do not have
any CD/DVD drive or USB socket in your computer. You can use another operating system to process the installation of
Knoppix
SystemRescueCd, and enable it. Thus, this method is recommended if you often use SystemRescueCd and you want to avoid
having to insert the disc in the drive each time.
Site
map The installation is done by copying files from the SystemRescueCd media to the local filesystem where your operating system
is installed. This approach does not require any repartitioning of your disk. Using grub4dos you can even install
Homepage
SystemRescueCd on a Windows NTFS partition. All you have to do is to install the files that are on the SystemRescueCd disc to
Download
an existing partition on your local disk, that can be either a linux partition (ext4, xfs, …) or a Windows one (NTFS). That way
you can boot SystemRescueCd from your Windows partition, and using the
ChangeLog
System
```ntpass``` to reset the administrator password or ```ntfs-3g``` to work on
tools the filesystem where it is installed.
Bootable
There are two steps in this installation: first you will have to copy the main
USB SystemRescueCd files onto a partition of your disk. Then, you will have to
Beta configure your boot loader. The installation process requires a partition with
about 1GB of free space. You must have a working Linux boot loader such as Grub
versions
installed if you want to install the SystemRescueCd files on a Linux partition.
Package
Four kernels are provided with SystemRescueCd: ```rescue32```, ```rescue64```,
list
``àltker32```, ``àltker64```. In this chapter we will consider you are using
Screenshots
```rescue64``` but you can just do the same thing with any other kernel that is
provided with SystemRescueCd.
Customization
Docum
Kernel The last section of this page explains how to boot SystemRescueCd from the hard
disk as an ISO image. You can do that if you have Linux installed on your disk
Manua
Modules
with Grub2 as the boot loader. This alternative method is more convenient if you LVM Gu
FAQ want to frequently update SystemRescueCd on your disk. All you will have to do
Disk pa
is to update the copy of the ISO image on your disk if you follow this method.
Documentation Networ
## First step: copy important files Manua
ManualThis
(EN) step is very trivial: you just have to copy the SystemRescueCd main files
to the partition. If that is a Windows partition, you can perform the copy with
LVM Guide
any operating system. Of course, if you choose a Linux native partition, you Related
Disk partitioning
will have to copy from Linux (you can copy from SystemRescueCd itself). Source
Networking
You must create a directory ```/sysrcd/``` and this directory must be in the FSArch
Manual (FR)
root of the partition (not a subdirectory)
Now, take the disc with the latest SystemRescueCd version (you may prefer to
mount the ISO image with mount under Linux
(eg: ```mount -o loop systemrescuecd-x86-x.y.z.iso /mnt/cdrom```) or you can use
a software such as Daemon-Tools under Windows if you did not burn the disc), in
order to have the main files.
Finally, just copy ```sysrcd.dat```, ```sysrcd.md5```, ``ìnitram.igz```,

```rescue32```, ```rescue64```, ``àltker32```, ``àltker64``` from the CDRom to
the directory you made (```/sysrcd/```). Some of these files are located in
``ìsolinux``` inside of the CDRom. You must not keep the directory structure.
All the files must be copied to the ```sysrcd``` directory.
## Second step: update the Linux bootmanager configuration (if you install on Linux)
Now, you must update your bootmanager (Lilo or Grub). This section describe how
to update a boot manager based on linux (lilo or grub). If you are using an NTFS
partition, please read the next section instead.
We will have to add several lines to the configuration file of the bootmanager
(usually ```/etc/grub.d/``` for Grub2). You have to customize the configuration
given there. With grub, you will have to give the grub device name for the
partition you have chosen. It is usually a name such as ```(hd0,0)``` instead of
```sda1``` or ```(hd0,1)``` instead of ```sda2```, ... Then, you may update
several options related to your keyboard (```setkmap=xx```). You may have a look
at ``ìsolinux.cfg``` that is on the CDRom, if you do not know the values you
can use for these options.
### Example for Grub2 bootmanager

Here is an example of Grub2 configuration. Create a new file such as
```/etc/grub.d/20_sysresccd``` so its configuration is located after your
default operating system configuration. The search directive is very important
as it must provide a way for grub to locate the filesystem which contains the
SystemRescueCd files. In the following example the filesystem is identified
using its label which is ```boot``` but you can also identify the filesystem
using its UUID if you prefer.
menuentry ‘SystemRescueCd’ { load_video insmod gzio insmod part_gpt insmod part_msdos insmod ext2 search –no-floppy –
label boot –set=root echo ‘Loading Linux kernel …’ linux /sysrcd/rescue64 docache echo ‘Loading initial ramdisk …’ initrd
/sysrcd/initram.igz }
You can then run a command such as grub-mkconfig which will produce the final grub
configuration from fragments located in ```/etc/grub.d/```.
## Second step: update the grub4dos bootmanager (if you install on Windows)
Now, you must update your bootmanager using grub4dos that is the grub port to
windows. This section describes how to install the grub4dos boot manager if you
installed the SystemRescueCd files on an NTFS partition running Windows. If you
are using a Linux partition, please read the previous section instead.
One of the most interesting things you can do with the sysresccd ntfs
installation is to troubleshoot windows when it has problems. This way you can
mount the windows partition with ntfs-3g and repair your windows (replace a
backup of the registry, ...). The only problem is you cannot mount the windows
disk read-write with ntfs-3g because it was already mounted read-only during the
boot process. The solution to this problem is to use the ```docache``` option at
boot time. When this option is enabled, sysresccd will cache its own files
(found on the ntfs disk) into memory during the boot process, and the ntfs disk
will be unmounted. So it allows you to mount it again with ntfs-3g. So you have
to add ```docache``` to the ```menu.lst``` boot options if you want to be able
to mount your windows disk with ntfs-3g after booting from the ntfs disk itself.
Installation is really straight forward. In this mini tutorial, I assume Windows

is installed on an NTFS disk (Disk-C) and that you copied the SystemRescueCd
main files into ```C:\sysrcd```
### install grub4dos

You must [download grub4dos](https://gna.org/projects/grub4dos/), extract the
zip file into a temporary directory, and copy ```grldr``` to ```C:\```. This
installation has been tested using the ```grldr``` file provided with
```grub4dos-0.4.3-2007-08-27.zip``` but it should work with any recent version.
### update the windows boot loader

#### update your boot.ini (if you are using Windows XP or older)
These instructions should work on Windows NT4/2000/2003/XP. Edit ```C:\boot.ini```
(with a text editor such as Notepad++, do not use Microsoft Word), and add a
line that boots the ```grldr``` at the bottom of that file. Below is an example
of a ```boot.ini``` file. Be careful: do not replace your ```boot.ini``` with
the version given there. It is very important that you keep the current lines as
they are in your ```boot.ini```. You must just add the last line to your ```boot.ini```.
[boot loader] timeout=4 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows” /noexecute=optin /fastdetect C:\grldr=“SystemRescueCd”
#### update your boot loader (if you are using Windows Vista/7/8/10)
Together with ```grldr``` you need to copy ```grldr.mbr``` (part of the archive)
to the root of the Windows boot partition. Then you need to type several commands
at a command prompt (run ```cmd.exe``` with an administrator user account).
In the command prompt window (```C:>``` is a dummy substitute for the cmd prompt)
do the following:
C:> bcdedit /create /d “SystemRescueCd [GRUB4DOS]” /application bootsector
You get in return the boot entry ```{id}``` - use it (copy/paste or type) in the following steps
C:> bcdedit /set {id} device boot C:> bcdedit /set {id} path \grldr.mbr C:> bcdedit /displayorder {id} /addlast
### create the ```C:\menu.lst``` file

You have to create a ```C:\menu.lst``` that is the ```grub4dos``` configuration
file. Here is an example:
THIS IS A SAMPLE MENU.LST FILE FOR SYSTEMRESCUECD

title SystemRescueCd from the NTFS disk root (hd0,0) kernel /sysrcd/rescuecd subdir=sysrcd setkmap=us docache initrd
/sysrcd/initram.igz
In ```menu.lst``` you will have to replace the ```setkmap``` with the code that
matches your keyboard configuration. In this example, files are located on the
NTFS partition that is the first partition of the first hard disk. Then the grub
device name is ```(hd0,0)```. It would be ```(hd1,0)``` for the first partition
of the 2nd hard-disk, ```(hd0,1)``` for the second partition of the first
hard-disk, ... You have to replace ```root (hd0,0)``` with the grub name of your
NTFS partition.
### check the SystemRescueCd files

Check that the SystemRescueCd files are correctly installed in ```C:\sysrcd```
### reboot
Just reboot and choose ```grldr```, then ```SystemRescueCd``` in the boot menus
displayed by the Windows boot loader.
## Booting the ISO image from the disk using Grub2

Grub2 provides a new feature to boot from an ISO image which is stored on the
hard disk. If you put a copy of ```systemrescuecd-x86-x.y.z.iso``` on a
filesystem that Grub2 can read then you can boot SystemRescueCd directly from
the ISO image stored on your hard drive. This is very convenient if you
frequently update SystemRescueCd and you want to boot it directly from Grub2.
This installation can be done either by following this documentation or by using

a package from Linux distributions on [ArchLinux](https://aur.archlinux.org/packages/systemrescuecd/)
or [Gentoo](https://packages.gentoo.org/packages/sys-boot/systemrescuecd-x86-grub)
Grub2 knows what an ISO image is and it will load the kernel image such as
rescue32 or rescue64 and the initramfs (initram.igz) from the ISO into memory.
It will then do its normal job and execute the kernel. The SystemRescueCd init
script must then be aware that its ```sysrcd.dat``` file is in an ISO and not
directly on the partition. For that reason, this ``ìsoloop=xxx``` boot option
is required so you must use it in your ```grub.cfg```.
This option specifies the path of the ISO image in the partition that grub
considers as its root partition. It is important to understand that the path of
the ISO image may be different from the path on your linux system. If you have a
separate boot partition mounted on ```/boot``` and if you copy this ISO image to
```/boot/sysrcd/systemrescuecd-x86-x.y.z.iso``` then the option has to be
``ìsoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso```. This is because the boot
partition is what Grub2 will consider as its root partition during the boot
process.
Here is an example of a Grub2 configuration section. Replace

```rescue64``` below with your kernel, when you chose a different kernel:
menuentry “SystemRescueCd (isoloop)” { search –no-floppy –label boot –set=root loopback loop /systemrescuecd-x86-x.y.z.iso
linux (loop)/isolinux/rescue64 isoloop=systemrescuecd-x86-x.y.z.iso initrd (loop)/isolinux/initram.igz } ```
What happens when Grub2 boots is that:
Grub2 reads the filesystem that it considers as its root partition (the filesystem labelled as boot)
Grub2 searches for a file called /systemrescuecd-x86-x.y.z.iso at the root of that partition
Grub2 loads both isolinux/rescue64 and isolinux/initram.igz from the ISO image
Grub2 executes the kernel image (rescue64)
The kernel boots, then it executes the /init script from the initramfs
The /init boot script will see that the isoloop=systemrescuecd-x86-x.y.z.iso option has been used
This script tries to find systemrescuecd-x86-x.y.z.iso on any partition and device
This script mounts the ISO image and reads the root filesystem image (sysrcd.dat) and boots normally.
Clonezilla
The Free and Open Source Software for Disk Imaging and Cloning
About
News
Clonezilla Live on Hard Drive
Screenshots
Live CD/USB In this doc we explain how to put clonezilla live in your harddrive which already has an OS installed.
Live Docs
Here we use grub boot loader as an example. You have to put the clonezilla live files in a FAT, ext2/3, reiserfs or any grub
Server Edition
Download supported partition.
CD/USB key vendors If you do not have such a partition, you can use gparted to resize your partition and create another partition to put clonezilla live.
DRBL-winroll
Here we assume you already have a FAT partition /dev/sda4 to put clonezilla live. This is how to do that:
Related LiveCD
Testimonials
Lecture Materials
1. Boot the OS in the harddrive, saying it's GNU/Linux.
Related Articles 2. Mount /dev/sda4 as /mnt, you can make it by: mount /dev/sda4 /mnt
Partners 3. Download clonezilla live zip file, and unzip all the files in /mnt, make sure you put all the files in /mnt, say, "GPL" is in /mnt/,
FAQ/Q&A
Forum
not in any subdir. You can make it by something like: "unzip clonezilla-live-*.zip -d /mnt" (Replace clonezilla-live-*.zip with the
Mailing Lists file name you just downloaded).
Developers 4. Change the dir name "live" under /mnt as another name, say "live-hd". You can make it by: "cd /mnt; mv live live-hd"
Contributors
Related links
5. If your grub is 2.x (grub-pc), e.g. on Debian Jessie or Ubuntu 16.04, edit /etc/grub.d/40_custom, make it like:
Local communities
================================================
Custom Search
menuentry "Clonezilla" {
set root=(hd0,4)
linux /live-hd/vmlinuz boot=live union=overlay username=user config components quiet noswap nolocales edd=on
nomodeset ocs_live_run=\"ocs-live-general\" ocs_live_extra_param=\"\" keyboard-layouts= ocs_live_batch=\"no\"
locales= vga=788 ip=frommedia nosplash live-media-path=/live-hd bootfrom=/dev/sda4 toram=filesystem.squashfs
initrd /live-hd/initrd.img
}
================================================
//NOTE//
In grub2, (hd0,4) means the first harddrive and the 4th partition. It's different from that in grub version 1. Then run
"update-grub2" to update your grub2 config. (Thanks to Louie Chen for providing this).
Remember to put back slash \ before " for the boot parameters in grub 2. Otherwise it won't shown in /proc/cmdline,
then some actions of Clonezilla won't work.
Besides, you can use only the Clonezilal live iso file in grub2 (Thanks to the patches files from grml). For example, put
clonezilla-live-2.4.2-32-i686-pae.iso in dir /home/isos/, then make the grub2 custom menu (/etc/grub.d/40_custom) like:
================================================
menuentry "Clonezilla live" {
set isofile="/home/isos/clonezilla-live-2.4.2-32-i686-pae.iso"
loopback loop $isofile
linux (loop)/live/vmlinuz boot=live union=overlay username=user config components quiet noswap nolocales edd=on
nomodeset ocs_live_run=\"ocs-live-general\" ocs_live_extra_param=\"\" keyboard-layouts= ocs_live_batch=\"no\"
locales= vga=788 ip=frommedia nosplash toram=filesystem.squashfs findiso=$isofile
initrd (loop)/live/initrd.img
}
================================================
Then run "update-grub2" to update your grub2 config.
6. If your grub is version 1.x, edit your grub config file /boot/grub/menu.lst, and append the following:
================================================
title Clonezilla live on harddrive
root (hd0,3)
kernel /live-hd/vmlinuz boot=live union=overlay username=user config components quiet noswap nolocales edd=on
nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts= ocs_live_batch="no" locales=
vga=788 ip=frommedia nosplash live-media-path=/live-hd bootfrom=/dev/sda4 toram=filesystem.squashfs
initrd /live-hd/initrd.img
boot
================================================
//NOTE// There is a length limit (256 characters, for example) on the boot parameters for grub 1. For more info, please
check this discussion.
//NOTE//:
1. Here we assign "live-media-path=/live-hd" since the files are not put in the default path (live). We force to use
"bootfrom=/dev/sda4" (files are on /dev/sda4) so that if there is another Clonezilla live on your CD drive (e.g. /dev/hdc), the
live initramfs wont's find the wrong files from your CD drvie. An extra param "toram=filesystem.squashfs" is added so that
later later you can mount /dev/sda4 as clonezilla image dir if you want. If you want live-initramfs to copy all the files in
/dev/sda4 to memory, you can use "toram" (not "toram=filesystem.squashfs") only. This is useful when you have some
customized files you need in /dev/sda4/.
2. Remember to check kernel and initrd file names and the parameters in syslinux/syslinux.cfg from the zip file, copy them to
here. It might be different from here, say vmlinuz path, username and hostname maybe different.
3. If you do not change the dir name from "live" to "live-hd" in the above, you might encounter a problem when you have a
version of Clonezilla live on harddrive and you want to boot your Clonezilla live CD or USB flash drive. There are some
discussions about this. Check:
https://sourceforge.net/tracker2/?func=detail&atid=671650&aid=2202156&group_id=115473
http://drbl.org/faq/fine-print.php?
path=./2_System/34_2_or_more_filesystem_squashfs.faq#34_2_or_more_filesystem_squashfs.faq
Features
Business
Explore
Marketplace
Pricing
Sign in or Sign up
livecd‐tools / livecd‐tools Watch 18 Star 83 Fork 65
Code Issues 11 Pull requests 2 Insights
livecd‐tools /
API
AUTHORS
COPYING
HACKING
Makefile
README
config/livecd‐fedora‐minimal.ks
config/livecd‐mageia‐minimal‐i586.ks
config/livecd‐mageia‐minimal‐x86_64.ks
docs/livecd‐creator.pod
docs/livecd‐iso‐to‐disk.pod
docs/mkbiarch.8
imgcreate/.gitignore
imgcreate/__init__.py
imgcreate/creator.py
imgcreate/debug.py
imgcreate/dnfinst.py
imgcreate/errors.py
imgcreate/fs.py
imgcreate/kickstart.py
imgcreate/live.py
imgcreate/util.py
tools/edit‐livecd
tools/editliveos
tools/livecd‐creator
tools/livecd‐iso‐to‐disk.sh
tools/livecd‐iso‐to‐pxeboot.sh
tools/liveimage‐mount
tools/mkbackup
tools/mkbiarch
© 2018 GitHub, Inc.

Terms
Privacy
Security
Status
Help
Contact GitHub
API
Training
Shop
Blog
About
Features
Business
Explore
Marketplace
Pricing
Sign in or Sign up
livecd‐tools /
API
AUTHORS
COPYING
HACKING
Makefile
README
config/livecd‐fedora‐minimal.ks
config/livecd‐mageia‐minimal‐i586.ks
config/livecd‐mageia‐minimal‐x86_64.ks
docs/livecd‐creator.pod
docs/livecd‐iso‐to‐disk.pod
docs/mkbiarch.8
imgcreate/.gitignore
imgcreate/__init__.py
imgcreate/creator.py
imgcreate/debug.py
imgcreate/dnfinst.py
imgcreate/errors.py
imgcreate/fs.py
imgcreate/kickstart.py
imgcreate/live.py
imgcreate/util.py
tools/edit‐livecd
tools/editliveos
tools/livecd‐creator
tools/livecd‐iso‐to‐disk.sh
tools/livecd‐iso‐to‐pxeboot.sh
tools/liveimage‐mount
tools/mkbackup
tools/mkbiarch

Terms
Privacy
Security
Status
Help
Contact GitHub
API
Training
Shop
Blog
About
Log in
Page Discussion Read View source View history Search PCLinuxOSHelp Knowle
LiveCD, Create your own

To create your own LiveCD you can use mylivecd this makes an exact copy of your system at any point in time and makes it into an
installable LiveCD ISO. From there K3B or your favorite burning program should be able to burn the ISO onto a CD/DVD. Mylivecd should
Main page
Recent changes already be installed on your system, accessed through the system start menu or the terminal. Mylivecd will create a clone of your installation,
Random page which, when burned to a DVD, will be bootable and installable on the original machine, or another computer. You may exclude specific files or
Help directories (/home, data, music, etc.) You may wish to run mylivecd before updating with Synaptic in case you run into problems. With /home
on a separate partition, you can reinstall and keep all your settings and desktop tweaks. Your /data partition remains untouched provided
Tools
that you only format the / (root) partition during reinstall.
What links here
Related changes To access your newly created iso backup, you will need to be in 'Super User" mode: PC > System > File Tools > File Manager-Super User
Special pages Mode.
Printable version
Tip - if you are using it to install on another PC, use the option "Run Hardrake at Boot", to detect any "different hardware” (also works if you
Permanent link
Page information install on machine A, and put the HDD in machine B).
More on forum, section "LiveCD, MyliveCD, LiveUSB and Remastering "
Category: HowTo
This page was last edited on 17 April 2018, at 00:22.
Content is available under Creative Commons Attribution-NonCommercial-ShareAlike unless otherwise noted.
Privacy policy About PCLinuxOSHelp Knowledge Base Disclaimers

PuppyLinux : ComponentHowTo
Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register :: Search:
cn::de::es::fr::gr::hr::it::ja::kr::nl::pl::pt::ru::se::us::vn::
HomePage > Components and HowTos
Component and HowTo Index

This Page contains information and 'how-to' guides about the different components of Puppy Linux,
(for information about Wiki see Wiki Index).
Installing Puppy OS
What is Puppy?
Components
Which Puppy?
Architecture - processor and motherboard type
Installation
FirstRun - Program run on first run
Booting (Start up)
File Manager
Configure
Files Types
Fonts
RaspberryPi and ARM Resources
Graphic User Interface - window managers etc.
PARM Puppy on ARM
Input Devices - mouse/keyboard etc.
Language Support
Using programs
Linux Directory Structure
Installing Software
Memory and Storage
How To Multimedia
Networking
RightClick
Printers and Scanners
Repositories
OS and Software
Security
How to find the Puppy Version
Sound system
How to find the Puppy State
Video Driver
How to fine tune Web browser
How to Uninstall software
Filesystem
Uninstalling
How to repair disk partitions
Internet Tools
Partitioning
Microsoft Windows User How To (Win XP)
Save File - part of the filesystem (Frugal install)
AUFS - utility that creates RootFs (Frugal install)
Hardware
Files Types
Detect Devices
Compatible USB Devices
Tutorials
USB2 and slower media
PuppySchool
USB3 Support
Tutorial Videos
Psync - set time via internet
Advanced
Laptops
Command Line - Command line and terminal info
Configuring Puppy on Laptops
Compiling
Puppy on Asus Eee Pc
Databases
EeePc Setup
Dependency
Kernel
Power
Programming
Battery Monitoring
Woof - build your own version of Puppy
Extend Laptop Battery Life
Virtualization
Suspend Puppy
CPU scaling mod
Also on the Wiki

Bug Trackers - record of OS and Software bugs
Display information about your Puppy Version
Tutorial Videos
Better Search
FAQ - Frequently Asked Questions
How Puppy Works
Organizations about the projects and foundations involved with open source
NoobHelp
Related Pages
Common Commands Reference Card
Index of resources for Beginners Help forum
Bruce B Puppy Links page
How to un/install a Pet file from the command line thread
Script to control laptops backlight settings
Which part of file system to store user's stuff? thread
Basic Linux Filesystems tutorial : ext2,ext3,ext4,JFS & XFS (nextstep4it)
Categories
CategoryTutorial
CategoryComponent
CategoryIndex
There are no comments on this page. New Comment
[Source] [History] 2018-03-16 16:36:04 Owner: darkcity Your hostname is 85.251.16.207.dyn.user.ono.com

Valid XHTML :: Valid CSS: :: Powered by WikkaWiki
Log in
Live CD faq
Contents [hide]
Main page 1 Using the LiveCD FAQ's
Recent changes 1.1 First Steps
Random page
1.2 My CD is in my drive, but when I turn my computer on, nothing different happens
Help
1.3 PCLinuxOS tries to start, but something strange happens
Tools 1.4 Check your CD
1.5 Try some LiveCD boot options
What links here
Related changes
2 Some More Specific Possible problems =
Special pages 2.1 When I boot PCLinuxOS the cd hangs when probing usb
Printable version 2.2 When I booted PCLinuxOS all I got was a black screen with a prompt?
Permanent link 2.3 After booting all I see is a black screen saying "login:"
Page information 2.4 I logged in but all I see is "[root@localhost root]#"
2.5 Why does live CD hang at starting non-interactive mode and nothing else happens?
2.6 Why does my computer freeze when trying to boot the live CD?
2.7 I'm not setup on broadband, how do I stop the livecd from trying to bring up eth0?
2.8 I've setup my USB key but when I log in as guest it doesn't have my previous settings?
2.9 Where is the installer and the usbkey setup routine?
2.10 How do I set up my desktop to see my other drives and partitions?
2.11 What is the password for root and guest users?
2.12 What does PCLinuxOS do to my Windows?
2.13 What happens with the documents I create with PCLinuxOS?
2.14 How is it possible I can make changes to the files on the CD?
2.15 Why bother installing PCLinuxOS if it works perfectly fine from CD?
2.16 If I take my CD and my USB key, I can work on my files everywhere?
3 I have a problem not listed here
Using the LiveCD FAQ's

Once you have a live CD, you can boot from it (you may need to change BIOS settings to allow your PC to boot from the CD drive rather than
the hard disk).
First Steps
It is absolutely essential that you:
Check your requirements

Check your hardware
Once that's out of the way, read through the contents below for your particular issue:
My CD is in my drive, but when I turn my computer on, nothing different happens
If your computer seems to be ignoring your CD, and not booting up into PCLinuxOS, then there could be a few reasons. Try each of these
steps in order:
1. Is the CD properly inserted? Remove it, think happy thoughts, and then re-insert it. Then try booting up again.
1. Check your BIOS settings
PCLinuxOS tries to start, but something strange happens
If your computer hangs or gives error messages as it tries to start from the PCLinuxOS LiveCD, then there could be a few things wrong. Try
each of these steps in order:
Check your CD
For people who download an ISO and burnt it themselves:
Downloading has instructions on checking your ISO before burning it.

When you burn the ISO your software should have been used to verify the disk after burning.
People who bought their CD usually don't have a problem with their disk, but if you are having strange problems then the disk itself could be
bad so it's a good idea to check it.
You can still check a CD after it's been burned.
Try some LiveCD boot options
In most situations you will not have to use the boot options. Put in the CD, restart your computer and just press Enter when it prompts for
input. There are a few situations however where you might want the live CD to start differently. In those situations you can change how the
live CD starts by using the boot options. There are several different options that can be given to the live CD to change how it handles the
boot process and the hardware detection.
Cheat codes
Some More Specific Possible problems =

When I boot PCLinuxOS the cd hangs when probing usb
You might be able to get past this by typing "livecd nousb" at the boot prompt.
When I booted PCLinuxOS all I got was a black screen with a prompt?
The hardware detection (hwdetect) could not determine the correct video driver for your video card. You might be able to boot by typing
"livecd xdrv=fbdev", without the quotes, at the boot prompt. fbdev is a generic driver that should work with most video cards.
When the live CD fails to detect your video driver you will probably see a message on how to proceed. This implies logging in as root
(password: root) and starting video configuration by typing: "video", without the quotes. When you are done with configuring your video, start
X by typing either "kdm" (for the graphical login) or "startx" to start KDE as root-user. Don't forget to log out the root when you start KDM!
After booting all I see is a black screen saying "login:"
See point above.
I logged in but all I see is "[root@localhost root]#"
See point above.
Why does live CD hang at starting non-interactive mode and nothing else happens?
This usually indicates a bad cd burn. Try another brand of CDR or burn the CD at a lower speed. I have had very good success at 16x speed
Can I install software while running the live CD?
On recent live CDs you can install software from our repository. Once you restart your computer however, installed software is gone
again. Also, you have to be running the unionfs functionality which in recent live cd versions is turned on by default. Interested in how
unionfs works?
With the changes= boot option you can make changes to the live CD persistent. Not only the home folder, but any file modified during
your live CD session. The changes can be saved to any partition (block device), except NTFS filesystems from Windows NT/XP/Vista.
Once you've installed PCLinuxOS on your harddisk, installed software is kept between restarts.
Why does my computer freeze when trying to boot the live CD?
Some motherboards require additional kernel options passed at the boot prompt. You may be able to boot by typing "livecd noapic nolapic
acpi=off" at the boot prompt.
I'm not setup on broadband, how do I stop the livecd from trying to bring up eth0?
Type "livecd nonetwork" at the boot prompt.
I've setup my USB key but when I log in as guest it doesn't have my previous settings?
When booting the LiveCD type "livecd home=usb" to let the LiveCD know you have a key plugged in. Continue reading the Saving your work
page for more information.
Where is the installer and the usbkey setup routine?
Log in as guest, not as root, and click the icons on the desktop.
How do I set up my desktop to see my other drives and partitions?
Type "livecd fstab=auto,rw" at the boot prompt
What is the password for root and guest users?
The password for root is root, and the password for guest is guest.
What does PCLinuxOS do to my Windows?
The live CD doesn't write to your hard disk or makes any changes to Windows. In fact, once you reboot your computer after using the live
CD, everything will be exactly as before starting the live CD.
What happens with the documents I create with PCLinuxOS?
The live CD doesn't write to harddisk. You can make it do that, but by default this doesn't happen. You might have noticed that when you
restart your computer, it returns completely to its original state and all documents you've written, bookmarks you've created, email you
downloaded, are gone. You can very easily (just plug it into your computer) use your USB key to store your files, and even your settings.
When you plug in your USB key, an icon will appear on the desktop. You can use this icon to access your USB key.
How is it possible I can make changes to the files on the CD?
As we all know, it's not that easy to make changes to files on a CD. So how come you can change files and install software when you are
running the entire content from a CD? If you burn the PCLinuxOS to a CD-R, you can't rewrite files but you can install software and edit files
while running the CD. Pure magic? Yes. Interested in how it works?
Why bother installing PCLinuxOS if it works perfectly fine from CD?
Starting the operating system and loading programs is quite a bit faster when you install it to your hard drive. Software available to
PCLinuxOS users is being constantly improved and updated. While the programs on the live cd are perfectly acceptable for use, you can
install new software easily when you've installed PCLinuxOS to your hard drive. Installing to the hard drive is truly advantageous, as some of
the software updates really are amazing. Our resident expert in disk partitioning and installation will give you easy to understand instructions
on how to do so.
If I take my CD and my USB key, I can work on my files everywhere?
We get this question a lot. ;) Yes, if you take the PCLinuxOS Live CD and your USB key with you, you can have a personalized working
environment and your files on most PCs you come across.
I have a problem not listed here
We're really sorry to hear that.
Have you been careful about trying all the ideas on this page?
Have already checked that you meet the minimum system Recommendations?
Have you checked that your hardware is not on the known hardware issues list?
Things to try:
Pause, and meditate on your hardware. Is any of it really cool and new? This might be a problem if the manufacturer hasn't shared their
technical documentation or drivers.
Check out the PCLinuxOS Hardware Database and look for your hardware.
Search through the forums .
Get on IRC - semi-live help, sometimes.
Things to avoid:
Do not write a note anywhere on this wiki asking for help. This is for documentation, not troubleshooting.
Don't pester your local computer-guru or Linux User Group until you've tried helping yourself and then asking the PCLinuxOS community
for help.
Post on another Linux forum asking for help. The best place to get PCLinuxOS help is from the PCLinuxOS community Forums .
Category: General

Log in
Live CD faq
Contents [hide]
Random page
Help
What links here
Related changes

the hard disk).
First Steps

Check your hardware
steps in order:
Check your CD

Cheat codes

See point above.
See point above.
unionfs works?
on how to do so.
Things to try:
Things to avoid:
for help.
Category: General

Log in
Live CD faq
Contents [hide]
Random page
Help
What links here
Related changes

the hard disk).
First Steps

Check your hardware
steps in order:
Check your CD

Cheat codes

See point above.
See point above.
unionfs works?
on how to do so.
Things to try:
Things to avoid:
for help.
Category: General

PuppyLinux : ComponentHowTo
Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register :: Search:
cn::de::es::fr::gr::hr::it::ja::kr::nl::pl::pt::ru::se::us::vn::
HomePage > Components and HowTos
Component and HowTo Index

This Page contains information and 'how-to' guides about the different components of Puppy Linux,
(for information about Wiki see Wiki Index).
Installing Puppy OS
What is Puppy?
Components
Which Puppy?
Architecture - processor and motherboard type
Installation
FirstRun - Program run on first run
Booting (Start up)
File Manager
Configure
Files Types
Fonts
RaspberryPi and ARM Resources
Graphic User Interface - window managers etc.
PARM Puppy on ARM
Input Devices - mouse/keyboard etc.
Language Support
Using programs
Linux Directory Structure
Installing Software
Memory and Storage
How To Multimedia
Networking
RightClick
Printers and Scanners
Repositories
OS and Software
Security
How to find the Puppy Version
Sound system
How to find the Puppy State
Video Driver
How to fine tune Web browser
How to Uninstall software
Filesystem
Uninstalling
How to repair disk partitions
Internet Tools
Partitioning
Microsoft Windows User How To (Win XP)
Save File - part of the filesystem (Frugal install)
AUFS - utility that creates RootFs (Frugal install)
Hardware
Files Types
Detect Devices
Compatible USB Devices
Tutorials
USB2 and slower media
PuppySchool
USB3 Support
Tutorial Videos
Psync - set time via internet
Advanced
Laptops
Command Line - Command line and terminal info
Configuring Puppy on Laptops
Compiling
Puppy on Asus Eee Pc
Databases
EeePc Setup
Dependency
Kernel
Power
Programming
Battery Monitoring
Woof - build your own version of Puppy
Extend Laptop Battery Life
Virtualization
Suspend Puppy
CPU scaling mod
Also on the Wiki

Bug Trackers - record of OS and Software bugs
Display information about your Puppy Version
Tutorial Videos
Better Search
FAQ - Frequently Asked Questions
How Puppy Works
Organizations about the projects and foundations involved with open source
NoobHelp
Related Pages
Common Commands Reference Card
Index of resources for Beginners Help forum
Bruce B Puppy Links page
How to un/install a Pet file from the command line thread
Script to control laptops backlight settings
Which part of file system to store user's stuff? thread
Basic Linux Filesystems tutorial : ext2,ext3,ext4,JFS & XFS (nextstep4it)
Categories
CategoryTutorial
CategoryComponent
CategoryIndex
There are no comments on this page. New Comment
[Source] [History] 2018-03-16 16:36:04 Owner: darkcity Your hostname is 85.251.16.207.dyn.user.ono.com

Valid XHTML :: Valid CSS: :: Powered by WikkaWiki
Descargar Fedora 28 Workstation
Descargar
ISO para Linux de 64 bits (1.7 GB).
Sólo necesita una descarga para instalaciones nuevas. Siga estas instrucciones si lo
que quiere es actualizar.
¿Necesita instrucciones o una versión diferente?
Ejecución de Fedora Workstation Otras Descargas

Para ejecutar Fedora Workstation necesita: Imagen viva de 64 bits 1.7GB
Fedora Media Writer (arriba encontrará el enlace para la descarga) Imagen Viva de 32 bits 1.6GB
Un dispositivo USB con al menos 1.7 GB de espacio disponible
Imágenes de instalación por
Fedora Workstation se distribuye mediante Fedora Media Writer. Descargue el programa red:
para su plataforma y siga los pasos que se le indiquen para generar una versión viva (vea
Imagen de 64 bits 583MB
'¿Qué significa imagen "Viva"?' en las notas a la derecha) de Fedora Workstation en una
unidad USB. Después podrá ejecutar esa versión de Fedora Workstation desde el USB. Imagen de 32 bits 536MB
De forma opcional puede instalar Fedora Workstation en un equipo con al menos

procesador de 1 GHz, 1 GB de RAM, y 10 GB de espacio disponible. Para ello ejecute en ese
equipo la versión viva de Fedora Workstation desde el dispositivo USB, abra la aplicación
Fedora Media Writer y siga las instrucciones que aparecerán en pantalla para completar la PRUEBE ATOMIC
instalación. WORKSTATION
Atomic proporciona una
Plataformas admitidas imagen inmutable del SO y
actualizaciones mediante
Fedora Media Writer funciona en las siguientes plataformas:
OSTree.
Mac OS X
 Imagen Atomic de 64
Windows
bits 1.9GB
Linux
 Más información
Parece que está usando Linux, por lo que le proporcionamos la descarga correspondiente.
Si ese no es su sistema operativo o quiere obtener una versión para otro sistema, pulse el
botón "Ver todas las descargas".
Recursos de apoyo
Ver todas las descargas
 Anuncio de lanzamiento
Lea el anuncio de
Otras formas de obtener un medio de instalación lanzamiento en la revista
Fedora.
Puede comprar medios de instalación de Fedora de vendedores en línea o algún vendedor
local en su área.
 Notas de lanzamiento
¿No puede permitirse el precio de un medio de instalación? Solicite un medio de
Conozca los cambios desde la
instalación de Fedora desde el Programa de Medios Gratuitos de Fedora.
versión anterior, así como los
requisitos mínimos y las
recomendaciones para el uso
Al continuar y descargar Fedora se compromete a cumplir los siguientes términos y
de Fedora.
condiciones.
By downloading Fedora software, you acknowledge that you understand all of the following:  Guía de instalación
Fedora software and technical information may be subject to the U.S. Export Administration
Le recomendamos que la
Regulations (the “EAR”) and other U.S. and foreign laws and may not... Leer más >
eche un vistazo antes de
instalar el sistema, pues en
ella se responde a algunas de
las preguntas más
frecuentes.
 Problemas comunes
Una excelente lista de

consulta si se encuentra con
algún problema en la
instalación o uso de Fedora.
¿Qué significa imagen

"Viva"?
Fedora Media Writer creará un

sistema Fedora Workstation
completo, que podrá ejecutar
directamente desde su
dispositivo USB. Puede usar la
imagen viva para probar
Fedora sin necesidad de
realizar cambios en su disco
duro.
Cuando esté seguro de que es

lo que quiere, puede instalar
Fedora a su disco duro desde
la versión viva de Fedora
Workstation.
Más Fedora
Ediciones de Fedora
Fedora Labs
Tecnología ARM®
ACERCA DE DESCARGAR ASISTENCIA UNIRSE
Acerca de Fedora Fedora Workstation Obtener ayuda Únase al Proyecto Fedora

Patrocinadores Fedora Server Ask Fedora Planeta Fedora
Revista de Fedora Fedora Atomic Errores comunes Grupos de interés especial (SIG)
Legal Ediciones de Fedora Portal Fedora para desarrolladores Sistema de Cuentas de Fedora
Código de conducta de Fedora Fedora Labs Guía de instalación Comunidad Fedora
Fedora ARM®
   Descargas alternativas
Fedora está patrocinado por Red Hat.
Conozca más sobre la relación entre Red Hat y Fedora »

Cambiar idioma
© 2017 Red Hat, Inc. y otros. Envíe cualquier comentario o corrección al equipo de
websites.
Descargar Fedora 28 Workstation
Descargar
ISO para Linux de 64 bits (1.7 GB).
Sólo necesita una descarga para instalaciones nuevas. Siga estas instrucciones si lo
que quiere es actualizar.
¿Necesita instrucciones o una versión diferente?
Ejecución de Fedora Workstation Otras Descargas

Para ejecutar Fedora Workstation necesita: Imagen viva de 64 bits 1.7GB
Fedora Media Writer (arriba encontrará el enlace para la descarga) Imagen Viva de 32 bits 1.6GB
Un dispositivo USB con al menos 1.7 GB de espacio disponible
Imágenes de instalación por
Fedora Workstation se distribuye mediante Fedora Media Writer. Descargue el programa red:
para su plataforma y siga los pasos que se le indiquen para generar una versión viva (vea
Imagen de 64 bits 583MB
'¿Qué significa imagen "Viva"?' en las notas a la derecha) de Fedora Workstation en una
unidad USB. Después podrá ejecutar esa versión de Fedora Workstation desde el USB. Imagen de 32 bits 536MB
De forma opcional puede instalar Fedora Workstation en un equipo con al menos

procesador de 1 GHz, 1 GB de RAM, y 10 GB de espacio disponible. Para ello ejecute en ese
equipo la versión viva de Fedora Workstation desde el dispositivo USB, abra la aplicación
Fedora Media Writer y siga las instrucciones que aparecerán en pantalla para completar la PRUEBE ATOMIC
instalación. WORKSTATION
Atomic proporciona una
Plataformas admitidas imagen inmutable del SO y
actualizaciones mediante
Fedora Media Writer funciona en las siguientes plataformas:
OSTree.
Mac OS X
 Imagen Atomic de 64
Windows
bits 1.9GB
Linux
 Más información
Parece que está usando Linux, por lo que le proporcionamos la descarga correspondiente.
Si ese no es su sistema operativo o quiere obtener una versión para otro sistema, pulse el
botón "Ver todas las descargas".
Recursos de apoyo
Ver todas las descargas
 Anuncio de lanzamiento
Lea el anuncio de
Otras formas de obtener un medio de instalación lanzamiento en la revista
Fedora.
Puede comprar medios de instalación de Fedora de vendedores en línea o algún vendedor
local en su área.
 Notas de lanzamiento
¿No puede permitirse el precio de un medio de instalación? Solicite un medio de
Conozca los cambios desde la
instalación de Fedora desde el Programa de Medios Gratuitos de Fedora.
versión anterior, así como los
requisitos mínimos y las
recomendaciones para el uso
Al continuar y descargar Fedora se compromete a cumplir los siguientes términos y
de Fedora.
condiciones.
By downloading Fedora software, you acknowledge that you understand all of the following:  Guía de instalación
Fedora software and technical information may be subject to the U.S. Export Administration
Le recomendamos que la
Regulations (the “EAR”) and other U.S. and foreign laws and may not... Leer más >
eche un vistazo antes de
instalar el sistema, pues en
ella se responde a algunas de
las preguntas más
frecuentes.
 Problemas comunes
Una excelente lista de

consulta si se encuentra con
algún problema en la
instalación o uso de Fedora.
¿Qué significa imagen

"Viva"?
Fedora Media Writer creará un

sistema Fedora Workstation
completo, que podrá ejecutar
directamente desde su
dispositivo USB. Puede usar la
imagen viva para probar
Fedora sin necesidad de
realizar cambios en su disco
duro.
Cuando esté seguro de que es

lo que quiere, puede instalar
Fedora a su disco duro desde
la versión viva de Fedora
Workstation.
Más Fedora
Ediciones de Fedora
Fedora Labs
Tecnología ARM®
ACERCA DE DESCARGAR ASISTENCIA UNIRSE
Acerca de Fedora Fedora Workstation Obtener ayuda Únase al Proyecto Fedora

Patrocinadores Fedora Server Ask Fedora Planeta Fedora
Revista de Fedora Fedora Atomic Errores comunes Grupos de interés especial (SIG)
Legal Ediciones de Fedora Portal Fedora para desarrolladores Sistema de Cuentas de Fedora
Código de conducta de Fedora Fedora Labs Guía de instalación Comunidad Fedora
Fedora ARM®
   Descargas alternativas
Fedora está patrocinado por Red Hat.
Conozca más sobre la relación entre Red Hat y Fedora »

Cambiar idioma
© 2017 Red Hat, Inc. y otros. Envíe cualquier comentario o corrección al equipo de
websites.
Features
Business
Explore
Marketplace
Pricing
Sign in or Sign up
Dismiss
Join GitHub today
GitHub is home to over 28 million developers working together to host and
review code, manage projects, and build software together.
Sign up
mas t er livecd‐tools / docs / livecd‐creator.pod Find file Copy path
zhangxianwei8 Update livecd‐creator manpage with info about imcomplete options 03a9476 on 6 Jan
4 contributors
162 lines (88 sloc) 3.9 KB Raw Blame History
NAME
livecd‐creator ‐ creates live CD or DVD images.
SYNOPSIS
livecd‐creator [OPTIONS]
DESCRIPTION
livecd‐creator creates live CD or DVD images﴾ISO images﴿ from kickstart files. Kickstart files contain information about
packages and configuration settings which are used to build the image.
OPTIONS
‐h, ‐‐help
Shows the help message and exits.
IMAGE OPTIONS
These options define the created image.
‐c KSCFG, ‐‐config=KSCFG
Path to kickstart configuration file.
‐b BASE_ON, ‐‐base‐on=BASE_ON
Add packages to an existing live CD iso9660 image.
‐f FS_LABEL, ‐‐fslabel=FS_LABEL
Defines the file system label. The default is based on the configuration name.
‐‐title=TITLE
Title used by syslinux.cfg file
‐‐product=PRODUCT
Product name used in syslinux.cfg boot stanzas and countdown
‐p, ‐‐plugins
Use DNF plugins during image creation
‐‐compression‐type=COMPRESSOR
Specify a compressor recognized by mksquashfs. xz is the default and works with 2.6.38 and later kernels. gzip works with
all kernels. lzo works with 2.6.36 and later kernels. lzma will only work with custom kernels. Set to 'None' to force reading
the compressor used in BASE_ON. If gzip is used, the ‐comp option is not passed to mksquashfs to allow the use of older
versions of mksquashfs.
‐‐releasever=VER
Set the value to substitute for $releasever in kickstart repo urls
SYSTEM DIRECTORY OPTIONS

These options define directories used on your system for creating the live image.
‐t TMPDIR, ‐‐tmpdir=TMPDIR
defines the temporary directory to use. The default directory is /var/tmp.
‐‐cache=CACHEDIR
Defines the cache directory to use ﴾default: private cache﴿.
‐‐cacheonly
Work offline from cache, use together with ‐‐cache ﴾default: False﴿
‐‐nocleanup
Skip cleanup of temporary files
DEBUGGING OPTIONS
These options control the output of logging information during image creation
‐d, ‐‐debug
Output debugging information
‐v, ‐‐verbose
Output verbose progress information
‐q, ‐‐quiet
Supress stdout
‐‐logfile=FILE
Save debug information to FILE
EXAMPLES
Barebones LiveCD
livecd‐creator \ ‐‐config=/usr/share/livecd‐tools/livecd‐fedora‐minimal.ks
Fedora Desktop Live CD

livecd‐creator \ ‐‐config=/usr/share/livecd‐tools/livecd‐fedora‐desktop.ks \ ‐‐fslabel=Fedora9‐LiveCD‐foo
REPO EXTENSIONS
livecd‐creator provides for some extensions to the repo commands similar to what DNF supports. The strings $arch, $basearch
and $releasever are replaced with the system arch, basearch and release version respectively. When no ‐‐releasever is passed it
defaults to the current system's version. The allows the use of repo commands such as the following:
repo ‐‐name=fedora ‐‐mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora‐$releasever&arch=$basearch
Note that in a chroot environment ﴾like koji﴿ the rpmdb is not available, so either don't use $releasever in that case, or pass ‐‐
releasever=VER
CONTRIBUTORS
David Zeuthen, Jeremy Katz, Douglas McClendon and a team of many other contributors. See the AUTHORS file in the source
distribution for the complete list of credits.
BUGS
Report bugs to the mailing list http://www.redhat.com/mailman/listinfo/fedora‐livecd‐list or directly to Bugzilla
http://bugzilla.redhat.com/bugzilla/ against the Fedora product, and the livecd‐tools component.
COPYRIGHT
Copyright ﴾C﴿ Fedora Project 2008,2009, and various contributors. This is free software. You may redistribute copies of it under
the terms of the GNU General Public License http://www.gnu.org/licenses/gpl.html . There is NO WARRANTY, to the extent
permitted by law.
SEE ALSO
livecd‐iso‐to‐disk(1) , project website http://fedoraproject.org/wiki/FedoraLiveCD

Terms
Privacy
Security
Status
Help
Contact GitHub
API
Training
Shop
Blog
About
grml2usb(8)
Table of Contents
1. Name
2. Synopsis
3. Introduction
4. Options
5. Developers Corner
5.1. Directory layout on usb device
5.2. Grabbing the source
5.3. Developers Debugging Hints
5.4. Performance tracing
6. Troubleshooting and Pitfalls when booting
7. Frequently Asked Questions (FAQ)
7.1. Where can I get grml2usb?
7.2. Why can’t I just dd the ISO to a USB device?
7.3. What’s the difference between grml2usb and just using dd?
7.4. What’s grml2iso?
7.5. Why is there a menu.lst and a grub.cfg inside /boot/grub/?
7.6. grub-install fails with 'The file ../boot/grub/stage1 not read correctly"?!
7.7. grub-install complains about /sbin/grub-install and/or xfs_freeze?!
7.8. grub-install complains about /boot/grub/device.map?!
7.9. grub-install complains about a unary operator?!
7.10. grub-install fails with grub-probe: error: unknown filesystem?!
7.11. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!
7.12. I’m getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?
7.13. Why do I have to use a FAT16/FAT32 filesystem?
7.14. Addons → Hardware Detection Tool freezes
7.15. I think I’ve got a really cool idea!
7.16. I’ve problems with booting from USB.
7.17. I’ve found a bug!
8. Usage examples
9. Online Ressources
10. Bugs
11. Author
1. Name
grml2usb - install Grml ISO(s) on usb device for booting
2. Synopsis
grml2usb [ options ] <ISO[s]> <device>
Important! The Grml team does not take responsibility for loss of any data!
3. Introduction
grml2usb installs Grml on a given partition of your usb device and makes it bootable. It provides multiboot ISO support, meaning you
can specify several Grml ISOs on the command line at once and select the Grml flavour you would like to boot on the bootprompt then.
Note that the first ISO specified on the grml2usb command line will become the default one (that’s the one that will boot when just
pressing enter on the bootprompt or wait until the boot timeout matches).
By default a compatible master boot record (MBR) is installed on the device (being for example /dev/sdX when
executing grml2usb grml.iso /dev/sdX1) and syslinux is being used as default bootloader. Avoid installation of
the default MBR using the --skip-mbr option or if you encounter any problems with the default MBR consider
using --syslinux-mbr instead.
4. Options
ISO[s] should be the path to one or multiple grml-ISOs and/or the path to the currently running live-system (being
/lib/live/mount/medium).
The device either might be a device name like /dev/sdX1 or a directory. When specifying a device name the device is mounted
automatically. When specifying a directory grml2usb is assuming that you did set up a bootloader on your own (or don’t need one) and a
bootloader won’t be installed automatically.
The following options are supported:
--bootoptions=…
Use specified bootoptions as default. To use flavour name as a argument for a boot parameter use %flavour which will be expanded
to the flavour name. To add multiple bootoptions you can specify the option multiple time.
--bootloader-only
Do not copy files but instead just install a bootloader. Note that the boot addons are copied to /boot/addons at this stage as well. If
you want to skip copying the boot addons consider using the --skip-addons option.
--copy-only
Copy files only but do not install a bootloader.
--dry-run
Avoid executing commands, instead show what would be executed. Warning: please notice that the ISO has to be mounted
anyway, otherwise identifying the Grml flavour would not be possible.
--fat16
Format specified partition with FAT16. Important: this will destroy any existing data on the specified partition!
--force
Force any (possible dangerous) actions requiring manual interaction (like --fat16).
--grub
Install grub bootloader instead of (default) syslinux.
--grub-mbr
Install grub into MBR (Master Boot Record) instead of PBR (Partition Boot Record). Check out the mbr-vs-pbr section in the FAQ
of this document for further details.
--help
Display usage information and exit.
--mbr-menu
Install master boot record (MBR) with integrated boot menu: interactively choose the partition to boot from, with a timeout to load
the default partition, or boot from floppy. When NOT using the --mbr-menu option a MBR with LBA and large disc support but
without an integrated boot menu is installed (so it’s not visible at all but instead directly jumps to the bootloader - being grub or
syslinux). Note: This options is available only when using the default MBR and won’t have any effect if you’re using the --syslinux-
mbr option.
--quiet
Do not output anything but just errors on console.
--skip-addons
Do not install /boot/addons/ files (like dos, grub, memdisk,…).
--remove-bootoption=…
Remove specified bootoption (could be a regex) from existing boot options. Use multiple entries for removing different bootoptions
at once.
--skip-bootflag
Do not check for presence of bootflag on target device.
--skip-grub-config
Skip generation of grub configuration files. By default the configuration files for syslinux and grub will be written so you’ve a
working configuration file no matter whether you’re using grub or syslinux as bootloader.
--skip-mbr
Do not touch/install the master boot record (MBR).
--skip-syslinux-config
Skip generation of syslinux configuration files. By default the configuration files for syslinux and grub will be written so you’ve a
working configuration file no matter whether you’re using grub or syslinux as bootloader.
--skip-usb-check
Skip check to verify whether given device is a removable device. Some USB devices are known to report wrong information, when
using such a device you can skip grml2usb’s removable device check.
--syslinux
This option is deprecated and is being left only for backwards compatibility reasons. Syslinux is the default bootloader of grml2usb
and therefore the --syslinux option doesn’t have any effects. If you do not want to use syslinux as bootloader consider using the - -
grub option.
--syslinux-mbr
Install syslinux' master boot record (MBR, which is booting from the partition with the "active" flag set) instead of the default one.
If you encounter any problems with the default MBR you can try using the syslinux MBR instead. If that works for you please let
us know so we can adjust our default MBR accordingly.
-v, --version
Return version and exit.
--verbose
Enable verbose mode.
5. Developers Corner
5.1. Directory layout on usb device

boot/ ->
|-- addons/
| |-- allinone.img [grub - all in one image]
| |-- bsd4grml/ [MirBSD]
| |-- balder10.imz [FreeDOS]
| |-- memdisk [chainloading helper]
| |-- memtest [memtest86+]
|-- release/
| |-- grml/
| | |-- linux26 [Kernel]
| | |-- initrd.gz [initramfs]
| |-- grml64
| | |-- linux26 [Kernel]
| | |-- initrd.gz [initramfs]
| |-- grml-medium
| | |-- linux26 [...]
| | |-- initrd.gz
| |-- grml64-medium
| | |-- linux26
| | |-- initrd.gz
| |-- grml-small
| | |-- linux26
| | |-- initrd.gz
| `-- grml64-small
| |-- linux26
| |-- initrd.gz
|-- grub/
| |-- grml.png [graphical bootsplash background image for grub2]
| |-- grub.cfg [configuration file for grub2]
| |-- menu.lst [configuration file for grub1]
| |-- splash.xpm.gz [splash screen for grub1]
`-- syslinux/
|-- grml.png [graphical bootsplash background image for syslinux]
|-- syslinux.cfg [main configuration file for syslinux]
`-- [....] [several further config files for syslinux]
grml/
|-- grml2usb.txt [not yet implemented]
|-- grml-cheatcodes.txt [list of bootoptions for Grml]
|-- grml-version.txt [file containing information about grml-version]
|-- LICENSE.txt [license information]
|-- md5sums [md5sums of original ISO]
|-- README.txt [informational text]
`-- web/ [browser related files]
|-- index.html
|-- style.css
`-- images/
|-- button.png
|-- favicon.png
|-- linux.jpg
`-- logo.png
live/
|-- grml/
| |-- filesystem.module [module specifying which squashfs should be used for grml]
| `-- grml.squashfs [squashfs file for grml]
|-- grml-medium/
| |-- filesystem.module [module specifying which squashfs should be used for grml-medium]
| `-- grml-medium.squashfs [squashfs file for grml-medium]
|-- grml-small/
| |-- filesystem.module [module specifying which squashfs should be used for grml-medium]
| `-- grml-small.squashfs [squashfs file for grml-small]
`-- ...
5.2. Grabbing the source

% git clone git://git.grml.org/grml2usb.git
5.3. Developers Debugging Hints

To play with grml2usb you can avoid using a real device via a loopback file setup, like:
# dd if=/dev/zero of=~/loopback bs=1M count=100 # adjust size to your needs

# losetup /dev/loop1 ~/loopback
Then create according partitions either running for example:
# echo -en "n\np\n1\n\n\nt\n6\na\n1\n w\n" | fdisk /dev/loop1
or:
# parted /dev/loop1 -s "mkpart primary fat16 0 -1s mkfs 1 fat16"
Finally create a filesystem and execute grml2usb as needed:

# mkfs.vfat /dev/loop1
# grml2usb --bootloader-only /grml/isos/grml-small_2013.01.iso /dev/loop1
5.4. Performance tracing

# blktrace -d /dev/sdX -o - | blkparse -i -
# grml2usb grml_2013.01.iso /dev/sdX1
6. Troubleshooting and Pitfalls when booting

Here is a list of common error messages from BIOS/bootloader when trying to boot from USB.
Error ran out of input data. System halted

message
Reason Everything OK, except for the filesystem used on your usb device. So instead of fat16 you are using for example fat32. Fix:
use the appropriate filesystem (fat16 for usb pens usually). The Bootsplash might be displayed, the kernel loads but you
very soon get the error message.
Error Invalid operating system
message
Reason the partition layout is not ok. Very probably there’s no primary partition (/dev/sdX{1..4}) or none has the flag bootable
set.
Error Boot error.
message
Reason Some BIOSses offer different modes for USB booting. The proper mode to boot a USB stick is USB-HDD. If that doesn’t
work or is not supported by your system, you need to format your USB-Stick as USB-ZIP. To do this, syslinux contains an
utility called mkdiskimage, which you can use to re-format your USB stick in USB-ZIP format running mkdiskimage -4
/dev/sdX 1 64 32. Please be aware that this procedure will erase all data on your stick. After executing mkdiskimage just
continue installing as usual (grml2usb … /dev/sdX4). Note that this is not going to work for any device larger than 8 GB,
since mkdiskimage only supports 1024c 256h 63s. For a more detailed explanation, refer to /usr/share/doc/syslinux-
common/usbkey.txt.
Error No operating system found.
message
Reason you forgot to set the boot-flag on the partition. Or there really isn’t any operating system at all. :)
Error kernel-panic: unable to mount root-fs…
message
Reason Kernel boots but fails to find the root filesystem. The root= argument in your kernel commandline is pointing to the wrong
device. Adjust root=…, consider using root=UUID=….
Error Could not find kernel image: …
message
Reason either a broken isolinux/syslinux version or a broken BIOS. Check out whether the vendor provides a BIOS update or if
using bootloader grub instead of isolinux/syslinux fixes the problem.
7. Frequently Asked Questions (FAQ)
7.1. Where can I get grml2usb?

grml2usb is available as Debian package via the grml-testing Debian repository.
If you do not want to (or can’t) use the grml2usb Debian package you can either use the grml2usb git tree running:
git clone git://git.grml.org/grml2usb.git

cd grml2usb
make -C mbr
sudo ./grml2usb ...
or download the provided http://grml.org/grml2usb/grml2usb.tgz (gpg signed md5 hash). Download and extract the tarball and
execute the provided script install.sh.
It is NOT enough to have just the grml2usb script itself without the according files provided either via the
Debian package, the git tree or the file grml2usb.tgz.
7.2. Why can’t I just dd the ISO to a USB device?

Well, you can. :) Starting with Grml 2009.10 the ISOs are dd-able straight out-of-the-box.
Note that ANY existing data on your USB device will be destroyed when using the dd approach.
This allows you to dd the Grml ISO to your USB device (use for example rawwrite if you’ve just a Windows system available) running:
% dd if=grml_2013.01.iso of=/dev/sdX
where /dev/sdX is your USB device. Of course this doesn’t provide such a flexible system like with grml2usb (no multi-ISO setup, no
additional default bootoptions,…) but it’s a nice way to get a working USB boot setup if you don’t have grml2usb available.
7.3. What’s the difference between grml2usb and just using dd?
grml2usb does not remove any data from your USB device and does not alter the partition table at all. grml2usb provides multi-ISO
support, support for adding default bootoptions and selecting the bootloader (syslinux vs. grub) without having to manually touch the
ISO at all.
7.4. What’s grml2iso?

grml2iso is a script which uses grml2usb to generate a multiboot ISO out of several grml ISOs. See man grml2iso for further details.
7.5. Why is there a menu.lst and a grub.cfg inside /boot/grub/?

grml2usb supports grub version 1 (grub1) as well as grub version 2 (grub2). Whereas grub1 uses menu.lst the new version grub2 needs
grub.cfg. Providing both files allows grml2usb to install grub on the target device no matter which grub version is available on the host
where grml2usb is executed on.
7.6. grub-install fails with 'The file ../boot/grub/stage1 not read correctly"?!
Check whether the partition has the right partition type. For example do NOT use FAT16 (partition type 6) when using a ext3
filesystem on the partition but instead use the correct partition type (83 - Linux) then.
7.7. grub-install complains about /sbin/grub-install and/or xfs_freeze?!

The following message:
You shouldn't call /sbin/grub-install. Please call /usr/sbin/grub-install instead!

xfs_freeze: specified file ["/tmp/tmpqaBK6z/boot/grub"] is not on an XFS filesystem
This is "normal". grub-install sends those messages to stderr. To avoid hiding any possible real error messages grml2usb doesn’t ignore
those messages.
7.8. grub-install complains about /boot/grub/device.map?!

grub-probe: error: Cannot open `/boot/grub/device.map'
This is "normal" (at least with grub1). This isn’t a problem, because the device.map file will be generated on the target device anyway.
7.9. grub-install complains about a unary operator?!

'/usr/sbin/grub-install: line 374: [: =: unary operator expected'
This is "normal". Just ignore it. (It usually doesn’t appear on the second invocation on the same device.)
7.10. grub-install fails with grub-probe: error: unknown filesystem?!

grub-probe: error: unknown filesystem

Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
usually means that the device partition table says something else than the filesystem on the device. For example using FAT16 as
filesystem type and using FAT32 as filesystem on the partition will not work. Either set filesystem type to FAT32 or format the partition
using FAT16. It is essential that device partition table and filesystem use the same filesystem type.
7.11. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD
idea.
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using
blocklists. However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: Cannot read `/grub/core.img' correctly
appears when using grub2 versions older than 1.98 as those version introduced a regression which avoids that grub is being installed into
a partition (PBR, Partition Boot Record) instead of MBR (Master Boot Record).
To work around this issue you can either 1) upgrade to grub versions >=1.98, 2) install grub into the MBR (Master Boot Record) using
the --grub-mbr option of grml2usb or 3) switch to syslinux as bootmanager (just drop the --grub option).
7.12. I’m getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?
Looks like you’ve only the grml2usb script itself available. Please make sure you’ve the grml2usb Debian package installed. The most
resent stable version is available via the grml-testing Debian repository. If you do not have a Debian system please see section Where
can I get grml2usb? in this FAQ.
7.13. Why do I have to use a FAT16/FAT32 filesystem?

Syslinux (currently) does not support any other filesystems besides FAT16/FAT32 (though that’s a sane default if you want to share
your files with other (operating) systems). If you want to use a different filesystem (like ext2/3) use the bootloader grub instead using
grml2usb’s --grub option.
FAT32 is supported since syslinux version 3.0.
7.14. Addons → Hardware Detection Tool freezes

This usually means that the machine you ran grml2usb on had syslinux 3.x installed. The version of hdt (Hardware detection tool)
shipping with Grml 2010.12 and newer requires syslinux 4.x.
7.15. I think I’ve got a really cool idea!

Great! Please check out the TODO file. Feel free to report your wishes to the author. Patches highly appreciated.
7.16. I’ve problems with booting from USB.

Check out Troubleshooting and Pitfalls when booting.
7.17. I’ve found a bug!

Please report it to the author. Please provide usage examples and output of your grml2usb commandline (consider using the "--verbose"
option).
8. Usage examples
# grml2usb /home/grml/grml_2013.01.iso /dev/sdX1
Install specified ISO on device /dev/sdX1.
# grml2usb /home/grml/grml_2013.01.iso /home/grml/grml_small_2013.01.iso /dev/sdX1
Install specified ISOs on device /dev/sdX1 for multibooting ISOs.
# grml2usb /lib/live/mount/medium /dev/sdX1
Install currently running Grml live system on device /dev/sdX1.
# grml2usb /lib/live/mount/medium /home/grml/grml_2013.01.iso /dev/sdX1
Install currently running Grml live system and the specified ISO on device /dev/sdX1 for multibooting.
# grml2usb --fat16 /home/grml/grml_2013.01.iso /dev/sdX1
Install specified ISO on device /dev/sdX1 and format partition /dev/sdX1 with FAT16 filesystem.
# grml2usb --grub --grub-mbr /home/grml/grml_2013.01.iso /dev/sdX1
Install specified ISO on device /dev/sdX1 and use grub as bootloader (instead of syslinux being the default) and install a master boot
record (MBR) to the MBR of /dev/sdX.
# grml2usb --bootoptions="lang=de ssh=mysecret" grml_2013.01.iso /dev/sdX1

# grml2usb --bootoptions="lang=de" --bootoptions="ssh=mysecret" grml_2013.01.iso /dev/sdX1
Install specified ISO on device /dev/sdX1 and use "lang=de ssh=mysecret" as default bootoptions.
# grml2usb --remove-bootoption="vga=791" --remove-bootoption="nomce" grml_2013.01.iso /dev/sdX1

Install specified ISO on device /dev/sdX1 remove vga=791 and nomce from existing bootoptions.
# grml2usb --bootoptions="persistent-path=%flavour_name" grml64_2010.04.iso grml_2010.04.iso

/dev/sdX1
Install specified ISOs on device /dev/sdx and add parameter persistent-path to every menu entry. %flavour_name will be expanded to
the flavour of the specific iso, e.g. grml64 and grml.
9. Online Ressources
Check out the grml2usb webpage and the grml2usb git repository.
10. Bugs
Please report feedback, bugreports and wishes to the author.
11. Author
Last updated 2015-03-05 01:31:15 CET

Log in
Installing Software without Synaptic

Contents [hide]
Main page 1 How to Install Software Without Synaptic
Recent changes 2 To install an tarball.
Random page
3 Cmake files.
Help
3.1 Example with configure:
Tools 4 Python files.
What links here

Related changes How to Install Software Without Synaptic
Special pages
Printable version
Reprinted with permission from Bald Brick.
Permanent link WARNING Installing apps that aren't in the repository is not a good idea if you are new to Linux, but if you have a testing setup,
Page information do use it.
To install an rpm, open a terminal, su to root, and either use the command
Code:
rpm -Uvh /path/to/the/package/you/want/to/install.rpm
or
Code:
rpm -ivh /path/to/the/package/you/want/to/install.rpm
The option "-U" stands for "update", and the option "-i" for "install". "-U" is usually the safer choice; if you don't have installed an earlier
version of an app "-U" and "-i" will do the same thing: install the package. If you have installed an earlier version of a package, "-U" will
remove the older version before installing the new one. If you want two different versions of the same program, you have to use the option "-
i", but the install may well fail.
Both the commands above will fail to finish and give you an error message if the package you are trying to install has a dependency that is
missing on your system. Then you first have to locate that dependency an install it.
If the app that you want to install and one of its dependencies are both dependent on each other, you have to install them both with the same
command.
If you want, you can also istall from Synaptic RPM-Installer for rpm package, this is simple desktop file to install rpm package, or analyzed rpm
package via right click.
'That's what great about Synaptic: it will find and install the dependencies almost automatically.
But what if you don't want to install an rpm package? What if you want to install from a tarball instead?
To install an tarball.
A tarball is simply a compressed archive. Depending on how it is compressed it may have extensions like .tar.gz or .tgz for gzip-compressed
archives, and .tar.bz2 or .tbz2 for bzip-compressed archives. Other used archives is tar.xz compression.
The archive may contain anything. Some, mainly proprietary, applications come as compiled binaries, sometimes accompanied by a script or
other program that installs and uninstalls them.
But the typical tarball would contain the source code of a program that you must compile yourself. When you unpack it you will usually find
both the code and other necessary files in a directory with more or less the same name as the tarball itself (but naturally without the the
tarball's extensions).
In that directory (or in a subdirectory) you may also find an "Info" file or an "INFO" file -- and a "README", "readme" or "Readme" file, and
sometimes "INSTALL"
Before compile this source code and install, try read files COPYING, LICENSE and INSTALL, README. The last two files should inform you:
- which dependencies you should install before compile

- how compile
- how install
More info can be also on main page website source code.
In most cases three-step recipe
./configure
make
make install
this is all you need to follow when you compile and install the application. Sometimes a lot more than three steps may be necessary,
sometimes less.
But let's suppose that the three-step formula is all your application needs.
The first step is ./configure. The dot in the beginning means "this directory": you want to run a version of "configure" that accompanies the
source code of the program you want to compile -- so you have to be in the directory containing the right "configure".
Often that is the top directory with the same name as your tarball, but it may also be a subdirectory further down in the hierarchy. Configure
script will check if you have installed the build dependencies and will inform with warnings or errors if something missing. If "./configure" gives
up with an error message before finishing you have to look at what happened just before the error and try to find out what went wrong.
More often than not the reason will be a missing dependency that you have to find and install before you rerun "./configure". If you see
missing dependencies in output in terminal, try find name packages with a tip -devel inside Synaptic and install. Than try again run script
configure.
When the script configure was successful, you should inside source code new file, Makefile, it is needed for compile.
The second step is make. Here you should not add "./" to the beginning of the command. You want to run /usr/bin/make and as /usr/bin is in
your $PATH variable you can leave out the path. But you have to remain in the directory where you ran "./configure". Command "make" will
read file "Makefile" and compile your source code.
For these two steps you can remain your ordinary user. But then comes make install, and for that you should be root. (Sometimes it may be
possible to install a program in your home directory, and then you don't have to be root -- but why would you want to?)
Other files.
Sometimes nothing writes or INSTALL and README files not exists.
Steps looks whichever files you can find, and you can see:
autogen.sh
configure or CMakeLists.txt
Makefile
In this order should be executed.

autogen.sh and configure file you can run from terminal inside source code like this:
./autogen.sh
./configure
autogen.sh will rebuild existing or create new configure file.
For CMakeLists.txt is needed cmake package installed, then you can run commands in terminal inside source code:
mkdir build
cd build
cmake ..
Command "mkdir build" create for you folder with name "build", "cd build" takes you to this folder, and "cmake" command will read
CMakeLists.txt which is ".." two levels above inside folders when we are.
Cmake doing the same what configure, this mean checks if you have installed all the dependencies needed to compile source code.
- If you have errors and you have installed all needed dependencies, just try update dependencies, to do this learn how build rpm packages.
- To check missing dependencies you can check "REAME", "INSTAL" files, website with source code, also you can check package on other
linux distribution.
Next step is just:
make
su
make install
"make" will compile source code, "su" allows to log on root user, "make install" allows install ready files.
"make install" this is also the crux of problems, when you trying install files:
- other files can overwritten and system can be broken

- none tool does not monitoring what you're trying to install, so you can not also uninstall
However sometimes you can use with source code
make uninstall
but not always working with source code.

Second way to uninstall source code is create file with list all files in system before install source code, and after install source code, the
difference file lists can be used to remove files from source code in your system. A third possibility, it use options with configure or cmake,
for example:
Cmake files.
Alternate Installation:
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/your/path/when/you/want/install/all/files
make
make install (in most case without root)
Beforw install files I suggest create folder where you want install files.
For me this is the best way install files, because:
- you have all in one place / folder

- for uninstall you can just remove folder with app
- your system can be more save when you install apps to /opt folder or /home/your_user_name/your_apps/name_app
- you don't need use root for install files
Example with configure:
./configure --prefix=your_path_where_app_will_installed
make
make install
If app not working you can try debug Debug_a_Program#Debug_with_strace_command .
and if you see: app trying open/search from source code in /usr/lib ...
you can try use autoconf before ./configure or other way
autoconf
./configure --prefix=your_path_where_app_will_installed
make
make install
Then your app should search own libs where your app ( --prefix=your_path ... )
More options you can find in:
./configure --help
cmake .. --help
Exists also gui tools for cmake,
ccmake ..
and
cmake-gui
(for this you should install cmake-qtgui package from Synaptic)
Python files.
Alternate Installation:
python setup.py install --user
In this case all will in home folder, but not in one new folder.
I suggest check output from install, because sometimes not all apps are installed in the same place in home folder.
More in https://docs.python.org/2/install/#inst-alt-install
More options you can find in:
python setup.py --help
Alternate way to remove files with commands (from source code)
python setup.py install --user --record files.txt

cat files.txt | xargs rm -rf
After that, are still empty directories.
If you do not have any of the previously mentioned files inside source code, maybe you download portable app ?
Portable apps you don't need compile and install, just run app and enjoy.
Other way is create from source code for example rpm package for PCLinuxOS
http://pclinuxoshelp.com/index.php/Packaging_for_PCLinuxOS
Category: Synaptic

Features
Business
Explore
Marketplace
Pricing
Sign in or Sign up
Dismiss
Join GitHub today
GitHub is home to over 28 million developers working together to host and
review code, manage projects, and build software together.
Sign up
mas t er livecd‐tools / docs / livecd‐iso‐to‐disk.pod Find file Copy path
F G r o s e livecd‐iso‐to‐disk+pod: Enable a ‐‐copy‐overlay option. 64de3fe on 23 Aug 2017
4 contributors
224 lines (112 sloc) 16.6 KB Raw Blame History
NAME
livecd‐iso‐to‐disk ‐ Installs bootable Live images onto USB/SD storage devices.
SYNOPSIS
livecd‐iso‐to‐disk [‐‐help] [‐‐noverify] [‐‐format] [‐‐msdos] [‐‐reset‐mbr] [‐‐efi] [‐‐skipcopy] [‐‐force] [‐‐xo] [‐‐xo‐no‐home] [‐‐
timeout <duration>] [‐‐totaltimeout <duration>] [‐‐nobootmsg] [‐‐nomenu] [‐‐extra‐kernel‐args <args>] [‐‐multi] [‐‐livedir
<dir>] [‐‐compress] [‐‐skipcompress] [‐‐no‐overlay] [‐‐overlayfs [temp]] [‐‐overlay‐size‐mb <size>] [‐‐copy‐overlay] [‐‐reset‐
overlay] [‐‐home‐size‐mb <size>] [‐‐copy‐home] [‐‐delete‐home] [‐‐crypted‐home] [‐‐unencrypted‐home] [‐‐swap‐size‐mb
<size>] [‐‐updates <updates.img>] [‐‐ks <kickstart>] [‐‐label <label>] <source> <target device>
Simplest
The script may be run in simplest form with just the two arguments:
livecd‐iso‐to‐disk <source> <target device>
To execute the script to completion, you will need to run it with root user permissions. SYSLINUX must be installed on the
computer running this script.
<source>
This may be the filesystem path to a LiveOS .iso image file, such as from a CD‐ROM, DVD, or download. It could also be the
device node reference, the LiveOS‐containing directory path, or the mount point for another LiveOS filesystem. Entering
'live' for the <source> will source the currently booted LiveOS device.
<target device>
This should be, or a link to, the device partition path for the attached, target device, such as /dev/sdc1. ﴾Issue the df ‐Th
command to get a listing of mounted partitions, so you can confirm the filesystem types, available space, and device
names.﴿ Be careful to specify the correct device, or you may overwrite important data on another disk! For a multi boot
installation to the currently booted device, enter 'live' as the target.
DESCRIPTION
livecd‐iso‐to‐disk installs a Live CD/DVD/USB image ﴾LiveOS﴿ onto a USB/SD storage device ﴾or any storage partition that will
boot with a SYSLINUX bootloader﴿. The target storage device can then boot the installed operating system on systems that
support booting via the USB or the SD interface. The script requires a LiveOS source image and a target storage device. The
script requires a LiveOS source image and a target storage device. A loop device backed by a file may also be targeted for virtual
block device installation. The source image may be either a LiveOS .iso file, or another reference to a LiveOS image, such as the
device node for an attached device installed with a LiveOS image, its mount point, a loop device backed by a file containing an
installed LiveOS image, or even the currently‐running LiveOS image. A pre‐sized overlay file for persisting root filesystem
changes may be included with the installed image.
Unless you request the ‐‐format option, installing an image does not destroy data outside of the LiveOS, syslinux, & EFI
directories on your target device. This allows one to maintain other files on the target disk outside of the LiveOS filesystem.
LiveOS images employ embedded filesystems through the Device‐mapper component of the Linux kernel. The filesystems are
embedded within files in the /LiveOS/ directory of the storage device. The /LiveOS/squashfs.img file is the default, compressed
filesystem containing one directory and the file /LiveOS/rootfs.img that contains the root filesystem for the distribution. These
are read‐only filesystems that are usually fixed in size to within a few GiB of the size of the full root filesystem at build time. At
boot time, a Device‐mapper snapshot with a sparse 32 GiB, in‐memory, read‐write overlay is created for the root filesystem.
Optionally, one may specify a fixed‐size, persistent on disk overlay to hold changes to the root filesystem. The build‐time size of
the root filesystem will limit the maximum size of the working root filesystem‐‐even if supplied with an overlay file larger than
the apparent free space on the root filesystem. *Note well* that deletion of any original files in the read‐only root filesystem
does not recover any storage space on your LiveOS device. Storage in the persistent /LiveOS/overlay‐<device_id> file is
allocated as needed. If the overlay storage space is filled, the overlay will enter an 'Overflow' state where the root filesystem will
continue to operate in a read‐only mode. There will not be an explicit warning or signal when this happens, but applications may
begin to report errors due to this restriction. If significant changes or updates to the root filesystem are to be made, carefully
watch the fraction of space allocated in the overlay by issuing the 'dmsetup status' command at a command line of the running
LiveOS image. Some consumption of root filesystem and overlay space can be avoided by specifying a persistent home
filesystem for user files, which will be saved in a fixed‐size /LiveOS/home.img file. This filesystem is encrypted by default. ﴾One
may bypass encryption with the ‐‐unencrypted‐home option.﴿ This filesystem is mounted on the /home directory of the root
filesystem. When its storage space is filled, out‐of‐space warnings will be issued by the operating system.
OPTIONS
‐‐help|‐h|‐?
Displays usage information and exits.
‐‐noverify
Disables the image validation process that occurs before the image is copied from the original Live CD .iso image. When this
option is specified, the image is not verified before it is copied onto the target storage device.
‐‐format
Formats the target device and creates an MS‐DOS partition table ﴾or GUID partition table, if the ‐‐efi option is passed﴿.
‐‐msdos
Forces format to use the msdos ﴾vfat﴿ filesystem instead of ext4.
‐‐reset‐mbr|‐‐resetmbr
Sets the Master Boot Record ﴾MBR﴿ of the target storage device to the mbr.bin file from the installation system's syslinux
directory. This may be helpful in recovering a damaged or corrupted device.
‐‐efi|‐‐mactel
Creates a GUID partition table when ‐‐format is passed, and installs a hybrid Extensible Firmware Interface ﴾EFI﴿/MBR
bootloader on the disk. This is necessary for most Intel Macs.
‐‐skipcopy
Skips the copying of the live image to the target device, bypassing the action of the ‐‐format, ‐‐overlay‐size‐mb, ‐‐copy‐
overlay, ‐‐home‐size‐mb, ‐‐copy‐home, & ‐‐swap‐size‐mb options, if present on the command line. ﴾The ‐‐skipcopy option
may be used while testing the script, in order to avoid repeated and lengthy copy commands, or with ‐‐reset‐mbr to repair
the boot configuration files on a previously installed LiveOS device.﴿
‐‐force
This option allows the installation script to bypass a delete confirmation dialog in the event that a pre‐existing LiveOS
directory is found on the target device.
‐‐xo
Used to prepare an image for the OLPC XO‐1 laptop with its compressed, JFFS2 filesystem. Do not use the following options
with ‐‐xo:
‐‐overlay‐size‐mb <size>, home‐size‐mb <size>, ‐‐delete‐home, ‐‐compress
‐‐xo‐no‐home
Used together with the ‐‐xo option to prepare an image for an OLPC XO laptop with the home directory on an SD card
instead of the internal flash storage.
‐‐timeout <duration>
Modifies the bootloader's timeout value, which indicates how long to pause at the boot prompt before booting
automatically. This overrides the value set during iso creation.
For SYSLINUX, a timeout unit is 1/10 second; the timeout is canceled when any key is pressed ﴾the assumption being
that the user will complete the command line﴿; and a timeout of zero will disable the timeout completely.
For EFI GRUB, the timeout unit is 1 second; timeout specifies the time to wait for keyboard input before booting the
default menu entry. A timeout of '0' means to boot the default entry immediately without displaying the menu; and a
timeout of '‐1' means to wait indefinitely.
Enter a desired timeout value in 1/10 second units ﴾or '‐1'﴿ and the appropriate value will be supplied to the configuration
file. For immediate booting, enter '‐0' to avoid the ambiguity between systems. An entry of '‐0' will result in an SYSLINUX
setting of timeout 1 and totaltimeout 1. '0' or '‐1' will result in an SYSLINUX setting of '0' ﴾disable timeout, that is, wait
indefinitely﴿, but '0' for EFI GRUB will mean immediate boot of the default, while '‐1' will mean EFI GRUB waits indefinitely
for a user selection.
‐‐totaltimeout <duration>
Adds a SYSLINUX bootloader totaltimeout, which indicates how long to wait before booting automatically. This is used to
force an automatic boot. This timeout cannot be canceled by the user. Units are 1/10 s. A totaltimeout of zero will disable the
timeout completely. ﴾This setting is not available in EFI GRUB.﴿
‐‐nobootmsg
Do not display boot.msg, usually, \"Press the <ENTER> key to begin the installation process.\"
‐‐nomenu
Skip the boot menu, and automatically boot the 'linux' label item.
‐‐extra‐kernel‐args <args>
Specifies additional kernel arguments, <args>, that will be inserted into the syslinux and EFI boot configurations. Multiple
arguments should be specified in one string, i.e., ‐‐extra‐kernel‐args "arg1 arg2 ..."
‐‐multi
Signals the boot configuration to accommodate multiple images on the target device. Image and boot files will be installed
under the ‐‐livedir <directory>. SYSLINUX boot components from the installation host will always update those in the boot
path of the target device.
‐‐livedir <dir>
Designates the directory for installing the LiveOS image. The default is /LiveOS.
‐‐compress (default state for the original root filesystem)

The default, compressed SquashFS filesystem image is copied on installation. ﴾This option has no effect if the source
filesystem is already expanded.﴿
‐‐skipcompress (default option when ‐‐xo is specified)

Expands the source SquashFS.img on installation into the read‐only /LiveOS/rootfs.img root filesystem image file. This
avoids the system overhead of decompression during use at the expense of storage space and bus I/O.
‐‐no‐overlay (effective only with ‐‐skipcompress or an uncompressed image)

Installs a kernel option, rd.live.overlay=none, that signals the live boot process to create a writable, linear Device‐mapper
target for an uncompressed /LiveOS/rootfs.img filesystem image file. Read‐write by default ﴾unless a kernel argument of
rd.live.overlay.readonly is given﴿ this configuration avoids the complications of using an overlay of fixed size for persistence
when storage format and space allows.
‐‐overlayfs [temp] (add ‐‐overlay‐size‐mb for persistence on vfat devices)

Specifies the creation of an OverlayFS type overlay. If the option is followed by 'temp', a temporary overlay will be used. On
vfat or msdos formatted devices, ‐‐overlay‐size‐mb <size> must also be provided for a persistent overlay. OverlayFS
overlays are directories of the files that have changed on the read‐only root filesystem. With non‐vfat‐formatted devices, the
OverlayFS can extend the available root filesystem space up to the capacity of the Live USB device.
The ‐‐overlayfs option requires an initial boot image based on dracut version 045 or greater to use the OverlayFS feature.
Lacking this, the device boots with a temporary Device‐mapper overlay.
‐‐overlay‐size‐mb <size>
Specifies creation of a filesystem overlay of <size> mebibytes ﴾integer values only﴿. The overlay makes persistent storage
available to the live operating system, if the operating system supports it. The overlay holds a snapshot of changes to the
root filesystem. *Note well* that deletion of any original files in the read‐only root filesystem does not recover any storage
space on your LiveOS device. Storage in the persistent /LiveOS/overlay‐<device_id> file is allocated as needed. If the
overlay storage space is filled, the overlay will enter an 'Overflow' state where the root filesystem will continue to operate in
a read‐only mode. There will not be an explicit warning or signal when this happens, but applications may begin to report
errors due to the restriction. If significant changes or updates to the root filesystem are to be made, carefully watch the
fraction of space allocated in the overlay by issuing the 'dmsetup status' command at a command line of the running
LiveOS image. Some consumption of root filesystem and overlay space can be avoided by specifying a persistent home
filesystem for user files, see ‐‐home‐size‐mb below. The target storage device must have enough free space for the image
and the overlay. A maximum <size> of 4095 MiB is permitted for vfat‐formatted devices. If there is not enough room on
your device, you will be given information to help in adjusting your settings.
‐‐copy‐overlay
This option allows one to copy the persistent overlay from one live image to the new image. Changes already made in the
source image will be propagated to the new installation.
WARNING: User sensitive information such as password cookies and application or user data will be copied to the
new image! Scrub this information before using this option.
‐‐reset‐overlay
This option will reset the persistent overlay to an unallocated state. This might be used if installing a new or refreshed image
onto a device with an existing overlay, and avoids the writing of a large file on a vfat‐formatted device. This option also
renames the overlay to match the current device filesystem label and UUID.
‐‐home‐size‐mb <size>
Specifies creation of a home filesystem of <size> mebibytes ﴾integer values only﴿. A persistent home directory will be
stored in the /LiveOS/home.img filesystem image file. This filesystem is encrypted by default and not compressed ﴾one may
bypass encryption with the ‐‐unencrypted‐home option﴿. When the home filesystem storage space is full, one will get out‐
of‐space warnings from the operating system. The target storage device must have enough free space for the image, any
overlay, and the home filesystem. Note that the ‐‐delete‐home option must also be selected to replace an existing persistent
home with a new, empty one. A maximum <size> of 4095 MiB is permitted for vfat‐formatted devices. If there is not enough
room on your device, you will be given information to help in adjusting your settings.
‐‐copy‐home
This option allows one to copy a persistent home.img filesystem from the source LiveOS image to the target image.
Changes already made in the source home directory will be propagated to the new image.
WARNING: User‐sensitive information, such as password cookies and user and application data, will be copied to the
new image! Scrub this information before using this option.
‐‐delete‐home
One must explicitly select this option in the case where there is an existing persistent home filesystem on the target device
and the ‐‐home‐size‐mb <size> option is selected to create an empty, new home filesystem. This prevents unwitting
deletion of user files.
‐‐crypted‐home (default that only applies to new home‐size‐mb requests)

Specifies the default option to encrypt a new persistent home filesystem when ‐‐home‐size‐mb <size> is specified.
‐‐unencrypted‐home
Prevents the default option to encrypt a new persistent home directory filesystem.
‐‐swap‐size‐mb <size>
Sets up a swap file of <size> mebibytes ﴾integer values only﴿ on the target device. A maximum <size> of 4095 MiB is
permitted for vfat‐formatted devices.
‐‐updates <updates.img>
Setup a kernel command line argument, inst.updates, to point to an updates image on the device. Used by Anaconda for
testing updates to an iso without needing to make a new iso.
‐‐ks <kickstart>
Setup inst.ks to point to an kickstart file on the device. Use this for automating package installs on boot.
‐‐label <label>
Specifies a specific filesystem label instead of default LIVE. Useful when you do unattended installs that pass a label to
inst.ks
CONTRIBUTORS
David Zeuthen, Jeremy Katz, Douglas McClendon, Chris Curran and other contributors. See the AUTHORS file in the source
distribution for the complete list of credits.
BUGS
Report bugs to the mailing list http://admin.fedoraproject.org/mailman/listinfo/livecd or directly to Bugzilla
http://bugzilla.redhat.com/bugzilla/ against the Fedora product, and the livecd‐tools component.
COPYRIGHT
Copyright 2008‐2010, 2017, Fedora Project and various contributors. This is free software. You may redistribute copies of it
under the terms of the GNU General Public License http://www.gnu.org/licenses/gpl.html . There is NO WARRANTY, to the
extent permitted by law.
SEE ALSO
livecd‐creator(1) , project website http://fedoraproject.org/wiki/FedoraLiveCD

Terms
Privacy
Security
Status
Help
Contact GitHub
API
Training
Shop
Blog
About
This website uses cookies to ensure you get the best experience on our website. By continuing to browse the site, you agree to our use of cookies. More info
Call us: 1-888-347-5462

Search English
Customer Login
Products Resources Partners Service & Support Company
Protect & Restore Ask For Webinar

Attend our free
Business Continuity and Disaster Recovery Made Easy webinar to learn more!
Easily get started from powerful free editions!

White Paper
VMware vSphere Free for agentless backup & replication of VMware
Snapshot, Backup, or Replication?
guest systems Size: 520 KB
Windows Workstation Free for agent-based backup & restore of
Windows workstations
Manual
Multi-tier storage infrastructure and exclusive data deduplication Protect & Restore
Remote recovery and on-site hardware independent restore (HIR) Size: 6.7 MB
Application-level backup of MS Exchange databases
Pre-sales FAQ
Protect & Restore
Protect & Restore Videos/Best Practice Downloads Features Get started!
Try Paragon Protect & Restore!

Paragon Protect & Restore includes everything which the ever more complex IT world requires to ensure the continuity of business operations in the event of a
system failure. It minimizes license management, training and support work in comparison with the use of various different individual products. The user interface
provides unhmapered visibility, simplifying operation and making work easier for system administrators in conjunction with individually configurable notification
and reporting options. Try out our comprehensive solution for yourself! You’re only a few clicks away from this amazing software for data security and restoration in
case of emergency.
Paragon Protect & Restore Paragon Protect & Restore VM Paragon Protect & Restore -
Free Edition Copy Tool Trial Version
No risk or obligation: The free solution for virtual The complete solution with all
Everything you need for backup, machines cloning with their snapshot functions accessible for virtual,
replication and restoration of virtual trees between different VMware ESX physical and mixed infrastructures as
VMware/vSphere and physical hosts and vCenters – even if you a free trial license, which includes a
Windows machines. The unlimited don’t use clusters or shared storage. 30-day trial period along with
free version can be upgraded to evaluation support from our support
expand functionality at any time. team.
Download free of charge ››

Download free of charge ›› Request an evaluation
copy ››
User Manual - VM Copy Tool ››

Fact-Sheet - Workstation Free ››
Fact-Sheet - Protect & Restore ››
for Windows for Mac Technologies Services About Join for exclusives!
Hard Disk Manager NTFS for Mac GPT Loader Support About Us Connect with us for giveaways,
Drive Backup CampTune Alignment Tool Beta Programs Latest news exclusive promotions and latest
Partition Manager Hard Disk Manager for NTFS-HFS Converter Knowledge Base Employment news!
Drive Copy Mac Support Forum Contact Us
MyParagon
Protect & Restore Rescue Kit for Mac Technology Advisory Press room
Login
Council Blog
IT Essentials Toolkit Partners Support request Subscribe to our newsletter
TeamViewer Sitemap
Paragon Partner MyDownloads Enter your email and receive
Program MyUpgrades Legal updates about special offers and
Paragon Affiliate Product registration Imprint exclusive content!
Program Company Details
Terms Newsletter Sign-Up ›
Privacy Statement
Copyright © 1994-2018 Paragon Technologie GmbH.

SOFTPEDIA®  WINDOWS  DRIVERS  GAMES  MAC  ANDROID  LINUX  WEBAPPS  NEWS   
 Softpedia > Linux > Linux Distributions > KNOPPIX-NSM FLASH SALE: Heimdal PRO  70% OFF!
DOWNLOAD KNOPPIX-NSM Search... 
 KNOPPIX-NSM 1.2 4,580 downloads · Updated: May 9th, 2007 · GPL  
 3.2/5 18 
Advertisement
 FILENAME:
knoppix_nsm-1.2.iso
 RUNS ON:
DESCRIPTION DOWNLOAD FEATURES  IMAGES
Linux
 MAIN CATEGORY: knoppix-nsm is dedicated to providing a framework for individuals wanting to learn about
Linux Distributions Network Security Monitoring.
 3 SCREENSHOTS: Advertisement
KNOPPIX-NSM is dedicated to providing a framework
for individuals wanting to learn about Network
Security Monitoring.
 We have tryed to do most of the hard work to help

get the beginner/newbie up and running fast so they
spend more time learning about NSM, leaving the
details as a later exercise once familiar with the
concepts.
KNOPPIX-NSM is based on the ever popular Knoppix,

which means that you can test all the tools in a live
 DEVELOPER:
session running on the cd without installing to
www.securixlive.com harddrive. KNOPPIX-NSM has the added bonus of be
able to install to harddisk so you can deploy a NSM
 VISIT HOMEPAGE
framework into your production network and use it
for realtime monitoring.
Advertisement
Some of the benefits include:
Rapid sensor deployment
You can boot you sensors from the live CD, store all
data to a local HD partion and have them logging
back to a central server.
Complete out of channel Intrusion Detection and

Analysis center
With KNOPPIX-NSM you can deploy a complete NSM

network to monitor your existing network
infrastructure. KNOPPIX-NSM comes pre-configured
for deployment of multiple sensors and databases, all you need to do is create the sensor accounts in
the database and change some passwords.
Secure
KNOPPIX-NSM has been built with security in mind. All remote communications are over ssl tunnels
so that you do not have to be concerned about eaves droppers if you decide to run KNOPPIX-NSM in
your main network channels. Another feature is the use of iptables to ensure that only allowed hosts
can connect and only necessary services are visible to the network.
Easy console deployment
Need another console, just boot from the cd (setting the host and ip at boot time) and you are up and
running straight away.
The intent of KNOPPIX-NSM is to provide a distrubtion with accompanying documentation on the

tools that we have selected and how they are put together in the NSM framework.
#Linux distribution, #Operating system, #Knoppix distro, #KNOPPIX-NSM, #Distribution,

#Linux, #OS
DOWNLOAD KNOPPIX-NSM 1.2
I  SOFTPEDIA®  202K 56K  13K  Search here...

© 2001-2018 Softpedia. All rights reserved. Softpedia® and the Softpedia® logo are registered trademarks of SoftNews NET SRL • Privacy Policy • Cookie Policy • Cookie Settings • Contact
Log in
Main page Discussion Read View source View history Search PCLinuxOSHelp Knowle
Main Page
Main page
Recent changes PCLinuxOS is about freedom, not just the free you get when you
Welcome to don't have to pay for something, but the kind of freedom to do what
Random page
you will with it, and to use it in any manner or fashion that best fits
Help
PCLinuxOS Knowledge Base your needs and intentions. It is truly by the people, of the people,
for the people.
Tools
What links here "The place where you learn PCLinuxOS" The Philosophy of PCLinuxOS is :
Related changes It is done when it is done
At present there are 251 articles here.
Special pages Use the best software available for the task, does not matter if it
Printable version is Qt, GTK etc
Permanent link
Be focused on the desktop.
Page information
Currently this wiki is being restored from a backup. Until the work is complete you are likely to see
missing links and outdated formatting. Please bear with us while we work on getting it back to
proper shape.
News and announcements Get PCLinuxOS

2018 Jul 24 : Work on restoring the Main Page has begun in earnest. Old design is being Official releases
copied manually from archives and restored delicately keeping as much formatting as Download via HTTP or FTP :
possible. KDE
Some details may look different. MATE
Download via BitTorrent :
Table of contents KDE Torrent Magnet

MATE Torrent Magnet
PCLinuxOS (abbreviated pclos) is a Linux distribution written from bottom to top with you, the Preloaded Discs :
new Linux user, in mind. None at present
Community releases
Introduction Collection :
DarkStar 2018.06 • md5sum
Welcome statement • What is PCLinuxOS? • The 10 commandments for Linux users • XFCE 2018.05 • md5sum
Flavors of PCLinuxOS • Community derived flavors • Minimum hardware requirements • LXDE 2018.01 • md5sum
TDE 2018.06 • md5sum
Get, Test and Install PCLinuxOS

Ways to get PCLinuxOS • About bittorrent • Md5sum checking • Burning PCLinuxOS disc • Links / Help / Community
Live CD faq • Installing PCLinuxOS • Things to do after installation • Official website
PCLinuxOS Twitter account
Forums • Where to start
PCLinuxOS and Hardware Magazine
PCLinuxOS Hardware Database is the central repository of hardware compatibility IRC Live chat at Freenode :
• " PCLinuxOS Support
information. This contains many sections such as : • " PCLinuxOS Chat
• Computers • Components • Storage media • Output devices • Input devices • Networking International websites
• Imaging devices • Multimedia • Other hardware •
Hwinfo can be used to get details about your hardware • Learning about your hardware • Contribute / Develop
Resolution size •
Contributions for the development of
PCLinuxOS are accepted in various
Update and Maintain PCLinuxOS ways including but not limited to :
Donations in cash or kind
Update PCLinuxOS • Synaptic Software Manager • Repositories • Synaptic and the
Testing and bug reporting
Repositories • Choosing the Right Repository • Installing Software without Synaptic • Root Artwork contributions
password • Passwords • LiveCD, Create your own • Backup your “just right” PCLinuxOS • Packaging for PCLinuxOS
Cron jobs • Disk Space Checking • Disk Usage Checking • R.E.I.S.U.B. reboot your system Patches and code contributions
Providing community support in
• forum / IRC
Writing and maintaining
documentation
Customize PCLinuxOS
Customize PCLinuxOS • Changing the default home directory • Kernel • Cheat codes/boot
codes • DNS, Changing your • DenyHosts Setup • File Sharing • Fonts, Windows • Grub
background theming • Hostname, Change Your • Mailfilter Installation and Operation •
Startup/shutdown music •
Software
Applications equivalences • PCLinuxOS Specific Software • Tar & tar.gz •
HowTo pages
The HowTo section contains many pointed and in-detail articles addressing a single issue.
For example :
HowTo do Bluetooth Dial Up Networking with PCLinuxOS • HowTo Properly Update Your
PCLinuxOS •
Errors and solutions

The Errors and solutions section lists many common and uncommon errors you might come
across in your day to day usage. It explains the cause where known and lists the possible
solution(s).
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held

packages. • Touchpad troubles - solutions by Texstar •
Miscellaneous
Not sure what a particular term means? Then check out the Glossary • Known issues
Advanced
This Advanced section lists pages that require slightly advanced knowledge of Linux beyond
point and click ability. You may often be found deep in the command line while following pages
listed here. Also not following instructions correctly might result in severe damage to your
PCLinuxOS installation.
Compiling drivers for Realtek card reader • CLI-commands • Configuration Files • •
Editing the Wiki

You need to have an account with us and logged in before you can edit this wiki. Checkout PCLinuxOS Wiki:Syntax before editing this
wiki. Feel free to add to this wiki, however, keep the content appropriate and useful. This is not the place to report bugs or to request help.
You can try the wiki syntax in the Sandbox, the test page.
For more information about editing this wiki, please visit PCLinuxOS Knowledge Base Wiki.
In case you still find it difficult to understand and follow the syntax, do not fear. We have a special Content dump page where you can just
enter the content you know will be useful without worrying about formatting. Someone will come along and do the job for you later.
This page was last edited on 25 July 2018, at 13:09.

Create an account or log in
article discussion view source history
Main Page
Welcome to the Damn Small Linux Community Wiki!!!

navigation Main pages of other languages: español, deutsch, Türkçe
Main Page
Community portal
Current events
Documentation News
Recent changes
Random page
Getting Started with DSL This is a temporary static mirror of the DSL wiki. I am in the process of
Help
updating the DSL server. Static copies of the wiki, blog area, and forums
Donations About Damn Small Linux
are an attempt to preserve all data as I update the site. Much of the
search Frequently Asked Questions (and short answers)
scripting on the site is old, vulnerable and has been abused. If you see
Local Startup Documentation something I missed please contact me: (John2 at this website's name).
What do I need to use DSL?
Go Search Thank you so much Fioddor, Winter Knight and everyone else
DSL Compared to Microsoft Windows
who has helped to maintain this wiki!
toolbox Known Issues
View All Docs The New Forums are now open.
What links here
Related changes
Installing DSL
Upload file
Special pages Choose the Right CD Image
About This Wiki
Printable version Getting DSL From the Mirrors
Other Ways to Get DSL
Creating a DSL CD
Frugal Install All For One
HDD Install
This is the community driven documentation effort for Damn Small
Installing to a USB Flash Drive
Linux . If you don't find the information you need, ask questions in the
Floppy Only Install with Netcard (Poormans Install)
forums . For general, Linux-type info, try here.
Booting compressed image from hard drive with Loadlin (from
DOS/Win98) One For All
Successful Installation Notes If you wish to contribute to this wiki, Thank You! Please read How To
Booting DSL Use This Wiki first so that we don't step on each others' toes. This page
has been locked to prevent vandalism. Use the Main Page Beta if you
Your BIOS and You
want to edit this page, and your changes will turn over shortly afterward.
Boot Floppies
Startup Commands A.K.A. Cheat Codes or Boot Options Important Stuff
USB Booting You need to read the Disclaimer.
Installing Grub History of this, the DSL Documentation Project.
Starting Programs at Boot
Saving Your Settings
Getting Help
Extending DSL with MyDSL
This wiki has answers to your questions. To post your questions,
About MyDSL extensions
though, visit the forums or IRC. The forums are always active. The wiki
Installing MyDSL Extensions
ops just don't spending much time searching for questions hidden in the
Creating MyDSL Extensions
wiki.
Using Installed MyDSL Extensions
Wanted MyDSL Extensions The Forums
Hacking DSL
The DSL Forums
Common Issues Forum Rules
The Search Function
Introduction to the DSL Desktop
Verified Wireless Cards Realtime Support
How to transfer files between Embedded and host Windows system
The DSL IRC Channel
Language Support
IRC Rules
Adding Icons to the Desktop
Reducing Memory Usage Community
Changing the Hostname
Configuring printers People of DSL
Optimizing Video Drivers Lead Developers
.desktop Wiki Master
.Xdefaults Beta-testing Team
Moderators
Crazy People Who Won't Go Away
This page was last modified 18 May 2012 09:57. This page has been accessed 1,649,369 times. About DSL Wiki Disclaimers
Log in
Cron jobs
Crontab Configuration Under Linux
Main page
Recent changes Cron is a time-based job scheduler in Unix-like computer operating systems. The name cron comes from the word “chronos”, Greek for “time”. Cron enables users to schedule jobs to run periodically at certain times
Random page or dates. It is commonly used to automate system maintenance or administration, though its general-purpose nature means that it can be used for other purposes, such as backing up important data.
Help
Each cronjob has following syntax:
Tools
What links here

Related changes
Special pages
Printable version
Permanent link
Page information
command to be executed
STEP 1: Now, Open terminal as a root / normal user and enter the following
crontab -e 1 * * * * /bin/echo "Congratulations...!"
This will echoed “Congratulation…!” every minute and you can see this message in user’s mail box. Save and exit the file.
STEP 2: Restart the cron daemon to make it effective, use the following command service crond restart
What does the line actually mean
crontab -e means to edit the users cron file. Your cron file(s) is located at /var/lib/spool/cron
The '1 * * * *' is the time base. 1 is the number of minutes to be ran. the following '* * * *' are wild cards meaning ALL so we are running this command every one minute of every hour, of every day of the month, every
month of the year, and every day of the week.
If the command line is not your cup of tea, there are several good GUI programs for setting up your cron job.
Webmin is a simple way to setup cron. It also is in the Repository.
So what can cron be used for besides sending out a silly little messages every minute, you ask? You can use it for almost anything. Only your mind is the limit of the things cron can do.
automate a daily backup send yourself reminders create and keep your own repository up to date
If you can dream it, cron surely can do it!
Category: HowTo

Log in
Packaging for PCLinuxOS

Relevant to all editions of PCLinuxOS.
Main page A packager is the life blood of PCLinuxOS . Packager is the one who keeps PCLinuxOS updated. Learning to package is an important step
Recent changes towards making useful contributions to the betterment of PCLinuxOS.
Random page
Help The whole process is easy to learn with a little attention to detail and perseverance. In case you run into difficulties just go to the forums or
IRC to get help.
Tools
Contents [hide]
What links here
Related changes 1 Introduction
Special pages 2 Rough overview
Printable version 3 Approach to learning
Permanent link 4 New packagers - How to get started
Page information
5 Setting up the build environment
6 Building - step by step
7 Gathering information
8 Dos and Don'ts
9 Dependency management
10 Packagers Tips and Hints
11 Notes
12 Errors and Warnings
13 Reading references
Introduction
Packaging is the process of preparing installable packages from source code of individual software. It is an umbrella word used to cover all
the things including building right from the source to adjusting spec files and making a PCLinuxOS package out of RPMs available elsewhere
to updating existing PCLinuxOS packages.
In order to become a successful packager, it is necessary to have patience. Do not give up easily. If you do not succeed, try again and again.
It is also very important to read a lot initially until your mind gets the picture.
Even if initially you do not understand whatever you are reading or supposed to do, continue reading or doing it. The puzzle will be solved in
the end.
Rough overview
Please understand that this section is only aimed at providing an approximate picture of what and how building a package works.
This is unlikely to be perfectly correct and hence you have to verify the correctness of this information on your own.
During packaging, we convert original software/items from coders into a form which is ready for download and installation by end users.
Now the original software/items could be media (wallpapers, icons, sounds etc.) or software (binary executables, source code) The most
common use of packaging however is to convert source into installable .rpms for end users.
Software from source - Most of the software written by humans is in the form of a human readable language such as Assembly, C /
C++, Java / Python. However a computer will only understand instructions in machine language which is in binary form. So we need to
convert the software from human readable languages to machine language. This is done by a method known generally as compiling /
building.
- In case of C / C++ etc., this conversion is done in the process of packaging by compiling / building.
- Java looks like a gray area what with there being an intermediate conversion to bytecode. Please read this guide for more
information on packaging Java programs - Creating an RPM for a Java Application' -
http://javaworkshop.wordpress.com/2008/10/22/rolling-up-an-rpm-for-a-java-application/
- In case of interpreted languages, this conversion is done on the fly during their execution in the user's computer. Hence here the
source is packaged as is.
Now this building can happen at 3 different levels :
- At the original author of software : Most commercial software is distributable pre-built.

- At the distributor : That is what our Bacon Brigade does.
- At the end user : Luckily users of PCLinuxOS do not have to do this. This is the standard method in source based distros.
So in our case the following is done :

- Software is procured from source by the packager.
- Source is extracted to BUILD area and build commands run there to get the target software.
- A directory structure mimicking the user's computer is created inside BUILDROOT. The target software is now installed into BUILDROOT
as if it is getting installed into the user's computer.
- The resulting files are picked out of this BUILDROOT environment and put together inside an archive and this is called a package. This
will be found in /src/rpm/RPMS/i586 or x64 depending on the target.
- A copy of the source code along with the .spec file used to create this package is placed in /src/rpm/SPRM. This is what is used by the
maintainer of PCLinuxOS to recreate the same package and enter it into the official repository after quality control checks.
Software binaries and media - Things are slightly different when it comes to binary packages and media as they already come in
compiled binary form. They mostly only need to be placed into their proper location.
Approach to learning
Please read through the complete guide. Parts of the guide are verbatim or barely modified posts from the forum by the authors
referred. Considering the high level of knowledge of the respective authors, it might seem intimidating at first. (I had a similar
experience too). Just read the rest of the guide.
To begin with you should learn rebuilding something which is already present in our repository. Look for software of size less than 1 MB at
first.
Next you should try to package something similar by your own. Try very simple items containing just 1 or 2 files.
Next you should try updating something in the present repository. (You will need to study the version numbers of existing packages and
compare them to those from the official websites in order to know which can be updated.)
Now you could try and package a software not present in the repository or without looking at the already packaged version.
Once you are comfortable here, try packaging libraries after understanding about them.
Now you could try your hand at very complex and interlinked packaging tasks such as whole desktop environments, wine etc.
At this level, you could try to package binary software such as graphic drivers etc.
New packagers - How to get started

Get an idea of our repository set-up by reading this page Repository and Sections and Mirrors .
Posted by Neal on the forum
Go to http://ftp.nluug.nl/pub/os/Linux/distr/pclinuxos/pclinuxos/ and scroll down to the SRPMS.(*) sections. Clicking any of those links will
open that section, where you will find SRPMs for PCLinuxOS.
These are the best src.rpms to start out with learning to package upto PCLinuxOS standards. Study them. Look closely at how the spec
files are written.
You should not start with an SRPM from another distro, as these will require changes you may be unaware of. They often use different
naming conventions, so that the BuildRequires and Requires in their spec files will call for something that has a different name in
PCLinuxOS. They may install to different directories, which will cause difficulties, also.
The point is that you should start with learning to rebuild PCLinuxOS packages, proceed to learning how to upgrade our packages and
only after learning how to create a PCLinuxOS package should you attempt to convert an SRPM from elsewhere.
Same folder from other mirrors of PCLinuxOS can also be used instead of NLUGG.
Setting up the build environment

Please follow these steps :
Download and install the KDE MiniMe or LXDE Mini flavour on a separate partition.
Install pkgutils-kde or pkgutils-thunar which will also install pkgutils.
Install jpackage-utils
Select the user name by clicking on it when prompted to setup that user as packager. All the packaging related directories will be created
under src directory in this user's /home.
NOTE : Even if there is only one user in this installation, it is necessary to click and highlight the user name. Else the process of setup will
be cancelled and you will need to re-do it from commandline using mkrepo command.
Avoid using special characters in the user name of packaging environment.
If everything went correctly, the /home/xxxx where xxxx is the packaging user name will have a new directory called src. If you go deeper
into it, there should be apt rpm tmp.
apt should be your local repository for self created packages.

rpm is where your packaging will happen.
tmp is a temporary directory.
/home/xxxx/src/rpm/RPMS will store built .rpms either in i586 or x86_64 depending on which architecture you are packaging for.
/home/xxxx/src/rpm/SOURCES will store your sources in tar.xz format for building.
/home/xxxx/src/rpm/SPECS will store the .spec files needed for the build.
/home/xxxx/src/rpm/SRPMS will store the final .srpms. These will be needed when you have succeeded in building, testing the package
and ensuring that it is bug free, to upload for the consideration of PCLinuxOS maintainer.
There will be 2 hidden files under /home/xxxx namely .rpmmacros and .rpmrc
Building - step by step

Now to the actual process of building a PCLinuxOS package. We need the following :
Source - It will be available for download from the original developer website or at the .srpm link mentioned above. It may be available as
tar.gz or tar.xz or in any other compressed format. However PCLinuxOS specifications require that you convert any of them to the tar.xz
format. This can be done easily by right clicking on the downloaded file and using convert to tar.xz option. Now this source file in tar.xz
format has to be placed in the /home/xxxx/src/rpm/SOURCES directory.
Spec - This is the file which contains instructions about the actual process of building. It can either be built anew or updated suitably from
an older version .srpm existing in our repositories.
Dependencies - Any package which we are trying to build may need the existence of other packages. Dependencies can be either
build-time or run-time. Build-time dependencies are usually in the form of -devel packages while run-time dependencies are usually in the
form of libraries or other packages. Dependencies can be ascertained by reading the release notes of original developer, Readme.txt or
equivalent text file inside the source package or by going through older .spec file. An easy way to install dependencies needed for build is
to right-click on the .spec file and select Install dependencies. Alternatively, one can make a list of dependencies and install them one-
by-one through Synaptic or apt-get install from command line.
If you are rebuilding a package from .srpm, you may either right-click on the .srpm and select Install for build option or go to command
line, navigate to the directory with the .srpm and type :
rpm -ivh nameofthepackage.srpm
Once everything is ready, you may right click on the .spec file and select Build all or Build all, log file options to start building.
Alternatively, navigate to the /home/xxxx/src/rpm/SPECS directory and type :
rpmbuild -ba nameofthepackage.spec
Time taken to complete build will depend on the size and complexity of the package, power of the build machine etc.
Right-click build will open a special purpose shell which will not close on completion. End of build is indicated when you see a exit 0 as
the last line.
If the build was started from commandline, you should be back at the command prompt once the build is complete.
Watch the output of the build carefully. Generally any WARNING will not cause the build to fail, but may cause some problems with the
package later on. However any ERROR will generally cause the build to abort. Note down these for further research.
Run gbd from the command line to update your local repository and then use Synaptic to install this and check if things work properly.
Gathering information
Before or during building / troubleshooting a build, you would need to have some information regarding settings, options etc. There are many
places to look for such information and the location would also depend on the language, type of package etc.
Homepage - If the package has a well maintained homepage, it should be your first port of call.
Source - The source tarball or the directory will have files such as README, INSTALL, CHANGELOG which are also very good sources
of information.
configure.ac - This file could provide very useful information about BuildRequires.
./configure --help - The options available for build could be ascertained by extracting the package to a directory and then running this
command from a terminal.
Dos and Don'ts

Slightly modified version of a post by Texstar on the forum :
Name your specfile - pclos-name-of-package.spec (example: pclos-doxygen.spec)

This makes it handy if you are updating a package and encounter a build error. You can install another distribution's source package and
compare their spec file with yours to see if they added a patch or a different build option to make the new version build.
Convert your source tarball to tar.xz from tar.gz and tar.bz2

The public servers do not have infinite space and bandwidth. By re-compressing your source tarball with tar.xz you will generate a much
smaller SRPM. This saves space on the mirrors and makes uploading the SRPMs from the build server to go much faster as there is less
to upload.
Use proper versions of your package release

If this is a new package going into the PCLinuxOS repository even if it has been based on another distribution's specfile then your
release macro for PCLinuxOS is %mkrel 1
Make a complete changelog

This gives information as to when the package was built, who built it, an email contact, version number and a description of what you did
to the package. If you are importing a package from another distribution then all you need to do is add in the description area based on
original specfile from fedora, Opensuse, mdv etc...
Example:
- Mon Mar 28 2011 Texstar <texstar at gmail.com> 1.7.4-1pclos2011
- 1.7.4
- add requires for new glibc
gcc/glibc updates need additional requires

When you update your gcc/glibc you will need to add the following to your specfile to force the user to update the following 2 packages to
ensure the new programs compiled with gcc 4.5.2 will install and run properly on their existing system.
Requires: glibc >= 2.12.1
Requires: libstdc++6 >= 4.5.2
Neal on the forum :
Test your packages before uploading them.

If you package beta software, be sure you put a note with it saying so. We will want to add it to testing first.
Do not package alpha software. Period!
Periodically check to see if a package you have submitted has an update available. If it does, create a new package, test and
submit it.
Don't forget your changelog entry. Be sure you use the day, date (Month and numbered day of the month) and year of the day you build
the package. Add your info to the entry. Do not use the info of the previous packager.
Dependency management
Slightly modified version of a post by TerryN on the forum :
Many people who are new to packaging think that dependency management is only about the Provides: and Requires: tags in the spec file.
These are only part of the story because rpm does automatic dependency generation as part of the rpmbuild process. This is handled by 2
scripts find-provides and find-requires which you will see run towards the end of the build.
find-provides :
This script examines all the files in the %files list and if any shared libraries are found the soname of the lib is added to the list of
capabilities provided by the rpm. This means that if another package depends on that shared lib your package can be selected by
apt/synaptic to satisfy that dependency.
- Be very careful when packaging apps where the SOURCES contain pre-built libraries as they will be added and you could find your
package being selected as a dependency of a seemingly totally unrelated application (Calibre springs to mind). Worse still, this can lead
to instability if those libraries are used with another application (because they were not built on PCLinuxOS).
- To avoid this you can add Autoprov: No to the summary section of the spec file (that is where the
Provides/BuildRequires/Requires/Obsoletes tags go) for these types of package (and only these types of package!).
Autoprov: No
- Documentation for these tags is here .
find-requires :
This script examines all the files in the %files list and effectively runs an ldd ( more about ldd ) on any executable to see what shared-
libraries are needed by the executable. The sonames for these libraries are added to the list of capabilities required by the rpm and will
need to be resolved when the rpm is installed.
- Once again pre-built binaries in the SOURCE can cause issues as they may reference sonames which cannot be resolved by existing
packages in the repo.
- An example would be because the SOURCE contains binaries for multiple architectures (see example here)
Devel dependencies :
There is a further twist with shared objects which are to be used as system shared libraries (there are other uses for .so files). The build
will produce 3 "copies" of the lib (actually only 1 is a real file the others are links but that doesn't matter for the purposes here ) :
/usr/lib/libxyz.so.1.2.3
/usr/lib/libxyz.so.1
/usr/lib/libxyz.so
The first 2 (the versioned files) are required at runtime and should be in the main package. The 3rd one (libxyz.so) is only required by the
linker when building apps against the shared lib and should therefore be in the -devel package (along with header files).
RPM is clever enough to know this and generates "devel" provides/requires for that file. Therefore if you put the unversioned .so in the
main package the automatic dependency management will generate a "devel" provides:
[terry@localhost ~]$ rpm -q --provides kde-workspace-core | grep devel

devel(libkwinglesutils)
devel(libkwinglutils)
devel(liboxygenstyleconfig)
devel(libpowerdevilconfigcommonprivate)
devel(libpowerdevilui)
and therefore devel dependencies:
[terry@localhost ~]$ rpm -qR kde-workspace-core | grep devel

devel(libdl)
devel(libEGL)
devel(libgcc_s)
devel(libGL)
devel(libGLESv2)
devel(libICE)
devel(libkdecore)
devel(libkdeui)
devel(libkephal)
devel(libkwineffects)
devel(libm)
devel(libpowerdevilcore)
devel(libpowerdevilui)
devel(libQtCore)
devel(libQtDBus)
devel(libQtGui)
devel(libQtSvg)
devel(libSM)
devel(libstdc++)
devel(libX11)
devel(libXau)
devel(libXdmcp)
devel(libXext)
devel(libXft)
devel(libXpm
and these devel dependencies will have their own dependencies etc. etc. This could result in a large amount of unnecessary -devel
packages and other "build" packages being installed on systems which are not used for software building. This can consume a lot of
space and make things like remastering more difficult.
If you are sure that nothing will ever want to link/build against such a library you could avoid creating a -devel subpackage by either
deleting the .so at the end of the %install section
rm -f %buildroot/%{_libdir}/libxyz.so
or using a %exclude' for the file in the %files list.
%files
...
%exclude %{_libdir}/libxyz.so
but if there is any doubt it is safer to provide a -devel package.
To summarize, great care must be taken with dependency management when dealing with system shared libraries. It is
complicated, tedious and certainly not glamorous but it IS necessary to avoid the repo descending into bloat and chaos.
Packagers Tips and Hints

Instructions specific to particular categories of packages are listed on Handling package categories page.
This is a running thread on the forum with many important tidbits of information to guide you in your packaging :
http://www.pclinuxos.com/forum/index.php/topic,101266.0.html
Old and new libraries and how they affect updates : http://www.pclinuxos.com/forum/index.php/topic,110765.0/topicseen.html
Notes
SRPMs : http://ftp.nluug.nl/pub/os/Linux/distr/pclinuxos/pclinuxos/srpms/SRPMS.pclos/
The importance of being organised can never be over emphasized. Note down everything. It may help with the work you are currently
engaged in or in another work later on.
Do not package as root.
Always keep a clean and fully updated packaging environment. This means run a full update before beginning a task and remove any
dependencies / libraries installed for a particular work before going on to another.
When you run rpm -ivh nameofthepackage.srpm you may get a complaint about user Neal does not exist or something like that. It is
because the original packager is not you. Do not worry.
Enabling the Components section of Synaptic will enable you to more easily locate the relevant section under which the required .srpm
is present in the repository.
If you are running from the commandline and want to capture all the messages of the build in a text file for easy reference, run this
command :
daniel - http://www.pclinuxos.com/forum/index.php/topic,109252.msg933761.html#msg933761
rpmbuild -ba pclos-nameofpackage.spec > ~/Desktop/nameofpackage.spec.log 2>&1
Install ccache. It will speed up your succeeding rebuilds. Archie -

[http://www.pclinuxos.com/forum/index.php/topic,109252.msg934066.html#msg934066
http://www.pclinuxos.com/forum/index.php/topic,109252.msg934066.html#msg934066}
When packaging Qt and KDE, when cmake is required and well, the dependency was not indicated on the spec and cmake is nowhere to
be found, you can find it on kdelibs-devel. Archie -
http://www.pclinuxos.com/forum/index.php/topic,109252.msg934066.html#msg934066
./autogen.sh is used as the first line of the build section to generate the configure and make files so a package can be built. Usually
used for software checked out of svn or git. Sometimes used for a package that isn't linking to the proper build libraries. Texstar -
{http://www.pclinuxos.com/forum/index.php/topic,112517.msg962671.html#msg962671
http://www.pclinuxos.com/forum/index.php/topic,112517.msg962671.html#msg962671 ]
Errors and Warnings

It would have to be the rarest of rare packages that builds without a single Error or Warning. Here is a list of some of them and wherever
known, how to deal with them.
file not found by glob

make: *** No rule to make target ìnstall'. Stop.
This is seen in case of packages where a separate subdirectory is created for config/build files. Commonly it is called build but the exact
name can be made out by reading the build log. This can be fixed by adding -C nameofsubdirectory to the make install macro in %install
section of .spec file. TerryN - forum .
Reading references
Repository and Sections and Mirrors
Basic PCLinuxOS packaging manual - http://www.montanalinux.org/files/RPM_Build_Manual_Rev2.pdf
Slightly updated version of above manual - https://dl.dropbox.com/u/32533806/Building_RPMS.tar.gz
Packaging software with RPM, Part 1: Building and distributing packages - http://www.ibm.com/developerworks/library/l-rpm1/
Packaging software with RPM, Part 2: Upgrading and uninstalling software - http://www.ibm.com/developerworks/library/l-rpm2/
Packaging software with RPM, Part 3: Accommodating software dependencies' - http://www.ibm.com/developerworks/library/l-rpm3/
How to make good RPM packages -
http://www.redhat.com/promo/summit/2008/downloads/pdf/Wednesday_130pm_Tom_Callaway_OSS.pdf
RPM Guide - http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html
Maximum RPM - http://www.rpm.org/max-rpm-snapshot/index.html
Macros - http://www.zarb.org/~jasonc/macros.php
Problems and issues with packaging - http://wiki.mandriva.com/en/Development/Packaging/Problems
Program Library HOWTO - http://tldp.org/HOWTO/Program-Library-HOWTO/index.html
Creating an RPM for a Java Application - http://javaworkshop.wordpress.com/2008/10/22/rolling-up-an-rpm-for-a-java-application/
Categories: Advanced Packaging
This page was last edited on 14 June 2018, at 10:36.

Usamos cookies en nuestro sitio web para garantizarle la mejor experiencia en él. Si sigue navegando por el sitio, acepta nuestro uso de las cookies. Saber más
Iniciar sesión en mi cuenta Buscar Español
Productos Recursos Asociados Servicio y soporte Empresa

/ Products / Para el hogar / Hard Disk Manager Suite / Visión general
Versión Inglés
Hard Disk Manager 15 Suite

La solución global para la protección,
mantenimiento y gestión integrales del PC.
Todas las soluciones imprescindibles para gestionar los discos
duros actuales
Gama completa de soluciones de copia de seguridad,

recuperación y partición
Migración rápida a nuevos discos duros, discos de estado sólido

(SSD) y máquinas virtuales
NEW Eliminación de datos segura en SSD
NEW Recovery Media Builder 3.0 integrado

Prueba gratuita
NEW Compatibilidad con Windows 10
39,95 € | Demo Documentación
(Inglés)
Hard Disk Manager 15 Suite
Características
Visión general Escenarios de uso Visita guiada Comprar ahora > Manual
completas Tamaño: 5.7 MB
Hard Disk Manager 15 Suite es el sistema y la solución de gestión de datos ideal para el usuario privado exigente.
Contactos
Copias de seguridad fiables, funciones de recuperación flexibles, herramientas de optimización, todo lo necesario para Recomendación
realizar particiones perfectas, el nuevo entorno de recuperación de Paragon, algoritmos de eliminación de datos de gran
fiabilidad y mucho más... todas estas características son las que convierten a Hard Disk Manager 15 en el complemento Hard Disk Manager
perfecto de su equipo durante todo su ciclo de vida. Professional (Inglés)
Copias de seguridad de
Partición y optimización
sistemas y datos
Hard Disk Manager 15 Suite gestiona de manera El motor de partición de alto rendimiento de Paragon
automática las tareas de copia de seguridad–, ya se trate permite gestionar cualquier tarea de partición de discos
de copias de seguridad de todo el sistema, de duros y realizar un uso óptimo del espacio disponible en
particiones individuales o solo de archivos específicos. los mismos. Gracias a la alineación automática de
Gracias a las tecnologías de copia de seguridad particiones* siempre podrá obtener el máximo
Todo lo que necesita para la
incrementales y diferenciales, las copias de seguridad rendimiento de los SSD y los discos duros con sectores
gestión profesional de
continuas del sistema resultan extraordinariamente de 4K y volúmenes RAID. sistemas y discos duros.
eficaces con Paragon Hard Disk Manager. Con una copia Saber más
de seguridad completa de todo el equipo seguida de El modo avanzado pone a su alcance precisas
copias de seguridad incrementales periódicas, el último herramientas de análisis y reparación que le permiten
estado de su PC se mantiene a salvo en todo momento. solucionar problemas de arranque o analizar el estado del
Los nuevos contenedores de copias de seguridad en disco duro.
formato pVHD aceleran la realización de copias de
seguridad en redes (como las redes NAS).
Migración y clonado de
Por cierto: puede utilizar el asistente de complementos sistema uniformes
de archivos para añadir archivos de máxima prioridad a Con el nuevo asistente de migración avanzada de Hard
las copias de seguridad existentes fuera del proceso de Disk Manager, trasladar el sistema es un juego de niños.
copia de seguridad general. Si desea aprovechar el rendimiento que ofrece un SSD
rápido, puede trasladar el sistema existente a un soporte
de almacenamiento de ese tipo. También puede separar
Paragon Recovery Medium los datos del usuario y del sistema entre sí y distribuirlos
entre varios discos duros de destino para aprovechar al
Si su sistema operativo no arranca, puede iniciar su máximo el espacio de un SSD. Si necesita un clon virtual
equipo con el entorno de recuperación de arranque de de su sistema Windows, el asístente para ajuste P2V
Paragon y cargar una copia de seguridad existente, del sistema operativo le permite adaptarlo a los
salvaguardar los datos importantes o corregir errores de hipervisores convencionales (como VMware Workstation,
arranque. Con el nuevo Recovery Media Builder 3.0, Oracle Virtual Box o MS Hyper-V). Y si desea probar
crear un entorno de recuperación personal resulta nuevo software, dispondrá de un sistema de prueba virtual
extremadamente sencillo y flexible. Y gracias a la en un abrir y cerrar de ojos. ¿Solo necesita una copia
tecnología WinPE más reciente, el uso del entorno de exacta del disco duro o de la partición? Puede realizar el
recuperación también resulta muy intuitivo. clonado de discos duros o particiones sin mayor
¿Se encuentran sus copias de seguridad en una unidad problema.
de red? Si es así, utilice las opciones avanzadas y añada ¿Tiene un equipo o una versión de Windows nuevos?
sin más dilación la configuración de red y la unidad de ¿Por qué no mantener una versión virtual del sistema
durante la creación del soporte de recuperación. anterior a la que recurrir en caso de necesidad?
Más información sobre el nuevo soporte de
recuperación (Inglés) >>
Eliminación de datos fiable
Recuperación y adaptación Sus datos privados le pertenecen exclusivamente,
incluso si va a desechar un disco duro antiguo. Pero un
¿Qué ocurre si algo falla? profesional es capaz de recuperar datos que haya–
Con Hard Disk Manager, la seguridad siempre estará de aunque el disco duro se haya destruido físicamente.
su lado. Restaurar copias de seguridad existentes, Sin embargo, gracias a la función de eliminación de
incluso en hardware diferente, no es un problema datos de Hard Disk Manager puede liberar espacio de
gracias a los asistentes integrados. Le proporciona una almacenamiento y asegurarse de que los datos se
flexibilidad total y permite restaurar el sistema íntegro, eliminan de forma definitiva. Solo tiene que utilizar los
particiones específicas o archivos concretos. eficaces algoritmos de eliminación de datos de Paragon
Universal Image Mounter (UIM) le otorga acceso o desarrollar un algoritmo propio.
completo a los archivos seguros en todo momento. Solo
tiene que asignar un archivo de copias de seguridad en Ahora, Hard Disk Manager 15 le ofrece funciones de
una unidad de red y podrá acceder a los archivos que eliminación de datos de SSD que permiten borrar
contenga como si se encontraran en un disco duro datos de SSD de forma segura sin acortar su vida útil.
normal.
* La alineación automática de particiones está siempre activa durante las operaciones de creación/movimiento; activa durante las operaciones
redistribución del espacio libre/cambio de tamaño solo cuando esté afectado el límite izquierdo de la partición; y activa durante las operaciones de
copia/restauración solo con cambio de tamaño.
PRODUCTOS PARA WINDOWS TECNOLOGÍAS QUIÉNES SOMOS ¡SUSCRIBIRSE A LAS NOTICIAS!

Hard Disk Manager Migrate OS to SSD Acerca de la empresa ¡Aquí podrá suscribirse a los boletines de
HFS+ for Windows GPT Loader Noticias (Inglés) Paragon Software!
Partition Manager (Inglés) NTFS-HFS Converter (Inglés) Contacto (Inglés)
Drive Copy (Inglés) Sala de prensa
Protect & Restore (Inglés) Paragon Blog (Inglés)
SERVICIOS Regional blog posts
PRODUCTOS PARA MAC Asistencia técnica SUSCRIBIRSE A LAS OFERTAS
NTFS for Mac Programas beta (Inglés) LEGAL ESPECIALES
Camptune X Base de conocimientos (Inglés) Nosotros ¡Ofertas de descuento exclusivas para nuestras
extFS for Mac Foro de asistencia (Inglés) Condiciones (Inglés) aplicaciones (software) y las aplicaciones
(software) de nuestros socios!
Hard Disk Manager for Mac Declaración de
confidencialidad
Suscríbase al boletín
ASOCIADOS
Paragon Partner Program
Paragon Affiliate Program
Log in
Update Your PCLinuxOS

This page deals with the method of keeping your PCLinuxOS system up-to date.
Main page
Contents [hide]
Recent changes
1 Introduction
Random page
Help 2 Preparation
3 Locating Synaptic
Tools 4 Running Synaptic
What links here 5 Note
Related changes
Special pages
Printable version
Introduction
Permanent link PCLinuxOS is a Linux distribution that follows the system of rolling updates. It means that you do not need to reinstall each time an update is
Page information
released and when fully updated you have the most current system. However it is very important to update properly to make sure that your
system does not break.
* It is recommended that you do a proper system update as outlined below once every week or two.
* Leaving a long gap between system updates may cause breakdown. Do not wait more than 60 days to update
your system.
[ PCLinuxOS DOES NOT AUTOMATICALLY UPDATE KERNELS;ONE SHOULD INSTALL NEW KERNELS MANUALLY FROM SYNAPTIC.]
Preparation
PCLinuxOS updates are delivered over the internet. A working internet connection is needed. Broadband connections are preferred because
sometimes the updates can be of the order of hundreds of MBs. So before proceeding with the update, make sure that you have a working
internet connection.
Locating Synaptic
Synaptic is the software that manages the task of downloading and installing updates for your system. The software on your system is
delivered as packages and hence Synaptic is also called package manager. You can launch it by any one of the following 3 methods:
* By clicking on Synaptic Package Manager icon in the taskbar near the left hand lower corner of your
screen.
* By going to PC Menu (Also called Kickoff Application Launcher) at the left hand lower corner of your
screen > Applications > Software Centre > Package Manager.
* By typing 'synaptic' into a terminal.
Running Synaptic
Since updating your system might require making changes to the system as a whole or changing important system files, Synaptic needs the
privileges of super user or root. Hence while starting up Synaptic, you need to enter the root password first. link title
As soon as Synaptic starts, it scans your system for existing software and gets ready.
Now you need to reload the package information to become informed about new, removed or upgraded
software packages. Click on 'Reload' button.
A window labelled 'Downloading package information' will come up and show the progress of this
operation. Once the download is complete, Synaptic will do another scan and get ready for the next step.
Now click on 'Mark All Upgrades'.
You will get another window with the prompt "Mark additional required changes?'. Go through the list and
click on 'Mark'.
Now click on 'Apply'. You will be presented with another summary window. After going through the list,
click on 'Apply' to begin the actual process of downloading and installing updates.
You can expand To be upgraded and To be installed sections by clicking on the small triangle before each
line.
Once the process is complete you may see another window showing some output. Some of the changes
effected by Synaptic might require you to either log-off and log-in again or rarely in case of kernel
update etc require you to reboot which would be shown in this window. After this you may close Synaptic.
If required, as mentioned above, log-off/log-in or reboot.
That completes your system update.
Note
* In case Synaptic gives a prompt such as "Not able to retrieve all packages, continue anyway?" DO NOT
click Yes. Say 'NO and try updating sometime later. This might be because the repositories are being
updated with new software themselves and only after this process is complete, you should update your
system. If the message continues to appear even after a day, report the issue to the forum .
* DO NOT USE apt-get update and apt-get upgrade from the command line. This has never been the recommended
way. If you insist on using command line, the correct procedure is apt-get update and apt-get dist-upgrade.
* Once a new ISO is produced and made available to the public, we no longer test upgrading from older ISO
releases. This does not mean, though, that previous releases should not be used. On the contrary, there is
no need to reinstall PCLinuxOS unless you wish to have a fresh install, due to PCLinuxOS being a "rolling"
release distribution.
Category: HowTo
This page was last edited on 26 July 2018, at 12:50.

This website uses cookies to ensure you get the best experience on our website. By continuing to browse the site, you agree to our use of cookies. MORE INFO › ›
Overview How it Works Features FAQ Free Version Limitations Resources 
Menu
 Search
 MyParagon
 English
 / Products for Home Users / Microsoft NTFS for Linux
Microsoft NTFS for Linux by Paragon Software


Download Buy now
Full read/write access to NTFS and HFS+ volumes!

Microsoft NTFS for Linux by Paragon Software is a unique combination of drivers for the NTFS and
HFS+ file systems accessible from a Linux environment.
“Paragon’s driver technology clearly delivered the performance we demand for our ReadyNAS products.”
Matt Pahnke, Senior Product Marketing Manager,

NETGEAR Storage
Paragon partnering with NETGEAR
Easy to Install and Uninstall
 Simply run the assistant scripts (install.sh and uninstall.sh scripts) that will perform
all the necessary operations to build the driver, install it, and deactivate and remove
it from the platform.
High Performance
The Paragon tool boosts your performance by opening direct access to partitions
you had difficulties with accessing previously from Linux. The transfer rate is the
same for native Linux file systems and in some cases even better.

Full Access to NTFS and HFS+ Volumes
 Rapid and transparent read and write access to NTFS/HFS+ volumes from Linux. Use
HFS+ file system and its native journaling support for better file system integrity,
when transferring files between Linux PC and Mac.
Additional Utilities
Microsoft NTFS for Linux by Paragon Software allows you to format any volume as
NTFS or HFS+, check the formatted volumes for integrity and fix errors. 
Free Version

Microsoft NTFS for Linux by Paragon Software has also limited version that is free of
charge and covers common usage scenarios. Try now ›
Choose the Professional version for professional features, highest performance and
premium support.
Expertise You Can Trust

Paragon Software Group has been providing market-proven reliable solutions since

1994, helping 8 million customers achieve maximum productivity. We keep an eye on
the IT industry, its news and trends and regularly supply you with product updates
and enhancements.
Visit your personal MyParagon account, where we select and regularly publish the
latest news and best deals!
OEM and Embedded Solutions

Microsoft NTFS for Linux by Paragon Software is a File System Link driver. Our FSL technology solves
incompatibility issues between various file systems and popular operating systems. With FSL support
for all popular file systems embedded into modern digital devices, consumers can enjoy issue-free
platform interoperability. In search of a solution for your product?
Interested? Call us!

US: 1-888-347-5462
Europe: +49 (0)761 59018-202
Contact us!
Many Paragon products come with free technical support. All of our
Customers are entitled to a free 30-day upgrade if a new version appears
within 30 days of product purchase. Should you have any questions about
the installation or configuration of our software, do not hesitate to contact
our Support Team via MyParagon Customer Portal.
Run the Check Volumes operation
Features
Features Benefits
New Features
Support for Linux kernel versions 2.6.36 up to 4.12.x.

NEW Supports Linux Kernels
Automatic driver rebuild for newer supported kernels with
up to 4.12.x
DKMS library.
Supported NTFS features (see also “Compatibility”):

NEW Read support of new
NTFS versions 1.2, 3.0, and 3.1 (Windows NT 4.0, 2000, XP,
NTFS system compression 2003, Vista, 7, 8.1, 10, Server 2016);
methods on Windows
Compressed files support;
10/Server 2016
Sparse files support.
NEW Stability improvements Improved driver behavior in case target storage could be
in unsafe storage removal detached unexpectedly to minimize possibility of file system
scenarios issues.
NEW Minimized file system Added single ‘ufsd’ utility instead of standalone mk*fs and
utilities package size chk*fs utilities, which are hardlinks to ‘ufsd’ utility.
NEW Improved Updated automounting script for better recognition of
automounting script volume names with spaces. (Professional version only).
Key Features
Improved HFS+ support Supported HFS+ features (see also “Compatibility”):

(including compatibility with Full support for the native HFS+ journal.
macOS Sierra HFS+)
Implementation of changes into driver and file system

utilities to provide a more user-friendly behavior by default,
Improved support for very without the need for additional options, when working with
large volumes (16+TB) very large volumes (16TB and larger). NTFS&HFS+ for Linux
confirmed to work on 20 TB physical and 25 TB virtual
volumes in the Paragon lab.
Use the ‘discard’ mount option to enable TRIM support on

Improved TRIM/discard
the SSD storages mounted by Paragon driver to improve
support for SSD storages
performance.
Transparent read/write access Kernel modules provide support for both NTFS and HFS+ file
to NTFS/HFS+ volumes systems.
32/64 Bit architecture support Both x86 and x86-64 CPUs are supported.
Extended SMP support Support for SMP kernels (multiprocessor systems).
Share your data over network Share volumes mounted by NTFS&HFS+ for Linux via SAMBA.
Low CPU load during data Reduced CPU load and memory consumption.
transfers
Automatic NTFS/HFS+ volumes Mount any NTFS/HFS+ volumes like native Linux ones
mounting on Linux platform automatically.
No file or volume size There are no limitations to maximum file and volume size
limitations (but within Linux kernel and NTFS/HFS+ limitations).
File and folder names in national languages, including Asian.

Support of non-Roman
Codepage for filename translation is specified via mount
characters and languages
options.
Additional Utilities
Compatibility
Supported Technologies
Frequently Asked Questions

Questions Answers
NTFS File System General
NTFS is an acronym for New Technology File System. NTFS

was first released with Windows NT. It is much more
modern, stable and reliable than FAT or FAT 32. This file
system was designed for use specifically with Windows OS. It
What is NTFS File System?
supports long file names, huge disk partitions and files, full
security access control, the ability to recover files/directories
and its structure in the event of hardware failure and many
other features.
Yes. The NTFS File System is a replacement for the FAT (File
Allocation Table) and HPFS (High-Performance File System)
Is NTFS File System better than file systems. It gives many advantages over the other file
FAT or HPFS? systems such as the ability to restore files/directories and
their structure in the event of hardware failure, improved
security, support of huge files/partitions, etc.
There are three versions of NTFS File System: 1.2, 3.0 and 3.1.
Each of these versions is used in different Windows OS and
has additional features.
Is NTFS File System the same NTFS version: v1.2; v3.0; v3.1 and the respective Windows
in every version of Windows? version: Windows NT 4.0, 2000, XP, 2003, Vista, 7, 8.1, 10,
Server 2016.
Note: The version 1.2 is also known as 4.0, the version 3.0 as
5.0 and the version 3.1 as 5.1.
NTFS Volumes
HFS File System
UFSD (Universal File System Driver) General
NTFS for Linux Software
System Requirements and Performance Issues
Installation
Maintenance
OEM / FAQ
Glossary
Mount
Mounting is the process of connecting volumes to the operating system. Once completed, the
operating system, any application or user can access contents of the volume in standard ways.
For Windows, the standard way means the volume is assigned a ‘drive letter’. For Linux, it means
the volume becomes available under one of its tree nodes.
Kernel version
Sparse files
Codepage
SMP
Journaling file system
DKMS
Free Version Limitations

FREE TO TRY BUY NOW ›
Key Features
Supported NTFS features
Supported HFS+ features
Additional utilities
chkntfs – check NTFS partition

integrity and fix errors

mkntfs – format any partition

as NTFS under Linux

chkhfs – check HFS+ partition

integrity and fix errors

mkhfs – format any partition as

HFS+ under Linux

DKMS library support 

Automatic NTFS/HFS+ volume
mounting

Free one year update

(New kernel versions support)

Free 30 days upgrade 

Support Complimentary
Self Support
support
Resources
Free Version Download Microsoft NTFS for Linux by Paragon Software
Download Microsoft NTFS for Linux by Paragon Software

Product Documentation
User Manual
WE OFFER OUR WEBSITES STAY CONNECTED
Products for Home Users Paragon drivers Copyright © 1994–2018

Subscribe by email Paragon Technologie
Products for Business Knowledge base
GmbH.
Users Support Terms of Use | Privacy
 Contact us
Backup solutions Forum Policy
Apple, the Apple logo, iOS, iPhone,
Technology Solutions iPad, iPad Pro, Mac, MacBook,
Blog MacBook Pro, macOS and iMac are
trademarks of Apple Inc., registered
All Products in the U.S. and other countries.
Windows® & the Windows® Logo are
trademarks of Microsoft Corporation,
registered in the U.S. and other
countries.
Puppy Linux Wiki Forum Blog Newsletter
Overview and Getting How to download Puppy Long-Term-Supported Manual-English

Started Linux Puppy
CD, Help, Warranty
Download Latest How NOT to install Puplet for special
Release Puppy Linux features More information
Puppy Linux 5
Manual-English
Lucid Puppy - Nothing
but Praise: Learn
How to Use the Manual and Download Puppy | How to Run Puppy | Saving and Installing
about the new features
to Hard Disk | Preparing the Hard Disk | Installation-Frugal | Installation-Full | Internet
of the first Puppy 5,
Connection | Setup EMail | Setup Devices (Printer, Keyboard)
Lucid Puppy.
The links above are parts of a Puppy Linux manual in English provided and - Dedoimedo
updated by volunteers.
This site is tablet-ready.
The newest installation tutorial in PDF is about Lucid Puppy 5.2.8, prepared
Support this site:
by Md. Hanbala in Arabic, click here to get it, or click to get English or
Bahasa. Note that the installation method is very similar among Puppy Linux
distros.
There is a book by Grant Wilson about Puppy 4.2 downloadable as PDF,

click here. Pay attention to the NOTE below about version numbering
(naming pup_xxx.sfs was changed in version 4.3.1).
A good tutorial for USB install of Puppy Linux 4.30 is made available as PDF
(English, also Italian, Spanish and Portuguese) by Alex Gotev for Linux Day
09 - GALLUG, October 24, 2009, Novara, Italy.
NOTE that the version number used in the manual below is 4.00, and version
numbering is shown as 400 (when used with filenames). You should replace
this with the latest version number, like 4.21 or 421 (Use the number with
filenames, like pup_421.sfs).
IMPORTANT: With version 431, use dash instead of underscore, like pup-
431.sfs. Starting April 23, 2011, long filenames are used for puppy.sfs in
Puppy Linux, and there is a file /etc/DISTRO_SPECS that helps to identify the
matching puppy.sfs however it is named (i.e. this helps the start-up become
fool-proof.).
Thanks to forum members Oliver (oli), Rod (cryftybytes), Jay (puppyluvr) and
Bill (BillWho?).
How to Use the Manual and Download Puppy

Back to Top
Introduction
This manual will appeal to Linux beginners and Linux users, who would like to
become acquainted with Puppy Linux. This manual summarizes the most
important information for Puppy beginners and explains the first steps with
Puppy.
How to use the manual:
Menu entries and buttons are set in "". Sub-menus are separated by vertical
lines. Example: "Menu | Shut Down | JWM restart" means, that you first click
on the button "Menu", than (at the appearing menu) on the headword "Shut
Down" and finally on the headword "JWM restart".
In the manual the letter x is used as a substitute symbol for a number. For
example /dev/hdax means that you have to write /dev/hda1, /dev/hda2 or
/dev/hda3 - just use what suits your computer.
With the term "shell" the program "Menu | Run | Rxvt terminal emulator" is
meant.
How to get Puppy
You can get Puppy Linux from ibiblio.org. Save the current release pup-
431.iso on your harddrive. The filesize is about 105 MB.
To make sure that you downloaded a genuine original file, you can compare
the checksum of the ISO file with the associated file pup-431-md5sum.txt.
(right-click to download this file as well).
Within Linux:
Open a shell and change into the directory, in which you stored the two files.
Enter the following command:
md5sum -c pup-431-md5sum.txt
This will run the md5sum program on your .iso file and compare it with the
value in the .txt file. You should get an OK. If not you need to download the
iso again.
Within Windows:
Download the DOS-Program md5sum.exe and save it in the same directory

where you saved the downloaded files.
To open a DOS-Box click on "Start | Run". This opens an input window, into
which you enter the following command:
cmd
Now you get a DOS-Box. Change into the directory in which you stored the
two files, e.g. c:/pup431. Enter these commands:
c:
cd pup431
dir
Now you should see the Puppy-files (make sure that you copy md5sum.exe to
this same location). Next, enter the command:
md5sum.exe -c pup-431-md5sum.txt
You should get an "OK".
Subsequently you burn the ISO file (in our example, pup-431.iso) on CD. To
burn an ISO file on CD, consult the manual of your CD-burning software.
Beginners sometimes copy the ISO file simply as a data-file on CD, which
doesn’t work. Usually the CD-burning software has a special menu option for
burning an ISO file on CD. You can verify whether you burned the CD
correctly by looking at the CD with the file manager (e.g. Windows Explorer). If
you see files as "initrd.gz" or "vmlinuz" everything is OK. If you see the file
"pup-431.iso" (an ISO filename) this is incorrect.
A small and excellent CD burning program for Windows is BurnCDCC - just

download, unzip to a folder in Windows and click on burncdcc.exe (do not
forget to choose low burning speed of 4X for CD or 1X for DVD).
Tip:
Create a second, identical Puppy CD as a backup copy, in case the original

CD becomes corrupted.
Back to Top
How to Run Puppy

Back to Top
A great advantage of Puppy Linux is that Puppy doesn't have to be installed.

You can run Puppy directly from the CD, without affecting your operating
system. Alternatively you can install Puppy on a harddrive or a USB stick.
How to run Puppy the very first time
First you must set up the boot sequence in the BIOS. If you do not know how
to get into the BIOS-setup, consult the computers manual. Usually you press
one of the following keys immediately after switching on the PC: ESC, one of
the function keys F1 to F12 or the delete key. At the BIOS-setup you change
the boot sequence so that the CD-ROM drive is first and the harddrive is
second. Close the BIOS-setup and store the settings.
The PC then usually reboots. Immediately insert the Puppy CD into the CD-
ROM drive. If you are too slow your old operating system starts. In this case
keep the CD inserted in the CD drive and start the PC again.
Now Puppy should start. During the starting procedure you are requested to
choose from a few options such as mouse, country or timezone. The choice
for mouse is usually automatic, and you can choose "ps2" even if you have
no attached mouse to yout laptop. For other questions, navigate with the
cursor keys downward to your choice. Then strike the return-key. Thereafter
a further window (Puppy video Wizard) appears, "Xorg" is already highlighted.
Press the return-key. Wait some seconds till the next window (Puppy video
Wizard) appears. There you navigate with the cursor keys to your screen
(LCD panel = flat screen, CRT = standard monitor) and your choice
resolution. Then strike the return-key. After some seconds the Puppy desktop
appears.
Should Xorg not work on your computer, choose Xvesa. A few seconds later,
the Puppy desktop will be displayed using a resolution of 640 x 480 pixels. If
you wish to use an even higher resolution choose e.g. 1280x1024x24 and
click on the button "Change".
After some seconds the Puppy desktop appears again. Click on the OK-
button.
Unfortunately, with Xvesa you will have to adjust the keyboard layout if you
are not using a US keyboard.
If your PC has 256 MB RAM, Puppy will be loaded completely into RAM (or
mounted to the CD/DVD disk if your PC lacks RAM). Your old operating
system is not touched, so that you can look safely at Puppy Linux. Now you
can take the CD out of the CD drive, unless you do not have enough ram, in
which case Puppy will not allow the CD to be ejected.
If you terminate Puppy you are asked whether you want to store the settings
(and your personal files) in two ways (you can change between the options
with the tab-key and then and press the return-key):
SAVE TO FILE - Save to a file named pup_save.2fs on a hard disk or

USB flash drive.
SAVE TO CD - Save to the same CD or DVD where you booted from (this
requires that the Puppy CD or DVD was burned in a way that files can
still be added to it).
DO NOT SAVE - Exit Puppy without saving anything.
If you would like to store the settings (and your personal files) you are asked
on which hard disk or USB flash drive this should happen. If saving to
pup_save.2fs, choose at least 128 MB.
Boot Options
When Puppy boots it offers you some boot-options. If you do not enter
anything, Puppy is loaded after some seconds into RAM. When starting,
Puppy automatically looks for a previously stored pup_save.2fs-file. If this file
doesn't exist yet, you will be asked again the same boot-up questions.
With the boot-option
puppy pfix=ram
you have the option to start Puppy into RAM without your pre-saved-settings
and without your personal files even if a pup_save.2fs-file already exists. This
boot option is very useful and is used in this manual a few times. The other
boot options are normally not needed.
Back to Top
Saving and Installing to Hard Disk

Back to Top
How to save the settings and your personal files
So that Puppy can store all settings and your personal data, a file named
pup_save.2fs is saved. I recommend a size of 512 MB for this file. This is big
enough for further programs and can be backed-up on CD-ROM (note: if you
want to backup the file on a USB stick, it must have a storage capacity of 1
GB). Puppy can store the pup_save.2fs-file on many different filesystems
including FAT and NTFS as used by windows. (note: USB sticks and external
harddrives are usually formatted with a FAT32-filesystem, so that they can be
used without problems). Windows XP-users normally have a NTFS-filesystem
only. There are two options for you to store the pup_save.2fs-file as well:
(1) Save the file on an external harddrive or USB-stick.
(2) Make the NTFS partition smaller and create one or more further partition
with FAT32-filesystem and ext2/ext3-filesystem.
If you intend to use Puppy durably you should select the second alternative.
This alternative has many advantages.
How to install Puppy
If you prefer not to keep booting Puppy from CD-ROM, you can install Puppy
to a hard disk drive. This requires some preparation.
Hard drives, partitions and filesystems
A hard drive can be divided in one or more partitions. If you create several
partitions on a harddrive, each partition appears like a hard drive in the
operating system. In other words: although you have only one harddrive in
your PC, you will see several (virtual) hard-drives with Windows or Linux.
Windows designates the harddrives (as well as the floppy disk drive and
CD/DVD drive). In Windows they will be identified with letters. Usually A
designates the floppy disk drive, C the harddrive (first partition), D the CD-
ROM drive, E the harddrive (second partition), F the harddrive (third partition)
and so on. Each partition has its own file system, Windows normally uses
NTFS (Windows XP) or FAT32 (Win98, Win95).
With Linux the (first) harddrive is adressed as /dev/hda or /dev/sda. If your

PC has a second harddrive, it is adressed as /dev/hdb or /dev/sdb. The
partitions are sequentially numbered, starting with one. The partitions of your
harddrive are adressed as /dev/hda1 (corresponds to the Windows C-
partition), /dev/hda2 (corresponds to the Windows E-partition), /dev/hda3 and
so on. Linux can work with different file systems such as ext2, ext3 or
ReiserFS. These file systems are not readable by Windows. In addition Linux
can work with Windows filesystems too.
Back to Top
Preparing the Hard Disk

Back to Top
Defragment your hard disk
Before creating new partitions on your hard drive, you should defragment the
drive so that all data is stored at the beginning of the existing partition. Here
is how to do it:
Start up Windows.
First, backup your files to CD-ROM, DVD, or an external hard drive. Also
remember to backup your Internet link collection (Favourites) and your e-
mails. If your data is encrypted, it is advisable to decrypt it before backing it
up. This protects you from data loss because modifying hard drive partitions
always carries the risk of data loss.
Next, start the Disk Defragmenter program under Windows. The program is
located at "Start | All Programs | Utilities | System Programs | Disk
Defragmenter". Select hard drive c:\ and click the "Check" button.
Click the "Defragment" button. Depending on the size of the partition and the
amount of data on it, this process can take a long time (over an hour). If you
have very large amounts of data, you can speed up this process drastically
by deleting your files after you have backed them up (see the previous item)
and restoring them once you are done with the modifications. In this case,
please make sure beforehand that your backup is readable, otherwise there
will be wailing and gnashing of teeth.
Click the "Close" button.
There is now space on the harddisk for additional partitions.
Shut down Windows.
Creating partitions
Now you should plan the layout of your hard disk partitions regarding file
system and size. I recommend creating three or four partitions in addition to
the Windows partition. The following example assumes you have exactly one
Windows partition (drive letter C). Your hard disk would then look like this:
First partition: NTFS or FAT32 (Windows)

Second partition: ext2 or ext3 (this is where Puppy will be installied to)
Third partition: Linux swap (for page files)
Fourth partition: FAT32 (for exchanging data between Windows and Linux)
Optionally, a fifth partition: ext2 or ext3 (Linux)
Windows will continue to reside on your first partition with all its programs and
data. The second partition (recommended size about 1-2 GB) has a Linux file
system (ext2 or ext3). This is the partition Puppy will be installed to. The third
partition (exactly as large as your computer's memory) will be a Linux swap
partition that Linux can ... well, swap files to. The fourth partition has a FAT32
file system, which is recognized by both Windows and Linux. This partition
(recommended size about 5 GB) is used for files that you want to access from
both Windows and Linux. If you want to manage large amounts of data under
Puppy (e.g. music collection, pictures), you should create a fifth partition with
a Linux file system (ext2/ext3). This file system cannot be accessed from
Windows and is meant for Linux only.
To create the partitions, proceed as follows:
Start Puppy Linux from CD with the "pfix=ram" boot option.
Start the Gparted program: "Menu | System | Gparted partition manager".
First, shrink your Windows partition (NTFS file system). To do this, select the
Windows partition /dev/hda1.
Click the "Resize/Move" button.
Reduce the "New Size" value until the "Free Space Following" field shows
enough free space following for the new partitions. My test computer's hard
disk has only 3 gigabytes; I am using half of that for the mew partitions. You
probably have a much larger hard drive so your partition sizes can be
increased accordingly.
Then press the "Resize/Move" button.
Next, select "Edit | Apply All Operations" from the menu.
In the dialogue box that comes up, click the "Apply" button.
Click the "Close" button. You now have an "unallocated" area on your hard
disk.
Select the line saying "unallocated" and click the "New" button.
Enter the size of the second partition in the "New Size" field. This is where
Puppy Linux will be installed to. I recommend a size of 1 to 2 gigabytes (i.e.,
1024 to 2048 MB). Select ext2 from the "Filesystem" box and click "Add".
Again select the line saying "unallocated" and click the "New" button. (You
can see where this is going.)
Enter the size of the third partition in the "New Size" field. This partition is to
hold Linux's swap files as a Linux swap partition. You should make it as large
as your computer's memory (RAM). With my test computer, this amounts to
128 megabytes (MB). Select linux-swap from the "Filesystem" box and click
"Add".
Again select the line saying "unallocated" and click the "New" button.
Enter the size of the fourth partition in the "New Size" field.This partition is
meant for shared access to files from Windows and Linux. I recommend a size
of about 5 gigabytes (5120 MB). Since my test computer does not have a
large enough hard disk, I am using 396 megabytes (MB) as an example.
Select FAT32 from the "Filesystem" box and click "Add".
Hint: if you want to create additional partitions (e.g., for very large files under
Linux), repeat the process outlined above accordingly. In this case, you may
have to create so-called logical partitions. Please consult additional sources if
you are unsure about how to do that.
To actually write the changes to disk, select "Edit | Apply All Operations" from
the menu.
In the dialogue box that comes up, click "Apply".
Exit GParted.
Back to Top
Installation-Frugal
Back to Top
There are different ways to install Puppy:
Frugal Installation (Pupy CD image on hard drive)
Universal Installer
Manual Install
Other Ways
Full Installation
Installation to a USB flash drive
Installation to a CF card
Frugal Installation is recommended if you have 256 MB RAM or more. If you

have less than 256 MB RAM you should choose Full Installation.
Frugal Installation using Puppy Universal Installer
A Frugal Installation copies the image from the Puppy CD to the hard drive. At
bootup, Puppy is loaded into your computer's memory (RAM) just as it is
when you boot Puppy from CD, however, loading it from a hard drive is much
faster. This way, Frugal Installation combines the advantages of booting from
CD-ROM (protection from malware) and a hard drive bootup (speed).
Moreover, upgrading to a new Puppy version is very simple - all you have to
do is replace some files.
Start "Menu | Setup | Puppy universal installer". Choose which medium Puppy
should be installed to. In this example, I chose the internal hard drive.
If you have several hard drives, select one.
Next, click on the button next to the partition that you want Puppy to be
installed to - /hda2 in this example.
In the dialogue box, click "OK".
You now have to decide whether you want a "Frugal" or a "Full" installation. In
our example, click on the "FRUGAL" button.
Now you change the installation directory. Just click on the "OK" button.
The files are now copied from CD to the hard drive.
The installation is finished. In the next two dialogue boxes, click "OK".
Since you now have two operating systems on your computer (Windows and
Puppy Linux), you need a boot loader. The boot loader is the first program
executed after switching the computer on. It enables you to specify which
operating system should be started up. If Windows was the only operating
system on your computer up to now, you do not have a boot loader. Start the
installation of the boot loader GRUB with "Menu | System | Grub bootloader
config".
Select "simple installation" and click "OK".
In the next dialogue box, select "standard" and click "OK".
Now you have to specify where the GRUB boot loader should store its files.
These can only be written to a Linux file system partition. Thus, please
specify one of the Linux (ext2 or ext3 file system) partitions you created
(/dev/hda2 in the example). If you do not have a Linux file system partition
yet, you need to create one.
Now you have to specify where the GRUB boot loader itself should be
installed to. Select the Master Boot Record "MBR" and click "OK".
In the next dialogue box, click "OK".
The installation is complete. What remains to be done is to configure the

GRUB boot loader so that Puppy Linux can be booted. This is how to do it:
Open the file "menu.lst". You will find this file in the /boot/grub directory of the
partition you installed the GRUB files to (/dev/hda2 in our example). For Linux
newbies, I include detailed instructions on how to find and open this file. More
advanced users can skip ahead to where menu.lst gets edited.
Start "Menu | Filesystem | Pmount mount/unmount drives" and click on the

button "MOUNT" next to "/dev/hda2".
The button changes to "UNMNT".
Start "Menu | Filesystem | ROX-Filer file filemanager".
Right-click with the mouse and choose "Window | Enter Path".
Enter the following path next to "Goto: /mnt/hda2/boot/grub/
You are now at the folder /mnt/hda2/boot/grub/
Use the right mouse button to click on the file called "menu.lst".
From the context menu that pops up, select "File menu.lst | Open As Text".
You can now see the contents of the menu.lst file.
Edit the file at this point:
title Puppy Linux 4.00 frugal (on /dev/hda2)

rootnoverify (hd0,1)
kernel /puppy400/vmlinuz pmedia=idehd psubdir=puppy400
initrd /puppy400/initrd.gz
(Notice: depending on what medium you boot from, you have to set the
pmedia parameter to one of usbflash, usbhd, usbcd, ideflash, idehd, idecd,
idezip, satahd, scsihd or scsicd. If you did not install the GRUB files to the
/dev/hda2 partition, you need to change the rootnoverify parameter as well -
partition number and Linux drive letter minus one, so if the GRUB files are on
/dev/hdb3 (partition 3 in second drive hdb), make it "rootnoverify (hd1,2)".)
With the changed line, the grub entry should now look like this:

"Comment out", i.e. put a number sign (#) before the lines:that are no longer
needed, like the following extra entries automatically written by Grub:
# Linux bootable partition config begins

title Linux (on /dev/hda3)
root (hd0,2)
kernel /boot/vmlinuz root=/dev/hda3 ro vga=normal
# Linux bootable partition config ends
root (hd0,3)
Save the file by selecting "File | Save" from the program's menu. Exit the text
editor.
Close the ROX file manager.
Click on the button "UNMNT" next to /dev/hda2.
The button changes to "MOUNT".
Click on the button "QUIT".
Exit Puppy and reboot the computer: "Menu | Shutdown | Reboot computer".
When you reboot the computer, you will be asked whether you want to save
the "session" (i.e., all the configuration changes you made). Hit Return to
select the entry "SAVE TO FILE", which is already highlighted.
Confirm the next dialogue (Warning) by hitting Return.
In the next dialogue, select the "hda2" partition with the cursor keys and press
Return.
Now. you will be asked, if the file should get a special filename. Just press
Return.
You will be asked whether you want a normal (unencrypted) or an encrypted

save file. Select "NORMAL" with the cursor keys and press Return.
The next dialogue lets you choose a size for your save file. A file size of 512
megabytes is usually sufficient. You can increase (but not decrease) this size
anytime from within Puppy. Pick the desired file size with the cursor keys and
press Return.
In the next screen you see a summary. Choose "Change Folder" and press
return.
Next, you enter "/puppy400" as subfolder and confirm with return.
Again a summary is shown and if everything seems to be ok, choose "Yes,

save" with the arrow keys, then press return.
Please be patient while the file is created.
Next you will be asked if Puppy 4.xx should test for serial devices at each
boot. Choose ""No" with the arrow keys and confirm with return.
Now you decide wether the system file pup400.sfs should be copied over to
the harddrive. Choose "Yes" with the arrow keys and confirm with return.
Last not least the computer restarts automatically. Remove the Puppy CD
from the drive before the shutdown is complete. Upon reboot the boot loader
will show up. Choose ""Puppy Linux 4.00 frugal (on /dev/hda2)"" with the
arrow keys and confirm with return.
Manual Installation
To be able to use this option, a boot loader has to be installed on your

computer. If there is no boot loader installed on your computer, I recommend
doing so using the Puppy Universal Installer.
Boot Puppy fom CD with the "puppy pfix=ram" boot option.
Create a new directory "puppy400" onto a partition with a Linux file system
(ext2/ext3) or a FAT32 file system.
Copy the files
pup_400.SFS
zdrv_400.SFS
initrd.gz
vmlinuz
into this directory. If you are updating Puppy, overwrite the existing files.
Reconfigure the GRUB boot loader by editing the menu.lst file. You will
usually find this file on a Linux partition in the /boot/grub folder.
Append the following two lines to the file menu.lst:

Notice: (hd0,1) signifies the hard disk and partition on which GRUB is stored.
Depending on your boot medium, you will need to set the pmedia parameter
to one of usbflash, usbhd, usbcd, ideflash, idehd, idecd, idezip, satahd,
scsihd or scsicd.
Save the file menu.lst
Close the text editor. Remove the Puppy CD from the drive and exit Puppy
without saving your session. Reboot the PC. Puppy should now boot without
the CD in the drive.
Back to Top
Installation-Full
Back to Top
A Full Installation installs Puppy onto the hard drive like any other "normal"
Linux. This kind of installation is a good idea if you have less than 256 MB of
memory.
Start "Menu | Setup | Puppy universal installer". Select the medium that you
want to install Puppy to. I chose the internal hard drive for this example.
If you have more than one hard drive, choose one.
Click the button next to the partition that you want to install Puppy to.
Confirm the next dialogue by clicking "OK".
You now have to decide whether you want a "Frugal" or a "Full" installation.
Since this chapter describes a Full installation, click the button labelled
"FULL".
The files will be copied from the CD to the hard drive.
system on your computer up to now, you do not have a boot loader. The
Puppy Installer can install GRUB as a boot loader for you. To do this, click on
"INSTALL GRUB".
In the next dialogue box click "Install"
These can only be written to a Linux file system partition. Thus, please type
"/dev/hda2" - that is, the same partition to which Puppy has just been
installed.
In the next dialogue box, click the "No" button.


Click with the right mouse button and choose "Window | Enter Path" from the
context menu.
Type this into the box labelled "Goto" (do not omit the slash at the end):
/mnt/hda2/boot/grub/
You are now inside the /mnt/hda2/boot/grub/ folder.
# Start GRUB global section

#timeout 30
color light-gray/blue black/light-gray
# End GRUB global section
# Other bootable partition config begins
title Windows (on /dev/hda1)
makeactive
chainloader +1
# Other bootable partition config ends
root (hd0,1)
# title Linux (on /dev/hda4)
# root (hd0,3)
# kernel /boot/vmlinuz root=/dev/hda4 ro vga=normal
To include a display timeout, remove "#" from the start of the line of "timeout
30", and change the value, which is in seconds. Note that the entries "Other"
will be for Windows (in /dev/hda1) and "Linux" will be for Linux (on /dev/hda2)
- make sure to insert "Puppy" before the word "Linux"! If there are extra
entries below (the extra entries are made when you have extra partitions or
hard disks), you may ignore them or simply put "#" before the lines - this will
hide the entries.
editor.
the "session" (i.e., all the configuration changes you made). Select "DO NOT
SAVE" with the cursor keys and hit Return.
Your computer will now shut down completely and then start up again. You will
then see the boot loader come up. Select "Puppy Linux (on /dev/hda2)" with
the cursor keys and press Return. Puppy boots up. At the first bootup, you
will once again have to specify your country and your screen resolution. This
configuration is saved so that you do not have to repeat this process at the
next bootup.
Back to Top
Internet Connection
Back to Top
Modem
Start off clicking on "Menu | Network | PupDial modem dialup".
Next, enter the information from your provider.
DSL
First you should check if the ethernet-interface was detected.

Start a shell ("Menu | Utility | Rxvt terminal emulator") and enter the following
command:
ifconfig
Can you see "eth0"?
If you can not see "eth0" enter the following command:

ifconfig eth0 up
To check if the ethernet-interface is available now, enter the following

command:
ifconfig
Now you should see "eth0". Close the shell.

Start the program "Menu | Network | Roaring Penguin PPPoE".
Press the button "SETUP".
Enter your username (ask your provider), then press the return-key.
Enter the ethernet interface. eth0 is usually correct so you can press the
return-key.
At the next question you confirm the default "no" and press the return-key.
Then you have to enter your IP adress. If you get a dynamic IP adress press
the return-key only.
Now enter your password (ask your provider).
Enter your password again.
Choose "1" as a "standalone" firewall.
Now you can see your input again. If everything is alrigth press the key "y".
If you want to connect the internet-connection press the button "Start".
A message box opens and you get connected. Press the return-key.
You can now open the Internet browser "Menu | Internet | SeaMonkey
Webbrowser". Enter a URL and see if the Internet site is displayed.
If you want to disconnect the internet-connection press the button "Stop".
A message box opens and you get disconnected. Press the return-key.
Wireless LAN
To connect your Puppy to a wireless network take the following steps: Step 1
Click on the "connect" icon on your Desktop, then click "Connect to the
Internet by network interface"
.....OR.......
Click on Menu / Setup / Network Wizard
If Puppy recognizes your interface, it will be displayed in the upper portion of

the box.
Just click the button for your interface and see step 2 below.
If puppy does not see your interface you will have to load the appropriate
module with the Load Module button
If you are unsure, click the "more" tab to Auto-probe drivers, or to install a
Windows driver.
After you have loaded the correct module for your interface, it will show up in
the first box seen above.
Click on it and proceed to step 2
Step 2
Configuring Network Interface
Click the Wireless button
Click Scan ( Or enter the information for your interface if you know it)
Click on your Network from the list that appears . Click Save. Enter your WEP
/ WPA key if on a secured network.
Then click Use This Profile. Click the Test button to see if Puppy see`s a "live"
connection. If it does, then click
Auto DHCP. If successful Puppy will ask you if you want to save the
configuration for next boot. Choose yes or no.
Click Done on the box that appears, and you`re all set!
Back to Top
Setup EMail
Back to Top
Start the program "Menu | Internet | SeaMonkey mail and news". The
configuration depends on your email-provider. In the following you will find an
example for GMX.
After you press the button "Finish" the program automatically downloads your
emails from your email account. If you are offline, the following error message
appears:
Start an Internet-connection and click (in the Seamonkey-Mail-Programm) on

the button "Get new messages".
Back to Top
Setup Devices (Printer, Keyboard)

Back to Top
Puppy Linux has Setup in the Menu that contains many ways of setting up
your different devices. Examples are given below for setting up printer and
keyboard.
Printer
This is an easy one to get up and running.Just run "Menu | Setup | Printer
Wizard" and the directions there should be sufficient to get most printers
working.If your printer is not on the list that comes up try one that is similar for
example if you have an superjet 23e try the superjet 23 or superjet 23f.
Keyboard layout
If you are using Xvesa as your video server and you do not have a US
keyboard, you need to customise the keyboard layout. Start "Menu |
Document | Geany text editor" and copy the following lines into it for a
German keyboard layout.
clear shift
clear lock
clear control
clear mod1
clear mod2
clear mod3
!clear mod4
!clear mod5
!de-latin1.map: German keymap
keycode 9 = Escape Escape
keycode10 = 1 exclam
keycode11 = 2 quotedbl twosuperior
keycode12 = 3 section threesuperior
keycode13 = 4 dollar dollar
keycode14 = 5 percent
keycode15 = 6 ampersand
keycode16 = 7 slash braceleft
keycode17 = 8 parenleft bracketleft
keycode18 = 9 parenright bracketright
keycode19 = 0 equal braceright
keycode20 = ssharp question backslash
keycode21 = dead_acute dead_grave
keycode22 = BackSpace Delete
keycode23 = Tab Tab
keycode24 = q Q at
keycode25 = w
keycode26 = e E currency EuroSign

keycode27 = r
keycode28 = t
keycode29 = z
keycode30 = u
keycode31 = i
keycode32 = o
keycode33 = p
keycode34 = udiaeresis Udiaeresis
keycode35 = plus asterisk dead_tilde
keycode36 = Return
keycode37 = Control_L
keycode38 = a
keycode39 = s
keycode40 = d
keycode41 = f
keycode42 = g
keycode43 = h
keycode44 = j
keycode45 = k
keycode46 = l
keycode47 = odiaeresis Odiaeresis
keycode48 = adiaeresis Adiaeresis
keycode49 = dead_circumflex degree
keycode50 = Shift_L
keycode51 = numbersign apostrophe
keycode52 = y
keycode53 = x
keycode54 = c
keycode55 = v
keycode56 = b
keycode57 = n
keycode58 = m M mu
keycode59 = comma semicolon
keycode60 = period colon Multi_key
keycode61 = minus underscore
keycode62 = Shift_R
keycode63 = KP_Multiply
keycode64 = Alt_L Meta_L
keycode65 = space space
keycode66 = Caps_Lock
keycode67 = F1 F11
keycode68 = F2 F12
keycode69 = F3 F13
keycode70 = F4 F14
keycode71 = at F15
keycode72 = bar F16

keycode73 = dead_tilde F17
keycode74 = currency EuroSign F18
keycode75 = braceleft F19
keycode76 = braceright F20
keycode77 = Num_Lock
keycode78 = Scroll_Lock
keycode79 = KP_7
keycode80 = KP_8
keycode81 = KP_9
keycode82 = KP_Subtract
keycode83 = KP_4
keycode84 = KP_5
keycode85 = KP_6
keycode86 = KP_Add
keycode87 = KP_1
keycode88 = KP_2
keycode89 = KP_3
keycode90 = KP_0
keycode91 = KP_Decimal
keycode94 = less greater bar
keycode95 = bracketleft F11
keycode96 = bracketright F12
keycode98 = Up
!keycode99 = Prior
keycode 100 = Left
keycode 102 = Right
!keycode 104 = Down
keycode 105 = Control_R
keycode 106 = KP_Divide
keycode 108 = Alt_R
keycode 110 = Home
keycode 112 = Prior
keycode 113 = Left
keycode 114 = Right
keycode 115 = End
keycode 116 = Down
keycode 117 = Next
keycode 133 = Alt_L
keycode 134 = Alt_R
add shift = Shift_L Shift_R
add lock = Caps_Lock
add control = Control_L Control_R
add mod1 = Alt_L Alt_R
add mod2 = Mode_switch
add mod3 = Num_Lock
!add mod4 =
!add mod5 =
Save this file as .Xmodmap into the /root directory (please note that the first
character of the file name should indeed be a dot). Then restart the X server
by selecting "Menu | Shutdown | Restart X Server" (alternatively, you can
open a console and issue the "xmodmap /root/.Xmodmap" command). Now
the Ã¤Ã¶Ã¼Ã„Ã–Ãœ umlauts are available. The special characters @|~ have
been assigned to the function keys F5, F6 and F7 (F7 has to be pressed
twice to make the tilde appear). The {}[] brackets are located on function keys
F9 to F12.
You can create country-specific keyboard layouts of your own by editing that
file. To find out the correct keycodes, open a console and enter the "xev"
command. The keycode of any key you press and its assigned character will
then be displayed.
Back to Top
By the Puppy Linux Community Helped by eMinima and Simpliste

Puppy Linux Wiki Forum Blog Newsletter
Overview and Getting How to download Puppy Long-Term-Supported Manual-English

Started Linux Puppy
CD, Help, Warranty
Download Latest How NOT to install Puplet for special
Release Puppy Linux features More information
Puppy Linux 5
Manual-English
Lucid Puppy - Nothing
but Praise: Learn
How to Use the Manual and Download Puppy | How to Run Puppy | Saving and Installing
about the new features
to Hard Disk | Preparing the Hard Disk | Installation-Frugal | Installation-Full | Internet
of the first Puppy 5,
Connection | Setup EMail | Setup Devices (Printer, Keyboard)
Lucid Puppy.
The links above are parts of a Puppy Linux manual in English provided and - Dedoimedo
updated by volunteers.
This site is tablet-ready.
The newest installation tutorial in PDF is about Lucid Puppy 5.2.8, prepared
Support this site:
by Md. Hanbala in Arabic, click here to get it, or click to get English or
Bahasa. Note that the installation method is very similar among Puppy Linux
distros.
There is a book by Grant Wilson about Puppy 4.2 downloadable as PDF,

click here. Pay attention to the NOTE below about version numbering
(naming pup_xxx.sfs was changed in version 4.3.1).
A good tutorial for USB install of Puppy Linux 4.30 is made available as PDF
(English, also Italian, Spanish and Portuguese) by Alex Gotev for Linux Day
09 - GALLUG, October 24, 2009, Novara, Italy.
NOTE that the version number used in the manual below is 4.00, and version
numbering is shown as 400 (when used with filenames). You should replace
this with the latest version number, like 4.21 or 421 (Use the number with
filenames, like pup_421.sfs).
IMPORTANT: With version 431, use dash instead of underscore, like pup-
431.sfs. Starting April 23, 2011, long filenames are used for puppy.sfs in
Puppy Linux, and there is a file /etc/DISTRO_SPECS that helps to identify the
matching puppy.sfs however it is named (i.e. this helps the start-up become
fool-proof.).
Thanks to forum members Oliver (oli), Rod (cryftybytes), Jay (puppyluvr) and
Bill (BillWho?).
How to Use the Manual and Download Puppy

Back to Top
Introduction
This manual will appeal to Linux beginners and Linux users, who would like to
become acquainted with Puppy Linux. This manual summarizes the most
important information for Puppy beginners and explains the first steps with
Puppy.
How to use the manual:
Menu entries and buttons are set in "". Sub-menus are separated by vertical
lines. Example: "Menu | Shut Down | JWM restart" means, that you first click
on the button "Menu", than (at the appearing menu) on the headword "Shut
Down" and finally on the headword "JWM restart".
In the manual the letter x is used as a substitute symbol for a number. For
example /dev/hdax means that you have to write /dev/hda1, /dev/hda2 or
/dev/hda3 - just use what suits your computer.
With the term "shell" the program "Menu | Run | Rxvt terminal emulator" is
meant.
How to get Puppy
You can get Puppy Linux from ibiblio.org. Save the current release pup-
431.iso on your harddrive. The filesize is about 105 MB.
To make sure that you downloaded a genuine original file, you can compare
the checksum of the ISO file with the associated file pup-431-md5sum.txt.
(right-click to download this file as well).
Within Linux:
Open a shell and change into the directory, in which you stored the two files.
Enter the following command:
md5sum -c pup-431-md5sum.txt
This will run the md5sum program on your .iso file and compare it with the
value in the .txt file. You should get an OK. If not you need to download the
iso again.
Within Windows:
Download the DOS-Program md5sum.exe and save it in the same directory

where you saved the downloaded files.
To open a DOS-Box click on "Start | Run". This opens an input window, into
which you enter the following command:
cmd
Now you get a DOS-Box. Change into the directory in which you stored the
two files, e.g. c:/pup431. Enter these commands:
c:
cd pup431
dir
Now you should see the Puppy-files (make sure that you copy md5sum.exe to
this same location). Next, enter the command:
md5sum.exe -c pup-431-md5sum.txt
You should get an "OK".
Subsequently you burn the ISO file (in our example, pup-431.iso) on CD. To
burn an ISO file on CD, consult the manual of your CD-burning software.
Beginners sometimes copy the ISO file simply as a data-file on CD, which
doesn’t work. Usually the CD-burning software has a special menu option for
burning an ISO file on CD. You can verify whether you burned the CD
correctly by looking at the CD with the file manager (e.g. Windows Explorer). If
you see files as "initrd.gz" or "vmlinuz" everything is OK. If you see the file
"pup-431.iso" (an ISO filename) this is incorrect.
A small and excellent CD burning program for Windows is BurnCDCC - just

download, unzip to a folder in Windows and click on burncdcc.exe (do not
forget to choose low burning speed of 4X for CD or 1X for DVD).
Tip:
Create a second, identical Puppy CD as a backup copy, in case the original

CD becomes corrupted.
Back to Top
How to Run Puppy

Back to Top
A great advantage of Puppy Linux is that Puppy doesn't have to be installed.

You can run Puppy directly from the CD, without affecting your operating
system. Alternatively you can install Puppy on a harddrive or a USB stick.
How to run Puppy the very first time
First you must set up the boot sequence in the BIOS. If you do not know how
to get into the BIOS-setup, consult the computers manual. Usually you press
one of the following keys immediately after switching on the PC: ESC, one of
the function keys F1 to F12 or the delete key. At the BIOS-setup you change
the boot sequence so that the CD-ROM drive is first and the harddrive is
second. Close the BIOS-setup and store the settings.
The PC then usually reboots. Immediately insert the Puppy CD into the CD-
ROM drive. If you are too slow your old operating system starts. In this case
keep the CD inserted in the CD drive and start the PC again.
Now Puppy should start. During the starting procedure you are requested to
choose from a few options such as mouse, country or timezone. The choice
for mouse is usually automatic, and you can choose "ps2" even if you have
no attached mouse to yout laptop. For other questions, navigate with the
cursor keys downward to your choice. Then strike the return-key. Thereafter
a further window (Puppy video Wizard) appears, "Xorg" is already highlighted.
Press the return-key. Wait some seconds till the next window (Puppy video
Wizard) appears. There you navigate with the cursor keys to your screen
(LCD panel = flat screen, CRT = standard monitor) and your choice
resolution. Then strike the return-key. After some seconds the Puppy desktop
appears.
Should Xorg not work on your computer, choose Xvesa. A few seconds later,
the Puppy desktop will be displayed using a resolution of 640 x 480 pixels. If
you wish to use an even higher resolution choose e.g. 1280x1024x24 and
click on the button "Change".
After some seconds the Puppy desktop appears again. Click on the OK-
button.
Unfortunately, with Xvesa you will have to adjust the keyboard layout if you
are not using a US keyboard.
If your PC has 256 MB RAM, Puppy will be loaded completely into RAM (or
mounted to the CD/DVD disk if your PC lacks RAM). Your old operating
system is not touched, so that you can look safely at Puppy Linux. Now you
can take the CD out of the CD drive, unless you do not have enough ram, in
which case Puppy will not allow the CD to be ejected.
If you terminate Puppy you are asked whether you want to store the settings
(and your personal files) in two ways (you can change between the options
with the tab-key and then and press the return-key):
SAVE TO FILE - Save to a file named pup_save.2fs on a hard disk or

USB flash drive.
SAVE TO CD - Save to the same CD or DVD where you booted from (this
requires that the Puppy CD or DVD was burned in a way that files can
still be added to it).
DO NOT SAVE - Exit Puppy without saving anything.
If you would like to store the settings (and your personal files) you are asked
on which hard disk or USB flash drive this should happen. If saving to
pup_save.2fs, choose at least 128 MB.
Boot Options
When Puppy boots it offers you some boot-options. If you do not enter
anything, Puppy is loaded after some seconds into RAM. When starting,
Puppy automatically looks for a previously stored pup_save.2fs-file. If this file
doesn't exist yet, you will be asked again the same boot-up questions.
With the boot-option
puppy pfix=ram
you have the option to start Puppy into RAM without your pre-saved-settings
and without your personal files even if a pup_save.2fs-file already exists. This
boot option is very useful and is used in this manual a few times. The other
boot options are normally not needed.
Back to Top
Saving and Installing to Hard Disk

Back to Top
How to save the settings and your personal files
So that Puppy can store all settings and your personal data, a file named
pup_save.2fs is saved. I recommend a size of 512 MB for this file. This is big
enough for further programs and can be backed-up on CD-ROM (note: if you
want to backup the file on a USB stick, it must have a storage capacity of 1
GB). Puppy can store the pup_save.2fs-file on many different filesystems
including FAT and NTFS as used by windows. (note: USB sticks and external
harddrives are usually formatted with a FAT32-filesystem, so that they can be
used without problems). Windows XP-users normally have a NTFS-filesystem
only. There are two options for you to store the pup_save.2fs-file as well:
(1) Save the file on an external harddrive or USB-stick.
(2) Make the NTFS partition smaller and create one or more further partition
with FAT32-filesystem and ext2/ext3-filesystem.
If you intend to use Puppy durably you should select the second alternative.
This alternative has many advantages.
How to install Puppy
If you prefer not to keep booting Puppy from CD-ROM, you can install Puppy
to a hard disk drive. This requires some preparation.
Hard drives, partitions and filesystems
A hard drive can be divided in one or more partitions. If you create several
partitions on a harddrive, each partition appears like a hard drive in the
operating system. In other words: although you have only one harddrive in
your PC, you will see several (virtual) hard-drives with Windows or Linux.
Windows designates the harddrives (as well as the floppy disk drive and
CD/DVD drive). In Windows they will be identified with letters. Usually A
designates the floppy disk drive, C the harddrive (first partition), D the CD-
ROM drive, E the harddrive (second partition), F the harddrive (third partition)
and so on. Each partition has its own file system, Windows normally uses
NTFS (Windows XP) or FAT32 (Win98, Win95).
With Linux the (first) harddrive is adressed as /dev/hda or /dev/sda. If your

PC has a second harddrive, it is adressed as /dev/hdb or /dev/sdb. The
partitions are sequentially numbered, starting with one. The partitions of your
harddrive are adressed as /dev/hda1 (corresponds to the Windows C-
partition), /dev/hda2 (corresponds to the Windows E-partition), /dev/hda3 and
so on. Linux can work with different file systems such as ext2, ext3 or
ReiserFS. These file systems are not readable by Windows. In addition Linux
can work with Windows filesystems too.
Back to Top
Preparing the Hard Disk

Back to Top
Defragment your hard disk
Before creating new partitions on your hard drive, you should defragment the
drive so that all data is stored at the beginning of the existing partition. Here
is how to do it:
Start up Windows.
First, backup your files to CD-ROM, DVD, or an external hard drive. Also
remember to backup your Internet link collection (Favourites) and your e-
mails. If your data is encrypted, it is advisable to decrypt it before backing it
up. This protects you from data loss because modifying hard drive partitions
always carries the risk of data loss.
Next, start the Disk Defragmenter program under Windows. The program is
located at "Start | All Programs | Utilities | System Programs | Disk
Defragmenter". Select hard drive c:\ and click the "Check" button.
Click the "Defragment" button. Depending on the size of the partition and the
amount of data on it, this process can take a long time (over an hour). If you
have very large amounts of data, you can speed up this process drastically
by deleting your files after you have backed them up (see the previous item)
and restoring them once you are done with the modifications. In this case,
please make sure beforehand that your backup is readable, otherwise there
will be wailing and gnashing of teeth.
There is now space on the harddisk for additional partitions.
Shut down Windows.
Creating partitions
Now you should plan the layout of your hard disk partitions regarding file
system and size. I recommend creating three or four partitions in addition to
the Windows partition. The following example assumes you have exactly one
Windows partition (drive letter C). Your hard disk would then look like this:
First partition: NTFS or FAT32 (Windows)

Second partition: ext2 or ext3 (this is where Puppy will be installied to)
Third partition: Linux swap (for page files)
Fourth partition: FAT32 (for exchanging data between Windows and Linux)
Optionally, a fifth partition: ext2 or ext3 (Linux)
Windows will continue to reside on your first partition with all its programs and
data. The second partition (recommended size about 1-2 GB) has a Linux file
system (ext2 or ext3). This is the partition Puppy will be installed to. The third
partition (exactly as large as your computer's memory) will be a Linux swap
partition that Linux can ... well, swap files to. The fourth partition has a FAT32
file system, which is recognized by both Windows and Linux. This partition
(recommended size about 5 GB) is used for files that you want to access from
both Windows and Linux. If you want to manage large amounts of data under
Puppy (e.g. music collection, pictures), you should create a fifth partition with
a Linux file system (ext2/ext3). This file system cannot be accessed from
Windows and is meant for Linux only.
To create the partitions, proceed as follows:
Start Puppy Linux from CD with the "pfix=ram" boot option.
Start the Gparted program: "Menu | System | Gparted partition manager".
First, shrink your Windows partition (NTFS file system). To do this, select the
Windows partition /dev/hda1.
Click the "Resize/Move" button.
Reduce the "New Size" value until the "Free Space Following" field shows
enough free space following for the new partitions. My test computer's hard
disk has only 3 gigabytes; I am using half of that for the mew partitions. You
probably have a much larger hard drive so your partition sizes can be
increased accordingly.
Then press the "Resize/Move" button.
Next, select "Edit | Apply All Operations" from the menu.
In the dialogue box that comes up, click the "Apply" button.
Click the "Close" button. You now have an "unallocated" area on your hard
disk.
Select the line saying "unallocated" and click the "New" button.
Enter the size of the second partition in the "New Size" field. This is where
Puppy Linux will be installed to. I recommend a size of 1 to 2 gigabytes (i.e.,
1024 to 2048 MB). Select ext2 from the "Filesystem" box and click "Add".
Again select the line saying "unallocated" and click the "New" button. (You
can see where this is going.)
Enter the size of the third partition in the "New Size" field. This partition is to
hold Linux's swap files as a Linux swap partition. You should make it as large
as your computer's memory (RAM). With my test computer, this amounts to
128 megabytes (MB). Select linux-swap from the "Filesystem" box and click
"Add".
Again select the line saying "unallocated" and click the "New" button.
Enter the size of the fourth partition in the "New Size" field.This partition is
meant for shared access to files from Windows and Linux. I recommend a size
of about 5 gigabytes (5120 MB). Since my test computer does not have a
large enough hard disk, I am using 396 megabytes (MB) as an example.
Select FAT32 from the "Filesystem" box and click "Add".
Hint: if you want to create additional partitions (e.g., for very large files under
Linux), repeat the process outlined above accordingly. In this case, you may
have to create so-called logical partitions. Please consult additional sources if
you are unsure about how to do that.
To actually write the changes to disk, select "Edit | Apply All Operations" from
the menu.
In the dialogue box that comes up, click "Apply".
Exit GParted.
Back to Top
Installation-Frugal
Back to Top
There are different ways to install Puppy:
Frugal Installation (Pupy CD image on hard drive)
Universal Installer
Manual Install
Other Ways
Full Installation
Installation to a USB flash drive
Installation to a CF card
Frugal Installation is recommended if you have 256 MB RAM or more. If you

have less than 256 MB RAM you should choose Full Installation.
Frugal Installation using Puppy Universal Installer
A Frugal Installation copies the image from the Puppy CD to the hard drive. At
bootup, Puppy is loaded into your computer's memory (RAM) just as it is
when you boot Puppy from CD, however, loading it from a hard drive is much
faster. This way, Frugal Installation combines the advantages of booting from
CD-ROM (protection from malware) and a hard drive bootup (speed).
Moreover, upgrading to a new Puppy version is very simple - all you have to
do is replace some files.
Start "Menu | Setup | Puppy universal installer". Choose which medium Puppy
should be installed to. In this example, I chose the internal hard drive.
If you have several hard drives, select one.
Next, click on the button next to the partition that you want Puppy to be
installed to - /hda2 in this example.
In the dialogue box, click "OK".
You now have to decide whether you want a "Frugal" or a "Full" installation. In
our example, click on the "FRUGAL" button.
Now you change the installation directory. Just click on the "OK" button.
The files are now copied from CD to the hard drive.
The installation is finished. In the next two dialogue boxes, click "OK".
system on your computer up to now, you do not have a boot loader. Start the
installation of the boot loader GRUB with "Menu | System | Grub bootloader
config".
These can only be written to a Linux file system partition. Thus, please
specify one of the Linux (ext2 or ext3 file system) partitions you created
(/dev/hda2 in the example). If you do not have a Linux file system partition
yet, you need to create one.
In the next dialogue box, click "OK".


Right-click with the mouse and choose "Window | Enter Path".
Enter the following path next to "Goto: /mnt/hda2/boot/grub/
You are now at the folder /mnt/hda2/boot/grub/
Edit the file at this point:

(Notice: depending on what medium you boot from, you have to set the
pmedia parameter to one of usbflash, usbhd, usbcd, ideflash, idehd, idecd,
idezip, satahd, scsihd or scsicd. If you did not install the GRUB files to the
/dev/hda2 partition, you need to change the rootnoverify parameter as well -
partition number and Linux drive letter minus one, so if the GRUB files are on
/dev/hdb3 (partition 3 in second drive hdb), make it "rootnoverify (hd1,2)".)
With the changed line, the grub entry should now look like this:

"Comment out", i.e. put a number sign (#) before the lines:that are no longer
needed, like the following extra entries automatically written by Grub:

root (hd0,2)
root (hd0,3)
editor.
Click on the button "QUIT".
the "session" (i.e., all the configuration changes you made). Hit Return to
select the entry "SAVE TO FILE", which is already highlighted.
Confirm the next dialogue (Warning) by hitting Return.
In the next dialogue, select the "hda2" partition with the cursor keys and press
Return.
Now. you will be asked, if the file should get a special filename. Just press
Return.
You will be asked whether you want a normal (unencrypted) or an encrypted

save file. Select "NORMAL" with the cursor keys and press Return.
The next dialogue lets you choose a size for your save file. A file size of 512
megabytes is usually sufficient. You can increase (but not decrease) this size
anytime from within Puppy. Pick the desired file size with the cursor keys and
press Return.
In the next screen you see a summary. Choose "Change Folder" and press
return.
Next, you enter "/puppy400" as subfolder and confirm with return.
Again a summary is shown and if everything seems to be ok, choose "Yes,

save" with the arrow keys, then press return.
Please be patient while the file is created.
Next you will be asked if Puppy 4.xx should test for serial devices at each
boot. Choose ""No" with the arrow keys and confirm with return.
Now you decide wether the system file pup400.sfs should be copied over to
the harddrive. Choose "Yes" with the arrow keys and confirm with return.
Last not least the computer restarts automatically. Remove the Puppy CD
from the drive before the shutdown is complete. Upon reboot the boot loader
will show up. Choose ""Puppy Linux 4.00 frugal (on /dev/hda2)"" with the
arrow keys and confirm with return.
Manual Installation
To be able to use this option, a boot loader has to be installed on your

computer. If there is no boot loader installed on your computer, I recommend
doing so using the Puppy Universal Installer.
Boot Puppy fom CD with the "puppy pfix=ram" boot option.
Create a new directory "puppy400" onto a partition with a Linux file system
(ext2/ext3) or a FAT32 file system.
Copy the files
pup_400.SFS
zdrv_400.SFS
initrd.gz
vmlinuz
into this directory. If you are updating Puppy, overwrite the existing files.
Reconfigure the GRUB boot loader by editing the menu.lst file. You will
usually find this file on a Linux partition in the /boot/grub folder.
Append the following two lines to the file menu.lst:

Notice: (hd0,1) signifies the hard disk and partition on which GRUB is stored.
Depending on your boot medium, you will need to set the pmedia parameter
to one of usbflash, usbhd, usbcd, ideflash, idehd, idecd, idezip, satahd,
scsihd or scsicd.
Save the file menu.lst
Close the text editor. Remove the Puppy CD from the drive and exit Puppy
without saving your session. Reboot the PC. Puppy should now boot without
the CD in the drive.
Back to Top
Installation-Full
Back to Top
A Full Installation installs Puppy onto the hard drive like any other "normal"
Linux. This kind of installation is a good idea if you have less than 256 MB of
memory.
Start "Menu | Setup | Puppy universal installer". Select the medium that you
want to install Puppy to. I chose the internal hard drive for this example.
If you have more than one hard drive, choose one.
Click the button next to the partition that you want to install Puppy to.
You now have to decide whether you want a "Frugal" or a "Full" installation.
Since this chapter describes a Full installation, click the button labelled
"FULL".
The files will be copied from the CD to the hard drive.
system on your computer up to now, you do not have a boot loader. The
Puppy Installer can install GRUB as a boot loader for you. To do this, click on
"INSTALL GRUB".
In the next dialogue box click "Install"
These can only be written to a Linux file system partition. Thus, please type
"/dev/hda2" - that is, the same partition to which Puppy has just been
installed.
In the next dialogue box, click the "No" button.


Click with the right mouse button and choose "Window | Enter Path" from the
context menu.
Type this into the box labelled "Goto" (do not omit the slash at the end):
/mnt/hda2/boot/grub/
You are now inside the /mnt/hda2/boot/grub/ folder.
# Start GRUB global section

#timeout 30
color light-gray/blue black/light-gray
# End GRUB global section
# Other bootable partition config begins
title Windows (on /dev/hda1)
makeactive
chainloader +1
# Other bootable partition config ends
root (hd0,1)
# title Linux (on /dev/hda4)
# root (hd0,3)
# kernel /boot/vmlinuz root=/dev/hda4 ro vga=normal
To include a display timeout, remove "#" from the start of the line of "timeout
30", and change the value, which is in seconds. Note that the entries "Other"
will be for Windows (in /dev/hda1) and "Linux" will be for Linux (on /dev/hda2)
- make sure to insert "Puppy" before the word "Linux"! If there are extra
entries below (the extra entries are made when you have extra partitions or
hard disks), you may ignore them or simply put "#" before the lines - this will
hide the entries.
editor.
the "session" (i.e., all the configuration changes you made). Select "DO NOT
SAVE" with the cursor keys and hit Return.
Your computer will now shut down completely and then start up again. You will
then see the boot loader come up. Select "Puppy Linux (on /dev/hda2)" with
the cursor keys and press Return. Puppy boots up. At the first bootup, you
will once again have to specify your country and your screen resolution. This
configuration is saved so that you do not have to repeat this process at the
next bootup.
Back to Top
Internet Connection
Back to Top
Modem
Start off clicking on "Menu | Network | PupDial modem dialup".
Next, enter the information from your provider.
DSL
First you should check if the ethernet-interface was detected.

Start a shell ("Menu | Utility | Rxvt terminal emulator") and enter the following
command:
ifconfig
Can you see "eth0"?
If you can not see "eth0" enter the following command:

ifconfig eth0 up
To check if the ethernet-interface is available now, enter the following

command:
ifconfig
Now you should see "eth0". Close the shell.

Start the program "Menu | Network | Roaring Penguin PPPoE".
Press the button "SETUP".
Enter your username (ask your provider), then press the return-key.
Enter the ethernet interface. eth0 is usually correct so you can press the
return-key.
At the next question you confirm the default "no" and press the return-key.
Then you have to enter your IP adress. If you get a dynamic IP adress press
the return-key only.
Now enter your password (ask your provider).
Enter your password again.
Choose "1" as a "standalone" firewall.
Now you can see your input again. If everything is alrigth press the key "y".
If you want to connect the internet-connection press the button "Start".
A message box opens and you get connected. Press the return-key.
You can now open the Internet browser "Menu | Internet | SeaMonkey
Webbrowser". Enter a URL and see if the Internet site is displayed.
If you want to disconnect the internet-connection press the button "Stop".
A message box opens and you get disconnected. Press the return-key.
Wireless LAN
To connect your Puppy to a wireless network take the following steps: Step 1
Click on the "connect" icon on your Desktop, then click "Connect to the
Internet by network interface"
.....OR.......
Click on Menu / Setup / Network Wizard
If Puppy recognizes your interface, it will be displayed in the upper portion of

the box.
Just click the button for your interface and see step 2 below.
If puppy does not see your interface you will have to load the appropriate
module with the Load Module button
If you are unsure, click the "more" tab to Auto-probe drivers, or to install a
Windows driver.
After you have loaded the correct module for your interface, it will show up in
the first box seen above.
Click on it and proceed to step 2
Step 2
Configuring Network Interface
Click the Wireless button
Click Scan ( Or enter the information for your interface if you know it)
Click on your Network from the list that appears . Click Save. Enter your WEP
/ WPA key if on a secured network.
Then click Use This Profile. Click the Test button to see if Puppy see`s a "live"
connection. If it does, then click
Auto DHCP. If successful Puppy will ask you if you want to save the
configuration for next boot. Choose yes or no.
Click Done on the box that appears, and you`re all set!
Back to Top
Setup EMail
Back to Top
Start the program "Menu | Internet | SeaMonkey mail and news". The
configuration depends on your email-provider. In the following you will find an
example for GMX.
After you press the button "Finish" the program automatically downloads your
emails from your email account. If you are offline, the following error message
appears:
Start an Internet-connection and click (in the Seamonkey-Mail-Programm) on

the button "Get new messages".
Back to Top
Setup Devices (Printer, Keyboard)

Back to Top
Puppy Linux has Setup in the Menu that contains many ways of setting up
your different devices. Examples are given below for setting up printer and
keyboard.
Printer
This is an easy one to get up and running.Just run "Menu | Setup | Printer
Wizard" and the directions there should be sufficient to get most printers
working.If your printer is not on the list that comes up try one that is similar for
example if you have an superjet 23e try the superjet 23 or superjet 23f.
Keyboard layout
If you are using Xvesa as your video server and you do not have a US
keyboard, you need to customise the keyboard layout. Start "Menu |
Document | Geany text editor" and copy the following lines into it for a
German keyboard layout.
clear shift
clear lock
clear control
clear mod1
clear mod2
clear mod3
!clear mod4
!clear mod5
!de-latin1.map: German keymap
keycode 9 = Escape Escape
keycode10 = 1 exclam
keycode11 = 2 quotedbl twosuperior
keycode12 = 3 section threesuperior
keycode13 = 4 dollar dollar
keycode14 = 5 percent
keycode15 = 6 ampersand
keycode16 = 7 slash braceleft
keycode17 = 8 parenleft bracketleft
keycode18 = 9 parenright bracketright
keycode19 = 0 equal braceright
keycode20 = ssharp question backslash
keycode21 = dead_acute dead_grave
keycode22 = BackSpace Delete
keycode23 = Tab Tab
keycode24 = q Q at
keycode25 = w
keycode26 = e E currency EuroSign

keycode27 = r
keycode28 = t
keycode29 = z
keycode30 = u
keycode31 = i
keycode32 = o
keycode33 = p
keycode34 = udiaeresis Udiaeresis
keycode35 = plus asterisk dead_tilde
keycode36 = Return
keycode37 = Control_L
keycode38 = a
keycode39 = s
keycode40 = d
keycode41 = f
keycode42 = g
keycode43 = h
keycode44 = j
keycode45 = k
keycode46 = l
keycode47 = odiaeresis Odiaeresis
keycode48 = adiaeresis Adiaeresis
keycode49 = dead_circumflex degree
keycode50 = Shift_L
keycode51 = numbersign apostrophe
keycode52 = y
keycode53 = x
keycode54 = c
keycode55 = v
keycode56 = b
keycode57 = n
keycode58 = m M mu
keycode59 = comma semicolon
keycode60 = period colon Multi_key
keycode61 = minus underscore
keycode62 = Shift_R
keycode63 = KP_Multiply
keycode64 = Alt_L Meta_L
keycode65 = space space
keycode66 = Caps_Lock
keycode67 = F1 F11
keycode68 = F2 F12
keycode69 = F3 F13
keycode70 = F4 F14
keycode71 = at F15
keycode72 = bar F16

keycode73 = dead_tilde F17
keycode74 = currency EuroSign F18
keycode75 = braceleft F19
keycode76 = braceright F20
keycode77 = Num_Lock
keycode78 = Scroll_Lock
keycode79 = KP_7
keycode80 = KP_8
keycode81 = KP_9
keycode82 = KP_Subtract
keycode83 = KP_4
keycode84 = KP_5
keycode85 = KP_6
keycode86 = KP_Add
keycode87 = KP_1
keycode88 = KP_2
keycode89 = KP_3
keycode90 = KP_0
keycode91 = KP_Decimal
keycode94 = less greater bar
keycode95 = bracketleft F11
keycode96 = bracketright F12
keycode98 = Up
!keycode99 = Prior
keycode 100 = Left
keycode 102 = Right
!keycode 104 = Down
keycode 105 = Control_R
keycode 106 = KP_Divide
keycode 108 = Alt_R
keycode 110 = Home
keycode 112 = Prior
keycode 113 = Left
keycode 114 = Right
keycode 115 = End
keycode 116 = Down
keycode 117 = Next
keycode 133 = Alt_L
keycode 134 = Alt_R
add shift = Shift_L Shift_R
add lock = Caps_Lock
add control = Control_L Control_R
add mod1 = Alt_L Alt_R
add mod2 = Mode_switch
add mod3 = Num_Lock
!add mod4 =
!add mod5 =
Save this file as .Xmodmap into the /root directory (please note that the first
character of the file name should indeed be a dot). Then restart the X server
by selecting "Menu | Shutdown | Restart X Server" (alternatively, you can
open a console and issue the "xmodmap /root/.Xmodmap" command). Now
the Ã¤Ã¶Ã¼Ã„Ã–Ãœ umlauts are available. The special characters @|~ have
been assigned to the function keys F5, F6 and F7 (F7 has to be pressed
twice to make the tilde appear). The {}[] brackets are located on function keys
F9 to F12.
You can create country-specific keyboard layouts of your own by editing that
file. To find out the correct keycodes, open a console and enter the "xev"
command. The keycode of any key you press and its assigned character will
then be displayed.
Back to Top
By the Puppy Linux Community Helped by eMinima and Simpliste

Home  Fedora Quick Docs  Creating and using a live installation image
 Fedora Quick Docs

Quick Docs in progress (How to
help!)
 Remix Documentation
Checking integrity with AIDE
 Anaconda installation
program
Getting started with Apache

HTTP Server
Finding and installing Linux

applications
Installing Chromium or Google
Chrome browsers
Switching desktop
environments
Difference between Fedora and
Red Hat Enterprise Linux
Using the DNF software

package manager
Upgrading Fedora using the

DNF system upgrade
Securing the system by keeping

it up-to-date
Fedora Release Life Cycle
Upgrading to a new release of

Fedora
Controlling network traffic with
firewalld
Adding new fonts in Fedora
Creating GPG Keys

Bootloading with GRUB2
Creating and using a live

installation image
Installing Java
 Kernel
Managing keyboard shortcuts

for running an application in
GNOME
Setting a key shortcut to run an
application in GNOME
Disabling the GNOME

automatic screen locking
Viewing logs in Fedora
Installing plugins for playing

movies and music
Installing and running the VLC
player
Configuring networking with

NetworkManager CLI (nmcli)
Creating disk partitions
NVIDIA Optimus Bumblebee
Raspberry Pi
Fedora Repositories
Adding or removing software

repositories in Fedora
Resetting a root password
Creating RPM packages
Creating a GNU Hello World

RPM Package
Getting started using SELinux
Changing SELinux states and

modes
Troubleshooting SELinux
Using shared system

certificates
Installing software from source
code
Installing Spotify on Fedora
Performing administration
tasks using sudo
Understanding and
administering systemd
Displaying a user prompt on
the GNOME login screen
Installing virtual operating
systems with GNOME Boxes
Using virtualization emulation

in QEMU
Getting started with

virtualization (libvirt)
Using nested virtualization in

KVM
Creating Windows virtual

machines using virtIO drivers
Running Windows applications

with Wine
Configuring X Window System
using the xorg.conf file
Configuring X.org as the default
GNOME session
Creating and using a live installation image

Downloading Fedora
You can download Fedora from https://getfedora.org/.
There are multiple desktops available for use with Fedora. Each has a slightly different
look and feel and offers varying levels of customization. Visit Fedora Desktops to know
more.
Fedora spins are alternate versions of Fedora, tailored for various types of users, using
hand-picked application sets and other customizations. Visit Fedora Spins to know more.
 Please refer to Fedora Installation Guide for getting help on the process of
installing Fedora.
Creating and using live USB

You can write all Fedora ISO images to a USB stick, making this a convenient way on any
USB-bootable computer to either install Fedora or try a live Fedora environment without
writing to the computer’s hard disk. You will need a USB stick at least as large as the image
you wish to write.
Using Fedora Media Writer

The official and supported tool to create a Fedora USB stick is the Fedora Media Writer
utility, which was formerly known as LiveUSB Creator. To learn more about this
application and how to use it, refer to the Preparing for Installation chapter of the Fedora
Installation Guide.
Fedora Media Writer destroys all data on the USB stick. If you need a non-
 destructive write method (to preserve existing data on your USB stick) or
support for 'data persistence', you can use the livecd-iso-to-disk utility on
Fedora.
Using GNOME Disk Utility
This method will destroy all data on the USB stick. If you need a non-
 destructive write method (to preserve existing data on your USB stick)
and/or support for 'data persistence', you can use the
livecd-iso-to-disk utility on Fedora.
 This method is considered unsupported. You can use it on your own risk.
This method is for people running Linux, or another unix with GNOME, Nautilus and the
GNOME Disk Utility installed. Particularly, if you are using a distribution other than Fedora
which does not support Flatpak, this may be the easiest available method. A standard
installation of Fedora, or a standard GNOME installation of many other distributions,
should be able to use this method. On Fedora, ensure the packages nautilus and gnome-
disk-utility are installed. Similar graphical direct-write tools may be available for other
desktops, or you may use the command-line direct write method.
1. Download a Fedora image, choose a USB stick that does not contain any data you
need, and connect it.
2. Run Nautilus (Files), open the Overview by pressing the Start/Super key, type Files,
and hit Enter .
3. Find the downloaded image, right-click on it, go to Open With, and click Disk Image
Writer.
4. Select your USB stick as the Destination, and click Start Restoring.
Command line methods
 These methods are considered unsupported. You can use them on your own
risk.
Using the livecd-iso-to-disk tool
 This method will destroy all data on the USB stick if the --format parameter
is passed.
The livecd-iso-to-disk method is slightly less reliable than Fedora Media Writer and
can be used reliably only from within Fedora: it does not work in Windows or OS X, and is
not supported (and will usually fail) in non-Fedora distributions. However, it supports
three advanced features which FMW does not include:
1. You may use a non-destructive method to create the stick, meaning existing files on
the stick will not be destroyed. This is less reliable than the destructive write methods,
and should be used only if you have no stick you can afford to wipe.
2. On live images, you can include a feature called a persistent overlay, which allows
changes made to persist across reboots. You can perform updates just like a regular
installation to your hard disk, except that kernel updates require manual
intervention and overlay space may be insufficient. Without a persistent overlay, the
stick will return to a fresh state each time it is booted.
3. On live images, you can also have a separate area to store user account information
and data such as documents and downloaded files, with optional encryption for
security and peace of mind.
By combining these features, you can carry your computer with you in your pocket,
booting it on nearly any system you find yourself using.
It is not a good idea to try and write a new Fedora release using the version of
livecd-iso-to-disk in a much older Fedora release: it is best to only use a release a
maximum of two versions older than the release you are trying to write.
Ensure the livecd-tools package is installed: dnf install livecd-tools.
Remember to identify your USB stick’s device name first. In all cases, you can add the parameter
--efi to render the stick bootable in native UEFI mode. Detailed usage information is available
by running: livecd-iso-to-disk --help or man livecd-iso-to-disk.
To make an existing USB stick bootable as a Fedora image, without deleting any of the data on it,
make sure that the USB drive is not mounted before executing the following, and give the root
password when prompted:

# livecd-iso-to-disk Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
In case it is not possible to boot from a disk created with the method shown above, before re-
partitioning and re-formatting, often resetting the master boot record will enable booting:
# livecd-iso-to-disk --reset-mbr Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
 Using the --format option in the following command will erase all data on
the USB drive.
If necessary, you can have livecd-iso-to-disk re-partition and re-format the target
stick:
# livecd-iso-to-disk --format --reset-mbr Fedora-Workstation-Live-x86_64-28-

1.1.iso /dev/sdX
To include a persistent filesystem for /home, use the --home-size-mb parameter. For
example:
# livecd-iso-to-disk --home-size-mb 2048 Fedora-Workstation-Live-x86_64-28-1

.1.iso /dev/sdX
This will create a 2 GiB filesystem that will be mounted as /home each time the stick is
booted, allowing you to preserve data in /home across boots.
To enable 'data persistence' support - so changes you make to the entire live environment
will persist across boots - add the --overlay-size-mb parameter to add a persistent
data storage area to the target stick. For example:
# livecd-iso-to-disk --overlay-size-mb 2048 Fedora-Workstation-Live-x86_64-2

8-1.1.iso /dev/sdX
Here, 2048 is the desired size (in megabytes) of the overlay. The livecd-iso-to-disk
tool will not accept an overlay size value greater than 4095 for VFAT, but for ext[234]
filesystems it is only limited by the available space.
Due to the way it’s currently implemented, every single change to this form
of overlay, writes AND deletes, subtracts from its free space so it will
eventually be "used up" and your USB stick will no longer boot. You can use
dmsetup status live-rw to see how much space remains in the overlay.
 The output will contain something like snapshot 42296/204800, indicating
that 4229 of 204800 512-byte sectors are allocated. Because of these
limitations, it is advisable to use the system-level persistence sparingly,
for configuration changes and important security updates only. Or, if you
have sufficient disk space available, changes to the LiveOS root filesystem
snapshot can be merged into a new copy of the root filesystem.
You can combine --home-size-mb and --overlay-size-mb, in which case data

written to /home will not exhaust the persistent overlay.
Using a direct write method
This method will destroy all data on the USB stick. If you need a non-
 destructive write method, to preserve existing data on your USB stick,

and/or support for data persistence, you can use the
livecd-iso-to-disk utility on Fedora.
This method directly writes the image to the USB stick much like Fedora Media Writer or
GNOME Disk Utility, but uses a command line utility named dd. Like the other direct write
methods, it will destroy all data on the stick and does not support any of the advanced
features like data persistence, but it is a very reliable method. The dd tool is available on
most Unix-like operating systems, including Linux distributions and OS X, and a Windows
port is available. This may be your best method if you cannot use Fedora Media Writer or
GNOME Disk Utility, or just if you prefer command line utilities and want a simple, quick
way to write a stick.
1. Identify the name of the USB drive partition. If using this method on Windows, with
the port linked above, the dd --list command should provide you with the
correct name.
2. Unmount all mounted partition from that device. This is very important,
otherwise the written image might get corrupted. You can umount all mounted
partitions from the device with umount /dev/sdX*, where X is the appropriate
letter, e.g. umount /dev/sdc*.
3. Write the ISO file to the device:
# dd if=/path/to/image.iso of=/dev/sdX bs=8M status=progress oflag=direct
4. Wait until the command completes.
If you see dd: invalid status flag: 'progress', your dd
 version doesn’t support the status=progress option and you’ll need

to remove it. In this case, you won’t see writing progress.
Using UNetbootin for Windows, OS X, and Linux
 This method is considered unsupported. You can use it on your own risk.
UNetbootin may work in some cases but not others - for instance, it will likely
create a stick that is bootable in BIOS mode, but not UEFI mode. Fedora
cannot guarantee support for UNetbootin-written images.
 While your results may vary, it is usually the case that the Fedora Media
Writer, livecd-iso-to-disk, GNOME, and dd methods give better results
than UNetbootin. If you encounter problems with UNetbootin, please
contact the UNetbootin developers, not the Fedora developers.
UNetbootin is a graphical, bootable USB image creator. Using it will allow you to preserve
any data you have in the USB drive. If you have trouble booting, however, you may wish to
try with a blank, cleanly FAT32-formatted drive.
 If you are running a 64-bit Linux distribution, UNetbootin may fail to run until
you install the 32-bit versions of quite a lot of system libraries.
1. Download the latest UNetbootin version from the official site and install it. On Linux,
the download is an executable file: save it somewhere, change it to be executable
using chmod ugo+x filename or a file manager, and then run it.
2. Launch UNetbootin. On Linux, you might have to type the root password.
3. Click on Diskimage and search for the ISO file you downloaded.
4. Select Type: USB drive and choose the correct device for your stick.
5. Click OK.
If you do not see sdX listed, you might have to reformat the drive. You can do
 this from most file manager or disk utility tools, e.g. the GNOME disk utility
("Disks") on Fedora. The FAT32 format is most likely to result in a bootable
stick. This will cause you to lose all data on the drive.
Creating a USB stick from a running live environment

If you are already running a live CD, DVD, or USB and want to convert that into a bootable
USB stick, run the following command:
# livecd-iso-to-disk /run/initramfs/livedev /dev/sdX"
Booting from USB sticks

Almost all modern PCs can boot from USB sticks. However, how you tell the system to
boot from a USB stick varies substantially from system to system. Initially, you can try this:
1. Power off the computer.
2. Plug the USB drive into a USB port.
3. Remove all other portable media, such as CDs, DVDs, floppy disks or other USB
sticks.
4. Power on the computer.
5. If the computer is configured to automatically boot from the USB drive, you will see a
screen that says "Automatic boot in 10 seconds…" with a countdown.
If you do a native UEFI boot, where you will see a rather more minimal boot menu.
If the computer starts to boot off the hard drive as normal, you’ll need to manually
configure it to boot off the USB drive. Usually, that should work like this:
1. Wait for a safe point to reboot.
2. As the machine starts to reboot, watch carefully for instructions on which key to
press. Usually a function key, Escape, Tab or Delete is to be pressed to enter the
boot device selection menu, BIOS setup, firmware, or UEFI. Press and hold that
key. If you miss the window of opportunity, often only a few seconds, then reboot
and try again.
3. Use the firmware, BIOS, interface or the boot device menu to put your USB drive
first in the boot sequence. It might be listed as a hard drive rather than a removable
drive. Each hardware manufacturer has a slightly different method for doing so.
Your computer could become unbootable or lose functionality if you
 change any other settings. Though these settings can be reverted,

you’ll need to remember what you changed in order to do so.
4. Save the changes, exit, and the computer should boot from the USB drive.
If your system has a UEFI firmware, it will usually allow you to boot the stick in UEFI native
mode or BIOS compatibility mode. If you boot in UEFI native mode and perform a Fedora
installation, you will get a UEFI native Fedora installation. If you boot in BIOS compatibility
mode and perform a Fedora installation, you will get a BIOS compatibility mode Fedora
installation.
For more information on all this, see the UEFI page. USB sticks written from x86_64 images
with Fedora Media Writer, GNOME Disk Utility, dd, other dd-style utilities, and Creating and
using live CD with the --efi option specified, should be UEFI native bootable. Sticks written
with other utilities may not be UEFI native bootable, and sticks written from i686 images
will never be UEFI bootable.
Identifying a stick on Linux

Most of the writing methods will require you to know the /dev name for your USB stick,
e.g. /dev/sdc, when using them on Linux. You do not need to know this in order to use
Fedora Media Writer. To find this out:
1. Insert the USB stick into a USB port.
2. Open a terminal and run dmesg.
3. Near the end of the output, you will see something like:
[32656.573467] sd 8:0:0:0: [sdX] Attached SCSI removable disk
sdX will be sdb, sdc, sdd, etc.
This is the name of the disk you will use. We’ll call it sdX from now on. If you
 have connected more than one USB stick to the system, be careful that you
identify the correct one, often you will see a manufacturer name or capacity
in the output which you can use to make sure you identified the correct stick.
Troubleshooting a live USB

livecd-iso-to-disk problems
Partition isn’t marked bootable
If you get the message Partition isn’t marked bootable!, you need to mark the
partition bootable. To do this, run parted /dev/sdX, and use the toggle N boot
command, where X is the appropriate letter, and N is the partition number. For example:
$ parted /dev/sdb
GNU Parted 1.8.6
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: Imation Flash Drive (scsi)
Disk /dev/sdX: 1062MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags

1 32.3kB 1062MB 1062MB primary fat16
(parted) toggle 1 boot

(parted) print
Model: Imation Flash Drive (scsi)
Disk /dev/sdX: 1062MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags

1 32.3kB 1062MB 1062MB primary fat16 boot
(parted) quit
Information: Don't forget to update /etc/fstab, if necessary.
Partitions need a filesystem label

If you get the message Need to have a filesystem label or UUID for your USB
device, you need to label the partition: dosfslabel /dev/sdX LIVE.
Partition has different physical/logical endings

If you get this message from fdisk, you may need to reformat the flash drive when writing
the image, by passing --format when writing the stick.
MBR appears to be blank

If your test boot reports a corrupted boot sector, or you get the message
MBR appears to be blank., you need to install or reset the master boot record
(MBR), by passing --reset-mbr when writing the stick.
livecd-iso-to-disk on other Linux distributions

livecd-iso-to-disk is not meant to be run from a non-Fedora system. Even if it
happens to run and write a stick apparently successfully from some other distribution,
the stick may well fail to boot. Use of livecd-iso-to-disk on any distribution other
than Fedora is unsupported and not expected to work: please use an alternative method,
such as Fedora Media Writer.
Testing a USB stick using qemu

You can test your stick using QEMU.
# umount /dev/sdX1
$ qemu -hda /dev/sdX -m 1024 -vga std
Mounting a Live USB filesystem

You can use the liveimage-mount script in the livecd-tools package to mount an attached
Live USB device or other LiveOS image, such as an ISO or Live CD. This is convenient when
you want to copy in or out some file from the LiveOS filesystem on a Live USB, or just
examine the files in a Live ISO or Live CD.
Creating and using live CD

FIXME Needs modularization
Getting started
To create a live image, the livecd-creator tool is used. For this, super user privileges
are needed.
The livecd-creator tool is part of the _livecd-tools_package. If it is not installed on your

system, add it with DNF:
# dnf install livecd-tools spin-kickstarts
If you are interested in localized (i.e. translated into other languages) live CD files, install
also l10n-kickstarts.
Configuring the image

The configuration of the live image is defined by a file called kickstart. It can include some
basic system configuration items, the package manifest, and a script to be run at the end
of the build process.
For the Fedora project, the most important live image configurations files are:
fedora-live-base.ks : The base live image system, included in the livecd-tools package.
For Fedora 20 and earlier: fedora-livecd-desktop.ks : Complete desktop with

applications and input/output support for all supported locales in Fedora. This one
is part of the spin-kickstarts package. Despite the name, this is the kickstart
that generates the ~1GB-sized images for recent releases.
For Fedora 21 and later: fedora-live-workstation.ks. This is the Workstation product

configuration.
kickstart files for other spins, e.g. Fedora Electronics Lab, can be found in
/usr/share/spin-kickstarts/ after installing the spin-kickstarts package.
These pre-made configuration files can be a great place to start, as they already have
some useful pre and post-installation scripts.
You can create a customized kickstart file by running system-config-kickstart.
You might have to install the package first with

dnf install system-config-kickstart in Fedora 22 and beyond or
yum install system-config-kickstart in earlier versions of Fedora.
This tool is mainly intended for generating kickstart files for automated
 installs, not live images, so the output will probably not be usable without
editing, but it may help you to generate particular kickstart directives.
Remember to add the line
%include /usr/share/spin-kickstarts/fedora-live-base.ks at
the beginning of your kickstart file to include the base live configuration.
Making the image

To make the image, simply issue the following command:
livecd-creator --verbose \
--config=/path/to/kickstart/file.ks \
--fslabel=Image-Label \
--cache =/var/cache/live
The name given by --fs-label is used:
As a file system label on the ext3 and iso9660 file systems. As such, it’s visible on the
desktop as the CD name.
In the isolinux boot loader.
If you have the repositories available locally and don’t want to wait for the download of
packages, just substitute the URLs listed in the configuration file to point to your local
repositories.
If you have an x86_64 machine you’re building on but you want a 32-bit
happy iso image, add the following before your livecd-creator command:
 setarch i686 livecd-creator [...]
Examples
Spinning the Fedora desktop
The following command:
--config=/usr/share/spin-kickstarts/fedora-live-workstation.ks \
--fslabel=Fedora-LiveCD \
--cache=/var/cache/live
This will create a live CD called Fedora-LiveCD using the

fedora-live-workstation.ks configuration file.
A Barebones live CD
The following command:
--config=/usr/share/doc/livecd-tools-$(rpm -q livecd-tools --qf "%{VERSION}")/livecd-fedora-minimal.ks \
--cache=/var/cache/live
This will create a live CD that will boot to a login prompt.
Testing your live CD using KVM or qemu

As root:
# qemu-kvm -m 2048 -vga qxl -cdrom filename.iso
If you do not have KVM support, you have to use qemu instead.
 # qemu-system-x86_64 -m 2048 -vga qxl -cdrom filename.iso
Replace filename.iso with the name of your created Live CD image and
qemu-system-x86_64 with an appropriate qemu binary for the target system, e.g.
qemu-system-i386.
Using your new live image

You can burn your image directly to a CD or a DVD if it fits, or you can write it to a USB
stick.
Live image media verification

The live image can incorporate functionality to verify itself. To do so, you need to have
isomd5sum installed both on the system used for creating the image and installed into the
image. This is so that the implantisomd5 and checkisomd5 utilities can be used. These
utilities take advantage of embedding an md5sum into the application area of the iso9660
image. This then gets verified before mounting the real root filesystem.
ABOUT
Get Fedora
Sponsors
Fedora Magazine
Legal
SUPPORT
Get Help
Ask Fedora
Common Bugs
Fedora Developer
Portal
COMMUNITY
Join Fedora
About Fedora
Planet Fedora
Fedora Account
System
  

Search
livecd-tools livecd-tools in other apps
Tools for building live CDs
Overview Builds Updates Bugs Contents Changelog Sources
Tools for generating live CDs on Fedora based systems including Upstream
derived distributions such as RHEL, CentOS and others. See https://github.com/livecd-
http://fedoraproject.org/wiki/FedoraLiveCD for more details. tools/livecd-tools
Active Releases Overview Package Tree

Release Latest Released Version Version in Testing livecd-tools
livecd-iso-to-mediums
Rawhide 25.0-10.fc29 None
python-imgcreate-sysdeps
Fedora 28 25.0-6.fc28 25.0-6.fc28 python2-imgcreate
1 karma python3-imgcreate
Fedora 27 25.0-1.fc27 (update) None Point of Contact

Fedora EPEL 7 None None ngompa Rawhide
Fedora EPEL 6 13.4.10-1.el6 None Latest Build

25.0-10.fc29
Recent History
2 days ago dowdle@montanalinux.org commented on RHBZ#1602046 'livecd-creator fails with
"Error creatin...'
"Error creatin...'

"Error creatin...'
11 days ago mdapi noticed a koji repomd change: libyui-mga-qt, libyui-mga-qt-devel, and 125 others
11 days ago mdapi noticed a koji repomd change: Limnoria, config, and 140 others
11 days ago dowdle@montanalinux.org filed a new bug RHBZ#1602046 'livecd-creator fails with
"Error creatin...'
12 days ago dist.python-versions FAILED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.two_three FAILED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.py3_support PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.python_usage PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.executables PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.naming_scheme PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.unversioned_shebangs PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.python-versions.requires_naming_scheme PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.rpmgrill.build-log PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.rpmgrill.desktop-lint PASSED for livecd-tools-25.0-10.fc29

12 days ago dist.rpmgrill PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.rpmgrill.man-pages PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.rpmgrill.manifest PASSED for livecd-tools-25.0-10.fc29
12 days ago dist.rpmgrill.setxid PASSED for livecd-tools-25.0-10.fc29
Found a bug on this website? File a ticket. For bugs in packages, click the "Open a New Bug" link on the packages Bugs page. Note: There's some caching going
on here. If you expect something and don't see it, check back in 5 minutes.
This Web Site is licensed under the GNU Affero General Public License. You may get sources for the current running code from these repositories:
Trademark Guidelines | Get the source for Fedora Packages | Get the source for Moksha | Fedora Packages SRPMS
DRBL
Diskless Remote Boot in Linux
About
News
DRBL/Clonezilla FAQ/Q&A
Screenshots System : About DRBL or Clonezilla
Related Articles
Download
Installation 1. Where is the corresponding DRBL client directory in the server ?
Management
2. How can I append the Linux kernel boot time parameters to the DRBL clients ?
SAN Boot
Clonezilla 3. How can I debug in the PXE initrd when clients boot ?
DRBL-winroll
4. How can I start a DRBL client service (e.g. cron, sysklogd, klogd...) in the server ?
FAQ/Q&A
Forum 5. How can I run vmplayer in the DRBL client machine ?
Mailing Lists 6. Is it possible to run a script on the client after Clonezilla finishes cloning ?
Developers
Contributors 7. When I reboot the DRBL client in Ubuntu Breezy Linux, it hangs, What should I do ?
Related links 8. How can I put my own kernel for DRBL clients ?
Custom Search 9. How can I create module for some hardware, like Nvidia, ATI VGA card, to use in client ?
10. How can I share the printer in the server to clients ?
11. How can I insert bios flash program and firmware to the freedos so that I can upgrade the BIOS in client ?
12. How to get Japanese (Chinene, Korean) input method in English environment ?
13. How can I hide the mounted NFS icons in my KDE desktop environment ?
14. What the differences between Full DRBL, Full Clonezilla, DRBL SSI and Clonezilla Box modes ?
15. How can I make a common directory where clients on any box can read, copy and delete files freely ?
16. How can I make a local apt mirror in my Debian or Ubuntu DRBL server and use that as an apt repository ?
17. How can I upgrade DRBL and related packages ?
18. How can I hide the mounted NFS share icons in KDE desktop ?
19. How can I debug the clonezilla if it fails ?
20. I have some clients which mainboard include NIC, the mainboard supports RPL. How to make the clients to support
PXE?
21. When I use clonezilla to clone MS windows, there is no any problem when saving an image from template machine.
However, after the image is restored to another machine, it fails to boot, the error message is "Missing Operating
System" or just a blinking underscore. What's going on ?
22. How can I calibrate the clock of clients ?
23. A message "tftp: client does not accept options" appears in syslog file in server , shall I do someting ?
24. Why Clonezilla can _NOT_ image from a large drive to a smaller drive? Any workaround?
25. How can I restore the image from small harddisk to larger one on Clonezilla server?
26. I am trying to restore an image of a 300 Gb drive (with 30 Gb of data) onto a 250 Gb drive, but it gives me an error that
the output drive partition doesn't have enough space to fit the image. Is there any way to restore it anyway?
27. What's the difference between clonezilla and G4L or G4U ?
28. How can I change the yum repository in OpenSuSE/SuSe before I run drblsrv ?
29. How can I assign the kernel to let client use that ?
30. If my client computer only supports RPL instead of PXE, can it work with DRBL ?
31. I am sure that the GNU/Linux I have is compatible with the GNU/Linux distribution which DRBL supports, how can I
install drbl on that ?
32. I put a script file like "myscript.sh" in /usr/share/drbl/prerun/drbl, /usr/share/drbl/postrun/drbl, and I check the option "-
o0/--run-prerun-dir", or "-o1/--run-postrun-dir", but mscript.sh is not run. Why ?
33. How can I add a package, say ncpfs, in Clonezilla live ?
34. How can I create my own custom script to run in clonezilla live ?
35. What if I have 2 or more squashfs files (filesystem.squashfs) in my system, how can I assign clonezilla live to boot ?
36. How can I compile a kernel module in the DRBL client so that I can use it for DRBL clients ?
37. How can I compile a kernel module on DRBL server so that it can be used for DRBL clients ?
38. How can I mirror drbl packages ?
39. There is an existing DHCP service in my environment, so it's impossible for me to use the dhcp service comes with
DRBL server. Any solution ?
40. I have a weird problem when restoring an image. I always got an error message "Can't read the following volume file: ...
/stdin.001".
41. How can I remaster Clonezilla iso file ?
42. How can I put the kickstart file for netinstall GNU/Linux ?
43. How can I configure FreeBSD network installation in DRBL server ?
44. How can I restore those *.ntfs-img.* images into a partition manually ?
45. Is that possible I can read the content of an image (e.g. sda1.ext4-ptcl-img.gz.*) created by Clonezilla ?
46. Is there any way I can save image to CD-RW or DVD-RW directly ?
47. Is that possible I can put clonezilla live in my harddrive which already has an OS installed ?
48. How can I create Clonezilla live from scratch?
49. When I use Clonezilla server edition to do a multicast clone, the client machines just keep waiting, any hint ?
50. I'd like to translate DRBL/Clonezilla to other language, how can I help ?
51. How can I config my DRBL clients to use Active Directory authentication ?
52. How about the unique license key for each MS windows machine after I clone them ?
53. I have a class B subnet, the range is 172.16.0.1 - 172.16.31.254, how can I configre DRBL to fit this range ?
54. What's the difference between multicast, broadcast and unicast function in Clonezilla SE ?
55. How can I run Clonezilla live using serial console ?
56. How to put my own binary driver in Clonezilla live without modifying /live/filesystem.squashfs ?
57. How can I compile and put an extra module on Clonezilla live ?
58. Is that possible I can save Clonezilla image on a rewritable CD/DVD directly when using Clonezilla live ?
59. How much space do I need when saving an image ?
60. Why stable and testing Clonezilla live are based on Debian, but alternative one is based on Ubuntu ?
61. How can I make Clonezilla SE (DRBL) server as a RIS server, too ?
62. How to add MAC addresses of new clients in DRBL ?
63. Is there a way to make a hardware independent image with CloneZilla?
64. Is that possible I can hack my buggy PXE bootrom ?
65. I got a "tftp timeout" error on my DRBL client...
66. Clonezilla live gives me "kernel panic" or can not detect my hard drive, network card... Any solution ?
67. Where can I find the DRBL live or Clonezilla live source codes ?
68. Does Clonezilla support RAID ?
69. How can I enable sudo privilege for an account on clients ?
70. Using multicast clone on Clonezilla SE, for one client the speed is fast, but more than one, it's very slow. Any idea ?
71. How can I restore those *-ptcl-img.* images into a file manually ?
72. What are the differences between partclone and ntfsclone ?
73. How can I create my own recovery Clonezilla live CD or USB flash drive ?
74. How to use DRBL with existing Altiris setup ?
75. After I restored an image to my Macbook, it fails to boot. Any method to make it boot again?
76. How can I modify the contents of initrd.img from Clonezilla live?
77. How can I use the recovery-iso-zip function if I use PXE to boot Clonezilal live?
78. How can I modify the settings of DRBL SSI mode? e.g. the bash prompt?
79. How to create an autorun recover Clonezilla live?
80. How to Build and Install Partclone on Fedora 11 x86_64?
81. What are the compression options in Clonezilla? What are the differences?
82. I'd like to customize the Clonezilla boot menu, any doc I can refer?
83. I have more than 1 network card on my DRBL client, how can I force the client to use the specific network card, i.e. with
priority, to connect to DRBL server when booting in the initramfs?
84. How can I add a program in the main file system of Clonezilla live, i.e. in the file "filesystem.squashfs"?
85. I knew the network card of my DRBL client is supported by the kernel, however it fails to load the module during PXE
booting. What can I do?
86. When I save an image, I see messages like "{ DriveReady Error }" or "{ DriveReady DataRequest Error }", what can I
do?
87. How can I re-registering the individual MS Office installations with their own keys after the system is restored by
Clonezilla?
88. I got the error message "invalid or corrupt kernel image" when I boot clonezilla live CD, any hints?
89. I got an error "0xc00000e" after my MS Windows 7 image was restored. Any solution?
90. How can I create Clonezilla live iso file from clonezilla live zip file?
91. What do these restore options (-g auto, -t, -t1, -j1, -j2, -k, -k1, -j0, -r...) actually do?
92. How to save the image to external TrueCrypt harddisc?
93. I got an error message like "FS has been mounted 3234324234 times without being checked" in Clonezilla live. What
can I do?
94. I have put some prerun and postrun scripts in DRBL server, but it does not work. What happends?
95. I sent you an email directly from my sourceforge account, but I did not get any response. Why?
96. Why Clonezilla does not use fsarchiver as the engine?
97. After I restore the MS windows image, I got error messages about "0xc0000225, 0xc00000e", and something about
Winload.exe, any hint?
98. Any workaround that I can save and restore RAID 1 (mirrored) disk by Clonezilla?
99. Is there any method I can brodcast messages to DRBL clients?
100. What are the differences between i486, i686, and amd64 version of Clonezilla live?
101. How can I restore an image to multiple hard drives simultaneously?
102. Do I have to have a destination drive already formatted before trying to restore an image on it?
103. Is there any method I can resize my LVM device?
104. Is that possible I can clone the MS Windows partition to different order of partition on another disk?
105. How can I restore an image of a partition to different partition, e.g. restore the image of /dev/sda5 to /dev/sda6?
106. Is Clonezilla compatible with "WD Advanced Format" disk?
107. How can I can provide PXE service on a MS windows machine?
108. How can I use LDAP instead of NIS/YP in DRBL server?
109. How can I skip the prompt "Please remove the disc, close the the tray (if any) and press ENTER to continue" when
rebooting or shutdowning the Clonezilla live?
110. Is that possible to run Clonezilla-live using windows 2008 & wds?
111. I got an error message "extfsclone.c: bitmap free count err, free:...", any idea?
112. I have some Broadcom gigabits NICs, and it is not supported by Clonezilla live, why? How to support it?
113. After I did a disk-to-disk clone, my MS Windows in the source disk fails to boot. Why?
114. Possible solutions when connection drops or CRC-error message with Clonezilla.
115. Any hints about creating a customized unattended, automatic restoring (or saving) mode about Clonezilla live?
116. After restoring, grub2 complains "error: no argument specified". Why?
117. Is that possible I can restore a MS Windows image to different hardware?
118. I got a message "This disk contains mismatched GPT and MBR partition". What's that?
119. When I restored an image to the same, original SSD disk, Clonezilla complained the destination disk is too small.
What's wrong?
120. I got an error message like "extfsclone.c: FS was not cleanly unmounted" or ".extfsclone.c: bitmap free count err,
free:..." when saving an image? Any hints?
121. Is that possible I can restore to smaller HDD when the image was taken from bigger one?
122. Can I save the image on the same USB drive of Clonezilla live?
123. Any method to do a "PXE" booting for my Mac?
124. Does Clonezilla support Mac's fusion drive or Core storage?
125. When I use DRBL live, my client machines have an error "NFS over TCP not available from ..."?
126. How can I use VPN connection in Clonezilla live environment?
127. How can I change the passphrase of Clonezilla image?
128. I'd like to use http service instead of tftp service for my PXE clients to download the Clonezilla live root file system
(Clonezilla-live-filesystem.squashfs). What shall I do?
129. How can I disable the beep sound when booting Clonezilla?
130. I have a problem with the default tftp block size 64540 when PXE booting, any good solution?
Is that possible I can read the content of an image (e.g. sda1.ext4-

ptcl-img.gz.*) created by Clonezilla ?
Yes, but it's not straightforward. Here you are:
Method 1: Use Clonezilla live to restore the image to a virtual machine (e.g. VMWare workstation
or Virtual Box). Then mount the restored partition to read the contents.
Method 2:
1. Prepare a large disk in Linux
2. Say if your image is /home/partimag/YOURIMAGE/, if the image is like
/home/partimag/YOURIMAGE/*-ptcl-img.* (e.g. /home/partimag/YOURIMAGE/sda1.ext4-
ptcl-img.gz.aa), follow this to restore the image.
If the the image is like /home/partimag/YOURIMAGE/sda1.ntfs-img.aa, sda1.ntfs-img.ab...,
run
"file /home/partimag/YOURIMAGE/sda1.ntfs-img.aa"
to see it's gzip, bzip or lzop image. Say it's gzip, then you can run
cat /home/partimag/YOURIMAGE/sda1.ntfs-img.* | gzip -d -c | ntfsclone --restore-image -o
sda1.img -
Then you will have a "sda1.img" which you can mount it by
mount -o loop -t ntfs sda1.img /mnt
Then all the files are in /mnt/
You can do the similar thing for the ext3, ext4 or reiserfs file system.
Method 3: Use the tool partclone-utils to mount the image directly. (//NOTE// This program is not
maintained by Clonezilla team. However, it will be included in the future release of partclone when
the new release, e.g. 0.2 is released.). The example to use partclone-utils to mount the image,
and still you need to prepare enough disk space for that:
Boot Clonezilla live
Mount the image repository, as normal usage when restoring. However, do not restore the
image. Here we just need to read the image
The following commands have to be run as root (administrator). Therefore run "sudo -i" to
become root. Say if your image is /home/partimag/YOURIMAGE/, if the image is like
/home/partimag/YOURIMAGE/sda1.ext4-ptcl-img.gz*, from the file name you know its file
system is ext4, and is gzipped. You can run
cat /home/partimag/YOURIMAGE/sda1.ext4-ptcl-img.gz.aa* | gzip -d -c >
/home/partimag/my-sda1-img
This command will generate a single uncompressed image file "my-sda1-img" in the dir
/home/partimag/.
modprobe nbd
imagemount -d /dev/nbd0 -f /home/partimag/my-sda1-img
mount -t ext4 /dev/nbd0 /mnt
Now you have all the files in the dir /mnt/.
When everything is done, you can:
umount /mnt/
pkill imagemount
<< >>
DRBL-Winroll - A MS-Windows extension tool
MS Windows extension tool over DRBL environment
It supports Windows client to accecpt command from DRBL server and to solve related problems via using image clone tool on MS winodws.
*********** Welcome to use DRBL-Winroll ***********
Free Software Labs , NCHC ,Taiwan
GPL
ceasar _at_ nchc org tw, steven _at_ nchc org tw
*******************************************************
Download Installation Other tool Screenshot Documents i18n Forum Mail List Credits
DRBL-Winroll is a tool that enables MS-Windows client to accept commands from DRBL Page Index
server, and it resolve windows hostname, SID duplication problem via using image clone
tool at single local LAN.It can also adjust "workgroup" name and Windows network Download
configuration automatically. Installation
How to configure Windows HOSTNAME format
Feature : via DRBL-Winroll ?
How to configure WORKGROUP name via DRBL-
Winroll ?
Adjust Windows hostname, workgroup name, SID automatically How to auto-setup Network Configuration ?
Provide network auto-setup function How to auto-add to AD domain
Provide auto-add to AD domain functionNEW from v1.3.0 How to setup Monitor daemon for Windows
clients
Prodive system monitor service in Windows clientsNEW from v1.3.1 How to renew MS Windows SID ?
Install sshd service How to make Windows clients to accept the
Compatible with other image clone tool (like: Clonezilla, Ghost, Acronis True Image, commands form DRBL server automatically ?
.etc) to be able to restore large-scale windows system by utilizing one template Language Supports
image Others
License :
DRBL-Winroll itself is licensed under GNU GPL

It incorporates code from wsname and newsid porjects, each of which has its own license terms
Standard disclaimers apply
1. Download
Stable Version : [Donwload]

Testing Version: [Download]
Support : Windows 2000/ Windows XP/Windows 2003/Vista/Windows 7/Windows 2008
Note :
If you need md5sum check tool for Windows : md5summer
If you need unzip tool for Windows, we suggest 7-zip
This project use NSIS to package as executable installer. The winroll.nsi file is stored in ~/drbl-winroll/tool
2. Installation
EXE:
1. Download drbl-winroll-setup-x.x.x-setup.exe then execute it
ZIP:
1. Unzip the package : drbl-winroll-x.x.x-setup.zip
2. Execute the "winroll-setup.bat" , and the program will lead to complete installation
Note :
1. Please install the package with Administrator(s) privelege (Option: Make sure Internet connection is work fine if you need install
newsid program from Internet)
2. Please remove cygwin if you had installed it before; Or, use 『Install over』 option to install
3. For Vista or Windows 7/2008 OS, please refer here to disable UAC function before installation。If you still need UAC
function, please re-enable it after installtion.
Start to install DRBL-Winroll

[More]
3. How to configure Windows HOSTNAME format via DRBL-Winroll ?
By default, DRBL-winroll use the last six numbers of IP with one prefix string : "PC" as HOSTNAME for Windows, ex:
IP is 192.168.1.52 , the its hostname would be : PC-001-052
You can follow the steps to change HOSTNAME format :
1. [Programs]-> [Cygwin]-> [drbl_winroll-config] , to edit "winroll.conf"
2. Find out the follow line then replace the parameter :

HN_WSNAME_PARAM = xxxx
The parameter guide is as follow :
# HN_WSNAME_PARAM = /N:PC-$ZFIP[3+] (Last IP (ex:192.168.1.52) 3 chars with zero-filled, got:'PC-052'. Due to IP string
became to '192-168-001-052'；As default vaule.)
# HN_WSNAME_PARAM = /N:PC-$ZFIP[4+] (Last IP 4 chars with zero-filled, got:'PC--052')
# ----- Other common parameters

# HN_WSNAME_PARAM = /N:PC-$MAC (ex: PC-000C294EEF53)
# HN_WSNAME_PARAM = /N:PC-$MAC[+8] (First 8 codes of Mac Adress ", ex: PC-000C294E)
# HN_WSNAME_PARAM = /N:PC-$IP[3+] (Last 3 characters of IP, got: 'PC--52'. Due to IP string became to '192-168-1-52')
# HN_WSNAME_PARAM = /N:PC-$IP[4+] (Last 4 characters of IP, got: 'PC-1-52')
3. Advaced mode : By config file

DRBL-winroll also provide to setup HOSTNAME by a config file from local. Please edit "HN_WSNAME_PARAM = xxxx " as the follow:
HN_WSNAME_PARAM = /RDF:C:\cygwin\drbl_winroll-config\hosts.conf /DFK:$MAC
Note: /RDF define the path of local file, /DFK define the field for searching key
A reference format in hosts.conf is : "IP or MAc Address" = "hostname" , the follow for more detail :
00-0C-29-4E-EF-53 = Student-01 # (Assign "Student-01" as hostname if its MAC address is 000C294EEF53 )
192-168-1-12 = Student-02 # (Assign "Student-02" as hostname for IP address is 192.168.1.12 client. Replace dot '.' symbol
with dash '-')
Note: Hostname would be assigned as "Student-01" via /DFK:$MAC ; /DFK:$IP it would be "Student-02"
By this way, mananger can define hostname free! But we suggest you to collect all MAC address in template macine first. The other
cloned machines would be named hostname automatically.
PS:
In DRBL-Winroll, it changes the hostname by wsname tool. So the format of hostname we provide is fully consistent with wsname tool so far.
Windows have to reboot if its HOSTNAME or WORKGROUP be changed
4. How to configure WORKGROUP name via DRBL-Winroll ?
DRBL-winroll provides three options :

1. By fix string , ex: WG
2. By IP/Netmask, ex: GROUP-$NM
Use Windows IP address compared with Netmask and add a prefix string : "WG" (you can edit it in winroll.conf) as WORKGROUP
name, ex :
ip:192.168.20.2 NM:255.255.255.0=> workgroup will be "GROUP-020"
ip:172.18.1.5 NM:255.255.0.0 => workgroup will be "GROUP-018-001"
3. By DNS Suffix : $DNS_SUFFIX
DNS SUFFIX is one of IP information from DHCP service. On this option, DRBL-Winroll would use the fisrt two string (ex: get
"nchc.org" form "nchc.org.tw") then replace "." with "-" (ex: "nchc.org" -> "nchc-org" ). You can use "ipconfig /all" command
to show "DNS Suffix " information on Windows OS.
DNS Suffix Search List. . . . . . : my.org.domain=> WORKGROUP will be "WG-my-org"
Note :
DRBL-Winroll use FIX STRING "WG" as default format for WORKGROUP
5. How to use auto-setup Network Configuration via DRBL-Winroll ?
DRBL-Winroll provide 3 options to setup Windows network automatically. Open [Programs] -> [Cygwin]-> [drbl_winroll-config] ,
find out the follow parameter and edit it in "winroll.conf" CONFIG_NETWORK_MODE = xxxx
The parameter guide is as follow :
CONFIG_NETWORK_MODE = dhcp (use DHCP method)
CONFIG_NETWORK_MODE = /RDF:C:\cygwin\drbl_winroll-config\client-mac-network.conf (By config file from local)
CONFIG_NETWORK_MODE = none (skip network configuration, even no use dhcp )
1. DRBL-Winroll use DHCP as default for Windows clients
2. Advanced mode : By config file

Make sure CONFIG_NETWORK_MODE = /RDF:C:\cygwin\drbl_winroll-config\client-mac-network.conf in winroll.conf,
then edit c:\cygwin\drbl_winroll-config\client-mac-network.conf
The follow is a sample for client-mac-network.conf :
_DEFAULT_NETWORK = 192.168.100.254/24 # assign network and netmask

_DEFAULT_GATEWAY = 192.168.100.254 # assign default gateway
_DEFAULT_DNS = 168.95.1.1 # DNS, it could be empty, one or many values (use "comma"(,) as separated )
_DEFAULT_WINS = 192.168.100.1 # WINS, it could be empty, one or many values (use "comma"(,) as separated )
_DEFAULT_DNS_SUFFIX = # DNS_SUFFIX, it could be empty,
subnet 10.0.2.0/8 {
THIS_GATEWAY = 10.0.2.2 # use 10.0.2.2 as default gateway for this network
THIS_DNS = 10.0.1.1 # use 10.0.1.1 as default DNS for this network
THIS_WINS = # Use nothing as _DEFAULT_WINS value
# This subnet would inherit the "_DEFAULT_DNS_SUFFIX" value form global settings
# because no set value for it in this session
}
subnet 192.168.0.0/24 {
THIS_GATEWAY = 192.168.0.254
T H I S _ D N S = 1 9 2 . 1 6 8 . 0 . 1
#THIS _WINS
# This subnet would inherit "_DEFAULT_WINS" and
# "_DEFAULT_DNS_SUFFIX" value form global settings
}
[IP Address]
00-00-00-00-00-01 = 192.168.100.11
00-00-00-00-00-02 = 10.0.2.30 # it would use settings of subnet 10.0.2.0/8
00-00-00-00-00-03 = 192.168.0.7 # it would use settings of subnet 192.168.0.0/24
00-00-00-00-00-04 = dhcp # uses dhcp
00-00-00-00-00-05 = none # skip this NIC
3. There two samples for network cofiguration in c:\cygwin\drbl_winroll-doc\sample\

client-mac-network.conf.1.sample : For single subnet
client-mac-network.conf.2.sample : For multiple subnets
6. How to setup auto-add to AD domain function ?
1. Follow the installation step and input necessary information (AD domain name, valid user
account and password)
2. After mass deployment, clients would show the message of domain modification and reboot
by themself. As the right image show :
Explanation :
What to setup : After it added the audo-add to AD function, system would add a batch file
"add2ad.bat" in 'c:\cygwin\drbl_winroll-config\'. The contents as the follow：
netdom join %computername% /domain:[DOMAIN] /userd:[USER] /passwordd:
[PASSWORD] /reboot:8
How to work ：Client will execute the batch file untill system is ready (it means to already
done for hostname fix, network environment...). If it succeeds, system would delete the
batch file automatically for security issue (due to user account and password) and create a
new file "c:\cygwin\drbl_winroll-config\add2ad.md5". It records a value that the md5sum
result for this machine's phyical address of NIC
Note :
System use netdom.exe command to do the auto-add to AD function. So, please make sure netdom.exe is ready in it. (Suggest to
test if netdom.exe command works under command mode)
Windows XP : please refer here
Windows Vista : please refer here
Windows 7/Server 2008 : please refer here
For do the mass deployment, please DO NOTadd to AD domain before you image it as a template. It also avoid to reboot it into
Windows system after DRBL-winroll installation (Because that will lead to client add to AD domain too)
Need to renew SID ? Clients don't need to renew SID if it use Windows 2003 (or later) as AD server. It can work fine that clients
have different hostname but the same SID in domain. Of course, DRBL-winroll can do it after clients renew SID if necessary
7. How to setup system monitor service for Windows clients ?
DRBL-winroll integrate Munin Win32 project as system monitor/ tool. Munin is a networked resource monitoring tool with server-client
architecture. The explanations of insatllation and configuration would be presented in two parts : client site and server site.
Client site
1. During installing, it would query if to install system monitor service. Please type "y" then press [Enter] (default by 'No'). The
"Munin Node for DRBL-winroll" installer will popup and start to install daemon, show as follow：
Munin Node for DRBL-winroll Installer

2. Follow the steps to complete installation
Server site
1. For example : use Ubuntu Lucid, suggest to pre-install apache2 to easy view the reports of clients system via web, then install
munin package, as the follow
sudo apt-get install apache2 munin munin-node
2. Download DRBL-winroll Server-site package server-site-*.tgz then unpack it.Excute gen_munin_clients_conf.sh to collect
clients' informaction as configuration file. As the follow :
$ tar xzf server-site-v167.tgz ; cd server-site ; sudo ./gen_munin_clients_conf.sh
3. Script would get ip/hostname of clients for report via user assignment, then output to a configuration for Munin, named:
"munin-winroll-clients.conf" . It would help user to configure and restart crontab in server for supported Linux distribution.
As the follow:
Get ip list from DRBL server [Y/n]y
Domain name [domain.localdomain]
Set domain name as : domain.localdomain ...
Get clients hostname via Munin service ? Default from local /etc/hosts [N/y]
Still to keep the record if get hostname fail (to use ip as hostname) [N/y]
get hostname of '192.168.101.1' :PC101
Total 3 record(s) done in 'munin-winroll-clients.conf'
Please copy the file into correct folder for Munin (ex: /etc/munin/munin-conf.d) then restart munin daemon (ex: $ sudo -u
munin munin-cron)
4. If need, please copy the configuration file into correct directory for Munin server (ex: /etc/munin/munin-conf.d in Ubuntu Lucid
) then restart munin-cron to create necessary data for report. As the follow:
$ sudo cp munin-winroll-clients.conf /etc/munin/munin-conf.d ; sudo -u munin munin-cron
Where to view report
It would be easy to view the report by web page via http://localhost/munin on monitor server. By default, Munin report web only be
accessible from localhost. Please refer Munin document for details about remote access and security issue.
Note :
Acknowledge :Thansk to Munin Nodes win32 project. DRBL-winroll do repackage the installer via NSIS. Users can refer the NSIS
configuration in ~/drbl-winroll/tool/munin-node-winroll.nsi if needs
8. How to renew MS Windows SID ?
1. Please choose (and pre-download) your renew sid tool that support to run as command mode, ex:NewSID v4.10; Answer 'y' to
setup "SID-check" service, give the full path of tool (an executable file) and the appropriate parameters for it(ex: use '/a /n' for
newsid.exe). As the follow :
Setup 'SID-check' service

2. Service would record NIC mac address of Windows machine, it would give a new SID if service discover a new one mac address.
3. For security reason , SID should be given randomly, And service would encode the mac address what it discover via md5sum
4. DRBL-Winroll would startup first time after installation finished if you did setup 'SID-check' service. Please wait until system reboot
by itself.
Firt time to start SID-check service after installation and wait until system reboot by itself
Note: Some news about "NewSid Retired ?" [1] [2]
9. How to make Windows clients to accept the commands form DRBL server automatically ?
If you want to your windows clients can accept the commands from DRBL server, please follow the step:
0. Switch to root in your DRBL serer. Make sure do "id_rsa" and "id_rsa.pub" exist in /root/.ssh , jump to stpe 3 if yes.
1. Create root's ssh keys (private and public key) , and press [Enter] when it asks "passphrase " ( mean no passphrase)
$ ssh-keygen -d
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
fe:56:XX:XX:XX:XX:XX:XX:XX:XX:83:ff:42
root@drbl-server
2. It would create "id_rsa" and "id_rsa.pub" in /root/.ssh, ex:
$ ls /root/.ssh
id_dsa id_dsa.pub
3. "Copy" (ex: use "scp" command or usb flash) id_rsa.pub from DRBL server to Windows and save the file name as
"authorized_keys" in Administrator's .ssh folder of cygwin home directory (c:\cygwin\home\administrator\.ssh), ex :
c:\your\windows\path> copy [path-of-id_dsa.pub] c:\cygwin\home\administrator\.ssh\authorized_keys
Or use "ssh-copy-id" command on DRBL server to transmit
sudo ssh-copy-id -i ~/.ssh/id_rsa.pub administrator@[win-client-ip]
Store public key in c:\cygwin\home\administrator\.ssh named as "authorized_keys"
4. you can test the result via to send a command from drbl server to MS-client. It would not ask password if you setup the above
steps correctly ,ex:
$ ssh administrator@[win-client-ip] ipconfig
5. After all, you can send a command to clients from DRBL server via "/opt/drbl/sbin/dcs" command.
Note :
Except Windows NT and Windows XP, DRBL-winroll would create a new account "cyg_server" as ssh daemon runner. So, please DO
NOT change its password or disable it. That would lead to ssd daemon be out of service.
For security issue, its password be created by random with 8 strings and be stored in "C:\cygwin\drbl_winroll-
config\SSHD_SERVER_PW.txt" file。
10. Language Support
DRBL-winroll suppports the follow languages, and thanks the people's effort in language transaltion and testbed report !!
Traditional Chinese
English
French : Joël Gondouin (joel_at_gondouin_net)
Dutch : Dave Haakenhout (Almere, Netherlands)
Swedish : Yngve Spång (Systemkonsult AB)
Spanish : Artz Neo (artzneo_at_linuxmail_org)
Help us to translate !![How to]
11. Other
Text FAQ : [ Chinese ][English ]

Web FAQ : Read here
History : Read here
Other Tools
[Stable]
EZ command sender : EZ-commands
Description: A easy toolkit to send commands from windows client to server
[Testing]
User desktop recover tool : winroll-recover
Description: Windows user desktop recover tool. More detail please read inside document.
DRBL-Winroll is powered by Free Software Lab , NCHC, Taiwan

Log in
Installing PCLinuxOS
Contents [hide]
Main page 1 Basic Hard Drive Installation of PCLinuxOS
Recent changes 2 Getting Started
Random page
3 Format and Partition your Hard Drive
Help
4 Custom Disk Partitioning
Tools 5 Copying PCLinuxOS files to Hard Disk
6 Setting up Grub Boot Loader
What links here
Related changes 7 Installation Complete: Reboot
Special pages 8 First Boot
Printable version 8.1 User & Password configuration
Permanent link 9 Getting Help
Page information 9.1 IRC Chat
9.2 Community Forums
Basic Hard Drive Installation of PCLinuxOS

The following information will assist you in the installation of PCLinuxOS to either your PC or Laptop:
Note: If you wish to keep Microsoft Windows, you need to defragment your hard drive before installation.
Note: If you wish to install on a USB, please see this page: Installing without CD/DVD
Getting Started
Click on the Install PCLinuxOS Icon on your desktop to start the installation process, you will be asked for the root password. The password
for root is of course root.
Format and Partition your Hard Drive

Now you need to partition and format your hard drive. Please be very careful with your selection. If you select Use existing partitions or Erase
and use entire disk it will auto select and FORMAT your partitions. All data on those partitions will be lost forever. In addition if you have
Windows installed an additional option will be presented allowing you to re-size the windows partition to make room for Linux. This is an
experimental feature and should be used with caution. Please make sure you have your Windows partition backed up before attempting to
re-size it.
Custom Disk Partitioning

If you wish you can use Custom disk partitioning. Lets start by partitioning the hard drive.
You need to set up 3 partitions. A swap partition, a /home partition and a / partition (known as root). The swap partition is a temporary
storage area in the event you run out of memory. Linux can swap memory to and from the swap partition as needed. As a general rule your
swap partition should be double your memory.
Now we have our swap partition created.
Next we need a / partition. This is where all your data and programs are stored. A minimum of approx 4 gigs (4096 mb) is required though
you probably want to make it at least 10 gigs (10240 mb) if you wish to install additional programs from the repository. Please note the default
file system type is ext4. You cannot install Linux to a fat32 or ntfs formatted partition.
Now we have our /root partition created.
Finally we need to set up a /home partition. This is where you can store your personal data. The size of the home partition depends on your
personal needs. Since I am using a small hard drive I selected about 2.0 gig (2000 mb). On large hard drives I would recommend at least 10
gigs (10240 mb) or larger.
Now we have our /home partition created.

In some situations where you have deleted and re-created partitions the installer will identify a partition as native ext2. In the event this
happens please press the Toggle to expert mode and select Type and change it to Journalised FS: ext3.
Now we have our hard drive set up with a swap partition, a /home partition and a / partition. We are now ready to format the hard drive
partitions and begin the installation.
The install is now formatting your partitions.
Copying PCLinuxOS files to Hard Disk

We are ready to copy the system files from the livecd to your hard drive. This process takes between 10-20 minutes depending on the speed
of your computer.
Setting up Grub Boot Loader

Once the files have been transferred to your hard drive we need to set up the boot loader so that your new install can be booted from the
hard drive. The system defaults to Grub Graphical as the default boot loader. If this is your only Linux install you can select to install to the
MBR or Master Boot Record. If you already have previous Linux installs on other partitions you can select to install the boot loader to the
partition for chain loading.
The Master Boot Record (MBR) will always be identified without a partition number such as /dev/hda, /dev/sda or /dev/sdb. As an example, if
your /home partition and / partition is on /dev/hda5 and /dev/hda6 etc, you would install your boot loader to /dev/hda. If your /home partition
and / partition is on /dev/sdb5 and /dev/sdb6 etc, you would install your boot loader to /dev/sdb. For our installation we will just choose the
default selection.
These are the default entries. If you have other Linux installs, you can add them here.
Now we save our selection.
Installation Complete: Reboot

The installer has finished installing PCLinuxOS to your computer and you are ready to shut down and reboot.
First Boot
User & Password configuration
On first boot you must set up a new root password. This is your administrator access password. Normally you run Linux as a user and elevate
yourself to root access only when you need to perform various system functions. This keeps Linux safe and secure. Write your root password
down and keep it in a safe and secure place. If you forget your root password you wont be able to perform system tasks such as adding
software or configuring your system.
Enter the user name and password you will be using to log into the system. Once you are finished click the Next button.
Getting Help
IRC Chat
If you run into something you don't understand please click on XChat from the PCMenu > Internet > Xchat IRC and it will log you into our help
channel.
Community Forums
Help can also be found by searching and/or posting questions to the PCLinuxOS Community Forum
Good luck!
Category: HowTo

Home  Fedora Installation Guide  Installing Fedora  Preparing for Installation
 Fedora Release Notes

 Fedora Installation Guide
Book Information
Preface
Introduction
Downloading Fedora
 Installing Fedora
Preparing for Installation

Booting the Installation
Installing Using Anaconda

After the Installation
Troubleshooting
 Advanced Installation Options
 Technical Appendixes
Revision History
 Fedora System
Administration Guide
Preparing for Installation

This chapter describes the steps you need take before you begin the installation. Not
every step must be strictly followed - for example, if you plan to use the default installation
settings, you do not need to gather system information such as disk device labels/UUIDs
or network information such as the system’s IP address. However, you should still go
through this chapter, as it also describes the available types of installation media and how
to prepare boot media and installation sources.
Upgrade or Install?
If you already have Fedora installed and want to upgrade your installation to the current
version, there are two basic ways to do so:
Automatic upgrade using dnf system upgrade

The preferred way to upgrade your system is an automatic upgrade using the dnf system
upgrade utility. For information on performing an automatic upgrade, see Fedora Wiki dnf
system upgrade.
Manual Reinstallation
You can upgrade to the latest version of Fedora manually instead of relying on dnf system
upgrade. This involves booting the installer as if you were performing a clean installation,
letting it detect your existing Fedora system, and overwriting the root partition while
preserving data on other partitions and volumes. The same process can also be used to
reinstall the system, if you need to. For detailed information, see Manual System Upgrade
or Reinstallation.
 Always back up your data before performing an upgrade or reinstalling your

system, no matter which method you choose.
Downloading Boot and Installation Images

The Fedora Project offers different Editions tailored for some specific use cases. Choose
the Fedora Edition best for you, or you can build your own by customizing after the
installation, or by using a kickstart file as described in Creating a Kickstart File. Kickstart
installation requires the netinstall media type, or a direct installation booting method
such as PXE; kickstarts are not supported with live images.
Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available
media types in Downloading Fedora.
You can also choose a Fedora Spin featuring favorite alternative desktops or tools for
specialized tasks at http://spins.fedoraproject.org.
Verifying the Downloaded Image

Because transmission errors or other problems may corrupt the Fedora image you have
downloaded, it is important to verify the file’s integrity. After the images are created, an
operation is performed on the file that produces a value called a checksum using a
complex mathematical algorithm. The operation is sufficiently complex that any change
to the original file will produce a different checksum.
By calculating the image’s checksum on your own computer and comparing it to the
original checksum, you can verify the image has not been tampered with or corrupted.
The original checksum values are provided at https://fedoraproject.org/verify, and are gpg
signed to demonstrate their integrity.
Verifying checksums on Windows systems

Verifying checksums on Windows systems
1. Download the Fedora image of your choice from https://fedoraproject.org/get-
fedora and the corresponding checksum file from https://fedoraproject.org/verify
2. Open a powershell session.
3. Change to the directory containing the downloaded files.
> cd $HOME\Downloads\
> ls
Directory: C:\Users\Pete\Downloads
Mode LastWriteTime Length Name

---- ------------- ------ ----
-a--- 11/25/2014 12:39 PM 272 Fedora-Server-21-x86_
64-CHECKSUM
-a--- 11/25/2014 12:39 PM 2047868928 Fedora-Server-DVD-x86
_64-21.iso
4. Load the resources required to calculate the checksum.
> $image = "Fedora-Server-DVD-x86_64-21.iso"

> $checksum_file = "Fedora-Server-21-x86_64-CHECKSUM"
> $sha256 = New-Object -TypeName System.Security.Cryptography.sha256Cry
ptoServiceProvider
> $expected_checksum = ((Get-Content $checksum_file | Select-String -Pa
ttern $image) -split " ")[0].ToLower()
5. Calculate the downloaded image’s checksum. This will take a while!
> $download_checksum = [System.BitConverter]::ToString($sha256.ComputeH

ash([System.IO.File]::ReadAllBytes("$PWD\$image"))).ToLower() -replace
'-', ''
6. Compare the calculated checksum to the expected checksum.
> echo "Download Checksum: $download_checksum"

> echo "Expected Checksum: $expected_checksum"
> if ( $download_checksum -eq "$expected_checksum" ) {
echo "Checksum test passed!"
} else {
echo "Checksum test failed."
}
Verifying checksums on Linux and OSX systems

Verifying checksums on Linux and OSX systems
1. Download the Fedora image of your choice from https://fedoraproject.org/get-
fedora and the corresponding checksum file from https://fedoraproject.org/verify
2. Open a terminal window, and navigate to the directory with the downloaded files.
$ cd ~/Downloads
3. Use the appropriate utility to verify the image checksum.
For Linux:
$ sha256sum -c *CHECKSUM
For OSX:
$ shasum -a 256 -c *CHECKSUM
Preparing Boot Media

Fedora images are Hybrid ISOs and can be used to create installation media with both
optical and USB disks, for booting on both BIOS and UEFI systems.
Fedora Media Writer and Universal USB Creators

Fedora Media Writer has been improved and is now the default way to make
bootable media. Fedora Media Writer supports Linux, Mac, and Windows. It
is an easy way to make bootable USB media to install Fedora (or other
operating systems). While use of Fedora Media Writer is strongly
encouraged, other USB media creation software can work as well.
Some of the new additions to Fedora Media Writer are that Fedora
Workstation and Server are the first choices on the main screen. However
more choices are available if you select the button below "Custom OS".
Options like Fedora Spins will appear. Fedora Spins such as XFCE and Mate
 will be selectable.
Universal USB creation tools such as Unetbootin are a historically popular

way to create USB installers from ISOs intended for optical media. They
typically function by creating a filesystem on the USB drive, extracting files
from the image, and writing syslinux bootloader to the device.
These methods circumvent the boot-loader configuration built into Fedora

images, which are pre-partitioned and designed to boot on UEFI systems
with SecureBoot enabled as well as BIOS systems. They do not produce a
consistent result with Fedora’s images, especially for use with UEFI systems.
Utilities that use a direct write method, and do not modify the Fedora image,
will produce the most consistently successful results.
Be sure you choose the right device!
Most media creation methods in this section are destructive. Ensure you do not
need any data on the USB stick, and double check you have chosen the correct
device before continuing.
Creating USB Media on Windows

1. Download the latest Windows Installer file from Marin Briza’s github page:
https://github.com/MartinBriza/MediaWriter/releases.
2. Run the installation by double clicking it, and then clicking next through the set-up
wizard. The Wizard gives you the options to customize the software’s installation if
you choose to.
3. In Windows 8 and 10, the application will be under "all apps" under F for Fedora
Media Writer. Or in Windows 10, you can just type Fedora Media Writer in the
search box on the task bar.
4. Select the Fedora Edition you wish to make a bootable USB drive for.
Figure 1. Fedora Media Writer Main Screen: Choose your Edition of Fedora
5. If you choose one of the beginning default Fedora editions, such as Fedora
workstation or server. Fedora Media Writer will give you information and details
about it before you proceed with the download and USB creation. For Fedora
Workstation, you can choose a different architecture, such as 32bit if you select
"other architectures". Otherwise select "Create Live USB" to proceed.
Figure 2. Fedora Media Writer Distro Information
6. Fedora Media Writer will automatically download the ISO for you, but if you all-ready
have it in your Downloads directory it will be immediately available to use.
Figure 3. Fedora Media Writer Automatic Download
7. After the download completes, or when Fedora Media Writer is ready. Plug in a USB
drive you wish to use as a bootable media.
8. Click the red "Write to disk" button.
Figure 4. Fedora Media Writer Write to USB Device
Creating USB Media with Fedora Media Writer.

1. On Fedora 25 or later, you can download Fedora Media Writer with the command:
$ sudo dnf install mediawriter
2. You can call Fedora Media Writer by issuing the command:
$ sudo mediawriter
or in Gnome 3 by selecting Activities, then selecting Utilities, and then selecting

Fedora Media Writer.
Creating USB Media on Macintosh

1. Download the latest Macintosh Disk Image (the package will have a .dmg extension)
from Marin Briza’s github page:
https://github.com/MartinBriza/MediaWriter/releases.
2. Open the .dmg file and copy the mediawriter file into your applications folder.
3. Navigate to your applications directory, and then launch the mediawriter app.
4. Mac OS will then ask if you are sure you want to open the file (it is from the internet
after all), select "Open" to run the program.

Creating USB media with GNOME Disks

1. On a system with GNOME, or with the gnome-disk-utility package installed, open
Disks using the system menu.
2. Click your USB device in the left column.
3. Click the menu icon in the upper right corner of the window, and choose the
Restore Disk Image option.
4. Navigate to your image file and click Start Restoring. After a few minutes, it will
report the process is complete and your installation media will be ready to use.
Creating USB Media on the Linux command line
1. Open a terminal window and insert the usb drive.
2. Find the device node assigned to the drive. In the example below, the drive is given
sdd.
$ dmesg|tail
[288954.686557] usb 2-1.8: New USB device strings: Mfr=0, Product=1, Se
rialNumber=2
[288954.686559] usb 2-1.8: Product: USB Storage
[288954.686562] usb 2-1.8: SerialNumber: 000000009225
[288954.712590] usb-storage 2-1.8:1.0: USB Mass Storage device detected
[288954.712687] scsi host6: usb-storage 2-1.8:1.0
[288954.712809] usbcore: registered new interface driver usb-storage
[288954.716682] usbcore: registered new interface driver uas
[288955.717140] scsi 6:0:0:0: Direct-Access Generic STORAGE DEVICE
9228 PQ: 0 ANSI: 0
[288955.717745] sd 6:0:0:0: Attached scsi generic sg4 type 0
[288961.876382] sd 6:0:0:0: sdd Attached SCSI removable disk
3. Use the dd utility to write the image. Make sure you have the right drive!
# dd if=/path/to/Fedora-Live-Security-x86_64-21.iso of=/dev/sdd
Creating a Boot CD or DVD
In addition to creating a bootable USB flash drive, you can also use the provided ISO
images to create bootable optical media (a CD or DVD). This approach may be necessary
when installing Fedora on an older system which can not boot from USB.
The exact steps you need to take to burn a bootable CD or DVD from an ISO
 image will vary depending on what disc burning software you use. This
procedure only offers a general overview.
1. Insert a blank CD or DVD into your system’s CD or DVD burner.
2. Open your system’s burning software - for example, Brasero on Fedora systems with
GNOME desktop environment, or Nero on Windows systems. In the software’s main
menu, find an option which lets you burn an ISO image to a disc. For example, in
Brasero, this option is Burn image in the main menu on the left side of the window.
3. When prompted, select the ISO image of Fedora to be burned, and the CD or DVD
burner with a blank disc inside (if you have more than one drive).
4. Confirm your selection, and wait for the disc to be burned.

ABOUT
Get Fedora
Sponsors
Fedora Magazine
Legal
SUPPORT
Get Help
Ask Fedora
Common Bugs
Fedora Developer
Portal
COMMUNITY
Join Fedora
About Fedora
Planet Fedora
Fedora Account
System
  

Introducción a Puppy Linux:
Instalación en Memoria USB
Alex Gotev
Novara, 2009-10-24
Alex Gotev – Introducción a Puppy Linux: Instalación en Memoria USB 1
Contenido
Qué es Puppy Linux?

Cómo lo puedo obtener?
Cómo lo hago booteable?
Qué programas incluye?
Instalación en una memoria USB
Novara, 2009-10-24
Puppy Linux es una distribución en Disco Vivo
GNU/Linux desarrollado por Barry Kauler. Está
diseñado para ser rapido y pequeño. Se puede
correr e instalar incluso en Hardware muy viejo
(Pentium I) además de que es ligero y portable.
Todo el sistema operativo y todas las aplicaciones
se corren desde la memoria RAM (si hay
suficiente en la PC) y esto otorga gran
desempeño a Puppy Linux.
Incluso se puede instalar en el Disco Duro como
otras distribuciones de Linux, pero esto no es
necesario, porque el Sistema Operativo puede ser
usado desde un CD o una memoria USB sin
cambiar nada en la PC Host .
Novara, 2009-10-24
Cómo puedo obtener Puppy Linux?
Ve al sitio oficial: http://www.puppylinux.org
Da click en “Download Puppy Linux 4.30”
Novara, 2009-10-24
Da click en: pup-430.iso y escoge donde guardar el archivo
Novara, 2009-10-24
Despues de descargar el archivo, abrelo con tu programa
favorito de grabación de Cds:
CDBurnerXP, freeware, website: http://cdburnerxp.se
ImgBurn, freeware, website: http://www.imgburn.com
Nero, shareware, website: http://www.nero.com
Ejemplos de grabación con CDBurnerXP y Nero
Novara, 2009-10-24
Grabando un CD Puppy con CDBurnerXP
Ejecuta CDBurnerXP desde el menú inicio o desde su icono en
escritorio . Selecciona “Burn ISO image” y da click en OK.
Novara, 2009-10-24
Burning Puppy CD with CDBurnerXP
Da click en el boton “...”
Un ventana de dialogo se abrirá preguntando por el archivo
ISO de Puppy que descargamos. Busca donde los guardaste,
seleccionalo y confirma clickeando en OK.
Inserta un CD virgen en la unidad grabadora de CD-ROM y da
click en “Burn”.
Selecciona
aquí el archivo
que
descargaste
Novara, 2009-10-24
Grabando un CD Puppy con Nero
Da un click derecho sobre el archivo ISO que descargaste y
escoge Abrir con...> Nero Burning ROM
Novara, 2009-10-24
Inserta CD virgen en la Grabadora de CD/DVD y da click en
“Write”
Novara, 2009-10-24
Arrancando Puppy Linux desde un CD
Previamente inserta el CD Puppy Linux que grabaste en tu
lector de CD/DVD Rom y reinicia tu PC
Despues del “beep” de la PC si un mensaje similar a este es
mostrado: “Press any key to boot from CD...”, presiona Enter
Si no se muestra nada o si el Sistema Operativo en la PC
arranca automaticamente, tendrás que ajustar el orden de
arranque de los dispositivos en la BIOS. Para más información
sobre Cómo hacer esto, visita:
http://www.hiren.info/pages/bios-boot-cdrom
Novara, 2009-10-24
Si todos los ajustes en la PC son correctos, una vez que has
reiniciado verás esto:
Novara, 2009-10-24
Despues de una serie de mensajes de lineas de comando, un
cuadro de dialogo se mostrará en pantalla, preguntando para
que selecciones el teclado adecuado. Usa las teclas de
dirección para seleccionar el apropiado para ti. Una vez que lo
haya hecho, presiona ENTER para continuar.
Novara, 2009-10-24
A continuación, se te preguntará que selecciones el área para
tu pais. Selecciona la que mejor se ajuste a ti y presiona
ENTER.
Novara, 2009-10-24
Selecciona la zona horaria de tu país. Presiona ENTER para
continuar.
Novara, 2009-10-24
Configuración de Video: presiona ENTER para continuar
Novara, 2009-10-24
Configuración de video: selecciona la resolución preferida
desde el cuadro de dialogo (los más comunes son 800x600 y
1024x768). Presiona ENTER para continuar
Novara, 2009-10-24
Todas las configuraciones están
hechas!!
Estás listo para ver a Puppy Linux?
Novara, 2009-10-24
Escritorio de Puppy Linux
Novara, 2009-10-24
Programas principales de Puppy Linux
Navegador de Archivos Panel de Control de Puppy
Linux
Navegador de internet MediaPlayer para audio y

(SeaMonkey) video
Cliente de Email Manejador de archivos

(similar a OutlookExpress) comprimidos(ZIP,RAR,TAR,...)
Programa de chat
compatible con los Agregar/Quitar programas
estandares de: MSN,Yahoo,ICQ
Sustitutos para Word y Excel,

compatible con los estandares MS Office
Dos programas gráficos: El 1ro similar a MS Paint con algunas

adiciones y la 2da es una versión ligera de Inkscape
Novara, 2009-10-24
Instalando Puppy Linux en una
Memoria Flash
(en menos de 5 minutos!)
Novara, 2009-10-24
Instalando Puppy en una memoria USB - 1
Abre Menu>Setup>BootFlash install Puppy to USB
El programa que hemos
lanzado formateara la
memoria USB y lo hará
booteable
PRECAUCIÓN!
Primero guarda todos los datos
contenidos en la memoria USB ,
porque todo será borrado dentro de
la memoria!
Novara, 2009-10-24
Selecciona USB-HDD (hard drive) y presiona OK
Novara, 2009-10-24
Inserta el dispositivo USB en uno de tus puertos USB y espera
a que sea reconocido:
A continuación, presiona OK para continuar
Novara, 2009-10-24
Selecciona la memoria USB de la lista y da click en OK en la
segunda ventana para continuar...
Novara, 2009-10-24
Espera hasta que el formateo termine...
A continuación da click en “Exit finished” para salir de la

aplicación de formateo de la USB
Novara, 2009-10-24
Abre Menu>Setup>Puppy Universal Installer
Con el Universal Installer
podemos instalar Puppy Linux
en casi cualquier dispositivo.
En este caso lo usaremos para
copiar los archivos de sistema
en la memoria USB booteable
recien formateada que hemos
creado
Novara, 2009-10-24
Selecciona “USB Flash Drive” de la lista y da click en OK. En la
siguiente ventana que aparezca da click en OK para confirmar
y continuar
Novara, 2009-10-24
Da click en OK para confirmar la instalación. En la siguiente
ventana que aparezca, da click en “CD” para que el instalador
copie los archivos de sistema de Puppy del disco vivo (LiveCD)
Novara, 2009-10-24
Instalando Puppy en una memoria - 9
Da click en OK en la siguientes dos ventanas para empezar
con la instalación por default para dispositivos USB
Novara, 2009-10-24
Da click en la ventana del terminal y presiona Enter para la
instalación final
Presiona Enter de nuevo para continuar sin borrar nada de la

USB la cual ya hemos preparado
Novara, 2009-10-24
Si queremos que Puupy trabaje por default con menos de
256MB de RAM, presiona ENTER. De otra forma, teclea
cualquier letra y presiona Enter (recomendado).
Tecleando una letra y presionando Enter ajustaremos a Puppy
para que automaticamente escoja la mejor opción de RAM de
acuerdo a la RAM disponible en la PC
Novara, 2009-10-24
Instalando Puppy en una memoria USB- 12
Cuando la instalación termine, presiona ENTER
La instalación ha terminado! Ahora estas listo para ir a

cualquier parte con tu sistema operativo Puppy USB !
La principal ventaja de traer Puppy en una USB es que puedes
llevar tus ajustes y todos tus archivos a donde quiera que
vayas, sin tener que cargar nada más! Otro hecho interesante
es que la PC host no se verá afectada en lo más minimo. Nada
será guardado en la PC solo en la USB Puppy, preservando tu
privacidad!
Novara, 2009-10-24
Gracias por tu Atención!
Alex Gotev
Tecnico en Tecnologías de la Computación y estudiante de
Ingenieria en Computación en el Politecnico de Milano
e-mail: alexgotev@gmail.com
Traducción: Nestor Gabriel

Egresado del Tecnológico de Veracruz en el área de
Ingenieria en Electrónica (ITV)
e-mail:ngabriel1987@hotmail.com
Novara, 2009-10-24
Search
PCLinuxOS
So cool ice cubes are jealous
Main Menu Home About PCLinuxOS Help us out Get PCLinuxOS Support Community International Get PCLinuxOS
Home Contact Us Community Releases Forum Merchandise KDE Desktop Mate Desktop FullMonty KDE Desktop
About PCLinuxOS Desktop MATE Desktop
Get PCLinuxOS
Support Community Releases
Community
International
Contact Us
Mate Desktop
Get a Chimpbox Computer
Forum
Merchandise PCLinuxOS64 MATE Desktop
Help us out Introducing The Chimpbox
Download Locations
Sponsors Info: The MATE Desktop: a popular, multi-platform desktop environment for your computer. MATE’s focus is
ease of use, stability, and provides all the common tools computer users expect from a modern
computing environment. Tiny but powerful!
MATE64 (pclinuxos64-MATE-2018.06.iso)
Support PCLinuxOS!
PCLinuxOS Magazine Size: 1.3 GB ISO
Recent Issues: Md5sum: 9315f8db3796d693b32ba9d4687e999b

Release Date: June 2018
July 2018 Produced by: Texstar or
User Level: Beginner, Intermediate, Advanced PCLinuxOS $5/Mo Donation
June 2018
PCLinuxOS $10/Mo Donation
PCLinuxOS $25/Mo Donation
May 2018
April 2018 PCLinuxOS $5/Yr Donation

PCLinuxOS $10/Yr Donation
March 2018 PCLinuxOS $25/Yr Donation
PCLinuxOS $50/Yr Donation
February 2018
Support
January 2018
PCLinuxOS Forum
December 2017 PCLinuxOS Wiki
PCLinuxOS Live Chat Support
November 2017
Social Media
October 2017
PCLinuxOS Twitter Feed
September 2017
Related Web Sites

August 2017
PCLinuxOS Magazine
July 2017
PCLinuxOS Design Studio
June 2017
PCLinuxOS International
May 2017
PCLInuxOS BR
PCLInuxOS DE
April 2017
PCLinuxOS DK
March 2017 PCLinuxOS IT
PCLinuxOS NL
February 2017 MATE64 features: PCLinuxOS TR
===================== PCLinuxOS SU
January 2017 * kernel 4.16.13
* xorg server
December 2016
* Full MATE Desktop 1.20.3
November 2016 * Nvidia drivers pre-installed

* basic uefi/gpt/nvme installation support
October 2016 * systemd free
* grub2 by default
September 2016
* updated administration tools
* mylivecd can now create isos greater than 4 gigs
August 2016
* compiz/emerald for wobbly windows.
July 2016 * Highlighted apps include Firefox, Thunderbird, Clemetine, VLC, Atril, Engrampa, Caja file manager, Eye
of Mate, Gimp
June 2016 * LibreOffice office software included
* System Config Printer plus HP printer drivers
May 2016
* Ready to dd to usb stick. (no isohybrid command required)
April 2016
Known issue: Net Applet icon on panel is odd sized.
March 2016
Hardware requirements
February 2016 Processor
64bit Modern Intel or AMD processor.
January 2016
Memory & storage

December 2015
RAM : 2 GB or more recommended.
November 2015
Hard disk : 15 GB or more recommended if you plan to install additional software from our repository.
October 2015
Video card
September 2015 nVidia, ATI, Intel
August 2015 3D desktop support requires a 3D instructions set compatible card.
Sound card
July 2015
Any Sound Blaster, AC97 or HDA compatible card.
June 2015
Other
CD/DVD drive required for burned liveCD/DVD image, or USB flash drive larger than 2 GB for liveUSB
May 2015
image conversion.
April 2015
Copy to USB stick:
March 2015
dd bs=4M if=pclinuxos64-MATE-2018.06.iso of=/dev/sdX status=progress && sync
February 2015
Special device – pendrive – /dev/sdX – without any number.
January 2015
Download
December 2014 Disclaimer (CYA): THIS SOFTWARE IS PROVIDED BY BILL REYNOLDS AND CONTRIBUTORS “AS IS”
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
November 2014
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
October 2014
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
September 2014 TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
August 2014 CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE
News Archives Torrent Links
June 2018 (2) PCLOS ISO Download mirrors

May 2018 (3)
April 2018 (1)
Australia 1 Australia 2 Brazil Bulgaria
January 2018 (2)
December 2017 (3)
Denmark Ecuador 1 Ecuador 2 France France 2
November 2017 (2)
October 2017 (10)
July 2017 (2) Germany Greece Japan Netherlands 1 Netherlands 2
June 2017 (3)
May 2017 (3) USA Vietnam
April 2017 (2)
March 2017 (6)
Please help ensure that PCLinuxOS remains available in the future, by
February 2017 (4)
making a financial contribution.
January 2017 (8)
December 2016 (4)
October 2016 (1) Comments are closed.
September 2016 (1)
August 2016 (7)
July 2016 (16)
June 2016 (19)
May 2016 (6)
April 2016 (9)
March 2016 (6)
February 2016 (9)
January 2016 (6)
November 2015 (5)
September 2015 (6)
August 2015 (2)
July 2015 (5)
June 2015 (1)
May 2015 (6)
April 2015 (5)
March 2015 (13)
February 2015 (11)
January 2015 (10)
December 2014 (8)
October 2014 (4)
September 2014 (10)
August 2014 (7)
June 2014 (1)
May 2014 (2)
April 2014 (1)
February 2014 (2)
December 2013 (3)
November 2013 (1)
October 2013 (3)
August 2013 (3)
July 2013 (4)
June 2013 (3)
May 2013 (2)
April 2013 (4)
March 2013 (2)
January 2013 (3)
December 2012 (1)
November 2012 (1)
October 2012 (1)
September 2012 (2)
August 2012 (2)
July 2012 (1)
June 2012 (1)
May 2012 (1)
April 2012 (1)
March 2012 (1)
February 2012 (4)
January 2012 (1)
December 2011 (5)
November 2011 (3)
October 2011 (3)
September 2011 (1)
August 2011 (2)
July 2011 (9)
June 2011 (10)
May 2011 (1)
April 2011 (2)
March 2011 (1)
February 2011 (1)
January 2011 (1)
December 2010 (4)
November 2010 (5)
October 2010 (7)
September 2010 (5)
August 2010 (1)
July 2010 (5)
June 2010 (6)
May 2010 (4)
April 2010 (4)
March 2010 (1)
February 2010 (1)
January 2010 (1)
Introducción a Puppy Linux:
Instalación en Memoria USB
Alex Gotev
Novara, 2009-10-24
Contenido

Cómo lo puedo obtener?
Cómo lo hago booteable?
Qué programas incluye?
Instalación en una memoria USB
Novara, 2009-10-24
Puppy Linux es una distribución en Disco Vivo
GNU/Linux desarrollado por Barry Kauler. Está
diseñado para ser rapido y pequeño. Se puede
correr e instalar incluso en Hardware muy viejo
(Pentium I) además de que es ligero y portable.
Todo el sistema operativo y todas las aplicaciones
se corren desde la memoria RAM (si hay
suficiente en la PC) y esto otorga gran
desempeño a Puppy Linux.
Incluso se puede instalar en el Disco Duro como
otras distribuciones de Linux, pero esto no es
necesario, porque el Sistema Operativo puede ser
usado desde un CD o una memoria USB sin
cambiar nada en la PC Host .
Novara, 2009-10-24
Ve al sitio oficial: http://www.puppylinux.org
Da click en “Download Puppy Linux 4.30”
Novara, 2009-10-24
Da click en: pup-430.iso y escoge donde guardar el archivo
Novara, 2009-10-24
Despues de descargar el archivo, abrelo con tu programa
favorito de grabación de Cds:
CDBurnerXP, freeware, website: http://cdburnerxp.se
ImgBurn, freeware, website: http://www.imgburn.com
Nero, shareware, website: http://www.nero.com
Ejemplos de grabación con CDBurnerXP y Nero
Novara, 2009-10-24
Grabando un CD Puppy con CDBurnerXP
Ejecuta CDBurnerXP desde el menú inicio o desde su icono en
escritorio . Selecciona “Burn ISO image” y da click en OK.
Novara, 2009-10-24
Burning Puppy CD with CDBurnerXP
Da click en el boton “...”
Un ventana de dialogo se abrirá preguntando por el archivo
ISO de Puppy que descargamos. Busca donde los guardaste,
seleccionalo y confirma clickeando en OK.
Inserta un CD virgen en la unidad grabadora de CD-ROM y da
click en “Burn”.
Selecciona
aquí el archivo
que
descargaste
Novara, 2009-10-24
Da un click derecho sobre el archivo ISO que descargaste y
escoge Abrir con...> Nero Burning ROM
Novara, 2009-10-24
Inserta CD virgen en la Grabadora de CD/DVD y da click en
“Write”
Novara, 2009-10-24
Previamente inserta el CD Puppy Linux que grabaste en tu
lector de CD/DVD Rom y reinicia tu PC
Despues del “beep” de la PC si un mensaje similar a este es
mostrado: “Press any key to boot from CD...”, presiona Enter
Si no se muestra nada o si el Sistema Operativo en la PC
arranca automaticamente, tendrás que ajustar el orden de
arranque de los dispositivos en la BIOS. Para más información
sobre Cómo hacer esto, visita:
http://www.hiren.info/pages/bios-boot-cdrom
Novara, 2009-10-24
Si todos los ajustes en la PC son correctos, una vez que has
reiniciado verás esto:
Novara, 2009-10-24
Despues de una serie de mensajes de lineas de comando, un
cuadro de dialogo se mostrará en pantalla, preguntando para
que selecciones el teclado adecuado. Usa las teclas de
dirección para seleccionar el apropiado para ti. Una vez que lo
haya hecho, presiona ENTER para continuar.
Novara, 2009-10-24
A continuación, se te preguntará que selecciones el área para
tu pais. Selecciona la que mejor se ajuste a ti y presiona
ENTER.
Novara, 2009-10-24
Selecciona la zona horaria de tu país. Presiona ENTER para
continuar.
Novara, 2009-10-24
Configuración de Video: presiona ENTER para continuar
Novara, 2009-10-24
Configuración de video: selecciona la resolución preferida
desde el cuadro de dialogo (los más comunes son 800x600 y
1024x768). Presiona ENTER para continuar
Novara, 2009-10-24
Todas las configuraciones están
hechas!!
Estás listo para ver a Puppy Linux?
Novara, 2009-10-24
Escritorio de Puppy Linux
Novara, 2009-10-24
Programas principales de Puppy Linux
Navegador de Archivos Panel de Control de Puppy
Linux
Navegador de internet MediaPlayer para audio y

(SeaMonkey) video
Cliente de Email Manejador de archivos

(similar a OutlookExpress) comprimidos(ZIP,RAR,TAR,...)
Programa de chat
compatible con los Agregar/Quitar programas
estandares de: MSN,Yahoo,ICQ
Sustitutos para Word y Excel,

compatible con los estandares MS Office
Dos programas gráficos: El 1ro similar a MS Paint con algunas

adiciones y la 2da es una versión ligera de Inkscape
Novara, 2009-10-24
Instalando Puppy Linux en una
Memoria Flash
(en menos de 5 minutos!)
Novara, 2009-10-24
Abre Menu>Setup>BootFlash install Puppy to USB
El programa que hemos
lanzado formateara la
memoria USB y lo hará
booteable
PRECAUCIÓN!
Primero guarda todos los datos
contenidos en la memoria USB ,
porque todo será borrado dentro de
la memoria!
Novara, 2009-10-24
Selecciona USB-HDD (hard drive) y presiona OK
Novara, 2009-10-24
Inserta el dispositivo USB en uno de tus puertos USB y espera
a que sea reconocido:
A continuación, presiona OK para continuar
Novara, 2009-10-24
Selecciona la memoria USB de la lista y da click en OK en la
segunda ventana para continuar...
Novara, 2009-10-24
Espera hasta que el formateo termine...
A continuación da click en “Exit finished” para salir de la

aplicación de formateo de la USB
Novara, 2009-10-24
Abre Menu>Setup>Puppy Universal Installer
Con el Universal Installer
podemos instalar Puppy Linux
en casi cualquier dispositivo.
En este caso lo usaremos para
copiar los archivos de sistema
en la memoria USB booteable
recien formateada que hemos
creado
Novara, 2009-10-24
Selecciona “USB Flash Drive” de la lista y da click en OK. En la
siguiente ventana que aparezca da click en OK para confirmar
y continuar
Novara, 2009-10-24
Da click en OK para confirmar la instalación. En la siguiente
ventana que aparezca, da click en “CD” para que el instalador
copie los archivos de sistema de Puppy del disco vivo (LiveCD)
Novara, 2009-10-24
Instalando Puppy en una memoria - 9
Da click en OK en la siguientes dos ventanas para empezar
con la instalación por default para dispositivos USB
Novara, 2009-10-24
Da click en la ventana del terminal y presiona Enter para la
instalación final
Presiona Enter de nuevo para continuar sin borrar nada de la

USB la cual ya hemos preparado
Novara, 2009-10-24
Si queremos que Puupy trabaje por default con menos de
256MB de RAM, presiona ENTER. De otra forma, teclea
cualquier letra y presiona Enter (recomendado).
Tecleando una letra y presionando Enter ajustaremos a Puppy
para que automaticamente escoja la mejor opción de RAM de
acuerdo a la RAM disponible en la PC
Novara, 2009-10-24
Instalando Puppy en una memoria USB- 12
Cuando la instalación termine, presiona ENTER
La instalación ha terminado! Ahora estas listo para ir a

cualquier parte con tu sistema operativo Puppy USB !
La principal ventaja de traer Puppy en una USB es que puedes
llevar tus ajustes y todos tus archivos a donde quiera que
vayas, sin tener que cargar nada más! Otro hecho interesante
es que la PC host no se verá afectada en lo más minimo. Nada
será guardado en la PC solo en la USB Puppy, preservando tu
privacidad!
Novara, 2009-10-24
Gracias por tu Atención!
Alex Gotev
Tecnico en Tecnologías de la Computación y estudiante de
Ingenieria en Computación en el Politecnico de Milano
e-mail: alexgotev@gmail.com
Traducción: Nestor Gabriel

Egresado del Tecnológico de Veracruz en el área de
Ingenieria en Electrónica (ITV)
e-mail:ngabriel1987@hotmail.com
Novara, 2009-10-24
Linux distributions
Linux Distributions
Welcome to ibiblio.org’s Linux Distribution homepage!
This page lists Linux distributions that we host or mirror–it is not an

exhaustive list. To access a distribution, simply click on its title. You
will find a link to the distribution’s homepage beneath each
description.
If you prefer to browse the Linux distribution directory tree itself,

please use http://distro.ibiblio.org/.
If you need help with installation, you may refer to The Linux
Installation HOWTO at tldp.org. For questions on individual
distributions, please refer to the distribution’s homepage.
These distributions are freely available for download and

distribution under Open Source copyleft and licensing restrictions.
Please refer to each package for copying and distribution
restrictions. See copyleft & licensing for overview explanation of
Open Source licensing.
7linux 7linux is small, fast distribution built from scratch. Its

main characteristics are: use of 7z compression, pkgtools from
Slackware, Enlightenment, and KDE desktops. Distribution
homepage
AdminsParadise AdminsParadise VoIP PBX is a full Web-based

phone and fax solution that integrates the best-of-breed open
source VoIP software. It runs Asterisk 1.4.1, hylafax, avantfax, and
PHP5 with a themed, easy-to-use, Web-based interface.
Distribution homepage
ALT Linux Developed in Russia, ALT Linux is a universal

distribution created by an international team of free software
developers. ALT Linux Junior is a single-disk distribution for home
computers designed especially for beginners and is easy to install
and use. ALT Linux Master is a universal distribution which can
be used on a server or on a workstation. It is equally useful for
software developers. ALT Linux Castle is a protected server
distributions on the basis of RSBAC system. English Distribution
homepage
Amigo Linux AMIGO Linux is one of the easiest ways yet to run
Linux. Just unzip on a FAT partition and boot. No installation
needed. The first time Amigo runs it will quickly detect your
system’s hardware and configure itself. Pre-installed GUI desktop
and power-user let you get right to work. No configuration
needed. Easiest way yet to install a Slackware-compatible distro.
Small (+200MB), fast distro is nearly as easy to use as a ‘live-CD
Linux’ but without the disadvantages. Runs with as little as 16MB
RAM. This is Low-Fat Linux at its’ best. Distribution homepage
Annvix Annvix is a free secure Linux-based operating system

produced by the Annvix development team and Danen Consulting
Services. The Annvix project aims to provide a secure, stable, and
fast Linux distribution specifically tailored to servers that provide
reliable services such as e-mail, Web, DNS, FTP, File sharing, and
more. Distribution homepage
Animux Animux is a free animation based toolset which can

handle tasks from creative development to post-production stage
of your creative project. Distribution homepage
Anubis Linux Anubis-Linux is a distro that’s designed to provide a

lot of development tools and documentation. Possible options with
Anubis include: study programming, networking and security,
creating and testing bootloaders or OS’, distro remastering
(current AL kernel source included), analyzing network traffic
and perform tests, using Wireshark, tcpdump, PackEth, packit,
etc., compile Win32, DOS and Linux(64) programs, in C, C++ or
various flavours of Assembly, debug executables, using KDbg,
OllyDbg and other tools, run Win32 and DOS programs, or use the
Tor network to browse anonymously. Features a classic design
with one big compressed filesystem (as opposed to the modular
design used by Slax and its derivatives, etc).
Archiso Linux Archiso is a small set of bash scripts that is capable

of building fully functional Arch Linux based live CD/DVD and
USB images. It is a very generic tool, so it could potentially be used
to generate anything from rescue systems, to install disks and
special interest live CD/DVD/USB systems. Simply put, if it involves
Arch on a shiny coaster, it can do it. Archo-Debian Linux. Arco-
debian is a bootable CD Linux with automatic hardware detection
is originally based on Knoppix and Kurumin. Single CD includes
apache2, mysql, php4 and kde-3.5.5. Distribution homepage
Arklinux Ark Linux is a Linux distribution designed especially for

desktop use, primarily for people without prior Linux experience.
Its main goal is ease of use, and the inclusion of many tools end
users will need. Distribution homepage
Archpwn linux ArchPwn is a security based Linux Live CD/DVD

system that aims to be a fully working swiss
army knife for pentesting purpose (GPL licensed). Distribution
Homepage
Aurora Linux Aurora Linux is a port of Red Hat Linux (now

Fedora) to Sun SPARC processor based machines. Distribution
homepage
Baslinux BasicLinux is a multipurpose mini-Linux that boots

from HD, FD or CD-ROM. The 2mb package provides the usual
rescue/repair tools, but it can also dial an ISP and browse the net,
or act as a router/firewall. BasicLinux uses a newbie-friendly shell
and editor, and it would make a good introductory Linux for a
DOS dinosaur. Distribution homepage
Bayanihan Linux Bayanihan Linux is a complete open source-

based desktop solution for office and school use. It is a package
that includes an operating system, a word processor, spreadsheet
program, presentation software, email facility, an internet
browser, and a graphics editor. This complete system is packaged
in a single easy-to-install CD. The word “Bayanihan” relates to a
Filipino tradition where people in a community help their
neighbor in physically moving their house to a different place.
The most recent versions of Bayanihan Linux are based on Debian
GNU/Linux; previous releases (3.1 and earlier) were based on
Fedora Core and Red Hat Linux. Distribution homepage
Belenix BeleniX is essentially a first class OpenSolaris operating

environment with very little modifications to the base. It is also
very stable and very compatible with SUN‚Äôs OpenSolaris having
derived packages out of sources from JDS, SFW, FOX, G11N,
Caiman and other repos plus its own repo. It is also a full-blown
OpenSolaris development environment being completely self-
hosting. Every package delivered for BeleniX is built on BeleniX
including the base OS (ON). Distribution Homepage
Bolix Designed for both Linux newcomers and power users, and
inspired by Ubuntu. Features include: boots in live mode, straight
from the CD, includes Firefox, OpenOffice.org, games and more,
excellent hardware detection, user-friendly hard drive installer.
Burning Thunder Pup (BTP) Burning Thunder Pup is a Puppy

Linux distribution with (working) Firefox and Thunderbird
desktop icons and Wine in the terminal.
Distribution Homepage
CD Linux CDlinux is a compact distribution of GNU/Linux. The

name is a synonymous of ‚ÄúCompact Distro Linux.‚Äù It is small
in size, yet rich in features. You can use CDlinux as your
‚ÄúMobile OS‚Äù. Install it onto a USB key, take it anywhere and
turn any PC/Mac that supports booting from USB to your own
workstation, with the same user interface. CDlinux ships with an
up-to-date version of the Linux kernel, Xorg, Xfce, and many
popular applications, like Firefox, Pidgin, GIMP, and even Java
and Wine. Just work anywhere like at home.
CrunchBang Linux CrunchBang Linux is an Ubuntu based

distribution featuring the lightweight Openbox window manager
and GTK+ applications. The distribution has been built and
customised from a minimal Ubuntu install. The distribution has
been designed to offer a good balance of speed and functionality.
CrunchBang Linux is currently available as a LiveCD; however,
best performance is achieved by installing CrunchBang Linux to
your hard disk. Distribution homepage
Damnsmall Linux Damn small Linux is a very small live CD

Linux distribution. It has a working desktop environment yet is
small enough to fit on a business card-size CD. Distribution
homepage
Davinci Linux Linux DaVinci is an operating system based upon

Slax, which permits to develop and fulfill Italian schools
necessities about computer science course into college schools.
Deli Linux A Linux distribution for old computers, Deli Linux is a

distribution for old x86 compatible computers from 486 to
Pentium III with 32 to 128 MB RAM. It is based on uClibc and
provides a full graphical Environment with a web browser, an e-
mail client and an office package. Distribution homepage
DragoraDragora GNU/Linux is a new, independent distribution

made in Argentina. Web site in Spanish only. Distribution page
Dream Linux Dreamlinux is a free, modern and modular

GNU/Linux system. It can be run directly from a CD/DVD/USBStick
and optionally be installed to a HDD, including IDE, SCSI, SATA,
PATA and USB drives.
Dreamlinux comes with a selection of the best applications
designed to meet most of your daily needs. Distribution Homepage
Dyne:bolic Linux Dyne:bolic GNU/Linux is a live bootable

distribution working directly from the CD without the need to
install or change anything on harddisk. It can recognize most of
your hardware devices and offers a
vast range of softwares for sound and video production,
streaming, 3d modeling, peer to peer and filesharing, deejaying
and veejaying, games, a world navigator with detailed maps and
factbooks and much more. Distribution homepage
Elemental Linux Server The Elemental Linux Server (ELS) is

designed from the outset to be a minimal, no-frills server
distribution. There is no GUI, everything is console-based. There is
no package manager, packages are installed from .tar.gz files.
There is no administration tool, all configuration is done by
manually editing files in the /etc directory. Distribution homepage
E-Loop E-Loop is a Linux distribution on a bootable CD that

mounts a serpent encrypted file system on a windows partition. It
also includes scripts to encrypt personal files.
Engarde A secure distribution of Linux that implements advanced

security techniques. It can be used as a Web, DNS, e-mail,
database, e-commerce, and general Internet server. Includes a
complete suite of e-business services, intrusion alert capabilities,
improved authentication and access control utilizing strong
cryptography, and complete SSL secure web-based administration
capabilities. Distribution homepage
Esun Linux ESUN Linux is an Ubuntu-based distribution

containing free software for enterprise management. Developed
at the University of Tarapaca in Chile, the project’s goal is to
deliver a new alternative to students, teachers and the community
at large. The distribution includes software for enterprise resource
planning (ERP), customer relationship management (CRM),
project management, accounting, electronic commerce, human
resources, office and database. Distribution Homepage
Epidemic Epidemic GNU/Linux is a Brazilian Live-CD Linux

Distribution based on Debian. The focus is the desktop use. New
users will just use the base CD, experienced users can add more
software, change the configurations, etc. Distribution homepage
Fatdog 64 Fatdog is an all 64bit version of Linux built from source

packages and using Puppy Linux scripts and structure. Fatdog is
quite ‘fat’ compaired to Puppy, the complete Xorg is included
along with other extras that make it larger than Puppy.
Fedora The Fedora Project is a Red-Hat-sponsored and

community-supported open source project, though it is not a
supported product of Red Hat, Inc. The goal of The Fedora Project
is to work with the Linux community to build a complete, general
purpose operating system exclusively from free software. The
project will produce time-based releases of Fedora Core about 2-3
times a year with a public release schedule. The Red Hat
engineering team will continue to participate in the building of
Fedora Core and will invite and encourage more outside
participation than was possible in Red Hat Linux. Distribution
homepage
FortMacTux FortMacTux is a small, fast, and full featured

KDE/Slackware-based, Slax forked, Linux distribution.
It was inspired by and for AlbertA. It offers a great introduction to
Linux with no installation necessary,
and can revitalize old system hardware. It maintains a small
footprint, yet offers wireless Internet access, video, audio, and
games, full productivity suite (OpenOffice, CAD software,
financial/banking software, etc.). A USB version is coming soon.
Funtoo Linux Funtoo is a variation on Gentoo Linux. From an

installation perspective, the main difference
between Funtoo Linux and Gentoo Linux is that Funtoo Linux has
a different Portage tree. We store our Portage tree in a git
repository. Our Portage tree does track the Gentoo repository (we
import Gentoo changes almost every day,) but our tree does
contain some significant changes from Gentoo’s tree. Distribution
Homepage
Generations Generations Linux is a bootable ISO live GNU/Linux

operating environment. The ISO9660 image file can be used to
burn a CD-ROM or used with virtualization products such as
VMware Player or VirtualBox. The minimal requirements is an
Intel 80486 processor and 64MB of memory. The Generations
Linux operating environment nickname is vortex. The ultra-light
desktop environment uses fluxbox and a GTK+ based panel for a
familiar start menu, docklets such as a clock, volume control, and
battery monitor (when battery detected), and built-in management
of desktop shortcut icons. The name of the ISO9660 image is in the
form: generations–.iso where, version is currently at 3.0.2 and
sizecut indicates which production ISO image is provided. The
122MB production ISO image is currently the smallest and uses
Xvesa. Larger production images have both Xorg and Xvesa X
Window servers as well as additional software such as Inkscape,
Java, OpenOffice.org, Skype, and more. Distribution homepage
Gentoo Gentoo Linux is a versatile and fast, completely free x86-

based Linux distribution geared towards developers and network
professionals. Unlike other distros, Gentoo Linux has an advanced
package management system called Portage. Portage is a true
ports system in the tradition of BSD ports, but is Python-based and
sports a number of advanced features including dependencies,
fine-grained package management, “fake” (OpenBSD-style)
installs, safe unmerging, system profiles, virtual packages,
configuration file management, and more. Distribution homepage
Gibraltar Gibraltar, a Debian GNU/Linux based firewall

distribution, available for download. This Gibraltar does not need
to be installed on a hard disk but can be run directly from the
bootable, live CD-ROM. All software packages written for
Gibraltar, including the shell scripts for booting, maintaining and
administering it, can be distributed under the terms of the GNU
general public license. The complete, bootable ISO images of
Gibraltar can be used freely but commercial distribution is
restricted.German Distribution homepage, English Distribution
homepage
Gobolinux GoboLinux is a Linux distribution that breaks with the

historical Unix directory hierarchy. Basically, this means that
there are no directories such as /usr and /etc. The main idea of the
alternative hierarchy is to store all files belonging to an
application in its own separate subtree; therefore we have
directories such as /Programs/GCC/2.95.3/lib. Distribution
homepage
gOS gOS is an easy-to-use, Ubuntu-based distribution designed for

less technical computer users. Its main features are the use of
Enlightenment as the default desktop and tight integration of
various Google products and services into the product.
Granular Granular is a Linux Operating System that is intended to

be as user-friendly and flexible as possible.
For potential newcomers unfamiliar with Linux, Granular is an
excellent starting point and one that will make their introduction
to Linux as easy and smooth as possible. Distribution homepage
GUFI GUFI is a complete universal operating system for your

computer that can be used instead of Microsoft Windows or
Macintosh.Distribution homepage
Hanthana Hanthana is a Linux based operating system and a

Fedora remix suitable for desktop and laptop users. Hanthana
comes to you in the form of a Live CD for regular PC (i686
architecture) systems. You can run Hanthana Operating System
directly from the LiveCD and check out each and every feature
before installing it on your hard disk.Distribution Homepage
KateOS KateOS is a free (as in freedom) multitasking operating

system targeted toward intermediate Unix users. It combines the
most popular Open Source software with its own original
solutions. KateOS has a simple yet fully functional and fully-
featured TGZex package system which makes system
administration and updating a breeze. KateOS also has a set of
text-mode and graphical tools for system configuration, user-
friendly text-mode and graphical installation systems, a unified
PAM authorization system, and many more solutions which make
system maintenance a lot easier while preserving the classical
Unix structure of the system. The main foci of KateOS are
efficiency, security, reliability, and low system requirements.
Support for common multimedia is also included. Distribution
homepage
Knoppix KNOPPIX is a bootable CD with a collection of GNU/Linux

software, automatic hardware detection, and support for many
graphics cards, sound cards, SCSI and USB devices and other
peripherals. KNOPPIX can be used as a Linux demo, educational
CD, rescue system, or adapted and used as a platform for
commercial software product demos. Distribution homepage
Knoppix_NSM Knoppix-NSM is dedicated to providing a

framework for individuals wanting to learn about Network
Security Monitoring (NSM) or who want to quickly and reliably
deploy a NSM capability in their network. Our goal is to provide an
introduction to NSM and a distribution that can be used as a
launch pad to bigger and better things. We have tried to do most
of the hard work to help you get up and running as fast as
possible so you can spend more time learning about NSM, leaving
the details as a latter exercise once familiar with the concepts.
LadyBug LadyBug is a french GNU/Linux Live System base on

PCLINUXOS and SAM. It’s a installable LiveCD or LiveUSB. It uses
Mandriva tools, PCLINUXOS base, synaptic, xfce4 and mklivecd
script. You can make your own modification and remaster it
simply. Distribution homepage
Lamppix LAMPPIX is a Linux live CD originating in Germany,

based on Knoppix and Damn Small Linux. It comes with the
XAMPP web server, MySQL database, PHP and Perl scripting
languages, as well as other tools to run PHP-driven web pages
directly off a CD-ROM. Distribution homepage
LNX The LNX-BBC is a mini Linux-distribution, small enough to fit

on a CD-ROM that has been cut, pressed, or molded to the size and
shape of a business card.LNX-BBCs can be used to rescue ailing
machines, perform intrusion postmortems, act as a temporary
workstation, and perform many other tasks that we haven’t yet
imagined. Distribution Homepage
LinuxShark LinuxShark is based on opens use 11.2 and The Linux

Kernel Version 2.6.32.2, It is regularly updated with the latest
security patches and Kernel upgrades. Distribution Homepage
LQlinux LQ Linux is an easy Linux for older people.The LQ Linux

has an easy and big menu. A pre-Version can you find in the
Subdirectory lqmen1 . The menu requires Gambas2. For a good
function you need Firefox3, Thunderbird, Abiword, Gnumeric,
Thunar. Distribution Homepage Currently Unavailable
Mepis MEPIS Linux is a Debian-based desktop Linux distribution

designed for both personal and business purposes. It includes
cutting-edge features such as a live, installation and recovery CD,
automatic hardware configuration, NTFS partition resizing, ACPI
power management, WiFi support, anti-aliased TrueType fonts, a
personal firewall, KDE, and much more. Distribution homepage
Morphix Morphix is a modular Linux distribution, based on

Knoppix (which is in turn based on Debian). Morphix uses the Live
CD features of Knoppix, but it is more modular. Different modules
can be combined on a CD for varying purposes, making Morphix
a sort of Live CD construction kit. Distribution homepage
MyDebian MyDebian is Debian Live based Live Linux distribution.

It was started as an educational project at Gdansk University. I
made it as a help system for my students. Right now I use it two
years long as an ONLY operating system. MyDebian is distributed
as less-than 600MB *.iso image. MyDebian was tested on Intel
processor but as far as I know it works also with AMD.
Net Linx Net Linux is remastered and pre-configured Linux 4.31

with Firefox and Skype. Distribution Homepage Currently
Unavailable
OnionDSL oniondsl is a live CD based on Damn Small Linux

which is set up to automatically bypass the Australian Internet
censorship program Distribution Homepage
openSUSE The openSUSE project is a worldwide community

program sponsored by Novell that promotes the use of Linux
everywhere. The program provides free and easy access to
openSUSE. Here you can find and join a community of users and
developers, who all have the same goal in mind to create and
distribute the world’s most usable Linux. openSUSE also provides
the base for Novell’s award-winning SUSE Linux Enterprise
products. Distribution homepage
OpenWall Openwall GNU/*/Linux (or Owl for short) is a security-

enhanced operating system with Linux and GNU software as its
core, compatible with other major distributions of GNU/*/Linux. It
is intended as a server platform. And, of course, it is free.
PCLinuxOS PCLinuxOS is an English only live CD initially based

on Mandrake Linux that runs entirely from a bootable CD. Data on
the CD is uncompressed on the fly, allowing up to 2GB of
programs on one CD including a complete X server, KDE desktop,
OpenOffice.org and many more applications all ready to use. In
addition to the live CD, you can also install PCLinuxOS to your
hard drive with an easy-to-use livecd-installer. Additional
applications can be added or removed from your hard drive using
a friendly apt-get front end via Synaptic. Distribution homepage
PC/OS Its the first Linux based distribution that provides ease of
use out of the box. It provides all multimedia codecs out of the
box, an easy to use and simplified interface. Great compatibility
with older hardware to help you extend your hardware and
software investments. Distribution homepage
PCPAC The PCPAC project describes a method for converting a

Linux desktop distribution into a safe, reliable and efficient PAC, a
Public Access Computer, for a library, school or waiting room.
The intention is to have discussions about distros and scripts.
pdaXrom pdaXrom is a cross-platform Linux distribution with

own build system. Its targets are PDA and embedded systems.
pdaXrom uses X11 for GUI applications, hence greater versatility,
improved portability and better performance. Distribution
homepage
Peanut Linux Peanut Linux is a Linux OS (O)perating (S)ystem. Do

you want an alternative to your existing OS? With
Peanut Linux you only have to download 375MB. Distribution
Homepage
Pendrive Linux A Portable Linux Operating system that you can

bring with you on a USB hard drive, flash pendrive, thumbdrive,
flashdrive, ipod, phone or other mobile device. Project is no
longer under active development.
Phantomix Phantomix is a Live CD for anonymous surfing,

chatting and other internet based applications. Intended uses: 1)
Personal/private anonymous internet surfing, 2) Demo CD for
raising security anonymity awareness. Phantomix is based on the
KNOPPIX Live CD. It comes with a preconfigured tor and privoxy.
Tor and privoxy will be started during the boot sequence. After
booting from the CD, the user is in the common KNOPPIX KDE
Environment. Access to the Internet is configured to be routed via
tor/privoxy for anonymous surfing. Distribution homepage
poly-p-ux A Linux Operating system designed to run on very old

386, 486, and pentium computers. Distribution homepage
Puppy Linux Puppy Linux is a Live CD Linux distribution that is

very small and focuses on ease of use. If the computer has at least
256 MB of RAM, the entire operating system and all the
applications will run from RAM, allowing the boot medium to be
removed after the operating system starts. Applications such as
SeaMonkey, AbiWord, Gnumeric, and Gxine/xine are included.
The distribution is actively developed by Barry Kauler and other
active members of the community. Distribution homepage
PuppyRus PuppyRus Linux is a Russian version of Puppy Linux.

Quelitu A fast, lightweight, and user-friendly Linux operating

system based on Ubuntu/Lubuntu distributions for use in older
computers (minimum 250 MB RAM) or for lightning speed in
newer models.The distribution is released by Waves of the Future
as part of an environmental project (Quelitu Global) aiming to
increase the worldwide recycling and reuse of older computers by
refurbishing them to the fastest and latest standards. Quelitu is
multilingual with a special focus on English, French, and Spanish
guides. Distro homepage unavailable.
Quirky A variant of puppy, Quirky is a Linux distribution and is

in the “Puppy Linux family”, also known as a “puplet”. However,
Quirky is not a mainline Puppy release–it is a distinct distro in its
own right. Quirky is built with the Woof build system, as is Puppy
4.3.x and later official puppies.
RefractaRefracta is a variant of the GNU operating system and

uses the Linux kernel. It is a complete operating system and has
plenty of software available for it including office software,
cd/dvd burning software, photo editing software, and much more.
It does not run software made for the windows family of
operating systems. It also does not get any of the malware that is
designed for windows operating systems either. Distribution
Homepage
RoboHobby Linux LiveCD Knoppix-Based Linux LiveCD for

robotics hobbyists. Distribution homepage
ROOT Linux ROOT is a GNU/Linux operating system aiming for

speed, simpleness and flexibility. It contains many high quality
software packages for both server and workstation use.
Sabayon Linux Sabayon Linux is an operating system powered by

the Linux kernel and GNU. There are many Linux flavors, but
most geeks just call them distributions. We are a Linux
distribution, though, and try to provide our users the best and
most complete computing experience. Sabayon Linux uses Gentoo
Linux as its base. It is (and always will be) 100% compatible with
it. We are one of the most scalable distributions and are happy to
support everyone from the most creative kernel hacker to the
newbie. Distribution homepage
Security Onion The Security Onion LiveCD is a bootable CD that

contains software used for installing, configuring, and testing
Intrusion Detection Systems. Distribution Homepage
Slack390 Slack/390 is the official port of Slackware Linux to the

IBM mainframe platform. It is intended to be a maintained,
Free/Libre, and free (no charge) Linux/390 distribution. Slack/390 is
kept as close as possible to the Intel Slackware distribution, with
some exceptions due to the different needs of the two platforms.
Slackware Linux Slackware has offered a stable and secure Linux

distribution for UNIX veterans as well as an easy-to-use system for
beginners. Slackware configurations are applicable for either
server or workstation. Distribution homepage
Slitaz SliTaz is a free operating system, working completely in

RAM and booting from removable media such as a cdrom or USB
key. SliTaz is distributed as a LiveCD, and weighs less than 30MB.
The system is quick and responsive, clean and robust. SliTaz is
simple and intuitive, providing a lightweight, elegant desktop,
detailed documentation and easy to use configuration tools.
Documentation Homepage
SME Server The SME Server is an open-source software package

that, when installed on a PC-compatible computer,
transforms it into a easy-to-use, Linux-based communications
server. SME Server, a modified version of Red Hat Linux, is a
complete suite of essential networking services for internal and
external communications and collaboration. This standard Linux
distribution has been simplified by making all of the
configuration decisions in advance, such as which server
packages to run, how permissions and security should be set, how
the disk should be partitioned, how the directories should be
organized so that the servers are properly integrated with one
another, and so on. Distribution homepage
SoL SoL is short for Server optimized Linux and is a Linux

distribution completely independent from other Linux-
distributions. It was built from the original src-packages and is
optimized for heavy-duty server work. It contains all common
server applications. Distribution homepage
SourceMage Source Mage is a source-based GNU/Linux

distribution based on a Sorcery metaphor of “casting”
and “dispelling” programs, which we refer to as “spells”, and a
package manager called “Sorcery”. Our packages are designed to
allow the user to customize the package any way they want
(custom CFLAGS, LDFLAGS, ./configure flags, etc.) as well as
offering as many of the package options as possible to the user up-
front (you will not need to know what options a package has or
what optional dependencies it can use ahead of time). All of our
scripts are GPL’d and our package manager and packages are
written in bash, so they are easy to learn and modify. Sorcery
supports custom packages maintained by users, which can
override the default package and will never be touched by
updates. Distribution homepage
StartCom Enterprise Linux The StartCom Linux operating

systems are based on the Red Hat Enterprise and Fedora source
code, each modified with reliability, security and efficiency in
mind, to fit the tasks assigned to each flavor of StartCom Linux.
SYSlinux The SYSLINUX Project is a suite of lightweight

bootloaders, for starting up computers with the Linux
kernel. It is the work of H. Peter Anvin, and consists of several
separate systems, the best-known of which is ISOLINUX.
T2 T2 started as a community driven fork from the ROCK Linux

Project with the aim to create a decentralized development and
clean a framework for spin-off projects and customized
distributions. Another goal was to provide a more continous
release stream for stable security updates. With T2 you can define
targets for various purposes, ranging from embedded Linux
systems with a few MB of size over server configurations to a full
desktop system featuring X.Org foundation, KDE, Gnome,
OpenOffice.Org and many more. Those targets can be compiled
for use on the most common architectures: Alpha, ARM, HPPA
(incl. HPPA64), IA64, MIPS, PowerPC (incl. PowerPC-64), SPARC
(incl. SPARC64), SuperH, x86 (incl. x86-64) – theoretically any
GCC/Linux supported one. T2 comes with many predefined targets
(desktop, router, live CD …) and over 2000 package descriptions
ready to build. Distribution homepage
Tiny Core Linux Tiny Core Linux is a very small (10 MB) minimal
Linux Desktop. It is based on Linux 2.6 kernel, Busybox, Tiny X,
Fltk, and Jwm. The core runs entirely in ram and thus boots very
quickly. The user has complete control over which applications
and/or additional hardware to have supported selectable from
our online repository. Distribution Homepage
TinyMe Linux TinyMe is a remaster of PCLinuxOS. It comes

packaged in a miniscule 200MB or smaller ISO. We do this for
those of you who have old computers, like to mess around with
small/fast systems, or just want a minimal environment. TinyMe
is comparable to distributions like Puppy, AntiX, and DSL. If you
like small distributions of Linux, give TinyMe a try. Distribution
homepage
Trustix Secure Linux Comodo has announced that it will

discontinue all distribution, updates and direct support for Trustix
Secure Linux effective December 31, 2007. The user support forum
at www.trustix.org/forum will continue to remain online
throughout 2008.
UltimaLinux Ultima Linux is a fast, powerful, and above all

convenient computer operating system, available
for Intel and AMD-based personal computers. Features KDE,
Mozilla Firefox/Thunderbird, OpenOffice, and more. Distribution
homepage
Unity Linux The community-oriented Unity Linux is a minimalist
distribution and live CD based on Mandriva Linux. The project’s
main goal is to create a base operating system from which more
complete, user-oriented distribution can easily be built – either by
other distribution projects or by the users themselves. Unity Linux
uses Openbox as the default window manager. Its package
management is handled via Smart and RPM 5 which can
download and install additional software packages from the
project’s online repository Distribution Homepage
UW-Linux UW-Linux is a GNU/Linux distribution based

Slackware. It is a live-cd so you can boot and run it from the
cdrom drive. It’s kind of S-T-D distribution, with a lot of admin
stuff. But it could be used as a multimedia distribution (mplayer,
xmms etc. included) Distribution homepage
Vector Linux Vector Linux is a small, fast, Intel Linux operating

system based on one of the original Linux distributions,
Slackware. Slackware has been traditionally known to be about as
user friendly as a coiled rattlesnake and that’s where Vector Linux
comes into play. VL is a bloat free, easy to install, configure and
maintain Slackware-based system. Distribution homepage
Winlinux WinLinux is a Linux distribution with an installer that

runs from inside the Windows operating system. It also has a
configuration tool that can be run inside of Windows to set up the
hardware options of the Linux OS. It is installed to a directory on
an existing FAT32 partition, which means it has the ability to
share the Windows partition and disk space. Distribution
Homepage Currently Unavailable
Yellow Dog Yellow Dog Linux is an open source Linux operating

system for home, office, server, and cluster users. Built upon the
Red Hat/CentOS core, Terra Soft and now Fixstars (which acquired
Terra Soft in 2008) has since the spring of 1999 developed and
maintained Yellow Dog Linux for the Power architecture family
of processors. The distribution combines a graphical installer with
support for a wide range of Power hardware, leading-edge
kernels, stable, functional compilers for code development, and
servers for web, database, email, and network services. More than
2,000 packages are included on the install DVD. Distribution
Homepage
Zenarch Zenarch is a hybrid/modular live cd based on slax and

archlinux OS. Distribution Homepage Currently Unavailable
Zenwalk Zenwalk is a GNU/Linux operating system, designed to

provide the following characteristics: Modern and user-friendly
(latest stable software, selected applications); Fast (optimized for
. performance capabilities); Rational (one mainstream application
for each task); Complete (full development/desktop/multimedia
environment); Evolutionary (simple network package
management tool – netpkg). Distribution homepage
Zorin Zorin OS is a multi-functional operating system designed

Browse specifically for Windows users who want to have easy and
Share smooth access to Linux. Zorin OS is a gateway for Windows users
to the exciting world of open source software. It is based on
Software 
Ubuntu which is the most popular Linux operating system in the
Projects  world.
Donate Distribution Homepage
About 
Help 
WELCOME TO IBIBLIO
Home to one of the largest free

information databases online,
ibiblio.org has something for
ibiblio.org is a collaboration of the School of
everyone. Visitors can browse
Information and Library Science, the School of
through our eclectic
Media and Journalism, and
collections catalog and
Information Technology Services at the University
contributors can host and
of North Carolina at Chapel Hill.
share their unique collections
with millions worldwide.
About ibiblio | Contact | Privacy Policy | Help
Get started: Browse | Share

DISTROS&&CLONIN Merge PDF

Transféré par

Informations du document

Titre original

Copyright

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

DISTROS&&CLONIN Merge PDF

Transféré par

Droits d'auteur :

FAI - Fully Automatic Installation

FAI - Fully Automatic Installation

FAI ISO (1012 MB)

Motto: Plan your installation, and FAI installs your plan.

 Fedora Release Notes

Copyright 2017 Red Hat, Inc. and others.

For guidelines on the permitted uses of the Fedora trademarks, refer to

Java ® is a registered trademark of Oracle and/or its affiliates.

XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the

Fedora Documentation Project

Fedora is sponsored by Red Hat.

System tools included

More information about this project

# grml-live -s testing -c GRMLBASE,GRML_SMALL,AMD64 -o /srv/grml-live

6. Main features of grml-live

class based concept, providing a maximum of flexibility

supports integration of own hooks, scripts and configuration

native support of FAI features

7. The class concept

DEBORPHAN: get rid of all packages listed in output of deborphan

FRESHCLAM: execute freshclam (if it’s present) to update clamav definitions

GRML_SMALL: minimum sized Grml version, known as grml-small (~230MB ISO

LATEX: LaTeX(-related) packages like auctex, texlive,… (which used to be shipped

REMOVE_DOCS: get rid of documentation directories (like /usr/share/doc,

The main directory for configuration of FAI/grml-live. More details below.

Scripts for customising the ISO within the build process.

10. Available log files

11. Requirements for the build system

For further information see next section.

12. Current state of grml-live with squashfs-tools and kernel

13.1. How do I deploy grml-live on a plain Debian installation?

What we have: plain, original Debian jessie (8.x).

# grml stable repository:

# grml testing/development repository:

# get keyring for apt:

# optionally(!) install basefile so we don't have to build basic

# install relevant tools

# adjust grml-live configuration for our needs:

# just optional(!) - upgrade FAI to latest available version:

[*] Successfully finished execution of grml-live [running 687 seconds]

and the ISO can be found inside /grml-live/grml-live/grml_isos/ then.

13.2. What is $GRML_FAI_CONFIG?

13.4. How do I install further files into the chroot/ISO?

echo "CHROOT_INSTALL=\$GRML_FAI_CONFIG/chroot_install" >> /etc/grml/grml-live.local

13.5. Can I use my own (local) Debian mirror?

# cat > /etc/grml/fai/config/package_config/MIKA << EOF

and specify it when invoking grml-live then:

13.7. I fscked up my grml-live configuration. How do I reset it to the

rm -rf /etc/grml/fai /etc/grml/grml-live.conf

13.8. Set up apt-cacher-ng for use with grml-live

Make sure apt-cacher-ng is running (/etc/init.d/apt-cacher-ng restart). That’s it. All

13.9. How do I revert the manifold feature from an ISO?

% dd if=/dev/zero of=grml.iso bs=512 count=1 conv=notrunc

13.10. How do I create a base tar.gz (I386.tar.gz or AMD64.tar.gz)

Finally place the generated tarball in /etc/grml/fai/config/basefiles/ (note that it needs to be

13.11. How to use your own local repository

13.11.1. Serving via bind mount / MIRROR_DIRECTORY

# cat > /etc/grml/fai/config/files/etc/apt/sources.list.d/local-packages.list/CUSTOM

Add the according MIRROR_DIRECTORY configuration to your grml-live configuration:

# echo "MIRROR_DIRECTORY='/home/foobar/packages'" >> /etc/grml/grml-live.local

Make sure the local directory looks like a mirror:

13.11.2. Serving a repository via HTTP

# cat > /etc/grml/fai/config/files/etc/apt/sources.list.d/local-packages.list/CUSTOM

14. Download / install grml-live as a Debian package

git clone git://git.grml.org/grml-live

15. Run grml-live directly from git