RT @sonjdol: I finally stopped using @itunes and switsched to @banshee. #freesoftware is better than #apple

RT @sonjdol: I finally stopped using @itunes and switsched to @banshee. #freesoftware is better than #apple

Mozilla delays turning on third-party cookie killer in Firefox http://t.co/EaT3KYR6WO #freesoftware

RT @sonjdol: I finally stopped using @itunes and switsched to @banshee. #freesoftware is better than #apple

RT @sonjdol: I finally stopped using @itunes and switsched to @banshee. #freesoftware is better than #apple

The beat goes on in the Apple v. Motorola appeal of Judge Richard Posner's ruling dismissing both parties' claims with prejudice, saying neither was entitled to damages or an injunction. Both are appealing, but for different reasons. Motorola has now filed its redacted reply brief [PDF] in response to Apple's response and reply brief [PDF]. And as soon as Judge James Robart issued his Microsoft-friendly ruling in Microsoft v. Motorola in the Seattle litigation, Apple sent a letter to this appeals court, bringing it to the court's attention, because it supports Apple's position and calls Motorola's patents a trivial contribution to the standard.

Motorola defends the value of its patents and then tells the Federal Circuit that RAND patent holders have to be able to seek injunctions against "intransigent" licensees like Apple. Otherwise, they'll take advantage, delaying by litigation any reckoning for years while benefiting from the technology without paying for it.

What exactly should happen to a company that refuses to pay and won't accept an offered rate or a court-set rate? The RAND patent holder *still* can't do a thing? No injunction? Nothing? Apple began its infringement, Motorola points out, in 2007. It's now 2013, and it still hasn't paid a dime. "Motorola should have the opportunity to seek an injunction to stop Apple's six years of ill-gotten gains from stretching into a decade or more," Motorola says.

Vreau ca toate instituțiile de stat să ruleze programe libere #gnu #linux #romania #freesoftware #programelibere #linuxromania

Linux Mint 15 brings prettier desktop, new software and driver managers http://t.co/TfBWbxAxuH #freesoftware

RT @sonjdol: I finally stopped using @itunes and switsched to @banshee. #freesoftware is better than #apple

LTTng (Linux Trace Toolkit - next generation) is a highly efficient system tracer that allows tracing of the kernel and userspace. It also provides tools to view and analyse the gathered trace data.  So let's see how to install and use LTTng kernel tracing in Ubuntu. First, one has to install the LTTng userspace tools:
sudo apt-get update sudo apt-get install lttng-tools LTTng was already recently added into the Ubuntu 13.10 Saucy kernel, however, with earlier releases one needs to install the LTTng kernel driver using lttng-modules-dkms as follows:

sudo apt-get install lttng-modules-dkms It is a good idea to sanity check to see if the tools and driver are installed correctly, so first check to see the available kernel events on your machine:
sudo lttng list -k And you should get a list similar to the following:
Kernel events: ------------- mm_vmscan_kswapd_sleep (loglevel: TRACE_EMERG (0)) (type: tracepoint) mm_vmscan_kswapd_wake (loglevel: TRACE_EMERG (0)) (type: tracepoint) mm_vmscan_wakeup_kswapd (loglevel: TRACE_EMERG (0)) (type: tracepoint) mm_vmscan_direct_reclaim_begin (loglevel: TRACE_EMERG (0)) (type: tracepoint) mm_vmscan_memcg_reclaim_begin (loglevel: TRACE_EMERG (0)) (type: tracepoint) .. Next, we need to create a tracing session:
sudo lttng create examplesession ..and enable events to be traced using:
sudo lttng enable-event sched_process_exec -k One can also specify multiple events as a comma separated list. Next, start the tracing using:
sudo lttng start and to stop and complete the tracing use:
sudo lttng stop sudo lttng destroy and the trace data will be saved in the directory ~/lttng-traces/examplesession-[date]-[time]/.  One can examine the trace data using the babeltrace tool, for example:
sudo babeltrace ~/lttng-traces/examplesession-20130517-125533 And you should get a list similar to the following:
[12:56:04.490960303] (+?.?????????) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/bin/firefox", tid = 4892, old_tid = 4892 } [12:56:04.493116594] (+0.002156291) x220i sched_process_exec: { cpu_id = 0 }, { filename = "/usr/bin/which", tid = 4895, old_tid = 4895 } [12:56:04.496291224] (+0.003174630) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/lib/firefox/firefox", tid = 4892, old_tid = 4892 } [12:56:05.472770438] (+0.976479214) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/lib/libunity-webapps/unity-webapps-service", tid = 4910, old_tid = 4910 } [12:56:05.478117340] (+0.005346902) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/bin/ubuntu-webapps-update-index", tid = 4912, old_tid = 4912 } [12:56:10.834043409] (+5.355926069) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/usr/bin/top", tid = 4937, old_tid = 4937 } [12:56:13.668306764] (+2.834263355) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/bin/ps", tid = 4938, old_tid = 4938 } [12:56:16.047191671] (+2.378884907) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/usr/bin/sudo", tid = 4939, old_tid = 4939 } [12:56:16.059363974] (+0.012172303) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/usr/bin/lttng", tid = 4940, old_tid = 4940 } The LTTng wiki contains many useful worked examples and is well worth exploring.

