Please note: I made this video with a mobile phone cam and so the Video is pretty poor quality. Also I had to use Audioswap to replace the barking of my dog.
For those who believe that Slackware is just another geeky distro with no eye-candy, well you are wrong. It’s all about customization. Anything you can do with any GUI-based distros like Ubuntu or openSUSE, you can do those with Slackware.
First of all apologies for poor video quality, took this one with my mobile phone cam. This is just to show an idea to the world that Slackware is not all about “all text and no fun”.
Using splashy with Slackwar64 – current [but works in 13.0 as well] and Fluxbox with a conky on top and Gkrellm.

“Mostrerò loro un mondo senza di voi, un mondo senza regole o controlli, senza frontiere e confini, un mondo in cui tutto è possibile. Quello che accadrà dopo dipenderà da voi e da loro”.

Complice l’influenza che mi ha colto in questi giorni ieri ho avuto modo di rivedere il secondo capitolo della saga di Matrix. Ora… non starò qui a sottolineare il potere che ha su di me questa trilogia, vi basti sapere che la visione di un solo capitolo mi è stata sufficiente per buttarmi a capo fitto…

…nella creazione di un tema, ispirato al film in questione, da utilizzare durante l’avvio della nostra distro preferita.

Come avrete capito non vi svelerò il segreto per collegarvi alla matrice da GNU/Linux (a meno che non vogliate farvi installare un plug dietro la nuca ) ma in compenso di seguito riporterò i pochi semplici passi per dare un tocco cyberpunk alla vostra GNU/Linux – box.

• Scaricate il file debian-matrix.tar.gz dal Forziere di Morg4n

• Aprire un terminale e diventare root:

su (e digitare la password)

• Installare splashy:

apt-get install splasy splashy-themes

in realtà non sarebbe stato necessario installare splashy-themes, che contiene i temi predefiniti di Debian, ma se poi il mio tema di Matrix non vi piace?

• Decomprimere il tema e copiarlo nella directory dei temi di splashy:

tar -xvzf debian-matrix.tar.gz

cp debian-matrix /etc/splashy/themes

• selezionare il tema e aggiornare il ramdisk di avvio:

splashy_config -s debian-matrix

update-initramfs -u

• modificare il file /boot/grub/menu.lst aggiungendo in fondo alla riga che inizia con kernel le istruzioni vga=791 splash in modo da avere una cosa simile a questa.:

title    Debian GNU/Linux, kernel 2.6.26-1-686
root     (hd0,0)
kernel   /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet vga=791 splash
initrd   /boot/initrd.img-2.6.26-1-686

riavviate la vosta GNU/Linux – box e preparatevi a scoprire “quant’è profonda la tana del bianconiglio…”

]]> http://sarahparis.wordpress.com/2009/08/01/374/ Sat, 01 Aug 2009 21:08:48 +0000 Sally http://sarahparis.wordpress.com/2009/08/01/374/ http://justsoftwares.wordpress.com/2009/07/26/change-ubuntu-boot-screen-with-splashy/ Sun, 26 Jul 2009 09:21:22 +0000 swagatmishra http://justsoftwares.wordpress.com/2009/07/26/change-ubuntu-boot-screen-with-splashy/

i was pretty bored with the simple yet not-so-cool boot screen of Ubuntu (to see what i am talking about click here).i wanted to change it .now there are 2 ways to change your boot screen.

1.install usplash and start-up manager.

2.install splashy.

but i wanted to go a step further…i did not want to be dependent on other theme sites for my boot screens,i wanted to create my own.this proved to be quite a pain with usplash,so i switched to splashy.it’s so simple to create your own splash screens with splashy.splashy is a boot splash program that does not require patching the linux kernel.it’s simple and easy to use.so go ahead and install it.

here’s how:

32-bit machine – libsplashyl_0.3.10-1_i386.deb, spalshy_0.3.10-1_i386.deb (i will be placing links for 64 bit machines soon)

In the terminal, type the following command to install the splashy-themes:

sudo apt-get install splashy-themes

now we will install gsplashy which is a GUI tool to create and set your boot screens

first install the dependencies

sudo apt-get install libglade2-dev libsplashy1-dev build-essential

download gsplashy to your desktop from here.

now compile the code

cd ~/Desktop/gsplashy0.1 (change the path if you have extracted gsplashy in another location)
./configure
make
make install

