FAIWiki - Recent changes [en]

Make-fai-nfsroot.conf

2009-11-19T15:09:35Z

←Older revision		Revision as of 15:09, 19 November 2009
(One intermediate revision not shown.)
Line 1:		Line 1:
-	Configuration file for the FAI command [[make-fai-nfsroot]].	+	Configuration file for the FAI command [[make-fai-nfsroot]]. This file is typically located at <tt>/etc/fai/make-fai-nfsroot.conf</tt>.

	== Sample configuration file ==		== Sample configuration file ==

Multiple Network Interfaces Howto

2009-11-19T15:07:45Z

+ NFSROOT troubleshooting and link

←Older revision		Revision as of 15:07, 19 November 2009
(2 intermediate revisions not shown.)
Line 25:		Line 25:
	; Boot process stops at ''ipconfig'' (client installation over network)		; Boot process stops at ''ipconfig'' (client installation over network)
	: Check which MAC address ipconfig is trying to set up. Typically, the related interface is not connected to a network that provides a DHCP address for that network card.		: Check which MAC address ipconfig is trying to set up. Typically, the related interface is not connected to a network that provides a DHCP address for that network card.
		+	; NFSROOT cooperates only with one network interface
		+	: Before you build your NFSROOT (using [[make-fai-nfsroot]]) make sure you have specified all possible IP addresses and server names for your FAI server at the <tt>NFSROOT_ETC_HOSTS</tt> option in /etc/fai/[[make-fai-nfsroot.conf]]

	== See also ==		== See also ==

	* [[Multi-ethernet\|Multi-ethernet setup with custom initrd]]		* [[Multi-ethernet\|Multi-ethernet setup with custom initrd]]
		+	* [[fai-chboot]]
		+	* [[make-fai-nfsroot.conf]]

	=== Related Discussions ===		=== Related Discussions ===
Line 37:		Line 41:
	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01748.html Dual NIC = hang] (Feb 2009)		* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01748.html Dual NIC = hang] (Feb 2009)
	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01553.html tg3 network cards] (Dec 2008)		* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01553.html tg3 network cards] (Dec 2008)
		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01321.html problem install client with multiple interfaces] (Sep 2008)

	[[Category:Howto]]		[[Category:Howto]]

Fai-chboot

2009-11-19T10:12:05Z

Multiple Network Interfaces Howto

2009-11-19T09:46:52Z

Solution: + 2nd draft (suggested by olivalukas@gmail.com)

←Older revision		Revision as of 09:46, 19 November 2009
Line 9:		Line 9:
	== Solution ==		== Solution ==

-	''Draft recommendation:''	+	''Draft recommendation I:''

	* Set up DHCP for each network (card), otherwise the installation boot process will hang when <tt>ipconfig</tt> tries to set up all interfaces.		* Set up DHCP for each network (card), otherwise the installation boot process will hang when <tt>ipconfig</tt> tries to set up all interfaces.
	* You should have one template <tt>/etc/network/interfaces</tt> for each class of machine, and then plug in the IP addresses for each machine via search and replace. Use cfagent for this.		* You should have one template <tt>/etc/network/interfaces</tt> for each class of machine, and then plug in the IP addresses for each machine via search and replace. Use cfagent for this.
		+
		+	''Draft recommendation II:''
		+
		+	* Set up BIOS to boot preferably from network card on internal network where you have the FAI server.
		+	* Specify a <tt>ip=eth0:dhcp</tt> line in the tftp config file for all clients. If that doesn't work specify it statically (see <tt>/usr/src/linux/Documentation/filesystems/nfsroot.txt</tt> for the syntax).
		+	* Set up the dhcp server to assign IP address to the MAC address of the client network interface you boot from.
		+	* Write a simple shell script to generate an appropriate <tt>/etc/network/interfaces</tt> file from the <tt>$HOSTNAME</tt> corresponding to the IP address obtained from DHCP (also check <tt>/etc/hosts file</tt>).

	== Analysis, Troubleshooting ==		== Analysis, Troubleshooting ==

Multi-ethernet

2009-11-19T08:39:47Z

