On Wed, Apr 13, 2011 at 9:46 AM, Glenn Cogle <[email protected]> wrote: > On 12 April 2011 20:37, Robert Fisher <[email protected]> wrote: >> >> On 12/04/11 20:26, Glenn Cogle wrote: >> >> Hi all, >> >> I'm trying to replicate a Debian server, so I >> >> 1. did a minimal Debian install on the new server, using a different IP >> address, then >> 2. used rsync to copy /etc /opt /home /usr /lib /bin /sbin /var to new >> server, then >> 3. rebooted to see how clever I had been. >> >> But because the hardware is so different, the network interfaces on the >> new server are not recognised. >> >> Is there a file (or files) that I shouldn't have copied forward? >> >> Can I go though all or part of the Debian installation again to fix the >> NICs? >> >> i.e. what should I do different next time? >> >> gc >> >> I recently upgraded my mobo and cpu and all I had to do was edit >> /etc/udev/rules.d/70-persistent-net.rules >> to put a # in front of the old network card line (eth0 for me) - you could >> delete the line I suppose. >> The new network card was then detected at next reboot and became the new >> eth0 >> >> HTH >> >> -- >> Regards, Robert >> >> -------------------------------------------------------------- >> Robert Fisher >> (aka - Rob, Bob, Robbie, Robbo, Fish) >> www.fisher.net.nz >> Phone: 03 383 5807 >> Mobile: 027 228 4698 >> >> That worked perfectly! > > In my case it was /etc/udev/rules.d/z25_persistent-net.rules. > > Next time I think I'll exclude the /etc/udev directory altogether. > > gc
Not necessarily, some packages add files in there, and may not work without those files. _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