that’s it.you can start gsplashy by typing in a terminal

sudo gsplashy

this will pop up a window like this:

you have to specify boot skins for resume,shutdown,boot,hibernate and suspend.the picture should be a .png format.

for progress bar specify dimensions of X:250 Y:690width=512 height=15.feel free to experiment with all dimensions.

after installing a new theme do in a terminal

sudo update-initramfs –u

also change your vga settings:

gksu gedit /boot/grub/menu.lst

add vga=792 at end of line after splash.

that’s it..enjoy the new look of your ubuntu.

THE ABOVE METHOD MAY NOT WORK FOR YOU.IF SO,DO LET ME KNOW I WILL DO EVERYTHING TO HELP YOU.

DON’T FORGET TO COMMENT ON THIS.

In a typical splashy summer vacation scenario, near the Adriatic Riviera of Italy, ROMAGNA MIA is the classic “bring your girlfriend kind of skating contest”.

Second stop for the ITALIAN ROLLER LEAGUE 2009, street contest, vert contest, best trick miniramp contest, diving contest, tent city contest. This year seems that the prize money is 500 euros for cat. A, free stuff for cat. B and a Special Gift Holiday for the best trick.

Did I mention wet T-shirt contest?… Ask the guys @ Italianrollerleague or Fardamatti for further infos and the schedule.

Eyes on the prize.

Programma:

SABATO 18

ore 11.00

Apertura e free skating

ore 16.00

Street contest, categorie A-B

Vert contest

ore 20.00

Best trick minirampa

After Party

Tent City

DOMENICA 19

ore 11.00

Free skating

ore 13.00

Grigliata & bbq, categorie A-B

Gare di tuffi

Info:

info@italianrollerleague.com

Info park :

http://www.centrovacanzesanmarino.com/fardamatti%20sk8park.html

Main Sponsor:

Valo

Supporters:

Fardamatti

Freemove

Hedonskate

Lunatica clothing

Media partners :

www.bladeinitaly.it

www.bladermagazine.com

gettinther had issues with Splashy and so Unity Linux is returning to Bootsplash for the time being.

Plymouth (wiki, source) is something to keep an eye on in the future, but right now it doesn’t support all cards and especially not older hardware.  Once Plymouth has its issues solved, it’ll be looked at again.

I recently installed Debian Lenny KDE on my Thinkpad R61. The installation went smooth but suspend/hibernate did not work. When suspend was initiated from KPowersave or Guidance, the machine would go into suspend (the moon LED on the Thinkpad panel blinks) but it immediately resumes in to the KDE session.

After reading about software suspend in the debian wiki, I decided pm-utils and uswsusp was the recommended way to go.

http://wiki.debian.org/Suspend

http://en.opensuse.org/S2ram

I played with the s2ram script with different options, ‘s2ram -f‘, ‘s2ram -f -a 3‘, but I still got the same problem of suspend-immediate-wakeup (hibernate also had the same problem).

Then, I found thinkwiki had the exact problem description.

http://www.thinkwiki.org/wiki/Problems_with_ACPI_suspend-to-ram

http://www.thinkwiki.org/wiki/Installing_Fedora_8_on_a_ThinkPad_T61#Suspend_to_RAM

The problem is that the USB kernel modules are not unloaded for the suspend to complete. So, I created file called ‘defaults’ under /etc/pm/config.d/ with the following flags enabled (this is the preferred location for pm-utils customization – ref: /usr/lib/pm-utils/defaults):

# The default sleep/wake system to use.  Valid values are:
#   kernel    The built-in kernel suspend/resume support.
#             Use this if nothing else is supported on your system.
#   uswsusp   If your system has support for the userspace
#             suspend programs (s2ram/s2disk/s2both), then use this.
#   tuxonice  If your system has support for tuxonice, use this.
#
# The system defaults to "kernel" if this is commented out.
SLEEP_MODULE="uswsusp"

# If you need to unload any modules to suspend/resume, add them here.
SUSPEND_MODULES="uhci_hcd ehci_hcd"

Bam. Suspend and Hibernate were working beautifully. Just not quite. When the machine was waking up from hibernate nicely, splashy was emitting some errors. I got it working by reinstalling splashy and libsplashy1 and adding the kernel options for splashy in my grub menu. hwinfo was useful in finding the correct vga parameter that would be supported by my R61 (1280×800).

