Grub-bootxen.sh

Home » CentOS-Virt » Grub-bootxen.sh
CentOS-Virt 4 Comments

This is not abit issue just a minor annoyance.

I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo.

I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d.

4 thoughts on - Grub-bootxen.sh

  • Maybe you just don’t need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself.

    Xlord

    —–Original Message—

  • I actually move the default *.repo files and replace them with “”.

    The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don’t have to install any more *-release-*
    rpms any more.

    I would argue that I should not need to install any *-release-* rpms at all to get all the required software.

  • –xxBfiFVgdabgSUqBUBjadxgvmhaid3XVG
    Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    The reason it exists that way is to allow you to not get duplicate kernel entries. If we don’t get the script installed before you get the kernel, then you get a normal kernel entry, then later a xen kernel entry.

    –xxBfiFVgdabgSUqBUBjadxgvmhaid3XVG

  • –CfovmV2jNCUb3jTudOMHc50F6aL4xghHe Content-Type: multipart/alternative;
    boundary=”————24071203E1F8A4CDC9CA78AB”

    This is a multi-part message in MIME format.
    ————–24071203E1F8A4CDC9CA78AB
    Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself.

    Xlord

    -----Original Message---

LEAVE A COMMENT