Customizing Knoppix - Revision history

PhilippeTeuwen: Reverted edits by Etegohy (Talk) to last revision by PhilippeTeuwen

2010-11-24T20:32:17Z

Reverted edits by Etegohy (Talk) to last revision by PhilippeTeuwen

Can't load revision 6785

at 00:26, 24 November 2010

2010-11-24T00:26:07Z

Can't load revision 6624

PhilippeTeuwen at 16:00, 28 March 2008

2008-03-28T16:00:38Z

← Older revision		Revision as of 16:00, 28 March 2008
Line 44:		Line 44:
	This is slightly different between Knoppix v5.0.1 and v5.1.1.		This is slightly different between Knoppix v5.0.1 and v5.1.1.
	<br>Here is for Knoppix v5.0.1:		<br>Here is for Knoppix v5.0.1:
			<source lang=diff>
	<pre>
	--- knoppix-image 2006-04-23 00:19:38.000000000 +0200		--- knoppix-image 2006-04-23 00:19:38.000000000 +0200
	+++ knoppix.sh 2006-08-16 11:19:04.000000000 +0200		+++ knoppix.sh 2006-08-16 11:19:04.000000000 +0200
Line 83:		Line 83:
	+		+
	+#All My own customisation will be done from here:		+#All My own customisation will be done from here:
	</~~pre~~>		</source>

	Here is for Knoppix v5.1.1:		Here is for Knoppix v5.1.1:
			<source lang=diff>
	<pre>
	--- knoppix-image 2007-03-22 09:28:15.000000000 -0400		--- knoppix-image 2007-03-22 09:28:15.000000000 -0400
	+++ knoppix.sh 2007-03-22 15:06:12.000000000 -0400		+++ knoppix.sh 2007-03-22 15:06:12.000000000 -0400
Line 127:		Line 127:
	+		+
	+#All My own customisation will be done here		+#All My own customisation will be done here
	</~~pre~~>		</source>

	When later we will boot from the Knoppix CD, by giving the "myconf=scan" argument on the boot line, the CD will look for... a script called knoppix.sh		When later we will boot from the Knoppix CD, by giving the "myconf=scan" argument on the boot line, the CD will look for... a script called knoppix.sh
Line 198:		Line 198:
	* restarting udev so that it is aware of the new driver (for subsequent hotpluggings of the hardware)		* restarting udev so that it is aware of the new driver (for subsequent hotpluggings of the hardware)
	* loading manually the driver (in case the hardware was already plugged when the Knoppix booted)		* loading manually the driver (in case the hardware was already plugged when the Knoppix booted)
			<source lang=bash>
	# My driver		# My driver
	/etc/init.d/udev restart		/etc/init.d/udev restart
	modprobe my_module		modprobe my_module
			</source>

	====New shared library====		====New shared library====
	Install the new lib and its symlink under /KNOPPIX.IMG/usr/local/lib		Install the new lib and its symlink under /KNOPPIX.IMG/usr/local/lib
Line 213:		Line 214:
	Then we have to append the following to our knoppix.sh script:		Then we have to append the following to our knoppix.sh script:
	* Simply force reloading of the driver, which will look again for its firmware		* Simply force reloading of the driver, which will look again for its firmware
			<source lang=bash>
	# ipw2200 driver		# ipw2200 driver
	if lsmod \| grep -q ipw2200; then		if lsmod \| grep -q ipw2200; then
Line 218:		Line 220:
	modprobe ipw2200		modprobe ipw2200
	fi		fi
			</source>

	This is solved on v5.1.1 so this example is here just for... the example.		This is solved on v5.1.1 so this example is here just for... the example.

Line 230:		Line 232:
	* Copy the driver to /ramdisk as well		* Copy the driver to /ramdisk as well
	* Force reloading of the updated driver		* Force reloading of the updated driver
			<source lang=bash>
	# my new version of driver		# my new version of driver
	# Note that loaded drivers were copied also to /ramdisk so we need to change them there		# Note that loaded drivers were copied also to /ramdisk so we need to change them there
Line 237:		Line 240:
	modprobe new_driver		modprobe new_driver
	fi		fi
			</source>

	<br>With aufs you don't need to do so!		<br>With aufs you don't need to do so!
	<br>Just rmmod + modprobe the module		<br>Just rmmod + modprobe the module
Line 248:		Line 251:
	We put our new background in e.g. /home/knoppix/resources/my_background.png		We put our new background in e.g. /home/knoppix/resources/my_background.png
	<br>Then we have to append the following to our knoppix.sh script:		<br>Then we have to append the following to our knoppix.sh script:
			<source lang=bash>
	# Customize background		# Customize background
	# This is tricky, /etc/init.d/knoppix-autoconfig defines $BACKGROUND		# This is tricky, /etc/init.d/knoppix-autoconfig defines $BACKGROUND
