Translate

Image of Beginning Google Maps API 3
Image of Modern Operating Systems (3rd Edition)
Image of Linux Kernel Development (3rd Edition)
Image of Android Wireless Application Development

Upgrade Fedora 15 to Fedora 16

It goes without saying that you should back up all essential data and files before attempting an upgrade. As superuser, drop down to runlevel 3 (init 3), i.e. non-GUI multiuser and execute the following commands in the order that they are shown below. # rpm –import https://fedoraproject.org/static/A82BA4B7.txt # yum -y update yum # yum clean all # yum -y –releasever=16 –disableplugin=presto distro-sync That is it. Reboot your system to ensure that the upgrade to Fedora 16 was successful. Note that your multiboat loader will still be Legacy GRUB and partitioning on the boot fdisk will still be MBR (Master Boot

GNOME 3.2 Simple Popup Menu Example

GNOME 3.2 is about to be released. There are major changes in the way GNOME Shell extensions must to be written in order to work with this version of GNOME. Here is a simple GNOME 3.2 Shell extension which demonstrates a simple popup menu on the right hand side of the panel (top bar.) Once loaded, it can be enabled (displayed) or disabled (removed) without restarting the GNOME Shell. This is a major improvement over GNOME 3.0 and 3.1. // // Copyright (c) 2011 Finnbarr P. Murphy. All rights reserved. // const St = imports.gi.St; const PanelMenu = imports.ui.panelMenu; const

Fedora 16 1000 System Accounts

Some changes are coming to user and group accounts in Fedora 16 (codename Verne.) According to the project owner, Miloslav Trma─Ź of Red Hat, the UID/GID space allocation in Fedora (and I assume also in Red Hat, CentOS, and other derivatives) is not clearly defined, and is hard-coded in various applications. The intent of this feature is to allocate 1000 ID values for system accounts. Quite a few applications have hard-coded the 500 value as a boundary; instead of replacing this with a hard-coded value of 1000, such applications will be modified to read the boundary from /etc/login.defs. According to