Difference between revisions of "Install Over Net HowTo"

Revision as of 00:20, 2 November 2005

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.==== 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.