/boot/grub/menu.lst:

kernel          /boot/vmlinuz-2.6.26-2-686 root=/dev/sda3 ro quiet vga=0x368 splash

thinkpad:~# hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.450]
Unique ID: rdCR.pM4x9oRqolF
Hardware Class: framebuffer
Model: "Intel(r)Crestline Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(r)Crestline Graphics Controller"
SubVendor: "Intel(r)Crestline Graphics Chip Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 7 MB + 448 kB
Memory Range: 0xe0000000-0xe076ffff (rw)
Mode 0x0360: 768x480 (+768), 8 bits
Mode 0x0361: 768x480 (+1536), 16 bits
Mode 0x0362: 768x480 (+3072), 24 bits
Mode 0x0363: 960x600 (+960), 8 bits
Mode 0x0364: 960x600 (+1920), 16 bits
Mode 0x0365: 960x600 (+3840), 24 bits
Mode 0x0366: 1280x800 (+1280), 8 bits
Mode 0x0367: 1280x800 (+2560), 16 bits
Mode 0x0368: 1280x800 (+5120), 24 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

thinkpad:~# update-initramfs -u

This post was very helpful:

http://forums.debian.net/viewtopic.php?p=201686&sid=cc4c5c6d9573baa02f407dc1f36b587c#p201686

Per chi non lo sapesse, il BootSplash non è altro che la barra di caricamento che vediamo all’avvio di Ubuntu. Questa non fa altro che nasconderci la procedura di boot che visualizza tutto ciò che viene caricato all’avvio del sistema operativo. Nativamente su Ubuntu, è Usplash ad occuparsi di questo. Quest’ultimo è personalizzabile, ma con Splashy possiamo sbizzarrirci molto di più! E a noi piace tanto complicarci la vita per delle frivolezze simili
Splashy è sicuramente più bello e accattivante, ma Uspash resta più affidabile e sicuramente più veloce… quindi non mi senti di consigliarne la sostituzione per chi utilizza computer datati o comunque poco potenti e a chi non piace smanettare.

Allora, per chi avesse deciso di dare un tocco di originalità al BootSplash, per prima cosa procuriamoci Splashy. Quest’ultimo non lo troveremo nei repository ufficiali di Ubuntu, ma è reperibile qui. Una volta scaricata la versione adatta alla nostra architettura, procediamo col rimuovere il meta-pacchetto ubuntu-desktop. Non abbiate timore, in quanto meta-pacchetto, la sua disinstallazione non causerà problemi. Da terminale diamo quindi:

sudo apt-get remove ubuntu-desktop usplash

Come potete notare, anche Usplash è da rimuovere in quanto va in conflitto con Splashy. Alla fine del processo di rimozione, non ci resta che installare il pacchetto .deb pocanzi scaricato con gdebi cliccandoci sopra due volte. Terminata l’installazione, procediamo a crearci una copia di sicurezza del file menu.lst nel caso qualcosa vada storto:

sudo cp /boot/grub/menu.lst /boot/grub/menu.lst.old

così da poterla ripristinare in qualsiasi momento. Passiamo ora ad editare il file menu.lst col nostro editor di testo preferito (nell’esempio userò gedit in quanto uso GNOME):

sudo gedit /boot/grub/menu.lst

individuate la riga (simile a questa) “kernel /vmlinuz root=/dev/hda1 ro quiet splash” relativa al kernel in uso e aggiungetene alla fine “vga=792″. Dovremmo avere questo risultato finale (esempio):

kernel /vmlinuz root=/dev/hda1 ro quiet splash vga=792

Ora, procuriamoci qualche nuovo tema a questo indirizzo oppure direttamente su kde-look. Una volta scaricato il tema, scompattiamolo e copiamo l’intero contenuto nella cartella di Splashy in questo modo:

sudo cp -a ubuntu/ /etc/splashy/themes

e potremmo scegliere il nuovo tema da visualizzare al boot del sistema operativo.

i was pretty bored with the simple yet not-so-cool boot screen of Ubuntu (to see what i am talking about click here).i wanted to change it .now there are 2 ways to change your boot screen.

1.install usplash and start-up manager.

2.install splashy.

