Fedora-Related Speaking Opportunity
by William R. Lorenz
Hi Everyone,
I'm working as part of the Ohio LinuxFest team to coordinate this year's
event. We drew people from all throughout the Mid-West last year: Ohio,
Pennsylvania, Michigan, West Virginia, Tennessee, Kentucky, and Illinois.
We're planning an even bigger and better event for this year, with speaker
representation from the The Apache Software Foundation, Novell, Samba, and
more. We have confirmed talks from many authoritative speakers on many
interesting topics. The event is free to attend (registration required so
that we know how many to expect), and it will be held in Columbus, Ohio.
Our website is at http://www.ohiolinux.org/, so you can check us out.
I'd like to find a good speaker to represent the Fedora project, and I'm
hoping I might find a talkative Fedora developer here who is interested in
the opportunity. I'm open to many talk ideas, and if you happen to be an
eager Fedora devloper willing to talk at the event, I'd love to help you
secure a timeslot at the event this year if you can contact me off-list.
I myself use and love Fedora, and so I'd like to help make it happen.
In any case, I do hope I might hear from some of you. Tnx, in advance.
-- _
__ __ ___ _| | William R. Lorenz <wrl(a)express.org>
\ V V / '_| | http://www.clevelandlug.net/ ; "Every revolution was
\./\./|_| |_| first a thought in one man's mind." - Ralph Waldo Emerson
19 years, 10 months
ethereal update package broken
by Matthew Miller
Hmmm. When I rebuild the ethereal-0.10.5-0.2.1.src.rpm, the resulting
packages won't install, complaining about a missing dependency
'libethereal.so.0'.
A bit more investigation reveals this interesting difference:
Original FC2 package:
$ rpm -qlp ethereal-0.10.3-2.i386.rpm |grep libethereal
/usr/lib/libethereal.so
/usr/lib/libethereal.so.0
/usr/lib/libethereal.so.0.0.1
Update package:
$ rpm -qlp ethereal-0.10.5-0.2.1.i386.rpm |grep libethereal
/usr/lib/libethereal
/usr/lib/libethereal.0
/usr/lib/libethereal.0.0.1
Hey! What happened to the .so? This is the case with both my rebuilt package
and the distributed update binary.
But there's more --
Original FC2 package:
$ rpm -qlp ethereal-0.10.3-2.i386.rpm |grep ethereal/plugins
/usr/lib/ethereal/plugins
/usr/lib/ethereal/plugins/0.10.3
/usr/lib/ethereal/plugins/0.10.3/acn.so
/usr/lib/ethereal/plugins/0.10.3/artnet.so
/usr/lib/ethereal/plugins/0.10.3/asn1.so
/usr/lib/ethereal/plugins/0.10.3/ciscosm.so
/usr/lib/ethereal/plugins/0.10.3/coseventcomm.so
/usr/lib/ethereal/plugins/0.10.3/cosnaming.so
/usr/lib/ethereal/plugins/0.10.3/docsis.so
/usr/lib/ethereal/plugins/0.10.3/enttec.so
/usr/lib/ethereal/plugins/0.10.3/gryphon.so
/usr/lib/ethereal/plugins/0.10.3/irda.so
/usr/lib/ethereal/plugins/0.10.3/lwres.so
/usr/lib/ethereal/plugins/0.10.3/megaco.so
/usr/lib/ethereal/plugins/0.10.3/mgcp.so
/usr/lib/ethereal/plugins/0.10.3/pcli.so
/usr/lib/ethereal/plugins/0.10.3/rdm.so
/usr/lib/ethereal/plugins/0.10.3/rlm.so
/usr/lib/ethereal/plugins/0.10.3/rtnet.so
/usr/lib/ethereal/plugins/0.10.3/rudp.so
/usr/lib/ethereal/plugins/0.10.3/v5ua.so
Update package:
$ rpm -qlp ethereal-0.10.5-0.2.1.i386.rpm | grep ethereal/plugins
/usr/lib/ethereal/plugins
/usr/lib/ethereal/plugins/0.10.5
My rebuilt version of the update package:
$ rpm -qlp ethereal-0.10.5-0.2.1bu40.1.i386.rpm | grep ethereal/plugins
/usr/lib/ethereal/plugins
/usr/lib/ethereal/plugins/0.10.5
/usr/lib/ethereal/plugins/0.10.5/acn.so
/usr/lib/ethereal/plugins/0.10.5/artnet.so
/usr/lib/ethereal/plugins/0.10.5/asn1.so
/usr/lib/ethereal/plugins/0.10.5/ciscosm.so
/usr/lib/ethereal/plugins/0.10.5/coseventcomm.so
/usr/lib/ethereal/plugins/0.10.5/cosnaming.so
/usr/lib/ethereal/plugins/0.10.5/docsis.so
/usr/lib/ethereal/plugins/0.10.5/enttec.so
/usr/lib/ethereal/plugins/0.10.5/gryphon.so
/usr/lib/ethereal/plugins/0.10.5/irda.so
/usr/lib/ethereal/plugins/0.10.5/lwres.so
/usr/lib/ethereal/plugins/0.10.5/megaco.so
/usr/lib/ethereal/plugins/0.10.5/mgcp.so
/usr/lib/ethereal/plugins/0.10.5/pcli.so
/usr/lib/ethereal/plugins/0.10.5/rdm.so
/usr/lib/ethereal/plugins/0.10.5/rlm.so
/usr/lib/ethereal/plugins/0.10.5/rtnet.so
/usr/lib/ethereal/plugins/0.10.5/rudp.so
/usr/lib/ethereal/plugins/0.10.5/v5ua.so
And, it turns out that these plugins are the ones that are linked against
the missing libethereal.so.0 -- the update binary only works because it's
missing all of its plugins.
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127945>
--
Matthew Miller mattdm(a)mattdm.org <http://www.mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
19 years, 10 months
Progeny & Componentization
by Mike Fedyk
http://www.orangecrate.com/article.php?sid=757
This sounds like a direction Fedora is already headed in, but now it can
be termed "componentization"...
*Chuck Talk*: I know that Progeny has developed the idea of
componentized Linux for developers to build their Linux environment
"from the bottom-up", can you explain what that means in terms of
building a Linux distribution?
*Jeff Licquia*: In the past, people building custom Linux distributions
have generally started with a standard distribution, stripped out the
parts they don't need, and added or altered the features that they need.
This results in a fork, with all that forking entails; the group doing
the distribution now has to get into the Linux distribution business,
spending lots of resources on things that are peripheral to the group's
main purpose.
Componentized Linux is a different way to build custom Linux
distributions. People pick and choose the standard components they need,
build their own components for features that they need that aren't yet
available, and put it all together to produce a complete distribution.
In doing so, the work to maintain the core Linux components is shared
among several groups of people with similar goals, with each group
focusing on the part of the puzzle that they do best.
19 years, 10 months
man pages
by Lawrence Bowie
Is it me or is the makewhatis db not being created on Fedora Core 2?
Thanks,
LDB
19 years, 10 months
autoreconf Best Practice?
by Toshio Kuratomi
Some months ago I asked whether patching or rerunning the auto* tools was
the better method when modifying build files in a spec file. This
question is for those that thought that using the auto* tools was the right
way to go.
I've recently run across autoreconf [1]_ in the autoconf toolset and
wondered if the best way to rebuild build scripts would be something like::
%setup
# Patch to configure.in, Makefile.am, etc
%patch0 -p1
%build
autoreconf
...
Is this cleaner than using libtoolize --force or autogen.sh?
If so, are there some options that would be appropriate to always pass to
autoreconf? --force --install seem like likely candidates.
Thanks for input,
-Toshio
[1] http://www.freebsdchina.org/utils/phpMan.php/info/autoreconf
19 years, 10 months
s390 lcs kernel module problem
by Matthias Saou
Hi,
I'm trying to fool around with hercules to get an emulated s390 system
running and play around with it, unfortunately I'm not able to get the CTCI
networking working (attempted to kill init, it worked with Red Hat Linux
7.2, doesn't with Fedora Core Development), so I decided to give LCS a try,
as FC says it supports it, unfortunately, it looks like the lcs kernel
module has a problem :
lcs: Unknown symbol cu3088_type
lcs: Unknown symbol unregister_cu3088_discipline
lcs: Unknown symbol register_cu3088_discipline
This looks like a bug, one that doesn't bite many people, though ;-)
The running kernel is 2.6.7-1.492.
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 2 (Tettnang) - Linux kernel 2.6.6-1.435.2.3
Load : 0.04 0.19 0.22
19 years, 10 months
pppd active-filter outbound problem
by Bruno Wolff III
I am having trouble running pppd using the active-filter outbound option.
I am using FC2 with some things from development, in particular:
ppp-2.4.2-3.1
libpcap-0.8.3-4
kernel-2.6.7-1.471
on a dual athlon system.
The error message I am getting is:
pppd: error in active-filter expression: inbound/outbound not supported on linktype 0
This makes it seem like either the kernel or ppp is checking the link
type before ppp has set the link type.
19 years, 10 months