As it stands, LTTng is relatively light weight.   Research by Romik Guha Anjoy and Soumya Kanti Chakraborty shows that LTTng describes how the CPU overhead is ~1.6% on a Intel® CoreTM 2 Quad with four 64 bit Q9550 cores.  With measurements I've made with oprofile on a Nexus 4 with 1.5 GHz quad-core Snapdragon S4 Pro processor shows a CPU overhead of < 1% for kernel tracing.  In flight recorder mode, one can generate a lot of trace data. For example, with all tracing enabled running multiple stress tests I was able to generate ~850K second of trace data, so this will obviously impact disk I/O.

@macgirvin: More exactly: To me freedom in #freesoftware is about choice (freedom for me) and responsibility (freedom for others).

@macgirvin: To me freedom in #freesoftware is about choice (choosing my own path) and responsibility (being a good neighbor).

Microsoft improves Skype on the Mac http://t.co/Ml2sflCQXD #Article #Apple #FreeSoftware #MessagingandCollaboration #Microsoft

I finally stopped using @itunes and switsched to @banshee. #freesoftware is better than #apple

What does every development team want? New contributors!

I'd like to suggest a simple process that can turn visitors to your website, list or IRC channel into a successful part of the development team. When people actually contribute, they quickly feel like a valuable part of the group. New people bring fresh energy, and new ideas.

At your next sprint or meeting, start dreaming. Is your user documentation well-written and up-to-date? Do you need promotion, or video guides? How about art or diagrams for your website? Speaking of your website, when was the last time all the links were tested, and it was checked for spelling and grammar? Create a nice, friendly list of tasks for your newcomers.

Could your codebase use some grooming, for common misspellings, for instance? (EBN is a great source for these). When you run across a bit of code which needs pruning or refactoring, or normalizing signal-slot stuff, the easy thing is to fix it while it's in front of your eyes. Instead, consider which of these small tasks can be filed as a "Junior Job", created for the purpose of getting those knowledgeable people to move from faithful user, to part of the team.

The Bugsquad and Quality Control teams can likely suggest more ideas, too.

KDE Junior Jobs can be easily found: http://kde.org/jj. Teams can create their own shortcut links too, such as Amarok has done, listed in the #amarok IRC channel topic: http://tinyurl.com/amarokjjs. Other tasks can be blogged about, posted on a trello, on the Community wiki; whatever your team likes to use. For more ideas, see http://community.kde.org/Getinvolved.

The Kubuntu team has a list of tasks in Trello, which works well.

So, when you feel like not fixing a little issue, don't feel lazy. Feel responsible! File a bug, make it a JJ, and call attention to those issues when new folks show up and ask, how can I help?


PS: Thanks to the #kde-www team for suggesting this blog. Einar77, neverdingo, mamarok; you are wonderful.

PPS: How LibreOffice does it: https://wiki.documentfoundation.org/Development/Easy_Hacks

Das Recht zu lesen - #EbenMoglen: http://t.co/wfRJ9VNGnj #FreeSoftware #Internet #Wissensaustausch #Verbrechen #Zugang #dieInternetze

RT @WealthWitness: One of the best tools for Online Marketing offered Free until May 20th! Limited Amount Available. #makemoney #freesoftwa…

IObit releases Malware Fighter 2: IObit has announced... http://t.co/6Ir1sxkLgZ #Article #FreeSoftware #Security |http://t.co/2rrdwAnwc8

Keiser Report: Happy Hacking! (ft. Richard Stallman) http://t.co/fh1vVyfBzP #Facebook #freesoftware #FSF

IObit releases Malware Fighter 2 http://t.co/rOuD8ODXxT #Article #FreeSoftware #Security