but i wanted to go a step further…i did not want to be dependent on other theme sites for my boot screens,i wanted to create my own.this proved to be quite a pain with usplash,so i switched to splashy.it’s so simple to create your own splash screens with splashy.splashy is a boot splash program that does not require patching the linux kernel.it’s simple and easy to use.so go ahead and install it.

here’s how:

32-bit machine – libsplashyl_0.3.10-1_i386.deb, spalshy_0.3.10-1_i386.deb (i will be placing links for 64 bit machines soon)

In the terminal, type the following command to install the splashy-themes:

sudo apt-get install splashy-themes

now we will install gsplashy which is a GUI tool to create and set your boot screens

first install the dependencies

sudo apt-get install libglade2-dev libsplashy1-dev build-essential

download gsplashy to your desktop from here.

now compile the code

cd ~/Desktop/gsplashy0.1 (change the path if you have extracted gsplashy in another location)
./configure
make
make install

that’s it.you can start gsplashy by typing in a terminal

sudo gsplashy

this will pop up a window like this:

you have to specify boot skins for resume,shutdown,boot,hibernate and suspend.the picture should be a .png format.

for progress bar specify dimensions of X:250 Y:690width=512 height=15.feel free to experiment with all dimensions.

after installing a new theme do in a terminal

sudo update-initramfs –u

also change your vga settings:

gksu gedit /boot/grub/menu.lst

add vga=792 at end of line after splash.

that’s it..enjoy the new look of your ubuntu.

THE ABOVE METHOD MAY NOT WORK FOR YOU.IF SO,DO LET ME KNOW I WILL DO EVERYTHING TO HELP YOU.

DON’T FORGET TO COMMENT ON THIS.

copy/pasted

The Hong Kong movie, In the Mood for Love has inspired hundreds of fashion shoots. I believe there are at least four other fashion editorials on this theme in this blog alone.

Here is another editorial inspired by In the Mood for Love from a new online fashion/design/culture magazine called UCE Magazine. I have to admit, the quality of the content and photogprahy are quite exceptional for an online magazine. It reads like a real paper magazine without resorting to those childish, splashy, ADD-addled contents/typography that are so prevalent in ditigal media publications today.

Model: Shitomi Gibson & Shien Lee

Editorial: Mood for Love

Magazine: UCE Magazine #2, June/July 2008

Photographer: Fillipo Vel Dita

Stylist: Shelley Zhao

Source: UCE Magazine

En el post anterior vimos como instalar Splashy, ahora vamos a ver como instalar uSplash. La diferencia entre los dos es que con uSplash no tenemos que tocar ninguna configuración ya que él lo hace todo por defecto. Para instalar tecleamos en consola:

#aptitude install usplash usplash-theme-debian

Y listo… reiniciamos el PC y vemos el resultado…

Splashy

En un post anterior explicaba como instalar Splashy. Realmente con el método anterior resultaba más engorroso  y es por eso que escribo esta segunda parte. ¿Qué es Splashy? Pues Splashy no es más que una barra de progreso que se muestra cuando iniciamos nuestro sistema Operativo. Esta barra se puede ver en distribuciones como Ubuntu, DreamLinux y demás… En Debian, cuando usted arranca el sistema lo que se muestran son lineas de texto, pero con Splashy esto puede cambiar… Para instalar seguimos los pasos básicos:

#aptitude install splashy splashy-themes

Una vez instalado lo único que tenemos que hacer es modificar el menu.lst de nuestro grub. Para ello tecleamos en consola con tu editor de texto favorito lo siguiente:

#nano /boot/grub/menu.lst

Buscamos la linea que dice ( en mi caso ):

title Debian GNU/Linux, con barra de progreso kernel 2.6.25-2-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.25-2-686 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.25-2-686
savedefault

y la ponemos asi:

title Debian GNU/Linux, con barra de progreso kernel 2.6.25-2-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.25-2-686 root=/dev/hda1 ro quiet splash vga=789
initrd /boot/initrd.img-2.6.25-2-686
savedefault

y listo, debe funcionar… Hay que tener en cuenta de que esto es con Debian Lenny…

This quest chain looks long, but is actually very short. The only real hard part is getting the ten elemental essence, and I’ll give you a quick guide on the fastest way to do that later on (no, it doesn’t require hacking the game). I beat it in about one hour, with the correct weapons, and the extremely powerful Necromancer armor, which I highly recommend using.

Warlic is so desperate to get Elemental Essence that we won't let you start this quest chain unless you give him ten.

