news, Open Source, OS

Yay! OpenMandriva Punya Muka

Setelah beberapa lama tak punya muka, logo, akhirnya OpenMandriva mengumumkan sekarang mereka sudah punya. Muka baru OpenMandriva ini adalah hasil voting publik atas 36 proposal yang masuk dan terpilih.

openmandriva-logo

Proses voting publik sendiri hanya berjalan selama 5 hari yaitu sejak tanggal 6 dan berakhir 10 Maret 2013. Selanjutnya dari 5 besar hasil voting dilakukan brainstorming dan diskusi lalu dilanjutkan dengan voting internal.

Sekarang, setelah memiliki muka, OpenMandriva butuh sesuatu lagi: nama distro. Mau nyumbang?
quest-for-holy-name

linux, news, Open Source, OS

Ubuntu 12.04 (Precise Pangolin) LTS Beta Screenshots

The Ubuntu team has announced the first beta release of Ubuntu 12.04 –codename Precise Pangolin– on March 1st. This version is an LTS of Desktop, Server, Cloud, and Core products. In previous releases an LTS version supported for 3 years. But, starting 12.04 both desktop and server version will be supported for 5 years. Lovely.

Ubuntu 12.04 LTS

Check out these 31 screenshots of this first beta version while you waiting for the release one –which will be announced at April 26th.

And, of course, you can have first beta version with these provided steps by the Ubuntu team.

linux, Open Source, viewpoint

[UNIX] Understanding the bin, sbin, usr/bin, usr/sbin split

As Unix users, we know there are so much paths in our system. From / to /home, etc, etc. And you knew these paths are assigned to particular files and folders. For example, /home is home users directories while /opt is the path for packages installed. But, how did it went like that? And why?

Understanding Unix

Rob Landley, who maintain Linux Firmware and an ex-maintainer of BusyBox, is trying to tell us the story behind these paths. Quoting from his explanation:

“.. when the system first boots, it has to come up enough to be able to mount the second disk on /usr, so don’t put things like the mount command /usr/bin or we’ll have a chicken and egg problem bringing the system up.”

Of course once the split existed, some people made other rules to justify it. Root was for the OS stuff you got from upstream and /usr was for your site-local files. Then / was for the stuff you got from AT&T and /usr was for the stuff that your distro like IBM AIX or Dec Ultrix or SGI Irix added to it, and /usr/local was for your specific installation’s files. Then somebody decided /usr/local wasn’t a good place to install new packages, so let’s add /opt! I’m still waiting for /opt/local to show up…

Of course given 30 years to fester, this split made some interesting distro-specific rules show up and go away again, such as “/tmp is cleared between reboots but /usr/tmp isn’t”. (Of course on Ubuntu /usr/tmp doesn’t exist and on Gentoo /usr/tmp is a symlink to /var/tmp which now has the “not cleared between reboots” rule. Yes all this predated tmpfs. It has to do with read-only root filesystems, /usr is always going to be read only in that case and /var is where your writable space is, / is mostly read only except for bits of /etc which they tried to move to /var but really symlinking /etc to /var/etc happens more often than not…)

Later on, there are some changes.

You can read complete Rob’s explanation here.

image: glasbergen.com

news, Open Source, Technology

Chrome is Connecting Web Apps through Web Intents

Chromium team is working on Web Intents, a framework that will let Web apps express a simple call for an action, like ‘share’ or ‘edit,’ which receiving apps will be designed to use, without either app needing to have specific knowledge of the APIs of the other. This framework designed based on Intents on Android which is a facility for late run-time binding between components in the same or different applications.

This Web Intents will change the way developers codes because they can just use these simple requests, which will be built into the browser, instead of having to code for each specific Web app one might want to access.

It’s not over yet, because Chromium team said they’re working closely with Mozilla engineers to unify their proposals into one simple, useful API.

Sounds legit!