Re: Anaconda Bug?

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

 



lang en_US.UTF-8
langsupport --default en_US.UTF-8 en_US.UTF-8
network --device eth0 --bootproto dhcp --hostname nfs-basic
firewall --disabled
cdrom
device scsi aacraid
device scsi megaraid
device scsi aic7xxx
device eth eepro100
keyboard us
bootloader --location=mbr
clearpart --linux --drives sda
part /boot --fstype "ext3" --size=128 --ondisk=sda
part swap --size=512 --ondisk=sda
part / --fstype "ext3" --size=100 --grow --ondisk=sda
install
mouse genericwheelps/2 --device psaux
timezone --utc Etc/GMT
rootpw --iscrypted ###
authconfig --enableshadow --enablemd5
skipx
reboot

From what I understand, the "expert noprobe" that is appended to the
boot prompt makes anaconda skip probeing for devices. The device options
in the Kickstart file are supposed to define the devices. This doesn't
work. Am I wrong in how this is supposed to work?

I assume it's not working in the way you posted in your bug #150238 -
that is, the SCSI adapters are still getting recognized in an order
other than what you want.  Can you remove "reboot" from your kickstart
config file so the machine will not automatically reboot, then post the
relevant section out of /tmp/anaconda.log so we can see if the SCSI
modules are getting loaded in the same order as you're specifying?

You could also attach anaconda.log to your bug report, I suppose.

I think your understanding of how it's supposed to work is correct, but
most of this code is new to me so I might not have a full understanding
of it myself.

- Chris


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux