Difference between revisions of "TFTP server disclaimer"
Line 1: | Line 1: | ||
− | + | [[Category:Linux]] | |
=Maintenance advise= | =Maintenance advise= |
Latest revision as of 14:19, 28 January 2015
Maintenance advise
For each kernel you add, you should create a small README file.
Ex: /tftpboot/images/README.txt or /tftpboot/sources-images/README.txt
# README file version 1.1 - January 2015 - Guillaume Diaz
# Image "trusty" ==> Ubuntu 14.04 LTS kernel 3.13.0-44-generic | January 2015
Global disclaimer
I advise you to put the following test inside your /tftpboot/README.txt directory:
# README file version 1.1 - January 2015 - Guillaume Diaz
#--------------------------------
# IMAGES CREATION
#--------------------------------
You can have many images over here.
Definition:
image = a kernel that will be loaded by the NetBoot client.
Composition:
each image must have a "vmlinuz" + "initrd.img" file.
No matter where you pick these files from - locally or remotely - but don't forget to:
* Configure the "/etc/initramfs-tools/initramfs.conf" to support NetBoot + NFS
* Enable all kernel modules + server reboot before copying the "vmlinuz"
* Don't forget to do a "mkinitramfs" on the target "initrd.img" using your own 'initramfs.conf'
* Don't forget to copy the kernel sources files into the target netboot NFS share in "/lib/modules/`uname -r`" + "/usr/src/linux-headers-`uname -r`"
Hint:
If you plan to serve different flavors of the same distribution (ex: ubuntu | Xubuntu | Lubuntu) then you can use the same kernel for all of them.
#--------------------------------
# IMAGES USAGE
#--------------------------------
Each image matches a specific kernel version.
>> That's the version you have to install on your NFS image!
Also, you need to put the /tftboot/source-images kernel modules + libraries into the target NFS image.
Enjoy!