Arduino Sever PXE Script - Revision history

Jvaughters at 21:59, 8 November 2012

2012-11-08T21:59:11Z

← Older revision		Revision as of 21:59, 8 November 2012
Line 1:		Line 1:
		+	<anyweb>http://combustory.com/wiki/ads/ad_rtc.html</anyweb>
		+
		+	{{default}}
		+
		+	<anyweb>http://combustory.com/wiki/ads/ad_rtc_1.html</anyweb>
		+
		+
	=Introduction=		=Introduction=
	Note:This page is related to the [[Arduino Server]] article. Without reading that article, this one will probably not make much sense.		Note:This page is related to the [[Arduino Server]] article. Without reading that article, this one will probably not make much sense.

Jvaughters at 01:06, 8 November 2012

2012-11-08T01:06:04Z

← Older revision		Revision as of 01:06, 8 November 2012
Line 91:		Line 91:
	* Update the root file system per instructions above.		* Update the root file system per instructions above.
	* Next time you reboot, you should be able to access ssh without accepting a key		* Next time you reboot, you should be able to access ssh without accepting a key
−	~~==Add Packages to the server==~~
−	~~There are literally tons of packages that can be added to the server. I am sure I will be adding more as I go along. This is how you add packages to your PXE server.~~
−
−	* Go to this address and look for packages you would like to add - http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/
−	* Find the package you are interested in adding and you will see several files for each package
−	** .info - This is a brief description of the package
−	** .dep - This file is very important if it exists. You need to download this file and download the packages you find in the file as well as any dependencies that those packages need as well.
−	** .md5.txt - This file can be used to verify the file after downloaded. I will leave it to the reader to investigate.
−	** .tcz - This is the actual package you need to download
−	* We will use the vino.tcz package as an example.

	==Change the tc_pxe directory name==		==Change the tc_pxe directory name==
Line 114:		Line 104:
	==Other Configuration Ideas==		==Other Configuration Ideas==
	* Use multiple servers with different image directories. Study how to boot PXE by MAC address.		* Use multiple servers with different image directories. Study how to boot PXE by MAC address.
−	*	+	* Add packages to the PXE server.

	=Troubleshooting=		=Troubleshooting=

Jvaughters at 03:25, 6 November 2012

2012-11-06T03:25:03Z

← Older revision		Revision as of 03:25, 6 November 2012
Line 99:		Line 99:
	** .dep - This file is very important if it exists. You need to download this file and download the packages you find in the file as well as any dependencies that those packages need as well.		** .dep - This file is very important if it exists. You need to download this file and download the packages you find in the file as well as any dependencies that those packages need as well.
	** .md5.txt - This file can be used to verify the file after downloaded. I will leave it to the reader to investigate.		** .md5.txt - This file can be used to verify the file after downloaded. I will leave it to the reader to investigate.
−	** .~~tgz~~ - This is the actual package you need to download	+	** .tcz - This is the actual package you need to download
		+	* We will use the vino.tcz package as an example.

	==Change the tc_pxe directory name==		==Change the tc_pxe directory name==

Jvaughters: /* Change the tc_pxe directory name */

2012-11-06T01:50:32Z

Change the tc_pxe directory name

← Older revision		Revision as of 01:50, 6 November 2012
Line 91:		Line 91:
	* Update the root file system per instructions above.		* Update the root file system per instructions above.
	* Next time you reboot, you should be able to access ssh without accepting a key		* Next time you reboot, you should be able to access ssh without accepting a key
		+	==Add Packages to the server==
		+	There are literally tons of packages that can be added to the server. I am sure I will be adding more as I go along. This is how you add packages to your PXE server.
		+
		+	* Go to this address and look for packages you would like to add - http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/
		+	* Find the package you are interested in adding and you will see several files for each package
		+	** .info - This is a brief description of the package
		+	** .dep - This file is very important if it exists. You need to download this file and download the packages you find in the file as well as any dependencies that those packages need as well.
		+	** .md5.txt - This file can be used to verify the file after downloaded. I will leave it to the reader to investigate.
		+	** .tgz - This is the actual package you need to download
		+
	==Change the tc_pxe directory name==		==Change the tc_pxe directory name==
