D/l kernel and rebooted. Noticed error: could not find /proc/bus/usb
in fstab or mtab (actually I find that this error was there before, but
did not affect the problem). Any way, once logged in, my USB disk-key
is not found, though I can mount it manually.
Will bugzilla, though it is down ATM.
I've just installed fc3 x86_64. pkgconfig still uses /usr/lib/pkfconfig.
other than symbolic links or setting the env each time, is there a way to
tell it to check /usr/lib64?
I can't build any 64 apps on this machine.
Seth Vidal wrote:
>umm, the i386 ones that are available should be listed.
>it's not an either-or sort of thing.
What should exactarch be set to?
>the question you should ask is why didn't you get an /etc/rpm/platform
Dunno. Installed Friday. Except that i couldn't install gnome - bad rpm for
gnome-volume-manager - all seemed to go correctly.
Gnome volume manager has quit unexpectedly.
It says to click on restart application i do there are no icons on desktop
after i did a full update of FC3 final is there any way to fix this so gnome
will work right ?
Express yourself instantly with MSN Messenger! Download today - it's FREE!
Something has gone wrong which means I can't start my main linux box and it's
When I did an update to the current testing kernel, I had the error that
/proc/partitions couldn't be opened and as such, a conversion couldn't be
done. grubby then gave a fatal error.
When I do a reboot, the bootloader fires up, but when I choose a kernel, all I
get it that the kernel can't be found (file not found)
I have /boot on /dev/hda2
Any ideas on getting this working?
Get your free @ukpost.com account now
How is the updating of fedora-release pkg supposed to work? I've run
an extensive and complete update off of rawhide, but my release
package is still fedora-release-2.90-3.
Running `yum --obsoletes update fedora-release' doesn't find a package
of that name of course.
Since the most recent round of updates i've been having trouble with
ldconfig, apparently it's requiring the security context to be set
exactly right on everything and the libraries aren't configured that way
by default. ldconfig (or selinux, whatever actually handles this) wants
the context set to "system_u:object_r:shlib_t" where most of the
libraries are set to "system_u:object_r:lib_t" or
"root_u:object_r:lib_t". For most things this isn't that big of a deal,
but some things (such as wine or the nvidia driver) will fail since they
create the libraries just before trying to ldconfig them. Any help with
this is greatly appreciated.
Seth Vidal wrote:
>what does /etc/rpm/platform have in it?
Nothing. But since that did tell me what to google for, I found the yum
list. Inserted x86_64-redhat-linux.
But that's only half my Xmas wish. Now it's showing ONLY x86_64. From the
yum list messages I take it this is a function of exactarch and
transaction_color ( which I didn't see in macros ).
Seth Vidal wrote:
>Do you only have the i386 repositories configured?
Heres my .conf:
name=Fedora Core $releasever - Development Tree
In /etc/yum.repos.d all the .repo files have enabled=0
>if you do yum list available
>can you see packages listed as x86_64 ?
They're all noarch or i386.
yum -c /etc/yum.development-fedora-main.conf list available
Repository development already added, not adding again
Setting up Repo: development
repomd.xml 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
developmen: ################################################## 3767/3767
Canna-libs.i386 3.7p3-9 development
Xaw3d.i386 1.5E-1 development
alsa-lib.i386 1.0.6-6 development
anaconda-help.noarch 10.1.0-1 development
Any help appreciated.