Knoppix Documentation Wiki - User contributions [en]

Knoppix Remastering Howto French

2008-05-21T03:45:35Z

202.88.238.45: /* Démarrer les images Knoppix avec GRUB */

== Traductions: ==
* Version Anglaise: [[Knoppix Remastering Howto]]
* Version Allemande: [[Knoppix Remastering Howto Deutsch]]
* Version Espagnole: [[Knoppix Remastering Howto Spanish]] en espagnol
----
== Voir aussi : ==
* Si vous voulez ajouter un noyau personnalisé, regardez le [[Knoppix Custom Kernel Howto]]
* Il y a aussi un guide aux éditions O'reilly sur le même sujet (mais daté de 2003!!): [[http://linux.oreillynet.com/lpt/a/4323 Utiliser et personnaliser Knoppix]]
----
=== Ceci est un guide qui va vous montrer comment remasteriser KNOPPIX ===
(Notes : Les commandes doivent apparaitre sur une ligne, maximisez la fenêtre s'il vous plait. Si vous avez des commentaires/suggestions, merci de les poster ci-dessous.)

Vous voulez peut être commencer à partir d'une Knoppix déjà personnalisée, si tel est le cas vous n'avez probablement pas autant de travail à faire (comme enlever des programmes). Si vous êtes dans ce cas, voir [[Knoppix Customizations]].

==== Système Requis: ====
*CD-ISO
** Au moins 1 GB de mémoire RAM+Swap libre totale (ex 256M ram, et 750M swap DISPONIBLE) (à moins que vous utilisiez un programme de compression différent - voir cette page pour [[http://projects.openoffice.nl/downloads/compressloop/ compressloop]])
** 3 GB de libre sur une partition '''Linux filesystem (ext2/3, xfs, etc.)''' formattée
*DVD-ISO
** 5 GB de RAM + swap libre (pour le DVD en entier)
** 15 GB de libre sur une partition '''Linux filesystem (ext2/3, xfs, etc.)''' formattée

==== Instructions: ====

# Booter à partir du ''Knoppix CD''
# Ouvrir un shell root :
** Menu: Kmenu->Knoppix->Shell Root
** Note: Toutes les commandes ci-dessous s'éxecutent à partir de ce shell root.
# Configurer votre connexion internet (nous en aurons besoin plus tard). Si vous utilisez DHCP, cela devrait déjà être configuré.
** Note: Executez '''ifconfig''' pour vérifier.
# Trouver la partition que vous utiliserez pour travailler. Dans cet exemple, elle est appellée '''hda1''' . La partition devrait avoir au minimum 3 GB d'espace libre.
# Monter la partition:
** '''mount -rw /dev/hda1 /mnt/hda1'''
** Note: Soyez sûr d'avoir les droits en lecture/écriture ou vous aurez des erreurs lors du chroot plus tard. Pour vérifier: éxecuter '''mount'''
# Créer un repertoire racine pour travailler dedans:
** '''mkdir /mnt/hda1/knx'''
** Si vous mettez tous vos fichiers ici, ils seront plus facile à nettoyer
# Si vous n'avez pas 1 GB de RAM ('''cat /proc/meminfo''' (physical+swap)) alors vous devrez avoir un fichier de swap:
** '''cd /mnt/hda1/knx ; dd if=/dev/zero of=swapfile bs=1M count=750 ; mkswap swapfile ; swapon swapfile'''
# Créer 2 repertoires, un pour votre nouveau Master CD, un pour les sources, sur une partition. Créer également des répertoires additionnels sous celui-ci nommé KNOPPIX:
** '''mkdir -p /mnt/hda1/knx/master/KNOPPIX'''
** '''mkdir -p /mnt/hda1/knx/source/KNOPPIX'''
# Maintenant, copiez les fichiers KNOPPIX vers votre répertoire source :
'''cp -Rp /KNOPPIX/*''' '''/mnt/hda1/knx/source/KNOPPIX '''
** Note: Cela peut prendre un petit momment
# Copier la page HTML principale pour la page de démarrage :
** '''cp /cdrom/index.html /mnt/hda1/knx/master/ '''
# Copier tout les fichiers nécessaires execpté le fichier KNOPPIX de ~700 Mb .
** < 3.4: '''cd /cdrom/KNOPPIX;find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;'''
** 3.4: '''cd /cdrom;find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;'''
# Maintenant, vous pouvez "chrooter" dans l'arborescence copiée du fichier KNOPPIX:
** '''chroot /mnt/hda1/knx/source/KNOPPIX'''

Si vous avez un ensemble d'erreurs '''/dev/null permission denied''', vous devriez faire ce qui suit. Ceci peut arriver si vous sauvez vos données configurées pour la Knoppix sur la même partition que celle que vous utilisez, ET si vous démarrrez Knoppix avec '''knoppix home=scan'''.

Vérifiez l'état de vos montages si vous rencontrez le probleme: '''mount /dev/hdaX on /mnt/hdaX type ext3 (rw,nosuid,nodev)''' (remplacer X par le numéro de votre partition) où "nodev" signifie que vous n'avez pas accès au système de fichier monté et que vous ne pouvez ainsi pas acceder à /dev/null. Alors que cetains scripts ont besoin de rediriger leur sortie vers /dev/null ... Pour résoudre ceci, vous devez monter la partiton cible avant de "chrooter", comme ca :
^d # control+d sortira de l'environnement chroot
mount /dev/hda1 /mnt/hda1
Vous devriez ensuite voir:
mount /dev/hda1 on /mnt/hda1 type ext3 (rw)

Si les erreurs "/dev/null" persistent, faites alors avant le chroot :
mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
Vous devez démonter /mnt/hda1/knx/source/KNOPPIX/dev avant de construire l'image du CD ou bien votre répertoire /dev sur le CD sera en bordel !

Ensuite vous pouvez continuer et chrooter.

* Vous êtes maintenant "chrooter". "/" est en fait "/mnt/hda1/knx/source/KNOPPIX"
* Pour utiliser votre connexion internet you devez monter proc '''mount -t proc /proc proc'''
* Maintenant éditer /etc/resolv.conf et ajouter votre serveur de nom ou "sortir" du chroot et copier le fichier resolve.conf dans le dossier chrooté: '''cp /etc/dhcpc/resolv.conf vers /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf'''
* Changer aussi smb.conf vers votre groupe MS si vous voulez le support smbd (MSHOME pour XP Familliale édition, et WORKGROUP pour les Windows 9x).
* Vérifiez votre connection internet chrootée : '''ping google.com'''
* Mettez à jour votre list de paquet avec '''apt-get update'''
* Maintenant vous pouvez changer des trucs.
* '''Attention''': apt-get upgrade est une MAUVAISE IDEE. Cela va, très probablement, rendre votre KNOPPIX remasterisée inbootable, ou cassée en quelque sorte. Une méthode bien plus sûre est de seulement mettre à jour les paquets nécessaires
** Avant de pouvoir ajouter des choses, vous aurez probablement besoin d'enlever quelques packages. Pour avoir une liste des packages installé, tapez ce qui suit:
'''*''' '''dpkg-query -l'''
** Si vous voulez une liste triée par taille (de cette façon vous vous pourrez vous débarassez des plus encombrants), tapez :
'''*''' '''dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n'''
** Pour enlever un paquet (et toutes ses dépendances), tapez:
'''*''' '''apt-get remove <name-of-package-to-remove>'''
** Pour vérifier les paquets orphelins, tapez:
'''*''' '''deborphan'''
** Pour vouloir économiser plus de place en se débarrassant de ces irritants orphelins (comme c'est cruel!), tapez ('''Attention''', vous n'aurez pas à confirmer pour enlever ces paquets. Quand vous pressez Entrée après cette commande, ces paquets '''seront partis'''):
'''*''' '''deborphan | xargs apt-get -y remove'''
** Si vous êtes incertain quand à la commande précèdente et voulez voir ce qu'il va se passer sans faire de changement, ajoutez simplement l'option '''-s''' à la commande apt-get comme cela (vous pouvez faire ça avec toutes les commandes apt-get, et c'est une bonne habitude d'utiliser cette option avant des opérations "massive" comme celle la):
'''*''' '''deborphan | xargs apt-get -s -y remove'''
** Maintenant les bonnes choses. Si vous voulez ajouter un package, tapez:
'''*''' '''apt-get install <name-of-package-to-install>'''
** Quoi, vous ne savez pas quel paquet installer ? Tapez cela. Quand la liste apparait, vous pouvez lire attentivement (13000 lignes !) ou chercher des termes en utilisant '''/<terme-a-recherher>''':
'''*''' '''apt-cache search .* | sort | less'''
** Quand vous avez fini d'enlever et d'ajouter des paquets, un bon moyen de nettoyer est de taper:
'''*''' '''COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P'''
** De même,parce que le système des paquets Debian garde en cache ce qui a été téléchargé, vous pouvez éxecuter la commande suivante pour faire le ménage :
'''*''' '''apt-get clean'''
** les paramètres utilisateurs sont dans /etc/skel
** astuce: ne mettez pas de fichiers dans /root ils seront seulement disponible (durant l'éxecution) dans /KNOPPIX/root
* Unmount /proc - très important! '''umount /proc'''
* Presser '''CTRL+D''' pour quitter l'environnement chrooté.

==== Notes : ====

Quand vous testez des programmes basés sur X, vous aurez a faire '''export DISPLAY=localhost:0.0'''

Quand vous voulez auto-éxecuter quelques programmes, créez un script et placez le dans le repertoire /etc/rc5.d/ (Ceci charge seulement les items avant que X ne se charge)

trucs interessants dans /etc/init.d/knoppix-autoconfig :
* Le fichier fond d'écran est /cdrom/KNOPPIX/background.gif '''(dans knoppix 3.4: background.jpg)'''
* Comme pour floppyconfig, il existe cdromconfig qui lancera cdrom/KNOPPIX/knoppix.sh

trucs intéressants dans /etc/init.d/xsession :
* Ca place également le fond d'écran dans /usr/local/lib/knoppix.gif

Maintenant, la création de l'image ISO :

* nous avons fini de personnaliser et sommes prêt à graver !
* d'abord faire quelques nettoyages : ''' enlever le fichier .bash_history , les fichiers tmp etc '''
* '''rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved'''
* Maintenant, nous allons faire un gros fichier KNOPPIX qui est un système de fichier ISO 9660 cloop (compress loopback) compressé (cloop compressed ISO 9660 filesystem) : '''mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" -hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX | nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX'''

le "www.knoppix.net" et le "Knoppix.net filesystem" peuvent être changé par le nom que vous voulez donner au fichier. Vous aurez une erreur si vous ne respectez les standards de la norme ISO9660, sans trop grande importance.

Dans Knoppix 3.4 le script create_compressed_fs a été mis à jour, utilisez le pour obtenir les meilleurs résultats.
Il possède une nouvelle option '''-b''' (best), qui permet une meilleure compression en utilisant différents arrangement de compression et essaye d'optimiser ce processus, mais soyez vigilant, parce que cette option est lente (10x plus lente).

* Si tout va bien, faisons l'image du CD final :
* '''cd /mnt/hda1/knx/master'''
* '''rm -f KNOPPIX/md5sums; find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin -exec md5sum '{}' \; >> KNOPPIX/md5sums''' (ceci va mettre à jour les hashages md5 des fichiers inclus dans l'ISO, utilisé pour les vérifications d'intégrité)
* Pour Knoppix <= 3.3: '''mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat -hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master''' (the ISO is stored in /mnt/hda1/knx/knoppix.iso)
* Pour Knoppix >= 3.4 ou autre distribution basée sur isolinux, faites:
'''mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master''' (l'ISO est stockée dans /mnt/hda1/knx/knoppix.iso)
* Voila !

=== Astuces ===
Si vous êtes à la recherche des gros paquets installés, alors la commande
: dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
: awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
: perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
listera les paquets par taille en ordre décroissant.
Cette commande est 10 fois plus rapide

: dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n

et vous n'avez pas besoin de dpkg-awk ou awk ou perl.

Si vous avez des problèmes avec la commande de tri précèdente, essayez d'utiliser KPackage, elle parcoure les arborescences et trie par taille à la recherche de gros paquets.

Regardez du côté du programme "deborphan", il liste les paquets orphelins que vous pouvez enlever, ces paquets étaient utilisés par des paquets qui sont maintenant enlevés.

J'ai eu des bons résultats de remastering à partir du cd en tant que root, travaillant à partir de fluxbox. Choisir "knoppix 2" lors du boot et le système va démarrer sur une invite de commande root où vous pourrez dire "startx /usr/bin/fluxbox". J'aime utiliser le shell unicode xterm.

Lors du travail en chroot pour le remastering, j'aime bien utiliser "apt-get remove --purge nom-du-paquet" pour enlever les paquets parce que avant de faire quoi que ce soit cela va stopper et montrer les détails sur ce que apt va supprimer; il faut confirmer par "oui" ou "non".

Si vous n'utilisez pas l'instruction "apt-get" ci dessus et si vous avez beaucoup de ménage à faire, la façon la plus simple de faire est :
"COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' >topurge". Ceci fera une liste de tout les paquets enlevés à purger et ensuite vous n'avez plus qu'a faire "dpkg -P `cat topurge `" et voila.
"COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P" est la même chose en une ligne.
Aussi "deborphan >orphaned" puis "dpkg -P `cat orphaned `". "deborphan | xargs dpkg -P " est une version en une seule ligne de cela.

Ca y est. Ceci est une version mise à jour de mon précèdent howto. Il n'est pas destiné aux débutant sous linux, vous devriez avoir une bonne connaissance de linux pour tout faire fonctionner. Je le metterais à jour via des corrections et des améliorations bientôt.

Merci a aay, charan, Tech2k, and #knoppix pour les quelques corrections, astuces et idées. Libre à vous d'éditer ou de compléter ce how-to
Note à propose de la swap: 
Vous n'avez pas réellement besoin d'1G de swap puisque il y a deux nouveaux outils de compressions de système de fichiers. Voila deux candidats pour faire des système de fichiers ''compressés'':
* Réecriture de Valentijn [http://projects.openoffice.nl/downloads/compressloop/]
* Port de compressloop par Quozl's pour la Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Compressloop répartis par Quozl's (utiliser plus d'un processeur pour accelerer les choses) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Patch de Justin [http://s.bouncybouncy.net/~justin/code/] (lien cassé) J'ai également écrit un compresseur réparti cloop (ou pour smp) C'est dans le même repertoire.

==== Astuce, tester le cd-image sans graver le cd ====

Si vous avez une partition avec au moins 700MB d'espace libre formattée en ext2, ext3 ou Vfat, vous pouvez l'utiliser pour tester en démarrant à partir d'une disquette. Une disquette de démarrage recherchera une partition avec /KNOPPIX dans la racine, et l'image compressée /KNOPPIX/KNOPPIX. Au lieu d'utiliser le sous répertoire /mnt/hda1/knx/master/KNOPPIX/ comme décrit précèdemment, il devrait être appellé /mnt/hda2/KNOPPIX/ . La racine index.html sera située dans /mnt/hda2/index.html et l'image compressée sera dans /mnt/hda2/KNOPPIX/KNOPPIX . Maintenant vous pouvez booter à partir de la disquette et utiliser /mnt/hda2 comme image. Pour plus d'informations voir [[Hd BasedHowTo]].

Si vous n'avez pas de partitions supplémentaires ou si vous ne voulez pas en faire autant, vous pouvez utiliser Qemu (voir
[http://fabrice.bellard.free.fr/qemu/] ) avec l'image ISO comme ça:
'''qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -user-net'''
Vous n'avez même pas à créer une image sur le disque dur avant, seulement installer Qemu et l'essayer. Stupéfiant!

==== Démarrer les images Knoppix avec GRUB ====
* D'abord copier /boot du cd Knoppix cd vers votre partition de boot (ou même votre partition dos). J'ai nommé la mienne boot.knoppix
''' Copier le répertoire /KNOPPIX vers votre '''répertoire racine* d'un des diques dur. Vous pouvez le placer ailleurs que dans une partition de boot. (ext2/3, reiserfs, vfat sont supportés)
* Mettre les éléments suivants dans votre /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* Remarquer le paramètre "fromhd": c'est l'emplacement du repertoire /KNOPPIX
* redémarrez et appreciez.

Si mon how-to est trop confus, ou si vous voulez une secondes opinion, regardez le très joli remastering howto de charan :
http://brainstorms.in/?page_id=84.
Un autre howto est disponible à l'adresse http://www.stirnimann.com/mystuff/doc/knoppix.txt

Il y a un assistant qui connais toutes les démarches d'installation, compression et gravure de CD mentionnées ici. Il propose également un shell ou vous pouvez mettre à jour la KNOPPIX décompressée en utilisant les outils standards Debian d'installation de logiciel. Il s'appelle mmkcdrom et fait partie du packaqe plugscript: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Encore un autre Howto, pour les adeptes du shell sur http://quozl.linux.org.au/knoppix/

Soyez sûr de jeter un oeil à [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] pour des idées et de l'aide concernant le remastering.
----
Une l'arborescence recommandée pour remasteriser une KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
Le script suivant "remaster" fera le processus de remasterisation à votre place. Lancez le en tant que root, ou il se terminera avec des erreurs d'accès sur l'image.

Le script a été essayé sur une Debian sid le 02-04-2002

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create''compressed''fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
The following script will loop-mount boot floppy image and initrd image for modification. The umount function will build a new initrd image and put it back on the boot floppy image.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto Brazilian Portuguese

2008-05-21T03:44:03Z

202.88.238.45: /* Veja Também */

Este guia mostrará a você como remasterizar o '''KNOPPIX''' a partir do CD original em inglês. Isto significa que muitas configurações precisarão ser feitas para deixar o sistema do jeito que você quer.

Se quiser evitar muito trabalho na remasterização (tal como adicionar ou remover programas), você pode começar a partir de uma versão personalizada do Knoppix. Se quer isso, consulte o tópico [[Knoppix Customizations]], que trata de diversas distribuições adaptadas baseadas no Knoppix (geralmente, em inglês) e voltadas para uma área específica.

Observações:
* Este guia é uma tradução livre do texto original. Alguns comentários/observações foram acrescentados por alguns usuários, manifestando experiências pessoais. Alguns pontos mal-entendidos foram marcados como "obscuros".
* Os comandos de terminal mostrados neste texto devem ser digitados em uma única linha, isto é, não pode haver quebras de linha. Onde houver a barra invertida ("\"), significa que o comando continua na linha seguinte, mas a barra invertida em si não deveria ser digitada.
* Se você tem algum comentário/sugestão, por favor, utilize a guia ''Discussion'' na parte superior da página.

===Requisitos do Sistema===
* CD-ISO
** pelo menos 1 GB de espaço total de RAM+swap (e.g. 256 MB RAM + 750 MB swap DISPON�?VEIS) (a não se que você utilize um programa de compressão diferente - procure nesta página por "compressloop")
** 3 GB livres numa partição de disco formatada com '''sistema de arquivos Linux''' (ext2, ext3, reiserfs, xfs, etc.)
* DVD-ISO
** 5 GB livres de espaço de RAM+swap (para um DVD completo)
** 15 GB livres numa partição de disco formatada com '''sistema de arquivos Linux''' (ext2, ext3, reiserfs, xfs, etc.)

===Preparando a Remasterização===
# Inicialize o computador a partir do ''CD do Knoppix''
# Abra um "shell" como "root": '''KMenu => Knoppix => Root Shell'''
#* Nota: Todos os comandos seguintes são executados dentro deste "shell" como "root".
# Configure sua conexão com a Internet (você precisará disto mais tarde).
#* Nota 1: Se você usa DHCP, pode ser que a conexão já esteja configurada.
#* Nota 2: Execute <tt>ifconfig</tt> para checar as configurações.
# Defina a partição que você utilizará no trabalho. Neste guia, ela será chamada de '''hda1'''. A partição deverá ter um mínimo de 3 GB de espaço livre.
# Monte a partição:
#:<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Nota: O parâmetro <tt>-rw</tt> serve para habilitar a partição para leitura e escrita. Isso é importante, pois do contrário o comando <tt>chroot</tt> dará erros. Utilize o comando <tt>mount</tt> sem nenhum parâmetro para verificar essa habilitação.
# Crie um diretório-raiz para trabalhar nele:
#:<pre>mkdir /mnt/hda1/knx</pre>
#*Nota: Se você puser todos os seus arquivos aqui será mais fácil fazer limpeza depois.
# Se você não tem RAM de 1 GB (verifique com <tt>egrep (MemTotal|SwapTotal) /proc/meminfo</tt>(=RAM+swap) ou <tt>cat /proc/meminfo (=RAM+swap)</tt>), então você precisará de um arquivo de trocas ("swap"):
#:<pre><nowiki>
cd /mnt/hda1/knx
dd if=/dev/zero of=swapfile bs=1M count=750
mkswap swapfile
swapon swapfile
</nowiki></pre>
# Crie outros dois diretórios, um para seu novo CD mestre e outro para a fonte, na partição de trabalho. Crie também subdiretórios chamados "KNOPPIX" dentro de cada um:
#:<pre><nowiki>mkdir -p /mnt/hda1/knx/master/KNOPPIX
mkdir -p /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# Agora, copie os arquivos de "/KNOPPIX" para o diretório-fonte:
#:<pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Nota: Isto vai demorar muito, pois estamos copiando 2 GB.
#* Aviso: Para fazer a cópia mais rápido, poderíamos utilizar o comando <tt>unionfs</tt>. Porém, a partir do Knoppix 4.0.2 há um erro no <tt>unionfs</tt>, o que impede a sua utilização. É melhor utilizar o comando <tt>cp</tt> mesmo.
# Adicionalmente, copie o diretório "boot" do CD:
#:<pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
#* Nota: Você precisará destes arquivos para construir o arquivo ISO mais tarde.
# Para o Knoppix 5.0.1. você também deve copiar o diretório "modules":
#:<pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copie a página HTML principal para funcionar como página inicial:
#:<pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copie todos os arquivos necessários, exceto o arquivo KNOPPIX (que tem cerca de 700 MB):
#* Para Knoppix < 3.4:
#:<pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* Para Knoppix >= 3.4:
#:<pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* Nota: Para a versão em DVD, você terá de usar <tt>-size -15000k</tt> e copiar o diretório KNOPPIX2 assim: <tt>cp /cdrom/KNOPPIX/KNOPPIX2 /mnt/hda1/knx/master/KNOPPIX/</tt>
# Prepando o ambiente para o comando <tt>chroot</tt>:
#:<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</nowiki></nowiki></pre>
# Agora, você pode entrar como "chroot" dentro do diretório KNOPPIX copiado na partição (isto é, tornar o diretório "knx/source/KNOPPIX" a partição "root" do novo sistema):
#:<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# Se você obtiver erros relativos a <tt>/dev/null</tt> aos montes, consulte a sessão [[#Problemas Comuns|Problemas Comuns]].

Neste ponto, você estará como "chroot". Portanto, o "/" é realmente <tt>"/mnt/hda1/knx/source/KNOPPIX"</tt>.

===Configurando como "chroot"===

Lembre-se de que qualquer coisa que você faça ou crie no ambiente como "chroot" será "queimado" no CD. Se você faz alguma alteração (por exemplo, configurações no APT, no proxy, etc.), tome nota destas coisas para conseguir desfazer as mudanças antes da remasterização.

====Configurando o acesso à Internet====
Para usar a Internet você precisa editar o arquivo <tt>"/etc/resolv.conf"</tt> para adicionar o nome do servidor (ou saia do modo "chroot" e copie o arquivo <tt>"resolv.conf"</tt> exterior para o diretório de trabalho:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf

A configuração de proxy pode ser exportada com
export http_proxy=<nowiki>http://your.proxy.com</nowiki>:<''porta-proxy''>

Para confirmar a conexão com a Internet dentro do ambiente "chroot", teste algo como
ping google.com

Se o ICMP for barrado em algum firewall ou semelhante, tente
<nowiki>lynx http://www.google.com</nowiki>
e verifique se obtém a página após permitir "cookies".

====Configurando o SAMBA====
Se deseja suporte ao serviço "smbd", altere o grupo de trabalho no arquivo <tt>"smb.conf"</tt> para o grupo de trabalho da rede local Windows. No caso do Windows XP, o padrão é "MSHOME".

====Adicionando e removendo pacotes====
=====Atualizando a lista de pacotes=====
Atualize a lista de pacotes do APT com "<tt>'''apt-get update'''</tt>".
* Nota: Se o comando "<tt>apt-get update</tt>" resultar no erro "FATAL -> Could not set non-blocking flag Bad file descriptor", você precisará se certificar de que seu ambiente "chroot" está montado sem a opção "<tt>nodev</tt>". Consulte o item sobre erros no "<tt>/dev/null</tt>" quando entra com ambiente "chroot" pela primeira vez.
* Aviso: O comando "<tt>apt-get upgrade</tt>" é uma ''M�? IDÉIA''. Muito provavelmente, isso tornará o disco remasterizado do KNOPPIX não-inicializável ou defeituoso de alguma forma. O método mais seguro é fazer atualização somente dos pacotes necessários.
* Nota: Se o "<tt>apt-get</tt>" resultar no erro "Dynamic NMap ran out of room", você pode tentar o seguinte truque, que já resolveu o problema em alguma situação:
*:<pre>echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf</pre>
*:Nota: Isso foi feito como "chroot" conforme descrito acima.

=====Listando pacotes=====
Antes de poder adicionar programas, você provavelmente precisará remover alguns pacotes. Para obter uma lista de pacotes instalados, tecle isto:
dpkg-query -l
Se você está procurando por pacotes instalados pelo tamanho, para identificar os que ocupam mais espaço, então utilize o comando a seguir, que vai listar os pacotes em ordem decrescente de tamanho:
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg

O comando a seguir é, pelo menos, dez vezes mais rápido:
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
e você não precisa de "<tt>dpkg-awk</tt>" ou "<tt>awk</tt>" ou "<tt>perl</tt>"; entretanto, ele não exclui pacotes que não estejam instalados. Se você tiver problemas com o comando "<tt>sort</tt>" acima, tente usar "<tt>KPackage</tt>", expandido em todas as árvores e ordenado pela coluna de tamanho para encontrar os maiores pacotes.

Ou, você poderia usar este comando para obter velocidade no comando "<tt>dpkg-query</tt>" com os pacotes não-instalados que não forem listados:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
Ele faz a mesma coisa anterior, para os que não têm o "<tt>dpkg-awk</tt>".

=====Removendo pacotes indesejados=====
Para remover um pacote (e todos os pacotes dependentes dele), tecle isto:
apt-get remove --purge ''name-of-package-to-remove''
Para verificar se há pacotes órfãos, tecle isto:
deborphan
Se quer salvar mais espaço retirando os pacotes órfãos irritantes {?}(que crueldade!){?}, tecle isto (Cuidado: O "yes/no" não não aparecerá para confirmar a remoção destes pacotes. Quando você pressionar Enter depois deste comando, os pacotes terão desaparecido!):
deborphan | xargs apt-get -y remove
Se você não está seguro sobre o comando anterior e quer ver o que acontecerá sem fazer nenhuma mudança, simplesmente adicione a opção "<tt>-s</tt>" ao comando "<tt>apt-get</tt>" como isto (você pode fazer isto com todos os comandos "<tt>apt-get</tt>", e é um bom hábito usar esta opção antes de operações em massa como esta):
deborphan | xargs apt-get -s -y remove

=====Adicionando pacotes=====
Agora, a parte boa. Se você deseja adicionar um pacote, tecle isto:
apt-get install '''name-of-package-to-install''
Então não sabe que pacotes instalar? Tecle isto:
apt-cache search .* | sort | less
Quando a lista aparecer, você pode examiná-la (mais de 13 mil linhas!) ou procurar por textos usando o comando "/": <tt>/''texto-a-procurar''</tt>.

=====Limpando o cachê=====
Quando você terminar de remover e adicionar pacotes, uma boa maneira de limpar tudo é teclando isto:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Também, dado que o sistema de pacotes do Debian guarda em "cachê" os pacotes baixados, você pode querer fazer a seguinte limpeza daqueles arquivos inúteis:
apt-get clean

====Configurando as configurações de novo usuário====
As configurações de usuário estão em "<tt>/etc/skel</tt>. Este diretório será copiado para fazer os diretórios "home" dos novos usuários.
* Dica: Não coloque arquivos em "<tt>/root</tt>" pois eles serão somente disponíveis (em tempo de execução) em "<tt>/KNOPPIX/root</tt>".

Observe que o usuário padrão "knoppix" não é criado com "<tt>adduser(1)</tt>", logo o diretório "<tt>/etc/skel</tt>" não é completamente copiado, mas seletivamente. Isto é, para fazer um arquivo "<tt>.xyrc</tt>" aparecer em "<tt>/home/knoppix</tt>" não é suficiente colocá-lo em "<tt>/etc/skel</tt>". Uma possibilidade é estender o código em "<tt>/etc/X11/Xsession.d/45xsession</tt>" o qual é responsável por preencher o diretório "<tt>/home/knoppix</tt>".

Note that the default user 'knoppix' is not created by adduser(1), thus /etc/skel is not copied completely but rather selectively. That is, to make a file .xyrc appear in /home/knoppix, it is not sufficient to place it in /etc/skel. One possibility is to extend the code in /etc/X11/Xsession.d/45xsession which is responsible for filling /home/knoppix.

====Autoexecutando programas====
Quando você quer autoexecutar alguns programas, pode-se criar um script e pô-lo no diretório "<tt>/etc/rc5.d/</tt>", que executa itens antes de o ambiente X ser carregado. Pesquise o processo "init" para conhecer mais possibilidades.

====Editando o script de auto-configuração do KNOPPIX====
Você pode encontrar muita informação interessante sobre como o KNOPPIX auto-configura seu sistema estudando o script "<tt>/etc/init.d/knoppix-autoconfig script</tt>". As seguintes configurações são particularmente notáveis.

=====Trocando a figura de plano de fundo do KDE=====
O script de auto-configuração configura como figura do plano de fundo padrão do KDE uma figura presente no CD-ROM. Esta figura pode ser facilmente trocada quando você está remasterizando o KNOPPIX.
* No Knoppix 3.3 e abaixo ela está em "<tt>/cdrom/KNOPPIX/background.gif</tt>"
* No Knoppix 3.5 e acima ela está em "<tt>/cdrom/KNOPPIX/background.jpg</tt>"
{?}Como trocar, então?{?}

=====Editando o uso da unidade de disquete e de CD-ROM ou adicionando um script personalizado=====
O script de auto-configuração configura ambas as unidade de disquete e de CD-ROM. Os comandos que fazem isso são "<tt>floppyconfig</tt>" e "<tt>cdromconfig</tt>", respectivamente. O script de auto-configuração também executará "<tt>cdrom/KNOPPIX/knoppix.sh</tt>", o qual é um script fácil de alterar quando remasterizando.

=====Alterando os parâmetros de inicialização padrões=====
Todos os parâmetros de "boot" obtêm valores padrões a partir do script "<tt>/etc/init.d/knoppix-autoconfig</tt>". Este é um script em "bash" muito complexo (você precisa conhecer bastante o "bash" para lidar com ele), mas é o local onde você pode editar qualquer dos parâmetros padrões. Por exemplo, você poderia procurar ocorrências de "kde" para alterar para "twm" nas variáveis que indicam o desktop padrão (DESKTOP, IIRC, etc.). Outro exemplo poderia ser a mudança do idioma padrão.

* Nota: Se você está interessado em trocar o idioma padrão que o KDE utiliza, a maneira mais fácil é carregar o KDE (veja as instruções abaixo) e usar o utilitário de configuração do KDE para selecionar o idioma desejado.

====Configurando a sessão do X====
Quando trabalha com programas baseados no ambiente X, você precisa se certificar de que o seu monitor está configurado corretamente. Você pode fazer isto manualmente quando remasteriza o KNOPPIX. Também, em dois scripts relativos à Sessão X você pode mudar ou desabilitar os sons de inicialização e desligamento.

=====Iniciando programas baseados no ambiente X=====
Quando testando programas baseados no ambiente X, você terá que
export DISPLAY=localhost:0.0
que permitirá a você se conectar com o a sua sessão X normal. Alternativamente (se você precisar testar gerenciadores de janelas), você pode criar uma sessão aninhada. Fora do "chroot", execute
Xnest -ac :1
Dentro do "chroot", configure a sua variável DISPLAY
export DISPLAY=localhost:1
Uma coisa interessante em "<tt>/etc/inid.d/xsession</tt>":
* ele TAMBÉM coloca o plano de fundo como "<tt>/usr/local/lib/knoppix.gif</tt>".

=====Modificando/Desabilitando o som de inicialização=====
O som da inicialização é tocado por "<tt>/etc/X11/Xsession.d/45xsession</tt>". Você pode desabilitá-lo colocando comentários (#) nas seguintes linhas:

<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

=====Modificando/Desabilitando o som de finalização=====
O som da finalização é tocado por "<tt>/etc/X11/Xsession.d/45xsession</tt>". Você pode desabilitá-lo colocando comentários (#) nas linhas 210-220 do script:

<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

====Trocando a imagem e a mensagem de "boot" e o texto do script de inicialização====
Ainda no ambiente "chroot", você poderá facilmente trocar a imagem e as mensagens que aparecem durante a inicialização e a figura de plano de fundo padrão do KDE.

=====Trocando a imagem de "boot"=====
A imagem de "boot" é a primeira imagem que você vê na tela no momento da inicialização do Knoppix com CD ou DVD. Ela é semelhante a arte de texto ASCII e é normalmente o texto "Knoppix" algo "brilhante". Você pode trocar isto para qualquer figura que tenha resolução de 640x400 e somente 16 cores.
# Mude para o diretório <tt>/mnt/hda1/knx/master/boot</tt> (altere "/mnt/hda1/" para refletir a sua configuração particular):
#:<pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
# Faça cópia de segurança do antigo logotipo no caso de algo dar errado:
#:<pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
# Crie uma figura de 640x400 pixels com 16 cores e salve-a como GIF, por exemplo, "logo.16.gif". Utilize o GIMP ou KolourPaint, por exemplo.
#*Nota: Você pode usar uma imagem que originalmente tenha mais de 16 cores, mas terá que forçosamente convertê-la para 16 cores antes de continuar este procedimento.
# Converta a figura GIF para "lss16" usando as ferramentas incluídas no CD do Knoppix:
#:<pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm
ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

=====Trocando a mensagem de "boot"=====
A mensagem de "boot" é o texto que você vê sob a imagem de "boot" na tela no momento da inicialização do Knoppix com CD ou DVD. Esse texto diz algo sobre a versão do Knoppix e um linque para o saite do Knoppix. Você pode alterar esse texto para o que quiser, mas não deve colocar muito texto ou a tela de "boot" ficará engraçada. Restrinja a apenas uma linha de texto que não seja maior do que a original.

# Mude para o diretório <tt>/mnt/hda1/knx/master/boot</tt> (altere "/mnt/hda1/" para refletir a sua configuração particular):
#:<pre><nowiki>cd /mnt/hda1/knx/master/boot</nowiki></pre>
# Faça cópia de segurança da mensagem original no caso de algo dar errado:
#:<pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
# Edite a mensagem com um editor de textos. Você verá no topo do arquivo uma mensagem: Não altere esse texto, apenas as linhas abaixo:
#:<pre><nowiki>vi boot.msg</nowiki></pre>

=====Alterando o texto do script de inicialização=====
O texto do script de inicialização é o texto que você vê depois da tela de "boot", enquanto o Knoppix carrega e configura o sistema. Você pode alterar esse texto como melhor achar, até mesmo adicionar novas linhas ao script; entretanto não recomendamos "mexer" nesse arquivo. Limite-se a editar apenas a mensagem "Benvindo ao KNOPPIX".

# Mude para o diretório <tt>/mnt/hda1/knx/master/boot</tt> (altere "/mnt/hda1/" para refletir a sua configuração particular):
#:<pre><nowiki>cd /mnt/hda1/knx/master/boot</nowiki></pre>
# Faça cópia de segurança do "minirt.gz" original no caso de algo dar errado:
#:<pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
# Descomprima "minirt.gz":
#:<pre><nowiki>gunzip minirt.gz</nowiki></pre>
# Crie um diretório temporário para montar o sistema de arquivos "minirt":
#:<pre><nowiki>mkdir todelete</nowiki></pre>
# Monte o sistema de arquivos "minirt" como "ext2":
#:<pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
# Edite o script <tt>linuxrc</tt> para mostrar a mensagem que você deseja. Você vai encontrar a mensagem padrão com aproximadamente 2 páginas e configurada com várias cores, i.e. ${WHITE}, ${RED}, etc., tornando difícil a leitura.
#:<pre><nowiki>vi todelete/linuxrc</nowiki></pre>
# Desmonte o sistema de arquivos "minirt":
#:<pre><nowiki>umount todelete</nowiki></pre>
# Comprima o sistema de arquivos "minirt":
#:<pre><nowiki>gzip -9 minirt</nowiki></pre>
# Remova o seu diretório temporário:
#:<pre><nowiki>rmdir todelete</nowiki></pre>

====Abrindo o KDE para modificar menus, ícones, etc.====
Enquanto estiver no ambiente "chroot", você pode carregar o KDE e usar as ferramentas de configuração do próprio KDE para modificar botões, menus, ícones, etc. Quando terminar, você pode sair do KDE e copiar os arquivos de "<tt>/home/knoppix</tt>" para "<tt>/etc/skel</tt>" para manter estas mudanças. Para carregar o KDE faça o seguinte:

# Se você não está no "runlevel" 2 (i.e., se você ainda está no KDE), mude para o "runlevel" 2.
#:<pre><nowiki>init 2</nowiki></pre>
# Copie os arquivos de "<tt>/etc/skel</tt>" para "<tt>/home/knoppix</tt>".
#:<pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
# Mude as permissões de dono do diretório "<tt>/home/knoppix</tt>" para o usuário "knoppix".
#:<pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
# Copie a configuração de X11 exterior sobrepondo a do ambiente do "chroot" (pressione Ctrl+Alt+F2 para ir para um terminal "não-chroot" e então pressione Ctrl+Alt+F1 para voltar quando tiver feito a cópia).
#:<pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#** Nota: No Knoppix 3.7 é o arquivo "<tt>XF86Config-4</tt>" no lugar de "<tt>xorg.conf</tt>".
# (Opcional) Mude para o usuário "knoppix". Se você quiser desinstalar pacotes, fique como "root" e pule este passo. Se você quer configurar botões, ícones, plano de fundo, etc. que você vê quando o KDE inicia, assegure-se de fazer este passo.
#:<pre><nowiki>su knoppix</nowiki></pre>
# Inicie o KDE
#:<pre><nowiki>startx</nowiki></pre>
# Faça as mudanças no KDE
# Saia do KDE
#(Opcional - faça este passo somente se você fez o passo 5) Saia do "su" e volte para o usuário "knoppix".
#:<pre><nowiki>exit</nowiki></pre>
# Copie o diretório "<tt>/home/knoppix</tt>" de volta a "<tt>/etc/skel</tt>" para manter as mudanças.
#:<pre><nowiki>mv /etc/skel /etc/skel-old
mv /home/knoppix /etc/skel</nowiki></pre>
# Reconfigure o dono de "<tt>/etc/skel</tt>" como "root".
#:<pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
# Remova o arquivo "<tt>xorg.conf</tt>" {?}por quê?{?}
#:<pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>

=====Trocando a imagem "ksplash" do KDE=====
Você pode mudar a imagem que o KDE exibe via "ksplash" quando ele inicializa. Estas imagens estão no diretório "<tt>/mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/</tt>". Você provavelmente vai querer trocar o arquivo "<tt>splash_top.png</tt>" por uma figura PNG personalizada de 400x248 de resolução. Note que o "ksplash" não colocará automaticamente uma borda ao redor da figura. Se você quiser uma borda, terá que manualmente editar a figura.

====Saindo do "chroot"====
Isto deve acontecer só depois das configurações e antes da criação do arquivo ISO.

Se você montou "<tt>/proc</tt>", você precisará desmontá-lo -- isto é muito importante!
umount /proc
Pressione Ctrl+D para voltar à raiz original (ou seja, sair de "chroot").

===Remasterizando o arquivo ISO===
Terminada a parte da personalização, estamos prontos para "queimar" o CD/DVD!
Primeiro, façamos algumas limpezas:
* remova qualquer arquivo .bash_history, tmp, etc.
* reverta qualquer mudança que você não deseja que vá para o disco
*:<pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

====KNOPPIX Compressed Image====
====Imagem compactada do KNOPPIXX====
Agora, vamos fazer o grande arquivo "<tt>KNOPPIX</tt>" que é um sistema de arquivos ISO 9660 compactado para ser utilizado com o dispositivo "<tt>cloop</tt>":
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
Os textos "www.knoppix.net" e "Knoppix.net filesystem" podem ser trocados para qualquer texto com que você queira nomear o arquivo. Você vai obter um erro sobre não estar em conformidade com padrões ISO -- você pode ignorar isto. Note que, para executar "<tt>create_compressed_fs</tt>", você vai precisar ter bastante espaço para armazenar o arquivo ISO inteiro na RAM/Swap. Certifique-se de ter, pelo menos, 800 MB de espaço livre antes de começar.

No Knoppix 3.4 o script "<tt>create_compressed_fs</tt>" foi atualizado. Logo, certifique-se de utilizá-lo para obter o melhor resultado. Ele tem uma nova opção "-b" (de "best"), que habilita a
melhor compressão pela utilização de diferentes esquemas de compressão e tenta otimizar dessa maneira. Mas, seja cuidadoso, porque essa opção torna a compressão 10 vezes mais lenta.

* Nota: Isso acima não funcionou para mim usando o último script "create_compressed_fs". Eu pude criar o ISO mas ele não pode ler a imagem compactada propriamente quando inicializa (erros de E/S quando lendo o dispositivo "cloop0"). Eu penso que isto foi porque o "create_compressed_fs" não teve bastante RAM e fracassou silenciosamente. O comando abaixo funcionou, todavia. Ele usa um
arquivo temporário ao invés da memória para armazenamento temporário:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/sda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

====O Live-CD ISO====
Se tudo correu bem, vamos fazer a imagem de CD-ROM final:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(isto vai atualizar os códigos "md5" dos arquivos incluídos no ISO, que são usados para verificar a integridade)
Agora, vamos queimar a imagem:
Para Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
Para Knoppix >= 3.4 ou outras distribuições baseadas em "isolinux":
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(o ISO é armazenado em "<tt>/mnt/hda1/knx/knoppix.iso</tt>")

Queime o ISO no CD/DVD utilizando sua ferramenta de gravação favorita, e você está feito!

===Dicas===
====No Fluxbox====
Eu tenho tido bons resultados remasterizando a partir do CD como "root" dentro do "Fluxbox". Apenas digite "knoppix 2" no prompt de "boot" e ele inicializará para você um prompt de "root" onde você poderá fazer "start x /usr/bin/fluxbox". Eu gosto de usar o "shell" do "xterm" em modo "unicode".

====Gerenciamento de pacotes====
Enquanto estou no modo "chroot" fazendo a remasterização eu gosto de usar
apt-get remove --purge pkg-name
para remover pacotes, porque antes de fazer algo, ele parará e mostrará detalhes sobre o que está programando para remover e deixará você responder "yes" ou "no".

Se você não usar as instruções do "apt-get" acima e tiver muita coisa para limpar e expurgar, aqui está uma maneira fácil de fazer isso:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
Isso vai fazer uma lista de todos os pacotes removidos para expurgo e então você só precisará fazer:
dpkg -P `< topurge `
e estará terminado.
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
é a mesma coisa, mas em uma única linha.
Use também isso:
deborphan | xargs dpkg -P .

====Alternativas para máquinas com pouca memória====
Você não precisa realmente de 1 GB de "swap" já que existem duas novas ferramentas para criar sistemas de arquivos compactados. Aqui estão alguns candidatos para fazer compressão:
* "Rewrite" de Valentijn -- http://projects.openoffice.nl/downloads/compressloop/
* Portagem do "compressloop" para Knoppix 3.4 de Quozl -- http://quozl.linux.org.au/compressloop-1.9-64bit.c
* "Compressloop" distribuído de Quozl (usa mais que um processador para acelerar as coisas) -- http://quozl.linux.org.au/knoppix/compressloop/ ou http://quozl.netrek.org/knoppix/compressloop/
* Remendo do Justin -- http://s.bouncybouncy.net/~justin/code/ (linque quebrado) -- Eu também escrevi um compressor "cloop" distribuído (ou para "smp"). Ele não está no mesmo diretório. {?}onde está, então?{?}

====Testando a imagem de CD sem queimar um CD====
Se você tem uma partição livre com pelo menos 700 MB de espaço formatado com ext2, ext3 ou vfat, você pode usar isto para testar, inicializando a partir de um disquete. Um disquete de "boot" procurará por uma partição com o diretório "/KNOPPIX" na raiz, e a imagem compactada "/KNOPPIX/KNOPPIX". Em vez de usar o subdiretório "/mnt/hda1/knx/master/KNOPPIX/" como descrito acima, ele deveria ser chamado "/mnt/hda2/KNOPPIX". O arquivo "index.html" da raiz será então localizado em "/mnt/hda2/index.html" e a imagem compactada estará em "/mnt/hda2/KNOPPIX/KNOPPIX". Agora, você pode inicializar a partir do disquete e usar "/mnt/hda2" como sua imagem. Para mais informações veja [[Hd BasedHowTo]].

Se você não tem uma partição extra e não quer (ou pode) criar uma, você pode utilizar o Qemu (veja http://fabrice.bellard.free.fr/qemu/ ou a distribuição brasileira chamada Kurumin) para inicializar a imagem ISO assim:
qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -net user
Você nem mesmo terá que construir uma imagem de disco rígido antes, apenas instale o Qemu e tente isto. Incrível! {?}obscuro{?}

====Testando a versão remasterizada sem criar o arquivo "cloop" ou ISO====
Eu uso uma configuração similar ao servidor de terminal do knoppix para testar os arquivos remasterizados sem ter que recriar uma imagem "cloop" cada vez: os arquivos remasterizados ficam num sistema de arquivos do tipo "ext2" num dispositivo "loopfile" ("knoppix_loop") montado em modo "rw" (este é onde eu faço "chroot"). Quando eu quero testar a configuração corrente, eu tenho outra máquina com "boot" de rede e uso os arquivos do "loopfile" diretamente (é necessário outro "miniroot.gz"). Veja [[User:Ml#dev_setup]]

Se você quer usar somente uma máquina, você precisará reinicializar (ou usar o "qemu") e usar os macetes "loopfile" e "fromhd" (veja [[User:Ml#miniroot_changes]]). Por exemplo, isto é o que minha entrada de boot no GRUB parece:

title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz

====Inicializando imagens Knoppix com GRUB====
* Primeiramente, copie "/boot" do CD do Knoppix para sua partição de "boot" (ou mesmo sua partição DOS). Eu nomeei a minha com "boot.knoppix".
Copie o diretório master/Knoppix para o seu diretório-raiz de qualquer disco rígido. Você pode colocá-lo em algum lugar que não seja a partição de "boot" (ext2, ext3, reiserfs, vfat são suportados).
* Para Knoppix <= 3.3, ponha o seguinte no seu "/boot/grub/menu.lst":
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* Para Knoppix >= 3.4 ou outras distribuições do tipo "isolinux":
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* Note o parâmetro "fromhd": é o local do diretório "/KNOPPIX".
* Reinicialize e divirta-se.

====Scripts úteis====
----
Este é o layout recomendado para o diretório de remasterização do KNOPPIX:

. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----

O script de remasterização a seguir fará o processo de remasterização para você. Utilize-o como "root", senão você obterá erros de acesso à imagem, devido às permissões.

O script foi testado pela última vez com Debian "sid" em 02/04/2004.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----

O script a seguir fará uma montagem de disquete de "boot" no modo "loop" e da imagem "initrd" para modificação. A função "umount" formará uma nova imagem "initrd" e a recolocará na imagem do disquete de "boot".

O script foi testado pela última vez no Debian "sid" em 13/01/2004.


#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if <nowiki>[[</nowiki> "`id -u`" -ne 0 <nowiki>]]</nowiki>; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if <nowiki>[[</nowiki> "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" <nowiki>]]</nowiki>; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! <nowiki>[[</nowiki> -e "$BOOTIMGFILE" <nowiki>]]</nowiki>; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if <nowiki>[[</nowiki> -e "$nofile" <nowiki>]]</nowiki>; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

====Dicas sobre "apt-get" para instalar/atualizar/remover aplicações====
(por 'gnarvaja')
* Se você inicializou a partir de CD, ou mesmo de uma instalação em HD (exemplo: instalação Pivot), em vez de copiar o CD e o diretório KNOPPIX originais para o HD, você pode usá-los diretamente a partir do ponto de montagem deles.{?}obscuro{?}
* Outra alternativa é montar uma imagem ISO do CD original como um dispositivo "loop" e montar a imagem do KNOPPIX como um dispositivo "cloop". Você poupará perto de 2 GB de espaço. O script para montar a partir de uma imagem ISO é:
#!/bin/bash
# Assume que o diretório corrente é o espaço de trabalho
# "original.iso" é uma imagem do CD que vamos utilizar como mestre:
mount -t iso9660 original.iso ./oldcd -o ro,loop
# inicialize o dispositivo de "loop" comprimindo
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop
* Instale o "apt-spy" e use-o para modificar o arquivo "sources.list" com os melhores servidores-espelho na sua região. Isso vai aumentar a velocidade de descarregamento. Faça cópia do arquivo "sources.list" original para o caso de algo dar errado.
* Outra técnica consiste em modificar o arquivo "sources.list". Substitua o termo ".de." nos endereços de "ftp" (por exemplo: "ftp.de.debian.org") com o código correspondente ao seu país. Por exemplo: EUA: "ftp.us.debian.org", Brasil: "ftp.b.debian.org". Verifique no saite da Debian os servidores-espelho existentes no seu país.
* Lembre-se de descomentar (retirar o "#") os endereços com "linuxtag" para obter o mais recente e maior {?} do Knoppix.
* Utilize "apt-get update" para obter as listas com as últimas versões e correções. Não atualize um pacote se você não precisa dele, pois isso pode levar a ocupar mais espaço em disco (tendo sempre em mente que tudo deve ficar abaixo de 700 MB em CD) e você pode, sem saber, "prejudicar" algo que esteja funcionando plenamente. Abuse da opção "-s" para simular a instalação (e verificar as "desinstalações" sugeridas, principalmente).
* Antes de fazer a atualização, eu modifiquei minhas versões padrão para "testing", o que significa que o software que eu estarei utilizando terá um bom balanço entre estabilidade e características. Knoppix utiliza "unstable" por default, o que é muito arriscado no meu modo pessoal de ver.
* Obtenha "apt-get install locale" e configure-o com os "locales" que você vai utilizar. Isso vai poupar bastante espaço quando baixar aplicações com muitos módulos de "locales" e páginas de documentação localizadas.
* Eu utilizo "aptitude" para obter/remover aplicações. Ele opera em modo caractere, de forma que funciona com "runlevel" 2. Quando você marca os pacotes para instalar/atualizar/remover, ele informa quando de espaço em disco você poupará/usará, tenta resolver problemas com dependências de pacotes e dá a você total controle para corrigi-los manualmente quando possível.
* Quando instalar aplicações, é provável que os diretórios "/etc/rc?.d" ganhem novas entradas, muitas delas indesejadas ou não-requisitas. Certifique-se de verificar e remover as novas entradas baseando-se nas suas preferências. Eu geralmente deixo "/etc/rc2.d" e "/etc/rc5.d" tão próximo quanto possível ao original e modifico "/etc/rc3.d" e "/etc/rc4.d" para testar as novas coisas. Por exemplo: Você pode querer ter "ntfs" instalado, mas não necessariamente executando por padrão. O mesmo em relação ao "apache", "mysql" e muitos outros serviços.
* Quando removendo/expurgando aplicações, eles podem deixar diretórios não-vazios para trás. Geralmente isto é revelado pelo "aptitude", "apt-get" ou qualquer outro utilitário de instalação. Certifique-se de verificar as mensagens e manualmente remover aqueles diretórios.
* Depois de terminar, "aptitude" pode deixar alguns arquivos temporários para trás. Aqui está um script para fazer a limpeza:
# !/bin/bash
# Limpa os arquivos de pacotes gerados pelo "aptitude"
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

===Problemas Comuns===
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] -- trata de problemas de "chroot" no acesso a arquivos de dispositivos.

* Você fez <tt>startx</tt> para chamar algum ambiente de janelas que você tenha e iniciou um terminal ("gnome-terminal", "konsole", "xterm", etc.), mas nada aconteceu ou talvez um erro seja exibido como:
get_pty: not enough ptys
: Consegui resolver isso assim:
<pre><nowiki>
# FORA do ambiente "chroot"
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# DENTRO do ambiente "chroot"
chroot /mnt/hda1/knx/source/KNOPPIX/

# e montando "/dev/pts"
mount -t devpts /dev/pts/ /dev/pts
</nowiki></pre>
: Pode ser que dê o erro "fstab not found" que dá na montagem de "proc", então você ignora, apenas.
* Inicie o X novamente e tente entrar no terminal, pois deve funcionar.
* Obrigado a: 'technovelty' em http://www.technovelty.org/linux/tips/xinchroot.html pela iluminação.

===Veja Também===

Se este tutorial é muito confuso, ou você quer uma segunda opinião, examine este tutorial de remasterização do 'charan': http://brainstorms.in/?page_id=84 Outro tutorial está em http://www.stirnimann.com/mystuff/doc/knoppix.txt.

Há um assistente que sabe tudo sobre os passos de descompactação, compressão e gravação em CD mencionados aqui. Ele também mostra um "shell" onde você pode atualizar o sistema KNOPPIX descompactado usando ferramentas de instalação de software padrão do Debian. É chamado de "mmkcdrom" e é parte do pacote "plugscript": http://rcswww.urz.tu-dresden.de/~holzhey/plugscript.

Há ainda outro tutorial em http://quozl.linux.org.au/knoppix/.

Certifique-se de checar o [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] para idéias e ajudas com remasterização.

* Se você quer adicionar um kernel personalizado na remasterização, examine o [[Knoppix Custom Kernel Howto]].
* Há também uma guia na O'Reilly sobre o mesmo tópico: [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

===Conclusão===
É isso. Esta é uma versão atualizada do meu tutorial anterior. Não foi feito para iniciantes, pois é preciso conhecer as "entranhas" do Linux para fazer isto funcionar. Eu atualizarei este tutorial na medida que novas correções/melhoramentos aparecerem.

===Agradecimentos===
Tenho que agradecer a estes: 'aay', 'charan', 'Tech2k' e '#knoppix' por algumas correções, dicas e idéias. Sinta-se à vontade para editar or aumentar este tutorial.
Nota sobre o "swap":

===Traduções===
* Versão em inglês: [[Knoppix Remastering Howto]]
* Versão em alemão: [[Knoppix Remastering Howto Deutsch]]
* Versão em espanhol: [[Knoppix Remastering Howto Spanish]]
* Versão em francês: [[Knoppix Remastering Howto French]]
* Versão em indonésio: [[Knoppix Remastering Howto Indonesian]]
* Versão em russo: [[Knoppix Remastering Howto Russian]]

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto Italiano

2008-05-21T03:42:51Z

202.88.238.45: /* Altre Indicazioni */

Questa è una guida che illustra come eseguire il remaster della KNOPPIX. (Note: I comandi appaiono in una riga, massimalizate il Vs. Browser per una corretta lettura. Se avete commenti/suggerimenti usate il post qui sotto.)

Potete intanto cominciare da una versione di Knoppix già su misura, in modo che non dobbiate fare tanto lavoro (vedendo quali programmi rimuovere). In caso affermativo, vedete [[Knoppix Customizations]].

=Sistema Richiesto=
*CD-ISO
** Almeno 1 GB di RAM+Swap liberi (esempio: 256M RAM, and 750M SWAP Disponibili) (unless you use a different compression program - look in this page for compressloop)
** 3 GB di filesystem '''Linux filesystem (ext2/3, xfs, etc.)''' liberi in una partizione formattata
*DVD-ISO
** 5 GB RAM + swap libera (per un DVD a dimensione completa)
** 15 GB di filesystem '''Linux filesystem (ext2/3, xfs, etc.)''' liberi in una partizione formattata

=Istruzioni=
==Settaggio per il Remastering==
# Boot di una qualunque ''Knoppix CD''
# aprite un terminale e andate in root o aprite un terminale in root shell:
#* Menu: Kmenu->Knoppix->Root Shell
#* Note: tutti i comandi sotto vanno eseguiti in root shell.
# Configurate la vostra connessione Internet (ne avremo bisogno sucessivamente). se usate il DHCP, dovete avere una rete che vi da tale supporto ( router, DHCP server,ecc....).
#* Note: Eseguite il comando '''ifconfig''' per una verifica.
# Trovate la partizione che volete usare per lavorare. In questo esempio si usa un disco '''hda1''' . La partizione deve avere un minimo di 3 GB di spazio libero
# Mountare la partizione con il comando:
#*<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Note: accertatevi che sia in read/write oppure incorrete in errore quando dopo usate la chroot. Per Verificare: eseguite '''mount'''
# Create una root directory per lavorare -- Se voi mettere qui i vostri file poi potete cancellarli facilmente
#* <pre>mkdir /mnt/hda1/knx</pre>
# Se il Vs.PC non ha almeno 1 GB RAM ( '''egrep "(MemTotal|SwapTotal)" /proc/meminfo && echo "(physical+swap)"''' ) Allora avete bisogno di una SWAP creata su un swapfile:
<code>cd /mnt/hda1/knx
dd if=/dev/zero of=swapfile bs=1M count=750
mkswap swapfile
swapon swapfile</code>
# Costruite 2 directori, uno per il vostro nuovo Master CD, uno per sourgente, nella vostra partizione. Create le directori come sotto con il nome KNOPPIX:
#* <pre>mkdir -p /mnt/hda1/knx/master/KNOPPIX</pre>
#* <pre>mkdir -p /mnt/hda1/knx/source/KNOPPIX</pre>
# Ora, copiate i KNOPPIX del vostro live CD nella directori sorgente :
#* <pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Note: Questo richiede un lungo tempo (state copiando circa 2GByte). ATTENZIONE: sarete tentati di sostituire questo ordine di copia con una procedura molto più veloce: il risultato genera un indice vuoto. Tuttavia, a partire da Knoppix 4.0.2, vi è un bug nei unionfs che rende questa procedura più veloce si ma con perdita di dat. Per ora, copiate il comando ed usatelo cosi come si trova.
# In Aggiunta, copiare la cartella di 'boot' dal vostro cdrom - abbiamo bisogno di queste informazioni per creare la ISO image del CDROM verso la fine.
#* <pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
# Per la Knoppix 5.0.1 dovete avere la copia della cartella che contiene i 'modules':
#* <pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copia le main page HTML dello startup:
#* <pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copiare tutto il resto dei file circa ~700 Mb di KNOPPIX file.
#* < 3.4:
#** <pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* >= 3.4:
#** <pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* Per la versione in DVD usete -size -15000k e copiate la cartella KNOPPIX2 come sotto qui:
#** <pre>cp /KNOPPIX2 /mnt/hda1/knx/source/KNOPPIX</pre>
# Preparate gli environment di ambiente per attivare il chroot
#* <pre>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev</pre>
#* <pre>mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</pre>
# Ora potete entare in "chroot" nella copia di KNOPPIX:
#* <pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# Se vedete errori dei <tt>/dev/null</tt>, datte uno sguardo alla guida [[#Common Problems|common problems]] nella apposita sezione
Ora siete in chroot . "/" che si trova in "/mnt/hda1/knx/source/KNOPPIX"

==Lavorare in Chroot Environment==
Ricordate che qualunque cosa voi facciate o modficate in chroot viene concretizzato nel CD. Se fate cambiamenti fatevi una nota che vi aiuta a capire quale variazioni avete apportato ( configurazione, desktop, file di sistema, script, eccc...) prima della masterizzazione.
===Accesso a Internet===
Per usare internet avete bisogno di editare <tt>/etc/resolv.conf</tt> per aggiungere il nome del Server Dns del Vs. Provider o della Vs. rete oppure uscite dal chroot e copiate il <tt>resolv.conf</tt> nella cartella di chroot:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf
(proxy (nel caso ne abbiate uno sulla Vs.Rete): digitate "export http_proxy=http://your.proxy.com:<port>") 
Per controllare la vostra connessione internet in chroot,
ping google.com
(se l'ICMP e filtrato dal vostro firewall potete fare una verifica del funzionamento di internet con "lynx http://www.google.com" e verificate se riceve la pagina dopo avere risposto "allow" alla richiesta di accettare i cookie)

===Accesso SMB (Samba o Domini Windows)===
Cambiate smb.conf con il vostro gruppo MS se avete bisogno del supporto smbd (MSHOME, DOMAIN e XP Home sono usaualmente con WORKGROUP per Windows 9x i nomi di gruppo usati, consultate il Vs. control pannel di una stazione Windows con l'icona "Sistema").

===Accesso APT ( repositor di aggiornamento e upload pacchetti)===
Aggiornate la lista pacchetti con '''apt-get update'''.
<blockquote>Nota: Se ''''apt-get update''' termina con il messaggio "FATAL -> Could not set non-blocking flag Bad file descriptor", È necessario assicurarsi che il proprio chroot è montato senza le option "nodev". (Vedi sopra, dove si parla di errori /dev/null quando avete inserito il chroot, per la prima volta)</blockquote>
<blockquote>'''Warning''': apt-get upgrade e una ''CATTIVA IDEA''. Esso conclude , con una buona probabilita', rendendo la vostra KNOPPIX remaster non bootabe, o da buttare. Una buona cosa e' aggiornare solo i pacchetti necessari alla vostra distribuzione Live.</blockquote>

'''Nota: Se apt-get termina con il messaggio "Dynamic NMap ran out of room" ''' Potresti provare questo piccolo gioiello, che fissa il problema per me:
#echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf
(Va fatto questo, mentre siete in chroot, come descritto in precedenza.)

Prima di poter aggiungere roba, si avrà probabilmente bisogno di rimuovere alcuni pacchetti. Per ottenere una lista dei pacchetti installati, digitate questo comando:
dpkg-query -l
Se siete alla ricerca di grossi pacchetti installati allora il comando:
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
ottenete una lista dei pacchetti in ordine discendente.

Almeno dieci volte più veloce è il comando:
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
e non avete bisogno dei pacchetti dpkg-awk or awk or perl; Tuttavia non esclude che i pacchetti non sono installati. Se hai problemi con il comando di ordinamento, provare a utilizzare KPackage, ampliati tutti gli alberi e ordinati in base alla colonna dimensione cercate i grandi pacchetti.

Oppure, si potrebbe usare questo comando per ottenere velocemente da qpkg-query la lista dei pachetti non installati:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
Si fa la stessa cosa, come sopra. Solo che non ho potuto ottenere i risultati perché non ho dpkg-awk.

Per rimuovere i pachetti (e tutte le dipendenze incrociate), digitate:
apt-get remove --purge ''name-of-package-to-remove''
Per verificare i pacchetti orfani, digitate:
deborphan
Vuoi risparmiare più spazio e per sbarazzarsi di questi strani orfani (come crudele!), il messaggio ('''Warning''', non ti chiederà sì / no per rimuovere questi pacchetti. Quando si preme Invio dopo questo comando , Questi pacchetti saranno processati''''):
deborphan | xargs apt-get -y remove
Se siete incerti circa il comando precedente e volete vedere cosa accadrà senza apportare eventuali modifiche, è sufficiente aggiungere il'''-s''' opzione per il comando apt-get (potete farlo con tutti i comandi Apt-get, si tratta di una buona abitudine fare uso di questa opzione prima di operazioni di massa come queste):
deborphan | xargs apt-get -s -y remove
Ora il comando giusto. Se si desidera aggiungere un pacchetto, digitate questo:
apt-get install '''name-of-package-to-install''

Quando non si sa quali sono i pacchetti da installare? Digitate questo comando: Quando viene visualizzato l'elenco, è possibile esaminalo (sono >13k! linee) o usare la ricerca rapida usando <tt>/''search-term''</tt>:
apt-cache search .* | sort | less
Quando hai finito di aggiungere e rimuovere i pacchetti, un buon modo per ripulire è digitando questo comando:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Inoltre, poiché il sistema dei pacchetti Debian mantiene una cache dei pacchetti scaricati, è possibile che si desideri eseguire il seguente comando per eliminare quei file appoggio:
apt-get clean

===Settaggio degli utenti===

Impostazioni utente le trovate in /etc/skel. Questa directory viene copiata quando create nuove home directory degli utenti.
<blockquote> Consiglio: non mettete i file in /root saranno disponibili solo (in fase di runtime), in
/KNOPPIX/root</blockquote>

Nota: L'utente di default 'knoppix' non è creata con adduser (1), quindi /etc/skel non viene copiato completamente, ma piuttosto in modeo selettivo. Se dovete mettere un file .xyrc in /home/knoppix, non è sufficiente a metterelo in /etc/skel. Una possibilità è quella di modifcare il codice di /etc/X11/Xsession.d/45xsession che è responsabile per la costruzione del contenuto di /home/knoppix.

===AutoEsecuzione programmi===
Quando si desidera il lancio automatico di alcuni programmi, si può creare uno script e metterlo nella directory <tt>/etc/rc5.d/</tt> (Questo per i soli programmi caricabili prima del server X). Leggete i processi di SysV init per altre possibilità operative.

''Per i programmi X considerate <tt>/home/knoppix/.kde/Autostart</tt> ma questo può trasferire il controllo a <tt>/etc/skel/.kde/Autostart</tt> on boot''--[[User:12.106.237.2|12.106.237.2]] 18:08, 7 December 2007 (UTC)

==Edit del KNOPPIX auto-configuration script==

Potete trovare un sacco di informazioni interessanti su come KNOPPIX si autoconfigura il Vs. sistema guardando in /etc/init.d/knoppix-autoconfig script. Una serie particolare di note la trovate qui sotto.

===Cambire la default KDE background image===
L'auto-script di configurazione di default imposta l'immagine di sfondo di KDE per essere un'immagine caricata da CD-ROM. Un'immagine che è possibile modificare facilmente quando si rimasterizzazione KNOPPIX.

** In KNOPPIX 3.3 e precedenti la trovate /cdrom/KNOPPIX/background.gif
** In KNOPPIX 3.4 e successive la trovate /cdrom/KNOPPIX/background.jpg

===Editare i file di autoconfigurazione di floppy e CD-ROM===
La configurazione automatica di script imposta sia il CD-ROM sia il vostro disco floppy. I comandi per fare questo sono, rispettivamente 'floppyconfig' e 'cdromconfig'. La configurazione automatica con lo script anche cdrom/KNOPPIX/knoppix.sh, che è un semplice script per cambiare quando rimasterizzate KNOPPIX.

===Cambiare i parametri del boot alla partenza===
Tutti i parametri di boot ottngono i valori di default in /etc/init.d/knoppix-autoconfig script. Si tratta di uno script di BASH massiccio (è meglio conoscere bene BASH per giocare con questo file), ma è il luogo dove è possibile modificare uno qualsiasi dei parametri di boot di default. Per esempio, per passare da 'kde' a 'twm' come desktop di default cercate dove 'kde' è definito come valore di default (variabile DESKTOP, IIRC). Un altro esempio sarebbe quello di cambiare la lingua di default che può essere cambiato.

Notate che, se siete interessati a cambiare la lingua di default usata da KDE, la cosa più semplice da fare è caricare ilKDE, le istruzioni si trovano al di sotto, e utilizzare l'utility di configurazione di KDE per selezionare la lingua di vostro interesse.

==Configurazione delle sessioni X==
Quando si lavora con programmi basati su X, si dovrà fare in modo che lo schermo è impostato adeguatamente. Puoi farlo manualmente quando rimasterizzazione KNOPPIX. Inoltre,ci sono due script correlati a X Session è dove è possibile modificare o disattivare il suono di avvio e di arresto.

===Start dei programmi della interfaccia X===
Quando testate i programmi basati su X voi dovete avere attivato le variabili di ambiente
export DISPLAY=localhost:0.0
Questo consente di connettere le vostre applicazioni alle sessioni del server X. In alternativa (se avete lda testare il windows manager),Potete creare un successiva sessione X. Fuori da chroot, eseguite
Xnest -ac :1
All'interno di chroot, Settate così le variabili di ambiente
export DISPLAY=localhost:1

Indicazioni interessati le trovate in /etc/init.d/xsession :
* Potete personalizzare il background modificando /usr/local/lib/knoppix.gif

===Modifica/Disattivazione del sound alla partenza===
Il suono alla attivazione di X è eseguito mediante le indicazioni presenti in /etc/X11/Xsession.d/45xsession. Potete disattivare il suono commentando le linee seguenti nello script.
<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

===Modifica/disabilita il suono in shutdown===
Il suono allo shutdown ( spegnimento) è eseguito mediante le indicazioni presenti in /etc/init.d/xsession. Potete disattivare il suono commentando le linee 210-220 nello script.
<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

===Cambiare il windows manager di default===

Aprire /etc/init.d/knoppix-autoconfig e guardare o trovate la linea qui sotto:
<pre><nowiki>
# Allow only supported windowmanagers
# Actually, this check is useless because it's done again in 45xsession. -KK
# case "$DESKTOP" in gnome|enlightenment|kde|larswm|xfce|xfce4|lg3d|ratpoison|blackbox|openbox|windowmaker|wmaker|icewm|fluxbox|twm|nx|rdp|kiosk) ;; *) DESKTOP="kde"; ;; esac
[ -n "$DESKTOP" ] || DESKTOP="kde"
</nowiki></pre>

Cambiate "kde" tra gli apici della vostra interfaccia preferita, per esempio ( gdm, fluxbox, twm, ecc...).

==Cambiare la grafica al boot, il messaggio di boot, e gli script di start==
Quando siete in ambiente chroot potete cambiare facilmente il boot message, la grafica al boot e lo sfondo della grafica KDE.

===Cambiare la grafica del boot===
La Grafica di boot e' la prima immagine quando il CD/DVD partono. It looks similar to ASCII art and it is normally something flashy that says 'Knoppix'. You can change this to be any graphic that you please, but you must use a 640x400 graphic that has only 16 colors.

#Cambiate posizione di lavoro andando a /mnt/hda1/knx/master/boot. Scambiate '/mnt/hda1/' con il disco che si sta utilizzando.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Fate una copia del vecchio logo nel caso abbiate problemi.
#* <pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
#Costruite una immagine 640x400 16 colori e salvatela in formato GIF, es: 'logo.16.gif'. GIMP è favoloso per questo processo. Nota: Si può utilizzare una immagine grafica che originariamente ha più di 16 colori, ma è fondamentale che la conversione grafica a 16 colori avvenga prima di fare il passo successivo.
#Convertite le gif in lss16 usando i tools inclusi nella Knoppix CD.
#* <pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm
ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

===Cambiare il messaggio di boot===
The 'boot message' is the message that you see under the 'boot graphic' on the initial screen when the Knoppix CD or DVD loads. It normally says something along the lines of Knoppix with the version number and includes a link to the Knoppix website. You can change this text to be whatever you please, but you shouldn't add too much text or it will make the boot screen look funny. Restricting yourself to a singly line of text that is no larger than the default one is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot</nowiki></pre>
#Back up your old message in case you break things.
#* <pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
#Edit the message with a text editor. You'll see at the top of the message that it shows the graphic. Don't change this text, just the line under.
#* <pre><nowiki>vi boot.msg</nowiki></pre>

===Cambiare lo script di startup ===
The 'startup script text' is the text that you see after the initial boot screen, while Knoppix loads and configures your system. You can change as much of this text as you please. You can even add addition lines to the script; however, it is recommended that you don't play with this file. Limiting yourself to editing the 'Welcome to KNOPPIX' message is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old minirt.gz in case you break things.
#* <pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
#Uncompress minirt.gz
#* <pre><nowiki>gunzip minirt.gz</nowiki></pre>
#Make a temporary directory to mount the minirt filesystem.
#* <pre><nowiki>mkdir todelete</nowiki></pre>
#Mount the minirt filesystem as an ext2 filesystem.
#* <pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
#::or if the above does not work use
#* <pre><nowiki>mount minirt todelete -t ext2 -o loop</nowiki></pre>
#Edit the linuxrc script to display the message you want. You'll find the default message approximately 2 pages down and it'll be using several colors, i.e. ${WHITE}, ${RED}, etc., so it might be slightly tricky to spot.
#* <pre><nowiki>vi todelete/linuxrc</nowiki></pre>
#unmount the minirt filesystem.
#* <pre><nowiki>umount todelete</nowiki></pre>
#Compress the minirt filesystem.
#* <pre><nowiki>gzip -9 minirt</nowiki></pre>
#Remove your temporary directory.
#* <pre><nowiki>rmdir todelete</nowiki></pre>

==Lanciare KDE per cambiare Menu,Icone,ecc...==
While you are in the chroot environment you can load KDE and use the configuration tools to change buttons, icons, etc. Once you are finished you can exit KDE and copy /home/knoppix to /etc/skel to keep these changes. To load KDE do the following.

#If you are not at runlevel 2 (i.e. if you are already in KDE), switch to runlevel 2.
#* <pre><nowiki>init 2</nowiki></pre>
#Copy /etc/skel to /home/knoppix
#* <pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
#Change permissions to the user 'knoppix'
#* <pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
#Copy over your X11 configuration to the chroot'd environment (press ctrl+alt+F2 to switch to a non-chroot'd terminal, then ctrl+alt+F1 to switch back when done)
#* <pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#*<blockquote>'' Knoppix 3.7: I think it's XF86Config-4 rather than xorg.conf.''</blockquote>
#(Optional)Switch to user 'knoppix'. If you want to uninstall packages, stay as root -- e.g. skip this step. If you want to configure the buttons, icons, background, etc., that you see when KDE boots, be sure to do this step.
#* <pre><nowiki>su knoppix</nowiki></pre>
##Launch KDE
##* <pre><nowiki>startx</nowiki></pre>
##Do your KDE changes
##Exit KDE
##Exit su and switch back to user 'root'.
##* <pre><nowiki>exit</nowiki></pre>
#Copy /home/knoppix back to /etc/skel to keep the changes
#* <pre><nowiki>mv /etc/skel /etc/skel-old
mv /home/knoppix /etc/skel</nowiki></pre>
#Set the owner back to root
#* <pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
#Remove the xorg.conf file
#* <pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>
#If you find that some of your settings are not persistent after booting the new image, check the initialization file at /etc/X11/Xsession.d/45xsession. By default, Knoppix does '''not''' simply copy over all files from /etc/skel. You may need to make modifications here if you wish to do something different.

===Cambiare la grafica del ksplash di KDE ===
Puoi cambiare la grafica di KDE che mostra attraverso ksplash quando carichi il KDE. Queste immagini sono in
/mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/. E' probabile che volgiate cambiare
splash_top.png con la Vs. grafica personalizzata in un PNG 400x248. Nota che il ksplash automaticamente non genera il bordo attorno alla Vs. immagine. Se desideri un bordo lo dovete aggiungere manualmente al vostro grafico.

==Lasciare l'ambiente Chroot==
Se voi montate chroot, dovete smontare /proc - Molto IMPORTANTE!!!!!

umount /proc
Premere '''CTRL+D''' per rilasciare chroot.

==Rientrare in modo chroot==

Se hai lasciato il chroot, ma si desidera tornare indietro e modificare alcune cose...

rimontare il Vs. hard disk locale (se necessario)
<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
Settaggio delle variabili di ambiente per chroot
<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</nowiki></pre>
Ora potete entrare in "chroot" nella copia di KNOPPIX:
<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>

==Rimasterizzare la ISO==
Quando siete pronti per bruciare il vostro CD:
Iniziate con un po di pulizia:
* rimovere i .bash_history file, tmp file, etc.
* Riordinare i cambiamenti che non si desidera trovare quando si masterizza il CD
* <pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

===KNOPPIX Immagine Compressa===
Ora creiamo l'immagine del file <tt>KNOPPIX</tt> che è un file system compresso ISO 9660 per l'uso da parte del <tt>cloop</tt> driver:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
"www.knoppix.net" e "Knoppix.net filesystem" possono essere cambiati con quello che volete. Verrà visualizzato un messaggio di errore che non è conforme alle norme ISO - potete ignorare questo messaggio. Si noti che, per eseguire <tt>create_compressed_fs</tt>, devi avere spazio sufficiente per memorizzare tutto l'ISO e RAM/swap. Assicurare di avere almeno 800M di spazio libero prima di cominciare.

Knoppix 3,4 e il <tt>create_compressed_fs</tt> script è stato aggiornato in modo da assicurarsi di utilizzare per ottenere il miglior risultato. Ha una nuova opzione'' '-b''' (migliore), che consente la migliore compressione utilizzando differenti schemi di compressione e cerca di ottimizzare questo modo, ma fate attenzione, perché questa opzione è lenta (10x più lenta).

Nota: La suddetta non ha funzionato per me, con le ultime create_compressed_fs. Ho potuto creare la ISO, ma potrebbe non leggere correttamente l'immagine compressa quando si avvia (I/O errori durante la lettura del dispositivo cloop0). Penso che questo è stato perché create_compressed_fs non ha abbastanza RAM e anche se funzionava il comando non ha eseguito la compressione correttamente. Esso utilizza un file di memoria temporaneo per lo stoccaggio:

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/hda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

===Live CD ISO===
Bene quando avete finito, potete procedere a produrre l'immagine finale del CD-ROM:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(Questo aggiona il marker MD5 calcolando l'hash dei file includi nell'ISO, usato per verificare l'integrità) ora potete masterizzare; per Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
per Knoppix >= 3.4 o altre distribuzioni isolinux:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(la ISO è memorizzata in <tt>/mnt/hda1/knx/knoppix.iso</tt>)

Trasferite la vostra ISO usando il vostro tool preferito, è il CD e pronto per l'uso.

=Trucchi=
Ho avuto buoni risultati rimasterizzazione di lavoro dal CD di lavoro come root da Fluxbox. Basta dire "Knoppix 2" al prompt boot e si avvio a un prompt di root dove si può poi dire "startx /usr/bin/fluxbox". Mi piace utilizzare la shell di xterm unicode.

==Gestione dei pacchetti Software==
Prima di fare il lavoro di rimasterizzazione da chroot e meglio usare
apt-get remove --purge pkg-name
per rimuovere i pacchetti, perché prima di tutto non si blocchi la masterizzazione e vi mostra dettagli su ciò che è lo stato delle dipendenze segnalando "sì o no" per la rimozione del superfluo.

Se non si utilizza il sopra "apt-get" e la lunga sequenza di controllo pacchetti, ecco il modo più semplice per farlo:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
Che farà un elenco di tutti i pacchetti rimossi da spurgare
dpkg -P `< topurge `
se si purgano con:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
il comando che completa l'opera:
deborphan | xargs dpkg -P .

==Alternativa per macchine con poca Memoria==

Non si ha realmente bisogno 1G di swap in quanto vi sono due nuovi strumenti per creare i filesystem compresso. Ecco alcuni dei candidati a sostituire il sistema di fs ''compresso'':

* Valentijn's riscrive il compressore [http://projects.openoffice.nl/downloads/compressloop/]
* Quozl's porting di compressloop per Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Quozl's distribuisce compressloop (Utilizzate più di un processore per velocizzare le cose) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Justin's patch [http://s.bouncybouncy.net/~justin/code/] (link broken)che a distribuito il cloop (anche per smp) Che trovate in questa stessa directory.

==Test della immagine CD senza creare il supporto CD==
Se avete un partizione con almeno 700MB di spazio libero formattato con ext2, ext3 o Vfat, è possibile utilizzarla per questo test per il boot da un floppy disk. Un floppy di boot vengono cercate un partizione con /KNOPPIX/ nella root, e la compressa immagine /KNOPPIX/KNOPPIX. Invece di usare la sotto-directory /mnt/hda1/knx/master/KNOPPIX/ come descritto sopra, deve essere chiamato /mnt/hda2/KNOPPIX/. La root index.html si trova in /mnt/hda2/index.html e immagine compressa sarà in /mnt/hda2/KNOPPIX/KNOPPIX. Ora potete fare il boot da dischetto e usare /mnt/hda2 come immagine. Per ulteriori informazioni, vedere [[Hd BasedHowTo]].

Se non si dispone di una partizione o non si vuole usare il metodo precedente si può usare Qemu (vedi [http://fabrice.bellard.free.fr/qemu/]), con l'immagine ISO come questo comando:
Qemu-m 128 -cdrom /temp/Knoppix-custom.iso -boot d -net user
Come vedete la ISO deve essere pronta prima di lanciare il comando, provate Qemu è un emulatore che funziona bene per questo test.

==Test della versione rimasterizzata senza creare il cloop file/iso==
Ho usato una configurazione simile a Knoppix server terminal per testare il file remasterizzato senza dover ricreare una immagine
Cloop ogni volta: il file remasterizzato vivere in un filesystem ext2 in un loopfile (knoppix_loop) montato in rw (questo è in chroot). Quando volte testare la configurazione attuale, ho un altro computer di rete in boot remoto e utilizzo i file della loopfile directory (si ha bisogno di un altro miniroot.gz). Vedi [[Utente: Ml # dev_setup]]

Se si desidera utilizzare una sola macchina, dovrete riavviare (o utilizzare qemu) e usare il "loopfile" e "fromhd" cheatcodes (vedi [[Utente: Ml # miniroot_changes]]). Ad esempio, questo è ciò che ho usato nel mio avvio di grub:

<pre>
title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz
</pre>

== Boot della immagine Knoppix con GRUB==
* Prima copiate /boot fuori dal Knoppix cd nella vostra partizione di booto (o la vostra partizione dos). Io la ho chiamata boot.knoppix
copate la master/KNOPPIX directory nella vostra directori di root. È possibile collocarlo altrove rispetto alla partizione di boot (ext2/3, reiserfs, vfat sono supportete).
* Per Knoppix <= 3.3, ponete queste righe nel vostro: /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* per Knoppix >= 3.4 o altre distribuzioni basate su isolinux:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* Note: il parametro fromhd: è la locazione della directory /KNOPPIX
* reboot è buon divertimento.

==Script Utili al vostro remastering==
----
Questa e una struttura di directory raccomandata per il vostro remastering di KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
Il seguente script "remaster" farà il processo di rimasterizzare per voi. Utilizzatelo come root, o vi ritroverete con errori ai diritti di accesso e dell'immagine ISO.

The script has last been tried out on Debian sid on 2004-04-02.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
Il seguente script loop-mount floppy di boot di immagine e di immagine initrd per la modifica. La funzione umount costruire una nuova immagine initrd e reinserirla sul floppy di boot di immagine.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

==Spunti Intorno all'uso di apt-get per installare/update/rimozione applicazioni==
(by gnarvaja)
* If you booted from CD, even on a HD install (example: Pivot Install) instead of copying the original CD and KNOPPIX directory to the HD, you can use them directly from their mount points.
* Another alternative is to mount an ISO image of the original CD as a loop device and mount the KNOPPIX image as a '''cloop''' device. You will save close to 2GB of space. Script to mount from an ISO image:

#!/bin/bash
# Assumes that the current directory is the working space
# original.iso is an image of the CD we will be using as master
mount -t iso9660 original.iso ./oldcd -o ro,loop
# initialize the compressed loop device
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop

* Get '''apt-spy''' and use it to modify the sources.list file with the best mirrors for your particular region. This will speed up the downloading. Backup the original '''sources.list''' just in case.
* Another technique is to modify '''sources.list'''. Replace the string '''.de.''' in the ftp addresses (ftp.de.debian.org) with the code corresponding to your country. Examples: USA -> .us. (ftp.us.debian.org), Brazil -> .br. (ftp.br.debian.org). Check the Debian site for debian.org mirrors in your country.
* Remember to uncomment the '''linuxtag''' ftp addresses to get the latest and greatest from Knoppix
* Use '''apt-get update''' to get the lists with the latest releases and patches. Do not update a package if you don't need to, it may lead to the use of additional disk space (precious commodity when you want to keep everything below 700MB) and you may brake something else without knowing. Abuse the '''-s''' option to simulate the installation.
* Before doing the update, I modified my default releases to '''testing''', that means that the software I'll be using will have a good balance of stability and features. Knoppix uses '''unstable''' by default, which is too risky for my personal taste.
* Get '''[apt-get install] locale''' and configure it with the locales you are going to use. It will save lots of space when downloading applications with plenty of locale modules and localized manual pages.
* I use '''aptitude''' to get/remove applications, it is character based so it works with init 2. As you mark packages for install/update/removal, it will tell you how much disk space you will save/use, try to solve depencies problems and give you plenty control to fix them manually when possible.
* When installing applications it is likely that your '''/etc/rc?.d''' directories will have new entries, many of them unwanted or unplanned. Make sure you check them and remove the new entries based on your preferences. I usually leave '''/etc/rc2.d''' and '''/etc/rc5.d''' as close as the originals as possible and modify '''/etc/rc3.d''' and '''/etc/rc4.d''' to test new stuff. '''Example:''' You may want to have ntfs installed, but not necessarily running by default. Same with apache, mysql and many others.
* When removing/purging applications, they may leave behind non-empty directories. Usually this is announced by aptitude, apt-get or any other installation utilty. Make sure to check the messages and manually remove those directories.
* After you are done, '''aptitude''' may leave some files behind. Here's a clean up script I use:

# !/bin/bash
# Clean package files generated by aptitude
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

=Problemi Comuni riscontrati=
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] Chroot problems accessing device files

* You've <code>startx</code>'d (into whatever window manager you like) and you start a terminal (gnome-terminal, konsole, xterm). Nothing happens (such is the case in fluxbox, and you'll see an error in you <code>~/.xsession-errors</code> file). Or perhaps the error is helpfully displayed: <code>
get_pty: not enough ptys
</code>
I had plenty yesterday... but then I <code>chroot</code>ed so, to solve this, <code>
# NOT in your chroot environment
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# enter your chroot environment
chroot /mnt/hda1/knx/source/KNOPPIX/

# and mount /dev/pts
mount -t devpts /dev/pts/ /dev/pts

</code>
it might give that same "fstab not found" error as mounting proc
does. so do what you'd do then, disregard.

start your X up again and try your terminal, should work.
thanks to: technovelty[http://www.technovelty.org/linux/tips/xinchroot.html] for the final enlightenment

=Altre Indicazioni=

Se la mia guida è troppo confusa, o desideri un secondo parere, guardate questo altro Howto per rimasterizzazione: http://brainstorms.in/?page_id=84
Un altro Howto lo trovate qui http://www.stirnimann.com/mystuff/doc/knoppix.txt

There is a wizard, which knows all the unpacking, compressing and CD-recording steps mentioned here. It also shows a shell where you can update the uncompressed KNOPPIX system using debian's standard software installation tools. It is called mmkcdrom and part of the plugscript package: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Vedete questo HOWTO, per smanettoni delle shell, a http://quozl.linux.org.au/knoppix/

Potete dare uno sguardo a [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] per altre idee ad aiuto al vostro remastering.

* Se volete introdurre un kernel personalizzato, vedete questo link [[Knoppix Custom Kernel Howto]]
* Trovate alcune utili quide alla O'Reilly con molte varianti: [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

=Conclusioni=
Questa è una versione aggiornata del mio howto precedente. Un suggerimento ai principianti del linux; Dovete conoscere bene come utilizzate i comandi del linux e apprendere delle singole funzioni l'esito dei comandi. Evitate se non avete una buona esperienza di Linux potreste fare danni alla Vs. installazione. Continueremo ad aggiornare e dettagliare la procedura in funzione anche dei vostri suggerimenti.

=Ringraziamenti=
Traduzione a cura di [http://www.mcmax.info mcmax], e a [http://www.knoppix.org knoppix] per le correzioni i trucchi e le idee. Ritenetevi liberi di operare modifiche per aggiornamenti sulle procedure.

Note sullo swap: 

=Translations=
* German Version: [[Knoppix Remastering Howto Deutsch]]
* Spanish Version: [[Knoppix Remastering Howto Spanish]] en español
* French Version: [[Knoppix Remastering Howto French]]
* Indonesian Version: [[Knoppix Remastering Howto Indonesian]]
* Russian Version: [[Knoppix Remastering Howto Russian]]
* Brazilian Portuguese Version: [[Knoppix Remastering Howto Brazilian Portuguese]]

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto

2008-05-19T12:06:34Z

202.88.238.45: /* See also */

This is a guide that will show you how to remaster KNOPPIX. (Note: commands should appear on one line, so please maximize the window. If you have any comments/suggestions please post below.)

You may wish to start from an already customized Knoppix, so you don't have to do as much work (such as removing programs). If so, see [[Knoppix Customizations]].

=System Requirements=
*CD-ISO
** at least 1 GB of FREE RAM+Swap total (e.g. 256M ram, and 750M swap AVAILABLE) (unless you use a different compression program - look in this page for compressloop)
** 3 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition
*DVD-ISO
** 5 GB free RAM + swap (for fullsized DVD)
** 15 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition

=Instructions=
==Setting up for Remastering==
# Boot from the ''Knoppix CD''
# Open a root shell:
#* Menu: Kmenu->Knoppix->Root Shell
#* Note: All commands below are run from this root shell.
# Configure your Internet connection (we'll need this later). If you use DHCP, it should already be configured.
#* Note: Run '''ifconfig''' to check.
# Find the partition you will use to work on. In this example it is called '''hda1''' . The partition should have a minimum of 3 GB free space
# Mount the partition:
#*<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Note: Make sure that it is read/write or you will get errors when you later chroot. To check: run '''mount'''
# Create a root directory to work in -- if you put all your files here it will be easy to clean up
#* <pre>mkdir /mnt/hda1/knx</pre>
# If you don't have 1 GB RAM ( '''egrep "(MemTotal|SwapTotal)" /proc/meminfo && echo "(physical+swap)"''' ) then you will need a swapfile:
#* <pre>cd /mnt/hda1/knx</pre>
#* <pre>dd if=/dev/zero of=swapfile bs=1M count=750</pre>
#* <pre>mkswap swapfile</pre>
#* <pre>swapon swapfile</pre>
# Make 2 directories, one for your new Master CD, one for the source, on a disk partition. Also, make additional directories under these named KNOPPIX:
#* <pre>mkdir -p /mnt/hda1/knx/master/KNOPPIX</pre>
#* <pre>mkdir -p /mnt/hda1/knx/source/KNOPPIX</pre>
# Now, copy the KNOPPIX files to your source directory :
#* <pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Note: This will take a long time (you are copying 2GB). Warning: you will be tempted to replace this copy command with a much faster procedure: create an empty directory, then use unionfs to merge the empty directory with /KNOPPIX in order to create the read-write copy. However, as of Knoppix 4.0.2, there is a bug in unionfs that causes this faster procedure to fail. For now, stick with the copy-command shown above.
# Additionally, copy the 'boot' folder from your cdrom - you'll need these files to build the ISO later.
#* <pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
# For Knoppix 5.0.1 you also have to copy the 'modules' folder:
#* <pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copy the main HTML page for the startup page:
#* <pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copy everything necessary files except the ~700 Mb KNOPPIX file.
#* < 3.4:
#** <pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* >= 3.4:
#** <pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* for the DVD Version you have to use -size -15000k and copy the KNOPPIX2 folder like this
#** <pre>cp -ar /KNOPPIX2/* /mnt/hda1/knx/source/KNOPPIX</pre>
# setup the environment for chroot
#* <pre>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev</pre>
#* <pre>mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</pre>
#* <pre>mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</pre>
# Now you can "chroot" into the copied KNOPPIX:
#* <pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# If you see errors regarding <tt>/dev/null</tt>, see the [[#Common Problems|common problems]] section
You are now chrooted. "/" is actually "/mnt/hda1/knx/source/KNOPPIX"

==Working in the Chroot Environment==
Remember that anything you do or create in the chrooted environment will get burned to the CD. If you make any changes (e.g,. to the APT configuration, proxy settings, etc.), make a note to back the changes out before remastering.
===Internet Access===
To use the Internet you need to edit <tt>/etc/resolv.conf</tt> to add your nameserver or exit the chroot and copy the outer <tt>resolv.conf</tt> into the chroot folder:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf
(proxies (a.k.a. doing it at work): you can type "export http_proxy=http://your.proxy.com:<port>") 
To check your chrooted internet connection,
ping google.com
(if ICMP is barred at some corporate firewall or something then try "lynx http://www.google.com" and see if you get the page -after a cookie "allow")

===SMB access===
Also change smb.conf to your MS group if you want smbd support (MSHOME is XP Home ed. usually, and WORKGROUP is 9x Windows)
===APT===
Update your package list with '''apt-get update'''.
<blockquote>Note: If ''''apt-get update''' fails with "FATAL -> Could not set non-blocking flag Bad file descriptor", you need to make sure your chrooted environment is mounted without the "nodev" option. (see above where it talks about the /dev/null errors when entering the chroot environment for the first time)</blockquote>
<blockquote>'''Warning''': apt-get upgrade is a ''BAD IDEA''. It will, quite probably, render your KNOPPIX remaster unbootable, or broken in some way. A far safer method is to only upgrade packages as necessary.</blockquote>

'''Note: If apt-get fails with "Dynamic NMap ran out of room" ''' you might try this little gem, which fixed the problem for me:
#echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf
(I did this while chrooted as described above.)

Before you can add stuff, you will probably need to remove some packages. To get a list of packages installed, type this:
dpkg-query -l
If you are looking for big installed packages then the command
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
will list the packages with size in descending order.

At least ten times faster is the command
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
and you don't need dpkg-awk or awk or perl; however it does not exclude packages that are not installed. If you have trouble with the above sort command, try using KPackage, expanded all the trees and sorted by the size column to find big packages.

Or, you could use this command to get the qpkg-query speed with the non-installed packages not listed:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
It does the same thing as above, I assume. I couldn't get the first one to work because I don't have dpkg-awk.

To remove a package (and all packages dependant on it), type this:
apt-get remove --purge ''name-of-package-to-remove''
To check for orphaned packages, type this:
deborphan
Want to save more space by getting rid of those pesky orphans (how cruel!), type this ('''Warning''', you won't be prompted yes/no to remove these packages. When you press Enter after this command, those packages ''will be gone''):
deborphan | xargs apt-get -y remove
If you're uncertain about the previous command and want to see what will happen without making any changes, just add the '''-s''' option to the apt-get command like this (you can do this with all of the apt-get commands, and it's a good habit to use this option before mass operations like this one):
deborphan | xargs apt-get -s -y remove
Now the good stuff. If you wish to add a package, type this:
apt-get install '''name-of-package-to-install''
What, don't know what packages to install? Type this. When the list appears, you can peruse (over 13k lines!) or search for things using <tt>/''search-term''</tt>:
apt-cache search .* | sort | less
When you're done removing and adding packages, a good way to clean up is by typing this
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Also, because the Debian package system keeps a cache of downloaded packages, you may want to run the following to clear out those spare files:
apt-get clean

===User Settings===
User settings are in /etc/skel. This directory will be copied to make new user home directories.
<blockquote>tip: don't put files in /root they will be only available (at runtime) in /KNOPPIX/root</blockquote>

Note that the default user 'knoppix' is not created by adduser(1), thus /etc/skel is not copied completely but rather selectively. That is, to make a file .xyrc appear in /home/knoppix, it is not sufficient to place it in /etc/skel. One possibility is to extend the code in /etc/X11/Xsession.d/45xsession which is responsible for filling /home/knoppix.

===Autorunning Programs===
When you want to autorun some programs, one can create a script and put it in the directory <tt>/etc/rc5.d/</tt> (This only loads items before X loads). Read up on the SysV init process for more possibilities.

''For X-programs consider <tt>/home/knoppix/.kde/Autostart</tt> but this may transfer form <tt>/etc/skel/.kde/Autostart</tt> on boot''--[[User:12.106.237.2|12.106.237.2]] 18:08, 7 December 2007 (UTC)

==Editing the KNOPPIX auto-configuration script==
You can find a lot of interesting information about how KNOPPIX auto-configures you system by looking in the /etc/init.d/knoppix-autoconfig script. Of particular note are the following.

===Changing the default KDE background image===
The auto-configuration script sets the default KDE background image to be an image from the CD-ROM. An image that you can easily change when you are remastering KNOPPIX.
** In KNOPPIX 3.3 and below it is /cdrom/KNOPPIX/background.gif
** In KNOPPIX 3.4 and above it is /cdrom/KNOPPIX/background.jpg

===Editing floppy and CD-ROM use or adding a custom script===
The auto-configuration script sets up both your CD-ROM and your floppy disk. The commands for doing this are 'floppyconfig' and 'cdromconfig', respectively. The auto-configuration script will also run cdrom/KNOPPIX/knoppix.sh, which is an easy script to change when remastering KNOPPIX.

===Changing the default boot parameters===
All boot parameters obtain default values from the /etc/init.d/knoppix-autoconfig script. This is one massive BASH script (you best know your BASH to play with this), but it is the place that you can edit any of the default boot parameters. For example, to switch from 'kde' to 'twm' as default desktop just search for the place where 'kde' is provided as default value (variable DESKTOP, IIRC). Another example would be changing the default language.

Note, if you are interested in changing the default language KDE uses, the easiest thing to do is to load KDE, instructions are below, and use the KDE configuration utility to select your language of interest.

==X Session Configuration==
When working with X-based programs you will have to make sure that your display is set appropriately. You can do this manually when remastering KNOPPIX. Also, two scripts related to X Session is where you can change or disable the startup and shutdown sounds.

===Starting X-based programs===
When testing X-based programs, you will have to
export DISPLAY=localhost:0.0
which will allow you to connect to your normal X session. Alternately (if you need to test window managers), you can create a nested X session. Outside of the chroot, run
Xnest -ac :1
Within the chroot, set your DISPLAY variable
export DISPLAY=localhost:1

Interesting stuff in /etc/init.d/xsession :
* it ALSO sets background as /usr/local/lib/knoppix.gif

===Modifying/Disabling the startup sound===
The startup sound is played by /etc/X11/Xsession.d/45xsession. You can disable it by commenting out the following lines.
<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

===Modifying/Disabling the shutdown sound===
The shutdown sound is played by /etc/init.d/xsession. You can disable it by commenting out lines 210-220 from the script.
<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

===Change default window manager===

Open /etc/init.d/knoppix-autoconfig and look for lines which look like these:
<pre><nowiki>
# Allow only supported windowmanagers
# Actually, this check is useless because it's done again in 45xsession. -KK
# case "$DESKTOP" in gnome|enlightenment|kde|larswm|xfce|xfce4|lg3d|ratpoison|blackbox|openbox|windowmaker|wmaker|icewm|fluxbox|twm|nx|rdp|kiosk) ;; *) DESKTOP="kde"; ;; esac
[ -n "$DESKTOP" ] || DESKTOP="kde"
</nowiki></pre>

Then, change "kde" in the last quoted line to whatever you like, for example to "fluxbox" or "twm".

==Changing the boot graphic, boot message, and startup script text==
While you are in the chroot environment you can easily change the boot messages, the boot graphic, and the default KDE background graphic.

===Changing the boot graphic===
The 'boot graphic' is the first image you see when the CD or DVD boots. It looks similar to ASCII art and it is normally something flashy that says 'Knoppix'. You can change this to be any graphic that you please, but you must use a 640x400 graphic that has only 16 colors.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old logo in case you break things.
#* <pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
#Make a 640x400 pixel 16 color graphic and save it as a GIF, e.g. 'logo.16.gif'. GIMP can easily do this. Note, you can use a graphic that originally had more than 16 colors, but it is critical that you convert the graphic to 16 colors before doing the next step.
#Convert the GIF to lss16 using the tools included on the Knoppix CD.
#* <pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm</nowiki></pre>
#* <pre><nowiki>ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

===Changing the boot message===
The 'boot message' is the message that you see under the 'boot graphic' on the initial screen when the Knoppix CD or DVD loads. It normally says something along the lines of Knoppix with the version number and includes a link to the Knoppix website. You can change this text to be whatever you please, but you shouldn't add too much text or it will make the boot screen look funny. Restricting yourself to a single line of text that is no larger than the default one is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old message in case you break things.
#* <pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
#Edit the message with a text editor. You'll see at the top of the message that it shows the graphic. Don't change this text, just the line under.
#* <pre><nowiki>vi boot.msg</nowiki></pre>

===Changing the startup script text===
The 'startup script text' is the text that you see after the initial boot screen, while Knoppix loads and configures your system. You can change as much of this text as you please. You can even add addition lines to the script; however, it is recommended that you don't play with this file. Limiting yourself to editing the 'Welcome to KNOPPIX' message is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old minirt.gz in case you break things.
#* <pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
#Uncompress minirt.gz
#* <pre><nowiki>gunzip minirt.gz</nowiki></pre>
#Make a temporary directory to mount the minirt filesystem.
#* <pre><nowiki>mkdir todelete</nowiki></pre>
#Mount the minirt filesystem as an ext2 filesystem.
#* <pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
#::or if the above does not work use
#* <pre><nowiki>mount minirt todelete -t ext2 -o loop</nowiki></pre>
#Edit the linuxrc script to display the message you want. You'll find the default message approximately 2 pages down and it'll be using several colors, i.e. ${WHITE}, ${RED}, etc., so it might be slightly tricky to spot.
#* <pre><nowiki>vi todelete/linuxrc</nowiki></pre>
#unmount the minirt filesystem.
#* <pre><nowiki>umount todelete</nowiki></pre>
#Compress the minirt filesystem.
#* <pre><nowiki>gzip -9 minirt</nowiki></pre>
#Remove your temporary directory.
#* <pre><nowiki>rmdir todelete</nowiki></pre>

==Launching KDE to Change Menus, Icons, etc.==
While you are in the chroot environment you can load KDE and use the configuration tools to change buttons, icons, etc. Once you are finished you can exit KDE and copy /home/knoppix to /etc/skel to keep these changes. To load KDE do the following.

#If you are not at runlevel 2 (i.e. if you are already in KDE), switch to runlevel 2.
#* <pre><nowiki>init 2</nowiki></pre>
#Copy /etc/skel to /home/knoppix
#* <pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
#Change permissions to the user 'knoppix'
#* <pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
#Copy over your X11 configuration to the chroot'd environment (press ctrl+alt+F2 to switch to a non-chroot'd terminal, then ctrl+alt+F1 to switch back when done)
#* <pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#*<blockquote>'' Knoppix 3.7: I think it's XF86Config-4 rather than xorg.conf.''</blockquote>
#(Optional)Switch to user 'knoppix'. If you want to uninstall packages, stay as root -- e.g. skip this step. If you want to configure the buttons, icons, background, etc., that you see when KDE boots, be sure to do this step.
#* <pre><nowiki>su knoppix</nowiki></pre>
##Launch KDE
##* <pre><nowiki>startx</nowiki></pre>
##Do your KDE changes
##Exit KDE
##Exit su and switch back to user 'root'.
##* <pre><nowiki>exit</nowiki></pre>
#Copy /home/knoppix back to /etc/skel to keep the changes
#* <pre><nowiki> mv /etc/skel /etc/skel-old</nowiki></pre>
#* <pre><nowiki>mv /home/knoppix /etc/skel</nowiki></pre>
#Set the owner back to root
#* <pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
#Remove the xorg.conf file
#* <pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>
#If you find that some of your settings are not persistent after booting the new image, check the initialization file at /etc/X11/Xsession.d/45xsession. By default, Knoppix does '''not''' simply copy over all files from /etc/skel. You may need to make modifications here if you wish to do something different.

===Changing the ksplash KDE graphics===
You can change the graphics that KDE shows via ksplash when it first loads. These graphics are in the /mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/ directory. You'll most likely want to swap out splash_top.png for a custom 400x248 PNG graphic. Note that ksplash will not automatically put a border around your graphic. If you'd like a border, you have to manually add it to your graphic.

==Leaving the Chroot==
If you mounted it, you'll need to unmount /proc - very important!
umount /proc
Press '''CTRL+D''' to leave being chrooted.

==Re-Entering the chroot==
If you've left the chroot, but you want to go back in and modify some things...

Remount the local hard disk (if needed)
<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
Setup the environment for chroot
<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc
mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</nowiki></pre>
Now you can "chroot" into the copied KNOPPIX:
<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>

==Remastering the ISO==
We've finished customizing and ready to burn!
First do some cleanup:
* remove any .bash_history files, tmp files, etc.
* back out any changes you don't want burned back to the disc
* make sure you umount /proc /dev /sys or mkisofs will not work properly
* <pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

===KNOPPIX Compressed Image===
Now we'll make the big <tt>KNOPPIX</tt> file which is an ISO 9660 filesystem compressed for use by the <tt>cloop</tt> driver:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
the "www.knoppix.net" and "Knoppix.net filesystem" can be changed to what you want to call the file. You will get an error that it doesn't conform to ISO standards -- you can ignore this. Note that, to run <tt>create_compressed_fs</tt>, you'll need to have enough space to store the entire ISO in RAM/swap. Ensure you have at least 800M of free space before starting.

In Knoppix 3.4 the <tt>create_compressed_fs</tt> script has been updated so be sure to use it to obtain the best result. It has a new option '''-b''' (best), which enables the best compression by using different compression schemes and tries to optimize that way, but be careful, because that option is slow (10x slower).

Note: The above didn't work for me using the latest create_compressed_fs. I could create the ISO but it couldn't read the compressed image properly when booting (I/O errors when reading the cloop0 device). I think this was because create_compressed_fs didn't have enough RAM and it was just failing silently. The command below did work though. It uses a file rather than memory for temporary storage:

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/hda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

------I tried this ,but it report a error,so i think there is some mistake in the command,it may be like follow,tell me if anyone confirm it-------
----------(by zhblue(newsclanATgmail.com))-------

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -b \
-f /mnt/hda1/isotemp -B 65536 - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

I noted several problems with the commands above: 
1) The option "-no-bak" excludes files with the ending ".bak". Non-backup files with this ending are found in some software packages, e.g. glest. It is safer not to use this option. 
2) Just calling "create_compressed_fs - 65536" gives a warning about old command syntax. The compatible parameters are "-m -B 65536". The later examples here already fixed this, the first example still uses the deprecated version.

===Live CD ISO===
If all went well, onto making the final CD-ROM Image:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(this will update the md5 hashes of the files included in the ISO, used for integrity checking) Now to burn the image; for Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
for Knoppix >= 3.4 or other isolinux based distributions:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(the ISO is stored in <tt>/mnt/hda1/knx/knoppix.iso</tt>)

Burn the ISO using your favorite tools, and you're ready!

==How to add new device driver to KNOPPIX==

Recently in a client project, I added the Digital Persona’s finger print driver to the Knoppix 5.1 distribution as an embedded solution to this project. This is a typical case where both the kernel level driver and the user level drivers and libraries are involved.

Most of the Knoppix books and online documentation have documented about how to keep a persistent storage of user configuration and user data. But those persistent configuration only saves the data in /home and /etc directories. If you have added kernel level drivers and/or other system libraries which are not in above two directories, you have to save the file images as a whole right after the boot. The saved file image can be big and may not what you want as a regular usage model. If you are building a customed Knoppix image for a long term solution, definitely you want to remaster the Knoppix to make the new drives be a permanent part of it.

The Digital Persona’s OneTouch SDK for their finger print scanner driver comes with a kernel level driver source code, plus a set of user level application libraries, as well as a sample test application. The SDK do not have a ready made binary for Debian or Knoppix. So I have to compile it from the source SDK. However, the CD version of Knoppix 5.1 do not even come with the source include header files to compile a kernel level driver. So I have to compile it under the DVD version of the Knoppix 5.1 and copy the compiled binary to the CD version of Knoppix 5.1 to do testing and remastering. The steps I have tried to make it work under Knoppix are as follows:

1. First compile the driver under DVD version of the Knoppix. Change the source code build scripts so that the include files and library path are matching what we have in Knoppix. The details are specific to the OneTouch SDK itself. If you are interested about this detail, write to me.

2. Install the just built kernel driver, the user libraries to their regular location as we will show in following step 4. And then build and run their sample applications per Digital Persona’s instruction. This proves that the basic kernel module build steps are built correctly and the user level libraries are working properly in a standard installation. This is important before we moved to chroot environment to make this changes permanent to our remastered Knoppix.

3. Then I followed the Knoppix remastering instructions documented in the book of “Live Linux CD” by Christoper Negus.

4. In the above remastering instructions, there is a step to update all the Debian packages and other software under the chroot environment. It is at this step that I re-run the drivers installation steps like I have done in above step 2 in the real root environment. In this particular case, it is make a directory and copy the kernel module file mod_usbdpfp.ko to that directory as follows:

mkdir /lib/modules/2.6.19/kernel/drivers/biometric
cp mod_usbdpfp.ko /lib/modules/2.6.19/mod_usbdpfp.ko

And also copy all those Digital Persona user level libraries to following location:

cp libdpfp* /usr/lib

5. I then run /sbin/depmod to let system detects the new kernel mode driver I have installed. This will refresh the /dev directory so it will have entries like:

/dev/usbdpfpPNP
/dev/usbdpfp0

At this time, if all works right, when you run command lsmod, you will also see something like:

mod_usbdpfp

shows up in the loaded module list

6. At this time, you are ready to make a remaster of the Knoppix. Next time when you boot up with this remastered Knoppix, it will have the kernel driver and user level libraries setup ready for you to run the sample applications. Just as if you have done above step 2 and step 4 right after a refresh reboot from the original Knoppix CD.

John Xu, USA. ( johnxu at n2k.net )

=Tips=
I have had good results remastering working from the CD as root working from fluxbox. Just say "knoppix 2" at the boot prompt and it will boot you to a root prompt where you can then say "startx /usr/bin/fluxbox". I like to use the xterm unicode shell.

==Package Management==
While working chroot doing the remastering I like to use
apt-get remove --purge pkg-name
to remove packages because before it does anything it will stop and show details on what it is fixing to remove and let you say "yes or no".

If you don't use the above "apt-get" instructions and have a lot to cleanup and purge, here's the easy way to do it:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
That will make a list of all removed packages to purge and then you just say
dpkg -P `< topurge `
and you're all done.
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
is a one-line version of this. Also use
deborphan | xargs dpkg -P .

==Alternatives for Low-Memory Machines==
You don't really need 1G swap as there are two new tools to create compressed filesystems. Here are some candidates to make ''compressed'' fs:
* Valentijn's rewrite [http://projects.openoffice.nl/downloads/compressloop/]
* Quozl's port of compressloop for Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Quozl's distributed compressloop (use more than one processor to speed things up) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Justin's patch [http://s.bouncybouncy.net/~justin/code/] (link broken) I also just wrote a distributed cloop compressor(or for smp) It's in that same directory.

==Test CD Image Without Burning a CD==
If you have a spare partition with at least 700MB free space formatted with ext2, ext3 or Vfat, you can use this for test by booting from a floppy disk. A floppy boot will look for a partiton with /KNOPPIX/ in the root, and the compressed image /KNOPPIX/KNOPPIX. Instead of using the sub-directory /mnt/hda1/knx/master/KNOPPIX/ as described above, it should be called /mnt/hda2/KNOPPIX/ . The root index.html will then be located at /mnt/hda2/index.html and the compressed image will be at /mnt/hda2/KNOPPIX/KNOPPIX . Now you can boot from floppy and use /mnt/hda2 as your image. For further information see [[Hd BasedHowTo]].

If you don't have an extra partition or you don't want to do so much for it, you can use Qemu ( see [http://fabrice.bellard.free.fr/qemu/] ) with the ISO image like this:
qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -net user
You even do not have to build a hard disk image before, just install Qemu and try this. Amazing!

==Test remastered version without creating cloop file/iso==
i use a setup similar to knoppix terminal server to test the remastered files without having to recreate a
cloop image every time: the remastered files live in an ext2 filesytem in a loopfile (knoppix_loop) mounted rw (this is where i chroot in). when i want to test the current setup, i have another machine network boot and use the files from the loopfile directly (needs another miniroot.gz). See [[User:Ml#dev_setup]]

If you want to use only one machine, you'll have to reboot (or use qemu) and use the "loopfile" and "fromhd" cheatcodes (see [[User:Ml#miniroot_changes]]). For example, this is what my grub boot entry looks like:

<pre>
title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz
</pre>

== Booting Knoppix images with GRUB==
* First copy /boot off the Knoppix cd to your boot partition (or even your dos partition). I named mine boot.knoppix
Copy the master/KNOPPIX directory to your root directory of any hard disk. You may place it somewhere other than the boot partition (ext2/3, reiserfs, vfat are supported).
* for Knoppix <= 3.3, put the following in your /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* for Knoppix >= 3.4 or other isolinux based distributions:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* notice the fromhd parameter: it's the location of the /KNOPPIX directory
* reboot and have fun.

==Helpful Scripts==
----
This is the recommended directory layout for remastering KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
the following script "remaster" will do the remaster process for you. Use as root, or you will end up with wrong access rights in the image.

The script has last been tried out on Debian sid on 2004-04-02.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
The following script will loop-mount boot floppy image and initrd image for modification. The umount function will build a new initrd image and put it back on the boot floppy image.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

==Tips around apt-get to install/update/remove applications==
(by gnarvaja)
* If you booted from CD, even on a HD install (example: Pivot Install) instead of copying the original CD and KNOPPIX directory to the HD, you can use them directly from their mount points.
* Another alternative is to mount an ISO image of the original CD as a loop device and mount the KNOPPIX image as a '''cloop''' device. You will save close to 2GB of space. Script to mount from an ISO image:

#!/bin/bash
# Assumes that the current directory is the working space
# original.iso is an image of the CD we will be using as master
mount -t iso9660 original.iso ./oldcd -o ro,loop
# initialize the compressed loop device
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop

* Get '''apt-spy''' and use it to modify the sources.list file with the best mirrors for your particular region. This will speed up the downloading. Backup the original '''sources.list''' just in case.
* Another technique is to modify '''sources.list'''. Replace the string '''.de.''' in the ftp addresses (ftp.de.debian.org) with the code corresponding to your country. Examples: USA -> .us. (ftp.us.debian.org), Brazil -> .br. (ftp.br.debian.org). Check the Debian site for debian.org mirrors in your country.
* Remember to uncomment the '''linuxtag''' ftp addresses to get the latest and greatest from Knoppix
* Use '''apt-get update''' to get the lists with the latest releases and patches. Do not update a package if you don't need to, it may lead to the use of additional disk space (precious commodity when you want to keep everything below 700MB) and you may brake something else without knowing. Abuse the '''-s''' option to simulate the installation.
* Before doing the update, I modified my default releases to '''testing''', that means that the software I'll be using will have a good balance of stability and features. Knoppix uses '''unstable''' by default, which is too risky for my personal taste.
* Get '''[apt-get install] locale''' and configure it with the locales you are going to use. It will save lots of space when downloading applications with plenty of locale modules and localized manual pages.
* I use '''aptitude''' to get/remove applications, it is character based so it works with init 2. As you mark packages for install/update/removal, it will tell you how much disk space you will save/use, try to solve depencies problems and give you plenty control to fix them manually when possible.
* When installing applications it is likely that your '''/etc/rc?.d''' directories will have new entries, many of them unwanted or unplanned. Make sure you check them and remove the new entries based on your preferences. I usually leave '''/etc/rc2.d''' and '''/etc/rc5.d''' as close as the originals as possible and modify '''/etc/rc3.d''' and '''/etc/rc4.d''' to test new stuff. '''Example:''' You may want to have ntfs installed, but not necessarily running by default. Same with apache, mysql and many others.
* When removing/purging applications, they may leave behind non-empty directories. Usually this is announced by aptitude, apt-get or any other installation utilty. Make sure to check the messages and manually remove those directories.
* After you are done, '''aptitude''' may leave some files behind. Here's a clean up script I use:

# !/bin/bash
# Clean package files generated by aptitude
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

=Common Problems=
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] Chroot problems accessing device files

* You've <code>startx</code>'d (into whatever window manager you like) and you start a terminal (gnome-terminal, konsole, xterm). Nothing happens (such is the case in fluxbox, and you'll see an error in you <code>~/.xsession-errors</code> file). Or perhaps the error is helpfully displayed: <code>
get_pty: not enough ptys
</code>
I had plenty yesterday... but then I <code>chroot</code>ed so, to solve this, <code>
# NOT in your chroot environment
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# enter your chroot environment
chroot /mnt/hda1/knx/source/KNOPPIX/

# and mount /dev/pts
mount -t devpts /dev/pts/ /dev/pts

</code>
it might give that same "fstab not found" error as mounting proc
does. so do what you'd do then, disregard.

start your X up again and try your terminal, should work.
thanks to: technovelty[http://www.technovelty.org/linux/tips/xinchroot.html] for the final enlightenment

=See also=

If my howto is too confusing, or you'd like a second opinion, check out charan's very nice remastering howto: http://brainstorms.in/?page_id=84
Another Howto is at http://www.stirnimann.com/mystuff/doc/knoppix.txt

There is a wizard, which knows all the unpacking, compressing and CD-recording steps mentioned here. It also shows a shell where you can update the uncompressed KNOPPIX system using debian's standard software installation tools. It is called mmkcdrom and part of the plugscript package: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Yet another HOWTO, for shell freaks, is at http://quozl.linux.org.au/knoppix/

Be sure to check out the [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] for ideas and help with remastering.

* If you want to add a custom kernel, check out the [[Knoppix Custom Kernel Howto]]
* There also a guide at O'Reilly on the same topic : [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

=Conclusion=
Thats it. This is an updated version of my previous howto. This is not meant for linux beginners, you will need to know your way around linux to get this to work. I'll update this as corrections/improvements/etc come through.

=Thanks=
Thanks to aay, charan, Tech2k, and #knoppix for some corrections and tips and ideas. Feel free to edit or add to this howto.
Note about swap: 

=Translations=
* German Version: [[Knoppix Remastering Howto Deutsch]]
* Spanish Version: [[Knoppix Remastering Howto Spanish]] en español
* French Version: [[Knoppix Remastering Howto French]]
* Indonesian Version: [[Knoppix Remastering Howto Indonesian]]
* Russian Version: [[Knoppix Remastering Howto Russian]]
* Brazilian Portuguese Version: [[Knoppix Remastering Howto Brazilian Portuguese]]
* Italian Version: [[Knoppix Remastering Howto Italiano]]

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto

2008-05-19T11:57:19Z

202.88.238.45: /* See also */

This is a guide that will show you how to remaster KNOPPIX. (Note: commands should appear on one line, so please maximize the window. If you have any comments/suggestions please post below.)

You may wish to start from an already customized Knoppix, so you don't have to do as much work (such as removing programs). If so, see [[Knoppix Customizations]].

=System Requirements=
*CD-ISO
** at least 1 GB of FREE RAM+Swap total (e.g. 256M ram, and 750M swap AVAILABLE) (unless you use a different compression program - look in this page for compressloop)
** 3 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition
*DVD-ISO
** 5 GB free RAM + swap (for fullsized DVD)
** 15 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition

=Instructions=
==Setting up for Remastering==
# Boot from the ''Knoppix CD''
# Open a root shell:
#* Menu: Kmenu->Knoppix->Root Shell
#* Note: All commands below are run from this root shell.
# Configure your Internet connection (we'll need this later). If you use DHCP, it should already be configured.
#* Note: Run '''ifconfig''' to check.
# Find the partition you will use to work on. In this example it is called '''hda1''' . The partition should have a minimum of 3 GB free space
# Mount the partition:
#*<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Note: Make sure that it is read/write or you will get errors when you later chroot. To check: run '''mount'''
# Create a root directory to work in -- if you put all your files here it will be easy to clean up
#* <pre>mkdir /mnt/hda1/knx</pre>
# If you don't have 1 GB RAM ( '''egrep "(MemTotal|SwapTotal)" /proc/meminfo && echo "(physical+swap)"''' ) then you will need a swapfile:
#* <pre>cd /mnt/hda1/knx</pre>
#* <pre>dd if=/dev/zero of=swapfile bs=1M count=750</pre>
#* <pre>mkswap swapfile</pre>
#* <pre>swapon swapfile</pre>
# Make 2 directories, one for your new Master CD, one for the source, on a disk partition. Also, make additional directories under these named KNOPPIX:
#* <pre>mkdir -p /mnt/hda1/knx/master/KNOPPIX</pre>
#* <pre>mkdir -p /mnt/hda1/knx/source/KNOPPIX</pre>
# Now, copy the KNOPPIX files to your source directory :
#* <pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Note: This will take a long time (you are copying 2GB). Warning: you will be tempted to replace this copy command with a much faster procedure: create an empty directory, then use unionfs to merge the empty directory with /KNOPPIX in order to create the read-write copy. However, as of Knoppix 4.0.2, there is a bug in unionfs that causes this faster procedure to fail. For now, stick with the copy-command shown above.
# Additionally, copy the 'boot' folder from your cdrom - you'll need these files to build the ISO later.
#* <pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
# For Knoppix 5.0.1 you also have to copy the 'modules' folder:
#* <pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copy the main HTML page for the startup page:
#* <pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copy everything necessary files except the ~700 Mb KNOPPIX file.
#* < 3.4:
#** <pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* >= 3.4:
#** <pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* for the DVD Version you have to use -size -15000k and copy the KNOPPIX2 folder like this
#** <pre>cp -ar /KNOPPIX2/* /mnt/hda1/knx/source/KNOPPIX</pre>
# setup the environment for chroot
#* <pre>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev</pre>
#* <pre>mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</pre>
#* <pre>mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</pre>
# Now you can "chroot" into the copied KNOPPIX:
#* <pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# If you see errors regarding <tt>/dev/null</tt>, see the [[#Common Problems|common problems]] section
You are now chrooted. "/" is actually "/mnt/hda1/knx/source/KNOPPIX"

==Working in the Chroot Environment==
Remember that anything you do or create in the chrooted environment will get burned to the CD. If you make any changes (e.g,. to the APT configuration, proxy settings, etc.), make a note to back the changes out before remastering.
===Internet Access===
To use the Internet you need to edit <tt>/etc/resolv.conf</tt> to add your nameserver or exit the chroot and copy the outer <tt>resolv.conf</tt> into the chroot folder:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf
(proxies (a.k.a. doing it at work): you can type "export http_proxy=http://your.proxy.com:<port>") 
To check your chrooted internet connection,
ping google.com
(if ICMP is barred at some corporate firewall or something then try "lynx http://www.google.com" and see if you get the page -after a cookie "allow")

===SMB access===
Also change smb.conf to your MS group if you want smbd support (MSHOME is XP Home ed. usually, and WORKGROUP is 9x Windows)
===APT===
Update your package list with '''apt-get update'''.
<blockquote>Note: If ''''apt-get update''' fails with "FATAL -> Could not set non-blocking flag Bad file descriptor", you need to make sure your chrooted environment is mounted without the "nodev" option. (see above where it talks about the /dev/null errors when entering the chroot environment for the first time)</blockquote>
<blockquote>'''Warning''': apt-get upgrade is a ''BAD IDEA''. It will, quite probably, render your KNOPPIX remaster unbootable, or broken in some way. A far safer method is to only upgrade packages as necessary.</blockquote>

'''Note: If apt-get fails with "Dynamic NMap ran out of room" ''' you might try this little gem, which fixed the problem for me:
#echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf
(I did this while chrooted as described above.)

Before you can add stuff, you will probably need to remove some packages. To get a list of packages installed, type this:
dpkg-query -l
If you are looking for big installed packages then the command
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
will list the packages with size in descending order.

At least ten times faster is the command
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
and you don't need dpkg-awk or awk or perl; however it does not exclude packages that are not installed. If you have trouble with the above sort command, try using KPackage, expanded all the trees and sorted by the size column to find big packages.

Or, you could use this command to get the qpkg-query speed with the non-installed packages not listed:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
It does the same thing as above, I assume. I couldn't get the first one to work because I don't have dpkg-awk.

To remove a package (and all packages dependant on it), type this:
apt-get remove --purge ''name-of-package-to-remove''
To check for orphaned packages, type this:
deborphan
Want to save more space by getting rid of those pesky orphans (how cruel!), type this ('''Warning''', you won't be prompted yes/no to remove these packages. When you press Enter after this command, those packages ''will be gone''):
deborphan | xargs apt-get -y remove
If you're uncertain about the previous command and want to see what will happen without making any changes, just add the '''-s''' option to the apt-get command like this (you can do this with all of the apt-get commands, and it's a good habit to use this option before mass operations like this one):
deborphan | xargs apt-get -s -y remove
Now the good stuff. If you wish to add a package, type this:
apt-get install '''name-of-package-to-install''
What, don't know what packages to install? Type this. When the list appears, you can peruse (over 13k lines!) or search for things using <tt>/''search-term''</tt>:
apt-cache search .* | sort | less
When you're done removing and adding packages, a good way to clean up is by typing this
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Also, because the Debian package system keeps a cache of downloaded packages, you may want to run the following to clear out those spare files:
apt-get clean

===User Settings===
User settings are in /etc/skel. This directory will be copied to make new user home directories.
<blockquote>tip: don't put files in /root they will be only available (at runtime) in /KNOPPIX/root</blockquote>

Note that the default user 'knoppix' is not created by adduser(1), thus /etc/skel is not copied completely but rather selectively. That is, to make a file .xyrc appear in /home/knoppix, it is not sufficient to place it in /etc/skel. One possibility is to extend the code in /etc/X11/Xsession.d/45xsession which is responsible for filling /home/knoppix.

===Autorunning Programs===
When you want to autorun some programs, one can create a script and put it in the directory <tt>/etc/rc5.d/</tt> (This only loads items before X loads). Read up on the SysV init process for more possibilities.

''For X-programs consider <tt>/home/knoppix/.kde/Autostart</tt> but this may transfer form <tt>/etc/skel/.kde/Autostart</tt> on boot''--[[User:12.106.237.2|12.106.237.2]] 18:08, 7 December 2007 (UTC)

==Editing the KNOPPIX auto-configuration script==
You can find a lot of interesting information about how KNOPPIX auto-configures you system by looking in the /etc/init.d/knoppix-autoconfig script. Of particular note are the following.

===Changing the default KDE background image===
The auto-configuration script sets the default KDE background image to be an image from the CD-ROM. An image that you can easily change when you are remastering KNOPPIX.
** In KNOPPIX 3.3 and below it is /cdrom/KNOPPIX/background.gif
** In KNOPPIX 3.4 and above it is /cdrom/KNOPPIX/background.jpg

===Editing floppy and CD-ROM use or adding a custom script===
The auto-configuration script sets up both your CD-ROM and your floppy disk. The commands for doing this are 'floppyconfig' and 'cdromconfig', respectively. The auto-configuration script will also run cdrom/KNOPPIX/knoppix.sh, which is an easy script to change when remastering KNOPPIX.

===Changing the default boot parameters===
All boot parameters obtain default values from the /etc/init.d/knoppix-autoconfig script. This is one massive BASH script (you best know your BASH to play with this), but it is the place that you can edit any of the default boot parameters. For example, to switch from 'kde' to 'twm' as default desktop just search for the place where 'kde' is provided as default value (variable DESKTOP, IIRC). Another example would be changing the default language.

Note, if you are interested in changing the default language KDE uses, the easiest thing to do is to load KDE, instructions are below, and use the KDE configuration utility to select your language of interest.

==X Session Configuration==
When working with X-based programs you will have to make sure that your display is set appropriately. You can do this manually when remastering KNOPPIX. Also, two scripts related to X Session is where you can change or disable the startup and shutdown sounds.

===Starting X-based programs===
When testing X-based programs, you will have to
export DISPLAY=localhost:0.0
which will allow you to connect to your normal X session. Alternately (if you need to test window managers), you can create a nested X session. Outside of the chroot, run
Xnest -ac :1
Within the chroot, set your DISPLAY variable
export DISPLAY=localhost:1

Interesting stuff in /etc/init.d/xsession :
* it ALSO sets background as /usr/local/lib/knoppix.gif

===Modifying/Disabling the startup sound===
The startup sound is played by /etc/X11/Xsession.d/45xsession. You can disable it by commenting out the following lines.
<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

===Modifying/Disabling the shutdown sound===
The shutdown sound is played by /etc/init.d/xsession. You can disable it by commenting out lines 210-220 from the script.
<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

===Change default window manager===

Open /etc/init.d/knoppix-autoconfig and look for lines which look like these:
<pre><nowiki>
# Allow only supported windowmanagers
# Actually, this check is useless because it's done again in 45xsession. -KK
# case "$DESKTOP" in gnome|enlightenment|kde|larswm|xfce|xfce4|lg3d|ratpoison|blackbox|openbox|windowmaker|wmaker|icewm|fluxbox|twm|nx|rdp|kiosk) ;; *) DESKTOP="kde"; ;; esac
[ -n "$DESKTOP" ] || DESKTOP="kde"
</nowiki></pre>

Then, change "kde" in the last quoted line to whatever you like, for example to "fluxbox" or "twm".

==Changing the boot graphic, boot message, and startup script text==
While you are in the chroot environment you can easily change the boot messages, the boot graphic, and the default KDE background graphic.

===Changing the boot graphic===
The 'boot graphic' is the first image you see when the CD or DVD boots. It looks similar to ASCII art and it is normally something flashy that says 'Knoppix'. You can change this to be any graphic that you please, but you must use a 640x400 graphic that has only 16 colors.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old logo in case you break things.
#* <pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
#Make a 640x400 pixel 16 color graphic and save it as a GIF, e.g. 'logo.16.gif'. GIMP can easily do this. Note, you can use a graphic that originally had more than 16 colors, but it is critical that you convert the graphic to 16 colors before doing the next step.
#Convert the GIF to lss16 using the tools included on the Knoppix CD.
#* <pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm</nowiki></pre>
#* <pre><nowiki>ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

===Changing the boot message===
The 'boot message' is the message that you see under the 'boot graphic' on the initial screen when the Knoppix CD or DVD loads. It normally says something along the lines of Knoppix with the version number and includes a link to the Knoppix website. You can change this text to be whatever you please, but you shouldn't add too much text or it will make the boot screen look funny. Restricting yourself to a single line of text that is no larger than the default one is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old message in case you break things.
#* <pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
#Edit the message with a text editor. You'll see at the top of the message that it shows the graphic. Don't change this text, just the line under.
#* <pre><nowiki>vi boot.msg</nowiki></pre>

===Changing the startup script text===
The 'startup script text' is the text that you see after the initial boot screen, while Knoppix loads and configures your system. You can change as much of this text as you please. You can even add addition lines to the script; however, it is recommended that you don't play with this file. Limiting yourself to editing the 'Welcome to KNOPPIX' message is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old minirt.gz in case you break things.
#* <pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
#Uncompress minirt.gz
#* <pre><nowiki>gunzip minirt.gz</nowiki></pre>
#Make a temporary directory to mount the minirt filesystem.
#* <pre><nowiki>mkdir todelete</nowiki></pre>
#Mount the minirt filesystem as an ext2 filesystem.
#* <pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
#::or if the above does not work use
#* <pre><nowiki>mount minirt todelete -t ext2 -o loop</nowiki></pre>
#Edit the linuxrc script to display the message you want. You'll find the default message approximately 2 pages down and it'll be using several colors, i.e. ${WHITE}, ${RED}, etc., so it might be slightly tricky to spot.
#* <pre><nowiki>vi todelete/linuxrc</nowiki></pre>
#unmount the minirt filesystem.
#* <pre><nowiki>umount todelete</nowiki></pre>
#Compress the minirt filesystem.
#* <pre><nowiki>gzip -9 minirt</nowiki></pre>
#Remove your temporary directory.
#* <pre><nowiki>rmdir todelete</nowiki></pre>

==Launching KDE to Change Menus, Icons, etc.==
While you are in the chroot environment you can load KDE and use the configuration tools to change buttons, icons, etc. Once you are finished you can exit KDE and copy /home/knoppix to /etc/skel to keep these changes. To load KDE do the following.

#If you are not at runlevel 2 (i.e. if you are already in KDE), switch to runlevel 2.
#* <pre><nowiki>init 2</nowiki></pre>
#Copy /etc/skel to /home/knoppix
#* <pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
#Change permissions to the user 'knoppix'
#* <pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
#Copy over your X11 configuration to the chroot'd environment (press ctrl+alt+F2 to switch to a non-chroot'd terminal, then ctrl+alt+F1 to switch back when done)
#* <pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#*<blockquote>'' Knoppix 3.7: I think it's XF86Config-4 rather than xorg.conf.''</blockquote>
#(Optional)Switch to user 'knoppix'. If you want to uninstall packages, stay as root -- e.g. skip this step. If you want to configure the buttons, icons, background, etc., that you see when KDE boots, be sure to do this step.
#* <pre><nowiki>su knoppix</nowiki></pre>
##Launch KDE
##* <pre><nowiki>startx</nowiki></pre>
##Do your KDE changes
##Exit KDE
##Exit su and switch back to user 'root'.
##* <pre><nowiki>exit</nowiki></pre>
#Copy /home/knoppix back to /etc/skel to keep the changes
#* <pre><nowiki> mv /etc/skel /etc/skel-old</nowiki></pre>
#* <pre><nowiki>mv /home/knoppix /etc/skel</nowiki></pre>
#Set the owner back to root
#* <pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
#Remove the xorg.conf file
#* <pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>
#If you find that some of your settings are not persistent after booting the new image, check the initialization file at /etc/X11/Xsession.d/45xsession. By default, Knoppix does '''not''' simply copy over all files from /etc/skel. You may need to make modifications here if you wish to do something different.

===Changing the ksplash KDE graphics===
You can change the graphics that KDE shows via ksplash when it first loads. These graphics are in the /mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/ directory. You'll most likely want to swap out splash_top.png for a custom 400x248 PNG graphic. Note that ksplash will not automatically put a border around your graphic. If you'd like a border, you have to manually add it to your graphic.

==Leaving the Chroot==
If you mounted it, you'll need to unmount /proc - very important!
umount /proc
Press '''CTRL+D''' to leave being chrooted.

==Re-Entering the chroot==
If you've left the chroot, but you want to go back in and modify some things...

Remount the local hard disk (if needed)
<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
Setup the environment for chroot
<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc
mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</nowiki></pre>
Now you can "chroot" into the copied KNOPPIX:
<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>

==Remastering the ISO==
We've finished customizing and ready to burn!
First do some cleanup:
* remove any .bash_history files, tmp files, etc.
* back out any changes you don't want burned back to the disc
* make sure you umount /proc /dev /sys or mkisofs will not work properly
* <pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

===KNOPPIX Compressed Image===
Now we'll make the big <tt>KNOPPIX</tt> file which is an ISO 9660 filesystem compressed for use by the <tt>cloop</tt> driver:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
the "www.knoppix.net" and "Knoppix.net filesystem" can be changed to what you want to call the file. You will get an error that it doesn't conform to ISO standards -- you can ignore this. Note that, to run <tt>create_compressed_fs</tt>, you'll need to have enough space to store the entire ISO in RAM/swap. Ensure you have at least 800M of free space before starting.

In Knoppix 3.4 the <tt>create_compressed_fs</tt> script has been updated so be sure to use it to obtain the best result. It has a new option '''-b''' (best), which enables the best compression by using different compression schemes and tries to optimize that way, but be careful, because that option is slow (10x slower).

Note: The above didn't work for me using the latest create_compressed_fs. I could create the ISO but it couldn't read the compressed image properly when booting (I/O errors when reading the cloop0 device). I think this was because create_compressed_fs didn't have enough RAM and it was just failing silently. The command below did work though. It uses a file rather than memory for temporary storage:

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/hda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

------I tried this ,but it report a error,so i think there is some mistake in the command,it may be like follow,tell me if anyone confirm it-------
----------(by zhblue(newsclanATgmail.com))-------

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -b \
-f /mnt/hda1/isotemp -B 65536 - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

I noted several problems with the commands above: 
1) The option "-no-bak" excludes files with the ending ".bak". Non-backup files with this ending are found in some software packages, e.g. glest. It is safer not to use this option. 
2) Just calling "create_compressed_fs - 65536" gives a warning about old command syntax. The compatible parameters are "-m -B 65536". The later examples here already fixed this, the first example still uses the deprecated version.

===Live CD ISO===
If all went well, onto making the final CD-ROM Image:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(this will update the md5 hashes of the files included in the ISO, used for integrity checking) Now to burn the image; for Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
for Knoppix >= 3.4 or other isolinux based distributions:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(the ISO is stored in <tt>/mnt/hda1/knx/knoppix.iso</tt>)

Burn the ISO using your favorite tools, and you're ready!

==How to add new device driver to KNOPPIX==

Recently in a client project, I added the Digital Persona’s finger print driver to the Knoppix 5.1 distribution as an embedded solution to this project. This is a typical case where both the kernel level driver and the user level drivers and libraries are involved.

Most of the Knoppix books and online documentation have documented about how to keep a persistent storage of user configuration and user data. But those persistent configuration only saves the data in /home and /etc directories. If you have added kernel level drivers and/or other system libraries which are not in above two directories, you have to save the file images as a whole right after the boot. The saved file image can be big and may not what you want as a regular usage model. If you are building a customed Knoppix image for a long term solution, definitely you want to remaster the Knoppix to make the new drives be a permanent part of it.

The Digital Persona’s OneTouch SDK for their finger print scanner driver comes with a kernel level driver source code, plus a set of user level application libraries, as well as a sample test application. The SDK do not have a ready made binary for Debian or Knoppix. So I have to compile it from the source SDK. However, the CD version of Knoppix 5.1 do not even come with the source include header files to compile a kernel level driver. So I have to compile it under the DVD version of the Knoppix 5.1 and copy the compiled binary to the CD version of Knoppix 5.1 to do testing and remastering. The steps I have tried to make it work under Knoppix are as follows:

1. First compile the driver under DVD version of the Knoppix. Change the source code build scripts so that the include files and library path are matching what we have in Knoppix. The details are specific to the OneTouch SDK itself. If you are interested about this detail, write to me.

2. Install the just built kernel driver, the user libraries to their regular location as we will show in following step 4. And then build and run their sample applications per Digital Persona’s instruction. This proves that the basic kernel module build steps are built correctly and the user level libraries are working properly in a standard installation. This is important before we moved to chroot environment to make this changes permanent to our remastered Knoppix.

3. Then I followed the Knoppix remastering instructions documented in the book of “Live Linux CD” by Christoper Negus.

4. In the above remastering instructions, there is a step to update all the Debian packages and other software under the chroot environment. It is at this step that I re-run the drivers installation steps like I have done in above step 2 in the real root environment. In this particular case, it is make a directory and copy the kernel module file mod_usbdpfp.ko to that directory as follows:

mkdir /lib/modules/2.6.19/kernel/drivers/biometric
cp mod_usbdpfp.ko /lib/modules/2.6.19/mod_usbdpfp.ko

And also copy all those Digital Persona user level libraries to following location:

cp libdpfp* /usr/lib

5. I then run /sbin/depmod to let system detects the new kernel mode driver I have installed. This will refresh the /dev directory so it will have entries like:

/dev/usbdpfpPNP
/dev/usbdpfp0

At this time, if all works right, when you run command lsmod, you will also see something like:

mod_usbdpfp

shows up in the loaded module list

6. At this time, you are ready to make a remaster of the Knoppix. Next time when you boot up with this remastered Knoppix, it will have the kernel driver and user level libraries setup ready for you to run the sample applications. Just as if you have done above step 2 and step 4 right after a refresh reboot from the original Knoppix CD.

John Xu, USA. ( johnxu at n2k.net )

=Tips=
I have had good results remastering working from the CD as root working from fluxbox. Just say "knoppix 2" at the boot prompt and it will boot you to a root prompt where you can then say "startx /usr/bin/fluxbox". I like to use the xterm unicode shell.

==Package Management==
While working chroot doing the remastering I like to use
apt-get remove --purge pkg-name
to remove packages because before it does anything it will stop and show details on what it is fixing to remove and let you say "yes or no".

If you don't use the above "apt-get" instructions and have a lot to cleanup and purge, here's the easy way to do it:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
That will make a list of all removed packages to purge and then you just say
dpkg -P `< topurge `
and you're all done.
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
is a one-line version of this. Also use
deborphan | xargs dpkg -P .

==Alternatives for Low-Memory Machines==
You don't really need 1G swap as there are two new tools to create compressed filesystems. Here are some candidates to make ''compressed'' fs:
* Valentijn's rewrite [http://projects.openoffice.nl/downloads/compressloop/]
* Quozl's port of compressloop for Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Quozl's distributed compressloop (use more than one processor to speed things up) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Justin's patch [http://s.bouncybouncy.net/~justin/code/] (link broken) I also just wrote a distributed cloop compressor(or for smp) It's in that same directory.

==Test CD Image Without Burning a CD==
If you have a spare partition with at least 700MB free space formatted with ext2, ext3 or Vfat, you can use this for test by booting from a floppy disk. A floppy boot will look for a partiton with /KNOPPIX/ in the root, and the compressed image /KNOPPIX/KNOPPIX. Instead of using the sub-directory /mnt/hda1/knx/master/KNOPPIX/ as described above, it should be called /mnt/hda2/KNOPPIX/ . The root index.html will then be located at /mnt/hda2/index.html and the compressed image will be at /mnt/hda2/KNOPPIX/KNOPPIX . Now you can boot from floppy and use /mnt/hda2 as your image. For further information see [[Hd BasedHowTo]].

If you don't have an extra partition or you don't want to do so much for it, you can use Qemu ( see [http://fabrice.bellard.free.fr/qemu/] ) with the ISO image like this:
qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -net user
You even do not have to build a hard disk image before, just install Qemu and try this. Amazing!

==Test remastered version without creating cloop file/iso==
i use a setup similar to knoppix terminal server to test the remastered files without having to recreate a
cloop image every time: the remastered files live in an ext2 filesytem in a loopfile (knoppix_loop) mounted rw (this is where i chroot in). when i want to test the current setup, i have another machine network boot and use the files from the loopfile directly (needs another miniroot.gz). See [[User:Ml#dev_setup]]

If you want to use only one machine, you'll have to reboot (or use qemu) and use the "loopfile" and "fromhd" cheatcodes (see [[User:Ml#miniroot_changes]]). For example, this is what my grub boot entry looks like:

<pre>
title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz
</pre>

== Booting Knoppix images with GRUB==
* First copy /boot off the Knoppix cd to your boot partition (or even your dos partition). I named mine boot.knoppix
Copy the master/KNOPPIX directory to your root directory of any hard disk. You may place it somewhere other than the boot partition (ext2/3, reiserfs, vfat are supported).
* for Knoppix <= 3.3, put the following in your /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* for Knoppix >= 3.4 or other isolinux based distributions:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* notice the fromhd parameter: it's the location of the /KNOPPIX directory
* reboot and have fun.

==Helpful Scripts==
----
This is the recommended directory layout for remastering KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
the following script "remaster" will do the remaster process for you. Use as root, or you will end up with wrong access rights in the image.

The script has last been tried out on Debian sid on 2004-04-02.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
The following script will loop-mount boot floppy image and initrd image for modification. The umount function will build a new initrd image and put it back on the boot floppy image.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

==Tips around apt-get to install/update/remove applications==
(by gnarvaja)
* If you booted from CD, even on a HD install (example: Pivot Install) instead of copying the original CD and KNOPPIX directory to the HD, you can use them directly from their mount points.
* Another alternative is to mount an ISO image of the original CD as a loop device and mount the KNOPPIX image as a '''cloop''' device. You will save close to 2GB of space. Script to mount from an ISO image:

#!/bin/bash
# Assumes that the current directory is the working space
# original.iso is an image of the CD we will be using as master
mount -t iso9660 original.iso ./oldcd -o ro,loop
# initialize the compressed loop device
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop

* Get '''apt-spy''' and use it to modify the sources.list file with the best mirrors for your particular region. This will speed up the downloading. Backup the original '''sources.list''' just in case.
* Another technique is to modify '''sources.list'''. Replace the string '''.de.''' in the ftp addresses (ftp.de.debian.org) with the code corresponding to your country. Examples: USA -> .us. (ftp.us.debian.org), Brazil -> .br. (ftp.br.debian.org). Check the Debian site for debian.org mirrors in your country.
* Remember to uncomment the '''linuxtag''' ftp addresses to get the latest and greatest from Knoppix
* Use '''apt-get update''' to get the lists with the latest releases and patches. Do not update a package if you don't need to, it may lead to the use of additional disk space (precious commodity when you want to keep everything below 700MB) and you may brake something else without knowing. Abuse the '''-s''' option to simulate the installation.
* Before doing the update, I modified my default releases to '''testing''', that means that the software I'll be using will have a good balance of stability and features. Knoppix uses '''unstable''' by default, which is too risky for my personal taste.
* Get '''[apt-get install] locale''' and configure it with the locales you are going to use. It will save lots of space when downloading applications with plenty of locale modules and localized manual pages.
* I use '''aptitude''' to get/remove applications, it is character based so it works with init 2. As you mark packages for install/update/removal, it will tell you how much disk space you will save/use, try to solve depencies problems and give you plenty control to fix them manually when possible.
* When installing applications it is likely that your '''/etc/rc?.d''' directories will have new entries, many of them unwanted or unplanned. Make sure you check them and remove the new entries based on your preferences. I usually leave '''/etc/rc2.d''' and '''/etc/rc5.d''' as close as the originals as possible and modify '''/etc/rc3.d''' and '''/etc/rc4.d''' to test new stuff. '''Example:''' You may want to have ntfs installed, but not necessarily running by default. Same with apache, mysql and many others.
* When removing/purging applications, they may leave behind non-empty directories. Usually this is announced by aptitude, apt-get or any other installation utilty. Make sure to check the messages and manually remove those directories.
* After you are done, '''aptitude''' may leave some files behind. Here's a clean up script I use:

# !/bin/bash
# Clean package files generated by aptitude
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

=Common Problems=
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] Chroot problems accessing device files

* You've <code>startx</code>'d (into whatever window manager you like) and you start a terminal (gnome-terminal, konsole, xterm). Nothing happens (such is the case in fluxbox, and you'll see an error in you <code>~/.xsession-errors</code> file). Or perhaps the error is helpfully displayed: <code>
get_pty: not enough ptys
</code>
I had plenty yesterday... but then I <code>chroot</code>ed so, to solve this, <code>
# NOT in your chroot environment
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# enter your chroot environment
chroot /mnt/hda1/knx/source/KNOPPIX/

# and mount /dev/pts
mount -t devpts /dev/pts/ /dev/pts

</code>
it might give that same "fstab not found" error as mounting proc
does. so do what you'd do then, disregard.

start your X up again and try your terminal, should work.
thanks to: technovelty[http://www.technovelty.org/linux/tips/xinchroot.html] for the final enlightenment

=See also=

If my howto is too confusing, or you'd like a second opinion, check out charan's very nice remastering howto: http://brainstorms.in/?page_id=83
Another Howto is at http://www.stirnimann.com/mystuff/doc/knoppix.txt

There is a wizard, which knows all the unpacking, compressing and CD-recording steps mentioned here. It also shows a shell where you can update the uncompressed KNOPPIX system using debian's standard software installation tools. It is called mmkcdrom and part of the plugscript package: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Yet another HOWTO, for shell freaks, is at http://quozl.linux.org.au/knoppix/

Be sure to check out the [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] for ideas and help with remastering.

* If you want to add a custom kernel, check out the [[Knoppix Custom Kernel Howto]]
* There also a guide at O'Reilly on the same topic : [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

=Conclusion=
Thats it. This is an updated version of my previous howto. This is not meant for linux beginners, you will need to know your way around linux to get this to work. I'll update this as corrections/improvements/etc come through.

=Thanks=
Thanks to aay, charan, Tech2k, and #knoppix for some corrections and tips and ideas. Feel free to edit or add to this howto.
Note about swap: 

=Translations=
* German Version: [[Knoppix Remastering Howto Deutsch]]
* Spanish Version: [[Knoppix Remastering Howto Spanish]] en español
* French Version: [[Knoppix Remastering Howto French]]
* Indonesian Version: [[Knoppix Remastering Howto Indonesian]]
* Russian Version: [[Knoppix Remastering Howto Russian]]
* Brazilian Portuguese Version: [[Knoppix Remastering Howto Brazilian Portuguese]]
* Italian Version: [[Knoppix Remastering Howto Italiano]]

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto

2008-05-17T06:11:21Z

202.88.238.45: Undo revision 7799 by 202.88.238.45 (Talk)

This is a guide that will show you how to remaster KNOPPIX. (Note: commands should appear on one line, so please maximize the window. If you have any comments/suggestions please post below.)

You may wish to start from an already customized Knoppix, so you don't have to do as much work (such as removing programs). If so, see [[Knoppix Customizations]].

=System Requirements=
*CD-ISO
** at least 1 GB of FREE RAM+Swap total (e.g. 256M ram, and 750M swap AVAILABLE) (unless you use a different compression program - look in this page for compressloop)
** 3 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition
*DVD-ISO
** 5 GB free RAM + swap (for fullsized DVD)
** 15 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition

=Instructions=
==Setting up for Remastering==
# Boot from the ''Knoppix CD''
# Open a root shell:
#* Menu: Kmenu->Knoppix->Root Shell
#* Note: All commands below are run from this root shell.
# Configure your Internet connection (we'll need this later). If you use DHCP, it should already be configured.
#* Note: Run '''ifconfig''' to check.
# Find the partition you will use to work on. In this example it is called '''hda1''' . The partition should have a minimum of 3 GB free space
# Mount the partition:
#*<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Note: Make sure that it is read/write or you will get errors when you later chroot. To check: run '''mount'''
# Create a root directory to work in -- if you put all your files here it will be easy to clean up
#* <pre>mkdir /mnt/hda1/knx</pre>
# If you don't have 1 GB RAM ( '''egrep "(MemTotal|SwapTotal)" /proc/meminfo && echo "(physical+swap)"''' ) then you will need a swapfile:
#* <pre>cd /mnt/hda1/knx</pre>
#* <pre>dd if=/dev/zero of=swapfile bs=1M count=750</pre>
#* <pre>mkswap swapfile</pre>
#* <pre>swapon swapfile</pre>
# Make 2 directories, one for your new Master CD, one for the source, on a disk partition. Also, make additional directories under these named KNOPPIX:
#* <pre>mkdir -p /mnt/hda1/knx/master/KNOPPIX</pre>
#* <pre>mkdir -p /mnt/hda1/knx/source/KNOPPIX</pre>
# Now, copy the KNOPPIX files to your source directory :
#* <pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Note: This will take a long time (you are copying 2GB). Warning: you will be tempted to replace this copy command with a much faster procedure: create an empty directory, then use unionfs to merge the empty directory with /KNOPPIX in order to create the read-write copy. However, as of Knoppix 4.0.2, there is a bug in unionfs that causes this faster procedure to fail. For now, stick with the copy-command shown above.
# Additionally, copy the 'boot' folder from your cdrom - you'll need these files to build the ISO later.
#* <pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
# For Knoppix 5.0.1 you also have to copy the 'modules' folder:
#* <pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copy the main HTML page for the startup page:
#* <pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copy everything necessary files except the ~700 Mb KNOPPIX file.
#* < 3.4:
#** <pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* >= 3.4:
#** <pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* for the DVD Version you have to use -size -15000k and copy the KNOPPIX2 folder like this
#** <pre>cp -ar /KNOPPIX2/* /mnt/hda1/knx/source/KNOPPIX</pre>
# setup the environment for chroot
#* <pre>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev</pre>
#* <pre>mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</pre>
#* <pre>mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</pre>
# Now you can "chroot" into the copied KNOPPIX:
#* <pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# If you see errors regarding <tt>/dev/null</tt>, see the [[#Common Problems|common problems]] section
You are now chrooted. "/" is actually "/mnt/hda1/knx/source/KNOPPIX"

==Working in the Chroot Environment==
Remember that anything you do or create in the chrooted environment will get burned to the CD. If you make any changes (e.g,. to the APT configuration, proxy settings, etc.), make a note to back the changes out before remastering.
===Internet Access===
To use the Internet you need to edit <tt>/etc/resolv.conf</tt> to add your nameserver or exit the chroot and copy the outer <tt>resolv.conf</tt> into the chroot folder:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf
(proxies (a.k.a. doing it at work): you can type "export http_proxy=http://your.proxy.com:<port>") 
To check your chrooted internet connection,
ping google.com
(if ICMP is barred at some corporate firewall or something then try "lynx http://www.google.com" and see if you get the page -after a cookie "allow")

===SMB access===
Also change smb.conf to your MS group if you want smbd support (MSHOME is XP Home ed. usually, and WORKGROUP is 9x Windows)
===APT===
Update your package list with '''apt-get update'''.
<blockquote>Note: If ''''apt-get update''' fails with "FATAL -> Could not set non-blocking flag Bad file descriptor", you need to make sure your chrooted environment is mounted without the "nodev" option. (see above where it talks about the /dev/null errors when entering the chroot environment for the first time)</blockquote>
<blockquote>'''Warning''': apt-get upgrade is a ''BAD IDEA''. It will, quite probably, render your KNOPPIX remaster unbootable, or broken in some way. A far safer method is to only upgrade packages as necessary.</blockquote>

'''Note: If apt-get fails with "Dynamic NMap ran out of room" ''' you might try this little gem, which fixed the problem for me:
#echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf
(I did this while chrooted as described above.)

Before you can add stuff, you will probably need to remove some packages. To get a list of packages installed, type this:
dpkg-query -l
If you are looking for big installed packages then the command
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
will list the packages with size in descending order.

At least ten times faster is the command
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
and you don't need dpkg-awk or awk or perl; however it does not exclude packages that are not installed. If you have trouble with the above sort command, try using KPackage, expanded all the trees and sorted by the size column to find big packages.

Or, you could use this command to get the qpkg-query speed with the non-installed packages not listed:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
It does the same thing as above, I assume. I couldn't get the first one to work because I don't have dpkg-awk.

To remove a package (and all packages dependant on it), type this:
apt-get remove --purge ''name-of-package-to-remove''
To check for orphaned packages, type this:
deborphan
Want to save more space by getting rid of those pesky orphans (how cruel!), type this ('''Warning''', you won't be prompted yes/no to remove these packages. When you press Enter after this command, those packages ''will be gone''):
deborphan | xargs apt-get -y remove
If you're uncertain about the previous command and want to see what will happen without making any changes, just add the '''-s''' option to the apt-get command like this (you can do this with all of the apt-get commands, and it's a good habit to use this option before mass operations like this one):
deborphan | xargs apt-get -s -y remove
Now the good stuff. If you wish to add a package, type this:
apt-get install '''name-of-package-to-install''
What, don't know what packages to install? Type this. When the list appears, you can peruse (over 13k lines!) or search for things using <tt>/''search-term''</tt>:
apt-cache search .* | sort | less
When you're done removing and adding packages, a good way to clean up is by typing this
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Also, because the Debian package system keeps a cache of downloaded packages, you may want to run the following to clear out those spare files:
apt-get clean

===User Settings===
User settings are in /etc/skel. This directory will be copied to make new user home directories.
<blockquote>tip: don't put files in /root they will be only available (at runtime) in /KNOPPIX/root</blockquote>

Note that the default user 'knoppix' is not created by adduser(1), thus /etc/skel is not copied completely but rather selectively. That is, to make a file .xyrc appear in /home/knoppix, it is not sufficient to place it in /etc/skel. One possibility is to extend the code in /etc/X11/Xsession.d/45xsession which is responsible for filling /home/knoppix.

===Autorunning Programs===
When you want to autorun some programs, one can create a script and put it in the directory <tt>/etc/rc5.d/</tt> (This only loads items before X loads). Read up on the SysV init process for more possibilities.

''For X-programs consider <tt>/home/knoppix/.kde/Autostart</tt> but this may transfer form <tt>/etc/skel/.kde/Autostart</tt> on boot''--[[User:12.106.237.2|12.106.237.2]] 18:08, 7 December 2007 (UTC)

==Editing the KNOPPIX auto-configuration script==
You can find a lot of interesting information about how KNOPPIX auto-configures you system by looking in the /etc/init.d/knoppix-autoconfig script. Of particular note are the following.

===Changing the default KDE background image===
The auto-configuration script sets the default KDE background image to be an image from the CD-ROM. An image that you can easily change when you are remastering KNOPPIX.
** In KNOPPIX 3.3 and below it is /cdrom/KNOPPIX/background.gif
** In KNOPPIX 3.4 and above it is /cdrom/KNOPPIX/background.jpg

===Editing floppy and CD-ROM use or adding a custom script===
The auto-configuration script sets up both your CD-ROM and your floppy disk. The commands for doing this are 'floppyconfig' and 'cdromconfig', respectively. The auto-configuration script will also run cdrom/KNOPPIX/knoppix.sh, which is an easy script to change when remastering KNOPPIX.

===Changing the default boot parameters===
All boot parameters obtain default values from the /etc/init.d/knoppix-autoconfig script. This is one massive BASH script (you best know your BASH to play with this), but it is the place that you can edit any of the default boot parameters. For example, to switch from 'kde' to 'twm' as default desktop just search for the place where 'kde' is provided as default value (variable DESKTOP, IIRC). Another example would be changing the default language.

Note, if you are interested in changing the default language KDE uses, the easiest thing to do is to load KDE, instructions are below, and use the KDE configuration utility to select your language of interest.

==X Session Configuration==
When working with X-based programs you will have to make sure that your display is set appropriately. You can do this manually when remastering KNOPPIX. Also, two scripts related to X Session is where you can change or disable the startup and shutdown sounds.

===Starting X-based programs===
When testing X-based programs, you will have to
export DISPLAY=localhost:0.0
which will allow you to connect to your normal X session. Alternately (if you need to test window managers), you can create a nested X session. Outside of the chroot, run
Xnest -ac :1
Within the chroot, set your DISPLAY variable
export DISPLAY=localhost:1

Interesting stuff in /etc/init.d/xsession :
* it ALSO sets background as /usr/local/lib/knoppix.gif

===Modifying/Disabling the startup sound===
The startup sound is played by /etc/X11/Xsession.d/45xsession. You can disable it by commenting out the following lines.
<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

===Modifying/Disabling the shutdown sound===
The shutdown sound is played by /etc/init.d/xsession. You can disable it by commenting out lines 210-220 from the script.
<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

===Change default window manager===

Open /etc/init.d/knoppix-autoconfig and look for lines which look like these:
<pre><nowiki>
# Allow only supported windowmanagers
# Actually, this check is useless because it's done again in 45xsession. -KK
# case "$DESKTOP" in gnome|enlightenment|kde|larswm|xfce|xfce4|lg3d|ratpoison|blackbox|openbox|windowmaker|wmaker|icewm|fluxbox|twm|nx|rdp|kiosk) ;; *) DESKTOP="kde"; ;; esac
[ -n "$DESKTOP" ] || DESKTOP="kde"
</nowiki></pre>

Then, change "kde" in the last quoted line to whatever you like, for example to "fluxbox" or "twm".

==Changing the boot graphic, boot message, and startup script text==
While you are in the chroot environment you can easily change the boot messages, the boot graphic, and the default KDE background graphic.

===Changing the boot graphic===
The 'boot graphic' is the first image you see when the CD or DVD boots. It looks similar to ASCII art and it is normally something flashy that says 'Knoppix'. You can change this to be any graphic that you please, but you must use a 640x400 graphic that has only 16 colors.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old logo in case you break things.
#* <pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
#Make a 640x400 pixel 16 color graphic and save it as a GIF, e.g. 'logo.16.gif'. GIMP can easily do this. Note, you can use a graphic that originally had more than 16 colors, but it is critical that you convert the graphic to 16 colors before doing the next step.
#Convert the GIF to lss16 using the tools included on the Knoppix CD.
#* <pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm</nowiki></pre>
#* <pre><nowiki>ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

===Changing the boot message===
The 'boot message' is the message that you see under the 'boot graphic' on the initial screen when the Knoppix CD or DVD loads. It normally says something along the lines of Knoppix with the version number and includes a link to the Knoppix website. You can change this text to be whatever you please, but you shouldn't add too much text or it will make the boot screen look funny. Restricting yourself to a single line of text that is no larger than the default one is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old message in case you break things.
#* <pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
#Edit the message with a text editor. You'll see at the top of the message that it shows the graphic. Don't change this text, just the line under.
#* <pre><nowiki>vi boot.msg</nowiki></pre>

===Changing the startup script text===
The 'startup script text' is the text that you see after the initial boot screen, while Knoppix loads and configures your system. You can change as much of this text as you please. You can even add addition lines to the script; however, it is recommended that you don't play with this file. Limiting yourself to editing the 'Welcome to KNOPPIX' message is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old minirt.gz in case you break things.
#* <pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
#Uncompress minirt.gz
#* <pre><nowiki>gunzip minirt.gz</nowiki></pre>
#Make a temporary directory to mount the minirt filesystem.
#* <pre><nowiki>mkdir todelete</nowiki></pre>
#Mount the minirt filesystem as an ext2 filesystem.
#* <pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
#::or if the above does not work use
#* <pre><nowiki>mount minirt todelete -t ext2 -o loop</nowiki></pre>
#Edit the linuxrc script to display the message you want. You'll find the default message approximately 2 pages down and it'll be using several colors, i.e. ${WHITE}, ${RED}, etc., so it might be slightly tricky to spot.
#* <pre><nowiki>vi todelete/linuxrc</nowiki></pre>
#unmount the minirt filesystem.
#* <pre><nowiki>umount todelete</nowiki></pre>
#Compress the minirt filesystem.
#* <pre><nowiki>gzip -9 minirt</nowiki></pre>
#Remove your temporary directory.
#* <pre><nowiki>rmdir todelete</nowiki></pre>

==Launching KDE to Change Menus, Icons, etc.==
While you are in the chroot environment you can load KDE and use the configuration tools to change buttons, icons, etc. Once you are finished you can exit KDE and copy /home/knoppix to /etc/skel to keep these changes. To load KDE do the following.

#If you are not at runlevel 2 (i.e. if you are already in KDE), switch to runlevel 2.
#* <pre><nowiki>init 2</nowiki></pre>
#Copy /etc/skel to /home/knoppix
#* <pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
#Change permissions to the user 'knoppix'
#* <pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
#Copy over your X11 configuration to the chroot'd environment (press ctrl+alt+F2 to switch to a non-chroot'd terminal, then ctrl+alt+F1 to switch back when done)
#* <pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#*<blockquote>'' Knoppix 3.7: I think it's XF86Config-4 rather than xorg.conf.''</blockquote>
#(Optional)Switch to user 'knoppix'. If you want to uninstall packages, stay as root -- e.g. skip this step. If you want to configure the buttons, icons, background, etc., that you see when KDE boots, be sure to do this step.
#* <pre><nowiki>su knoppix</nowiki></pre>
##Launch KDE
##* <pre><nowiki>startx</nowiki></pre>
##Do your KDE changes
##Exit KDE
##Exit su and switch back to user 'root'.
##* <pre><nowiki>exit</nowiki></pre>
#Copy /home/knoppix back to /etc/skel to keep the changes
#* <pre><nowiki> mv /etc/skel /etc/skel-old</nowiki></pre>
#* <pre><nowiki>mv /home/knoppix /etc/skel</nowiki></pre>
#Set the owner back to root
#* <pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
#Remove the xorg.conf file
#* <pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>
#If you find that some of your settings are not persistent after booting the new image, check the initialization file at /etc/X11/Xsession.d/45xsession. By default, Knoppix does '''not''' simply copy over all files from /etc/skel. You may need to make modifications here if you wish to do something different.

===Changing the ksplash KDE graphics===
You can change the graphics that KDE shows via ksplash when it first loads. These graphics are in the /mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/ directory. You'll most likely want to swap out splash_top.png for a custom 400x248 PNG graphic. Note that ksplash will not automatically put a border around your graphic. If you'd like a border, you have to manually add it to your graphic.

==Leaving the Chroot==
If you mounted it, you'll need to unmount /proc - very important!
umount /proc
Press '''CTRL+D''' to leave being chrooted.

==Re-Entering the chroot==
If you've left the chroot, but you want to go back in and modify some things...

Remount the local hard disk (if needed)
<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
Setup the environment for chroot
<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc
mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</nowiki></pre>
Now you can "chroot" into the copied KNOPPIX:
<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>

==Remastering the ISO==
We've finished customizing and ready to burn!
First do some cleanup:
* remove any .bash_history files, tmp files, etc.
* back out any changes you don't want burned back to the disc
* make sure you umount /proc /dev /sys or mkisofs will not work properly
* <pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

===KNOPPIX Compressed Image===
Now we'll make the big <tt>KNOPPIX</tt> file which is an ISO 9660 filesystem compressed for use by the <tt>cloop</tt> driver:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
the "www.knoppix.net" and "Knoppix.net filesystem" can be changed to what you want to call the file. You will get an error that it doesn't conform to ISO standards -- you can ignore this. Note that, to run <tt>create_compressed_fs</tt>, you'll need to have enough space to store the entire ISO in RAM/swap. Ensure you have at least 800M of free space before starting.

In Knoppix 3.4 the <tt>create_compressed_fs</tt> script has been updated so be sure to use it to obtain the best result. It has a new option '''-b''' (best), which enables the best compression by using different compression schemes and tries to optimize that way, but be careful, because that option is slow (10x slower).

Note: The above didn't work for me using the latest create_compressed_fs. I could create the ISO but it couldn't read the compressed image properly when booting (I/O errors when reading the cloop0 device). I think this was because create_compressed_fs didn't have enough RAM and it was just failing silently. The command below did work though. It uses a file rather than memory for temporary storage:

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/hda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

------I tried this ,but it report a error,so i think there is some mistake in the command,it may be like follow,tell me if anyone confirm it-------
----------(by zhblue(newsclanATgmail.com))-------

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -b \
-f /mnt/hda1/isotemp -B 65536 - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

I noted several problems with the commands above: 
1) The option "-no-bak" excludes files with the ending ".bak". Non-backup files with this ending are found in some software packages, e.g. glest. It is safer not to use this option. 
2) Just calling "create_compressed_fs - 65536" gives a warning about old command syntax. The compatible parameters are "-m -B 65536". The later examples here already fixed this, the first example still uses the deprecated version.

===Live CD ISO===
If all went well, onto making the final CD-ROM Image:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(this will update the md5 hashes of the files included in the ISO, used for integrity checking) Now to burn the image; for Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
for Knoppix >= 3.4 or other isolinux based distributions:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(the ISO is stored in <tt>/mnt/hda1/knx/knoppix.iso</tt>)

Burn the ISO using your favorite tools, and you're ready!

==How to add new device driver to KNOPPIX==

Recently in a client project, I added the Digital Persona’s finger print driver to the Knoppix 5.1 distribution as an embedded solution to this project. This is a typical case where both the kernel level driver and the user level drivers and libraries are involved.

Most of the Knoppix books and online documentation have documented about how to keep a persistent storage of user configuration and user data. But those persistent configuration only saves the data in /home and /etc directories. If you have added kernel level drivers and/or other system libraries which are not in above two directories, you have to save the file images as a whole right after the boot. The saved file image can be big and may not what you want as a regular usage model. If you are building a customed Knoppix image for a long term solution, definitely you want to remaster the Knoppix to make the new drives be a permanent part of it.

The Digital Persona’s OneTouch SDK for their finger print scanner driver comes with a kernel level driver source code, plus a set of user level application libraries, as well as a sample test application. The SDK do not have a ready made binary for Debian or Knoppix. So I have to compile it from the source SDK. However, the CD version of Knoppix 5.1 do not even come with the source include header files to compile a kernel level driver. So I have to compile it under the DVD version of the Knoppix 5.1 and copy the compiled binary to the CD version of Knoppix 5.1 to do testing and remastering. The steps I have tried to make it work under Knoppix are as follows:

1. First compile the driver under DVD version of the Knoppix. Change the source code build scripts so that the include files and library path are matching what we have in Knoppix. The details are specific to the OneTouch SDK itself. If you are interested about this detail, write to me.

2. Install the just built kernel driver, the user libraries to their regular location as we will show in following step 4. And then build and run their sample applications per Digital Persona’s instruction. This proves that the basic kernel module build steps are built correctly and the user level libraries are working properly in a standard installation. This is important before we moved to chroot environment to make this changes permanent to our remastered Knoppix.

3. Then I followed the Knoppix remastering instructions documented in the book of “Live Linux CD” by Christoper Negus.

4. In the above remastering instructions, there is a step to update all the Debian packages and other software under the chroot environment. It is at this step that I re-run the drivers installation steps like I have done in above step 2 in the real root environment. In this particular case, it is make a directory and copy the kernel module file mod_usbdpfp.ko to that directory as follows:

mkdir /lib/modules/2.6.19/kernel/drivers/biometric
cp mod_usbdpfp.ko /lib/modules/2.6.19/mod_usbdpfp.ko

And also copy all those Digital Persona user level libraries to following location:

cp libdpfp* /usr/lib

5. I then run /sbin/depmod to let system detects the new kernel mode driver I have installed. This will refresh the /dev directory so it will have entries like:

/dev/usbdpfpPNP
/dev/usbdpfp0

At this time, if all works right, when you run command lsmod, you will also see something like:

mod_usbdpfp

shows up in the loaded module list

6. At this time, you are ready to make a remaster of the Knoppix. Next time when you boot up with this remastered Knoppix, it will have the kernel driver and user level libraries setup ready for you to run the sample applications. Just as if you have done above step 2 and step 4 right after a refresh reboot from the original Knoppix CD.

John Xu, USA. ( johnxu at n2k.net )

=Tips=
I have had good results remastering working from the CD as root working from fluxbox. Just say "knoppix 2" at the boot prompt and it will boot you to a root prompt where you can then say "startx /usr/bin/fluxbox". I like to use the xterm unicode shell.

==Package Management==
While working chroot doing the remastering I like to use
apt-get remove --purge pkg-name
to remove packages because before it does anything it will stop and show details on what it is fixing to remove and let you say "yes or no".

If you don't use the above "apt-get" instructions and have a lot to cleanup and purge, here's the easy way to do it:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
That will make a list of all removed packages to purge and then you just say
dpkg -P `< topurge `
and you're all done.
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
is a one-line version of this. Also use
deborphan | xargs dpkg -P .

==Alternatives for Low-Memory Machines==
You don't really need 1G swap as there are two new tools to create compressed filesystems. Here are some candidates to make ''compressed'' fs:
* Valentijn's rewrite [http://projects.openoffice.nl/downloads/compressloop/]
* Quozl's port of compressloop for Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Quozl's distributed compressloop (use more than one processor to speed things up) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Justin's patch [http://s.bouncybouncy.net/~justin/code/] (link broken) I also just wrote a distributed cloop compressor(or for smp) It's in that same directory.

==Test CD Image Without Burning a CD==
If you have a spare partition with at least 700MB free space formatted with ext2, ext3 or Vfat, you can use this for test by booting from a floppy disk. A floppy boot will look for a partiton with /KNOPPIX/ in the root, and the compressed image /KNOPPIX/KNOPPIX. Instead of using the sub-directory /mnt/hda1/knx/master/KNOPPIX/ as described above, it should be called /mnt/hda2/KNOPPIX/ . The root index.html will then be located at /mnt/hda2/index.html and the compressed image will be at /mnt/hda2/KNOPPIX/KNOPPIX . Now you can boot from floppy and use /mnt/hda2 as your image. For further information see [[Hd BasedHowTo]].

If you don't have an extra partition or you don't want to do so much for it, you can use Qemu ( see [http://fabrice.bellard.free.fr/qemu/] ) with the ISO image like this:
qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -net user
You even do not have to build a hard disk image before, just install Qemu and try this. Amazing!

==Test remastered version without creating cloop file/iso==
i use a setup similar to knoppix terminal server to test the remastered files without having to recreate a
cloop image every time: the remastered files live in an ext2 filesytem in a loopfile (knoppix_loop) mounted rw (this is where i chroot in). when i want to test the current setup, i have another machine network boot and use the files from the loopfile directly (needs another miniroot.gz). See [[User:Ml#dev_setup]]

If you want to use only one machine, you'll have to reboot (or use qemu) and use the "loopfile" and "fromhd" cheatcodes (see [[User:Ml#miniroot_changes]]). For example, this is what my grub boot entry looks like:

<pre>
title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz
</pre>

== Booting Knoppix images with GRUB==
* First copy /boot off the Knoppix cd to your boot partition (or even your dos partition). I named mine boot.knoppix
Copy the master/KNOPPIX directory to your root directory of any hard disk. You may place it somewhere other than the boot partition (ext2/3, reiserfs, vfat are supported).
* for Knoppix <= 3.3, put the following in your /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* for Knoppix >= 3.4 or other isolinux based distributions:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* notice the fromhd parameter: it's the location of the /KNOPPIX directory
* reboot and have fun.

==Helpful Scripts==
----
This is the recommended directory layout for remastering KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
the following script "remaster" will do the remaster process for you. Use as root, or you will end up with wrong access rights in the image.

The script has last been tried out on Debian sid on 2004-04-02.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
The following script will loop-mount boot floppy image and initrd image for modification. The umount function will build a new initrd image and put it back on the boot floppy image.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

==Tips around apt-get to install/update/remove applications==
(by gnarvaja)
* If you booted from CD, even on a HD install (example: Pivot Install) instead of copying the original CD and KNOPPIX directory to the HD, you can use them directly from their mount points.
* Another alternative is to mount an ISO image of the original CD as a loop device and mount the KNOPPIX image as a '''cloop''' device. You will save close to 2GB of space. Script to mount from an ISO image:

#!/bin/bash
# Assumes that the current directory is the working space
# original.iso is an image of the CD we will be using as master
mount -t iso9660 original.iso ./oldcd -o ro,loop
# initialize the compressed loop device
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop

* Get '''apt-spy''' and use it to modify the sources.list file with the best mirrors for your particular region. This will speed up the downloading. Backup the original '''sources.list''' just in case.
* Another technique is to modify '''sources.list'''. Replace the string '''.de.''' in the ftp addresses (ftp.de.debian.org) with the code corresponding to your country. Examples: USA -> .us. (ftp.us.debian.org), Brazil -> .br. (ftp.br.debian.org). Check the Debian site for debian.org mirrors in your country.
* Remember to uncomment the '''linuxtag''' ftp addresses to get the latest and greatest from Knoppix
* Use '''apt-get update''' to get the lists with the latest releases and patches. Do not update a package if you don't need to, it may lead to the use of additional disk space (precious commodity when you want to keep everything below 700MB) and you may brake something else without knowing. Abuse the '''-s''' option to simulate the installation.
* Before doing the update, I modified my default releases to '''testing''', that means that the software I'll be using will have a good balance of stability and features. Knoppix uses '''unstable''' by default, which is too risky for my personal taste.
* Get '''[apt-get install] locale''' and configure it with the locales you are going to use. It will save lots of space when downloading applications with plenty of locale modules and localized manual pages.
* I use '''aptitude''' to get/remove applications, it is character based so it works with init 2. As you mark packages for install/update/removal, it will tell you how much disk space you will save/use, try to solve depencies problems and give you plenty control to fix them manually when possible.
* When installing applications it is likely that your '''/etc/rc?.d''' directories will have new entries, many of them unwanted or unplanned. Make sure you check them and remove the new entries based on your preferences. I usually leave '''/etc/rc2.d''' and '''/etc/rc5.d''' as close as the originals as possible and modify '''/etc/rc3.d''' and '''/etc/rc4.d''' to test new stuff. '''Example:''' You may want to have ntfs installed, but not necessarily running by default. Same with apache, mysql and many others.
* When removing/purging applications, they may leave behind non-empty directories. Usually this is announced by aptitude, apt-get or any other installation utilty. Make sure to check the messages and manually remove those directories.
* After you are done, '''aptitude''' may leave some files behind. Here's a clean up script I use:

# !/bin/bash
# Clean package files generated by aptitude
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

=Common Problems=
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] Chroot problems accessing device files

* You've <code>startx</code>'d (into whatever window manager you like) and you start a terminal (gnome-terminal, konsole, xterm). Nothing happens (such is the case in fluxbox, and you'll see an error in you <code>~/.xsession-errors</code> file). Or perhaps the error is helpfully displayed: <code>
get_pty: not enough ptys
</code>
I had plenty yesterday... but then I <code>chroot</code>ed so, to solve this, <code>
# NOT in your chroot environment
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# enter your chroot environment
chroot /mnt/hda1/knx/source/KNOPPIX/

# and mount /dev/pts
mount -t devpts /dev/pts/ /dev/pts

</code>
it might give that same "fstab not found" error as mounting proc
does. so do what you'd do then, disregard.

start your X up again and try your terminal, should work.
thanks to: technovelty[http://www.technovelty.org/linux/tips/xinchroot.html] for the final enlightenment

=See also=

If my howto is too confusing, or you'd like a second opinion, check out charan's very nice remastering howto: http://brainstorms.in/knoppix
Another Howto is at http://www.stirnimann.com/mystuff/doc/knoppix.txt

There is a wizard, which knows all the unpacking, compressing and CD-recording steps mentioned here. It also shows a shell where you can update the uncompressed KNOPPIX system using debian's standard software installation tools. It is called mmkcdrom and part of the plugscript package: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Yet another HOWTO, for shell freaks, is at http://quozl.linux.org.au/knoppix/

Be sure to check out the [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] for ideas and help with remastering.

* If you want to add a custom kernel, check out the [[Knoppix Custom Kernel Howto]]
* There also a guide at O'Reilly on the same topic : [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

=Conclusion=
Thats it. This is an updated version of my previous howto. This is not meant for linux beginners, you will need to know your way around linux to get this to work. I'll update this as corrections/improvements/etc come through.

=Thanks=
Thanks to aay, charan, Tech2k, and #knoppix for some corrections and tips and ideas. Feel free to edit or add to this howto.
Note about swap: 

=Translations=
* German Version: [[Knoppix Remastering Howto Deutsch]]
* Spanish Version: [[Knoppix Remastering Howto Spanish]] en español
* French Version: [[Knoppix Remastering Howto French]]
* Indonesian Version: [[Knoppix Remastering Howto Indonesian]]
* Russian Version: [[Knoppix Remastering Howto Russian]]
* Brazilian Portuguese Version: [[Knoppix Remastering Howto Brazilian Portuguese]]
* Italian Version: [[Knoppix Remastering Howto Italiano]]

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto

2008-05-17T06:08:06Z

202.88.238.45: /* Thanks */

This is a guide that will show you how to remaster KNOPPIX. (Note: commands should appear on one line, so please maximize the window. If you have any comments/suggestions please post below.)

You may wish to start from an already customized Knoppix, so you don't have to do as much work (such as removing programs). If so, see [[Knoppix Customizations]].

=System Requirements=
*CD-ISO
** at least 1 GB of FREE RAM+Swap total (e.g. 256M ram, and 750M swap AVAILABLE) (unless you use a different compression program - look in this page for compressloop)
** 3 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition
*DVD-ISO
** 5 GB free RAM + swap (for fullsized DVD)
** 15 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition

=Instructions=
==Setting up for Remastering==
# Boot from the ''Knoppix CD''
# Open a root shell:
#* Menu: Kmenu->Knoppix->Root Shell
#* Note: All commands below are run from this root shell.
# Configure your Internet connection (we'll need this later). If you use DHCP, it should already be configured.
#* Note: Run '''ifconfig''' to check.
# Find the partition you will use to work on. In this example it is called '''hda1''' . The partition should have a minimum of 3 GB free space
# Mount the partition:
#*<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Note: Make sure that it is read/write or you will get errors when you later chroot. To check: run '''mount'''
# Create a root directory to work in -- if you put all your files here it will be easy to clean up
#* <pre>mkdir /mnt/hda1/knx</pre>
# If you don't have 1 GB RAM ( '''egrep "(MemTotal|SwapTotal)" /proc/meminfo && echo "(physical+swap)"''' ) then you will need a swapfile:
#* <pre>cd /mnt/hda1/knx</pre>
#* <pre>dd if=/dev/zero of=swapfile bs=1M count=750</pre>
#* <pre>mkswap swapfile</pre>
#* <pre>swapon swapfile</pre>
# Make 2 directories, one for your new Master CD, one for the source, on a disk partition. Also, make additional directories under these named KNOPPIX:
#* <pre>mkdir -p /mnt/hda1/knx/master/KNOPPIX</pre>
#* <pre>mkdir -p /mnt/hda1/knx/source/KNOPPIX</pre>
# Now, copy the KNOPPIX files to your source directory :
#* <pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Note: This will take a long time (you are copying 2GB). Warning: you will be tempted to replace this copy command with a much faster procedure: create an empty directory, then use unionfs to merge the empty directory with /KNOPPIX in order to create the read-write copy. However, as of Knoppix 4.0.2, there is a bug in unionfs that causes this faster procedure to fail. For now, stick with the copy-command shown above.
# Additionally, copy the 'boot' folder from your cdrom - you'll need these files to build the ISO later.
#* <pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
# For Knoppix 5.0.1 you also have to copy the 'modules' folder:
#* <pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copy the main HTML page for the startup page:
#* <pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copy everything necessary files except the ~700 Mb KNOPPIX file.
#* < 3.4:
#** <pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* >= 3.4:
#** <pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* for the DVD Version you have to use -size -15000k and copy the KNOPPIX2 folder like this
#** <pre>cp -ar /KNOPPIX2/* /mnt/hda1/knx/source/KNOPPIX</pre>
# setup the environment for chroot
#* <pre>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev</pre>
#* <pre>mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</pre>
#* <pre>mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</pre>
# Now you can "chroot" into the copied KNOPPIX:
#* <pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# If you see errors regarding <tt>/dev/null</tt>, see the [[#Common Problems|common problems]] section
You are now chrooted. "/" is actually "/mnt/hda1/knx/source/KNOPPIX"

==Working in the Chroot Environment==
Remember that anything you do or create in the chrooted environment will get burned to the CD. If you make any changes (e.g,. to the APT configuration, proxy settings, etc.), make a note to back the changes out before remastering.
===Internet Access===
To use the Internet you need to edit <tt>/etc/resolv.conf</tt> to add your nameserver or exit the chroot and copy the outer <tt>resolv.conf</tt> into the chroot folder:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf
(proxies (a.k.a. doing it at work): you can type "export http_proxy=http://your.proxy.com:<port>") 
To check your chrooted internet connection,
ping google.com
(if ICMP is barred at some corporate firewall or something then try "lynx http://www.google.com" and see if you get the page -after a cookie "allow")

===SMB access===
Also change smb.conf to your MS group if you want smbd support (MSHOME is XP Home ed. usually, and WORKGROUP is 9x Windows)
===APT===
Update your package list with '''apt-get update'''.
<blockquote>Note: If ''''apt-get update''' fails with "FATAL -> Could not set non-blocking flag Bad file descriptor", you need to make sure your chrooted environment is mounted without the "nodev" option. (see above where it talks about the /dev/null errors when entering the chroot environment for the first time)</blockquote>
<blockquote>'''Warning''': apt-get upgrade is a ''BAD IDEA''. It will, quite probably, render your KNOPPIX remaster unbootable, or broken in some way. A far safer method is to only upgrade packages as necessary.</blockquote>

'''Note: If apt-get fails with "Dynamic NMap ran out of room" ''' you might try this little gem, which fixed the problem for me:
#echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf
(I did this while chrooted as described above.)

Before you can add stuff, you will probably need to remove some packages. To get a list of packages installed, type this:
dpkg-query -l
If you are looking for big installed packages then the command
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
will list the packages with size in descending order.

At least ten times faster is the command
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
and you don't need dpkg-awk or awk or perl; however it does not exclude packages that are not installed. If you have trouble with the above sort command, try using KPackage, expanded all the trees and sorted by the size column to find big packages.

Or, you could use this command to get the qpkg-query speed with the non-installed packages not listed:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
It does the same thing as above, I assume. I couldn't get the first one to work because I don't have dpkg-awk.

To remove a package (and all packages dependant on it), type this:
apt-get remove --purge ''name-of-package-to-remove''
To check for orphaned packages, type this:
deborphan
Want to save more space by getting rid of those pesky orphans (how cruel!), type this ('''Warning''', you won't be prompted yes/no to remove these packages. When you press Enter after this command, those packages ''will be gone''):
deborphan | xargs apt-get -y remove
If you're uncertain about the previous command and want to see what will happen without making any changes, just add the '''-s''' option to the apt-get command like this (you can do this with all of the apt-get commands, and it's a good habit to use this option before mass operations like this one):
deborphan | xargs apt-get -s -y remove
Now the good stuff. If you wish to add a package, type this:
apt-get install '''name-of-package-to-install''
What, don't know what packages to install? Type this. When the list appears, you can peruse (over 13k lines!) or search for things using <tt>/''search-term''</tt>:
apt-cache search .* | sort | less
When you're done removing and adding packages, a good way to clean up is by typing this
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Also, because the Debian package system keeps a cache of downloaded packages, you may want to run the following to clear out those spare files:
apt-get clean

===User Settings===
User settings are in /etc/skel. This directory will be copied to make new user home directories.
<blockquote>tip: don't put files in /root they will be only available (at runtime) in /KNOPPIX/root</blockquote>

Note that the default user 'knoppix' is not created by adduser(1), thus /etc/skel is not copied completely but rather selectively. That is, to make a file .xyrc appear in /home/knoppix, it is not sufficient to place it in /etc/skel. One possibility is to extend the code in /etc/X11/Xsession.d/45xsession which is responsible for filling /home/knoppix.

===Autorunning Programs===
When you want to autorun some programs, one can create a script and put it in the directory <tt>/etc/rc5.d/</tt> (This only loads items before X loads). Read up on the SysV init process for more possibilities.

''For X-programs consider <tt>/home/knoppix/.kde/Autostart</tt> but this may transfer form <tt>/etc/skel/.kde/Autostart</tt> on boot''--[[User:12.106.237.2|12.106.237.2]] 18:08, 7 December 2007 (UTC)

==Editing the KNOPPIX auto-configuration script==
You can find a lot of interesting information about how KNOPPIX auto-configures you system by looking in the /etc/init.d/knoppix-autoconfig script. Of particular note are the following.

===Changing the default KDE background image===
The auto-configuration script sets the default KDE background image to be an image from the CD-ROM. An image that you can easily change when you are remastering KNOPPIX.
** In KNOPPIX 3.3 and below it is /cdrom/KNOPPIX/background.gif
** In KNOPPIX 3.4 and above it is /cdrom/KNOPPIX/background.jpg

===Editing floppy and CD-ROM use or adding a custom script===
The auto-configuration script sets up both your CD-ROM and your floppy disk. The commands for doing this are 'floppyconfig' and 'cdromconfig', respectively. The auto-configuration script will also run cdrom/KNOPPIX/knoppix.sh, which is an easy script to change when remastering KNOPPIX.

===Changing the default boot parameters===
All boot parameters obtain default values from the /etc/init.d/knoppix-autoconfig script. This is one massive BASH script (you best know your BASH to play with this), but it is the place that you can edit any of the default boot parameters. For example, to switch from 'kde' to 'twm' as default desktop just search for the place where 'kde' is provided as default value (variable DESKTOP, IIRC). Another example would be changing the default language.

Note, if you are interested in changing the default language KDE uses, the easiest thing to do is to load KDE, instructions are below, and use the KDE configuration utility to select your language of interest.

==X Session Configuration==
When working with X-based programs you will have to make sure that your display is set appropriately. You can do this manually when remastering KNOPPIX. Also, two scripts related to X Session is where you can change or disable the startup and shutdown sounds.

===Starting X-based programs===
When testing X-based programs, you will have to
export DISPLAY=localhost:0.0
which will allow you to connect to your normal X session. Alternately (if you need to test window managers), you can create a nested X session. Outside of the chroot, run
Xnest -ac :1
Within the chroot, set your DISPLAY variable
export DISPLAY=localhost:1

Interesting stuff in /etc/init.d/xsession :
* it ALSO sets background as /usr/local/lib/knoppix.gif

===Modifying/Disabling the startup sound===
The startup sound is played by /etc/X11/Xsession.d/45xsession. You can disable it by commenting out the following lines.
<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

===Modifying/Disabling the shutdown sound===
The shutdown sound is played by /etc/init.d/xsession. You can disable it by commenting out lines 210-220 from the script.
<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

===Change default window manager===

Open /etc/init.d/knoppix-autoconfig and look for lines which look like these:
<pre><nowiki>
# Allow only supported windowmanagers
# Actually, this check is useless because it's done again in 45xsession. -KK
# case "$DESKTOP" in gnome|enlightenment|kde|larswm|xfce|xfce4|lg3d|ratpoison|blackbox|openbox|windowmaker|wmaker|icewm|fluxbox|twm|nx|rdp|kiosk) ;; *) DESKTOP="kde"; ;; esac
[ -n "$DESKTOP" ] || DESKTOP="kde"
</nowiki></pre>

Then, change "kde" in the last quoted line to whatever you like, for example to "fluxbox" or "twm".

==Changing the boot graphic, boot message, and startup script text==
While you are in the chroot environment you can easily change the boot messages, the boot graphic, and the default KDE background graphic.

===Changing the boot graphic===
The 'boot graphic' is the first image you see when the CD or DVD boots. It looks similar to ASCII art and it is normally something flashy that says 'Knoppix'. You can change this to be any graphic that you please, but you must use a 640x400 graphic that has only 16 colors.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old logo in case you break things.
#* <pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
#Make a 640x400 pixel 16 color graphic and save it as a GIF, e.g. 'logo.16.gif'. GIMP can easily do this. Note, you can use a graphic that originally had more than 16 colors, but it is critical that you convert the graphic to 16 colors before doing the next step.
#Convert the GIF to lss16 using the tools included on the Knoppix CD.
#* <pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm</nowiki></pre>
#* <pre><nowiki>ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

===Changing the boot message===
The 'boot message' is the message that you see under the 'boot graphic' on the initial screen when the Knoppix CD or DVD loads. It normally says something along the lines of Knoppix with the version number and includes a link to the Knoppix website. You can change this text to be whatever you please, but you shouldn't add too much text or it will make the boot screen look funny. Restricting yourself to a single line of text that is no larger than the default one is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old message in case you break things.
#* <pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
#Edit the message with a text editor. You'll see at the top of the message that it shows the graphic. Don't change this text, just the line under.
#* <pre><nowiki>vi boot.msg</nowiki></pre>

===Changing the startup script text===
The 'startup script text' is the text that you see after the initial boot screen, while Knoppix loads and configures your system. You can change as much of this text as you please. You can even add addition lines to the script; however, it is recommended that you don't play with this file. Limiting yourself to editing the 'Welcome to KNOPPIX' message is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old minirt.gz in case you break things.
#* <pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
#Uncompress minirt.gz
#* <pre><nowiki>gunzip minirt.gz</nowiki></pre>
#Make a temporary directory to mount the minirt filesystem.
#* <pre><nowiki>mkdir todelete</nowiki></pre>
#Mount the minirt filesystem as an ext2 filesystem.
#* <pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
#::or if the above does not work use
#* <pre><nowiki>mount minirt todelete -t ext2 -o loop</nowiki></pre>
#Edit the linuxrc script to display the message you want. You'll find the default message approximately 2 pages down and it'll be using several colors, i.e. ${WHITE}, ${RED}, etc., so it might be slightly tricky to spot.
#* <pre><nowiki>vi todelete/linuxrc</nowiki></pre>
#unmount the minirt filesystem.
#* <pre><nowiki>umount todelete</nowiki></pre>
#Compress the minirt filesystem.
#* <pre><nowiki>gzip -9 minirt</nowiki></pre>
#Remove your temporary directory.
#* <pre><nowiki>rmdir todelete</nowiki></pre>

==Launching KDE to Change Menus, Icons, etc.==
While you are in the chroot environment you can load KDE and use the configuration tools to change buttons, icons, etc. Once you are finished you can exit KDE and copy /home/knoppix to /etc/skel to keep these changes. To load KDE do the following.

#If you are not at runlevel 2 (i.e. if you are already in KDE), switch to runlevel 2.
#* <pre><nowiki>init 2</nowiki></pre>
#Copy /etc/skel to /home/knoppix
#* <pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
#Change permissions to the user 'knoppix'
#* <pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
#Copy over your X11 configuration to the chroot'd environment (press ctrl+alt+F2 to switch to a non-chroot'd terminal, then ctrl+alt+F1 to switch back when done)
#* <pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#*<blockquote>'' Knoppix 3.7: I think it's XF86Config-4 rather than xorg.conf.''</blockquote>
#(Optional)Switch to user 'knoppix'. If you want to uninstall packages, stay as root -- e.g. skip this step. If you want to configure the buttons, icons, background, etc., that you see when KDE boots, be sure to do this step.
#* <pre><nowiki>su knoppix</nowiki></pre>
##Launch KDE
##* <pre><nowiki>startx</nowiki></pre>
##Do your KDE changes
##Exit KDE
##Exit su and switch back to user 'root'.
##* <pre><nowiki>exit</nowiki></pre>
#Copy /home/knoppix back to /etc/skel to keep the changes
#* <pre><nowiki> mv /etc/skel /etc/skel-old</nowiki></pre>
#* <pre><nowiki>mv /home/knoppix /etc/skel</nowiki></pre>
#Set the owner back to root
#* <pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
#Remove the xorg.conf file
#* <pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>
#If you find that some of your settings are not persistent after booting the new image, check the initialization file at /etc/X11/Xsession.d/45xsession. By default, Knoppix does '''not''' simply copy over all files from /etc/skel. You may need to make modifications here if you wish to do something different.

===Changing the ksplash KDE graphics===
You can change the graphics that KDE shows via ksplash when it first loads. These graphics are in the /mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/ directory. You'll most likely want to swap out splash_top.png for a custom 400x248 PNG graphic. Note that ksplash will not automatically put a border around your graphic. If you'd like a border, you have to manually add it to your graphic.

==Leaving the Chroot==
If you mounted it, you'll need to unmount /proc - very important!
umount /proc
Press '''CTRL+D''' to leave being chrooted.

==Re-Entering the chroot==
If you've left the chroot, but you want to go back in and modify some things...

Remount the local hard disk (if needed)
<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
Setup the environment for chroot
<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc
mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</nowiki></pre>
Now you can "chroot" into the copied KNOPPIX:
<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>

==Remastering the ISO==
We've finished customizing and ready to burn!
First do some cleanup:
* remove any .bash_history files, tmp files, etc.
* back out any changes you don't want burned back to the disc
* make sure you umount /proc /dev /sys or mkisofs will not work properly
* <pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

===KNOPPIX Compressed Image===
Now we'll make the big <tt>KNOPPIX</tt> file which is an ISO 9660 filesystem compressed for use by the <tt>cloop</tt> driver:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
the "www.knoppix.net" and "Knoppix.net filesystem" can be changed to what you want to call the file. You will get an error that it doesn't conform to ISO standards -- you can ignore this. Note that, to run <tt>create_compressed_fs</tt>, you'll need to have enough space to store the entire ISO in RAM/swap. Ensure you have at least 800M of free space before starting.

In Knoppix 3.4 the <tt>create_compressed_fs</tt> script has been updated so be sure to use it to obtain the best result. It has a new option '''-b''' (best), which enables the best compression by using different compression schemes and tries to optimize that way, but be careful, because that option is slow (10x slower).

Note: The above didn't work for me using the latest create_compressed_fs. I could create the ISO but it couldn't read the compressed image properly when booting (I/O errors when reading the cloop0 device). I think this was because create_compressed_fs didn't have enough RAM and it was just failing silently. The command below did work though. It uses a file rather than memory for temporary storage:

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/hda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

------I tried this ,but it report a error,so i think there is some mistake in the command,it may be like follow,tell me if anyone confirm it-------
----------(by zhblue(newsclanATgmail.com))-------

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -b \
-f /mnt/hda1/isotemp -B 65536 - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

I noted several problems with the commands above: 
1) The option "-no-bak" excludes files with the ending ".bak". Non-backup files with this ending are found in some software packages, e.g. glest. It is safer not to use this option. 
2) Just calling "create_compressed_fs - 65536" gives a warning about old command syntax. The compatible parameters are "-m -B 65536". The later examples here already fixed this, the first example still uses the deprecated version.

===Live CD ISO===
If all went well, onto making the final CD-ROM Image:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(this will update the md5 hashes of the files included in the ISO, used for integrity checking) Now to burn the image; for Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
for Knoppix >= 3.4 or other isolinux based distributions:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(the ISO is stored in <tt>/mnt/hda1/knx/knoppix.iso</tt>)

Burn the ISO using your favorite tools, and you're ready!

==How to add new device driver to KNOPPIX==

Recently in a client project, I added the Digital Persona’s finger print driver to the Knoppix 5.1 distribution as an embedded solution to this project. This is a typical case where both the kernel level driver and the user level drivers and libraries are involved.

Most of the Knoppix books and online documentation have documented about how to keep a persistent storage of user configuration and user data. But those persistent configuration only saves the data in /home and /etc directories. If you have added kernel level drivers and/or other system libraries which are not in above two directories, you have to save the file images as a whole right after the boot. The saved file image can be big and may not what you want as a regular usage model. If you are building a customed Knoppix image for a long term solution, definitely you want to remaster the Knoppix to make the new drives be a permanent part of it.

The Digital Persona’s OneTouch SDK for their finger print scanner driver comes with a kernel level driver source code, plus a set of user level application libraries, as well as a sample test application. The SDK do not have a ready made binary for Debian or Knoppix. So I have to compile it from the source SDK. However, the CD version of Knoppix 5.1 do not even come with the source include header files to compile a kernel level driver. So I have to compile it under the DVD version of the Knoppix 5.1 and copy the compiled binary to the CD version of Knoppix 5.1 to do testing and remastering. The steps I have tried to make it work under Knoppix are as follows:

1. First compile the driver under DVD version of the Knoppix. Change the source code build scripts so that the include files and library path are matching what we have in Knoppix. The details are specific to the OneTouch SDK itself. If you are interested about this detail, write to me.

2. Install the just built kernel driver, the user libraries to their regular location as we will show in following step 4. And then build and run their sample applications per Digital Persona’s instruction. This proves that the basic kernel module build steps are built correctly and the user level libraries are working properly in a standard installation. This is important before we moved to chroot environment to make this changes permanent to our remastered Knoppix.

3. Then I followed the Knoppix remastering instructions documented in the book of “Live Linux CD” by Christoper Negus.

4. In the above remastering instructions, there is a step to update all the Debian packages and other software under the chroot environment. It is at this step that I re-run the drivers installation steps like I have done in above step 2 in the real root environment. In this particular case, it is make a directory and copy the kernel module file mod_usbdpfp.ko to that directory as follows:

mkdir /lib/modules/2.6.19/kernel/drivers/biometric
cp mod_usbdpfp.ko /lib/modules/2.6.19/mod_usbdpfp.ko

And also copy all those Digital Persona user level libraries to following location:

cp libdpfp* /usr/lib

5. I then run /sbin/depmod to let system detects the new kernel mode driver I have installed. This will refresh the /dev directory so it will have entries like:

/dev/usbdpfpPNP
/dev/usbdpfp0

At this time, if all works right, when you run command lsmod, you will also see something like:

mod_usbdpfp

shows up in the loaded module list

6. At this time, you are ready to make a remaster of the Knoppix. Next time when you boot up with this remastered Knoppix, it will have the kernel driver and user level libraries setup ready for you to run the sample applications. Just as if you have done above step 2 and step 4 right after a refresh reboot from the original Knoppix CD.

John Xu, USA. ( johnxu at n2k.net )

=Tips=
I have had good results remastering working from the CD as root working from fluxbox. Just say "knoppix 2" at the boot prompt and it will boot you to a root prompt where you can then say "startx /usr/bin/fluxbox". I like to use the xterm unicode shell.

==Package Management==
While working chroot doing the remastering I like to use
apt-get remove --purge pkg-name
to remove packages because before it does anything it will stop and show details on what it is fixing to remove and let you say "yes or no".

If you don't use the above "apt-get" instructions and have a lot to cleanup and purge, here's the easy way to do it:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
That will make a list of all removed packages to purge and then you just say
dpkg -P `< topurge `
and you're all done.
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
is a one-line version of this. Also use
deborphan | xargs dpkg -P .

==Alternatives for Low-Memory Machines==
You don't really need 1G swap as there are two new tools to create compressed filesystems. Here are some candidates to make ''compressed'' fs:
* Valentijn's rewrite [http://projects.openoffice.nl/downloads/compressloop/]
* Quozl's port of compressloop for Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Quozl's distributed compressloop (use more than one processor to speed things up) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Justin's patch [http://s.bouncybouncy.net/~justin/code/] (link broken) I also just wrote a distributed cloop compressor(or for smp) It's in that same directory.

==Test CD Image Without Burning a CD==
If you have a spare partition with at least 700MB free space formatted with ext2, ext3 or Vfat, you can use this for test by booting from a floppy disk. A floppy boot will look for a partiton with /KNOPPIX/ in the root, and the compressed image /KNOPPIX/KNOPPIX. Instead of using the sub-directory /mnt/hda1/knx/master/KNOPPIX/ as described above, it should be called /mnt/hda2/KNOPPIX/ . The root index.html will then be located at /mnt/hda2/index.html and the compressed image will be at /mnt/hda2/KNOPPIX/KNOPPIX . Now you can boot from floppy and use /mnt/hda2 as your image. For further information see [[Hd BasedHowTo]].

If you don't have an extra partition or you don't want to do so much for it, you can use Qemu ( see [http://fabrice.bellard.free.fr/qemu/] ) with the ISO image like this:
qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -net user
You even do not have to build a hard disk image before, just install Qemu and try this. Amazing!

==Test remastered version without creating cloop file/iso==
i use a setup similar to knoppix terminal server to test the remastered files without having to recreate a
cloop image every time: the remastered files live in an ext2 filesytem in a loopfile (knoppix_loop) mounted rw (this is where i chroot in). when i want to test the current setup, i have another machine network boot and use the files from the loopfile directly (needs another miniroot.gz). See [[User:Ml#dev_setup]]

If you want to use only one machine, you'll have to reboot (or use qemu) and use the "loopfile" and "fromhd" cheatcodes (see [[User:Ml#miniroot_changes]]). For example, this is what my grub boot entry looks like:

<pre>
title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz
</pre>

== Booting Knoppix images with GRUB==
* First copy /boot off the Knoppix cd to your boot partition (or even your dos partition). I named mine boot.knoppix
Copy the master/KNOPPIX directory to your root directory of any hard disk. You may place it somewhere other than the boot partition (ext2/3, reiserfs, vfat are supported).
* for Knoppix <= 3.3, put the following in your /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* for Knoppix >= 3.4 or other isolinux based distributions:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* notice the fromhd parameter: it's the location of the /KNOPPIX directory
* reboot and have fun.

==Helpful Scripts==
----
This is the recommended directory layout for remastering KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
the following script "remaster" will do the remaster process for you. Use as root, or you will end up with wrong access rights in the image.

The script has last been tried out on Debian sid on 2004-04-02.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
The following script will loop-mount boot floppy image and initrd image for modification. The umount function will build a new initrd image and put it back on the boot floppy image.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

==Tips around apt-get to install/update/remove applications==
(by gnarvaja)
* If you booted from CD, even on a HD install (example: Pivot Install) instead of copying the original CD and KNOPPIX directory to the HD, you can use them directly from their mount points.
* Another alternative is to mount an ISO image of the original CD as a loop device and mount the KNOPPIX image as a '''cloop''' device. You will save close to 2GB of space. Script to mount from an ISO image:

#!/bin/bash
# Assumes that the current directory is the working space
# original.iso is an image of the CD we will be using as master
mount -t iso9660 original.iso ./oldcd -o ro,loop
# initialize the compressed loop device
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop

* Get '''apt-spy''' and use it to modify the sources.list file with the best mirrors for your particular region. This will speed up the downloading. Backup the original '''sources.list''' just in case.
* Another technique is to modify '''sources.list'''. Replace the string '''.de.''' in the ftp addresses (ftp.de.debian.org) with the code corresponding to your country. Examples: USA -> .us. (ftp.us.debian.org), Brazil -> .br. (ftp.br.debian.org). Check the Debian site for debian.org mirrors in your country.
* Remember to uncomment the '''linuxtag''' ftp addresses to get the latest and greatest from Knoppix
* Use '''apt-get update''' to get the lists with the latest releases and patches. Do not update a package if you don't need to, it may lead to the use of additional disk space (precious commodity when you want to keep everything below 700MB) and you may brake something else without knowing. Abuse the '''-s''' option to simulate the installation.
* Before doing the update, I modified my default releases to '''testing''', that means that the software I'll be using will have a good balance of stability and features. Knoppix uses '''unstable''' by default, which is too risky for my personal taste.
* Get '''[apt-get install] locale''' and configure it with the locales you are going to use. It will save lots of space when downloading applications with plenty of locale modules and localized manual pages.
* I use '''aptitude''' to get/remove applications, it is character based so it works with init 2. As you mark packages for install/update/removal, it will tell you how much disk space you will save/use, try to solve depencies problems and give you plenty control to fix them manually when possible.
* When installing applications it is likely that your '''/etc/rc?.d''' directories will have new entries, many of them unwanted or unplanned. Make sure you check them and remove the new entries based on your preferences. I usually leave '''/etc/rc2.d''' and '''/etc/rc5.d''' as close as the originals as possible and modify '''/etc/rc3.d''' and '''/etc/rc4.d''' to test new stuff. '''Example:''' You may want to have ntfs installed, but not necessarily running by default. Same with apache, mysql and many others.
* When removing/purging applications, they may leave behind non-empty directories. Usually this is announced by aptitude, apt-get or any other installation utilty. Make sure to check the messages and manually remove those directories.
* After you are done, '''aptitude''' may leave some files behind. Here's a clean up script I use:

# !/bin/bash
# Clean package files generated by aptitude
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

=Common Problems=
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] Chroot problems accessing device files

* You've <code>startx</code>'d (into whatever window manager you like) and you start a terminal (gnome-terminal, konsole, xterm). Nothing happens (such is the case in fluxbox, and you'll see an error in you <code>~/.xsession-errors</code> file). Or perhaps the error is helpfully displayed: <code>
get_pty: not enough ptys
</code>
I had plenty yesterday... but then I <code>chroot</code>ed so, to solve this, <code>
# NOT in your chroot environment
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# enter your chroot environment
chroot /mnt/hda1/knx/source/KNOPPIX/

# and mount /dev/pts
mount -t devpts /dev/pts/ /dev/pts

</code>
it might give that same "fstab not found" error as mounting proc
does. so do what you'd do then, disregard.

start your X up again and try your terminal, should work.
thanks to: technovelty[http://www.technovelty.org/linux/tips/xinchroot.html] for the final enlightenment

=See also=

If my howto is too confusing, or you'd like a second opinion, check out charan's very nice remastering howto: http://brainstorms.in/knoppix
Another Howto is at http://www.stirnimann.com/mystuff/doc/knoppix.txt

There is a wizard, which knows all the unpacking, compressing and CD-recording steps mentioned here. It also shows a shell where you can update the uncompressed KNOPPIX system using debian's standard software installation tools. It is called mmkcdrom and part of the plugscript package: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Yet another HOWTO, for shell freaks, is at http://quozl.linux.org.au/knoppix/

Be sure to check out the [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] for ideas and help with remastering.

* If you want to add a custom kernel, check out the [[Knoppix Custom Kernel Howto]]
* There also a guide at O'Reilly on the same topic : [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

=Conclusion=
Thats it. This is an updated version of my previous howto. This is not meant for linux beginners, you will need to know your way around linux to get this to work. I'll update this as corrections/improvements/etc come through.

=Thanks=
Thanks to aay, <a href = "http://brainstorms.in> charan</a>, Tech2k, and #knoppix for some corrections and tips and ideas. Feel free to edit or add to this howto.
Note about swap

=Translations=
* German Version: [[Knoppix Remastering Howto Deutsch]]
* Spanish Version: [[Knoppix Remastering Howto Spanish]] en español
* French Version: [[Knoppix Remastering Howto French]]
* Indonesian Version: [[Knoppix Remastering Howto Indonesian]]
* Russian Version: [[Knoppix Remastering Howto Russian]]
* Brazilian Portuguese Version: [[Knoppix Remastering Howto Brazilian Portuguese]]
* Italian Version: [[Knoppix Remastering Howto Italiano]]

[[Category: Remastering Knoppix ]]

Knoppix Remastering Howto

2008-05-15T16:27:02Z

202.88.238.45: /* See also */

This is a guide that will show you how to remaster KNOPPIX. (Note: commands should appear on one line, so please maximize the window. If you have any comments/suggestions please post below.)

You may wish to start from an already customized Knoppix, so you don't have to do as much work (such as removing programs). If so, see [[Knoppix Customizations]].

=System Requirements=
*CD-ISO
** at least 1 GB of FREE RAM+Swap total (e.g. 256M ram, and 750M swap AVAILABLE) (unless you use a different compression program - look in this page for compressloop)
** 3 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition
*DVD-ISO
** 5 GB free RAM + swap (for fullsized DVD)
** 15 GB free on a '''Linux filesystem (ext2/3, xfs, etc.)''' formatted disk partition

=Instructions=
==Setting up for Remastering==
# Boot from the ''Knoppix CD''
# Open a root shell:
#* Menu: Kmenu->Knoppix->Root Shell
#* Note: All commands below are run from this root shell.
# Configure your Internet connection (we'll need this later). If you use DHCP, it should already be configured.
#* Note: Run '''ifconfig''' to check.
# Find the partition you will use to work on. In this example it is called '''hda1''' . The partition should have a minimum of 3 GB free space
# Mount the partition:
#*<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
#* Note: Make sure that it is read/write or you will get errors when you later chroot. To check: run '''mount'''
# Create a root directory to work in -- if you put all your files here it will be easy to clean up
#* <pre>mkdir /mnt/hda1/knx</pre>
# If you don't have 1 GB RAM ( '''egrep "(MemTotal|SwapTotal)" /proc/meminfo && echo "(physical+swap)"''' ) then you will need a swapfile:
#* <pre>cd /mnt/hda1/knx</pre>
#* <pre>dd if=/dev/zero of=swapfile bs=1M count=750</pre>
#* <pre>mkswap swapfile</pre>
#* <pre>swapon swapfile</pre>
# Make 2 directories, one for your new Master CD, one for the source, on a disk partition. Also, make additional directories under these named KNOPPIX:
#* <pre>mkdir -p /mnt/hda1/knx/master/KNOPPIX</pre>
#* <pre>mkdir -p /mnt/hda1/knx/source/KNOPPIX</pre>
# Now, copy the KNOPPIX files to your source directory :
#* <pre><nowiki>cp -Rp /KNOPPIX/* /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
#* Note: This will take a long time (you are copying 2GB). Warning: you will be tempted to replace this copy command with a much faster procedure: create an empty directory, then use unionfs to merge the empty directory with /KNOPPIX in order to create the read-write copy. However, as of Knoppix 4.0.2, there is a bug in unionfs that causes this faster procedure to fail. For now, stick with the copy-command shown above.
# Additionally, copy the 'boot' folder from your cdrom - you'll need these files to build the ISO later.
#* <pre><nowiki>cp -ar /cdrom/boot /mnt/hda1/knx/master/boot</nowiki></pre>
# For Knoppix 5.0.1 you also have to copy the 'modules' folder:
#* <pre><nowiki>cp -ar /cdrom/KNOPPIX/modules /mnt/hda1/knx/master/KNOPPIX/.</nowiki></pre>
# Copy the main HTML page for the startup page:
#* <pre><nowiki>cp /cdrom/index.html /mnt/hda1/knx/master/</nowiki></pre>
# Copy everything necessary files except the ~700 Mb KNOPPIX file.
#* < 3.4:
#** <pre><nowiki>cd /cdrom/KNOPPIX && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/KNOPPIX/ \;</nowiki></pre>
#* >= 3.4:
#** <pre><nowiki>cd /cdrom && find . -size -10000k -type f -exec cp -p --parents '{}' /mnt/hda1/knx/master/ \;</nowiki></pre>
#* for the DVD Version you have to use -size -15000k and copy the KNOPPIX2 folder like this
#** <pre>cp -ar /KNOPPIX2/* /mnt/hda1/knx/source/KNOPPIX</pre>
# setup the environment for chroot
#* <pre>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev</pre>
#* <pre>mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc</pre>
#* <pre>mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</pre>
# Now you can "chroot" into the copied KNOPPIX:
#* <pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>
# If you see errors regarding <tt>/dev/null</tt>, see the [[#Common Problems|common problems]] section
You are now chrooted. "/" is actually "/mnt/hda1/knx/source/KNOPPIX"

==Working in the Chroot Environment==
Remember that anything you do or create in the chrooted environment will get burned to the CD. If you make any changes (e.g,. to the APT configuration, proxy settings, etc.), make a note to back the changes out before remastering.
===Internet Access===
To use the Internet you need to edit <tt>/etc/resolv.conf</tt> to add your nameserver or exit the chroot and copy the outer <tt>resolv.conf</tt> into the chroot folder:
cp /etc/dhcpc/resolv.conf /mnt/hda1/knx/source/KNOPPIX/etc/dhcpc/resolv.conf
(proxies (a.k.a. doing it at work): you can type "export http_proxy=http://your.proxy.com:<port>") 
To check your chrooted internet connection,
ping google.com
(if ICMP is barred at some corporate firewall or something then try "lynx http://www.google.com" and see if you get the page -after a cookie "allow")

===SMB access===
Also change smb.conf to your MS group if you want smbd support (MSHOME is XP Home ed. usually, and WORKGROUP is 9x Windows)
===APT===
Update your package list with '''apt-get update'''.
<blockquote>Note: If ''''apt-get update''' fails with "FATAL -> Could not set non-blocking flag Bad file descriptor", you need to make sure your chrooted environment is mounted without the "nodev" option. (see above where it talks about the /dev/null errors when entering the chroot environment for the first time)</blockquote>
<blockquote>'''Warning''': apt-get upgrade is a ''BAD IDEA''. It will, quite probably, render your KNOPPIX remaster unbootable, or broken in some way. A far safer method is to only upgrade packages as necessary.</blockquote>

'''Note: If apt-get fails with "Dynamic NMap ran out of room" ''' you might try this little gem, which fixed the problem for me:
#echo 'APT::Cache-Limit "25168524";'>> /etc/apt/apt.conf
(I did this while chrooted as described above.)

Before you can add stuff, you will probably need to remove some packages. To get a list of packages installed, type this:
dpkg-query -l
If you are looking for big installed packages then the command
dpkg-awk "Status: .* installed$" -- Package Installed-Size | \
awk '{print $2}' | egrep -v '^$' | xargs -n2 echo | \
perl -pe 's/(\S+)\s(\S+)/$2 $1/' | sort -rg
will list the packages with size in descending order.

At least ten times faster is the command
dpkg-query -W --showformat='${Installed-Size} ${Package}\n' | sort -n
and you don't need dpkg-awk or awk or perl; however it does not exclude packages that are not installed. If you have trouble with the above sort command, try using KPackage, expanded all the trees and sorted by the size column to find big packages.

Or, you could use this command to get the qpkg-query speed with the non-installed packages not listed:
dpkg-query -W --showformat='${Installed-Size} ${Package} ${Status}\n' | grep -v deinstall | sort -n | awk '{print $1" "$2}'
It does the same thing as above, I assume. I couldn't get the first one to work because I don't have dpkg-awk.

To remove a package (and all packages dependant on it), type this:
apt-get remove --purge ''name-of-package-to-remove''
To check for orphaned packages, type this:
deborphan
Want to save more space by getting rid of those pesky orphans (how cruel!), type this ('''Warning''', you won't be prompted yes/no to remove these packages. When you press Enter after this command, those packages ''will be gone''):
deborphan | xargs apt-get -y remove
If you're uncertain about the previous command and want to see what will happen without making any changes, just add the '''-s''' option to the apt-get command like this (you can do this with all of the apt-get commands, and it's a good habit to use this option before mass operations like this one):
deborphan | xargs apt-get -s -y remove
Now the good stuff. If you wish to add a package, type this:
apt-get install '''name-of-package-to-install''
What, don't know what packages to install? Type this. When the list appears, you can peruse (over 13k lines!) or search for things using <tt>/''search-term''</tt>:
apt-cache search .* | sort | less
When you're done removing and adding packages, a good way to clean up is by typing this
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
Also, because the Debian package system keeps a cache of downloaded packages, you may want to run the following to clear out those spare files:
apt-get clean

===User Settings===
User settings are in /etc/skel. This directory will be copied to make new user home directories.
<blockquote>tip: don't put files in /root they will be only available (at runtime) in /KNOPPIX/root</blockquote>

Note that the default user 'knoppix' is not created by adduser(1), thus /etc/skel is not copied completely but rather selectively. That is, to make a file .xyrc appear in /home/knoppix, it is not sufficient to place it in /etc/skel. One possibility is to extend the code in /etc/X11/Xsession.d/45xsession which is responsible for filling /home/knoppix.

===Autorunning Programs===
When you want to autorun some programs, one can create a script and put it in the directory <tt>/etc/rc5.d/</tt> (This only loads items before X loads). Read up on the SysV init process for more possibilities.

''For X-programs consider <tt>/home/knoppix/.kde/Autostart</tt> but this may transfer form <tt>/etc/skel/.kde/Autostart</tt> on boot''--[[User:12.106.237.2|12.106.237.2]] 18:08, 7 December 2007 (UTC)

==Editing the KNOPPIX auto-configuration script==
You can find a lot of interesting information about how KNOPPIX auto-configures you system by looking in the /etc/init.d/knoppix-autoconfig script. Of particular note are the following.

===Changing the default KDE background image===
The auto-configuration script sets the default KDE background image to be an image from the CD-ROM. An image that you can easily change when you are remastering KNOPPIX.
** In KNOPPIX 3.3 and below it is /cdrom/KNOPPIX/background.gif
** In KNOPPIX 3.4 and above it is /cdrom/KNOPPIX/background.jpg

===Editing floppy and CD-ROM use or adding a custom script===
The auto-configuration script sets up both your CD-ROM and your floppy disk. The commands for doing this are 'floppyconfig' and 'cdromconfig', respectively. The auto-configuration script will also run cdrom/KNOPPIX/knoppix.sh, which is an easy script to change when remastering KNOPPIX.

===Changing the default boot parameters===
All boot parameters obtain default values from the /etc/init.d/knoppix-autoconfig script. This is one massive BASH script (you best know your BASH to play with this), but it is the place that you can edit any of the default boot parameters. For example, to switch from 'kde' to 'twm' as default desktop just search for the place where 'kde' is provided as default value (variable DESKTOP, IIRC). Another example would be changing the default language.

Note, if you are interested in changing the default language KDE uses, the easiest thing to do is to load KDE, instructions are below, and use the KDE configuration utility to select your language of interest.

==X Session Configuration==
When working with X-based programs you will have to make sure that your display is set appropriately. You can do this manually when remastering KNOPPIX. Also, two scripts related to X Session is where you can change or disable the startup and shutdown sounds.

===Starting X-based programs===
When testing X-based programs, you will have to
export DISPLAY=localhost:0.0
which will allow you to connect to your normal X session. Alternately (if you need to test window managers), you can create a nested X session. Outside of the chroot, run
Xnest -ac :1
Within the chroot, set your DISPLAY variable
export DISPLAY=localhost:1

Interesting stuff in /etc/init.d/xsession :
* it ALSO sets background as /usr/local/lib/knoppix.gif

===Modifying/Disabling the startup sound===
The startup sound is played by /etc/X11/Xsession.d/45xsession. You can disable it by commenting out the following lines.
<pre><nowiki>playsound(){
# Play sound if soundcore module present (checking /dev/sndstat is unreliable)
# OGGPLAY=/usr/bin/ogg123
# PLAY=/usr/bin/wavp
# [ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
# [ -x "$PLAY" ] || PLAY=/usr/bin/play
# if [ -x "$OGGPLAY" -a -f /usr/share/sounds/startup.ogg ]; then
# case "$(lsmod)" in *sound*) { $OGGPLAY -q -p 64 /usr/share/sounds/startup.ogg >/
# elif [ -f /usr/share/sounds/startup.wav -a -x "$PLAY" ]; then
# case "$(lsmod)" in *sound*) { $PLAY /usr/share/sounds/startup.wav >/dev/null 2>&
# fi
}</nowiki></pre>

===Modifying/Disabling the shutdown sound===
The shutdown sound is played by /etc/init.d/xsession. You can disable it by commenting out lines 210-220 from the script.
<pre><nowiki>## Play informational sound if soundcore module present
## (checking /dev/sndstat is unreliable)
#OGGPLAY=/usr/bin/ogg123
#PLAY=/usr/bin/wavp
#[ -x "$PLAY" ] || PLAY=/usr/bin/play-sample
#[ -x "$PLAY" ] || PLAY=/usr/bin/play
#if [ -x "$OGGPLAY" -a -f /usr/share/sounds/shutdown.ogg ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $OGGPLAY -q -p 64 /usr/share/sound
#elif [ -f /usr/share/sounds/shutdown.wav -a -x "$PLAY" ]; then
#case "$(</proc/modules)" in *sound*|*snd_*) { $PLAY /usr/share/sounds/shutdown.w
#fi</nowiki></pre>

===Change default window manager===

Open /etc/init.d/knoppix-autoconfig and look for lines which look like these:
<pre><nowiki>
# Allow only supported windowmanagers
# Actually, this check is useless because it's done again in 45xsession. -KK
# case "$DESKTOP" in gnome|enlightenment|kde|larswm|xfce|xfce4|lg3d|ratpoison|blackbox|openbox|windowmaker|wmaker|icewm|fluxbox|twm|nx|rdp|kiosk) ;; *) DESKTOP="kde"; ;; esac
[ -n "$DESKTOP" ] || DESKTOP="kde"
</nowiki></pre>

Then, change "kde" in the last quoted line to whatever you like, for example to "fluxbox" or "twm".

==Changing the boot graphic, boot message, and startup script text==
While you are in the chroot environment you can easily change the boot messages, the boot graphic, and the default KDE background graphic.

===Changing the boot graphic===
The 'boot graphic' is the first image you see when the CD or DVD boots. It looks similar to ASCII art and it is normally something flashy that says 'Knoppix'. You can change this to be any graphic that you please, but you must use a 640x400 graphic that has only 16 colors.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old logo in case you break things.
#* <pre><nowiki>mv logo.16 logo.16.backup</nowiki></pre>
#Make a 640x400 pixel 16 color graphic and save it as a GIF, e.g. 'logo.16.gif'. GIMP can easily do this. Note, you can use a graphic that originally had more than 16 colors, but it is critical that you convert the graphic to 16 colors before doing the next step.
#Convert the GIF to lss16 using the tools included on the Knoppix CD.
#* <pre><nowiki>giftopnm < 640x400x16.gif > logo.ppm</nowiki></pre>
#* <pre><nowiki>ppmtolss16 <logo.ppm > logo.16</nowiki></pre>

===Changing the boot message===
The 'boot message' is the message that you see under the 'boot graphic' on the initial screen when the Knoppix CD or DVD loads. It normally says something along the lines of Knoppix with the version number and includes a link to the Knoppix website. You can change this text to be whatever you please, but you shouldn't add too much text or it will make the boot screen look funny. Restricting yourself to a single line of text that is no larger than the default one is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old message in case you break things.
#* <pre><nowiki>cp boot.msg boot.msg.backup</nowiki></pre>
#Edit the message with a text editor. You'll see at the top of the message that it shows the graphic. Don't change this text, just the line under.
#* <pre><nowiki>vi boot.msg</nowiki></pre>

===Changing the startup script text===
The 'startup script text' is the text that you see after the initial boot screen, while Knoppix loads and configures your system. You can change as much of this text as you please. You can even add addition lines to the script; however, it is recommended that you don't play with this file. Limiting yourself to editing the 'Welcome to KNOPPIX' message is a good idea.

#Change to the /mnt/hda1/knx/master/boot directory. Swap '/mnt/hda1/' for whatever disk you are using.
#* <pre><nowiki>cd /mnt/hda1/knx/master/boot/isolinux</nowiki></pre>
#Back up your old minirt.gz in case you break things.
#* <pre><nowiki>cp minirt.gz minirt.gz.backup</nowiki></pre>
#Uncompress minirt.gz
#* <pre><nowiki>gunzip minirt.gz</nowiki></pre>
#Make a temporary directory to mount the minirt filesystem.
#* <pre><nowiki>mkdir todelete</nowiki></pre>
#Mount the minirt filesystem as an ext2 filesystem.
#* <pre><nowiki>mount minirt todelete -t ext2 -o=/dev/loop0</nowiki></pre>
#::or if the above does not work use
#* <pre><nowiki>mount minirt todelete -t ext2 -o loop</nowiki></pre>
#Edit the linuxrc script to display the message you want. You'll find the default message approximately 2 pages down and it'll be using several colors, i.e. ${WHITE}, ${RED}, etc., so it might be slightly tricky to spot.
#* <pre><nowiki>vi todelete/linuxrc</nowiki></pre>
#unmount the minirt filesystem.
#* <pre><nowiki>umount todelete</nowiki></pre>
#Compress the minirt filesystem.
#* <pre><nowiki>gzip -9 minirt</nowiki></pre>
#Remove your temporary directory.
#* <pre><nowiki>rmdir todelete</nowiki></pre>

==Launching KDE to Change Menus, Icons, etc.==
While you are in the chroot environment you can load KDE and use the configuration tools to change buttons, icons, etc. Once you are finished you can exit KDE and copy /home/knoppix to /etc/skel to keep these changes. To load KDE do the following.

#If you are not at runlevel 2 (i.e. if you are already in KDE), switch to runlevel 2.
#* <pre><nowiki>init 2</nowiki></pre>
#Copy /etc/skel to /home/knoppix
#* <pre><nowiki>cp -Rp /etc/skel /home/knoppix</nowiki></pre>
#Change permissions to the user 'knoppix'
#* <pre><nowiki>chown knoppix:knoppix -R /home/knoppix</nowiki></pre>
#Copy over your X11 configuration to the chroot'd environment (press ctrl+alt+F2 to switch to a non-chroot'd terminal, then ctrl+alt+F1 to switch back when done)
#* <pre><nowiki>cp /etc/X11/xorg.conf /mnt/hda1/knx/source/KNOPPIX/etc/X11</nowiki></pre>
#*<blockquote>'' Knoppix 3.7: I think it's XF86Config-4 rather than xorg.conf.''</blockquote>
#(Optional)Switch to user 'knoppix'. If you want to uninstall packages, stay as root -- e.g. skip this step. If you want to configure the buttons, icons, background, etc., that you see when KDE boots, be sure to do this step.
#* <pre><nowiki>su knoppix</nowiki></pre>
##Launch KDE
##* <pre><nowiki>startx</nowiki></pre>
##Do your KDE changes
##Exit KDE
##Exit su and switch back to user 'root'.
##* <pre><nowiki>exit</nowiki></pre>
#Copy /home/knoppix back to /etc/skel to keep the changes
#* <pre><nowiki> mv /etc/skel /etc/skel-old</nowiki></pre>
#* <pre><nowiki>mv /home/knoppix /etc/skel</nowiki></pre>
#Set the owner back to root
#* <pre><nowiki>chown root:root -R /etc/skel</nowiki></pre>
#Remove the xorg.conf file
#* <pre><nowiki>rm /etc/X11/xorg.conf</nowiki></pre>
#If you find that some of your settings are not persistent after booting the new image, check the initialization file at /etc/X11/Xsession.d/45xsession. By default, Knoppix does '''not''' simply copy over all files from /etc/skel. You may need to make modifications here if you wish to do something different.

===Changing the ksplash KDE graphics===
You can change the graphics that KDE shows via ksplash when it first loads. These graphics are in the /mnt/hda1/knx/source/KNOPPIX/usr/share/apps/ksplash/Themes/Default/ directory. You'll most likely want to swap out splash_top.png for a custom 400x248 PNG graphic. Note that ksplash will not automatically put a border around your graphic. If you'd like a border, you have to manually add it to your graphic.

==Leaving the Chroot==
If you mounted it, you'll need to unmount /proc - very important!
umount /proc
Press '''CTRL+D''' to leave being chrooted.

==Re-Entering the chroot==
If you've left the chroot, but you want to go back in and modify some things...

Remount the local hard disk (if needed)
<pre>mount -rw /dev/hda1 /mnt/hda1</pre>
Setup the environment for chroot
<pre><nowiki>mount --bind /dev /mnt/hda1/knx/source/KNOPPIX/dev
mount --bind /proc /mnt/hda1/knx/source/KNOPPIX/proc
mount --bind /sys /mnt/hda1/knx/source/KNOPPIX/sys</nowiki></pre>
Now you can "chroot" into the copied KNOPPIX:
<pre><nowiki>chroot /mnt/hda1/knx/source/KNOPPIX</nowiki></pre>

==Remastering the ISO==
We've finished customizing and ready to burn!
First do some cleanup:
* remove any .bash_history files, tmp files, etc.
* back out any changes you don't want burned back to the disc
* make sure you umount /proc /dev /sys or mkisofs will not work properly
* <pre>rm -rf /mnt/hda1/knx/source/KNOPPIX/.rr_moved</pre>

===KNOPPIX Compressed Image===
Now we'll make the big <tt>KNOPPIX</tt> file which is an ISO 9660 filesystem compressed for use by the <tt>cloop</tt> driver:
mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs - 65536 > /mnt/hda1/knx/master/KNOPPIX/KNOPPIX
the "www.knoppix.net" and "Knoppix.net filesystem" can be changed to what you want to call the file. You will get an error that it doesn't conform to ISO standards -- you can ignore this. Note that, to run <tt>create_compressed_fs</tt>, you'll need to have enough space to store the entire ISO in RAM/swap. Ensure you have at least 800M of free space before starting.

In Knoppix 3.4 the <tt>create_compressed_fs</tt> script has been updated so be sure to use it to obtain the best result. It has a new option '''-b''' (best), which enables the best compression by using different compression schemes and tries to optimize that way, but be careful, because that option is slow (10x slower).

Note: The above didn't work for me using the latest create_compressed_fs. I could create the ISO but it couldn't read the compressed image properly when booting (I/O errors when reading the cloop0 device). I think this was because create_compressed_fs didn't have enough RAM and it was just failing silently. The command below did work though. It uses a file rather than memory for temporary storage:

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -B \
65536 -f /mnt/hda1/isotemp - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

------I tried this ,but it report a error,so i think there is some mistake in the command,it may be like follow,tell me if anyone confirm it-------
----------(by zhblue(newsclanATgmail.com))-------

mkisofs -R -U -V "KNOPPIX.net filesystem" -publisher "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad /mnt/hda1/knx/source/KNOPPIX \
| nice -5 /usr/bin/create_compressed_fs -b \
-f /mnt/hda1/isotemp -B 65536 - /mnt/hda1/knx/master/KNOPPIX/KNOPPIX

I noted several problems with the commands above: 
1) The option "-no-bak" excludes files with the ending ".bak". Non-backup files with this ending are found in some software packages, e.g. glest. It is safer not to use this option. 
2) Just calling "create_compressed_fs - 65536" gives a warning about old command syntax. The compatible parameters are "-m -B 65536". The later examples here already fixed this, the first example still uses the deprecated version.

===Live CD ISO===
If all went well, onto making the final CD-ROM Image:
cd /mnt/hda1/knx/master'''
find -type f -not -name md5sums -not -name boot.cat -not -name isolinux.bin \
-exec md5sum '{}' \; > KNOPPIX/md5sums
(this will update the md5 hashes of the files included in the ISO, used for integrity checking) Now to burn the image; for Knoppix <= 3.3:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img -c KNOPPIX/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
for Knoppix >= 3.4 or other isolinux based distributions:
mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \
-boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \
-hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master
(the ISO is stored in <tt>/mnt/hda1/knx/knoppix.iso</tt>)

Burn the ISO using your favorite tools, and you're ready!

==How to add new device driver to KNOPPIX==

Recently in a client project, I added the Digital Persona’s finger print driver to the Knoppix 5.1 distribution as an embedded solution to this project. This is a typical case where both the kernel level driver and the user level drivers and libraries are involved.

Most of the Knoppix books and online documentation have documented about how to keep a persistent storage of user configuration and user data. But those persistent configuration only saves the data in /home and /etc directories. If you have added kernel level drivers and/or other system libraries which are not in above two directories, you have to save the file images as a whole right after the boot. The saved file image can be big and may not what you want as a regular usage model. If you are building a customed Knoppix image for a long term solution, definitely you want to remaster the Knoppix to make the new drives be a permanent part of it.

The Digital Persona’s OneTouch SDK for their finger print scanner driver comes with a kernel level driver source code, plus a set of user level application libraries, as well as a sample test application. The SDK do not have a ready made binary for Debian or Knoppix. So I have to compile it from the source SDK. However, the CD version of Knoppix 5.1 do not even come with the source include header files to compile a kernel level driver. So I have to compile it under the DVD version of the Knoppix 5.1 and copy the compiled binary to the CD version of Knoppix 5.1 to do testing and remastering. The steps I have tried to make it work under Knoppix are as follows:

1. First compile the driver under DVD version of the Knoppix. Change the source code build scripts so that the include files and library path are matching what we have in Knoppix. The details are specific to the OneTouch SDK itself. If you are interested about this detail, write to me.

2. Install the just built kernel driver, the user libraries to their regular location as we will show in following step 4. And then build and run their sample applications per Digital Persona’s instruction. This proves that the basic kernel module build steps are built correctly and the user level libraries are working properly in a standard installation. This is important before we moved to chroot environment to make this changes permanent to our remastered Knoppix.

3. Then I followed the Knoppix remastering instructions documented in the book of “Live Linux CD” by Christoper Negus.

4. In the above remastering instructions, there is a step to update all the Debian packages and other software under the chroot environment. It is at this step that I re-run the drivers installation steps like I have done in above step 2 in the real root environment. In this particular case, it is make a directory and copy the kernel module file mod_usbdpfp.ko to that directory as follows:

mkdir /lib/modules/2.6.19/kernel/drivers/biometric
cp mod_usbdpfp.ko /lib/modules/2.6.19/mod_usbdpfp.ko

And also copy all those Digital Persona user level libraries to following location:

cp libdpfp* /usr/lib

5. I then run /sbin/depmod to let system detects the new kernel mode driver I have installed. This will refresh the /dev directory so it will have entries like:

/dev/usbdpfpPNP
/dev/usbdpfp0

At this time, if all works right, when you run command lsmod, you will also see something like:

mod_usbdpfp

shows up in the loaded module list

6. At this time, you are ready to make a remaster of the Knoppix. Next time when you boot up with this remastered Knoppix, it will have the kernel driver and user level libraries setup ready for you to run the sample applications. Just as if you have done above step 2 and step 4 right after a refresh reboot from the original Knoppix CD.

John Xu, USA. ( johnxu at n2k.net )

=Tips=
I have had good results remastering working from the CD as root working from fluxbox. Just say "knoppix 2" at the boot prompt and it will boot you to a root prompt where you can then say "startx /usr/bin/fluxbox". I like to use the xterm unicode shell.

==Package Management==
While working chroot doing the remastering I like to use
apt-get remove --purge pkg-name
to remove packages because before it does anything it will stop and show details on what it is fixing to remove and let you say "yes or no".

If you don't use the above "apt-get" instructions and have a lot to cleanup and purge, here's the easy way to do it:
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' > topurge
That will make a list of all removed packages to purge and then you just say
dpkg -P `< topurge `
and you're all done.
COLUMNS=200 dpkg -l |grep ^rc |awk '{print $2} ' | xargs dpkg -P
is a one-line version of this. Also use
deborphan | xargs dpkg -P .

==Alternatives for Low-Memory Machines==
You don't really need 1G swap as there are two new tools to create compressed filesystems. Here are some candidates to make ''compressed'' fs:
* Valentijn's rewrite [http://projects.openoffice.nl/downloads/compressloop/]
* Quozl's port of compressloop for Knoppix 3.4 [http://quozl.linux.org.au/compressloop-1.9-64bit.c]
* Quozl's distributed compressloop (use more than one processor to speed things up) [http://quozl.linux.org.au/knoppix/compressloop/] or [http://quozl.netrek.org/knoppix/compressloop/]
* Justin's patch [http://s.bouncybouncy.net/~justin/code/] (link broken) I also just wrote a distributed cloop compressor(or for smp) It's in that same directory.

==Test CD Image Without Burning a CD==
If you have a spare partition with at least 700MB free space formatted with ext2, ext3 or Vfat, you can use this for test by booting from a floppy disk. A floppy boot will look for a partiton with /KNOPPIX/ in the root, and the compressed image /KNOPPIX/KNOPPIX. Instead of using the sub-directory /mnt/hda1/knx/master/KNOPPIX/ as described above, it should be called /mnt/hda2/KNOPPIX/ . The root index.html will then be located at /mnt/hda2/index.html and the compressed image will be at /mnt/hda2/KNOPPIX/KNOPPIX . Now you can boot from floppy and use /mnt/hda2 as your image. For further information see [[Hd BasedHowTo]].

If you don't have an extra partition or you don't want to do so much for it, you can use Qemu ( see [http://fabrice.bellard.free.fr/qemu/] ) with the ISO image like this:
qemu -m 128 -cdrom /temp/knoppix-custom.iso -boot d -net user
You even do not have to build a hard disk image before, just install Qemu and try this. Amazing!

==Test remastered version without creating cloop file/iso==
i use a setup similar to knoppix terminal server to test the remastered files without having to recreate a
cloop image every time: the remastered files live in an ext2 filesytem in a loopfile (knoppix_loop) mounted rw (this is where i chroot in). when i want to test the current setup, i have another machine network boot and use the files from the loopfile directly (needs another miniroot.gz). See [[User:Ml#dev_setup]]

If you want to use only one machine, you'll have to reboot (or use qemu) and use the "loopfile" and "fromhd" cheatcodes (see [[User:Ml#miniroot_changes]]). For example, this is what my grub boot entry looks like:

<pre>
title Remastered Knoppix
root (hd0,0)
kernel /boot/myknoppix/vmlinuz fromhd=/dev/hda4 loopfile=/samba/share/isos/knoppix_loop lang=us ramdisk_size=100000 init=/etc/init apm=power-off nomce vga=791 quiet BOOT_IMAGE=knoppix
initrd /boot/myknoppix/miniroot.gz
</pre>

== Booting Knoppix images with GRUB==
* First copy /boot off the Knoppix cd to your boot partition (or even your dos partition). I named mine boot.knoppix
Copy the master/KNOPPIX directory to your root directory of any hard disk. You may place it somewhere other than the boot partition (ext2/3, reiserfs, vfat are supported).
* for Knoppix <= 3.3, put the following in your /boot/grub/menu.lst:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/vmlinuz 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/miniroot.gz
* for Knoppix >= 3.4 or other isolinux based distributions:
title KNOPPIX
root (hd0,0)
kernel /boot.knoppix/isolinux/linux 2 fromhd=/dev/hda4 lang=us
initrd /boot.knoppix/isolinux/minirt.gz
* notice the fromhd parameter: it's the location of the /KNOPPIX directory
* reboot and have fun.

==Helpful Scripts==
----
This is the recommended directory layout for remastering KNOPPIX:
. (invoke ../remaster from here)
|-- master (invoke ../../[[u]]mountbootimage from here)
| |-- KNOPPIX
| | |-- KNOPPIX (compressed image)
| | |-- boot.img (boot floppy image)
| | `-- (other files snipped)
| `-- index.html
`-- source
`-- KNOPPIX (this directory can be chrooted into)
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- floppy
|-- home
|-- initrd
|-- lib
|-- mnt
|-- none
|-- opt
|-- proc
|-- root
|-- sbin
|-- tmp -> /var/tmp
|-- usr
|-- var
`-- vmlinuz -> boot/vmlinuz-2.4.22-xfs
----
the following script "remaster" will do the remaster process for you. Use as root, or you will end up with wrong access rights in the image.

The script has last been tried out on Debian sid on 2004-04-02.

#!/bin/bash -x
# This script builds a new KNOPPIX ISO image.
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2

ROOT="$PWD"
SOURCE="$ROOT/source/KNOPPIX"
MASTER="$ROOT/master"
CLOOPTARGET="$ROOT/master/KNOPPIX/KNOPPIX"
TARGET="$ROOT"
EXCLUDELIST="$ROOT/source/excludelist"

rm -rf $SOURCE/.rr_moved

cd $SOURCE
mkisofs -R -U -V "KNOPPIX.net filesystem" \
-P "KNOPPIX www.knoppix.net" \
-hide-rr-moved -cache-inodes -no-bak -pad \
-exclude-list $EXCLUDELIST \
. | nice -5 /usr/bin/create_compressed_fs - 65536 > $CLOOPTARGET

cd $MASTER
rm -f KNOPPIX/md5sums
find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums
mkisofs -pad -l -r -J -v -V "KNOPPIX" -b KNOPPIX/boot.img \
-c KNOPPIX/boot.cat -hide-rr-moved -o $TARGET/knoppix.iso $MASTER
----
The following script will loop-mount boot floppy image and initrd image for modification. The umount function will build a new initrd image and put it back on the boot floppy image.

The script has last been tried out on Debian sid on 2004-01-13.

#!/bin/bash -x
# This script will loop-mount boot floppy and initrd image
# Copyright (C) 2004 by Marc Haber <mh+knoppix-remaster@zugschlus.de>
# License: GPL V2
unset CDPATH || true

# if not root, re-invoke self as root
if [[ "`id -u`" -ne 0 ]]; then
export LOCUSER="$USER"
export LOCHOME="$HOME"
if [[ "${SHELLOPTS/xtrace/}" != "$SHELLOPTS" ]]; then
sudo bash -x $0 $@
exit $?
else
sudo $0 $@
exit $?
fi
else
LOCUSER="${LOCUSER:-$USER}"
LOCHOME="${LOCHOME:-$HOME}"
fi
set -e

KNOPPIXDIR="KNOPPIX"
BOOTIMGFILE="$KNOPPIXDIR/boot.img"
BOOTIMGFS="vfat"
BOOTIMGDIR="boot.img"
INITRDGZ="$BOOTIMGDIR/miniroot.gz"
INITRDFILE="$KNOPPIXDIR/miniroot"
INITRDFS="ext2"
INITRDDIR="miniroot"

mountbootimage() {
if ! modprobe loop; then
echo >&2 "ERR: cannot load loop module"
exit 1
fi

if ! [[ -e "$BOOTIMGFILE" ]]; then
echo >&2 "ERR: no $BOOTIMGFILE found"
exit 1
fi

for nofile in $BOOTIMGDIR $INITRDGZ $INITRDFILE $INITRDDIR; do
if [[ -e "$nofile" ]]; then
echo >&2 "ERR: $nofile already exists"
exit 1
fi
done

mkdir -p $BOOTIMGDIR
mount -o loop,uid=$LOCUSER -t $BOOTIMGFS $BOOTIMGFILE $BOOTIMGDIR

< $INITRDGZ gunzip > $INITRDFILE
mkdir -p $INITRDDIR
mount -o loop -t $INITRDFS $INITRDFILE $INITRDDIR
}

umountbootimage() {
dd if=/dev/zero of=$INITRDDIR/nullfile || true
sync
rm $INITRDDIR/nullfile
umount $INITRDDIR
rmdir $INITRDDIR
< $INITRDFILE gzip --best > $INITRDGZ
rm -f $INITRDFILE

umount $BOOTIMGDIR
rmdir $BOOTIMGDIR

syslinux KNOPPIX/boot.img
}

case "`basename $0`" in
mountbootimage)
mountbootimage
;;
umountbootimage)
umountbootimage
;;
*)
echo >&2 "ERR: called with unknown name `basename $0`"
exit 1
;;
esac

==Tips around apt-get to install/update/remove applications==
(by gnarvaja)
* If you booted from CD, even on a HD install (example: Pivot Install) instead of copying the original CD and KNOPPIX directory to the HD, you can use them directly from their mount points.
* Another alternative is to mount an ISO image of the original CD as a loop device and mount the KNOPPIX image as a '''cloop''' device. You will save close to 2GB of space. Script to mount from an ISO image:

#!/bin/bash
# Assumes that the current directory is the working space
# original.iso is an image of the CD we will be using as master
mount -t iso9660 original.iso ./oldcd -o ro,loop
# initialize the compressed loop device
losetup /dev/cloop1 ./oldcd/KNOPPIX/KNOPPIX
mount -t iso9660 /dev/cloop1 ./KNOPPIX -o ro,loop

* Get '''apt-spy''' and use it to modify the sources.list file with the best mirrors for your particular region. This will speed up the downloading. Backup the original '''sources.list''' just in case.
* Another technique is to modify '''sources.list'''. Replace the string '''.de.''' in the ftp addresses (ftp.de.debian.org) with the code corresponding to your country. Examples: USA -> .us. (ftp.us.debian.org), Brazil -> .br. (ftp.br.debian.org). Check the Debian site for debian.org mirrors in your country.
* Remember to uncomment the '''linuxtag''' ftp addresses to get the latest and greatest from Knoppix
* Use '''apt-get update''' to get the lists with the latest releases and patches. Do not update a package if you don't need to, it may lead to the use of additional disk space (precious commodity when you want to keep everything below 700MB) and you may brake something else without knowing. Abuse the '''-s''' option to simulate the installation.
* Before doing the update, I modified my default releases to '''testing''', that means that the software I'll be using will have a good balance of stability and features. Knoppix uses '''unstable''' by default, which is too risky for my personal taste.
* Get '''[apt-get install] locale''' and configure it with the locales you are going to use. It will save lots of space when downloading applications with plenty of locale modules and localized manual pages.
* I use '''aptitude''' to get/remove applications, it is character based so it works with init 2. As you mark packages for install/update/removal, it will tell you how much disk space you will save/use, try to solve depencies problems and give you plenty control to fix them manually when possible.
* When installing applications it is likely that your '''/etc/rc?.d''' directories will have new entries, many of them unwanted or unplanned. Make sure you check them and remove the new entries based on your preferences. I usually leave '''/etc/rc2.d''' and '''/etc/rc5.d''' as close as the originals as possible and modify '''/etc/rc3.d''' and '''/etc/rc4.d''' to test new stuff. '''Example:''' You may want to have ntfs installed, but not necessarily running by default. Same with apache, mysql and many others.
* When removing/purging applications, they may leave behind non-empty directories. Usually this is announced by aptitude, apt-get or any other installation utilty. Make sure to check the messages and manually remove those directories.
* After you are done, '''aptitude''' may leave some files behind. Here's a clean up script I use:

# !/bin/bash
# Clean package files generated by aptitude
rm /var/log/aptitude
rm /var/lib/apt/lists/*debian*
rm /var/lib/apt/lists/*knoppix*

=Common Problems=
* [[Dev_null_permission_denied|/dev/null: Permission Denied]] Chroot problems accessing device files

* You've <code>startx</code>'d (into whatever window manager you like) and you start a terminal (gnome-terminal, konsole, xterm). Nothing happens (such is the case in fluxbox, and you'll see an error in you <code>~/.xsession-errors</code> file). Or perhaps the error is helpfully displayed: <code>
get_pty: not enough ptys
</code>
I had plenty yesterday... but then I <code>chroot</code>ed so, to solve this, <code>
# NOT in your chroot environment
cd /mnt/hda1/knx/source/KNOPPIX/dev
MAKEDEV pty

# enter your chroot environment
chroot /mnt/hda1/knx/source/KNOPPIX/

# and mount /dev/pts
mount -t devpts /dev/pts/ /dev/pts

</code>
it might give that same "fstab not found" error as mounting proc
does. so do what you'd do then, disregard.

start your X up again and try your terminal, should work.
thanks to: technovelty[http://www.technovelty.org/linux/tips/xinchroot.html] for the final enlightenment

=See also=

If my howto is too confusing, or you'd like a second opinion, check out charan's very nice remastering howto: http://brainstorms.in/knoppix
Another Howto is at http://www.stirnimann.com/mystuff/doc/knoppix.txt

There is a wizard, which knows all the unpacking, compressing and CD-recording steps mentioned here. It also shows a shell where you can update the uncompressed KNOPPIX system using debian's standard software installation tools. It is called mmkcdrom and part of the plugscript package: [http://rcswww.urz.tu-dresden.de/~holzhey/plugscript]

Yet another HOWTO, for shell freaks, is at http://quozl.linux.org.au/knoppix/

Be sure to check out the [http://knoppix.net/forum/viewforum.php?f=2 Knoppix Customization Forum] for ideas and help with remastering.

* If you want to add a custom kernel, check out the [[Knoppix Custom Kernel Howto]]
* There also a guide at O'Reilly on the same topic : [http://linux.oreillynet.com/lpt/a/4323 Using and Customizing Knoppix]

=Conclusion=
Thats it. This is an updated version of my previous howto. This is not meant for linux beginners, you will need to know your way around linux to get this to work. I'll update this as corrections/improvements/etc come through.

=Thanks=
Thanks to aay, charan, Tech2k, and #knoppix for some corrections and tips and ideas. Feel free to edit or add to this howto.
Note about swap: 

=Translations=
* German Version: [[Knoppix Remastering Howto Deutsch]]
* Spanish Version: [[Knoppix Remastering Howto Spanish]] en español
* French Version: [[Knoppix Remastering Howto French]]
* Indonesian Version: [[Knoppix Remastering Howto Indonesian]]
* Russian Version: [[Knoppix Remastering Howto Russian]]
* Brazilian Portuguese Version: [[Knoppix Remastering Howto Brazilian Portuguese]]
* Italian Version: [[Knoppix Remastering Howto Italiano]]

[[Category: Remastering Knoppix ]]