HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Kickstart
Operating System - Linux
1829849
Members
2799
Online
109993
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
04-17-2007 07:24 PM
04-17-2007 07:24 PM
Kickstart
Am new to kickstart file, using parallel am running image of isolinux
In isolinux.cfg file .I have specified path of ks.cfg.I created image by using this command
sudo mkisofs -o ../ks.iso -V 'RH9 Install' -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -V -T .
When i boot it using parallel it say ks.cfg. Can u tell me how to specify path
for ks.cfg.
default ks
prompt 1
timeout 200
display boot.msg
F1 boot.msg
F2 options.msg
F3 general.msg
F4 param.msg
F5 rescue.msg
F7 snake.msg
label ks
kernel vmlinuz
append initrd=initrd.img ramdisk_size=8192 ks=file:/root/Desktop/isolinux/isolinux/ks.cfg
label linux
kernel vmlinuz
append initrd=initrd.img ramdisk_size=8192
label text
kernel vmlinuz
append initrd=initrd.img text ramdisk_size=8192
label expert
kernel vmlinuz
append expert initrd=initrd.img ramdisk_size=8192
label ks
kernel vmlinuz
append ks initrd=initrd.img ramdisk_size=8192
label lowres
kernel vmlinuz
append initrd=initrd.img lowres ramdisk_size=8192
label local
localboot 1
label memtest86
kernel memtest
append -
In isolinux.cfg file .I have specified path of ks.cfg.I created image by using this command
sudo mkisofs -o ../ks.iso -V 'RH9 Install' -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -V -T .
When i boot it using parallel it say ks.cfg. Can u tell me how to specify path
for ks.cfg.
default ks
prompt 1
timeout 200
display boot.msg
F1 boot.msg
F2 options.msg
F3 general.msg
F4 param.msg
F5 rescue.msg
F7 snake.msg
label ks
kernel vmlinuz
append initrd=initrd.img ramdisk_size=8192 ks=file:/root/Desktop/isolinux/isolinux/ks.cfg
label linux
kernel vmlinuz
append initrd=initrd.img ramdisk_size=8192
label text
kernel vmlinuz
append initrd=initrd.img text ramdisk_size=8192
label expert
kernel vmlinuz
append expert initrd=initrd.img ramdisk_size=8192
label ks
kernel vmlinuz
append ks initrd=initrd.img ramdisk_size=8192
label lowres
kernel vmlinuz
append initrd=initrd.img lowres ramdisk_size=8192
label local
localboot 1
label memtest86
kernel memtest
append -
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2007 10:41 AM
04-18-2007 10:41 AM
Re: Kickstart
If using a 'ks=' type of URL, it should be relative to the ISO image i.e. 'ks=cdrom:/ks.cfg' or 'ks=floppy'. The 'ks=file:/ks.cfg' type should only be used if the 'ks.cfg' is within the 'initrd' image.
See:
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-kickstart2-startinginstall.html
See:
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-kickstart2-startinginstall.html
One long-haired git at your service...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2007 05:47 PM
04-18-2007 05:47 PM
Re: Kickstart
Also, the "ks=..." option should be added to the "append" line. It should not be on its own line.
Where is the ks.cfg located in the CD-ROM?
If the ks.cfg is located in the top-level directory of the CD-ROM, the correct option would be "ks=cdrom:/ks.cfg".
If it's in the "isolinux" subdirectory, the correct option would be "ks=cdrom:/isolinux/ks.cfg".
MK
Where is the ks.cfg located in the CD-ROM?
If the ks.cfg is located in the top-level directory of the CD-ROM, the correct option would be "ks=cdrom:/ks.cfg".
If it's in the "isolinux" subdirectory, the correct option would be "ks=cdrom:/isolinux/ks.cfg".
MK
MK
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP