Setting up a very small network
A week or two ago I did a quick and dirty default install of FC 5 on my laptop. Which at the moment I'm using to debug some device driver code.
At my house, there was no problem, I plugged the laptop and the target machines into the LAN, they're both on DHCP and I can simply scp the cross compiled code over to the target box.
I got to the office today and there was no LAN, or even a router, so I just used a crossover cable.
There was some weird futzing around that I needed to do, but I eventually, sort of, got them talking to one another.
Is there an easy way, in FC5, to tell the computer that I want this (copy of, alias of, this) network interface to be a DHCP server. I know that I'm not connected to the outside world, so I just want to be the system that tells anyone on my network what to do.
Likewise, the timeout for the reverse DNS lookup on scp is a bother. I want to make it either magically happen, or tell scp that it doesn't need to happen.
At my house, there was no problem, I plugged the laptop and the target machines into the LAN, they're both on DHCP and I can simply scp the cross compiled code over to the target box.
I got to the office today and there was no LAN, or even a router, so I just used a crossover cable.
There was some weird futzing around that I needed to do, but I eventually, sort of, got them talking to one another.
Is there an easy way, in FC5, to tell the computer that I want this (copy of, alias of, this) network interface to be a DHCP server. I know that I'm not connected to the outside world, so I just want to be the system that tells anyone on my network what to do.
Likewise, the timeout for the reverse DNS lookup on scp is a bother. I want to make it either magically happen, or tell scp that it doesn't need to happen.
