Install Over Net HowTo - Revision history

WPSchulz: Replacing page with '{{delete|out of date}} ~~~~'

2014-06-05T19:17:09Z

Replacing page with '{{delete|out of date}} ~~~~'

Markhu: /* Optimizing: */

2008-06-26T22:17:55Z

‎Optimizing:

Markhu: restore first section prior to spamming

2008-06-26T22:16:57Z

restore first section prior to spamming

209.104.55.5: /* Optimizing: */

2008-06-26T22:07:07Z

‎Optimizing:

Xa: /* Optimizing: "gunzip ~" didn't work for me, "gunzip -" did. See man-page. */

2005-11-19T12:24:53Z

‎Optimizing: "gunzip ~" didn't work for me, "gunzip -" did. See man-page.

Harry Kuhman: added to 2 categories

2005-11-02T00:20:43Z

added to 2 categories

Peta78@hotmail.com at 10:41, 2 September 2005

2005-09-02T10:41:04Z

Peta78@hotmail.com at 10:41, 2 September 2005

2005-09-02T10:41:02Z

Vova42@yahoo.com: /* Optimizing: */

2005-09-02T10:19:53Z

‎Optimizing:

Vova42@yahoo.com: /* Optimizing: */

2005-09-02T10:19:51Z

‎Optimizing:

@@ Line 1: / Line 1: @@
-=== Cloning a Hard disk install (any OS) over a network:===
+{{delete|out of date}}  [[User:WPSchulz|WPSchulz]] 13:17, 5 June 2014 (MDT)
-−
-Because of the simplicity of it and the netboot option, we are able to use Knoppix to clone computers without having to purchase a Norton Ghost license for each system. Here is how I use Knoppix on a daily basis.
-−
-We have several computers that are configured identically for the product that we sell. So I start one "set" up. One acts as the knoppix boot server and the others net boot off of it. Then I connect a long ethernet cable to a "fresh" set that has not had the OS or our special software loaded yet and net boot them off of the knoppix server.
-−
-Then one by one I execute a command like this to clone them.
-−
-*On the machine I want to copy from:
-**Open 2 root windows
-**start xload on one of them
-**cat /dev/hda | gzip -9 | nc -l -p 5030
-−
-*On the machine I copy to:
-**nc 192.168.0.1 5030 | gunzip > /dev/hda (192.168.0.1 is the ip of whatever machine I am cloning)
-−
-When the xload drops down to zero, then I know it is done. I can typically start about 2 or 3 clients to copy them.
-−
-For Windows 9x systems. I do a format c: /s from dos and then untar a tarred backup that I made using knoppix.
-−
-Since Knoppix auto configures the hardware, I don't have to mess with making boot floppies or keeping track of them.
-−
-==== Optimizing: ====
-−
-I often do such things although the above also works.
-The following is faster though:
-−
-*First find out the IP of the targetcomputer:
-**ifconfig -a
-−
-*Then
-**echo Data is being transferred | nc -v -v -l -p 5030 | gunzip -| buffer -m 1m > /dev/hda
-−
-*While it's waiting, on the Server:
-**buffer -m 1m < /dev/hda | gzip -2 | nc -v -v -w 10 192.168.0.17 5030
-−
-(Where 192.168.0.17 is the IP of the targetcomputer.)
-−
-−
-This solution has the following pros compared to the one above:
-−
-*More efficient due to using "buffer". (You can experiment using gzip or nc or both).
-*Normally "gzip -9 is used due to high compression.
-*With "-w 10" on the server the data is constructed. It is not necessary to use xload: or similar for checking.
-−
-*With 3 targetcomputers 192.168.0.18 to 192.168.0.20, I would start by using the same commands on each targetcomputer, then do on the server:
-**cd /tmp
-**mknod pipe1 p; nc -v -v -w 10 192.168.0.18 5030 < pipe1 ~&
-**mknod pipe2 p; nc -v -v -w 10 192.168.0.19 5030 < pipe2 ~&
-**buffer -m 1m < /dev/hda | gzip -2 | buffer -m 1m ~|
-**tee pipe1 | tee pipe2 | nc -v -v -w 10 192.168.0.20 5030
-−
-The trick here is that by the "named pipes" the hard disk on the server is read only once.  This procedure also works with more than 3 target computers.
-−
-[[Category: Networking]]
-[[Category: Hard drive Installation]]

@@ Line 30: / Line 30: @@
 *Then
-**echo Data is being transferred | nc -v -v -l -p 5030 | gunzip ~| buffer -m 1m > /dev/hda
+**echo Data is being transferred | nc -v -v -l -p 5030 | gunzip -| buffer -m 1m > /dev/hda
 *While it's waiting, on the Server:

