Bug 31881 - boot time parameter PROFILE not evaluated
Summary: boot time parameter PROFILE not evaluated
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-15 17:39 UTC by Thilo Kopp
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:47:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Thilo Kopp 2001-03-15 17:39:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.7 [en] (WinNT; I)

With linuxconf you can set up several profiles. You should be able to load these profiles
at the boot prompt with "linux PROFILE=myprofile" or you can set up liloconf so that
the profile names even show up in the graphical LILO interface at the begining of the
boot process. This seems to be great however, the profile will actually not switch, that is,
the boot time parameter profile is not beeing evaluated. Does it work with the new kernel
2.4.xx ? or on a different machine than mine (Dell Latitude C800)? 

Reproducible: Always
Steps to Reproduce:
1. use LILO, get the boot prompt with ctrl-x
2. type at the boot prompt: linux PROFILE=myprofile
3. check if the profile switched from the previous to myprofile

Actual Results:  profile did not switch

Comment 1 Doug Ledford 2001-03-15 17:53:05 UTC
This should not be a lilo problem.  Lilo passes unknown options to the linux
kernel unmodified.  To check this, you can see if the file /proc/cmdline
includes your PROFILE= option.  If it does, that means the lilo passed the
option as it was suppossed to and the problem is somewhere else (most likely in
linuxconf at that point).

Comment 2 Thilo Kopp 2001-03-15 19:44:44 UTC
Yes indeed, the buggy component is not LILO but rather: Linuxconf 1.19 (subrev
I can switch profiles from within linuxconf -> Control -> Control panel ->
Switch system profile
perfectly fine however it will not work during boot time: LILO passes the option
to the kernel 
(as can be checked from /proc/cmdline) but the corresponding profile is not

Comment 3 Doug Ledford 2001-03-15 20:10:40 UTC
I'm switching the component to linuxconf and the assigned owner to the owner of
linuxconf then so that this can be addressed.

Comment 4 Thilo Kopp 2001-03-19 11:05:50 UTC
During the boot process, the system initialization /etc/rc.d/rc.sysinit  takes care of networking,
file systems, loading modules and so on. I guess that it should also contain program code
which evaluates the boot time parameter PROFILE. However, there is no single line which
contains the words linuxconf or  profile. Other boot time parameters (e.g. fastboot=yes) are taken
care of in this file but not the boot time parameter profile. 

Does anyone have a /etc/rc.d/rc.sysinit  which contains instructions for linuxconf and profile?

Comment 5 Brent Fox 2002-06-05 16:24:15 UTC
Closing because we don't ship linuxconf anymore

Comment 6 Red Hat Bugzilla 2006-02-21 18:47:56 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.