Requirements: 10 Elemental essence
Optional Requirements:

• Ice or Water weapon (VERY important)
• Fully-Trained dragon
• Stone weapon
• Fire or Energy weapon
• Fully-Trained Necromancer Armor

Prologue
Before you do these quests, you’ll need 10 elemental essence. There are 5 ways to get them, 2 of them are good, and one of those 2 is the best. Four of the five ways are available before you beat the quest chain, so the fifth one is quite useless for now.
Anyways, these are the five ways to get them:

• Miner’s Barracks quest. This is one of Warlic’s random quests.
• A Named Elemental quest. Again, this is another one of Warlic’s random quests.
• What’s Mine is Mine quest. This is yet another one of Warlic’s random quests.
• The Letter quest. You can access this from the Other Quests menu.
• Xan’s Fortress quest*. You an access this from the Save Lymcrest! quest chain.

*This is the last required quest in the Save Lymcrest! quest chain.

Don’t do The Letter quest or the Miner’s Barracks quest if you want to get Elemental Essence fast.

The quest on the left is a no-no, the one in the middle is the absolute best, and the one on the right is pretty good.

When you get all ten Elemental Essence, speak to Warlic, click Other Quests, then Save Lymcrest. Then click on the first quest, pay the Elemental Essence, and you’re in!

The Quests:

River of Fire

• If you have a Water/Ice weapon, use it now! And if you use a pet dragon, don’t forget to change its element to Water.
• Before you fight the boss, you’ll see the Battle! button, without a heal. If you’re low on HP, (or high on HP ), go to your inventory and drink a heal before you start the fight.
• When you fight the boss, use Sleep, Zombify, Final, then Seed (Ability on the far left) in that order. Three turns after you use Seed, use Turn! The result: double or triple attack, and a 200% resistance to fire!
• Don’t worry if Sleep doesn’t work; you still have a good chance of beating him.

Fetching Fire

• Again, use the same steup as in the last quest: Necromancer, Ice/Water weapon, water dragon.
• On the second frame, you will see two lava ‘geysers.’ Avoid these, as they deal lots of damage!
• Near the end, where there is a fork (Up or Right), it doesn’t matter which way you go, as you will have to go both ways to beat the quest.
• Be sure to get the optional healing zone because there is another Bassault later on.
• You’ll get the same Bassault boss again, so use the strategy as I mentioned above.

Wind Mountain

• Stone, Stone, Stone. Use a stone weapon, and stone dragon.
• Easy quest. Just use Multi on the triple-enemies. If you’re low on health, go the the healing spot at the beginning of the quest.
• Remember in the Necropolis quest chain where Zorbak’s “sheleton” has the DOOM attack? Well, this guy is similar. Stun the Wind guard farthest to the top, alternate your attacks between the top wind guard and Huffpuff. Why did I put it in bold, you ask? Because it is VERY imporatant.
• Use Artix’s Holy Attack on Huffpuff.
• Use Final on HuffPuff
• If you haven’t killed Huffpuff in the first five turns, on the fifth turn, Use the “turn” ability (Necromancer-only) and only attack Huffpuff until he is dead.

The Pure Pool

• If you brought you Fire/Energy weapon, use it now!
• Make sure you pet dragon’s element is Fire.
• Use the optional healing area. Even though you’ll have to fight double-Monsoon Elementals, it’s definitely worth it.
• When you fight Splashy, Here are the steps: Use Sleep
• He has a 65 Immobility resistance, but it’s still worth a try.
• After that, use Seed. You won’t attack, but this is still very important. When you use Seed, count your turns from one. I’ll tell you when the effect comes in, though, so you don’t have to count the turns.
• Then use Final. After, use Zombify.
• Now, do anything you want. If you’re not using Necromancer, use an 100+ to hit attack (if you have one), but if you are using Necromancer, just attack. This is also a good time to use a health potion, if needed. Do not use turn yet.
• Now, after you did your normal attack or whatever, use Turn! The result: Summon Minion that does double or triple damage, and, you’ll use turn! All at once! This is all the effect of the Seed that you used earlier. The turn is important because, if you successfully put him to sleep, he’ll go into berserk rages, and thanks to turn it’ll do negative! Double/triple heals!

Xan’s Fortess

