Yesterday I was trying to update my FC6 laptop. Quite a few updates,
because this system was not used that much recently.
I did not use the updates applet, because I was on a restrictive
network: first establish a VPN connection, then you can use a proxy
through VPN to browse the Internet.
Since this is not my typical location, the proxy was not set in the
So I had to run yum manually in a terminal window. First do an "export
http_proxy=..." then run yum.
Halfway through the update, X was killed by some script in one of the
update packages. Of course, that also killed yum, mid-transaction. :-(
Init restarted X, of course, but now I was staring at the gdm login screen.
This is pretty rude, not to mention that killing yum in the middle of a
transaction can leave the system in a messy state.
I'm not sure what needs to be fixed (don't kill X, or make yum or rpm
smarter and don't kill X if the session is being run from within X, or
something like that), I don't even know which package caused that, but
my take is that this is something that needs to be fixed.
Effective immediately, registration for SCALE 5X is available at
http://www.socallinuxexpo.org/order. The Early bird ticket price is $60
for full admission with a $30 admission for students with valid ID.
Fedora developers can use the FDORA promotional code for a 40%
discount on the full access pass. Prices go up Jan 24th, so don't dawdle;
get registered now!
If you're interested in seeing who's participating in SCALE, the
exhibitor list is at http://socallinuxexpo.com/scale5x/exhibitions.php
Fedora will be exhibiting at the show, come out and support your
A partial list of speakers can be viewed at
SCALE will be February 10-11, 2007, at The Westin Los Angeles Airport.
For those staying over, The Westin is offering special hotel room rates
for the Expo. Hotel information is available here:
Gareth J. Greenaway | g(a)socallinuxexpo.org
Voice - 877-831-2569 x130
Southern California Linux Expo
We should more proactively discourage static linking in FC7+, for
reasons for that see
Removing libc.a would be most effective, but I'm afraid we still need
a handful of statically linked binaries for boot time initialization and
system recovery utilities.
So, I think it would be best if we could analyze what in FC7/FE7
is linked statically, why, if it really needs to be linked that way
and what *.a libraries does it link in and kill all other *.a libraries
(unless the library is only in *.a form, examples libbfd.a,
libc_nonshared.a, libpthread_nonshared.a, libsupc++.a, libgfortranbegin.a)
and kill all other libraries.
E.g. ideally we'd drop libpthread.a, librt.a, libstdc++.a, libgfortran.a,
libboost*.a, all GUI libs that have also *.so libs, etc.
Is there a reason why fedora does not support blowfish (at least through
the various included tools, system-config-authentication etc.) for
From my understanding, Blowfish provides encryption far superior to
even MD5 and there should no license problems.
Even though MD5 might seem hard-enough-to-crack, why would we stop there?
Also, it seems like supporting blowfish would not be very hard to
implement in fedora, so why don't we?
(and the unavoidable:) Other linux distros have Blowfish encryption for
tcp_wrappers has two new sub packages: tcp_wrappers-devel and
All build requirements for tcp_wrappers have to get changed to
Software Engineer Phone: +49-711-96437-310
Red Hat GmbH Fax : +49-711-96437-111
Hauptstaetterstr. 58 Email: Thomas Woerner <twoerner(a)redhat.com>
D-70178 Stuttgart Web : http://www.redhat.de/
Sorry for the cross posting (I can't really decide which list was better...)
I'm seeing this regression (compared to FC-5, where it used to work
fine) on the hibernate function with this laptop, an ASUS M6Ne
(Centrino 1.7Ghz, 512Mb RAM, ATI mobility radeon 9700, _not_ using any
proprietary kernel modules)
Basically, the hibernate procedure go as far as the "shutting down
hda" message, then fails to turn off power.
I am forced to turn it off manually. Otherwise the operation seems working.
Anyone else with similar symptoms?
Moreover, I saw from time to time a screen of kernel error messages (
a stack trace ?) on the consule during wake up operation, but I am not
sure if this was generated during hibernation.
I will try to find a pattern for this and eventually post agina more details.
I am installing FC-6 onto a brand new server (HP ProLiant ML 350 G5);
my usual PXE+HTTP installation went just fine.
However, during the first update, I was logged out from X and returned
to the gdm screen.
The last package I can see in /var/log/yum.log is
Now "yum update" fails becuase python-devel confilcts with python <
2.4.4-1.fc6, but I am able to fix this by "yum remove python-2.4.4"
before doing the new "yum update".
Please also note this happened twice, the former being when I
installed the i386 arch while waiting the download of the X86_64 DVD.
Does anyone else saw this?