Re: Fedora Core 2 Test 2 kickstart problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



No experience with the bulk of your issues, but genhdlist will take an 
argument as such:

--productpath Fedora

That eliminates the need for a work around.

-brad

[ Charset ISO-8859-1 unsupported, converting... ]
> I have been using kickstart for some time to build selinux installs on a 
> RHL7.1 base, and am trying to leapfrog forward to  FC2 test 2, since 
> selinux is being integrated onto that distribution.  I am currently 
> working with a minimal ks.cfg file, generated by the configurator.  I am 
> appending it to the bottom of this email.
> 
> When I try to install with:
>    linux ks=cdrom:/ks.cfg
> I get a "No driver found" window with the message "Unable to find any 
> devices of the type needed for this installation type."
> 
> I am fairly certain that anaconda is finding my ks.cfg file, because if 
> I give it a bogus path, such as:
>    linux ks=cdrom:/foo.bar
> I get an Error window with the message "Cannot find kickstart file on 
> CDROM."
> 
> To test whether the problem is with the way I built my install CD, I 
> have also copied the ks.cfg to a diskette and booted from the FC2 test 2 
> disk 1 with the command:
>    linux ks=floppy:/ks.cfg
> I get identical results, i.e. the "No driver found" window.
> 
> 
> Has anyone successfully used kickstart with Fedora Core 2?  Can you give 
> me any clues as to what's wrong?
> 
> BTW, if anyone else is working with Fedora Core 2 I've noticed a couple 
> of other nits that are worth passing along:
> - the disk 1 ISO image for test 2 is not bootable.  Technically, when I 
> tested with the standard install CDs, I initially booted with the FC2 
> test 1 disk 1 and then swapped to FC2 test 2.
> - The current anaconda genhdlist program wants to write to RedHat/base 
> rather than Fedora/base.  I've been getting around this by symbolically 
> linking Fedora to RedHat before calling genhdlist, then removing the 
> link before creating the ISO file.
> - It appears to me that we will need an "selinux" option similar to the 
> "firewall" option in the ks.cfg file, with options to disable, warn or 
> enable.
> 
> Regards,
> Martin Robb
> MartinRobb@xxxxxxxx
> 
> My current ks.cfg file:
> 
> #Generated by Kickstart Configurator
> #platform=x86, AMD64, or Intel EM64T
>                                                                                                                              
> 
> #System  language
> lang en_US
> #Language modules to install
> langsupport en_US
> #System keyboard
> keyboard us
> #System mouse
> mouse genericwheelps/2
> #Sytem timezone
> timezone America/New_York
> #Root password
> rootpw 15:1AIsasih,ga
> #Reboot after installation
> reboot
> #Install OS instead of upgrade
> install
> #Use CDROM installation media
> cdrom
> #System bootloader configuration
> bootloader --location=mbr
> #Clear the Master Boot Record
> zerombr yes
> #Partition clearing information
> clearpart --all --initlabel
> #Disk partitioning information
> part / --fstype ext3 --size 1 --grow
> part swap --size 1024
> #System authorization infomation
> auth  --useshadow  --enablemd5
> #Firewall configuration
> firewall --disabled
> #Do not configure XWindows
> skipx
> #Package install information
> %packages --resolvedeps
> @ Core
> @ Dialup Networking Support
> @ Base
> 
> 
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
> 

-- 
Brad Doctor, CISSP



[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux