- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- ks.cfg location
Operating System - Linux
1822146
Members
4242
Online
109640
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2004 03:23 PM
07-30-2004 03:23 PM
ks.cfg location
The following is from Red Hat 9 Manual.
"7.8.2. Creating a Kickstart Boot CD-ROM
To perform a CD-ROM-based kickstart installation, the kickstart file must be named ks.cfg and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to the Making an Installation Boot CD-ROM section in the Red Hat Linux Installation Guide for instruction on creating a boot CD-ROM; however, before making the file.iso image file, copy the ks.cfg kickstart file to the isolinux/ directory"
Why copy the ks.cfg to the isolinux directory? That isn't the way my vendor boot CD is. Would that have an effect on the ks.cfg operation from the CD?
Yea, I'm stretching far and wide for answers/guesses
"7.8.2. Creating a Kickstart Boot CD-ROM
To perform a CD-ROM-based kickstart installation, the kickstart file must be named ks.cfg and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to the Making an Installation Boot CD-ROM section in the Red Hat Linux Installation Guide for instruction on creating a boot CD-ROM; however, before making the file.iso image file, copy the ks.cfg kickstart file to the isolinux/ directory"
Why copy the ks.cfg to the isolinux directory? That isn't the way my vendor boot CD is. Would that have an effect on the ks.cfg operation from the CD?
Yea, I'm stretching far and wide for answers/guesses
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2004 03:36 PM
07-30-2004 03:36 PM
Re: ks.cfg location
When creating the boot CD, you copy a whole swag-load of stuff into various structures.
One of those structuers is called 'isolinux/', and when you boot from that CD, that directory become the mounted-root environment.
However, be aware that a number of people I've spoken too have issues using a bootable-CD and follow on to load the OS from CD as well.
The best environment I've found is to have the sources on an NFS, FTP or HTTP server, and use a boot-net type image.
I did it by making a bootable CD with a dynamicly created ks.cfg on it (sourced by http), loading from an NFS server. Throw the CD in a new machine, and leave it for half an hour and *whee!* all built to the company spech's!
Previously I used a boot diskette with a KS on it loading the OS from CD.
One of those structuers is called 'isolinux/', and when you boot from that CD, that directory become the mounted-root environment.
However, be aware that a number of people I've spoken too have issues using a bootable-CD and follow on to load the OS from CD as well.
The best environment I've found is to have the sources on an NFS, FTP or HTTP server, and use a boot-net type image.
I did it by making a bootable CD with a dynamicly created ks.cfg on it (sourced by http), loading from an NFS server. Throw the CD in a new machine, and leave it for half an hour and *whee!* all built to the company spech's!
Previously I used a boot diskette with a KS on it loading the OS from CD.
One long-haired git at your service...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP