Ask Your Question

firebird's profile - activity

2017-11-21 03:27:09 -0500 received badge  Famous Question (source)
2014-09-14 12:29:09 -0500 received badge  Nice Question (source)
2014-08-11 10:08:50 -0500 received badge  Notable Question (source)
2013-11-13 02:51:44 -0500 received badge  Famous Question (source)
2013-08-20 05:48:04 -0500 received badge  Taxonomist
2013-02-22 14:27:26 -0500 received badge  Student (source)
2012-10-02 11:06:25 -0500 received badge  Popular Question (source)
2012-09-06 06:41:07 -0500 answered a question Update to Fedora 17 breaks Xmodmap settings


thank you for this advise. This solution seems to work but for touchpads only and will not resolve my issues with the mousewheel not beeing reversed consistently in all applications.

2012-08-29 11:18:10 -0500 received badge  Notable Question (source)
2012-07-13 14:28:22 -0500 received badge  Famous Question (source)
2012-07-10 09:43:37 -0500 received badge  Popular Question (source)
2012-05-25 02:17:12 -0500 asked a question Update to Fedora 17 breaks Xmodmap settings

Hi there,

up to Fedora 16 I used my .Xmodmap to implement natural scrolling (reversed mouse wheel). Since F17 this is still working, but not for all apps. Evolution Mail and GEdit are examples of apps that do not obey Xmodmap any more. I opened already an bug at Bugzilla to learn that F17 introduced Xinput2 which should be the culprit. Some Apps use this new method to access input devices directly.

Question: how can I tune and configure xinput2 so that evolution and other "new" apps will obey those settings. I tried:

xinput set-button-map <id> 1 2 3 5 4

but this has the same effect as my ~/.Xmodmap and works only for the same apps as Xmodmap does. E.g. Evolution seems unaffected by this (or do I have to reboot after applying xinput settings for those new apps)?

2012-05-01 05:00:12 -0500 received badge  Notable Question (source)
2012-03-29 14:42:40 -0500 received badge  Popular Question (source)
2012-02-01 02:42:07 -0500 commented answer udisks default mount options

Thank you very much. Unfortunately applying some tricks by writing udev-rules to call /bin/mount manually is not what I was looking for. It seems that there is no up-to-date documentation of udev and udisks providing the needed information on how to administer udisks.

2012-01-31 08:06:38 -0500 commented answer virt-top csv output format changed

Thank you very much for your reply: LANG=C did the trick.

2012-01-31 08:05:58 -0500 marked best answer virt-top csv output format changed

A few related issues/answers:

  1. We didn't change the format from period to comma. You could try setting LANG=C since it may be that your locale causes commas to be displayed for decimal points. (To see what I mean by these locales, try: LANG=es_ES virt-top --script --csv /dev/stdout)
  2. Don't use tr "," "\n" to parse CSV. It is not a robust way to parse any CSV file. Use a proper CSV parser such as spreadsheet/database, or Perl/Python/Ruby library, or /usr/bin/csvtool.
  3. We could add a flag to change the separator, but given (1) I don't think that's necessary to solve your problem.
2012-01-31 08:05:58 -0500 received badge  Scholar (source)
2012-01-31 08:01:09 -0500 asked a question udisks default mount options

Hi there,

all FAT-formatted usb-pen-drives are mounted with the showexec mount-option. How can I change that default behavior? Is this udisks-related or udev or hal or ....

2011-12-02 05:08:11 -0500 asked a question virt-top csv output format changed

I use virt-top with CSV-switch to output all stats to a file which is parsed to fill SNMP-tree so the vm-stats can be queried using SNMP-walk/get remotely by monitoring systems (e.g. nagios, zabbix)

This worked using libvirt verions 0.7.X but with the most recent version (fedora 16, libvirt 0.9.X) the CSV-format has changed: floating point was represented as ',N.NNNN,' in the CSV with version 0.7X and now its represented as ',"N,NNNN",'. So the point has been changed to a comma and the complete number is now double-qouted because the comma now has a double function (floating-point and CSV-seperator). This makes it very hard to parse. Before I just did:

tail -n 1 virt-top.log | tr "," "\n" to split all values into seperate lines so I could read in this output directly into SNMP (via extend) - very easy and robust.

How can I archive the same now? Why has beend the format changed? How to contact the developers to ask for a new switch so at least the default seperator can be changed to something unique (e.g. ";").

Help much appreciated Thanks