←Older revision		Revision as of 08:39, 19 November 2009
(One intermediate revision not shown.)
Line 1:		Line 1:
-	~~== Multi-Ethernet Setup with Custom initrd ==~~
-
	I wanted to share my experience with multi ethernet card on debian and FAI install.		I wanted to share my experience with multi ethernet card on debian and FAI install.
		+
		+	== Multi-Ethernet Setup with Custom initrd ==

	What I did is to use a custom initrd so this is not very easy as you need to create a new initrd for each machine that needs ethernet card renumbering.		What I did is to use a custom initrd so this is not very easy as you need to create a new initrd for each machine that needs ethernet card renumbering.

	# You should have your nfsroot created.		# You should have your nfsroot created.
-	# Do a chroot /srv/fai/nfsroot/live/filesystem.dir (or where your nfsroot is), cd /etc/udev/rules.d/	+	# Do a <tt>chroot /srv/fai/nfsroot/live/filesystem.dir</tt> (or where your nfsroot is), <tt>cd /etc/udev/rules.d/</tt>
-	# Create a rule for your ethernet cards in 70-persistent-net.rules	+	# Create a rule for your ethernet cards in <tt>70-persistent-net.rules</tt>

	Example:		Example:
Line 30:		Line 30:
	</pre>		</pre>

-	# ~~then~~ make the custom initrd : update-initramfs -u -k all	+	# Then make the custom initrd: <tt>update-initramfs -u -k all</tt>
-	# ~~exit~~ the chroot (exit)	+	# Exit the chroot: <tt>exit</tt>
-	# ~~copy~~ the initrd to the tftp server: cp /srv/fai/nfsroot/live/filesystem.dir/boot/initrd.* /srv/tftp/fai/	+	# Copy the initrd to the tftp server: <tt>cp /srv/fai/nfsroot/live/filesystem.dir/boot/initrd.* /srv/tftp/fai/</tt>

	That should do it. You should have the following in your boot output:		That should do it. You should have the following in your boot output:
Line 47:		Line 47:
	Regards,		Regards,
	Jean.		Jean.
		+
		+
		+	== See also ==
		+
		+	* [[Multiple Network Interfaces Howto]]
		+
		+	[[Category:Howto]]

Multiple Network Interfaces Howto

2009-11-19T08:33:43Z

Multi-ethernet

2009-11-19T08:30:20Z

Layout fixes for readability

←Older revision		Revision as of 08:30, 19 November 2009
Line 1:		Line 1:
-	~~Hi,~~	+	== Multi-Ethernet Setup with Custom initrd ==

-	I wanted to share my experience with multi ethernet card on debian and FAI install.	+	I wanted to share my experience with multi ethernet card on debian and FAI install.

-	What ~~i done~~ is to use a ~~custome~~ initrd so this is not very easy as you need to create a new initrd for each machine that ~~need~~ ethernet card renumbering.	+	What I did is to use a custom initrd so this is not very easy as you need to create a new initrd for each machine that needs ethernet card renumbering.

-	So	+	# You should have your nfsroot created.
		+	# Do a chroot /srv/fai/nfsroot/live/filesystem.dir (or where your nfsroot is), cd /etc/udev/rules.d/
		+	# Create a rule for your ethernet cards in 70-persistent-net.rules
		+
		+	Example:

-	~~# you should have your nfsroot created.~~
-	~~# do a chroot /srv/fai/nfsroot/live/filesystem.dir (or where your nfsroot is), cd /etc/udev/rules.d/~~
-	~~# create a rule for your ethernet cards in 70-persistent-net.rules~~
	<pre>		<pre>
-
-	~~exemple:~~
-
	# This file was automatically generated by the /lib/udev/write_net_rules		# This file was automatically generated by the /lib/udev/write_net_rules
	# program run by the persistent-net-generator.rules rules file.		# program run by the persistent-net-generator.rules rules file.
Line 27:		Line 25:
	# PCI device 0x8086:0x105e (e1000e)		# PCI device 0x8086:0x105e (e1000e)
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?", ATTR{address}=="00:1e:c9:f8:99:97", ATTR{type}=="1", KERNEL=="eth", NAME="eth0"		SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?", ATTR{address}=="00:1e:c9:f8:99:97", ATTR{type}=="1", KERNEL=="eth", NAME="eth0"
-

	# PCI device 0x8086:0x105e (e1000e)		# PCI device 0x8086:0x105e (e1000e)
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?", ATTR{address}=="00:1e:c9:f8:99:f8", ATTR{type}=="1", KERNEL=="eth", NAME="eth1"		SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?", ATTR{address}=="00:1e:c9:f8:99:f8", ATTR{type}=="1", KERNEL=="eth", NAME="eth1"
		+	</pre>

-	~~</pre>~~
	# then make the custom initrd : update-initramfs -u -k all		# then make the custom initrd : update-initramfs -u -k all
	# exit the chroot (exit)		# exit the chroot (exit)
	# copy the initrd to the tftp server: cp /srv/fai/nfsroot/live/filesystem.dir/boot/initrd.* /srv/tftp/fai/		# copy the initrd to the tftp server: cp /srv/fai/nfsroot/live/filesystem.dir/boot/initrd.* /srv/tftp/fai/

-		+	That should do it. You should have the following in your boot output:
-	~~that~~ should do it. ~~you~~ should have:	+

	<pre>		<pre>
-
	[ 7.695861] udev: renamed network interface eth2 to eth0		[ 7.695861] udev: renamed network interface eth2 to eth0
	[ 7.698869] udev: renamed network interface eth3 to eth1		[ 7.698869] udev: renamed network interface eth3 to eth1
	[ 7.752956] udev: renamed network interface eth0_rename to eth2		[ 7.752956] udev: renamed network interface eth0_rename to eth2
	[ 7.753904] udev: renamed network interface eth1_rename to eth3		[ 7.753904] udev: renamed network interface eth1_rename to eth3
-
	</pre>		</pre>

-	~~in your boot output.~~	+	Beware as each make-nfsroot will trash this setup so keep a backup somewhere!
-		+
-	~~beware~~ as each make-nfsroot will trash this setup so keep a backup somewhere !	+
-		+

-	~~regards~~,	+	Regards,
	Jean.		Jean.

Multiple Network Interfaces Howto

2009-11-19T08:23:13Z

Related Discussions: + another thread

←Older revision		Revision as of 08:23, 19 November 2009
(2 intermediate revisions not shown.)
Line 9:		Line 9:
	== Solution ==		== Solution ==

-	...	+	''Draft recommendation:''
		+
		+	* Set up DHCP for each network (card), otherwise the installation boot process will hang when <tt>ipconfig</tt> tries to set up all interfaces.
		+	* You should have one template <tt>/etc/network/interfaces</tt> for each class of machine, and then plug in the IP addresses for each machine via search and replace. Use cfagent for this.

	== Analysis, Troubleshooting ==		== Analysis, Troubleshooting ==
Line 18:		Line 21:
	== Related Discussions ==		== Related Discussions ==

		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg02582.html Two network cards] (Nov 2009)
		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg02110.html FAI - Debian Lenny and Hardware with Multiple Ethernets] (Jun 2009)
	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01845.html Multiple NICs, partial success, partial weirdness] (Mar 2009)		* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01845.html Multiple NICs, partial success, partial weirdness] (Mar 2009)
	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01748.html Dual NIC = hang] (Feb 2009)		* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01748.html Dual NIC = hang] (Feb 2009)

Main Page

2009-11-18T23:13:56Z

←Older revision		Revision as of 23:13, 18 November 2009
(One intermediate revision not shown.)
Line 18:		Line 18:
	* add this to your /etc/apt/sources.list, as well as /etc/fai/apt/sources.list(to get the correct fai-nfsroot package into the nfsroot) - depending on which flavor you want:		* add this to your /etc/apt/sources.list, as well as /etc/fai/apt/sources.list(to get the correct fai-nfsroot package into the nfsroot) - depending on which flavor you want:
	<pre>		<pre>
-	~~deb http://www.informatik.uni-koeln.de/fai/download sarge koeln~~
-	~~deb http://www.informatik.uni-koeln.de/fai/download etch koeln~~
	deb http://www.informatik.uni-koeln.de/fai/download lenny koeln		deb http://www.informatik.uni-koeln.de/fai/download lenny koeln
	deb http://www.informatik.uni-koeln.de/fai/download experimental koeln		deb http://www.informatik.uni-koeln.de/fai/download experimental koeln
Line 43:		Line 41:
	** [http://www.informatik.uni-koeln.de/fai/index.html#doc Search the fai guide]		** [http://www.informatik.uni-koeln.de/fai/index.html#doc Search the fai guide]
	* [http://www.informatik.uni-koeln.de/fai/doc/man/ Manpages in HTML Format]		* [http://www.informatik.uni-koeln.de/fai/doc/man/ Manpages in HTML Format]
-	* Some more information is also on the [http://www.informatik.uni-koeln.de/fai/ FAI Homepage]

Grml Kernel

2009-11-18T21:54:39Z

Added note about 2.6.31-grml

←Older revision		Revision as of 21:54, 18 November 2009
Line 1:		Line 1:
-	Since some newer Hardware won't work properly with Lenny's 2.6.26 kernel, and it's not always easy to get (working) AUFS modules for newer Debian kernels, it might be easier to use a GRML kernel, since GRML also uses AUFS. Here's how I did it:	+	Since some newer Hardware won't work properly with Lenny's 2.6.26 kernel, and it's not always easy to get (working) AUFS modules for newer Debian kernels, it might be easier to use a GRML kernel, since GRML also uses AUFS. Here's how I did it for 2.6.28, note that 2.6.31-grml/2.6.31-grml64 is now considered stable.

	1. In $FAI_ETC_DIR/NFSROOT, remove any other linux-image or aufs-modules package and add: <pre>PACKAGES aptitude I386		1. In $FAI_ETC_DIR/NFSROOT, remove any other linux-image or aufs-modules package and add: <pre>PACKAGES aptitude I386

Fai SVK howto

2009-11-18T06:05:18Z

←Older revision		Revision as of 06:05, 18 November 2009
Line 1:		Line 1:
	== FAI SVK howto ==		== FAI SVK howto ==

-	* See also [[Fai ~~Subversion~~ howto]] for the non-'distributed' version of these commands, which require a properly setup alioth account and are more appropriate for people who are maintaining large new feature sets and want to share them with others. Actually these commands work for that case too.	+	* See also [[Fai subversion howto]] for the non-'distributed' version of these commands, which require a properly setup alioth account and are more appropriate for people who are maintaining large new feature sets and want to share them with others. Actually these commands work for that case too.

	=== basic operation ===		=== basic operation ===

Fai subversion howto

2009-11-18T05:57:59Z

Anonymous access: + WebSVN

←Older revision		Revision as of 05:57, 18 November 2009
(One intermediate revision not shown.)
Line 1:		Line 1:
-	== ~~FAI subversion howto~~ ==	+	== Anonymous access ==
		+	If you simply want to check out the source code to analyze it or have a look at it.

-	* See also [[Fai SVK howto]] for the 'distributed' version of these commands, which do not require any special accounts and are more appropriate for people who just want to add a few features here and there, and submit their patches to the mailing list for discussion and potential inclusion.	+	svn co svn://svn.debian.org/svn/fai/trunk fai-source
		+
		+	Or read it online using Subversion web access:
		+	* http://svn.debian.org/wsvn/fai/trunk/
		+
		+	=== See also ===
		+	* [[Fai SVK howto]] for the 'distributed' version of these commands, which do not require any special accounts and are more appropriate for people who just want to add a few features here and there, and submit their patches to the mailing list for discussion and potential inclusion.
		+	* [[Main_Page#getting_FAI]]
		+
		+	== Developer access (contributions) ==
		+	If you want to have write access to the FAI sources, because you want to contribute enhancements or fix bugs.

	=== basic operation ===		=== basic operation ===

Developers information

2009-11-17T13:13:03Z

remove link to rails todo list, remove link t ofai-kernels

←Older revision		Revision as of 13:13, 17 November 2009
Line 1:		Line 1:
	== Coordination ==		== Coordination ==
-	* [http://faiwiki.informatik.uni-koeln.de/rails/todos/list todo list] of things most important needed to be done next:
	* [[etch-doc-todo \| List of BUGS important for correct documentation for FAI in Etch]]		* [[etch-doc-todo \| List of BUGS important for correct documentation for FAI in Etch]]
	* [[development plan]] - long term plan, notes and status of some bigger developments		* [[development plan]] - long term plan, notes and status of some bigger developments
Line 23:		Line 22:
	== FAI pages in the Debian Quality Assurance (QA) system ==		== FAI pages in the Debian Quality Assurance (QA) system ==
	* [http://packages.qa.debian.org/f/fai.html source package fai]		* [http://packages.qa.debian.org/f/fai.html source package fai]
-	* [http://packages.qa.debian.org/f/fai-kernels.html source package fai-kernels]

	== Subversion repository access ==		== Subversion repository access ==

Multiple Network Interfaces Howto

2009-11-17T13:08:07Z

Motivation:

←Older revision		Revision as of 13:08, 17 November 2009
(5 intermediate revisions not shown.)
Line 1:		Line 1:
	== Motivation ==		== Motivation ==

-	You want to use FAI to install systems with two or more network interface cards (NIC). By default FAI sets up only one (i.e. the first) network interface dynamically with the following script of the FAIBASE class:	+	You want to use FAI to install systems with two or more network interface cards (NIC).
		+
		+	Installing a client with two active interfaces usually causes trouble as the boot process hangs when ''ipconfig'' tries to set up the 'wrong' interface using DHCP when no DHCP server is present for the respective interface. Also, by default FAI sets up only one (i.e. the first) network interface dynamically with the following script of the ''FAIBASE'' class:

	/var/lib/fai/config/scripts/FAIBASE/30-interface		/var/lib/fai/config/scripts/FAIBASE/30-interface

		+	== Solution ==
		+
		+	...
		+
		+	== Analysis, Troubleshooting ==
		+
		+	; Boot process stops at ''ipconfig'' (client installation over network)
		+	: Check which MAC address ipconfig is trying to set up. Typically, the related interface is not connected to a network that provides a DHCP address for that network card.
		+
		+	== Related Discussions ==
		+
		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01845.html Multiple NICs, partial success, partial weirdness] (Mar 2009)
		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01748.html Dual NIC = hang] (Feb 2009)
		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01553.html tg3 network cards] (Dec 2008)

	[[Category:Howto]]		[[Category:Howto]]

Howtos

2009-11-17T10:53:20Z

HOWTOs for an unknown Debian version:

←Older revision		Revision as of 10:53, 17 November 2009
Line 46:		Line 46:
	* [[Public key authentication for svn over ssh]]		* [[Public key authentication for svn over ssh]]
	* [[DosBoot\|Automatically flash the BIOS and firmware, set the NVRAM and CMOS using DOS tools. This takes place before the FAI installation.]]		* [[DosBoot\|Automatically flash the BIOS and firmware, set the NVRAM and CMOS using DOS tools. This takes place before the FAI installation.]]
-	* [[~~MultipleNics~~\|Systems with multiple network interfaces]]	+	* [[Multiple Network Interfaces Howto\|Systems with multiple network interfaces]]

	[[Category:Development]]		[[Category:Development]]
	[[Category:Howto]]		[[Category:Howto]]
	[[Category:Tutorial]]		[[Category:Tutorial]]

Multiple Network Interfaces Howto

2009-11-17T10:52:27Z

New page: == Motivation == You want to use FAI to install systems with two or more network interface cards (NIC). By default FAI sets up only one (i.e. the first) network interface dynamically with...

New page

== Motivation ==

You want to use FAI to install systems with two or more network interface cards (NIC). By default FAI sets up only one (i.e. the first) network interface dynamically with the following script of the FAIBASE class:

/var/lib/fai/config/scripts/FAIBASE/30-interface

[[Category:Howto]]

Local testing with KVM, VDE and dnsmasq

2009-11-17T10:39:48Z

+ category

←Older revision		Revision as of 10:39, 17 November 2009
Line 56:		Line 56:
	<pre>kvm-img create -f qcow2 faitest.img 5G		<pre>kvm-img create -f qcow2 faitest.img 5G
	vdeq kvm -m 256 -net nic,vlan=1 -net vde,vlan=1,sock=/var/run/vde2/tap0.ctl -hda faitest.img -boot n</pre>		vdeq kvm -m 256 -net nic,vlan=1 -net vde,vlan=1,sock=/var/run/vde2/tap0.ctl -hda faitest.img -boot n</pre>
		+
		+
		+	[[Category:Howto]]

Public key authentication for svn over ssh

2009-11-17T10:35:31Z

+ category

←Older revision		Revision as of 10:35, 17 November 2009
Line 1:		Line 1:
-	Also demonstrated here is the ability to use the sshpass package to scp an identity file from another server (say, a keyserver). To do this, make sure the nfsroot has the sshpass package installed.	+	Also demonstrated here is the ability to use the sshpass package to scp an identity file from another server (say, a keyserver). To do this, make sure the nfsroot has the sshpass package installed.

	<pre>		<pre>
Line 26:		Line 26:
	exit $error		exit $error
	</pre>		</pre>
		+
		+
		+	[[Category:Howto]]

Adding hosts to install client's known hosts

2009-11-17T10:34:33Z

+ category

←Older revision		Revision as of 10:34, 17 November 2009
Line 1:		Line 1:
-	This is pretty easy. Just write a script for the class that echoes the host keys to the client's filesystem:	+	This is pretty easy. Just write a script for the class that echoes the host keys to the client's filesystem:

	<pre>		<pre>
Line 16:		Line 16:
	exit $error		exit $error
	</pre>		</pre>
		+
		+
		+	[[Category:Howto]]

Saving fai-logs via rsyncd

2009-11-17T10:33:42Z

+ category

←Older revision		Revision as of 10:33, 17 November 2009
Line 178:		Line 178:

	* would be nice to combine this rsyncd with the error collecting method of the default savelog.LAST method.		* would be nice to combine this rsyncd with the error collecting method of the default savelog.LAST method.
		+
		+
		+	[[Category:Howto]]

Generate random root password during installation, encrypt and send by mail

2009-11-17T10:33:02Z

+ category

←Older revision		Revision as of 10:33, 17 November 2009
Line 129:		Line 129:

	The perl modules String::Random, Crypt::GPG, and Mail::Sender, that are used by that script, have to be installed on the NFSROOT file system on the install server. GPG is used to encrypt the randomly choosen root password. A gpg key pair has to be generated beforehand. Copy all the files from your gpg home directory to ''/etc/fai/gnupg/'' on the NFSROOT file system, but be shure to omit the secret keyring. For encrypting of the root password we use the same gpg key pair as for [[Encrypting confidential files on the install server\|encrypting sensitive information on the install server]].		The perl modules String::Random, Crypt::GPG, and Mail::Sender, that are used by that script, have to be installed on the NFSROOT file system on the install server. GPG is used to encrypt the randomly choosen root password. A gpg key pair has to be generated beforehand. Copy all the files from your gpg home directory to ''/etc/fai/gnupg/'' on the NFSROOT file system, but be shure to omit the secret keyring. For encrypting of the root password we use the same gpg key pair as for [[Encrypting confidential files on the install server\|encrypting sensitive information on the install server]].
		+
		+
		+	[[Category:Howto]]

Encrypting confidential files on the install server

2009-11-17T10:32:19Z

+ category

←Older revision		Revision as of 10:32, 17 November 2009
Line 291:		Line 291:

	''fai-secrets-install'' copys the gpg keyrings from the directory ''/usr/local/fai/gpg-fai/'' of a secure remote system (defaults to myaccount@mydesktop.example.com) to ''/var/lib/fai/secrets/gnupg/'', decrypts and installs all files from ''/var/lib/fai/secrets/install/'', and deletes the temporary gpg keyrings afterwards.		''fai-secrets-install'' copys the gpg keyrings from the directory ''/usr/local/fai/gpg-fai/'' of a secure remote system (defaults to myaccount@mydesktop.example.com) to ''/var/lib/fai/secrets/gnupg/'', decrypts and installs all files from ''/var/lib/fai/secrets/install/'', and deletes the temporary gpg keyrings afterwards.
		+
		+
		+	[[Category:Howto]]

Using FAI to set up VServers

2009-11-17T10:31:07Z

+ category

←Older revision		Revision as of 10:31, 17 November 2009
Line 10:		Line 10:

	* The third has already worked for a long time with standard FAI - use `vserver xxx build -m debootstrap` to build the vserver, then once it's up, use SoftUpdate to get it up do date with your profile. [[Installing a VServer guest with debootstrap and softupdate]]		* The third has already worked for a long time with standard FAI - use `vserver xxx build -m debootstrap` to build the vserver, then once it's up, use SoftUpdate to get it up do date with your profile. [[Installing a VServer guest with debootstrap and softupdate]]
		+
		+
		+	[[Category:Howto]]

Installing laptops with PCMCIA cards using a floppy disk

2009-11-17T10:30:26Z

+ category

←Older revision		Revision as of 10:30, 17 November 2009
Line 1:		Line 1:
	FAI doesn't come with PCMCIA card support by default, so you need to [[Using_customized_kernels_with_FAI\|create a custom kernel]]. In addition to the configuration options mentioned on that page, ensure that the following options are set to "y".		FAI doesn't come with PCMCIA card support by default, so you need to [[Using_customized_kernels_with_FAI\|create a custom kernel]]. In addition to the configuration options mentioned on that page, ensure that the following options are set to "y".

-	~~<pre>~~
	CONFIG_PCMCIA=y		CONFIG_PCMCIA=y
	CONFIG_NET_PCMCIA=y		CONFIG_NET_PCMCIA=y
	CONFIG_YENTA=y		CONFIG_YENTA=y
-	~~</pre>~~

-	The PCMCIA driver needs some script and a file system for enabling drivers. But since no filesystem is ~~availible~~ before the PCMCIA driver is activated (because you are trying to mount it using NFS), a deadlock occurs. The PCMCIA driver can't load because the nfsroot isn't mounted and the nfsroot can't be mounted because the PCMCIA driver isn't activated. The way to resolve that problem is to use a ramdisk (initrd).	+	The PCMCIA driver needs some script and a file system for enabling drivers. But since no filesystem is available before the PCMCIA driver is activated (because you are trying to mount it using NFS), a deadlock occurs. The PCMCIA driver can't load because the nfsroot isn't mounted and the nfsroot can't be mounted because the PCMCIA driver isn't activated. The way to resolve that problem is to use a ramdisk (initrd).
		+
		+	[[Category:Howto]]

Fai-updater

2009-11-17T10:29:08Z

+ category

←Older revision		Revision as of 10:29, 17 November 2009
Line 71:		Line 71:

	Henning Glawe <glaweh (at) debian (dot) org>		Henning Glawe <glaweh (at) debian (dot) org>
		+
		+
		+	[[Category:Howto]]

FaiReplace

2009-11-17T10:27:47Z

+ category

←Older revision		Revision as of 10:27, 17 November 2009
Line 119:		Line 119:

	perldoc fai-replace		perldoc fai-replace
		+
		+
		+	[[Category:Development]]
		+	[[Category:Howto]]

FaiTemplates

2009-11-17T10:27:14Z

+ category

←Older revision		Revision as of 10:27, 17 November 2009
(One intermediate revision not shown.)
Line 143:		Line 143:
	perldoc lib/FaiTS.pm		perldoc lib/FaiTS.pm
	perldoc bin/fai-ts.pl		perldoc bin/fai-ts.pl
		+
		+
		+	[[Category:Development]]
		+	[[Category:Howto]]

FAIWiki:About

2009-11-13T12:05:36Z

←Older revision		Revision as of 12:05, 13 November 2009
Line 4:		Line 4:

	see [[FAIWiki:General disclaimer]] for more infos.		see [[FAIWiki:General disclaimer]] for more infos.
		+
		+	FAIWiki has been upgraded to MediaWiki V1.12.0.

←Older revision		Revision as of 10:12, 19 November 2009
(One intermediate revision not shown.)
Line 3:		Line 3:
	== See also ==		== See also ==
	* [http://www.informatik.uni-koeln.de/fai/doc/man/fai-chboot.html fai-chboot manpage]		* [http://www.informatik.uni-koeln.de/fai/doc/man/fai-chboot.html fai-chboot manpage]
		+	* [http://www.cyberciti.biz/howto/question/static/linux-kernel-parameters.php Kernel append parameters] (useful for the -k option)
		+
		+	=== Related Discussions ===
		+	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg01603.html fai-chboot -k] (Jan 2009; troubleshooting missing append line bug)

	[[Category:User Manual]]		[[Category:User Manual]]

←Older revision		Revision as of 08:33, 19 November 2009
(One intermediate revision not shown.)
Line 19:		Line 19:
	: Check which MAC address ipconfig is trying to set up. Typically, the related interface is not connected to a network that provides a DHCP address for that network card.		: Check which MAC address ipconfig is trying to set up. Typically, the related interface is not connected to a network that provides a DHCP address for that network card.

-	== Related Discussions ==	+	== See also ==
		+
		+	* [[Multi-ethernet\|Multi-ethernet setup with custom initrd]]
		+
		+	=== Related Discussions ===

	* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg02582.html Two network cards] (Nov 2009)		* [http://www.mail-archive.com/linux-fai@uni-koeln.de/msg02582.html Two network cards] (Nov 2009)