Tag Archives: James Hunt

Video: Latest Rush trailer reminds us that James Hunt was awesome

By Brandon Turkus

Rush The Movie - trailer screencap of F1 field in the rain

Filed under:

Rush, the upcoming Ron Howard flick that focuses on the intense rivalry between James Hunt and Niki Lauda during the 1976 Formula One World Championship, is looking better and better with each trailer.

The most recent spot focuses on Hunt, playing up his reputation as a notorious womanizer and playboy. You get a glimpse of the transformation that Chris Hemsworth’s character goes through as the movie proceeds, from the free spirit shown in the beginning of the trailer to the intense competitor eager to best Lauda.

Take a look at the trailer below and be sure to check out the previous clips here and here. Rush hits theaters on September 27. Don’t plan on much from Autoblog that day – we’ll all be at the theater.

Continue reading Latest Rush trailer reminds us that James Hunt was awesome

Latest Rush trailer reminds us that James Hunt was awesome originally appeared on Autoblog on Thu, 18 Jul 2013 12:46:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

…read more

Source: FULL ARTICLE at Autoblog

Ron Howard’s New Movie, Rush, Recreates One of F1′s Greatest Driver Battles—Lauda vs. Hunt

By Alexander Stoklosa

Niki Lauda Rush movie trailer

As F1 racing stages a comeback here in the States—this season it’s on NBC Sports, not to mention the new track down in Austin, Texas—along comes a movie about the sport that could move it closer to the forefront of the public’s mind. From none other than director Ron Howard comes a new flick, Rush, about the epic 1976 driver battle between Niki Lauda and James Hunt for the Formula 1 world championship. Now, we’re a lot better suited for reviewing cars than movies, but based on the trailer for Rush, it’s looking like a must-see for any race fan.

Hunt is played by Chris Hemsworth and Lauda by Daniel Brühl, while Olivia Wilde and Natalie Dormer also are in the mix. The ’76 season was characterized by Hunt and Lauda’s on-track rivalry, which at one point saw Lauda nearly killed at the Nürburgring. We’re just spitballing here, but our bet is that with detail-oriented Ron Howard at its helm, Rush should be far better to watch than the only other non-documentary open-wheel racing movie in recent (we reiterate, recent) memory, Driven. That movie had Sylvester Stallone in a lead role, so, yeah. It will be interesting to see whether Rush turns out better than 2010′s Senna, the excellent documentary that chronicled the life and premature death of F1 prodigy Ayrton Senna. Check the trailer out for yourself below and let us know what you think in the comments section:

…read more

Source: FULL ARTICLE at Car & Driver

Video: Ron Howard's Rush trailer sets stage for an epic F1 drama

By Seyth Miersma

Ron Howard's Rush F1 biopic - trailer

Filed under:

The story of the 1975 Formula One World Championship – and the rivalry cum friendship between Niki Lauda and James Hunt that lies at its core ­- is one step closer to making its Hollywood splash. The first theatrical trailer of Rush has cropped up on YouTube, and it’s safe to say that we’re more excited than ever to watch the movie when it hits theaters on September 20.

Based on some of the cuts we see here – Lauda’s infamous crash at the Nürburgring and a dark and sodden start to the 1976 Japanese Gran Prix – it appears that no effect expense was spared to make the Ron Howard film as convincing as possible. Should performances from Daniel Brühl and Chris Hemsworth stand up, Rush could be more than just a diversion for hardcore racing fans. Follow on below for the official trailer.

Continue reading Ron Howard’s Rush trailer sets stage for an epic F1 drama

Ron Howard’s Rush trailer sets stage for an epic F1 drama originally appeared on Autoblog on Mon, 08 Apr 2013 09:57:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

…read more

Source: FULL ARTICLE at Autoblog

James Hunt: Coverity static analysis for C, C++ and Java code

It’s a well known principle of software engineering that the earlier bugs can be caught, the lower the overall cost. As such, testing needs to happen at every level. Once your project is at the coding stage, the earliest form of testing is on the code itself, not on the binaries the compiler produces.

