I've run into another problem with IPv6 and FC6. This one is not a
"show stopper" (which it would be too late for, anyways) and more of an
extreme annoyance and install problem.
I just went to install FC6 into one of my networks which uses static
IPv4 addresses and stateless autoconf for IPv6. Guess what. Can't do
it. If you specify a static IPv4 address in the install, you also have
to specify a static IPv6 address if you have IPv6 enabled. That sucks
out loud. IPv6 and IPv4 configurations are independent.
What's worse, I now realize, is that if you are using dhcp for IPv4,
it's also attempting to use dhcp6 for IPv6! Gag! That can result in
terrible slowdowns for network startup in IPv6 environments which are
only using stateless autoconf, whether you are using dhcp for IPv4 or
static IPv4 addresses. If people are wondering why their FC6 installs
take forever to configure their network interfaces - surprise, you've
got IPv6 enabled and are using dhcp for IPv4 and don't have an IPv6
dhcp6 server. Let the bitching begin.
Bascally, someone was thinking in terms of IPv4 think when they
designed the installer and took no allowance for IPv6 autoconf (which
should be the most common method) and assumed that if you had IPv4 dhcp
you would have IPv6 dhcp, which is patently not a valid assumption at
all. There are certainly reasons and advantages to having a dhcp6
server, but I'm just betting that very few installations are going to.
The choices for IPv4 and IPv6 are orthogonal and different.
IPv4: dhcp / static / disabled
IPv6: dhcp6 / static / autoconf
If IPv6 is loaded, there appears to be no practical way to "disable"
IPv6 on an interface and the default is for "stateless autoconf" if IPv6
forwarding is disabled (/etc/sysctl.conf).
Workaround is to disable IPv6 on that interface at install. It really
doesn't disable IPv6 at all, it still configures and will then autoconf,
if you have IPv6 forwarding disabled). So, "disabling" IPv6 has exactly
the opposite effect and results in it being enabled and autoconf'ed
properly. Some of life's little ironies.
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
I'm on a brainstorm for my website work, and I got to thinking of a few of
ideas for Fedora that I believe would make it even cooler. I know FC6 is just
heading out of the proverbial door, but I'd like to get discussion going on
FC7+ things so that they will rock that much harder when implemented (if, in
fact, they are).
Firstly, there was talk at one point about switching the default RPM build
flags to use -Os (optimize for size, mostly) instead of -O2. For one, this
could potentially reduce the ISO sizes significantly. (I don't have any
specific numbers, but as I recall the estimate was something of the ~300 MB
range, give or take.) Also, this would mean that applications would
potentially feel faster because less would need to be read from disk, and hits
to processor cache would be increased, as well as being able to store more in
the RAM caching. Is this planned for the FC7/8 timeframe? If not, is there a
plan to implement such a thing at all, if even for specific packages that
would benefit from it?
Secondly, the current setup of Pirut is that it downloads things from the
network whenever you go to install something. Is there work being done to be
able to use the installer DVDs/CDs as optional repositories for this? (That
way, a user whose Internet connection is slow or non-functional would be able
to install packages from the discs, rather than the net.
Tangential to this point actually, is a third point: Are there planes to have
a packages CD/DVD of sorts which contains a snapshot of Extras packaging? I
think this would also be a definite plus, as many of the packages in Extras
are rather large (especially much of the game data for things like Nexuiz and
Peter Gordon (codergeek42)
GnuPG Public Key ID: 0xFFC19479 / Fingerprint:
DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479
My Blog: http://thecodergeek.com/blog/
What happened with the FC-5 2200 kernel update ? Looks like it broke
many people's systems (including one of our servers at work). Isn't it a
bit late in the lifetime of FC-5 to release such a new/untested kernel ?
Yes, you almost right ;).
if i use clearpart --all --initlabel instead of clearpart --all --drives=sda --initlabel it works.
But with this command i delete all partitions on all disks.
> From: admin(a)zapped.2y.net> To: fedora-devel-list(a)redhat.com> Date: Mon, 23 Oct 2006 00:12:34 +0200> Subject: Re: Possible bug found in kickstart (can anybody check this?)> > Op zondag 22-10-2006 om 23:13 uur [tijdzone +0200], schreef Rolf> lkjgljgljhkj:> > I have the following in the kickstart file:> > part swap --size=128 --grow --size=256 --ondisk=sda –asprimary> > Hi,> > Did you already notice that you have 2 size= options and> that the asprimary option is missing a dash (it should > be --asprimary instead of -asprimary). Prodably Anaconda> is failing due to these small mistakes.> > Regards,> > Erik van Pienbroek> > > > > -- > fedora-devel-list mailing list> fedora-devel-list(a)redhat.com> https://www.redhat.com/mailman/listinfo/fedora-devel-list
Probeer Live.com: je eigen persoonlijke opstartpagina met alleen de dingen die jij belangrijk vindt op één plek.
I setup a vmware server with 2 disks (sda and sdb)
I have the following in the kickstart file:
## - - disk setup - - - - - - - - - -
## :: remove old partitions
clearpart --all --drives=sda --initlabel
part /boot --fstype ext3 --size=100 --ondisk=sda --asprimary
part / --fstype ext3 --size=1024 --grow --ondisk=sda --asprimary
part swap --size=128 --grow --size=256 --ondisk=sda –asprimary
When I run the kickstart I see this:
Could not allocate requested partitions
Partioning failed: Could not allocate partitions as primary partitions.
What i bassicly want is that the installer only use sda.
Can anybody verify this?
Probeer Live.com: jouw leven online met nieuws, sport, weer en nog veel meer.
This is a simple thank you to all the developers out there working on their
various Fedora-Related projects.
In the midst of all the reported problems and debates, I think you should
all take a small moment out of your busy schedules to pat yourselves on the
back for being one of the very few in the world that understand and do what
*round of applause*
I can't wait to secure a schedule that will enable me to begin helping out,
and I certainly can't wait to get my hands on FC6!
Viva La Fedora!