I don't know the right way to fix this, but something is definitely broken;
and something needs to be fixed, one way or the other. The question is what
exactly needs to be fixed.
Consider something like this:
AC_TRY_LINK_FUNC(res_query, AC_MSG_RESULT(yes), AC_MSG_RESULT(no))
Here's what happens on x86_64:
gcc -o conftest -g -O2 -Wall -I.. -I./.. conftest.c -lresolv >&5
/tmp/ccW7EeDX.o(.text+0x7): In function `main':
/home/mrsam/src/courier/authlib/configure:5160: undefined reference to
collect2: ld returned 1 exit status
configure:5147: $? = 1
configure: failed program was:
[ blah blah blah ]
| /* We use char because int might match the return type of a gcc2
| builtin and then its argument prototype would still apply. */
| char res_query ();
| main ()
| res_query ();
| return 0;
The same exact test on FC1 x86 will work.
The reason appears to be that you have to #include <resolv.conf> on x86_64
in order to succesfully pull res_query() out of libresolv.so. You don't
need to do this on x86, and the test program generated by AC_TRY_LINK_FUNC
does not include any headers, but uses a manual prototype.
So, what now?
I saw zeroconf in action at a Mac based facility a while back and I have
to say I was impressed. It makes their networking setup very easy. The
biggest downside was that they knew very little about how their network
actually worked. That made my life integrating a Linux system in to
their environment much more difficult. So, I'd like to see zeroconf
really integrated in to FC5. I think it'll make network setup for a lot
of users much easier.
For those who don't know, zeroconf provides several functions:
*) Dynamically allocating an IP address to a system when it boots
(without requiring a DHCP server)
*) Translate between names and IP addresses (without any setup or
*) Allows for the publishing and discovery of services such as DNS,
NFS, ftp, http, printers, whatever (without requiring any setup or
*) Allocates multicast addresses (without a MADCAP server). (This part
isn't yet supported and I'm not sure I know what it means :))
Fedora ships with Howl which looks to be the framework for doing
zeroconf. It seems that what's needed is integrating howl in to all the
I have been a Fedora user since FC1, and now I'd like to contribute to
the project. I know some Python, but no GUI (as yet). My more tested
programming skills lie is pascal and delphi. I am interested in building
a cnfiguration tool for sshd to help me learn the python language
better, and also to contribute to the fedora project. But I need some help:
Knowledge - HOWTOs, tutorial, whitepapers, etc that I need to read to
properly write a system-config applicat ion
Rules - Standards, and guidelines that I shoudl follow
Technologies - gui toolkits, modules, etc that I should stick to in
learning and building a system-config tool.
Thanks for your assistance and time.
PS: the fedora-config-list is dead, so I'm reposting here
once dbus-qt was removed from fedora because there was no use for it. but now
kde 3.4 supports dbus-qt for the media:/ protocol which indicated if a new
device was connected. so there now is a use for dbus-qt so i think it ought
to be included.
Frederick Alexander Thomssen
On amd64 with radeon 8500, dmesg:
Bootdata ok (command line is root=/dev/hda5
Linux version 2.6.12-1.1437_FC5
(bhcompile(a)crowe.devel.redhat.com) (gcc version 4.0.1
20050720 (Red Hat 4.0.1-4)) #1 SMP Mon
Jul 25 18:21:05 EDT 2005
This used to give console output at 1024x768. Even a couple
of weeks ago, maybe. Now I get a vga display.
Have the kernel switches changed?
Subject: Re: Raising the bar for FC4
X-Operating-System: Linux concerto.rednote.net 2.6.11-1.14_FC3spksmp
Organization: Capital Accessibility LLC (http://www.CapitalAccessibility.com)
I understand the telnet bug fix is now in CVS, so can this fix please
Those of us who really need telnet install, REALLY need it. For us it's
I may be mistaken, but I believe it does not impact anyone who isn't
actually needing it.
Thanks also to Jeremy Katz for getting the fix in, and to Jim Cornette
for his help reporting the problem in the first instance.
Elliot Lee writes:
> Hi all,
> Fedora Core 4 public release is currently targeted for Monday, June 6. To
> hit that, we need some time in advance doing QA and final polishing. For
> test releases that is usually about a week, but this is the final FC4
> release so we need a bit of extra time to do the final steps.
> This means that Monday, May 23 is the final final freeze for FC4. After
> that, the bar for accepting changes into FC4 is even higher. Fixes will
> need to be for showstopper bugs (data corruption, crashing programs, and
> other things that impact a large percentage of users in a major way). I've
> sent out reminder e-mails to people who currently own FC4Target and
> FC4Blocker bugs in bugzilla, so you should know if you have specific bugs
> to address.
> If you don't have any bugs to address, you can still help by doing test
> installs of rawhide. I'll also try to get a few intermediate test trees
> out for people to install.
> If the plan needs clarification, please let me know!
> -- Elliot
> fedora-test-list mailing list
> To unsubscribe:
Chair, Accessibility Workgroup Free Standards Group (FSG)
Janina Sajka Phone: +1.202.494.7040
Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more.
I've started a new thread because this discussion was going to get lost
in the 200+ message thread-o-doom.
So so far we have the introduction of gnome-user-share, which uses an
http process dynamically bound to a port running as the user to share
stuff in a ~/Public file to the world w/out auth. It sounds like
gnome-user-auth will go into core. The restrictions have been put
* Functionality is provided by a package and removed by a package, w/out
* Functionality is controlled by a gconf entry which an admin can set to
mandatory off (or just remove the package)
Some ideas that have floated for this package include:
* Functionality disabled until a file is placed in ~/Public prompting
for a dialog box informing the user that the share is now active, with a
link to more help in this.
* Gnome-panel icon to show state of sharing with a timeout value to stop
the share (configurable)
* Integration with network-manager to enable/disable the share on
Jesse Keating RHCE (geek.j2solutions.net)
Fedora Legacy Team (www.fedoralegacy.org)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know:
>From kernel 1432 and 1433 in rawhide my boot process has some serious
delays where my system doesn't seem to do anything and doesn't respond.
This also happens when logining in and starting gnome.
I made a bootchart from the 1426 kernel which runs fine and one form
1433 which suffers from those delays.
Bart Vanbrabant <bart.vanbrabant(a)zoeloelip.be>
PGP fingerprint: 093C BB84 17F6 3AA6 6D5E FC4F 84E1 FED1 E426 64D1
Can somebody please point me at a good resource for understanding how
exec-shield and memory randomization work?
Specifically, I'm trying to understand the randomize_va_space variable
Is randomize_va_space independent of /proc/sys/kernel/exec-shield? That
is, if I "echo 0 > /proc/sys/kernel/exec-shield", I would have thought
that would also turn off memory randomization, but that doesn't seem to
be the case. Are things supposed to work that way, or am I goofing
Finally, is there a way to disable randomization on a per-binary basis
(with an ELF flag or lack thereof)? I seem have a binary (sbcl) that
doesn't like memory randomization. Rather than turn it off globally, I'd
rather just mark the binary as incompatible with it.
Dave Roberts <ldave(a)droberts.com>
It's very quiet on this list about printing, so I thought it would be a
nice idea to put forward a proposal. I don't know if there are internal
redhat discussions about this subject, but I think I'll find out soon :).
It's a rahter lengthy explanation with a diagram so I put it up here: