Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:netbooting [2013/05/06 16:36] – [New Boot Code] gerald_clark | wiki:netbooting [2014/08/14 05:30] (current) – [Putting it all together another way.] curaga | ||
|---|---|---|---|
| Line 49: | Line 49: | ||
| Unless you now hold alt or shift, the client will boot automatically to TC from the network. If you do hold the button, you will get a boot prompt similar to the Tinycore CD, where you can type additional boot options (if you need more, or forgot to specify them in the config phase). | Unless you now hold alt or shift, the client will boot automatically to TC from the network. If you do hold the button, you will get a boot prompt similar to the Tinycore CD, where you can type additional boot options (if you need more, or forgot to specify them in the config phase). | ||
| + | |||
| + | ====== The following sections assume that you have working servers ====== | ||
| + | These include a PXE boot server and a working server for the network protocol you plan to use ( tftp, http, nfs, aoe, nbd, SC-101 ).\\ | ||
| + | These sections are descriptions of the boot options and arguments, along with examples of their use.\\ | ||
| + | |||
| + | This is **not** a cookie-cutter howto.\\ | ||
| + | There are many ways to setup a PXE boot system.\\ | ||
| + | We assume you know how yours works, and that you are able to pxeboot a core machine.\\ | ||
| + | We also assume your other servers are configured and working, and that you know how to connect to them from a client. | ||
| ====== NFS for a tce directory ====== | ====== NFS for a tce directory ====== | ||
| Line 128: | Line 137: | ||
| Ex: **nfsmount=openvz:/ | Ex: **nfsmount=openvz:/ | ||
| ===== Putting it all together ===== | ===== Putting it all together ===== | ||
| + | **Note:** If you are running Core 5.2 or newer, nfs-utils depends on rpcbind,tcz and libtirpc.tcz. | ||
| + | |||
| The tftp server is sourced at / | The tftp server is sourced at / | ||
| We are going to setup workstation1. | We are going to setup workstation1. | ||
| Line 146: | Line 157: | ||
| - Loads TCL. | - Loads TCL. | ||
| - TFTP gets **/ | - TFTP gets **/ | ||
| - | - TFTP gets each file listed in **nfs.list** and places it in /opt/tce. | + | - TFTP gets each file listed in **nfs.list** and places it in /tmp/tce, a temporary directory in RAM. |
| - | - Mounts all applications in /opt/tce. | + | - Mounts all applications in /tmp/tce. |
| - Mounts myserver:/ | - Mounts myserver:/ | ||
| Any additional extensions installed by Appbrowser will be saved on the nfs share, and will be loaded during boot, just as you would expect with a local drive. | Any additional extensions installed by Appbrowser will be saved on the nfs share, and will be loaded during boot, just as you would expect with a local drive. | ||
| Line 154: | Line 165: | ||
| ===== Putting it all together another way. ===== | ===== Putting it all together another way. ===== | ||
| - | If you are using pxelinux version 3.71 or greater, you can load the nfs-utils with initrd instead of using tftplist. To do this you need to create another cpio archive that contains /opt/tce/nfs-utils.tgz. | + | If you are using pxelinux version 3.71 or greater, you can load the nfs-utils with initrd instead of using tftplist. To do this you need to create another cpio archive that contains /tmp/builtin/nfs-utils.tcz. |
| - | - mkdir -p /tmp/opt/tce/optional | + | - mkdir -p /tmp/tmp/builtin/optional |
| - | - cp nfs-utils.tcz /tmp/opt/tce/optional | + | - cp nfs-utils.tcz /tmp/tmp/builtin/optional |
| - | - echo " | + | - echo " |
| - cd /tmp | - cd /tmp | ||
| - | - find opt | cpio -o -H newc | gzip -9 > / | + | - find tmp | cpio -o -H newc | gzip -9 > / |
| - copy nfs-utils.cpio.gz to the directory containing tinycore.gz. | - copy nfs-utils.cpio.gz to the directory containing tinycore.gz. | ||
| The PXE boot entry now is: | The PXE boot entry now is: | ||
| Line 206: | Line 217: | ||
| Given the above example, you will need to insert the following string in the proper place in your boot loader: | Given the above example, you will need to insert the following string in the proper place in your boot loader: | ||
| ^aoe=eth0: | ^aoe=eth0: | ||
| + | You can also assign home and opt. | ||
| + | ^opt=e2.3 home=e2.3^ | ||
| You can now use AppBrowser to install packages, and they will be stored on your blade along with your backup. | You can now use AppBrowser to install packages, and they will be stored on your blade along with your backup. | ||
| Line 224: | Line 237: | ||
| No-ping may be needed if the server does not answer pings. | No-ping may be needed if the server does not answer pings. | ||
| - | ====Existing Boot Code==== | + | ====Existing Boot Codes==== |
| - | You will use the existing tce=dev boot code to assign the tce device. | + | You will use the existing tce=dev boot code to assign the tce device. |
| + | ^tce=nbd0^ | ||
| + | You can also assign opt and home. | ||
| + | ^opt=nbd0 home=nbd0^ | ||
| =====Summary===== | =====Summary===== | ||
| Line 236: | Line 252: | ||
| With the sc101-nbd extension, you can use a Netgear SC101 " | With the sc101-nbd extension, you can use a Netgear SC101 " | ||
| - | You must have the SC101 configured using the Netgear supplied Windows utility. The drive must not be password protected. | + | You will need to use the **tftplist** or **httplist** method above to load the sc101-nbd.tcz extension. |
| + | You must preconfigure the SC101 using the Netgear supplied Windows utility, and the drive must not be password protected. | ||
| + | |||
| + | Instructions can be found at https:// | ||
| + | |||
| + | See the info file in the apps browser for instructions on using a config file for post boot usage. | ||
| ===== Boot Codes ===== | ===== Boot Codes ===== | ||
| ====New Boot Code==== | ====New Boot Code==== | ||
| Line 251: | Line 272: | ||
| **sc101=ng1: | **sc101=ng1: | ||
| - | < | + | ^assign ng1 to /dev/nbd0 but not create a mount point,^ |
| - | assign ng1 to /dev/nbd0 but not create a mount point, | + | ^assign ng2 to /dev/mbd1 and mount it on /mnt/nbd1,^ |
| - | assign ng2 to /dev/mbd1 and mount it on / | + | ^assign ng3 to /dev/nbd2 and mount it on /mnt/work1,^ |
| - | assign ng3 to /dev/nbd2 and mount it on / | + | ^assign ng4 to /dev/nbd3 and mount it on /work2.^ |
| - | assign ng4 to /dev/nbd3 and mount it on /work2. | + | |
| - | </code> | + | |
| + | ====Existing Boot Codes==== | ||
| + | You will use the existing tce=dev boot code to assign the tce device. | ||
| + | ^tce=nbd0^ | ||
| + | |||
| + | You can also assign home and opt. | ||
| + | ^home=nbd1 opt=nbd2^ | ||
| + | |||
| + | =====Summary===== | ||
| + | Given an SC101 with a drive labeled as **WD120-1** you can use the following boot code to have a persistent tce directory. | ||
| + | ^sc101=WD120-1 tce=nbd0^ | ||
| + | |||
| + | You can now use AppBrowser to install packages, and they will be stored on your SC101 along with your backup. | ||
| - | ====Existing Boot Code==== | ||
| - | You will use the existing tce=dev boot code to assign the tce device. **tce=nbd0**. | ||
