Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 23335

Summary: Suppress the boot message.
Product: [Retired] Red Hat Linux Reporter: Red Hat Bugzilla <bugzilla>
Component: kudzuAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-04 18:02:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A patch none

Description Red Hat Bugzilla 2001-01-04 18:01:54 UTC
I will post a patch which will suppress the boot message if
/etc/sysconfig/hwconf doesn't exist.

Comment 1 Red Hat Bugzilla 2001-01-04 18:02:17 UTC
Created attachment 7064 [details]
A patch

Comment 2 Red Hat Bugzilla 2001-01-04 18:38:06 UTC
This explicitly changes the behavior to be not interactive.

Not applied.

Comment 3 Red Hat Bugzilla 2001-01-04 18:47:57 UTC
Please note that you have to remove /etc/sysconfig/hwconf
to change the hehavior. I believe you have to do it by
hand on purpose. The hardware support can be changed by

1. A new hardware.
2. A new kernel which supports the existing hw which was not
supported by the old kernel.

In some cases, I may not want to sit there to interact with
kudzu. My patch provides a way to avoid it. But I have to
do it on purpose by hand.

BTW, anaconda does the same thing by doing "kudzu -a" during
the install. I just want to have a way to do the same.

Comment 4 Red Hat Bugzilla 2001-01-04 18:50:02 UTC
You can do it by calling it explicitly itself; the run-on-each-boot
configuration is not necessarily meant for this.

Comment 5 Red Hat Bugzilla 2001-02-01 22:13:09 UTC
*** Bug 18916 has been marked as a duplicate of this bug. ***