Default git colour setup is not so good. On black terminal background it looks dark:
However, with small change in ~/.git/config file:
meta = yellow bold
frag = magenta bold
old = red bold
new = green bold
you would get much better diff display on your terminal:
When you see the following kind of errors during cross compilation (linking phase):
ld: warning: libfontconfig.so.1, needed by …/libQtGui.so, not found (try using -rpath or -rpath-link)
ld: warning: libaudio.so.2, needed by …/libQtGui.so, not found (try using -rpath or -rpath-link)
There could be two reasons:
- the list of required binaries is not complete and linker cannot complete the linking automatically
- your $SYSROOT/usr/lib is not passed to linker by -rpath-link as mentioned in error message
During normal native build your libraries are stored in standard locations (/usr/lib) and locating libraries is easier. Cross compilation needs more attention in this ares as SYSROOT is not standard.
Then search for LDFLAGS setup in your build scripts:
And change to the following:
The clumsy syntax -Wl,<options-with-comma-as-space> tells your compiler (that is used for linking purposes) to pass the options (with commas replaced by spaces of course) to linker (ld).
Posted in en
If you encounter the following error during VPN connection:
pptp: nm-pptp-service-12543 warn[decaps_gre:pptp_gre.c:331]: short read (-1): Message too long
there's an easy fix. You have to lower your MTU (automatically obtained value was invalid).
First, you have to locate your VPN gateway address in syslog:
NetworkManager: <info> VPN Gateway: X.X.X.X
Then, you have to check minimum MTU toward this address:
$ traceroute –mtu X.X.X.X
traceroute to X.X.X.X (X.X.X.X), 30 hops max, 65000 byte packets
1 192.168.43.1 (192.168.43.1) 4.309 ms F=1380 4.042 ms 2.535 ms
2 * *^C
Then you have to change MTU it in your primary connection settings (network manager on Ubuntu below):
That's all!. No more spurious disconnects!
Posted in en
The best idea PR guys from PayU might have:
Dear Sir or Madam,
We would like to apologize for the INCORRECT INFORMATION in our last communication.
During the break which will take place on 27 November 2014 from 05:00 am to 05:30 am you could not be able to log in into the system but all transactions WILL BE SETTLED. A message informing about unavailability of the service may be displayed during login attempt.
We are very sorry for the inconvenience and misrepresentation.
The funny thing is that I haven't got any e-mail on the technical break in the first place.