Results 1 to 2 of 2

Thread: cloning and persistent eth naming

  1. #1
    justajeffy NNTP User

    Default cloning and persistent eth naming

    for openSuse 11:

    I've got this cloning procedure that involves PXE booting into riplinux and restoring partition images from an nfs mount using partimage. After restoring the images, the partitions are mounted and config scripts are run.

    One of those scripts is to modify /etc/udev/rules.d/70-persistent-net.rules with the MAC of the the newly cloned machine to make sure the proper device is named eth0. This doesn't seem to work. When the machine reboots, it doesn't get named eth0 and the device previously configured on the clone master still appears as a "phantom" device in yast.

    Obviously, I haven't found all the required config edits. Anybody know?


  2. #2
    Join Date
    Jul 2008
    NJ, USA

    Default Re: cloning and persistent eth naming

    You'd need to look into the docs, but I have a feeling that this may have to deal with my greatest enemy - suseconfig.
    J. Antman
    Dedicated SuSE user since October, 2001 (7.3)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts