Medan Slackware Community blogspot

Here our Slackware community blog for slacker in Medan, Indonesia
medan-slackware.co.cc

My first Release code

i have created the code, if you want it download in my web
juanssipayung.googlepages.com
Do not release it. It is your responsibility if your realease it on the wild.

Learning JavaScript

I have an idea to create a script with javascript, maybe it will be a virus :>.
I will realease it before end of this month :D.

My Headache....

My head really sick, because the turning of seasons. Night cold caught me, make my body weaking, and my healthty decreasing....

Patching Linux Kernel

Patching linux kernel is so simple.
First, You must download the kernel and the patch (of Course !),
Then, Applying the patch, simple is it? he... he... he...

For Example on my Slackware 12.

My slack comes with kernel 2.6.21.5 and i want to use the new one, like 2.6.23,
So i must get the pacth-2.6.21.5, patch-2.6.22, patch-2.6.23 from www.kernel.org/pub/linux/kernel/v2.6

Now, how to applying the patch
extract the patch wherever you want,
go to /usr/src/linux-2.6.21.5 and apply the patch
$cd /usr/src/linux-2.6.21.5
$su
password:
#patch -p1 -R < /path/to/patch-2.6.21.5
#patch -p1 < /path/to/patch-2.6.22
#patch -p1 < /path/to/patch-2.6.23
#mv linux-2.6.21.5 linux-2.6.23
Edit symlink 'linux' to the new kernel source 2.6.23
now you have the new kernel 2.6.23

applying patch for branch from 2.6.23 2.6.23.9
download patch-2.6.23.9
extract the patch
$cd /usr/src/linux-2.6.23
$su
#patch -p1 < /path/to/patch-2.6.23.9
#mv linux-2.6.23 linux-2.6.23.9
Edit symlink 'linux' to the new kernel source 2.6.23.9

applying patch for branch from 2.6.23.9 to 2.6.24
download patch-2.6.23.9 and patch-2.6.24
extract the patch
$cd /usr/src/linux-2.6.23.9
$su
#patch -p1 -R < /path/to/patch-2.6.23.9
#patch -p1 < /path/to/patch-2.6.24
#mv linux-2.6.23.9 linux-2.6.24
Edit symlink 'linux' to the new kernel source 2.6.24

note:
patching from 2.6.21.5 to 2.6.21.7, just go through (-p1)
patching from 2.6.22 to 2.6.23, just go through (-p1)
patching from 2.6.23 to 2.6.23.9, just go through (-p1)
patching from 2.6.23.9 to 2.6.24, first you must reverse the 2.6.23.9 to 2.6.23 by
applying patch-2.6.23.9 (-p1 -R) then patch-2.6.24 (-p1).

Happy hacking :>

Link for current iso slackware 12

http://ftp.belnet.be/mirrors/ftp.slackware.com/slackware-current-iso/

ftp://ftp.slackware.no/pub/linux/ISO-images/slackware/Current-ISO-build/

http://linorg.usp.br/iso/slackware/

Splashy for slackware

(copy from splashy Slackware Installation)

Notes This page applies to Splashy 0.3.6 and older.

Compiling Dependencies

glib2

Slackware includes glib2 in the l/ diskset, but Splashy needs the static libraries, along with the shared libraries. To do this, you need to grab the contents of source/l/glib2/ from your favorite mirror. Next you need to add –enable-static to your ./configure section and increment BUILD. Now build the package with

# ./glib2.SlackBuild

This package can now be installed with

# upgradepkg /tmp/glib2-2.12.12-i486-2.tgz


freetype

Like glib2, freetype is included in Slackware, but needs to be rebuilt to include the static libraries. You need the files from /source/l/freetype like above. The static libraries are built by default, but are deleted by the build script. To preserve these libraries, you need to comment the following line:

rm -f $PKG/usr/lib/*.a

Increment BUILD in this file too, then run

# upgradepkg /tmp/freetype-2.3.4-i486-4.tgz


DirectFB

Eric Hameleers has created a SlackBuild for DirectFB which is available from his SlackBuilds Repository. Simply grab the three files from there, and execute directfb.SlackBuild.

Splashy

Eric also created SlackBuild for Splashy which is available from a here.


Pre-Built Binary

If all of the above seems like too much work, and you would rather use a prebuilt binary instead, Eric Hameleers has a binary package based on the above SlackBuild for Splashy 0.3.5 on Slackware 12.0, which is available here.
Configuration

As of now, the only known way of running Splashy during boot is by editing /etc/rc.d/rc.S and /etc/rc.d/rc.M. This is very dangerous if you don't know what you are doing, so it is imperative to make backups of these files before you start.

I added the following to the beginning of /etc/rc.d/rc.S

# Start Splashy
/sbin/splashy boot

I then added the following line after each “paragraph” of rc.S and rc.M

/sbin/splashy_update "progress #"

Updating # with the actual percentage as I went along.

MPLAB for Linux

Now i have the gputils, gpsim tools for learning PIC in linux, not really bad, but i think these software are really good.

have a good new years to go...