Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
> On Wed, 7 Apr 2004, Jeff Elkins wrote:
> > I'm getting failure messages on my nfs mounts i.e. :
> > mount to NFS server 'music.elkins' failed: server is down.
> > nsfd appears to be running and I didn't see anything suspicious in the
> > The servers are up and running and have other clients connected.
> You didn't mention what steps you took to debug it:
> Can you ping the server?
> What is the output of rpcinfo -p servername?
> Does the server have access restrictions (firewall, TCP Wrappers, etc)?
I have the same symptoms...
rpcinfo says that nfs et.al. are running.
Something has changed in test 2, since the same PC running RH9
accesses that host just fine.
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 do not have the file /etc/sysconfig/selinux, nor can I find it using
shaka: sudo yum provides "/etc/sysconfig/selinux"
Gathering header information file(s) from server(s)
Server: Test Linux 2.6-test prerelease kernels for RHL9/rawhide
Server: Fedora Core 1.91 - i386 - Base
Server: Fedora Core RawHide
Server: Livna.org Fedora Compatible Packages (stable)
Server: Livna.org Fedora Compatible Packages (testing)
Server: macromedia.mplug.org - Flash Plugin
Finding updated packages
Downloading needed headers
Looking in available packages for a providing package
No packages found
Looking in installed packages for a providing package
No packages found
So, other than the release notes which talk about it, where is it? What
package provides it?
Brian Millett - Technologist Rex
"What a pleasure it is to deal with someone reasonable. Negotiations
are so much more enjoyable when certain individuals are not here to
-- Londo, "A Voice in the Wilderness I"
Yikes! For kicks, I appended "enforcing=-1" at grub prompt with latest
kernel. Things seemed normal until init started and hard drive spun like
crazy. I pulled the power when I smelled that cooking dust smell. I'm
writing this from a windows machine (web mail) until I have some time to
let my test system cool down.
Not strictly a general FC2 problem, but I've been testing under VMware
with reasonably good success. The latest arjanv kernel-2.6.5-1.326
(with the reiserfs fix) generates the following error on boot:
*** VMware Workstation internal monitor error ***
NOT_IMPLEMENTED at 602 (7568)
Have filed it with VMware.
Is it just me, or is kernel-2.6.5-1.332 bust? On an SMP i686 box it
hangs as init starts, on x86_64 it goes into an oops loop at initrd
Alex Kiernan, Principal Engineer, Development, THUS plc
I am running a FC2T1 install that I have continuously kept up2date,
typically via up2date, but sometimes using yum if up2date refused to work.
But anyways, I am now up to Test 3 status. However, after installing the
updates that brought me to Test 3 an issue came up. Now everytime I boot X
tries to run at 640x480. Consultation of the X.org.log reveals this error:
(II) I810(0): not using default mode "1024x768" (bad mode
(II) I810(0): Not using mode "1024x768" (no mode of this name)
(--) I810(0): Virtual size is 640x480 (pitch 1024)
Does anyone know why this occurs and how to fix it. I have the DVD ISO
downloaded and can burn that if a fresh install is the solution. I mean
this system has just be updated through the various test versions. I
haven't seen anaconda in a while so maybe I should... I just don't want to
if I can avoid doing a reinstall before the final.