Bug 103310

Summary:	Docs incorrectly say netprofiles can't be set at boot time
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <gneeki>
Component:	rhl-cg	Assignee:	Tammy Fox <tammy.c.fox>
Status:	CLOSED ERRATA	QA Contact:	Tammy Fox <tammy.c.fox>
Severity:	low	Docs Contact:
Priority:	medium
Version:	9	CC:	notting
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-08-29 21:06:57 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:

Description Need Real Name 2003-08-28 18:57:57 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4; MultiZilla
v1.4.0.4A) Gecko/20030630

Description of problem:
Really a documentation issue:

http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-network-profiles.html

says that "A profile cannot be activated at boot time": it can and this proves
very useful once I realised!

grep netprofile /etc/rc.d/rc.sysinit

shows that all the hooks for passing netprofile= via grub are there as the boot
process correctly read /proc/cmdline.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Set up a new network profile
2. Pass netprofile=<new profile name> via grub.conf
3. Boot into the new profile
    

Actual Results:  It works.

Expected Results:  It should have worked. The documentation denies this.

Additional info:

Comment 1 Tammy Fox 2003-08-28 22:40:03 UTC

Thanks for the information. I'll try it out. I said that because when I asked
the developer about it, he told me that you couldn't activate them at boot time.

Comment 2 Tammy Fox 2003-08-29 21:06:57 UTC

A docs errata for this should appear in less than an hour on
http://www.redhat.com/docs/errata/RHL-9-Manual/.