Language Selection

English French German Italian Portuguese Spanish

Fedora 10 on SD Card for the OLPC Laptop

Filed under
Linux
OLPC
Hardware

For adults who may not find the child focused graphical interface called Sugar practical for daily use, the Fedora 10 option allows your XO to behave in a more familiar way.

In this sense, the XO is on-par with any small form factor laptop, except your purchase of an XO during the Give One Get One promotion directly effects the lives of children.

pre-order here




More in Tux Machines

Nintendo Nixes Android Rumors

  • Nintendo Nixes Android Rumors
  • 3 Reasons Nintendo Should Switch to Google Android
    What are the odds Nintendo’s next platform, possibly a suite of devices codenamed “NX,” would emerge running a flavor of Google’s popular operating system, as claimed by a single anonymous insider in a column by Japanese biz paper Nikkei?
  • Nintendo's next console won't run Android after all
    Aside from its codename, we know little about Nintendo's in-development "NX" console. Yesterday, however, Japanese publication Nikkei claimed to have hit upon a particularly juicy detail about the next-gen gaming system, with its sources stating the NX will run some form of Google's Android OS. The rumor wasn't exactly far-fetched, given Nintendo's plans to get into mobile games this year; but alas, it appears to have been a blast of hot air.

First Open Automotive Grade Linux Spec Released

Since its inception, the Linux Foundation's Automotive Grade Linux project has promoted itself as a collaborative open source project. With the release of the first AGL Requirements Specification for Linux-based in-vehicle infotainment (IVI), AGL has earned that description more than ever. Read more

Qt 5.4.2 Released

Today we have released Qt 5.4.2, the second patch update to Qt 5.4. In addition to improvements and fixes to Qt functionality it also packs new Qt Creator 3.4.1. Read more

diet4j: run Maven modules directly, and avoid gigantic JARs and WARs

Maven is great for breaking gigantic code bases into many little modules, with identified dependencies. This allows incremental builds etc. And then, to run that code, we usually put all together again into a uber-mega-JAR or WAR, or with mile-long class paths. While sometimes this makes sense, often it does not. diet4j can run command-line apps, and Tomcat web apps, similarly to how maven builds projects: simply specify the name of the top project, and diet4j assembles all the other JARs automatically for the run. E.g. if your project hierarchy looks like this:
    Project A
        Project B
            Project C
        Project D
you can say:
> diet4j A
which will read the POM in A.jar (in ~/.m2/repository, or a location of your choosing), determine run-time dependencies, then recursively look for B.jar, C.jar and D.jar, load them into separate ClassLoaders, hook up dependencies and jump on the main program (if it has one) of Project A. It may not be for all people, but it is for some who want to distribute changes incrementally, avoid rebuilding gigantic JARs every time some small change needs to happen, fit better into Linux-style package management etc. It’s also great for dynamically finding and loading modules without restarting the application. We’d love some feedback, it’s early days. http://diet4j.org/