Latest FC6 Respin installation DVD was released on 2007-01-19. Lots of
known FC6 bugs fixed and it uses the latest updated packages as of Jan
11th. If you have had install problems with Core 6 before, you are
encouraged to try installation with this new FC6 Respin DVD.
"The Fedora Unity Project is proud to announce the release of new ISO
Re-Spins of Fedora Core 6. These Re-Spin ISOs are based on Fedora Core 6
and all updates released as of January 11th, 2007. The ISO images are
available for i386 and x86_64 architectures via BitTorrent starting
Thursday, January 18th, 2007. PPC images will follow within the next 5
days, but will have had only limited testing.
This release was delayed while waiting for fixes to known issues with
Fedora Core 6 as well as the creation of a new tool for composing
Re-Spins. Previous releases were built with a homebrew script. This
release was built with the new tool called Pungi, developed by Jesse
Keating, a leading community member and Fedora Release Engineer, with
community input. This tool will be used in future official Fedora
releases and for Fedora Unity Re-Spins. We have joined in this effort to
bring a full featured tool to the Fedora community, enabling anyone to
build Re-Spins and Live-Spins now and in the future."
Off Topic or Political Discussions:
"Character is what you do when nobody's looking." - J.C. Watts
> I have an atheros cardbus card made by ubiquiti. Every once in a
> while wpa_supplicant gets in a loop where it negotiates the key, I
> very briefly see "completed" with the wpa-psk, CCMP, etc displayed in
> wpa_gui. Before I can blink the wpa_gui says DISCONNECTED and all the
> vitals are cleared. It then repeats the above forever. The fix is
> usually to do a "service wpa_supplicant restart". Sometimes I need to
> take down the ath0 interface and bring it up too. It feels like a
> timing problem where wpa_supplicant just isn't waiting long enough for
> BTW. I just spent an hour trying to get the network working with
> wpa_supplicant started before the network code. If I put an "exit 0"
> at the start of ifup-wireless then the dhclient never got started,
> even though wpa_gui shows the association exists. Ipv6 is also up, so
> the network is usable for that. I have no idea why dhclient didn't get
> started. The only thing I can guess is timing also. I've returned to
> starting wpa_supplicant from the bottom of ifup-wireless and things
> are back to normal.
Forgot to mention 2 things:
1) "exit 0" is not good since the file is included in another script
(I think), so you end up skipping the rest of its parent (where dhcp
You should add something like
if WPA ....
around all the settings via "iwconfig"
2) I had to disable ipv6 completely, otherwise my interfaces (both
wireless and cable) were not able to go up and down. They were up once
and then if-down hanged.
each time i boot fedora i must enable by hand the eth0 device (by the
What must i do to enable the device at boot?
# cat /etc/sysconfig/network
# cat /etc/sysconfig/networking/devices/ifcfg-eth0
# cat /etc/sysconfig/networking/profiles/default/ifcfg-eth0
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
all 3 the same output
# Macronix, Inc. [MXIC]|MX987x5
alias wfx (http://teg.sf.net)
I seem to have (finally :) ) acquired a complete(ish) / working x86_64
system .. but I'm still having trouble with a few bits, not least "yum".
Server: Fedora Core 1 - i386 - Base
Server: Fedora Core 1 - i386 - Released Updates
Server: Fedora Core 1 - i386 - Unreleased Updates
Finding updated packages
Traceback (most recent call last):
File "/usr/bin/yum", line 60, in ?
File "yummain.py", line 204, in main
File "clientStuff.py", line 363, in getupdatedhdrlist
File "clientStuff.py", line 409, in bestversion
IndexError: list index out of range
(This is a modified system [2.6.0-test11] however it seems to run well)
Pointing it at mozilla's channel for SeaMonkey seems to work if I
disable the default channels, however...
Anyone any ideas ?
(I was sort of expecting to see it say "no x86_64 updates supported yet"
as opposed to a complete crash)
Also, can yum pull SRPMS and rebuild them ?
I have a rocketraid 1740 controller that I want to use in a soon to be
installed Fedora 7 system. Highpoint's website doesn't have any Fedora
7 drivers, but they do provide a package that will let end users build
the rr1740x module for any 2.4 or 2.6 series kernel.
How would one build the rr1740x module for Fedora 7 if one doesn't have
a Fedora 7 system to build the driver on? Can I install the
kernel-devel package from Fedora 7 on a Fedora 6 host, and build the
module that way? Should I use a Fedora 7 virtual machine (e.g. vmware,
Kanwar Ranbir Sandhu
Linux 2.6.20-1.2962.fc6 i686 GNU/Linux
14:15:59 up 4 days, 2:59, 2 users, load average: 0.12, 0.07, 0.16
I am almost certain I have done this before but I am getting old and may
be imagining things. I have opened up a new message in Thunderbird
(latest and greatest). I have verified that the format is "Rich Text
(HTML)". I go to KSnapShot and snap a section of the screen and click on
the "Copy to Clipboard" button. I then try to paste it into the note and
it simply does nothing.
Am I missing something? I would like to paste an image into a note to
send as documentation to someone.
Real programmers don't eat muffins
I've bought a drive with usb and network connection. I used the usb to
quickly transfer a large quantity of data, but intended putting it onto the
network after that. The blurb on the box said it would just pick an ip by
dhcp. However, it seems to me that I need to know something about it in
order to mount it, and I've got a total blank on where to go next. Nothing
appears in /var/log/messages.
I've told the router to reserve an address for it and made an entry
in /etc/hosts. Since I can't see any sign of it being recognised I haven't a
clue how to mount it. Any ideas?
Just upgraded from 2.6.21-1.3228.fc7, and now seeing problems with NFS. I originally believed the problem was with the automounter, but it looks like it might be NFS instead. Rebooting with the old kernel solves the problem.
In this example, I'll create a new mountpoint, and try to mount my home directory. The directory is being served from a SUN Cluster 2.1 server.
# rm -rf /h
# mkdir -p /h/jminer
# mount superfly:/superfly/vol02/home/jminer /h/jminer
mount.nfs: /h/jminer is already mounted or busy
# echo $?
Now, if I try to mount the directory from the physical node, the mount suceeds.
# mount fly_a:/superfly/vol02/home/jminer /h/jminer
# echo $?
I saw similar problems with an earlier FC release, but it was related to either the autofs or nfs-utils package.
I just did a yum update on my son's computer. Now the cups daemon
won't start. Running /sbin/service cups start results in:
Unable to read configuration file '/etc/cups/cupsd.conf' - exiting!
I checked the permissions and they are root, lp 644.
If I run the same code as in the /etc/init.d/cups script, it starts
and works fine:
echo -n $"Starting $prog: "
[ $RETVAL = 0 ] && touch /var/lock/subsys/cups
Using su, I tested and user lp can read the cupsd.conf file.