Frankenpup 8, the ocho

 Well i'm annmouncing the latest frankenpup alpha, short story:

LINK 1 file 160Mb iso

-WARY-070 / Slackware-13.1
-kernel: 2.6.34.1 SMP (WARY)
-glibc: 2.11.1 (from Slackware 13.1)
-gcc: 4.4.4 (same)
-fluxbox instead jwm (from slack)
-python script to keep the fluxmenu structure (fixmenus linked to that script)
-firefox 3.6.10
-no office software yet =P (i'm still stripping down Open office)
-removed a lot of apps (abiword, gnumeric, osmo, attym, gftp, and some others i will upload the list later)
-The run action for the txz packages is linked to my TXZinstaller script so you can install them with 1 click =)
-dbus-uuidgen on starup (to prevent dbus to FAIL hard)
-dbus-daemon on starup (for obvius reasons)
-on shutdown a script cleans the /var/run/dbus/ folder (to prevent starup FAIL)


Slackware packages used so far:

>cxxlibs-6.0.13-i486-2 (MAIN)
>dbus-1.2.24-i486-2 (MAIN)
>dbus-glib-0.86-i486-3 (MAIN)
>gcc-4.4.4-i486-1 (devx_8.sfs)
>gcc-g++-4.4.4-i486-1 (devx_8.sfs) [testing]
>glibc-2.11.1-i486-3 (MAIN) [testing]
>gmp-5.0.1-i486-1 (devx_8.sfs)
>python-2.6.2-i486-3 (MAIN)(will upgrade it to 2.7)

Software from WARY:
-pmusic
-mplayer
-geany
-mp
-calcs

and all the common puppy apps (i'm deleting a lot of them)

screens:

That's all so far, it's the first build i made using WARY(Quirky family) so i'm going slow because i don't wanna fuck the whole system.

New processor

Hello normal people, well i recently brought a new processor (2Gz P IV, older was a 2.5Ghz Celeron) and i'm gonna talk you a little about teh HUGE differences between those 2 procs.

well technically speaking:
Celeron, 2.5Ghz, 128Kb L2 caché, 400FSB
Pentium4, 2Ghz, 256Kb L2 caché, 400FSB

they looks pretty similar, but after some test and in the common day use i have noticed how fast is the P4 against the celeron (almost 2X fast).

Why? some people usually thinks: more Mhz=More speed, that could be right if you are talking about 2 processor of the same production line (a Pentium4, 2Ghz, 256Kb L2 caché, 400FSB against a Pentium4, 2.8Ghz, 256Kb L2 caché, 400FSB) but when comes to 2 completely different procs, there is some things more importants than the Ghz, i'm gonna define 2 of them:

First: L2 Caché
What does L2 caché is/does? the simplest way to describe it is : Level 2 or L2 cache is part of a multi-level storage strategy for improving computers performance (i'm not going to describe it technically, way too much shit to talk about this xD). So, in other words, More L2 cache = more data can enter to the processor.

Second: the Front Side Bus (FSB)
a quick definition can be: In PC , the FSB is the bus that carries data between the CPU and the northbridge. So more FSB = more data between the proc and the motherboard.

So as we can see the L2 cache of my new processor is 2X higher than the older, so the cpu can take 2X more data, but that doesn't means the new processor is "faster" in speed, it can handle more data in almost the same amount of time, and why it isn't 2x or more times fast?, because the Ghz are sigthly lower, so it can't make the same cycles per second, so my conclusion is: P4 FTW!! FUCK YOU CELERON!!!

ok, i'm out.

samedog.

And nothing of value was lost

Hello normal people i have been busy like hell with life and university and lots of other kind of "normal peope" stuffs, hope i can make some post sooner, also i have finished (months ago) a frankenpup digital audio workstation version BUT i have no time to upload it (and the internet in home is .. just let's say it is SLOW), so i'm gonna see if a friend can upload it or something.

well hope i can blabklaskjdlakjdskdjalksdjla soon

samedog out.

playing with udev, dbus and hal for puppy and kde users

Hello normal people! I have been playing around with HAL on frankenpup2 for a while and i am having some good results to share after some very little mods to the rc.shutdown and the rc.local i was able to get some basic hardware detection for kde4, what does that means? that means kde4 is now aware of my sound card, video card and some usb devices (mp3 players, usb drives, etc) ok now the modifications i made: first you need to install dbus, HAL and udev (i got them from slackware-13.0 repos) then, when everything is installed and ready to go follow the next steps:

1.- type: dbus-uuidgen --ensure=/var/lib/dbus/machine-id after that make sure dbus monitor is running by typing: dbus-monitor if you get something like this: 

everything is ok and go to the next step
2.- now add the groups: video, lp, disk, floppy, cdrom, tape, plugdev and power
type: addgroup video (and then replace video with lp)

3.- ok let's make the socket we need for HAL
type: rm -rf /var/run/dbus/* then: dbus-daemon --system and check the /var/run/dbus for dbus.pid and system_bus_socket now go to the next step


4.- ok so you have the groups and the socket now let's test HAL
type hald on the terminal and if it just makes a little stop and drops you to # it's actually running =)

5.- ok now test if hal is detecting the hardware by typing hal-device on the terminal. if you get something like this: YOU ARE DONE! XD well that's the software and config part now we need hal to load on the system boot so weare gonna mod some files on /etc/rc.d/

1.- ok first open /etc/rc.d/rc.shutdown to make a dbus-daemon hand-made cleaner
goto line 880 it should look like this

rm -rf /root/.thumbnails/* 2> /dev/null
sync

now add

rm -rf /var/run/dbus/*

and it should look like...

rm -rf /root/.thumbnails/* 2> /dev/null
rm -rf /var/run/dbus/*
sync

save and close.

2.- good, now we need to start dbus and hal on the system init now open /etc/rc.d/rc.local it should say

#this file called from rc.sysinit
#you can edit this file
#When firewall is installed, will append lines to this file...

now add this to it

######################LOAD DBUS####################

echo -n "starting dbus-daemon" >/dev/console

dbus-daemon --system

status_func 0

######################LOAD HAL#####################

echo -n "starting HAL" >/dev/console

hald

status_func 0

save and close. ok now reboot your system and let the magic flow!!  [uploading video] pretty good now HAL must be able to see all your hardware, make sure of that typing hal-device ona terminal, and if you see (again) this everything is ok, now try looking on the kde panel for some hardware detection and check if it shows something, i'm using kde4.2.4 and i got this: [uploading screenshot xD] or try plugging a usb drive.. [uploading video xD] well, hope this help someone. i'm now looking for a config somewhere to make autoruns for the usb and cd/dvd drives (or will make a daemon for that) to avoid pmount (as i am using kde and not rox the drive icons are not showed on the bottom of the screen) hope i can come out with something to share with the puppylinux community. Will keep you informed samedog out.

Tuxguitar (teh linux guitar pro)

Hello again normal people, now i bring you this... *cars crashing* TUXGUITAR, yeah it's the damn linux solution to guitar pro, it is able to open guitar pro files and everything like that, well without anything to say but GO SUCK A SOCK!! enjoy (IT NEEDS JAVA (JRE))


screenshots:

LINK

TUXGUITAR

some KDE 4.2 stuffs xD

Hello normal people today i'm glad to bring to you this! "KDE4.2 BASE, LIBS AND DEPS", i hope you enjoy it. deps >> so many dotpets to install!! how much fun =) kdebase >> boooring kdelibs >> =) kdebindings >> because they are too lazy to put this and libs on the same package D: and that's all for today folks, stay tuned for more weird thing to come chao, arrivederchi, bye, sayonnara, anything i'm out.