Line 256:		Line 260:
	# so we modify /etc/sysconfig/knoppix		# so we modify /etc/sysconfig/knoppix
	sed -i 's#^BACKGROUND=.*#BACKGROUND="/UNIONFS/home/knoppix/resources/my_background.png"#' /etc/sysconfig/knoppix		sed -i 's#^BACKGROUND=.*#BACKGROUND="/UNIONFS/home/knoppix/resources/my_background.png"#' /etc/sysconfig/knoppix
			</source>

	====Software====		====Software====
	We could install the Debian package but this means having to bring the new dpkg caches to the USB stick too.		We could install the Debian package but this means having to bring the new dpkg caches to the USB stick too.
Line 275:		Line 279:
	Terminal=0		Terminal=0
	* We make sure the help file will be automatically open		* We make sure the help file will be automatically open
			<source lang=bash>
	ln -s /home/knoppix/Desktop/Help.desktop /KNOPPIX.IMG/home/knoppix/.kde/Autostart/showindex.desktop		ln -s /home/knoppix/Desktop/Help.desktop /KNOPPIX.IMG/home/knoppix/.kde/Autostart/showindex.desktop
			</source>

	====Misc icons====		====Misc icons====
	Icons positions can be defined in /KNOPPIX.IMG/home/knoppix/.kde/share/apps/kdesktop/IconPositions		Icons positions can be defined in /KNOPPIX.IMG/home/knoppix/.kde/share/apps/kdesktop/IconPositions

PhilippeTeuwen: /* Principle */

2007-03-22T21:09:48Z

Principle