−	You may want to use your own directory names and if you want to have multiple computers using different images, then you will want to consider changing the tc_pxe directory name.	+	You may want to use your own directory names and if you want to have multiple computers using different images, then you will want to consider changing the tc_pxe directory name.
		+
		+	* Change directory to ard_srv_1 from tc_pxe
		+	sed -i 's/tc_pxe/ard_srv_1/g' /tftpboot/tc_pxe/cde/onboot_x.lst
		+	sed -i 's/tc_pxe/ard_srv_1/g' /tftpboot/tc_pxe/pxelinux.cfg/default
		+	cd /tftpboot
		+	mv tc_pxe ard_srv_1
		+	* Point your PXE set up to the new directory and you are good to go.

−	~~TODO: I need~~ to ~~outline all the changes to the scripts~~	+	==Other Configuration Ideas==
		+	* Use multiple servers with different image directories. Study how to boot PXE by MAC address.
		+	*

	=Troubleshooting=		=Troubleshooting=

Jvaughters: /* Replace PXE TinyCore System */

2012-11-06T00:13:37Z

Replace PXE TinyCore System

← Older revision		Revision as of 00:13, 6 November 2012
Line 100:		Line 100:

	==Replace PXE TinyCore System==		==Replace PXE TinyCore System==
−	The best part of using TinyCore and this script is that if for some reason you messed up, you just start from scratch and it only takes a few minutes to run the script again as long as you do not delete the tc_downloads directory. ~~Even~~ more useful is if you had a running system from the start, then messed it up, all you have to do is delete the tc_pxe ~~directory in the tftpboot~~ directory and then copy it from the ~/my_tinycore_dir directory.	+	The best part of using TinyCore and this script is that if for some reason you messed up, you just start from scratch and it only takes a few minutes to run the script again as long as you do not delete the tc_downloads directory. It is even more useful if you had a running system from the start, then messed it up, then all you have to do is delete the /tftpboot/tc_pxe directory and then copy it from the ~/my_tinycore_dir directory.
	* Remove PXE set up and replace it with the default system created by script		* Remove PXE set up and replace it with the default system created by script
	rm -rf /tftpboot/tc_pxe		rm -rf /tftpboot/tc_pxe

Jvaughters at 00:10, 6 November 2012

2012-11-06T00:10:50Z

← Older revision		Revision as of 00:10, 6 November 2012
Line 42:		Line 42:
	Any changes you make on the server are not kept once you reboot. To change any files on the root file system you will need to change it in the ''/tftboot/tc_pxe/tc_pxe_dev/core_root'' directory. This is the root directory for your server. Then you will need to run a script to compact the root file system and copy it to your ''/tftpboot/tc_pxe'' directory. You can also use chroot commands to modify settings that that are needed to be done root access.		Any changes you make on the server are not kept once you reboot. To change any files on the root file system you will need to change it in the ''/tftboot/tc_pxe/tc_pxe_dev/core_root'' directory. This is the root directory for your server. Then you will need to run a script to compact the root file system and copy it to your ''/tftpboot/tc_pxe'' directory. You can also use chroot commands to modify settings that that are needed to be done root access.

