Red Hat Bugzilla – Bug 174629
diskless patches do not apply correctly
Last modified: 2008-07-24 15:32:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Description of problem:
When running 'mkdiskless' in order to prepare an NFS root filesystem for diskless booting, several patches are applied to files in '/etc/rc.d'. These patches fail to apply with the following errors:
patching file /targetfs/rh-cpm1/root/etc/rc.d/rc.sysinit
Hunk #1 FAILED at 243.
Hunk #2 FAILED at 322.
Hunk #3 FAILED at 339.
Hunk #4 FAILED at 808.
4 out of 4 hunks FAILED -- saving rejects to file /targetfs/rh-cpm1/root/etc/rc.d/rc.sysinit.rej
patching file /targetfs/rh-cpm1/root/etc/init.d/halt
Hunk #1 succeeded at 25 with fuzz 2.
patching file /targetfs/rh-cpm1/root/etc/init.d/netfs
Hunk #1 FAILED at 23.
Hunk #2 FAILED at 90.
2 out of 2 hunks FAILED -- saving rejects to file /targetfs/rh-cpm1/root/etc/init.d/netfs.rej
patching file /targetfs/rh-cpm1/root/etc/init.d/xfs
Hunk #1 FAILED at 56.
Hunk #2 succeeded at 104 (offset 22 lines).
1 out of 2 hunks FAILED -- saving rejects to file /targetfs/rh-cpm1/root/etc/init.d/xfs.rej
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Follow the steps in the Red Hat Enterprise Linux System Administration Guide to setup a diskless boot environment
2. Look for failed patch attempts (.rej files) in your NFS root filesystem
Yes, some initscripts have changed drastically since the patches were
In practice, however, the failed patches do not lead to any problems
with diskless client booting - I've not found any problems caused by
the mis-patched initscripts so far. If you do, please append details to this
The whole idea of patching initscripts during mkdiskless is wrong - it
should probably replace the initscripts by installing a 'diskless-initscripts'
rpm , or by making initscripts which accept options for diskless environments
so they don't need to be patched / replaced.
I'll remove the patches from the next release and look into implementing
one of the above options.
I have not experienced any problems booting with the failed patches. Perhaps the
severity of this bug should be lower?
In any case, I think creating initscripts that can handle both environments
would be the best solution.
From User-Agent: XML-RPC
system-config-netboot-0.1.38-2_FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
Created attachment 294214 [details]
patch to fix patches for rhel4.7
The patches updated for latest init scripts in RHEL4. This maybe isn't
necessary, but it's much nicer when the patches do not fail and do not leave
ugly .rej files throughout rc.d.
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
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 therefore 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.