Forkstat uses the kernel proc connector interface to detect process activity. Proc connector allows forkstat to receive notifications of process events such as fork, exec, exit, core dump and changing the process name in the comm field over a socket connection.
By default, forkstat will just log fork, exec and exit events, but the -e option allows one to specify one or more of the fork, exec, exit, core dump or comm events. When a fork event occurs, forkstat will log the PID and process name of the parent and child, allowing one to easily identify where processes are originating. Where possible, forkstat attempts to track the life time of a process and will log the duration of a processes when it exits (note: this is not an estimate of the CPU used).
The -S option to forkstat will dump out a statistical summary of activity. This is useful to identify the frequency of processes activity and hence identifying the top offenders.
Forkstat is now available in Ubuntu 14.04 Trusty Tahr LTS. To install forkstat use:
sudo apt-get install forkstat
For more information on the tool and examples of the forkstat output, visit the forkstat quick start page.
On the 25th of January, the Ubuntu Peru LoCo Team hosted the first Ubuntu App Dev School. We contacted the National Engineering University, and they offered their help in order to host the event at their premises.
After some planning, we showed up that morning. I was a bit rushed with everything as the connection on my PC was not good and I had to run an Ubuntu User Days session just before the event started, so I ended up running it from my phone. At 10:00 am, around 45 to 50 people joined us in the newly-opened auditorium, where we presented Ubuntu Touch to the community and explained how it all worked – from the foundations to app development. This was the first time the community had showed a device with Ubuntu Touch, and as I got my own Nexus 4 I decided to give it a try, and show it to the rest of the community.
Everything starting by showing the phone with the OS installed, and then we proceeded to explain how the system worked, the concepts inside the system, how edges work, and many more things that are featured on the phone. After this, we had a break, where we distributed some swag and DVDs/CDs we got from Canonical, as we are a verified team. We invited some people from the press, but as they didn’t show up we ended up having more time for the next part of the event. We continued by explaining how foundations and applications work, and we gave some tips on how to install Ubuntu on a machine or use a VM, install Ubuntu Touch on a phone or tablet, and terminal tips and tricks. We also explained the process of creating and publishing applications to the Ubuntu Click Store.
We encouraged people to write their own applications, whether they are in QML or HTML5. I had a couple spare YubiKeys from when I went to UDS-R (literally, a couple), so I decided to raffle them to the assistants. We got a bunch of numbered tickets and started giving them out to assistants, and then we raffled them as we kept the other side of the ticket (works great if you decide to do a raffle in your LoCo Team!). We hoped this was an incentive in order to increase security in their accounts and discovering what else can be done with Ubuntu.
Aaaand, that was basically it. Everyone ended up super happy, and knowing what the future of convergence is.
If you want to organize an App Dev School in your LoCo Team, it’s quite easy! Just make sure to read this page to have a general idea. Daniel Holbach and David Planella will be hosting two sessions at Ubuntu on Air! to answer all your questions about App Dev Schools – both organizational and technical. The first one is on the 26th of March at 9:00 UTC, and the second one is on the 27th of March at 18:00 UTC. Make sure you’re there if you want to ask anything about App Dev Schools. Also, if you want to use the slides I used for the presentation, they are on my people.ubuntu.com page, and fully translated to Spanish. The original slides can be found at Daniel’s people.canonical.com page, including also a VM with Ubuntu and the Ubuntu SDK installed. Now, I leave you with some photos from the event!
We’re not starting from scratch though, we’re building on top of the incredible work done in the Trojitá project. Trojitá provides a fast, light email client built with Qt, which made it ideal for using with Ubuntu. And yesterday, the first of that work was accepted into upstream, you can now build an Ubuntu Components front end to Trojitá.
None of this would have been possible without the help up Trojitá’s upstream developer Jan Kundrát, who patiently helped me learn the codebase, and also the basics of CMake and Git so that I could make this first contribution. It also wouldn’t have been possible without the existing work by Ken VanDine and Joseph Mills, who both worked on the build configuration and some initial QML code that I used. Thanks also to Dan Chapman for working together with me to get this contribution into shape and accepted upstream.
This is just the start, now comes the hard work of actually building the new UI with the Ubuntu UI Toolkit. Andrea Del Sarto has provided some fantastic UI mockups already which we can use as a start, but there’s still a need for a more detailed visual and UX design. If you want to be part of that work, I’ve documented how to get the code and how to contribute on the EmailClient wiki. You can also join the next IRC meeting at 1400 UTC today in #ubuntu-touch-meeting on Freenode.
Hummus is dead simple. Traditionally it's a paste of chickpeas, garlic, lemon and tahini, but I like to add a few other spices to give it more flavour.
- 1 can of your finest chickpeas, drained
- 3 cloves garlic, whole
- 1 tablespoon tahini (or 1 tablespoon each sesame oil & roasted sesame seeds)
- 1 tablespoon ground cumin
- 1/2 teaspoon ground paprika
- 1/2 teaspoon freshly ground black pepper
- 1/4 teaspoon ground cayenne pepper
- juice of one lemon
- salt to taste
- Just chuck all of the ingredients in a food processor and blend into a paste.
- Transfer into a bowl, garnish the top if you like, then cover and refrigerate –it gets better even after a short period in the fridge.
Guacamole is one of those things people either love or hate, I love it, and it's very easy to do.
Having said that, a classic mistake people make is blending all the ingredients –which one should never do. Instead a guacamole should be chunky, which is simply achieved by mashing everything.
- 3-4 ripe avocados –depending their size
- 3 cloves garlic, minced
- 1-3 jalapeno peppers, minced –depending on your tolerances
- 1 tablespoon olive oil
- 1 tablespoon fresh cilantro, finely chopped minced
- juice of one lime
- 1/2 teaspoon salt
Breaking Down the Avocados
- Halve the avocados by slicing to the pit and then running your knife around it slicing the avocado.
- Whack the edge of the knife into the pit, twist & pull, removing the pit. Discard.
- Scoop the flesh out with a spoon into a bowl.
- Repeat for all avocados.
- With your avocado flesh in a bowl, add the lime juice, salt, olive oil, chopped cilantro and minced garlic.
- Using a potato masher, mash the ingredients into the avocado until it's a chunky paste (see above).
- Stir in the minced jalapeno pepper.
- Taste and adjust the seasoning, if need be.
- Eat now or cover and refrigerate until use.
The last year has been a rough year. I started working for Deutsche Telekom (with a bunch of other FLOSS developers) on OpenStack. What started off as developing new features upstream ended up being more or less devops stuff (mainly Puppet and orchestration) which is not really my style.
During that time I was working on GNOME Music, I enjoyed developing it a lot, the students and the team are just amazing but I was growing unhappy with the external micromanagement that I experienced which personally stressed me and made me feel unappreciated for what I think I can bring to the table. What started off as a hobby became a burden, so at GUADEC I decided to spend time away from GNOME. Strangely enough I started feeling better, I took things a step further and switched to Mac and noticed what a long road we have for the Linux desktop. I became more convinced that the focus of delivering an experience for the desktop or mobile market is misplaced and we missed both trains. The only way for GNOME to continue being relevant is to either start focusing on wearable experience or focus on marketing the technology first then the experience. Get GNOME tech on wearables.
Anyhow being unhappy can take a toll on the mental and physical health, I became more depressed and negative person and my health was declining. I went through this a couple of years ago when my father passed away and found an escape contributing to GNOME and FLOSS. So with that some decision had to be taken.
Somehow I can’t see myself actively contributing to GNOME anymore and maybe its for the best. I’ll be around and will help out when I can if asked directly. But I won’t be running GNOME actively.
I am also taking time off contributing to Mozilla. However I do see myself coming back soon since I am missing it already. I really enjoy the compatibility team (where we use some GNOME technologies including GI) and the community building team.
I will continue maintaining Zeitgeist but there will be no active feature development. After almost 6 years we all moved on and Zeitgeist is feature complete.
I quit my job. I am on a nice vacation for a bit and will be starting my new job sooner than expected.
Feeling better already :D
Okay, this “lesson(s) learned” blog post might be a weird one but what happened to me is asking me to write this.
A few days ago, out of the blue, guess who offers me a job? Google! A recruiter from Google e-mails me offering me a job that requires coding and the problem is that I have no skill. For some reason, I Tweet the news and the reply from pleia2.
— Lyz Krumbach Joseph (@pleia2) March 19, 2014
The lesson that I learned from this is have your wiki userpage and launchpad page up to date and even include something of your skills. This is what I wrote:
NOTE: I’m only a Ubuntu Community member, not a developer/coder. I use Ubuntu Linux to get away from Windows and Mac. I’m a biologist that will most likely do research not developing programs.
I hope this helps for the ones who don’t develop or code.
While messing around with juju 1.17.x I managed to stumble across a setup that allows me to deploy both LXC and KVM containers in a single environment.Pre-reqs
- Juju v1.17 or higher
- Ubuntu Saucy or higher (only one I tested this on)
Very simple configuration for thisdefault: local environments: local: type: local network-bridge: virbr0 Bootstrap and Deploy $ juju bootstrap $ juju deploy mysql --to kvm:0 $ juju deploy wordpress
What this does is deploy mysql onto a KVM instance within Machine 0 and deploys wordpress onto an LXC instance which is Machine 1 by default. The juju status output should look similar to this:environment: local machines: "0": agent-state: started agent-version: 184.108.40.206 dns-name: localhost instance-id: localhost series: saucy containers: 0/kvm/0: agent-state: started agent-version: 220.127.116.11 dns-name: 192.168.122.233 instance-id: juju-machine-0-kvm-0 series: precise hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M "1": agent-state: started agent-version: 18.104.22.168 dns-name: 192.168.122.204 instance-id: adam-local-machine-1 series: precise hardware: arch=amd64 services: mysql: charm: cs:precise/mysql-38 exposed: false relations: cluster: - mysql db: - wordpress units: mysql/0: agent-state: installed agent-version: 22.214.171.124 machine: 0/kvm/0 public-address: 192.168.122.233 wordpress: charm: cs:precise/wordpress-21 exposed: true relations: db: - mysql loadbalancer: - wordpress units: wordpress/0: agent-state: started agent-version: 126.96.36.199 machine: "1" open-ports: - 80/tcp public-address: 192.168.122.204
You can also verify the instances via virsh and lxc-ls –fancy$ virsh list Id Name State ---------------------------------------------------- 55 juju-machine-0-kvm-0 running $ sudo lxc-ls --fancy NAME STATE IPV4 IPV6 AUTOSTART --------------------------------------------------------------- adam-local-machine-1 RUNNING 192.168.122.204 - YES
Since we set our network-bridge to virbr0 those instances happily talk to each other.Additional things you can do
Deploying all kvm instances into Machine 0 is as simple as:$ juju deploy mongodb --to kvm:0 $ juju deploy rails --to kvm:0 $ juju deploy wikipedia --to kvm:0 Disclaimer
- Is this a supported configuration? Nope.
- Is it crazy to do something like this? Maybe.
- Should I do this at my own risk? Hell yes.
xTuple, the makers of PostBooks, the compelling PostgreSQL-based accounting and CRM suite have started a discussion about how to move to a more recognised license.
It is really good to see a company dealing with these issues in an open manner and engaging the community for feedback. For those who are familiar with these issues or have practical experience of how businesses have been successful with GPL and other free licenses, please share your comments on John's blog.
Some of the reasons why companies need to think about licensing issues like this:
- They not only want to be open source, they also want to engage the community through Github, hoping to make it easier for developer collaboration. A familiar license makes this easier.
- They want to extend the product more rapidly by using other open source libraries and need to maintain compatibility of licenses. Using a less well known license can make this more awkward. In the case of xTuple, they are now using a number of libraries and frameworks to support their powerful new web front end.
- Having a recognised and respected license like GPL can also be a factor in other initiatives like crowd funding.
Earlier today, lfetool converted to using plugins (easier for contributors to play!), and hopefully later tonight YAWS + Bootstrap support will land. Regardless, there's tons more work to do, and what's more motivating for new work than a T-shirt? As you can see, we had no choice.
So let's get some. T-shirts, that is.
The lfetool logo is on the front, and Robert Virding's example Fibonacci lfescript code is on the back (with the lfetool command that generates the script at the top). Here's the front of the T-shirt:
And here's the back:
We've got a CustomInk sign-up sheet that you can add your name to if you want a shirt. I'll coordinate with folks individually, once we meet our minimum number (we're going to need to use paypal with payment upfront). Due to the colors of the source code on the back, the minimum order is 15. This will put the shirts at $22 a piece + $5 to send it to you. I've just ordered 2; 13 more go!
So it’s this time of the year again! As the end of the current cycle approaches, the Ubuntu Classroom Team is starting the planning of the next Ubuntu Open Week, for the Trusty cycle.
The Ubuntu Open Week is a series of classroom sessions which will guide many people in their way for contributing to the Ubuntu community. For this, we need actual Ubuntu contributors from different teams to help us run one-hour sessions, explaning what you do on the team you currently work on, as well as how to get started working on the team. We have three days with 5 one-hour slots each, making it 15 slots in total. The event is scheduled to run from 15 to 20 UTC, from the 22nd to the 24th April.
If you are interested in running a session, please send an email to myself (jose at ubuntu.com), ubuntu-classroom at lists.ubuntu.com, or let us know on IRC at the #ubuntu-classroom-backstage channel on irc.freenode.net. Logs from out past Open Week can be found here. Please, make sure to give the link to this announcement to anyone who may be interested in running a session. Thank you for your interest!
Qt 5.2.1 landed in Ubuntu 14.04 LTS last Friday, hooray! Making it into a drop-in replacement for Qt 5.0.2 was not trivial. Because of the qreal change, it was decided to rebuild everything against the new Qt, so it was an all at once approach involving roughly 130 source packages while the parts were moving constantly. The landing last week meant pushing to archives around three thousand binary packages - counting all six architectures - with the total size of closer to 10 gigabytes.
The new Qt brings performance and features to base future work on, and is a solid base for the future of Ubuntu. You may be interested in the release notes for Qt 5.2.0 and 5.2.1. The Ubuntu SDK got updated to Qt Creator 3.0.1 + new Ubuntu plugin at the same time, although updates for the older Ubuntu releases is a work in progress by the SDK Team.
How We Got HereThroughout the last few months before the last joint push, I filed tens of tagged bugs. For most of that time I was interested only in build and unit test results, since even tracking those was quite a task. I offered simple fixes here and there myself, if I found out a fix.
I created automated Launchpad recipe builds for over 80 packages that rely on Qt 5 in Ubuntu. Meanwhile I also kept on updating the Qt packaging for its 20+ source packages and tried to stay on top of Debian's and upstream's changes.
Parallel to this work, some like the Unity 8 and UI Toolkit developers started experimenting with my Qt 5.2 PPA. It turned out the rewritten QML engine in Qt 5.2 - V4 - was not entirely stable when 5.2.0 was released, so they worked together with upstream on fixes. It was only after 5.2.1 release that it could be said that V4 worked well enough for Unity 8. Known issues like these slowed down the start of full-blown testing.
Then everything built, unit tests passed, most integration tests passed and things seemed mostly to work. We had automated autopilot integration testing runs. The apps team tested through all of the app store to find out whether some needed fixes - most were fine without changes. On top of the found autopilot test failures and other app issues, manual testing found a few more bugs
Some critical pieces of software
like Sudoku needed small fixing
Finally last Thursday it was decided to push Qt in, with a belief that the remaining issues had fixes in branches or not blockers. It turned out the real deployment of Qt revealed a couple of more problems, and some new issues were raised to be blockers, and not all of the believed fixes were really fixing the bugs. So it was not a complete success. Considering the complexity of the landing, it was an adequate accomplishment however.
Specific IssuesThroughout this exercise I bumped into more obstacles that I can remember, but those included:
- Not all of the packages had seen updates for months or for example since last summer, and since I needed to rebuild everything I found out various problems that were not related to Qt 5.2
- Unrelated changes during 14.04 development broke packages - like one wouldn't immediately think a gtkdoc update would break a package using Qt
- Syncing packaging with Debian is GOOD, and the fixes from Debian were likewise excellent and needed, but some changes there had effects on our wide-spread Qt 5 usage, like the mkspecs directory move
- xvfb used to run unit tests needed parameters updated in most packages because of OpenGL changes in Qt
- arm64 and ppc64el were late to be added to the landing PPA. Fixing those archs up was quite a last minute effort and needed to continue after landing by the porters. On the plus side, with Qt 5.2's V4 working on those archs unlike Qt 5.0's V8 based Qt Declarative, a majority of Unity 8 dependencies are now already available for 64-bit ARM and PowerPC!
- While Qt was being prepared the 100 other packages kept on changing, and I needed to keep on top of all of it, especially during the final landing phase that lasted for two weeks. During it, there was no total control of "locking" packages into Qt 5.2 transition, so for the 20+ manual uploads I simply needed to keep track of whether something changed in the distribution and accommodate.
Qt 5.3?We are near to having a promoted Ubuntu image for the mobile users using Qt 5.2, if no new issues pop up. Ubuntu 14.04 LTS will be released in a month to the joy of desktop and mobile users alike.
It was discussed during the vUDS that Qt 5.3.x would be likely Qt version for the next cycle, to be on the more conservative side this time. It's not entirely wrong to say we should have migrated to Qt 5.1 in the beginning of this cycle and only consider 5.2. With 5.0 in use with known issues, we almost had to switch to 5.2.
Kubuntu will join the Qt 5 users next cycle, so it's no longer only Ubuntu deciding the version of Qt. Hopefully there can be a joint agreement, but in the worst case Ubuntu will need a separate Qt version packaged.
I love when things are simple and I love when things are simple on the web development side of things.Buttons Me on Twitter
To me a button is a glorified link (well, a glorified <div> within an <a>) and a nice simple button is a style class or two away. Here's a little JSFiddling to showcase mine.
Simple no? Althought the Twitter button above is a bit more complex – it's embedded with an SVG icon, but I talk about those in another post.
All the border:none; and outline:none; in the .button classes are there to override any user-agent stylesheets that like to theme buttons and make yours less pretty. :)
Here are the high-level bits that should make users' lives better:
- New yaws project type, provided for building basic web sites; includes the exemplar project as a dependency for generating HTML with S-expressions.
- Every project now gets TravisCI support by default.
- Unit tests, integration tests, and systems tests now each have their own dir.
- Tests now get run in parallel for faster run times.
- Added support for running on Linux and *BSD systems.
- Added unit tests for lfetool itself (shUnit) (for checking skeleton-generation and tool options).
- lfetool has a new logo :-)
- Support for an e2 service skeleton project.
- Support for a YAWS-RESTful service skeleton project.
- Support for YAWS embedded in a skeleton OTP application.
- Support for YAWS + Exemplar + Bootstrap projects
- Support for slide decks with Exemplare + Reveal.js
It annoys me to no end that I can’t run my own Linux kernel on an Android device. It’s very annoying that the android patches haven’t been upstreamed, and it’s even more annoying that I can’t run a host OS that I build lovingly and work on during the nights.
I hate that I can’t use my tablet as a porter box with a USB OTG Hard disk.
Alas. One day. One day I’ll have a proper armhf device that I can run Debian on.
But that day is not today.
Ubuntu GNOME Team is pleased to officially announce that Ubuntu GNOME 14.04 (Trusty Tahr) is going to be our first Long Term Support (LTS) Release. YES! You did read that correctly
[AGREED] Ubuntu GNOME is a 3 year LTS
Please see the log from the Technical Board Meeting on 17th of March, 2014.
What happened is, we have applied and sent this proposal. Ubuntu Technical Board asked Ubuntu GNOME Team to show more commitment and extend the support period for a very valid reason:
“I am very concerned about this proposed support timeline. 2 years and 3
months means that the support period would end the same month that 16.04.1 is likely to be released. Given that our policy has been to not recommend (or advertise in the UI) LTS upgrades until the first point release, this effectively gives users zero margin between the dropping of security support for Ubuntu-GNOME 14.04, and the first upgrades to Ubuntu-GNOME 16.04.
I would not be comfortable endorsing an LTS status for a release that is not going to provide a reasonable overlap between the LTS support periods. I think we should regard 3 years of support as the minimum for LTS status.”
Without a doubt and without a question, this is by far, the biggest and the best achievement for Ubuntu GNOME Community. We’re not only an official flavour of Ubuntu but also got the LTS Status.
Ubuntu GNOME and Lubuntu are going to have their very first LTS Release at the same time. This is a great achievement for both Communities
This is the result of very hard and great work that has been putting into Ubuntu GNOME for the last few months. We’re getting better in everything. Yes, we are not perfect (no such thing as perfect system) and we do have mistakes but we’re learning from our mistakes and we’re interested not to do the same mistakes, yet again. We’re growing fast in quality and quantity. This is the result of not giving up and for going the extra miles.
Congratulation for Ubuntu GNOME Community (Team Members and Users) for this huge achievement and huge thank to Ubuntu Technical Board for their trust and endless support. Of course, we’d like to thank each and every volunteer who has helped Ubuntu GNOME and still helping. All of you are the best people. Those who dedicate their time and effort to help other people just to draw a smile on their faces are indeed unique, special and great people who deserve our full respect. Everyone involved with Ubuntu GNOME is great and so kind because he/she helped and supported us.
A new era for Ubuntu GNOME and a new glory is on the way. We must be prepared and ready. It is not the end, this is just the beginning.
Now, this calls for more recruitment and more commitment. Ubuntu Board put their trust in us. We must be trust worthy. We must prove ourselves as the best when it comes to commitment and support.
If you like Ubuntu GNOME, if Ubuntu GNOME managed to change your life or the way you’re using the Computer with and/or if you want to do something for Ubuntu GNOME to show your appreciation … it is very very simple – just get involved and write your name with the great people who have done all what they could and even more to reach to this point.
We’re looking forward for more volunteers.
You can always contact us if you need anything.
And last but not least, it is time to spread the word and let the whole world know that Ubuntu GNOME 14.04 is going to be supported for 3 years as an LTS release.
Please, spread/share this with everyone
Thank you for choosing, using and supporting Ubuntu GNOME!
nothing new to report this week
Release Metrics and Incoming Bugs
Release metrics and incoming bug data can be reviewed at the following link:
Milestone Targeted Work Items
4 work items
2 work items
1 work item
1 work item
2 work items
3 work items
1 work item
Status: Trusty Development Kernel
The 3.13.0-18.38 Trusty kernel has been uploaded to the archive. This
is based on the v3.13.6 upstream stable kernel. I would also like to
remind everyone that Trusty Kernel Freeze is fast approaching on Thurs,
Apr 3. Please make sure to get any outstanding patches submitted to our
Ubuntu kernel team mailing list for review asap. After kernel freeze,
all patches are subject to our Ubuntu SRU policy.
Important upcoming dates:
Thurs Mar 27 – Final Beta (~1 week away)
Thurs Apr 03 – Kernel Freeze (~2 weeks away)
The current CVE status can be reviewed at the following link:
Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid
Status for the main kernels, until today (Nov. 26):
- Lucid – No changes this cycle
- Precise – No changes this cycle
- Quantal – Verification
Saucy – Verification
Current opened tracking bugs details:
For SRUs, SRU report is a good source of information:
Open Discussion or Questions? Raise your hand to be recognized
No open discussion.
It will be great to see more and more apps for Ubuntu coming in soon, and it will be especially fantastic since all of them are going to work on all current and future form-factors, being written in the same code.
What I was really happy to be involved with was our push for Ubuntu Apps in China. For the Ubuntu App Showdown (which is still running for around 3.5 weeks, until 9th April) we added a prize category for Chinese apps, which became the starting point for other activities.
App Showdown Judges
I’m super happy we have a diverse judges for the Ubuntu App Showdown. Jack Yu from Ubuntu Kylin, Joey Chan from the Ubuntu Core Apps team and Shuduo Sang from the PES team at Canonical. All of them have helped with lots of different questions and bits of organisation. Thanks a lot for your help!
App Development Events
We had a fantastic Ubuntu App Developer Week some two weeks ago, and while having the videos on YouTube works great for a lot of us, it’s not the best choice for China. Thanks a lot Shuduo for uploading all of the videos to youku.
This means that if you’re in China, you can just go ahead and get all the video goodness from there and learn all about Ubuntu App Development.
I’m very grateful for all the help from the people at Ubuntu Kylin.
In no time they invited Joey Chan (who has worked on the RSS Reader Core App, among others) to give a talk at the NUDT university in Chansha. The event was well-attended and well-received – around 100 Ubuntu enthusiasts turned up and Joey explained about Ubuntu for phones and using QML to write apps.
Videos are available here.
More events are planned, so stayed tuned for more news there. China was one of the first LoCos to have Ubuntu App Dev School events!
Translations of Chinese App Development Docs
The Ubuntu Community in China was super helpful in translating an initial set of developer documentation up at developer.ubuntu.com/zh. Translations, peer review and getting the docs online was done in just a couple of days, which is just fantastic. Right now we are looking at translating more content, which should make translations a lot easier. Thanks a lot everyone!
If you have more ideas for what we could do for Ubuntu apps being more interesting to and in China, get in touch with me.
If you are into writing apps yourself, there is still 3.5 weeks to get into the Ubuntu App Showdown. What you have to do is simple:
- Read how it all works.
- Start writing the app.
- Inform us on Weibo about your feedback (use the “#ubuntuappshowdown#” tag) and follow us on Weibo.
- Follow more instructions on the developer.ubuntu.com blog.
- In the Chinese prize category you can win one of these:
- Be creative and make Ubuntu even more beautiful in China!
Intel's thermald prevents machines from overheating and has been recently introduced in the Ubuntu Trusty 14.04 LTS release. Thermald actively monitors thermal sensors and will attempt to keep the hardware cool by modifying a variety of cooling controls:
* Active or passive cooling devices as presented in sysfs * The Running Average Power Limit (RAPL) driver (Sandybridge upwards) * The Intel P-state CPU frequency driver (Sandybridge upwards) * The CPU freq driver * The Intel PowerClamp driver
Thermald has been found to be especially useful when using the Intel P-state CPU frequency scaling driver since this can push the CPU harder than other CPU frequency scaling drivers.
Over the past several weeks I've been working with Intel to shake out some final bugs and get thermald included into Ubuntu 14.04 LTS, so kudos to Srinivas Pandruvada for handling my patches and also providing a lot of timely fixes too.
By default, thermald works without any need for configuration, however, if one has incorrect thermal trip settings or other firmware related thermal zone bugs one can write one's own thermald configuration.
For further details, consult the Ubuntu thermald wiki page.