Bug 10270 – mkkickstart creates a file with invalid characters

Bug 10270 - mkkickstart creates a file with invalid characters

Summary:	mkkickstart creates a file with invalid characters

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	mkkickstart (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-03-20 16:17 EST by Jason Shelton
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-10-09 17:30:52 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jason Shelton 2000-03-20 16:17:54 EST

when mkkickstart is invoked, the output contains lines with *** to indicate
comments. When booting and using the resulting file, kickstart fails
indicating that the *** characters are invalid. I have succesfully changed
these astrisks (*) to pound signs (#) using VI and the resulting file was
accepted by kickstart.

Comment 1 Matt Wilson 2003-10-09 17:30:52 EDT

mkkickstart isn't supported anymore, closing WONTFIX

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