• Meh, no monsters or guards to the door? This is weird. Oh no, it was a trap!
• You’ll lose all of your friends when you do this, and instead, you get Warlic.
• When you come to the decision to take the Pyronomicon or not, it doesn’t matter, because if you choose the wrong one, you get to try again.
• Oh, right. use your Ice/Water weapon, and dragon.
• First monster: 3 lava globs. HAHAHA! *crackle crackle crackle* You shouldn’t have much  trouble at all. And don’t worry, you heal between battles. Just make sure you always use Warlics Ice attack when you can.
• Three inferno elementals. Use Final on one of them, put one to sleep, and poison another one. Focus on attacking the one you used with Final. If he’s dead straight after you use Final, focus on attacking the one you poisoned.
• If you’re ever low on health, use Turn.
• OOOOooooOOOhhhHHH!! Sunwarriors. Demolish them the same way as the Infernos. But there are only two! An illusion of their design makes them look like three. So put one to sleep, and use Final on one. Again, only focus on attacking the one you used Final on.
• Meh. A Bassault? What? Use the abilities above, in River of Fire.
• Well, it’s the fight you’ve all been waiting for! You Versus Warlic! When you fight Warlic, he’ll turn into a much harder, level-scaled version. Unfortunately, he has an Ice resistance, but no weakness. So use any element that he isn’t resistant to.
• Kill him like you killed Splashy (in the Pure Pool quest)
• Now, kill Xan the same way as you killed Warlic.
• Since Xan is harder to kill then Splashy, when the steps are over, use your attack over and over again until you kill him. However, do not use Turn on the third turn after Seed, unless you unsuccessfully stunned him at the beginning. But if you did stun him (which you prbably did, as he only has a 10% stun resistance) then keep using normal attacks. When you’re running low on health, that is the time to use Turn. The turn should be the key to your victory, because when the effect is over he should either be dead or one turn away from dead. If neither, make sure you followed all steps correctly.
• Remember to use health potions whenever you ned to!

The End?

• To kill the Bassualts at the beginning, use Pierce to kill them easily. and don’t forget to change your dragons element to Water.
• If the Pierce doesn’t work, you can either attack, burn, or Breath.
• Don’t forget to go back to the healing pad before fighting Xan himself.
• When you start fighting Xan, use Burn, then MegaBurn
• After that, use Pierce, then Breath. If the Pierce was unsuccessful, then use a normal attack.
• Then, use Coil, then the Burn-MegaBurn combo. After, use Breath.
• After the Breath, use Regen. This is very important. Then use coil. Although you didn’t attack for two turns in a row, you need the Regen so that you can continue using abilities, and Coil so you can keep up with your enemy’s health.
• Again, use the Burn-MegaBurn combo. After, use Pierce.
• After, keep using breath until he dies.
• Congratulations! You defeated Xan once and for all.

Rewards Shop

• Well… no tips for this quest. Just try to make the best buying decisions when buying the weapons, okay?

Shorter Link: http://wp.me/phwNB-n

Para quem anda farto de ver sempre o mesmo splash screen quando o sistema inicia existe uma aplicação que o permite modificar de uma maneira muito simples, o splashy.

O splashy é uma aplicação que corre em modo de utilizador ambientes UNIX. Com esta aplicação não existe a necessidade de aplicar patchs ao kernel, uma vez que são utilizados framebuffers para mostrar a barra de progresso e as imagens.

Antes de passarmos à instalação temos que verificar alguns requisitos

Requisitos

1. Libraria standard de C (glibc)
2. Placa gráfica (lool)
3. Kernel com suporte a framebuffers (default na globalidade das distribuições)
4. Kernel 2.6.xx.xx

NOTA – Para activar o framebuffer é necessário adicionar os argumentos “vga=791 splash” aos parâmetros do kernel no ficheiro /boot/grub/menu.lst. Estes argumentos devem ser introduzidos a seguir a

kernel /boot/vmlinuz-2.6.xx-xx-generic root=/dev/sda2 ro quiet

ficando

kernel /boot/vmlinuz-2.6.xx-xx-generic root=/dev/sda2 ro quiet vga=791 splash

Instalação do splashy

Adicionar o repositório do splashy introduzindo as seguintes linhas no fim do ficheiro /etc/apt/sources.list

## Splashy
deb http://splashy.alioth.debian.org/debian/ unstable main

Fazer o update e instalar o splashy