We run a variety of tools over critical codebases such as Upstart and Whoopsie regularly to identify issues well before they “escape into the wild”. These tools include Coverity Scan (see the list of projects already using it).

If you really care about your code and you are involved with a C, C++ or Java project, I’d strongly encourage you to take a look at this awesome tool. If you aren’t directly involved in such projects, try contacting those running them and suggesting they use Coverity.

The Coverity Scan service is entirely free for OSS projects. You will need to register to obtain an account and then download the client analysis tool. Once setup, a particularly attractive feature is the ability to auto-upload the analysis data generated for your project using ESR’s coverity-submit tool. This could for example be hooked into your upload or release process to ensure no code quality regressions. After you have uploaded the analysis data, you can browse through the results of the scan using the web interface in a variety of ways, including a view that shows the errors “inline” with markers added around the code Coverity has identified as problematic.

For those who have either never used static analysis tools, or have simply never used Coverity, don’t fall into the trap of thinking that gcc -pedantic -Wall or even LLVM‘s scan-build should be “good enough for anyone” – it simply is not. Consider too Steckel’s Rule to Success,

“Good enough is never good enough”

Coverity performs very deep analysis and its results may well surprise you… but rather that than unexpected surprises for your users.

Apologies if this post sounds like a bit of a sales pitch. It really isn’t though: the Coverity service is free and what they are offering really is too good to ignore.

Note: I have no affiliation with Coverity – I’m just extremely impressed with their Scan tool! 🙂

…read more

Source: FULL ARTICLE at Planet Ubuntu

Rush Trailer Speeds Online

A brand-new trailer for racing drama Rush has hit the net, courtesy of MSN Movies. Set in the 1970s, the film details the rivalry between Formula 1 drivers James Hunt and Niki Lauda.

Thor himself – Chris Hemsworth – plays the English driver, while Inglourious Basterds star Daniel Bruhl plays the Austrian.

Written by Peter Morgan (Frost/Nixon, The Queen), Rush is directed by Ron Howard and set to hit screens worldwide this September.

Continue reading…

…read more

Source: FULL ARTICLE at IGN Movies

James Hunt: Upstart 1.8 released

Hot on the heels of Upstart 1.7 comes Upstart 1.8 which includes two interesting new features:

The File Bridge

Upstart now provides the upstart-file-bridge, a bridge that allows jobs to react to file events.

Here are a few examples:

Start a job when file is created, modified or deleted:

start on file FILE=/run/app.pid

Start job when file is created (only):

start on file FILE=/run/app.pid EVENT=created

Start job when any files within a directory are created, modified or deleted:

start on file FILE=/var/log/

Start job when files that match a glob pattern are created in the indicated directory:

