Tuesday, June 26, 2012

rc.local on suse

Suse does not have rc.local enabled by default.

which means it is difficult to have a program automatically start up, after your system has been booted.

Suse does have a file called /etc/init.d/boot.local.

However it is not the same as rc.local
Inputting paths to files to run in the boot.local file
executes them before going to the first run level.
Which is a problem if you need your application to run after the system has completely booted.

rc.local to the rescue.

simply create your own rclocal file like so.
I use vim but you can use any file editor program like nano or gedit
vim /etc/rc.d/rclocal

then inside the file type the following (between the -----)
#! /bin/sh
## This script simulates redhat's rc.local (Add commands at the end)
# Provides: rclocal
# Required-Start: $local_fs $remote_fs $network
# X-UnitedLinux-Should-Start: $ALL
# Required-Stop:
# X-UnitedLinux-Should-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: Simulates rc.local
# Description: Simulates redhat's rc.local: contains
# commands to execute after system has booted (all services are already
# available)
## Execute ony when service is started
case "$1" in
## commands will be executed
exit 0

#  Add your commands bellow this line

Save the file.
Make the file executable by typing the following: chmod +x rclocal
Create symlink to make it easy to find:  ln -s rclocal rc.local
Next, you need to enable the rc.local simulation in yast.
then scroll to
System > system services (Run Level)
then scroll down to
> rclocal   simulates rc.local
and enable it
 > Enable

Save your settings, and you are done.
you now have a rc.local that behaves exactly like the redhat/fedora  rc.local
You can add/remove commands to /etc/rc.d/rc.local anytime
by simply editing the rclocal file and adding your commands you wish to execute at the bottom of the file.

Tuesday, June 5, 2012

How to Upgrade from Fedora 16 to Fedora 17 (Beefy Miracle)

Insure that your system has more than 600MB of RAM, The upgrade requires this.(1GB or more is recommended)

First change to root user

su -

Upgrading To Fedora 17 (Desktop)
First upgrade your rpm package:

yum update rpm

Install the latest updates:

yum -y update

Clean the yum cache:

yum clean all

If a new kernel got installed during yum -y update, you should reboot the system


After the reboot, su back to root

su -

Install preupgrade...  (preupgrade will also take care of your RPMFusion packages)

yum install preupgrade

run preupgrade


The preupgrade wizard will then start on your desktop. Select Fedora 17 (Beefy Miracle). Your system will then prepare for the upgrade.

At the end, of the prepartion click on the Reboot Now button.
During the next boot make sure to catch the boot loader and select
Upgrade to Fedora 17 (Beefy Miracle).
During the reboot, your system will upgrade. This can take a  very long time, so please be patient.
(My system took about 4 hours)

That's it, Once Complete you can log into your new Fedora 17 (Beefy Miracle). system

To do the same on a Server that does not have X server (GUI) installed

Follow the same steps as above but run preupgrade with the following option


preupgrade will show you a list of releases that you can upgrade to. included in that list will be
Fedora 17 (Beefy Miracle) 

[root@server1 ~]# preupgrade-cli
Loaded plugins: blacklist, langpacks, whiteout
No plugin match for: rpm-warm-cache
No plugin match for: remove-with-leaves
No plugin match for: auto-update-debuginfo
Loaded plugins: langpacks, presto, refresh-packagekit
please give a release to try to pre-upgrade to
valid entries include:
   "Fedora 17 (Beefy Miracle)"
[root@server1 ~]#

To upgrade, append the release string to the preupgrade-cli command:

preupgrade-cli "Fedora 17 (Beefy Miracle)"

Preupgrade will also take care of your RPMFusion packages, so all you have to do after preupgrade has finished is to reboot:


catch the boot loader and select Upgrade to Fedora 17 (Beefy Miracle).

that's it, your Done.