not sure this is the best place, but...
by Gary Kline
guys,
I rely on a python script that *I* did not write to make my
keys click. {i've already run thru two expensive "clicky"
keyboards... .} anyway, my click program no longer works.
it cant find "Xlib" I have no clue. so I did a
# yum install python*
to see if that got the missing parts. it turns out that there
is, indeed, something that is program in the install. the
key-click.py script has been working on ubuntu and now on
fedora-17. I'm wondering if this:
--> Running transaction check
---> Package hunspell-en-GB.noarch 0:0.20110318-9.fc17 will be installed
---> Package python-tahrir.noarch 0:0.1.8-1.fc17 will be installed
--> Processing Dependency: python-pyramid-tm for package:
python-tahrir-0.1.8-1.fc17.noarch
--> Finished Dependency Resolution
Error: Package: python-tahrir-0.1.8-1.fc17.noarch (updates)
Requires: python-pyramid-tm
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
might be the cause of my click error:
pts/4 15:17 <tao> [3851] ./key_click.py
~/bin/keyclick/src/keyclick
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
Traceback (most recent call last):
File "./key_click.py", line 37, in <module>
import xlib
File "/home/kline/bin/keyclick/src/keyclick/xlib.py", line 25, in
<module>
from Xlib import display
ImportError: No module named Xlib
Another thought is that under gnome, the click program worked.
any ideas?
gary
PS: I Want to port this keyclick program to C because it is a
load hog... .
--
Gary Kline kline(a)thought.org http://www.thought.org Public Service Unix
Twenty-six years of service to the Unix community.
11 years, 3 months
how-to yum remove gnome anf yum install kde?
by Gary Kline
I found out how to install Fed-17 [[somehow]]; I now have Gnome
that I do not prefer. I've install konsole and I have a bunch of
KDE libraries.
Q: what is the best way to remove gnome and install KDE? Last time
it messed up my UEFI {?}{bootloader}. this time I want to be
Extremely careful.
--
Gary Kline kline(a)thought.org http://www.thought.org Public Service Unix
Twenty-six years of service to the Unix community.
11 years, 3 months
Bash - an odd problem using sed or awk or for
by John Horne
Hello,
I have a bash script in which a variable is set to one or more lines of
text. What I want is to remove any lines up to and including a blank
line (or alternatively to echo all the lines after the last blank line).
There may be zero or more blank lines, and the blank lines need not be
consecutive. If there is no blank line, then all the lines should be
shown. If the last line is blank, then nothing should be shown. So for
example the variable may contain:
============ (the '=' are not part of the variable)
abc def
hijk
xyz
============
So in this case what is wanted is:
============
hijk
xyz
============
to be shown.
I tried something like:
echo "$XX" | sed -e '/./,/^$/d'
but this didn't display anything. (Where XX is the variable.)
I also tried using a 'for' loop but again this displayed nothing:
opt=""
IFS=$'\n'
for n in $XX; do test -z "$n" && opt="" || opt="$opt $n"; done
(Echoing $opt after this shows that it contains nothing.) I'm not sure
why but even using a for loop just to show it had seen a blank line
didn't work either (using something like 'test -z "$n" && echo found').
My understanding was that by setting IFS to a newline, then the 'for'
loop should see the blank line and just set '$n' to the null string. We
should then be able to test on that.
Ideally what I am looking for is a snappy one line 'sed' or 'awk'
command to handle this :-) Unfortunately at the moment I seem to be
getting nowhere though, even with the 'for' loop.
Thanks,
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
11 years, 3 months
Preferred CPU model SandyBridge not allowed by hypervisor
by Corinna Vinschen
Hi,
Friday I switched one of my machines from an Opteron 2382 based
motherboard to a Xeon E5-2640 based one. I'm using this Fedora 17
machine to run my Windows test VMs using qemu-kvm. I changed the
Processor configuration setting in virt-manager from Opteron G3 to
SandyBridge and now, whenever I start a VM, I get the message from the
subject line:
Preferred CPU model SandyBridge not allowed by hypervisor; closest
supported model will be used
ps -ef | grep kvm shows the following CPU setting:
/usr/bin/qemu-kvm [...] \
--cpu core2duo,+lahf_lm,+rdtscp,+pdpe1gb,+avx,+osxsave,+xsave,+aes,\
+tsc-deadline,+popcnt,+x2apic,+sse4.2,+sse4.1,+dca,+pdcm,+xtpr,\
+cx16,+tm2,+est,+smx,+vmx,+ds_cpl,+dtes64,+pclmuldq,+pbe,+tm,\
+ht,+ss,+acpi,+ds \
[...]
I tried to add the following SandyBridge entry to
/etc/qemu/target-x86_64.conf (taken from
http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03765.html):
[cpudef]
name = "SandyBridge"
level = "0xd"
vendor = "GenuineIntel"
family = "6"
model = "42"
stepping = "1"
feature_edx = " sse2 sse fxsr mmx clflush pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"
feature_ecx = "avx xsave aes tsc-deadline popcnt x2apic sse4.2 sse4.1 cx16 ssse3 pclmulqdq sse3"
extfeature_edx = "i64 rdtscp nx syscall "
extfeature_ecx = "lahf_lm"
xlevel = "0x8000000A"
model_id = "Intel Xeon E312xx (Sandy Bridge)"
This doesn't quite match the host CPUs, since the model number of the
E5-26xx CPUs is 45. But, anyway, qemu-kvm -cpu ? prints:
error: feature "tsc-deadline" not available in set
error: bad option value [feature_ecx = avx xsave aes tsc-deadline popcnt x2apic sse4.2 sse4.1 cx16 ssse3 pclmulqdq sse3]
x86 Opteron_G3
x86 Opteron_G2
x86 Opteron_G1
x86 SandyBridge
x86 Nehalem
[...]
Adding this entry also appears to have no effect on the used cpu settings
when starting the VMs.
I'm using stock F17 qemu-kvm-1.0.1-2.fc17.x86_64. The VMs are working,
so that's not a pressing issue. I was just wondering, if full CPU
support is something I can change myself using the stock qemu-kvm, or
if I have to upgrade to the 1.2 virt preview release (or wait for F18)?
Corinna
11 years, 3 months
mdadm: How to access windows raids?
by Joshua C.
I have two 1tb disk that have been running in raid1 with the
intel-p67-built-in controller. Those were created in bios (uefi) and
are actually fake(software) raids. Windows sees only his own (ntfs)
raid and everything is fine. Under linux I set the partition type to
0xfd (linux auto raid) and mdadm can successfully see and access the
linux raid partion.
However mdadm cannot access the windows raid and I have each partition
three(!) times under KDE-Dolphin. So each time I click
(unintentionally) on the real hdd-partition instead of the
mdadm-partition I trigger the check of the raid, which takes about 3
hours.
How to make mdadm access the windows raid and ONLY show the raid
partitions in the kde-dolphin???
When I omit "rd.dm=0 and rd.md=0" on the command line then I see only
the raid partitions under kde-dolphin but for some reason I cannot
access them (so this is not a solution). Here is what mdadm says about
my disks (done with kernel-3.6.8.fc17.x86_64):
=============================
[root@localhost]# cat /proc/mdstat
Personalities : [raid1]
md126 : active raid1 sdb[1] sdc[0]
976759808 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sdb[1](S) sdc[0](S)
5288 blocks super external:imsm
unused devices: <none>
=============================
[root@localhost]# mdadm --examine /dev/md126
/dev/md126:
MBR Magic : aa55
Partition[0] : 1743810560 sectors at 2048 (type fd)
Partition[1] : 209711104 sectors at 1743812608 (type 07)
=============================
[root@localhost]# mdadm --examine /dev/md127
/dev/md127:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.1.00
Orig Family : 88e429ad
Family : 1e27d1ba
Generation : 0001acff
Attributes : All supported
UUID : 516f8fc8:bd5e663f:c254ea22:d30bb530
Checksum : 2438ebd3 correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1
Disk00 Serial : WD-xxxxxxxxxxxx
State : active
Id : 00000002
Usable Size : 1953519880 (931.51 GiB 1000.20 GB)
[Volume0]:
UUID : fa85ec01:25e9c177:da74f1e6:03284c35
RAID Level : 1
Members : 2
Slots : [UU]
Failed disk : none
This Slot : 0
Array Size : 1953519616 (931.51 GiB 1000.20 GB)
Per Dev Size : 1953519880 (931.51 GiB 1000.20 GB)
Sector Offset : 0
Num Stripes : 7630936
Chunk Size : 64 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Dirty State : clean
Disk01 Serial : WD-xxxxxxxxxxxx
State : active
Id : 00000003
Usable Size : 1953519880 (931.51 GiB 1000.20 GB)
=============================
[root@localhost]# cat /proc/partitions
major minor #blocks name
7 0 16 loop0
7 1 2796 loop1
7 2 900352 loop2
7 3 10485760 loop3
7 4 524288 loop4
8 0 62522712 sda
8 1 18350080 sda1
8 2 44171264 sda2
8 16 976762584 sdb
8 17 871905280 sdb1
8 18 104855552 sdb2
8 32 976762584 sdc
8 33 871905280 sdc1
8 34 104855552 sdc2
11 0 1048575 sr0
8 48 3903488 sdd
8 49 3903456 sdd1
253 0 10485760 dm-0
253 1 10485760 dm-1
9 126 976759808 md126
259 0 871905280 md126p1
259 1 104853504 md126p2
=============================
[root@localhost]# mdadm --examine /dev/md126p2
/dev/md126p2:
MBR Magic : aa55
Partition[0] : 1917848077 sectors at 6579571 (type 70)
Partition[1] : 1818575915 sectors at 1953251627 (type 43)
Partition[2] : 10 sectors at 225735265 (type 72)
Partition[3] : 51890 sectors at 2642411520 (type 00)
=============================
[root@localhost]# dmesg | grep md
[ 5.966318] md: bind<sdc>
[ 6.168403] md: bind<sdb>
[ 6.171261] md: bind<sdc>
[ 6.171463] md: bind<sdb>
[ 6.213554] md: raid1 personality registered for level 1
[ 6.215861] md/raid1:md126: active with 2 out of 2 mirrors
[ 6.216006] md126: detected capacity change from 0 to 1000202043392
[ 6.216775] md126: p1 p2
[ 6.216955] md126: p2 size 209711104 extends beyond EOD, truncated
[ 6.226735] md: md126 switched to read-write mode.
[ 6.436537] md: export_rdev(sdc)
[ 6.436733] md: export_rdev(sdb)
[ 227.889293] EXT4-fs (md126p1): warning: maximal mount count
reached, running e2fsck is recommended
[ 227.929448] EXT4-fs (md126p1): mounted filesystem with ordered data
mode. Opts: (null)
[ 227.929454] SELinux: initialized (dev md126p1, type ext4), uses xattr
=============================
[root@localhost]# mdadm --detail --scan
ARRAY /dev/md/imsm0 metadata=imsm UUID=516f8fc8:bd5e663f:c254ea22:d30bb530
ARRAY /dev/md/Volume0_0 container=/dev/md/imsm0 member=0
UUID=fa85ec01:25e9c177:da74f1e6:03284c35
=============================
--joshua
11 years, 3 months
fedora books
by Brian West
Hello everyone I'd like to hear any suggestions you may have when it
comes to a good book to learn the features of fedora. while there are
countless books that teach you how to use linux in the general way.
each distribution has its own unique set of tools and features. being
that fedora has been known since the beginning as a distribution that
stays on the cutting edge giving its users the latest software what book
would you suggest to ensure i can stay educated on fedora?
11 years, 3 months
Re: 3.7 kernels and kswapd
by JD
On Tue, Nov 27, 2012 at 1:03 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
> Upstream is pretty sure they know the causes of the kswapd issues. Two of
> the three patches should be in the latest rawhide kernel. So you already
> might see better results with that kernel. I would expect the third patch
> to make it in soon.
>
Thank for the heads up Bruno.
I am still booted in the 3.7.0-git kernel because
it is keeping the disks from sleeping or it is properly waking
the disks up before committing reads and writes.
However, because of the current kswapd, building a kernel is taking an
inordinately long time, so it will be likely 2 or 3 days on my old unicore
Athlon64 3700+ before I can boot the new 3.7X
11 years, 3 months
Printing multiple files results in hold
by Matthew Saltzman
Fedora 17, fully up to date. Shared printer from an F17 server. The
printer itself is a network printer using IPP. Tried with two different
printers, with the same result.
Using lp or lpr to print several plain text files with a single command
seems to result in the print job being held in the queue. Releasing the
job with system-config-printer results in the job vanishing into thin
air. Printing the files one at a time works as expected.
Has anyone else seen this behavior?
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
11 years, 4 months
install dvd image via usb (not live cd/dvd)
by Brian West
Hello everyone,
I know that you can install fedora via a usb flash drive using any of
the live images but i perfer to use the install dvd due to more control
over whats installed etc how can i copy the install dvd iso to a flash
drive so i can have a fedora install flash drive so i can avoid burning
a dvd with each new release id rather just update the flash drive with
the install dvd image. ive been able to do this using a live dvd image
but not the install dvd image any thoughts?
Thanks
Brian
11 years, 4 months
server-optimized Fedora, web-based desktop.
by 金本淳志
I have two ideas.
1st, server-optimized Fedora.
It's stable and small pack of Fedora that support only server-side.
2nd, web-desktop Fedora.
It's desktop like Google Chrome OS, but all apps by Web transparent.
11 years, 4 months