start on file FILE=/var/crash/*.crash EVENT=created

Even better, this bridge is available to both system jobs and users session jobs.

See upstart-file-bridge(8) and file-event(7) for further details.

The GUI

The upstart-monitor tool covered in a previous post has also been added to the release. This allows you to see what events Upstart is emitting and how jobs are changing state both at the system and user session levels.

You can download Upstart 1.8 from:

Upstart 1.8 should be landing in Ubuntu Raring in the next few days. Thanks to all involved!

Contributions

If you are interested in contributing to Upstart, we’d love to hear from you. Now is a great time to get involved, since with the advent of the upstart-monitor the fun expands to include GUI hackers too!! 😉

…read more
Source: FULL ARTICLE at Planet Ubuntu

James Hunt: A basic Upstart Events GUI (and cli!:-) tool

It didn’t quite make it into the release, but we now have a very basic Upstart GUI that should appear in Ubuntu along with the Upstart 1.7 release soon.

What is it?

upstart-monitor is a simple application that shows Upstart events as they are emitted. It can be used to view both system-level events and also session-level events when Upstart is running as a Session Init.

It requires Upstart 1.7.

What can I use it for?

The tool allows you to see events as they occur which is an aid to understanding. It also helps with writing new jobs since, if you are not sure which event to use, provoke the scenario you want, then just copy the appropriate event that appears in upstart-monitor to your .conf file (more details on this in a future post…).

How do I use it?

Just start it to see events being emitted:

If you’d prefer a command-line version, run it with the ‘-n‘ option:

Where can I get it?

If you can’t wait for it to land in Ubuntu, you can grab it from here:

…read more
Source: FULL ARTICLE at Planet Ubuntu

James Hunt: Upstart 1.7 released

We’ve just released Upstart 1.7 which expands Upstarts abilities a lot. I’ll follow up with a further post explaining what these changes mean for users as this release is soon to appear in Ubuntu.

Summary of changes

  • New initctl commands: set-env, unset-env, get-env, list-env, reset-env, list-sessions (all except last with corresponding D-Bus methods).
  • New D-Bus-only signals EventEmitted, Restarted, and EndSession method.
  • Ability to run with PID >1 to allow Upstart to manage a user session.
    Running Upstart as a ‘Session Init‘ in this way provides features
    above and beyond those provided by the original User Jobs such that
    the User Job facility has been removed entirely: to migrate from
    a system using User Jobs, simply ensure the user session is started with
    init –user‘.
  • New upstart-event-bridge bridge which proxies system-level events down to Session Inits, allowing users jobs to react to udev events.
  • Ability to read job configuration and override files from multiple freedesktop-compliant locations (Session Init only).
  • Ability to shutdown both via a system shutdown request and via a user logout request (Session Init only).
  • Additionally, there are a few bug fixes and 94 new tests.

Thanks to all the contributors, reviewers, testers and users!

Download

Get it here https://launchpad.net/upstart

…read more
Source: FULL ARTICLE at Planet Ubuntu

James Hunt: A bazaar hook to reduce VCS meta-data asynchrony

What changed?

Sometimes, when using VCS systems such as bazaar, there is a tendency to forget to perform the necessary ‘book-keeping’ for those not using it because you get so focused on the tooling itself.

Most VCS systems expect the author to provide a brief explanatory message per commit. This log is invaluable since it (hopefully!) provides insightful context into the programmers intentions. However, that meta-data is only available to those with a copy of the branch/checkout/stream/view or whatever your VCS calls it.

But what about those who only come into contact with the project via release tarballs for example?

I’m thinking specifically of changelogs. Debian and Ubuntu provide the incredibly useful ‘dch‘ (aka debchange) tool which synchronises the VCS commit message with the latest ‘debian/changelog‘ file entry. But what if you’re not working on a Debian project? When you’re working on a fast-paced project, or just working at a particularly fast pace, it’s easy to forget to update the top-level changelog in addition to providing your usual VCS commit message. If and when you remember or notice they have gone out of sync, you can of course create a new commit purely to “sync up” the VCS commit log with the actual changelog file. But having to do that is annoying. I hit this issue recently and duly put bzr to work to help avoid this situation in the future.

bzr hooks to the rescue

A minor tweak to my bzr pre-commit hook that checks for signs of unfinished work was all it took to solve this for me. What that hook now does is to also offer to abort the commit if:

  • the commit would change files below the debian/ directory, but debian/changelog has not been updated.
  • the commit would change non-debian-directory files, but the top-level changelog has not been updated.
  • both the top-level and the debian changelog have been modified (shouldn’t generally happen at the same time).
  • both debian and non-debian-directory files have been modified (shouldn’t generally happen at the same time).

 Code

Warning

If a bzr hook causes the commit to abort, you will lose your pending commit log entry text! Unfortunately, there doesn’t appear to be a public API to allow hooks to save the text to a file (but please tell me if I’ve missed this!)

I hadn’t noticed this issue since I generally commit having pre-prepared a bzr commit log entry (“bzr commit -F /tmp/commit.txt“) so didn’t notice this until recently.

Source: FULL ARTICLE at Planet Ubuntu