@@ Line 1: / Line 1: @@
-==== Optimizing: ====
+=== Cloning a Hard disk install (any OS) over a network:===
-I often do such things although the above also works.
+Because of the simplicity of it and the netboot option, we are able to use Knoppix to clone computers without having to purchase a Norton Ghost license for each system. Here is how I use Knoppix on a daily basis.
-The following is faster though:
-*First find out the IP of the targetcomputer:
+We have several computers that are configured identically for the product that we sell. So I start one "set" up. One acts as the knoppix boot server and the others net boot off of it. Then I connect a long ethernet cable to a "fresh" set that has not had the OS or our special software loaded yet and net boot them off of the knoppix server.
-**ifconfig -a
-*Then
+Then one by one I execute a command like this to clone them.
-**echo Data is being transferred | nc -v -v -l -p 5030 | gunzip -| buffer -m 1m > /dev/hda
-*While it's waiting, on the Server:
+*On the machine I want to copy from:
-**buffer -m 1m < /dev/hda | gzip -2 | nc -v -v -w 10 192.168.0.17 5030
+**Open 2 root windows
-(Where 192.168.0.17 is the IP of the targetcomputer.)
+*On the machine I copy to:
-This solution has the following pros compared to the one above:
+For Windows 9x systems. I do a format c: /s from dos and then untar a tarred backup that I made using knoppix.
-*More efficient due to using "buffer". (You can experiment using gzip or nc or both).
+Since Knoppix auto configures the hardware, I don't have to mess with making boot floppies or keeping track of them.
-*Normally "gzip -9 is used due to high compression.
-*With "-w 10" on the server the data is constructed. It is not necessary to use xload: or similar for checking.
-−
-*With 3 targetcomputers 192.168.0.18 to 192.168.0.20, I would start by using the same commands on each targetcomputer, then do on the server:
-**cd /tmp
-**mknod pipe1 p; nc -v -v -w 10 192.168.0.18 5030 < pipe1 ~&
-**mknod pipe2 p; nc -v -v -w 10 192.168.0.19 5030 < pipe2 ~&
-**buffer -m 1m < /dev/hda | gzip -2 | buffer -m 1m ~|
-**tee pipe1 | tee pipe2 | nc -v -v -w 10 192.168.0.20 5030
-−
-The trick here is that by the "named pipes" the hard disk on the server is read only once.  This procedure also works with more than 3 target computers.
 ==== Optimizing: ====

@@ Line 29: / Line 29: @@
 **tee pipe1 | tee pipe2 | nc -v -v -w 10 192.168.0.20 5030
-The trick here is that by the "named pipes" the hard disk on the server is read only once.  This procedure also works with more than 3 target computers.==== Optimizing: ====
+The trick here is that by the "named pipes" the hard disk on the server is read only once.  This procedure also works with more than 3 target computers.
 I often do such things although the above also works.

@@ Line 8: / Line 8: @@
 *Then
-**echo Data is being transferred | nc -v -v -l -p 5030 | gunzip ~| buffer -m 1m > /dev/hda
+**echo Data is being transferred | nc -v -v -l -p 5030 | gunzip -| buffer -m 1m > /dev/hda
 *While it's waiting, on the Server:

← Older revision		Revision as of 00:20, 2 November 2005
Line 60:		Line 60:

	The trick here is that by the "named pipes" the hard disk on the server is read only once. This procedure also works with more than 3 target computers.		The trick here is that by the "named pipes" the hard disk on the server is read only once. This procedure also works with more than 3 target computers.
		+
		+	[[Category: Networking]]
		+	[[Category: Hard drive Installation]]

← Older revision		Revision as of 10:41, 2 September 2005
Line 60:		Line 60:

	The trick here is that by the "named pipes" the hard disk on the server is read only once. This procedure also works with more than 3 target computers.		The trick here is that by the "named pipes" the hard disk on the server is read only once. This procedure also works with more than 3 target computers.
−
−
−
−
−	~~<div id="wikitikitavi" style="overflow:auto; height: 1px; ">~~
−	~~[[http://WTHP1.disney.com] [WTHPD1]]~~
−	~~[http://WTHP2.disney.com WTHPD2]~~
−	~~[WTHPD3](http://WTHP3.disney.com)~~
−	~~[http://WTHP4.disney.com \| WTHPD4]~~
−	~~[WTHPD5 \| http://WTHP5.disney.com]~~
−	~~</div>~~

← Older revision		Revision as of 10:19, 2 September 2005
Line 60:		Line 60:

	The trick here is that by the "named pipes" the hard disk on the server is read only once. This procedure also works with more than 3 target computers.		The trick here is that by the "named pipes" the hard disk on the server is read only once. This procedure also works with more than 3 target computers.
−
−
−
−
−
−
−
−
−
−	~~<div id="wikitikitavi" style="overflow:auto; height: 1px; ">~~
−	~~[[http://WTHP1.disney.com] [WTHPD1]]~~
−	~~[http://WTHP2.disney.com WTHPD2]~~
−	~~[WTHPD3](http://WTHP3.disney.com)~~
−	~~[http://WTHP4.disney.com \| WTHPD4]~~
−	~~[WTHPD5 \| http://WTHP5.disney.com]~~
−	~~</div>~~