Maybe I shouldn't be doing import at all, or doing a lot more configuration; I tried what you said, and then ran import with the RH4-i386 source and one distro over-wrote the other. I need 2 seperate "distros" one for i386 and one for x86_64 How can I do this? -----Original Message----- From: et-mgmt-tools-bounces@xxxxxxxxxx [mailto:et-mgmt-tools-bounces@xxxxxxxxxx] On Behalf Of Michael DeHaan Sent: Tuesday, January 01, 2008 8:24 PM To: Fedora/Linux Management Tools Subject: Re: cobbler: import of x86_64 repo creates i386 distro Eugene Ventimiglia wrote: > I'm running: > > cobbler import > --path=/mnt/os-install/exported/media/Linux/RH-4.0-ES-U4-AMD64/ > --name=rhel4 > > and cobbler list reports: > > ... > distro rhel4-i386 > profile rhel4-i386 > > _______________________________________________ > et-mgmt-tools mailing list > et-mgmt-tools@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/et-mgmt-tools > It sort of looks like a bug, but it isn't. Cobbler determines the "arch" bits based on the paths you import. As the standard rsync/build trees (well, RHEL really doesn't have them -- Fedora and RHEL derivatives do), typically say x86_64 or i386 in them, it uses the presense of these tokens in the part to ID the distro. If you are importing from a DVD, this shouldn't happen. Basically the names don't mean anything, so you can just do the following and will be fine: cobbler profile rename --name=rhel4-i386 --newname=rhel4-x86_64 --arch=x86 cobbler distro rename --name=rhel4-i386 --newname=rhel4-x86_64 --arch=x86 The arch field really isn't needed except for distinguishing that things are /not/ ia64 boxes, which require different baremetal boot loader setup. --Michael _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
