Skip to main content

Add The Group Information IN Yum Repository in simple Two steps

= Yum groups and repositories =

Yum supports the group commands
  * grouplist
  * groupinfo
  * groupinstall
  * groupremove
  * groupupdate

Groups are read from the "group" xml metadata that is optionally available from
each repository. If yum has no repositories which support groups then none of 
the group operations will work. 
#yum grouplist

   This will list the installed and available groups for your system in two
   separate lists. If you pass the optional 'hidden' argument then all of 
   the groups which are set to 'no' in the group xml tag.

  yum groupinfo groupname
 
  This will give you detailed information for each group including:
  description, mandatory, default and optional packages.

      #yum groupinstall groupname
     #yum groupupdate groupname

  Despite their differing names both of these commands perform the same
  function. They will attempt to install/update all of the packages in the
  group that are of the types 'default' or 'mandatory' (by default).
  (To change this types of packages edit the value of the group_package_types 
  option in yum.conf.) And they will install any additional dependencies 
  needed by any of the installing/updating packages.

    # yum groupremove groupname
 
  This will remove all packages, of any type, in the named group. It will also
  remove any package that depends on any of these packages.
   


== Setting up your own groups in your own repository ==

This process is pretty easy, just two steps:
 1. create a file in the groups format used by yum
 2. tell createrepo to include that group file in your repository.


=== Step 1 ===
  You can either open a text editor and create the groups xml file manually or you
  can run the yum-groups-manager command from yum-utils. 


 # yum-groups-manager -n "My Group" --id=mygroup --save=/root/mygroups.xml --mandatory yum glibc rpm  dhcp bind
  # cat /root/mygroups.xml


 
   mygroup
   False
   True
   1024
   My group
  
   
      glibc
      rpm
      yum

     dhcp
     bind
   
 




=== Step 2 ===
  To include this in a repository, just tell [http://createrepo.baseurl.org/ createrepo] to use it when making or remaking
  your repository.

#createrepo -g /path/to/mygroups.xml /srv/my/repo
 
After that we can check our Group Name
# yum grouplist
#yum groupinfo mygroup
# yum groupinstall

Comments

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image downloaded we can start a contai

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --now cockpit.socket If firewall is runnin

Containers Without Docker on RHEL/Fedora

Docker is perfectly doing well with the containerization. Since docker uses the Server/Client architecture to run the containers. So, even if I am a client or developer who just wants to create a docker image from Dockerfile I need to start the docker daemon which of course generates some extra overhead on the machine.  Also, a daemon that needs to run on your system, and it needs to run with root privileges which might have certain security implications. Here now the solution is available where we do not need to start the daemon to create the containers. We can create the images and push them any of the repositories and images are fully compatible to run on any of the environment.  Podman is an open-source Linux tool for working with containers. That includes containers in registries such as docker.io and quay.io. let's start with the podman to manage the containers.  Install the package  [root@rhel8 ~] # dnf install podman -y  OR [root@rhel8 ~] # yum