Re: list files but not directory
On 08/21/2009 12:58 PM, ann kok wrote: Hi any way to list files but not directory Thank you __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ Seems like a very reasonable request and its a shame that ls does not provide such an option (which I guess would be an extension to the -A option) Anyhow, if its OK to use grep, try this. ls -1A --indicator-style=slash |grep -v -E /$ The --indicator adds a / to the end of dirs, the grep excludes entries that end in / Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: list files but not directory
On 08/21/2009 03:35 PM, William Case wrote: Hi; On Fri, 2009-08-21 at 13:36 +0100, Albert Graham wrote: On 08/21/2009 12:58 PM, ann kok wrote: Hi any way to list files but not directory Thank you __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ Seems like a very reasonable request and its a shame that ls does not provide such an option (which I guess would be an extension to the -A option) I remember asking about this four or five years ago when I first started using Linux (RedHat). (It was the first question I asked on the users mailing list.) Now that I am familiar with 'find' and 'grep' etc. I no longer worry about it. However, 'ls' is probably the first commandline command a beginner learns. It seems illogical, that 'ls' wouldn't have a flag that just shows files when it has a flag for directories. It can cost newbies hours looking for a solution that isn't there. Couldn't the shell maintainers just add an appropriate flag to show files only? It would probably be easier to hack the ls source and extend the -A functionality. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: reliable gigabit NICs for fedora?
On 08/04/2009 02:41 AM, Tom Horsley wrote: I see just enough complaints about various gigabit network adapters in various versions of linux that I'm slightly leery of just buying whatever I can find and slapping it in the system :-). Anyone using gigabit (and actually using the bandwidth too :-) who can recommend some adapters that work well in fedora 11? I've got PCI as well as PCIE 1x slots available (PCI only in some systems though). If Jumbo frames are important to you, choose your hardware carefully, as some Gigabit nics (including some from Intel) cannot handle jumbo frames and some can but not full size i.e. 9k). Some examples (a bit old bit demonstrates a point). http://www.uoregon.edu/~joe/jumbo-clean-gear.html gripe For example, I recently purchased an Aopen MiniPC MP965-D, and it cannot do Jumbo Frames at all :( these particular devices are _extremely_ Linux unfriendly. /gripe -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: cachefilesd.ko missing in FC11
On 07/23/2009 01:54 PM, Albert Graham wrote:
Hi,
The init script for /etc/init.d/cachefilesd states:
echo -n $Starting $PROG:
# Load the cachefiles module if needed
[ -x $MODPROBE ] {
if ! /sbin/lsmod | grep cachefiles /dev/null ; then
$MODPROBE cachefiles $MODPROBE_ARGS || exit 1
fi
}
This implies there is a kernel modules called cachefiles.ko ? which
does not exist
# service cachefilesd start
Starting cachefilesd: FATAL: Module cachefiles not found.
The file called /sbin/cachefilesd is the userspace side of things
that relies on /proc/fs/cachefiles which I assume would be created by
the kernel module - if it existed ?
/sbin/cachefilesd -dns
Unable to open /proc/fs/cachefiles: errno 2 (No such file or directory)
Any ideas ?
Albert.
It seems that this is an existing bug outstanding since 2007 (Fedora 8)
https://bugzilla.redhat.com/show_bug.cgi?id=411051
Someone should probability remove the RPM from the Fedora repo as
suggested in the bug report.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
cachefilesd.ko missing in FC11
Hi,
The init script for /etc/init.d/cachefilesd states:
echo -n $Starting $PROG:
# Load the cachefiles module if needed
[ -x $MODPROBE ] {
if ! /sbin/lsmod | grep cachefiles /dev/null ; then
$MODPROBE cachefiles $MODPROBE_ARGS || exit 1
fi
}
This implies there is a kernel modules called cachefiles.ko ? which does
not exist
# service cachefilesd start
Starting cachefilesd: FATAL: Module cachefiles not found.
The file called /sbin/cachefilesd is the userspace side of things that
relies on /proc/fs/cachefiles which I assume would be created by the
kernel module - if it existed ?
/sbin/cachefilesd -dns
Unable to open /proc/fs/cachefiles: errno 2 (No such file or directory)
Any ideas ?
Albert.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Partitioning FC11 ??
On 07/19/2009 04:34 PM, Jim wrote: On 07/18/2009 11:12 PM, Albert Graham wrote: On 07/18/2009 02:15 AM, Jim wrote: My partition layout is sda1 ext3 /boot sda2 ext4 /home sda3 ext4 / sda4 Extended sda 5 Swap I want sda1 /boot to be my boot, why is it default selecting sda3 / , in Boot Loader Operating system list ?? Use fdisk to partition your disk how you want it (i.e. boot into rescue mode first), then install FC11, it will not be able to swap things around :) There should be a be an option in Anaconda that says something like Let fedora organize the disk layout or Let user organize the disk layout (God forbid!) I cannot understand why you even have the option to create custom disk layout if it's simply going to try an out smart you when you're done. Albert. Below is my /Grub/menulist file, Now that I have finnished installing. My partition layout; sda1 ext3 /boot sda2 ext4 /home sda3 ext4 / sda4 Extended sda 5 Swap How can I edit to boot off of sda1 /boot , instead of sda3 / . # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda3 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=0 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.29.5-191.fc11.i586) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.i586 ro root=UUID=992d6a7c-2f9a-4e6d-827a-79a37504bfbe rhgb quiet initrd /initrd-2.6.29.5-191.fc11.i586.img title Fedora (2.6.29.4-167.fc11.i586) root (hd0,0) kernel /vmlinuz-2.6.29.4-167.fc11.i586 ro root=UUID=992d6a7c-2f9a-4e6d-827a-79a37504bfbe rhgb quiet initrd /initrd-2.6.29.4-167.fc11.i586.img title Fedora (2.6.29.5-191.fc11.i586) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.i586 ro root=/dev/sda3 boot=/dev/sda1 rhgb quiet initrd /initrd-2.6.29.5-191.fc11.i586.img title Fedora (2.6.29.4-167.fc11.i586) root (hd0,0) kernel /vmlinuz-2.6.29.4-167.fc11.i586 ro root=/dev/sda3 boot=/dev/sda1 e rhgb quiet initrd /initrd-2.6.29.4-167.fc11.i586.img Should do the trick. If however you still want to use UUID get a list of UUIDs /dev/disk/by-uuid ls -la /dev/disk/by-uuid and change grub.conf accordingly. Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Partitioning FC11 ??
On 07/20/2009 02:40 PM, Don Quixote de la Mancha wrote: A kernel developer, I think from Red Hat, said on a list that lvm is 2% slower than a physical partition. Considering the obsession some folks have with performance, that seems like an awful lot to give up for some flexibility which really may not be at all helpful to some users. The reason for the overhead is basically that when you send the command over the wire to the actual disk, you have to give it an absolute Logical Block Address - relative to the beginning of the whole hard drive. Hard disk drives don't know from partitions or logical volumes. To convert a partition offset into a disk offset, you just add the starting sector of the disk. To get that starting sector, you have to look it up in a data structure that's maintained by the disk driver. I don't know how LVM is implemented, but I imagine there are some extra layers of indirection that enable that flexibility. The data structures involved will be more complex, as will be the code. They will also be more likely to be buggy as well. I've been setting up a bunch of partitions to run virtual machines on, for cross-platform development. While it's a PITA to keep repartitioning my RAID 5, I figure the extra effort is worth it for that consistently 2% faster disk I/O. Don Quixote quix...@dulcineatech.com http://www.dulcineatech.com/ Dulcinea Technologies: Software of Elegance and Beauty Thanks Don, I was going to make those exact points, however for performance reasons I go one step further and use the entire array without any partitions - this gives perfect raid chunk alignment :), and was infact the only way I could get the parallel and horizontal performance I needed (wanted). Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Partitioning FC11 ??
On 07/20/2009 04:15 PM, Jim wrote: On 07/20/2009 09:06 AM, Albert Graham wrote: boot=/dev/sda1 e rhgb quiet On the second kernel in your modification what is the e in boot=/dev/sda1 e rhgb quiet typo, :( Was hoping you would not notice :) Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Wirelsess N Draft 2 Mini PCI Card
On 07/14/2009 09:29 PM, Markus Kesaromous wrote: Does anyone know of a 802.11N-Draft 2 Mini PCI card that is currently supported by Linux? P.S: I know that the cards that have the Ralink rt28xx chipset series are NOT supported by linux, and even the Ralink provided driver does not work in F11. I have already posted a request for help about that and I was told effectively to firgetaboudit :) :) Cheers, Markus The EEEPC 1000 (Linux version) (I have two of em) do work perfectly with the Ralink rt2860 driver in Fedora 11, I connect @ 135Mb/s using WPA/WPA2 security, as a frontend to MythTV these machines are perfect :) In my case, I used the WebGui to set it up rather than Network Manager. I don't think Ivo's drivers (http://rt2x00.serialmonkey.com/) support N yet, but I'm sure they will at some point. Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest updates hosed NFS4?
On 07/17/2009 10:40 PM, Braden McDaniel wrote: My NFS4 mounts have gone south since the latest round of updates. Using mount directly yields this: # mount -t nfs4 hinge:/home/braden /mnt/foo mount.nfs4: Protocol not supported Anyone know what's going on? For now you can apply a quick fix: edit your /etc/init.d/nfs file as follows: Comment out line 97 and add the following line (which removes the -N 4.1) echo -n $Starting NFS daemon: # For now, turn off the nfs41 support # daemon rpc.nfsd -N 4.1 $RPCNFSDARGS $RPCNFSDCOUNT daemon rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT Then, restart your NFS server (service nfs restart) It should then work (mine does) Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
mount.nfs4: Protocol not supported
I already been posted this in response to someone else, but it may not be obvious to users of this problem. nfs-utils-lib-1.1.4-6.fc11.i586 nfs-utils-1.2.0-3.fc11.i586 Basically the latest nfs update disables NFS4, the server log file shows something like: Jul 18 10:47:10 username kernel: svc: 192.168.10.100, port=897: unknown version (4 for prog 13, nfsd) On the client, the message will be something like: mount.nfs4: Protocol not supported rpcinfo -p (on the server) will not show any version 4 protocols. The short term fix is: edit your /etc/init.d/nfs file as follows: Comment out line 97 and add the following line (which removes the -N 4.1) echo -n $Starting NFS daemon: # For now, turn off the nfs41 support # daemon rpc.nfsd -N 4.1 $RPCNFSDARGS $RPCNFSDCOUNT daemon rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT Then, restart your NFS server (service nfs restart) It should then work (mine does) Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
More than 7 DVB devices - How ?
Hi, I currently have 9 DVB devices, as the drivers are loaded a device in /dev/dvb is created typically: /dev/dvb/adapterX/demux0 /dev/dvb/adapterX/dvr0 /dev/dvb/adapterX/frontend0 /dev/dvb/adapterX/net0 However, there seems to be a limit of 8 devices (0-7), does anyone know how to extend the default limit ? While I'm on the point, I have the same problem with loop devices being limited to 0-7, in the old days you could add max_loop=64 etc.. in modprobe.conf, but that does not work anymore (since FC9 I think). Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Partitioning FC11 ??
On 07/18/2009 02:15 AM, Jim wrote: My partition layout is sda1 ext3 /boot sda2 ext4 /home sda3 ext4 / sda4 Extended sda 5 Swap I want sda1 /boot to be my boot, why is it default selecting sda3 / , in Boot Loader Operating system list ?? Use fdisk to partition your disk how you want it (i.e. boot into rescue mode first), then install FC11, it will not be able to swap things around :) There should be a be an option in Anaconda that says something like Let fedora organize the disk layout or Let user organize the disk layout (God forbid!) I cannot understand why you even have the option to create custom disk layout if it's simply going to try an out smart you when you're done. Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: PolicyKit - Authorizations - VNC - Add/Remove - Non-Root User
F-IN-A /* RANT ON I can't help but think that all of this policy junk on a default install of the Linux Operating System is akin to microsoft's implementation of the standard unix operating philosophy of operating as a non-root user. If we want to tighten up our security, then we should have tools such as Policy Kit to do this, and I am assuming that this is PolicyKit that is preventing me from running this and not some other bug. But its ridiculous to try the linux community in the same fashion that Microsoft treats the average household user. END RANT */ http://forums.fedoraforum.org/editpost.php?do=editpostp=1208467 Rediscover Hotmail®: Get e-mail storage that grows with you. Check it out. http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Storage2_042009 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Installing from a hard drive
Timothy, If you mount the ISO using -o loop and copy the install.img from the images directory and copy it to the same location as the actual ISO you are using (installing from), then try again. What I don't understand is why Anaconda simply cannot mount the ISO and get the install.img itself, having said this, it is documented at least. Albert. On 07/12/2009 03:25 AM, Timothy Murphy wrote: Is it possible to install from the ISO image of a live CD, in particular the Fedora-11 KDE Live CD? I followed the instructions at http://docs.fedoraproject.org/install-guide/f11/en-US/html/sn-expert- download.html which explicitly says Download the ISO image for a Live image before describing various installation methods, including Download the vmlinuz kernel file and the initrd.img ramdisk image from the distribution's isolinux/ directory. In my experience this does not work with the KDE Live CD. Have I misunderstood the instructions? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: How i start Network eth0 without NetworkManager
On 07/06/2009 08:26 PM, Frank Murphy wrote: On 06/07/09 20:23, Müslüm Ejder wrote: snip now i must start my Network Interface eth0 manually after every reboot. what can i do to start eth0 on Boot ? In a terminal su chkconfig --levels 345 network on Should do it. Regards, Frank You should probably add: chkconfig NetworkManager off -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Need help with WLAN on Eee PC 1000H
Hi Adalbert,
I have two of these EeePC 1000h, and WPA2 is not supported by the
default Linux OS installed,
I installed Fedora 10 via PXE boot (using a network cable) slooo..
but it worked out of the box.
I installed KDE only - which looks great cos the black theme matches the
black version of this machine so well - oops getting off track.
I then downloaded and compiled the
2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2 as per this thread:
http://forums.fedoraforum.org/showthread.php?t=199434 (details you need
at listed below).
However, I'm using the newer version 1.8 (and there may be a newer one
since, have not checked), I cannot remeber if it patched
(sta_ioctl.patch) cleanly or not or even if you need the patch in the
newer version, anyhow, reboot and it should work when you login.
TIP: If you have a USB Stick (mine was 1GB) unzip and compile the
drivers directly on that or better still, compile it on an NFS mount cos
the SDD disk is really slow :( (this does not effect the everyday
performance).
Also, don't mess with wpa_supplicant and what not (i.e chkconfig etc) ,
just let NetworkManager do it's stuff.
WPA2 works perfectly using this (and the network is very reliable).
I also installed a PAM module that automatically logged on to the
wireless when I log in (cos having to type in the Key Manager password
every time I login was just plain annoying).
(What would be nice is if it would connect via Wireless when in init 3
(like the cable) and use that connection for each user - and I think
that's on the cards for NetworkManager in the future).
INSTRUCTIONS FROM LINK ABOVE:
1. To be able to compile the driver we need a few extra packages. In the
terminal (as root), type
Code:
yum install gcc kernel-devel kernel-headers
2. Obtain the latest Ralink driver here (1.7.0.0 at the time of writing
this post)
3. Unzip the driver to a directory.
4. Open the directory, and go to
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_main_dev.c
5. Look up dev-nd_net and replace it with dev_net(dev), then save
the file and close it (thanx
toCiaran McCreesh’s Blag for this tip).
6. Open 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/config.mk and
change HAS_WPA_SUPPLICANT and
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT to y.
7. Download hdp's patch, and copy it to
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
8. Open a terminal, cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
and type patch sta_ioctl.c
sta_ioctl.patch
9. From the terminal cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0 and type
make, it should finish without
any errors.
10. Type make install, then when finished, exit the terminal.
11. If you restart the Eee PC and enable the wireless from the BIOS, it
should be recognized without
problems.
Best of luck.
Albert.
Adalbert Prokop wrote:
Hello!
Last week I wrote to the fedora-laptop list, bo nobody there was able to
help me. I need your help with my WLAN on a Asus Eee PC 1000H. It has a
Ralink WiFi card
--- 8 --- 8 --- 8 --- 8 --- 8 --- 8 ---
01:00.0 Network controller [0280]: RaLink Device [1814:0781]
Subsystem: RaLink Device [1814:2790]
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fbef (32-bit, non-prefetchable) [size=64K]
Capabilities: access denied
Kernel driver in use: rt2860
Kernel modules: rt2860sta
--- 8 --- 8 --- 8 --- 8 --- 8 --- 8 ---
I configured the rpmfusion repository and installed the rt2860
package. There was a small caveat - I had to do iwpriv ra0 radio_on in
order to do anything related with WLAN, but afterward scanning was
possible. But I can't connect my AP using Network Manager. Basically I
see those two lines in wpa_supplicant.log
Trying to associate with 00:18:f3:85:6a:31 (SSID='memphis' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.
NM keeps asking me for a password, but my input is definitely correct.
So I thought NM messes things up (as was my experience with my old
notebook) and I tried to get WLAN running using iwconfig +
wpa_supplicant configuration directly. Here is my wpa_supplicant.conf I
used.
--- 8 --- 8 --- 8 --- 8 --- 8 --- 8 ---
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid=memphis
scan_ssid=1
psk=myverysecretpassword
}
--- 8 --- 8 --- 8 --- 8 --- 8 --- 8 ---
But it did not work either, the Eee PC still could not connect to the AP.
The only way I can establish a WLAN connection is to compile the rt2860
driver from the Ralink homepage
(http://www.ralinktech.com/ralink/Home/Support/Linux.html) without any
patches and configure it *only* for wpa_supplicant support, not NM
support! Then and only then I can connect to my AP using WPA *but* I
have to use iwpriv command to set the encryption password! (iwpriv set
WPA=secret)
Did you succeed in using WLAN with F10 on Eee PC 1000H and if yes - how
did you do it? Do you have an idea how to convince Ralink's chip to
behave
yum broken after update
Hi I just did a yum update yum* and now yum is completely broken ? Any idea how to fix this ? (or link to fixed yum rpm) Here is what happened: [EMAIL PROTECTED] yum update yum* Loading allowdowngrade plugin Loading basearchonly plugin Loading changelog plugin Loading downloadonly plugin Loading fedorakmod plugin Loading merge-conf plugin Loading presto plugin Loading priorities plugin Loading protect-packages plugin Loading protectbase plugin Loading refresh-updatesd plugin Loading security plugin Loading skip-broken plugin Loading tsflags plugin Loading versionlock plugin Setting up and reading Presto delta metadata No Presto metadata available for updates-newkey No Presto metadata available for fedora updates | 2.6 kB 00:00 No Presto metadata available for updates 0 packages excluded due to repository protections Skipping security plugin, no data Reading version lock configuration Setting up Update Process Resolving Dependencies Skipping security plugin, no data -- Running transaction check --- Package yum-downloadonly.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-fedorakmod.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-priorities.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-basearchonly.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-refresh-updatesd.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-fastestmirror.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-versionlock.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-protect-packages.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-updateonboot.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-allowdowngrade.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-security.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-skip-broken.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-tsflags.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-utils.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-merge-conf.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-protectbase.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum-changelog.noarch 0:1.1.15-1.fc8 set to be updated --- Package yum.noarch 0:3.2.19-3.fc8 set to be updated -- Processing Dependency: pygpgme for package: yum -- Running transaction check --- Package pygpgme.i386 0:0.1-6.fc8 set to be updated -- Finished Dependency Resolution Dependencies Resolved = Package Arch Version RepositorySize = Updating: yum noarch 3.2.19-3.fc8 updates-newkey831 k yum-allowdowngrade noarch 1.1.15-1.fc8 updates-newkey8.3 k yum-basearchonlynoarch 1.1.15-1.fc8 updates-newkey8.8 k yum-changelog noarch 1.1.15-1.fc8 updates-newkey 12 k yum-downloadonlynoarch 1.1.15-1.fc8 updates-newkey8.3 k yum-fastestmirror noarch 1.1.15-1.fc8 updates-newkey 12 k yum-fedorakmod noarch 1.1.15-1.fc8 updates-newkey 11 k yum-merge-conf noarch 1.1.15-1.fc8 updates-newkey9.7 k yum-priorities noarch 1.1.15-1.fc8 updates-newkey9.7 k yum-protect-packagesnoarch 1.1.15-1.fc8 updates-newkey9.2 k yum-protectbase noarch 1.1.15-1.fc8 updates-newkey8.6 k yum-refresh-updatesdnoarch 1.1.15-1.fc8 updates-newkey8.5 k yum-securitynoarch 1.1.15-1.fc8 updates-newkey 15 k yum-skip-broken noarch 1.1.15-1.fc8 updates-newkey9.4 k yum-tsflags noarch 1.1.15-1.fc8 updates-newkey8.1 k yum-updateonbootnoarch 1.1.15-1.fc8 updates-newkey 10 k yum-utils noarch 1.1.15-1.fc8 updates-newkey 63 k yum-versionlock noarch 1.1.15-1.fc8 updates-newkey 12 k Installing for dependencies: pygpgme i386 0.1-6.fc8fedora 30 k Transaction Summary = Install 1 Package(s) Update 18 Package(s) Remove 0 Package(s) Total download size: 1.1 M Is this ok [y/N]: y Downloading Packages: Downloading DeltaRPMs: Rebuilding rpms from deltarpms warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 6df2196f Importing GPG key 0x6DF2196F Fedora (8 and 9) [EMAIL PROTECTED] from /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-8-and-9 Is this ok [y/N]: y Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: pygpgme ### [ 1/37] Updating : yum ### [
Re: yum broken after update
Thanks Rahul, That worked :) I'd never paid attention as to what all those plug-ins do and whether I needed them :( Albert. Rahul Sundaram wrote: Albert Graham wrote: Hi I just did a yum update yum* and now yum is completely broken ? Any idea how to fix this ? (or link to fixed yum rpm) rpm -e yum-skip-broken You don't need so many plugins. Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Reboot does not work on any machine
Hi Guys, I'm hoping someone can throw some light on this problem. Basically, reboot and shutdown do not fully work on any of my machines, (all are running Fedora 8) The machines vary from Laptops to Desktops and Mini-PCs (e.g. Aopen MP965-DR) they are currently running kernels version 2.6.26.3-14, but this problem started to appear last year sometime maybe around kernel 2.6.21 ish. When I run reboot it outputs the following and simply sits there: INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signal INIT: no more processes left in this runlevel After pressing the power button, the system shuts down all the services with the last two lines stating instead of powering off. Halting System... System halted. Then sits there... However the real problem is the CPU seems to be running at 100% (this is a guess), but my laptop's motherboard (Cleveo D900T) burnt out :) - it was running MythTV front end and was turned off by the other half who didn't realize the machine was running... :( Changes the power management settings in the BIOS makes no difference or whether or not acpid is running :( Here is a list of services I'm running: [EMAIL PROTECTED] ~]# chkconfig --list|grep 3:on ConsoleKit 0:off 1:off 2:on3:on4:on5:on6:off acpid 0:off 1:off 2:on3:on4:on5:on6:off autofs 0:off 1:off 2:on3:on4:on5:on6:off cpuspeed0:off 1:on2:on3:on4:on5:on6:off lirc0:off 1:off 2:on3:on4:on5:on6:off lm_sensors 0:off 1:off 2:on3:on4:on5:on6:off messagebus 0:off 1:off 2:on3:on4:on5:on6:off netfs 0:off 1:off 2:on3:on4:on5:on6:off network 0:off 1:on2:on3:on4:on5:on6:off nfs 0:off 1:off 2:on3:on4:on5:on6:off nfslock 0:off 1:off 2:on3:on4:on5:on6:off rpcbind 0:off 1:off 2:on3:on4:on5:on6:off rpcgssd 0:off 1:off 2:on3:on4:on5:on6:off rpcidmapd 0:off 1:off 2:on3:on4:on5:on6:off rsyslog 0:off 1:off 2:on3:on4:on5:on6:off sshd0:off 1:on2:on3:on4:on5:on6:on udev-post 0:off 1:off 2:off 3:on4:on5:on6:off xinetd 0:off 1:off 2:off 3:on4:on5:on6:off Any help would be very much appreciated. Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Reboot does not work on any machine
Just doing some testing and even if I boot the kernel in runlevel 1, reboot still does not work - strange... -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Reboot does not work on any machine
Patrick O'Callaghan wrote: On Sat, 2008-09-20 at 21:36 +0100, Albert Graham wrote: When I run reboot it outputs the following and simply sits there: INIT: Switching to runlevel: 6 Does your /etc/inittab have the default level set to 6? If so, try changing it to 5, which is the usual value. poc No, it's set to 3, however other machines do have it set to 5. The strange thing is, you would expect it to work run runlevel 1, reboot is a symlink to halt as follows: [EMAIL PROTECTED] ~]# file `which reboot` /sbin/reboot: symbolic link to `halt' [EMAIL PROTECTED] ~]# file `which halt` /sbin/halt: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped [EMAIL PROTECTED] ~]# which halt /sbin/halt [EMAIL PROTECTED] ~]# md5sum /sbin/halt a53feb292a2508e899fa07db97e3829f /sbin/halt [EMAIL PROTECTED] ~]# rpm -q --whatprovides /sbin/halt sysvinit-2.86-18 Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: More Qlogic driver madness.
Mark Haney wrote: This is really getting silly. How is it possible that an initrd will not USE the firmware included with it to allow me to initialize my Qlogic FC card? I've built my own, I've read everything I can about initrd and initramfs and I'm still stuck. Are there tools included with Fedora that let me edit/muck initramfs settings? Or do I have to roll my own? I just don't get it, between FC6 2.6.20 and 2.6.22 kernels in FC6 this capability was broken and no one's complained? I'm really very tempted to file a bug report on this for F8 and hope it gets fixed that way, since I'm unable to find an answer. Mark, Try something like, 1. Add your qlogic entries to your /etc/modprobe.conf (so that step 3 below will include and load the drivers) 2. Backup your current initrd image mv /boot/initrd-$(uname -r).img mv /boot/initrd-$(uname -r).img-OLD 3. Create a new initrd mkinitrd -v /boot/initrd-$(uname -r).img $(uname -r) If the card has a newer firmware version than the driver, it should not use the driver version - normally. Question: Why the need to build your own - they are included in Fedora, check with: ls -la /lib/modules/$(uname -r)/kernel/drivers/scsi/qla* Albert. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