−	==Best Practices==	+	===Best Practices===
	If you have created a bootable PXE system, then you are off to a great start. Since the configuration part can take some time, you may want to save the file periodically. That way if you make a mistake, you do not loose all your effort. Fortunately this is a breeze. You only need to copy one file. In a jam, you can extract this file and create known good root file system.		If you have created a bootable PXE system, then you are off to a great start. Since the configuration part can take some time, you may want to save the file periodically. That way if you make a mistake, you do not loose all your effort. Fortunately this is a breeze. You only need to copy one file. In a jam, you can extract this file and create known good root file system.

		+	* Create backup of root file system
	cd /tftpboot/tc_pxe/tc_pxe_dev/ard-core.gz /tftpboot/tc_pxe/tc_pxe_dev/ard-core.gz.bak		cd /tftpboot/tc_pxe/tc_pxe_dev/ard-core.gz /tftpboot/tc_pxe/tc_pxe_dev/ard-core.gz.bak
		+	* restore the backup of root file system
		+	cd /tftpboot/tc_pxe/tc_pxe_dev/core_root
		+	rm -rf /tftpboot/tc_pxe/tc_pxe_dev/core_root/*
		+	zcat ../ard-core.gz.bak \| sudo cpio -i -H newc -d

−		+	===Create New Root File System===
	How to change files in your root file system:		How to change files in your root file system:
	* Make sure you have root access		* Make sure you have root access

Jvaughters at 23:23, 5 November 2012

2012-11-05T23:23:29Z

← Older revision		Revision as of 23:23, 5 November 2012
Line 37:		Line 37:

	=Further Configuration=		=Further Configuration=
−	Hopefully you were able to get a server running. That is a big part of this set up. In this section we will discuss how to modify your system further to make the it even more useful.	+	Hopefully you were able to get a server running. That is a big part of this set up and the computer is useful even in this state, but I believe you will find it beneficial to make some more changes. In this section we will discuss how to modify your system further to make the it even more useful.

	==Root File System==		==Root File System==
	Any changes you make on the server are not kept once you reboot. To change any files on the root file system you will need to change it in the ''/tftboot/tc_pxe/tc_pxe_dev/core_root'' directory. This is the root directory for your server. Then you will need to run a script to compact the root file system and copy it to your ''/tftpboot/tc_pxe'' directory. You can also use chroot commands to modify settings that that are needed to be done root access.		Any changes you make on the server are not kept once you reboot. To change any files on the root file system you will need to change it in the ''/tftboot/tc_pxe/tc_pxe_dev/core_root'' directory. This is the root directory for your server. Then you will need to run a script to compact the root file system and copy it to your ''/tftpboot/tc_pxe'' directory. You can also use chroot commands to modify settings that that are needed to be done root access.
		+
		+	==Best Practices==
		+	If you have created a bootable PXE system, then you are off to a great start. Since the configuration part can take some time, you may want to save the file periodically. That way if you make a mistake, you do not loose all your effort. Fortunately this is a breeze. You only need to copy one file. In a jam, you can extract this file and create known good root file system.
		+
		+	cd /tftpboot/tc_pxe/tc_pxe_dev/ard-core.gz /tftpboot/tc_pxe/tc_pxe_dev/ard-core.gz.bak
		+

	How to change files in your root file system:		How to change files in your root file system:
Line 73:		Line 79:
	* If your Tiny Core system is already booted, then we can transfer over the keys to the root file system with scp		* If your Tiny Core system is already booted, then we can transfer over the keys to the root file system with scp
	mkdir /tftboot/tc_pxe/tc_pxe_dev/core_root/etc/dropbear		mkdir /tftboot/tc_pxe/tc_pxe_dev/core_root/etc/dropbear
−	scp	+	* Log into your TinyCore computer via ssh (Change ip's to match your network, accept ssh key and enter password), then copy key files over via scp
−	~~Unfinished~~	+	ssh tc@192.168.1.150
		+	sudo scp /etc/dropbear/dropbear_dss_host_key root@192.168.1.1:/tftpboot/tc_pxe/tc_pxe_dev/core_root/etc/dropbear/
		+	sudo scp /etc/dropbear/dropbear_rsa_host_key root@192.168.1.1:/tftpboot/tc_pxe/tc_pxe_dev/core_root/etc/dropbear/
		+	exit
		+	* Update the root file system per instructions above.
		+	* Next time you reboot, you should be able to access ssh without accepting a key
		+	==Change the tc_pxe directory name==
		+	You may want to use your own directory names and if you want to have multiple computers using different images, then you will want to consider changing the tc_pxe directory name.
		+
		+	TODO: I need to outline all the changes to the scripts

	=Troubleshooting=		=Troubleshooting=
		+
		+
		+	==Replace PXE TinyCore System==
		+	The best part of using TinyCore and this script is that if for some reason you messed up, you just start from scratch and it only takes a few minutes to run the script again as long as you do not delete the tc_downloads directory. Even more useful is if you had a running system from the start, then messed it up, all you have to do is delete the tc_pxe directory in the tftpboot directory and then copy it from the ~/my_tinycore_dir directory.
		+	* Remove PXE set up and replace it with the default system created by script
		+	rm -rf /tftpboot/tc_pxe
		+	cp -r ~/my_tinycore_dir/tc_pxe /tftpboot/tc_pxe
		+	* More drastic measure to remove the default system and re-run script
		+	rm -rf ~/my_tinycore_dir/tc_pxe
		+	cd ~/my_tinycore_dir
		+	./tc_pxe_script
		+
	=TinyCore PXE build script=		=TinyCore PXE build script=
	<source lang="bash">		<source lang="bash">

Jvaughters: /* ssh via dropbear */

