Linux netbooting - Revision history

Kingdavid: /* Building a linux system from scratch */

2008-02-07T15:08:47Z

Building a linux system from scratch

← Older revision		Revision as of 17:08, 7 February 2008
Line 1:		Line 1:




	Instructions follow on how to netboot using Ubuntu Linux.		Instructions follow on how to netboot using Ubuntu Linux.

Line 194:		Line 190:

	If you are logging in from bash		If you are logging in from bash

	change the /etc/passwd file to:		change the /etc/passwd file to:
	root:x:0:0:root:/root:/bin/bash		root:x:0:0:root:/root:/bin/bash

Kingdavid at 15:08, 7 February 2008

2008-02-07T15:08:22Z

@@ Line 1: / Line 1: @@
 Instructions follow on how to netboot using Ubuntu Linux.
@@ Line 183: / Line 187: @@
 Under devices->character devices
 [*] Unix98 PTY support

Kingdavid: /* Setup Filesystem */

2008-02-04T14:40:17Z

Setup Filesystem

← Older revision		Revision as of 16:40, 4 February 2008
Line 176:		Line 176:
	en		en
	local		local

			sudo dpkg-reconfigure locales

			5) In you kernel configuraion

			Under devices->character devices
			[*] Unix98 PTY support

Kingdavid at 13:28, 29 January 2008

2008-01-29T13:28:42Z

← Older revision		Revision as of 15:28, 29 January 2008
Line 163:		Line 163:

	3) Change the policy of the init		3) Change the policy of the init


			Add /usr/sbin/policy.init.d

			#!/bin/sh
			exit 101

			4) Add locale settings

			/var/lib/locales/supported.d/

			en
			local

Kingdavid at 12:58, 29 January 2008

2008-01-29T12:58:50Z

← Older revision		Revision as of 14:58, 29 January 2008
Line 142:		Line 142:

	3) Restart one of the client machines and check that it boots successfully		3) Restart one of the client machines and check that it boots successfully


			''How to build a gutsy file system''

			After chroot into file system

			1) Remove udev

			apt-get remove udev

			2) Get slackware devices

			[http://www.slackware.at/data/slackware-9.0/slackware/a/devs-2.3.1-i386-13.tgz Slackware devices]

			Copy these to root of chroot environemnt

			Untar in root

			tar zxvf devs-2.3.1-i386-13.tgz /

			3) Change the policy of the init

Kingdavid at 17:01, 27 April 2006

2006-04-27T17:01:48Z

← Older revision		Revision as of 19:01, 27 April 2006
Line 131:		Line 131:


	'''II root file system on server'''		'''II Create root file system on the server'''

	1) Login to the server containing these files		1) Login to the server containing these files

Kingdavid at 17:00, 27 April 2006

2006-04-27T17:00:20Z

@@ Line 1: / Line 1: @@
 Instructions follow on how to netboot using Ubuntu Linux.
 =Client Setup=
@@ Line 51: / Line 18: @@
   Device Drivers  --->
    Networking support  --->
     Networking options  --->
       [*] Packet socket
@@ Line 115: / Line 84: @@
 APPEND ip=dhcp root=/dev/nfs nfsroot=172.20.1.1:/export/linux/ubuntu ramdisk_size=16432 initrd=initrd.img-2.6.12
 ) Restart one of the client machines and check that it boots successfully

Kingdavid at 13:30, 25 April 2006

2006-04-25T13:30:37Z

← Older revision		Revision as of 15:30, 25 April 2006
Line 37:		Line 37:
	==Create Linux Kernel==		==Create Linux Kernel==

	To get a kernel up and running it needs firstly to boot itself and then run some file system drivers, or even network drivers in the case of NFS, to allow the file systems to mount and let the operating system boot normally. To do this the kernel needs to mount a RAM disk which contains all the drivers necessary for boot up. This RAM disk is called an initrd file or "initial ramdisk file" Below are the steps to firstly create the kernel with the necessary options ~~and secondly the~~ ramdisk file with the required drivers.		To get a kernel up and running it needs firstly to boot itself and then run some file system drivers, or even network drivers in the case of NFS, to allow the file systems to mount and let the operating system boot normally. To do this the kernel needs to mount a RAM disk which contains all the drivers necessary for boot up. This RAM disk is called an initrd file or "initial ramdisk file" Below are the steps to firstly create the kernel with the necessary options then create a ramdisk file with the required drivers and finally configure the server to network boot this kernel

	'''I Build the kernel image'''		'''I Build the kernel image'''
Line 86:		Line 86:
	sudo cp -r /usr/modules/<current kernel version> /usr/modules/<current kernel version>.bak		sudo cp -r /usr/modules/<current kernel version> /usr/modules/<current kernel version>.bak

	3) Install the module drivers (note this will install all the drivers in the directory /lib/modules/<kernel version> If your current kernel version is the same as the kernel source you are building it will overwrite all your current kernel modules but step 7 would have created a backup - after this process however you will need to restore your original kernel modules using the backup		3) Install the module drivers (note this will install all the drivers in the directory /lib/modules/<kernel version> If your current kernel version is the same as the kernel source you are building it will overwrite all your current kernel modules but step 2 would have created a backup - after this process however you will need to restore your original kernel modules using the backup

	sudo make modules_install		sudo make modules_install
Line 103:		Line 103:

	1) Login to the server containing these files		1) Login to the server containing these files

			ssh name@server

			2) Copy the kernel and the initrd file to the tftpboot directory

			cp vmlinuz.david initrd.img-2.6.12 /export/tftpboot

			3) Edit the pxelinux.cfg/defualt file to boot your new kernel

			DEFAULT vmlinuz.david
			APPEND ip=dhcp root=/dev/nfs nfsroot=172.20.1.1:/export/linux/ubuntu ramdisk_size=16432 initrd=initrd.img-2.6.12

			4) Restart one of the client machines and check that it boots successfully

