I found an odd behaviour with askmethod. I found this in Beta RC3.
When installing from a local http repo I normally give a repo= parameter
on the boot commandline. In anaconda still in text mode I am presented
with a UI to configure networking.
When I pass askmethod to the commandline and afterwards choose http
installation source, anaconda just fires a IPv4 DHCP process without
prompting for network parameters. In my situation installation then
fails because there is no DHCP server on the network, as there even is
no IPv4 on that network.
Why is anaconda behaving differently in these installation routes? I
would imaging that both instances of booting ask for the same type of
performing an installation.
Op 28-9-2011 21:13, Chuck Forsberg WA7KGX N2469R schreef:
I was able to do a fresh install of 64 bit F16 from a
mirror on my local network. I've tried the same thing
a number of times previously, but this time it worked!
It is really nice to install from a 1 gbps local network
instead of slow DVD.
The previous problem with mounting NFS shares was the
lack of xinetd and the locking procs. This time I
enabled a share with the GUI and then was able to
mount shares without problems.
At first glance it appears the Grub2 is working normally,
able to locate and boot Fedora or Win7. Haven't had a
chance to check for loading Ubuntu, etc.