bu@coiso ~ $ >sudo apt-get update
bu@coiso ~ $ >sudo apt-get install splashy splashy-themes

Instalação de splash screens

Agora que o splashy já está instalado vamos instalar a tarball que contém o tema

bu@coiso ~ $ >sudo splashy_config -i <path_da_tarball>
bu@coiso ~ $ >sudo update-initramfs -u

Outra forma de instalar temas é de forma manual, para isso

1. Fazer o download da tarball
2. Extrair a tarball em /etc/splashy/themes
3. Executar no terminal
   bu@coiso ~ $ >sudo update-initramfs -u

Para escolher o tema pretendido executamos no terminal

bu@coiso ~ $ >sudo splashy_config -s <nome_do_tema>

E pronto, o tema escolhido já está disponível da próxima vez que reiniciarem o PC.

Alguns temas
Para mais informações visitar – Splashy Homepage

]]> http://witnessthis.wordpress.com/2008/07/03/guy-buttery-on-sitar/ Thu, 03 Jul 2008 23:00:59 +0000 Galen Schultz http://witnessthis.wordpress.com/2008/07/03/guy-buttery-on-sitar/ http://elavdeveloper.wordpress.com/2008/04/23/instalar-splashy/ Wed, 23 Apr 2008 22:18:00 +0000 elavdeveloper http://elavdeveloper.wordpress.com/2008/04/23/instalar-splashy/

Splashy es una aplicación que sustituye al BootSplash en Linux. La función principal de Splashy es mostrar una barra de progreso en vez del texto que normalmente se muestra en Debian y otras distribuciones de Linux. Para instalarlo debemos seguir estos sencillos pasos.

Primero que nada, debo aclarar que uso Debian Lenny y por tanto ya Splashy se encuentra en mi repositorio. De todos modos usted puede descargarlo desde esta web:

http://alioth.debian.org/frs/?group_id=30657

o simplemente agregando a /etc/apt/source.list.d esta línea:

deb splashy.alioth.debian.org/debian/ unstable main

Si usted bajó el paquete en .deb o en .rpm puede instalarlo ejecutando:

dpkg -i splashy*.deb splashy-themes*.deb ( en el caso del .deb )

rpm -Uhv splashy*.rpm splashy-themes*.rpm ( en el caso del .rpm )

Pues bien una vez descargado ejecutamos desde una consola:

# apt-get update
# apt-get install splashy

Luego de todo esto debemos de modificar el gestor de arranque que estemos usando, me voy a referir a grub porque es el que yo uso, debemos editar el menu.lst si trabajas con Grub, o lilo.conf si utilizamos LiLo. Cuando lo hayamos editado buscamos una línea que diga

# kopt=root=/dev/hda1 ro ( o donde tengan montada la raíz )

Es muy importante dejar le linea como si fuese un comentario. Una vez que localizamos esa linea al final de ella tenemos que colocar vga=791. La línea debe quedar más o menos así:

# kopt=root=/dev/hda5 ro vga=791

Muy importante: No quitar el # o sea dejar la linea como un comentario…

Ahora solo queda hacer update-grub y todo queda listo.

Importante:
- Debemos asegurarnos que cuando instalemos el Splashy se instale por dependencias el paquete libdirectfb-0.9-20 en caso de lo contrario lo instalamos nosotros mismo.

Personalización:

Si queremos cambiar la imagen solo tenemos que ir a:

/etc/splashy/themes/default/

Y poner la imagen que queramos reemplazando background.jpg. También podemos configurar el tamaño de la barra de progreso, los colores y demás con un archivo llamado config.xml.

I know there are many people who do not like the slow development process of the Debian Linux Operating System (O.S) just like me. People who use stable distribution of Debian miss on lots of new featured-rich packages as compared to users of other Linux O.S. The reason why people still stick to the stable Debian system is because of its rock-solid stability.

One of the packages that is missing from the current Debian Stable release (Etch) is “splashy“.

Here are detailed instructions which explains how to install latest Splashy package on your Etch system:

Splashy is a native Debian package, so all you need to do is to download the current sources, untar and then build a .deb package from the untarred sources.

Step 1:
Go to http://packages.debian.org/source/lenny/splashy and download the three source files namely

splashy_0.3.8-1.dsc
splashy_0.3.8.orig.tar.gz
splashy_0.3.8-1.diff.gz

into a folder say /usr/src/root/splashy_build

or you can use “wget” command also like this:

debian# wget http://ftp.us.debian.org/…/splashy…{dsc,tar.gz}

Step 2:
Give the following commands:

cd /usr/src/splashy_build
dpkg-source -x splashy*.dsc
cd splashy-VERSION (in this example, VERSION=3.8-1)
debuild -uc -us
cd ..
dpkg -i splashy*.deb libsplashy*.deb

Step 3:
Test your splashy by giving command:

debian# splashy test

You should be able to see a Tux image and a progress bar.

Step 4:
Add the following line:

splash vga=791 quiet

in your /boot/grub/menu.lst file

Your line should read something like this:

title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/hda1 ro splash vga=791 quiet
initrd /boot/initrd.img-2.6.18-4-686

This will enable the splashy to start whenever you boot your system. Without the above line your splashy simply wouldn’t work.

What if you get error messages when you boot your system or you are not able to run splashy at all?
Don’t worry chances are that you will run into Splashy error messages on Debian Etch if you are not using an initrd/initramfs image. Please refer to Issue #1 – Splashy not working; Splashy Error Messages during boot in my blog entry.

Hope this helps.

As usual, please leave a comment/feedback.

Purpose:
I have been a fan of Debian Linux operating system since last 3 years. The purpose of this post is to continuously list issues that I was able to resolve either by asking the Open Source community or by researching on the Internet or just by playing around with the problem. I hope that this post will help many people to solve similar/same issues and thus will save their valuable time.

Issue #1 – Splashy not working; Splashy Error Messages during boot
Date: 02/25/2008

Package: Splashy (Version 0.3.8-1)

OS version: Debian GNU/Linux 4.0 (codename etch)

Kernel: 2.6.24 (Debian Source)

Error Messages:
Splashy Error: Connection refused
Splashy ERROR: Couldn’t splashy_start_splashy(). Error -2
Splashy ERROR: Couldn’t splashy_start_splashy(). Error -3
Splashy ERROR: Couldn’t splashy_start_splashy(). Error -7
Cannot create /dev/fb0 or No such device

Also see this posting in which I posted my query to the splashy mailing list.

Resolution:
Rename /etc/rcS.d/S03udev to /etc/rcS.d/S03audev.

Command to be given:

debian# mv /etc/rcS.d/S03udev /etc/rcS.d/S03audev.

You can test whether splashy is working properly or not by giving the following command:

debian# splashy test

The above solution was suggested by a person named, Mike Kelland,who happens to be on the same splashy mialing list as I am.

Also some of you might be wondering how to install splashy on Debian stable (Etch) since Splashy is only available in Lenny and Sid repository as of this writing. Please see my post on how to install splashy on Debian Stable.

Update:

Ok, you must be wondering why this issue occurs in the first place, right? Why don’t the developers fix this issue?

Here is mystery:
The way splashy is supposed to work is that it should start from initramfs (which superseded initrd) in the 2.6 kernel series. What is the difference between initrd and initramfs? I think that deserves a separate post/entry (may be for some later time, eh?). Any how, if you use initramfs to boot your kernel then you should not get any error messages. Debian system by default likes to use am initramfs during boot, but many people do not prefer to use an initramfs during the boot and thus built all the support for IDE controller and Filesystems into the Kernel itself (instead of modules), just like the way I like it. This is how you make your boot process free from using initramfs.

So in short if you don’t see an “initrd” entry into your /boot/grub/menu.lst, for example:

title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/hda1 ro

instead of

title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.18-4-686

it means that you are not using initramfs and you should follow the tip mentioned in the resolution section above.

Note: It is important to know that while the menu.lst file still says “initrd”, it actually means “initramfs”. For some reasons it is still being called by this name even when they switched to newer much improved “initramfs” in 2.6 Kernel. This thing kept me confused for a long time until someone just mentioned in one of my query.

In conclusion, if you don’t use initramfs/initrd during your boot process, then udev and splashy interferes with each other and you have to make sure that splashy is being called after udev script in the /etc/rcS.d directory. The only disadvantage is that you might end up seeing some text messages before splashy actually loads itself.

Also, I had a discussion with one of the splashy developer/maintainer regarding this issue which might give you further insight.

Issue #2

Coming soon…

As usual, please leave a comment/feedback.