← Older revision		Revision as of 21:09, 22 March 2007
Line 7:		Line 7:
	===Principle===		===Principle===
	Some Knoppix versions < 5.1 are based on Unionfs (cf [http://www.fsl.cs.sunysb.edu/project-unionfs.html here] or [http://www.filesystems.org/project-unionfs.html there])		Some Knoppix versions < 5.1 are based on Unionfs (cf [http://www.fsl.cs.sunysb.edu/project-unionfs.html here] or [http://www.filesystems.org/project-unionfs.html there])
	<br>See [http://www.linux-live.org/unionfs/ this page]to discover and understand unionfs.		<br>See [http://www.linux-live.org/unionfs/ this page] to discover and understand unionfs.
	<br>Knoppix since version 5.1 moved to [http://aufs.sourceforge.net/ aufs] (another unionfs) but the principles are the same and is it worth to have a look to unionfs presentation anyway.		<br>Knoppix since version 5.1 moved to [http://aufs.sourceforge.net/ aufs] (another unionfs) but the principles are the same and is it worth to have a look to unionfs presentation anyway.

PhilippeTeuwen: /* Versions currently supported */

2007-03-22T21:09:06Z

Versions currently supported

← Older revision		Revision as of 21:09, 22 March 2007
Line 1:		Line 1:
	===Versions currently supported===		===Versions currently supported===
	Currently this document is written for Knoppix 5.0.1		Currently this document is written for Knoppix 5.0.1 and Knoppix 5.1.1
	<br>It also works with FCCU v11.0 CD		<br>It also works with FCCU v11.0 CD

PhilippeTeuwen: /* Software */

2007-03-22T21:08:07Z

Software

← Older revision		Revision as of 21:08, 22 March 2007
Line 258:		Line 258:

	====Software====		====Software====
	We could install the Debian package but this means having to bring ~~hte~~ new dpkg caches to the stick too.		We could install the Debian package but this means having to bring the new dpkg caches to the USB stick too.
	<br>For small stuffs this is much easier just to extract the soft from the Debian package and install it in /usr/local		<br>For small stuffs this is much easier just to extract the soft from the Debian package and install it in /usr/local
	-> /KNOPPIX.IMG/usr/local/bin/my_soft (and the man page...)		-> /KNOPPIX.IMG/usr/local/bin/my_soft (and the man page...)
	This is better to take it ~~fron~~ the real Debian package as you benefit from the version control of dpkg and are sure you install a version compatible with the rest of the CD.		This is better to take it from the real Debian package as you benefit from the version control of dpkg and are sure you install a version compatible with the rest of the CD.

	====Help====		====Help====

PhilippeTeuwen: /* Upgrading a driver */

2007-03-22T20:53:26Z

Upgrading a driver

← Older revision		Revision as of 20:53, 22 March 2007
Line 239:		Line 239:

	<br>With aufs you don't need to do so!		<br>With aufs you don't need to do so!
	<r>Just rmmod + modprobe the module		<br>Just rmmod + modprobe the module

	====Background customization====		====Background customization====

PhilippeTeuwen: /* Upgrading a driver */

2007-03-22T20:53:12Z

Upgrading a driver

← Older revision		Revision as of 20:53, 22 March 2007
Line 223:		Line 223:
	====Upgrading a driver====		====Upgrading a driver====
	Here this is the case of a driver available on the original Knoppix CD but we want e.g. to upgrade it or use a patched version.		Here this is the case of a driver available on the original Knoppix CD but we want e.g. to upgrade it or use a patched version.
	<br>As said before, all drivers loaded during the boot are copied to /ramdisk so as we want to update them, we better have to update those in /ramdisk as well.		<br>As said before, when using unionfs all drivers loaded during the boot are copied to /ramdisk so as we want to update them, we better have to update those in /ramdisk as well.
	Install the compiled drivers under /KNOPPIX.IMG/lib/modules/2.6.17/kernel/drivers/... and /ramdisk/lib/modules/2.6.17/kernel/drivers/... and binaries under /KNOPPIX.IMG/usr/local/bin		<br>Install the compiled drivers under /KNOPPIX.IMG/lib/modules/2.6.17/kernel/drivers/... and /ramdisk/lib/modules/2.6.17/kernel/drivers/... and binaries under /KNOPPIX.IMG/usr/local/bin
	<br>Execute depmod and copy new /ramdisk/lib/modules/2.6.17/modules.* to /KNOPPIX.IMG		<br>Execute depmod and copy new /ramdisk/lib/modules/2.6.17/modules.* to /KNOPPIX.IMG

Line 237:		Line 237:
	modprobe new_driver		modprobe new_driver
	fi		fi

			<br>With aufs you don't need to do so!
			<r>Just rmmod + modprobe the module

	====Background customization====		====Background customization====

PhilippeTeuwen: /* Fixing a driver */

2007-03-22T20:51:46Z

Fixing a driver

← Older revision		Revision as of 20:51, 22 March 2007
Line 207:		Line 207:

	====Fixing a driver====		====Fixing a driver====
	Here this is the case of a driver available on the original Knoppix CD but not with the last firmware update (rendering the driver unusable): ipw2200		Here this is the case of a driver available on the original Knoppix CD v5.0.1 but not with the last firmware update (rendering the driver unusable): ipw2200

	Install the last firmware under /KNOPPIX.IMG/usr/lib/hotplug/firmware/ipw2200-*.fw		Install the last firmware under /KNOPPIX.IMG/usr/lib/hotplug/firmware/ipw2200-*.fw
Line 218:		Line 218:
	modprobe ipw2200		modprobe ipw2200
	fi		fi

			This is solved on v5.1.1 so this example is here just for... the example.

	====Upgrading a driver====		====Upgrading a driver====

PhilippeTeuwen: /* Drivers */

2007-03-22T20:50:07Z

Drivers

← Older revision		Revision as of 20:50, 22 March 2007
Line 185:		Line 185:
	* If the driver did not exist on the CD, then we can simply load manually the driver with a modprobe from our script.		* If the driver did not exist on the CD, then we can simply load manually the driver with a modprobe from our script.
	* If the system relies on udev to set automatically some rights or whatever and if udev rules were added, then it is wise to restart udev from knoppix.sh script so that next time the hardware is plugged these rules will be effective.		* If the system relies on udev to set automatically some rights or whatever and if udev rules were added, then it is wise to restart udev from knoppix.sh script so that next time the hardware is plugged these rules will be effective.
	* If the driver is an updated version of an existing driver on the CD then things are slightly more complex:<br>All drivers loaded during the boot are copied for a mysterious reason to /ramdisk<br>So before calling depmod, better first to overwrite the old driver with the new one in /ramdisk<br>The procedure will then be, from the knoppix.sh script: rmmod the driver, overwrite the old version with the new one in /ramdisk, modprobe the new one.		* If the driver is an updated version of an existing driver on the CD then things are slightly more complex with unionfs ('''note that this is solved with aufs'''):<br>All drivers loaded during the boot are copied for a mysterious reason to /ramdisk<br>So before calling depmod, better first to overwrite the old driver with the new one in /ramdisk<br>The procedure will then be, from the knoppix.sh script: rmmod the driver, overwrite the old version with the new one in /ramdisk, modprobe the new one.

	===Exception examples===		===Exception examples===