Cannot use yum
by Sanjay S Nair
I have tried to install gd for php but i can't install got some error
[root@localhost ~]# yum -y install php php-gd
Loaded plugins: refresh-packagekit
livna | 2.1 kB
00:00
fedora | 2.4 kB
00:00
http://apt.sw.be/fedora/9/en/i386/dag/repodata/repomd.xml: [Errno 14] HTTP
Error 404: Not Found
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: dag.
Please verify its path and try again
Thanks
15 years, 9 months
update error on F9
by Paul Allen Newell
Finally managed to get FC5 upgraded to F9 by forgetting the upgrade and
doing a full re-installation (the thread on 6 -> 9 made it clear I had
to do that if I had any errors).
Even managed to get internet access which I could never do on FC5, so
I'm already ahead of the game.
I got the expected notice of all the stuff that needed to be updated via
pop-up and said "sure" after I had logged in as root to make sure there
would be no permissions issue. It failed with the following error message:
org.freedesktop.packagelist.update-system
auth_admin_keep_always
I tried from the other pulldown (admin?) for update system, got the
window, said update, it did nothing.
I was able to verify that I could get an update by downloading Firefox
3.0.1 (install DVD has Firefox 3 Beta 5) ... of course I couldn't
install it as I could figure it out since it wasn't the "ultra newbie"
Windows "download, click, install" system (since I've never had internet
access on Linux, I know this is another issue I have to learn ... and will).
My question to fedora-list is "what is the org.frredesktop.etc error and
how to I correct so it will work". If I need to go command line and do
it through yum, that's okay ... I just need a bit of guidance on the
process.
Thanks in advance,
Paul
15 years, 9 months
H.D. install problem -
by Bob Goodwin
I removed the 80gB WindowsXP hard drive [/dev/sda] and replaced it with
a larger drive on which I installed F9 from a Live CD. The second drive
[dev/sdb] has F8 on it, my primary Linux until this morning. I would
like to extract some configuration date from the F8 drive but have been
unable to access it no matter what I've tried. The problem is that it
uses the LVM designations which I can't seem to deal with instead of the
old "/dev/sda" etc. I am lost!
Fortunately I have another F8 computer with most of the config data
duplicated on it but I still want to be able to use the secocnd drive in
this box. I'm not sure what data to provide or even what question to
ask other than how do I go about getting access to the old F8 system.
Grub only offers the the new F9 install.
Fdisk shows the following:
# fdisk -l /dev/sda
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000a7927
Device Boot Start End Blocks Id System
/dev/sda1 * 1 25 200781 83 Linux
/dev/sda2 26 30401 243995220 8e Linux LVM
# fdisk -l /dev/sdb
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005c4cc
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 9729 78043770 8e Linux LVM
Any suggestions appreciated.
Bob
15 years, 9 months
Fedora Systems that were Updated
by Michael Semcheski
I've got six Fedora 8 and two Fedora 9 systems. I was on vacation
while the whole security incident happened and the announcement went
out not to update the systems. I guess that announcement got lost in
the mail. When I got back, I had a ton of email that I was trying to
get through, and I saw that there were updates available for the F8
and F9 systems. I applied the updates, then saw that there might be
an issue.
I'm not trying to be overly paranoid, I'm trying to be just paranoid
enough. I'd prefer not to have to take any drastic corrective
actions, but I will if I need to.
Should I rebuild all those systems? I get the sense that there were
no packages altered. I'm not running a financial institution. I do
keep tabs on what these machines are up to, but its not my sole, or
even primary concern.
15 years, 9 months
Format /dev/dsp expects?
by Mike McCarty
Can anyone tell me what formats /dev/dsp, /dev/dsp56k,
/dev/audio, etc. expect? It seems that I can copy
a WAV format file directly to /dev/dsp and get recognizable
sound. I wonder just what format they actually expect.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
15 years, 9 months
fglrx driver on F9 x86-64?
by Raymond C. Rodgers
Well, I haven't seen recent word on this so I thought I'd ask the public
at large. Has there been any update on the fglrx driver for Fedora 9
x86-64? F9 has been out for months now, and ATI/AMD has released several
versions of their driver since the F9 release date, but the fglrx driver
is still missing from the Livna repository, the official driver doesn't
seem to work, and I'm still getting unaccelerated video on my Radeon
HD3850. Anyone have any idea when this issue might get resolved?
Thanks,
Raymond
15 years, 9 months
safe to update F8 yet?
by Kevin Martin
With all of the 'information' being passed back and forth about the
Fedora intrusion, I've been unable to determine if it's really alright
to do an update yet? Anybody know for sure?
Thanks.
kevin
15 years, 9 months
Automount of CD-ROMs no longer works
by Mike McCarty
I replaced my CD-ROM writer with a DVD-ROM writer, and now automounting
of either CD-ROMs or DVD-ROMs no longer takes place. Instead, the
CD-Creator gets started up, as it does for a blank writable CD-ROM.
I can force a mount by hand, which works. All the files show up and
the disc is usable. However, the label on the disc is not recognized,
and the mounted icon on the desktop simply shows it as CDROM.
I replaced the DVD writer with a Memorex 48x CD-ROM drive I
have lying around, and the auto mount and label recognition
both work. Putting the DVD writer back in made the symptoms
return. Kudzu didn't report anything about the change whatever.
Hardware:
Compaq Presario 2.7GHz Celeron (i386 build)
Sony DRU-V200A[-BR] (shows symptoms)
Memorex CD-482E (does not show symptoms)
Software:
$ uname -a
Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686
i686 i386 GNU/Linux
Gnome
I am aware that FC2 is very old, no need to comment.
I checked
Red Hat->Preferences->CD and DVD
and under Data Discs both "Mount discs when inserted" and
"Start auto run programs when present" are checked.
Someone please advise me on how to proceed to get this
drive to work for me the way I would like.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
15 years, 9 months
Re: question on a kernal "uhhuh" message
by Dan Koehler
At 04:14 PM 8/25/2008, you wrote:
>Subject: question on a kernal "uhhuh" message
>To: fedora-list(a)redhat.com
>Message-ID: <48B31A7A.6040309(a)cs.cmu.edu>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>While running a long "yum update", I got the following message in the
>middle:
>
> (367/406): cscope-15.6-2.fc9.i386.rpm | 141
> kB 00:01
> (368/406): gstreamer-p 86% | 20% |== | 57 kB/s | 192
> kB 00:12 ETA
> Message from syslogd@chowder at Aug 25 11:55:03 ...
> kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.
>
> Message from syslogd@chowder at Aug 25 11:55:03 ...
> kernel: You have some hardware problem, likely on the PCI bus.
>
> Message from syslogd@chowder at Aug 25 11:55:03 ...
> kernel: Dazed and confused, but trying to continue
> (368/406): gstreamer-plugins-base-0.10.19-2.fc9.i386.rpm | 929
> kB 00:12
> (369/406): exempi-2.0.1-1.fc9.i386.rpm | 297
> kB 00:03
>
>I am assuming that the second occurrence of "(368/406):
>gstreamer-plugins-base-0.10.19.2.fc9.i386.rpm" indicates that it did
>finish that rpm given that the rpm_debug_check and Transaction Test
>seemed to have passed.
>
>So, I am figuring this is my computer burping somewhere. Even though it
>is trying to point me at my PCI bus, I do not know what test / diags I
>should be running to find out if there really is a hardware problem and,
>if so, where and then how to deal with it.
>
>Any suggestions appreciated ... if I can provide any more info, please
>let me know what would be helpful.
>
>This is related to my prior email "update error on F9 -- round two" if
>more context is needed.
>
>Thanks,
>Paul
The last time I got one of these "dazed and confused" messages was
when I was running a Fedora distribution on a motherboard with
multiple PCI domains. Do you get a "dazed and confused" message
during your boot process, or did it only show up during the yum update?
--
SCANNED for viruses and
dangerous content by MailScanner.
Believed to be clean.
15 years, 9 months
Re: "Permission denied" error for root user when perms are 0775?
by R. G. Newbury
From: Stuart Sears <stuart(a)sjsears.com>
[ edited for relevance ]
> > Thanks to both of you. Good pointers.
> > The drive is a partition on the same spindle, mounted '-t ext3
/dev/sda5
> > /keep', BUT /etc/fstab has the partition as 'users,defaults'...so it IS
> > possible that 'defaults' = 'noexec'...easily tested: thank you.
nope, it's not 'defaults', it's 'users':
from the mount manpage:
users - Allow every user to mount and unmount the file system. This
option implies the options noexec, nosuid, and nodev (unless overridden
by subsequent options, as in the option line users,exec,dev,suid).
IIRC 'user' has the same problems.
Regards,
Stuart
****************
Thank you, that is the likely answer. 'Defaults' allows 'exec', but you
have to read further down in the options to see that 'user' or 'users'
implies 'noexec'.
Thank you, thank you. Easy to test/check and I now think that could be
the actual problem.....And the fedora recovery environment uses a
different set of defaults, which would explain why I could run the
configure script at /mnt/sysimage/keep/mythtv, but NOT as root at
/keep/mythtv.
What it does NOT explain, however, is why I could not run the script
EVEN THOUGH I WAS ROOT!. It would explain the failure of my attempts as
user mythtv. But it does *feel* like progress. (Since if this is
correct, I should be able to run the script as a user, using sudo...)
Fingers crossed.
Geoff
15 years, 9 months