Kingdavid at 13:21, 25 April 2006

2006-04-25T13:21:03Z

← Older revision		Revision as of 15:21, 25 April 2006
Line 38:		Line 38:

	To get a kernel up and running it needs firstly to boot itself and then run some file system drivers, or even network drivers in the case of NFS, to allow the file systems to mount and let the operating system boot normally. To do this the kernel needs to mount a RAM disk which contains all the drivers necessary for boot up. This RAM disk is called an initrd file or "initial ramdisk file" Below are the steps to firstly create the kernel with the necessary options and secondly the ramdisk file with the required drivers.		To get a kernel up and running it needs firstly to boot itself and then run some file system drivers, or even network drivers in the case of NFS, to allow the file systems to mount and let the operating system boot normally. To do this the kernel needs to mount a RAM disk which contains all the drivers necessary for boot up. This RAM disk is called an initrd file or "initial ramdisk file" Below are the steps to firstly create the kernel with the necessary options and secondly the ramdisk file with the required drivers.

			'''I Build the kernel image'''

	1) Start the kernel configuration program in /usr/src/<linux kernel version>		1) Start the kernel configuration program in /usr/src/<linux kernel version>
Line 74:		Line 76:
	scp bzImage djohnson@meshy.dhcp:~/vmlinuz.david		scp bzImage djohnson@meshy.dhcp:~/vmlinuz.david

	6) Make the kernel module drivers		'''II Build the initial ramdisk file (initrd)'''

			1) Make the kernel module drivers

	sudo make modules		sudo make modules

	7) Backup your current kernel modules (<current kernel version> is your current kernel e.g. 2.6.10-12		2) Backup your current kernel modules (<current kernel version> is your current kernel e.g. 2.6.10-12

	sudo cp -r /usr/modules/<current kernel version> /usr/modules/<current kernel version>.bak		sudo cp -r /usr/modules/<current kernel version> /usr/modules/<current kernel version>.bak

	8) Install the module drivers (note this will install all the drivers in the directory /lib/modules/<kernel version> If your current kernel version is the same as the kernel source you are building it will overwrite all your current kernel modules but step 7 would have created a backup - after this process however		3) Install the module drivers (note this will install all the drivers in the directory /lib/modules/<kernel version> If your current kernel version is the same as the kernel source you are building it will overwrite all your current kernel modules but step 7 would have created a backup - after this process however you will need to restore your original kernel modules using the backup

	sudo make modules_install		sudo make modules_install

	8) Create the initrd ramdisk image		4) Create the initrd ramdisk image

	sudo mkinitrd -o initrd.img-2.6.12 2.6.12		sudo mkinitrd -o initrd.img-2.6.12 2.6.12

			The mkinitrd script does a few default things here. First it looks at /etc/mkinitrd/mkinitrd.conf to see which modules it must include. In the example above it will look in /lib/modules/2.6.12 to find all the modules to build into the initrd.img-2.6.12 file

			5) Copy the initrd file to the server

			scp initrd.img-2.6.12 djohnson@meshy.dhcp:~

			'''III Setup the server to run the kernel with the initrd file'''

			1) Login to the server containing these files

Kingdavid at 13:09, 25 April 2006

2006-04-25T13:09:11Z

@@ Line 37: / Line 37: @@
 ==Create Linux Kernel==
-There are two types of Kernel images you can build. The first is an image which contains all the necessary file system drivers, or even network drivers in the case of NFS, to allow the file systems to mount and let the operating system boot normally. The second type of kernel image puts all the drivers in a file which is mounted in RAM as a RAM disk. This is known as an initrd file. initrd stands for "initial ramdisk"
+To get a kernel up and running it needs firstly to boot itself and then run some file system drivers, or even network drivers in the case of NFS, to allow the file systems to mount and let the operating system boot normally. To do this the kernel needs to mount a RAM disk which contains all the drivers necessary for boot up. This RAM disk is called an initrd file or "initial ramdisk file" Below are the steps to firstly create the kernel with the necessary options and secondly the ramdisk file with the required drivers.
-'''I Create kernel image with module drivers built in'''
+) Start the kernel configuration program in /usr/src/<linux kernel version>
   sudo make menuconfig
@@ Line 61: / Line 59: @@
     <*> NFS file system support
      [*] Root file system on NFS
 ) Make the kernel
@@ Line 78: / Line 74: @@
   scp bzImage djohnson@meshy.dhcp:~/vmlinuz.david
-'''II Create kernel image without module drivers built in'''
+ sudo make modules
-) Start the kernel configuration program
+) Backup your current kernel modules (<current kernel version> is your current kernel e.g. 2.6.10-12
-  sudo make menuconfig
+  sudo cp -r /usr/modules/<current kernel version> /usr/modules/<current kernel version>.bak
-) Set the following options on the kernel configuration menus
+) Install the module drivers (note this will install all the drivers in the directory /lib/modules/<kernel version> If your current kernel version is the same as the kernel source you are building it will overwrite all your current kernel modules but step 7 would have created a backup - after this process however
   sudo make modules_install
@@ Line 128: / Line 89: @@
   sudo mkinitrd -o initrd.img-2.6.12 2.6.12