bootable CD or diskette for FC3, how can i do it?

kenneth graham poken77 at hotmail.com
Mon Oct 31 02:31:52 UTC 2005


hi Stuart ...

may I know how you did the your custom CD bootable ? but please give me some 
details of
HOW-TO like for dummies :)


thanks everybody for your time
Kenneth


>From: "Stuart J. Browne" <sjbrowne at bluebottle.com>
>Reply-To: Discussion list about Kickstart <kickstart-list at redhat.com>
>To: "Discussion list about Kickstart" <kickstart-list at redhat.com>
>Subject: Re: bootable CD or diskette for FC3, how can i do it?
>Date: Mon, 31 Oct 2005 09:36:12 +1100
>
>>can i boot form CD 1 of FC3 and when I get the "boot> " wirte :
>>
>>boot> linux ks=http://some.server/ks.cfg  ip=1.2.3.4 
>>netmask=255.255.255.128 gateway=1.2.3.1 dns=1.2.3.2
>
>You said you have a DHCP server, why not use it?  anyway..
>
>>and after take the CD out, because i suppose that he will take the 
>>packages that I specified inside the ks.cfg  from the http server?
>
>I can't remember if it tries to access the boot media again, but it will 
>take the packages from the source defined in the ks.cfg file, where ever it 
>came from, i.e.  I used to use a HTTP ks, with NFS packages.
>
>>i have many servers to do the same, so I think i will put everything in 
>>the http server, with different ks.cfg
>
>*nod* good.
>
>>do i need to have all of the packages in the same directory?
>
>There are two ways.  Yes, one is to put all the packages in the 
>Fedora/RPMS/ structure (as it appears on the CD's), so all the RPM's end up 
>in the same directory.  The other involves using ISO files, but that isn't 
>available for all file-transfer methods.
>
>Reading the documentation on setting up a KS server would help:
>
>http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/ch-kickstart2.html 
>(part 8+9) and 
>http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/install-guide/s1-begininstall-net.html.
>
>>> >4. is it possible to do the kickstart installation with a diskette? if
>>>yes, how?
>>>
>>>It's possible to put the kickstart file on a floppy, but you can't boot
>>>from one as the install images have grown too large in recent releases.
>
>What I did was to create a custom bootable CD with update network and IO 
>drivers on it for my systems, but I was using dynamically generated ks 
>configurations, and DHCP in order to automate the entire process.
>
>>>An alternative I'd recommend looking into if you'll be doing a lot of
>>>installs is network booting, where all the configuration can live on the
>>>server and there's no need to create custom floppies or CDs per host or
>>>per subnet.
>
>bkx
>
>_______________________________________________
>Kickstart-list mailing list
>Kickstart-list at redhat.com
>https://www.redhat.com/mailman/listinfo/kickstart-list





More information about the Kickstart-list mailing list