2012-11-05T02:22:08Z

ssh via dropbear

← Older revision		Revision as of 02:22, 5 November 2012
Line 64:		Line 64:

	==ssh via dropbear==		==ssh via dropbear==
−	~~I personally~~ plan on using this server for more than just an [[Arduino Server]] so I ~~have~~ included ~~ssh~~ in ~~this set up~~. You can also use ssh to transfer files that can be used as a method other than the default set up of connecting the serial ports to a network TCP port. To use ssh on TinyCore linux, we have loaded a package called dropbear. We will need to change our root file system to create passwords for the tc and root users. We will also want to copy over the server identifying keys to prevent new keys every time the server reboots. This can be quite annoying when trying to access the server and getting rejected because of the keys.	+	If you plan on using this server for more than just an [[Arduino Server]] I recommend you configure ssh, which I included in the additional packages. You can also use ssh to transfer files that can be used as a method other than the default set up of connecting the serial ports to a network TCP port. To use ssh on TinyCore linux, we have loaded a package called dropbear. We will need to change our root file system to create passwords for the tc and root users. We will also want to copy over the server identifying keys to prevent new keys every time the server reboots. This can be quite annoying when trying to access the server and getting rejected because of the keys.

	Steps to use ssh:		Steps to use ssh:

Jvaughters at 02:12, 5 November 2012

2012-11-05T02:12:16Z

← Older revision		Revision as of 02:12, 5 November 2012
Line 2:		Line 2:
	Note:This page is related to the [[Arduino Server]] article. Without reading that article, this one will probably not make much sense.		Note:This page is related to the [[Arduino Server]] article. Without reading that article, this one will probably not make much sense.

−	This article provides instructions to build a complete PXE directory for the [http://distro.ibiblio.org/tinycorelinux/ Tiny Core Linux] Distribution. You will be able to run the script below and then move the created directory to the /tftpboot directory and point your dhcp server to the new directory. This will allow you to boot a wide range of computers via the network. The script is focused on taking care of the details to configure an [[Arduino Server]] that basically acts as a terminal server for connected Arduinos. The server is much more capable than just serving Arduinos, but I will let you investigate anything outside of the [Arduino Server]] focus.	+	This article provides instructions to build a complete PXE directory for the [http://distro.ibiblio.org/tinycorelinux/ Tiny Core Linux] Distribution. You will be able to run the script below and then move the created directory to the /tftpboot directory and point your dhcp server to the new directory. This will allow you to boot a wide range of computers via the network. The script is focused on taking care of the details to configure an [[Arduino Server]] that basically acts as a terminal server for connected Arduinos. The server is much more capable than just serving Arduinos, but I will let you investigate anything outside of the [[Arduino Server]] focus.

	=Assumptions=		=Assumptions=
Line 72:		Line 72:
	chroot /tftpboot/tc_pxe/tc_pxe_dev/core_root/ passwd root		chroot /tftpboot/tc_pxe/tc_pxe_dev/core_root/ passwd root
	* If your Tiny Core system is already booted, then we can transfer over the keys to the root file system with scp		* If your Tiny Core system is already booted, then we can transfer over the keys to the root file system with scp
−		+	mkdir /tftboot/tc_pxe/tc_pxe_dev/core_root/etc/dropbear
		+	scp
	Unfinished		Unfinished

Jvaughters: /* ssh via dropbear */

2012-11-05T02:06:52Z

ssh via dropbear

← Older revision		Revision as of 02:06, 5 November 2012
Line 72:		Line 72:
	chroot /tftpboot/tc_pxe/tc_pxe_dev/core_root/ passwd root		chroot /tftpboot/tc_pxe/tc_pxe_dev/core_root/ passwd root
	* If your Tiny Core system is already booted, then we can transfer over the keys to the root file system with scp		* If your Tiny Core system is already booted, then we can transfer over the keys to the root file system with scp
		+
		+	Unfinished

	=Troubleshooting=		=Troubleshooting=