Description of problem:
Package is not in repos.
If package has been renamed/removed please change
Version-Release number of selected component (if applicable):
yum -y install system-config-netboot
Steps to Reproduce:
No Match for argument: system-config-netboot
Package actually being in repos
RHEL Hardware Certification (v. 5 for 32-bit x86)
Red Hat Network Tools for RHEL Server (v.5 32-bit x86)
RHEL FasTrack (v. 5 for 32-bit x86)
RHEL Supplementary (v. 5 for 32-bit x86)
RHEL Virtualization (v. 5 for 32-bit x86)
I just ran into this today as well. This package is referenced in the RHEL5
If this package no longer exists, what's the recommended way to set up a PXE
boot server now?
*** Bug 260021 has been marked as a duplicate of this bug. ***
Whether this going to be fixed in any other updates of RHEL5.0
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This is STILL listed as the package to install to get the pxeos command in the
5.1 documentation. Is the documentation wrong or is this package missing?
System-config-netboot package should be included in next update, RHEL 5.2. At
this time, you can try current Fedora-devel package (0.1.45-1.fc9), which should
work with RHEL5 and which will be the base for RHEL5 package.
I have created diskless enviroment using fedora system-config-netboot (0.1.45-
Creation was OK, but when booting the machine following error has appeared:
/bin/bash: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
Kernel panic - not syncing: Attemped to kill init!
Please move this report if duplicant or if openened for wrong package.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.