Supposing you already have the crossover cable to connect both machines, you need to see if both machines have their ethernet interfaces configured in the same network.
You need to enter the command "ifconfig eth0" on both machines; the answer will be something like above:
Code:
eth0 Link encap:Ethernet HWaddr 00:14:2A:D6:CC:C6
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:23 Base address:0xe400
You have to be sure that both machines are in the same network, that is,
192.168.0.x but have different addresses, for instance, one should be
192.168.0.1 and the other
192.168.0.2.
If you don't have it on this condition, you can setup the network with the above commands, one for each machine:
Code:
# Machine A
ifconfig eth0 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
# Machine B
ifconfig eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255
These configuration will not be preserved on the boot. If you want to preserve configuration, on the fedora enter "netconfig" to setup the addresses and on the slackware, edit /etc/rc.d/rc.inet1.conf to specify the addresses.
When the configurations seem Ok, you can ping each other to see if the machines are really connected:
Code:
# Machine A
ping 192.168.0.2
# Machine B
ping 192.168.0.1
If it's all working, you will see a sequence like the above:
Code:
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=0.066 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.057 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.059 ms
Hit Ctrl-c to finish ping.
Now you need some kind of remote shell in both machines, like
ssh or
rsh. I don't want to setup flames here, but for a local network, I prefer rsh; however, you should already have ssh installed on both machines; you need at least one with ssh which is the client and the other with sshd, the ssh server. You can check if both are installed with the command:
Code:
which ssh
which sshd
If you have it installed, you will see the absolute path of the files ssh and sshd. If you have no answer from the command, you need to intall and configure the packages on both machines. The problem with ssh is that it's strongly recommended to do not permit open sessions with root user and doing this, you can't transfer all file attributes when transfering files from one machine to another, unless you set "user id" execution bit on the application, but we'll discuss it later.
To check if the connection is working, from one machine, open a session on the other:
Code:
# Machine A
ssh <user name>@192.168.0.2
# Machine B
ssh <user name>@192.168.0.1
If both clients and server are working, you'll get a password prompt and, after enter the proper password, you'll get a shell prompt on the other system. The
<user name> is a valid user name on the target machine and must not be "root".
All right, now we can think on the transfer issues. You can use scp, which comes with ssh. There are other utilities and forms to do the transfer over the ssh but I guess that scp is enough for now. The command will be:
scp <file name> <user name>@192.168.0.2:/<directory name>/
scp will ask the password before transfer the file.
