update/upgrade slackware distro through slackpkg utility

today, i will give a post on how to keep your slackware distro up to date quickly to the latest patches (bugs, security fixes if any) released for the distro the really quick way with slackpkg utility ( default in the distro if you have installed the full installation)….

1. open up /etc/slackpkg/mirrors with your fav text editor
vi /etc/slackpkg/mirrors

2. uncomment the mirror for your distro version or if you want the bleeding edge uncomment a link for slackware-current (note, this is not the stable releases but cutting edge developer’s build…where you have to tinker with issues and fix them if any./…dont uncommnet for production environments…not recommended thoughstill stable…yes i can assure you on that cos its current thats running for me and i feel at home for now with it too)

3. once done, save changes and close the file or exit vi…

4. now, run these four commands one by one….

i. slackpkg update gpg
ii. skackpkg update
iii. slackpkg install-new
iv. slackpkg upgrade-all

5. you can do system clean up after this to ensure no orphan files are present…

well, for now you should check for files with *.new extensions in your system….they are new configuration files that are from your updates for your applications and libraries….

the new files come into existence if you have made any changes to the old configuration files of those respective libraries….in such a case, slackware lets you have keep those old files while an update gives you the new configuration files in .new format so that you can see the difference between them and apply the changes as you wish….

eg: /etc/wpa_supplicant.conf usually have changes for your wireless connection or wifi you added like your essid and password….you get a wpa_supplicant.conf.new on an update so that you can check the diff and apply them…

i recommend going through each new files to see the changes and then remove old configs….

and now you get a brand new slackware( well, basically means you up to date with your times! )

keep slacking!!!

a distro you can tweak to how you want( and most importantly you are in full control)


rooting your android phone – a primer for beginners

i know it’s been a long time since i have penned down some thoughts…

the latest post i have got for you is all related to mobile rooting (hacking into your mobile device for more power)

a brief on rooting:

Mobile phones available in the market comes with a stock android (a term referred to android that comes pre-built in our mobile devices) that’s ready to use.

But the major caveat in this is that the system files are locked and we don’t have full access to the device. It’s like a locked device to me and one that is waiting to be explored.

Rooting is used to specify the action where we grant root access (similar to the super user or administrator in linux ) to the user, so that we can access the locked android files too and add more of our own.

Why do we need rooting?

if you google there are plenty of pages with pros and cons of rooting.

Major cons :

  • rooting voids any company warranty left on your device…in simple terms, you cannot take it to an authorized service center after rooting
  • workaround: unroot the device before you take it to the service center. Do a full unroot and they cannot trace if you had rooted the phone before.
  • chance of bricking the device (in rooting world that’s also known as damaging the device due to a corrupted file or hardware part thus rendering it useless) while performing the rooting
  • Now, to the brighter side (pros of rooting):

  • Giving more power to the user
  • Customization of phone right from tweaking hardware and additional softwares to changing the UI (user-interface)
  • Remove limitations of stock android to access system files
  • Customize, customize and more customizations
  • The last line is the only line needed to confirm us to make the switch from an un-rooted device to a rooted device.

    Rooting of mobile phones has come a long way and it is way more reliable than before but yes you got to be warned beforehand as precaution:

    Any firmware or executable on one phone might not necessarily work on your phone.

    Check your phone model, android version and firmware installed to proceed.
    To root your phone, all you need to do is google your phone model, android version and also firmware version to be just super sure to know you got the right tools to proceed.

    The tutorials or step by step procedure for the rooting procedure is all that is needed to perform a successful rooting.

    I rooted my asus zenfone 5 using the below working link:

    hack(root) into my asus zenfone 5

    kindly be warned that I am not responsible for you bricking your device. Not to worry folks, I think this has a success rate of 100% as compared to others. I tried a lot of them and yes could have bricked my device too trying them out.

    What I did after rooting?

    · Used device control (an app for rooted phones available from google play store) to overclock my cpu from 1.3 ghertz to 1.6 ghertz

    · Expand your ram using your physical memory that’s external card memory if any

    · Protect your apps using greenify which monitors apps and puts them to sleep as desired.

    · Gamers, can have a rich hd feel experience playing heavy games, (games that are a load on your phone before rooting it) like N.O.V.A. 3, tegra etc

    · A host of other apps waiting to be tried out if you have rooted your phone.
    . Xposed Framework for customizations to front end,flash your custom ROM ( more like a themer right from kernel to your front end), and a whole lot of tuner apps to check into.

    my view on rooting?
    you give power to yourself and life to your phone once you root it….you can turn any low cost android mobile handset and root it…

    ofcourse you can jailbreak your iphone too….
    do it to have freedom!
    a small last note to remember:
    if you find you lose root access after OTA (over the air) update of your android, you will have to root again…..thats all…just repeat the process in the link…..

    fluxbox – sticky wonder

    i loved fluxbox when i first installed it….
    low on resources pretty neat to look at….
    here is the sticky think i found…thought to share here too…

    basically it lets any application of your wish to stay on top….

    if you right click anytime on application taskbar and check the sticky option for the application then any application say firefox for instance stays across workspaces....so that when you switch to a terminal say in another workspace you still have this firefox as a side tab along with the other existing tabs you had in it as well....

    no cut of flow also….its way too cool….
    thats from the front end….

    cli mode:
    there is a directory in the home directory of current user namely fluxbox hidden so its .fluxbox....browse the files in it you'd be amazed at the options available....
    well the file in concern for us is the apps file which has application window settings saved across sessions....
    open the file and add this piece of line to make sticky stick
    [app] (name=firefox)
    [Sticky] {yes}

    i think for low memory footprint and decent usage fluxbox, a fork of blackbox is a nice window manager to have…..

    setting wallpaper in my fluxbox window manager

    simply executing the below command will set your wallpaper immediately but caution you wont have it when you re-login again:

    fbsetbg -f /path/to/wallpaper/thatsmywpbaby.jpg

    making it stick so that you have your wallpaper on every login:

    well yes the right click choose wp and yes i have it option not present here….
     not to be disappointed….just setting a couple of lines and you are good to go…
    now open a favorite text editor in console and open the init file present in .fluxbox in the user’s home directory with write permission….

    # nano /home/username/.fluxbox/init

    add this line to it….

    session.screen0.rootCommand: fbsetbg -l

    fbsetbg -l means to set the last wallpaper

    you can close this file now safely writing the changes to it…..now we go to add a line to one more file and we are done….
    you must have guessed it…there is the last wallpaper file in there too….open it up now and set the file you wish to as your wallpaper….

    # nano /home/username/.fluxbox/lastwallpaper

    if it doesnt exist make a new file with the same name as mentioned i.e. lastwallpaper….
    then add the below line to it….

    fbsetbg -f /path/to/wallpaper/thatsmywpbaby.jpg

    logout and login and you are done…

    you can do a man fbsetbg for more info from the man pages….
    -f option for fullscreen i.e. use the full screen for the wallpaper about to be set….

    happy slacking!!!

    wi-fi configuration in slackware

    for wireless configuration stay secure stay alert….quoting from slackdocs as is:

    if you need to secure your wireless network traffic, WPA2 should be considered the minimum level of protection required

    well i just got my wifi configured and thought i would note and also could share the same
    you can do it from either of the slackware turoials in slackdocs or arch tutorial…..i had earlier written the configuration based on my reading in arch linux tutorial and its time to move it below and give way for the slackware approach which makes it stick across sessions…..first system on boot defaults to check for a wired connection if it exists else then will try to check for the wireless…..

    way one: slackware tutorial for wifi
    the original article is found here…..

    below is the configuration for the more newer and updated wpa2 configuration….
    you can find the configuration for the older form of encryption(wep or wpa) too in the slack docs on the same page……

    iwconfig is the command used to configure but it would not automatically configure the wireless network with wpa2 encryption…..you need a helper daemon namely, wpa_supplicant
    for the same…

    we have to edit just two files again for the same….then you reboot to get the changes applied…

    1. edit /etc/wpa_supplicant.conf file

    # /etc/wpa_supplicant.conf
    # ========================
    # This line enables the use of wpa_cli which is used by rc.wireless
    # if possible (to check for successful association)
    # By default, only root (group 0) may use wpa_cli

    # WPA protected network, supply your own ESSID and WPAPSK here:
    psk=”secret passphrase”

    2. next we edit one more file namely, /etc/rc.d/rc.inet1.conf
    rc.inet1.conf is a very powerful file….you list all your necessary wired and wireless connections you want to manage in this file….

    # rc.inet1.conf (excert)
    # ======================
    ## Example config information for wlan0. Uncomment the lines you need and fill
    ## in your info. (You may not need all of these for your wireless network)
    WLAN_ESSID[4]="nest" //replace nest with your wireless network name or essid of the wifi router
    #WLAN_RATE[4]="54M auto"
    #WLAN_IWPRIV[4]="set AuthMode=WPAPSK | \
    # set EncrypType=TKIP | \
    # set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"

    you are done…..

    reboot your system and slackware will attempt to configure your wireless as yours is all setup and running….


    another option apart from rebooting your system is to run the following command

    /etc/rc.d/rc.inet1 wlan0_restart

    below is an earlier post of mine and i edited to add the above part you just read…i was having minor issues with the below solution…it work sin the session in which we do it and some more restarts….after that it just fails…above one is a sureshot!

    way two: archlinux tutorial (caution though: doesnt stick well across sessions….)

    below is the link if u want to click right away…..


    if you still here below are the core steps to follow:

    1. check your wireless device(s) is connected or not and is been identified by the system

    # iw dev

    2. now bring it up

    # ip link set wlan0 up

    3. to verify its up enter the following command

    # ip link show wlan0

    from the output.,
    The UP in is what indicates the interface is up, not the later state DOWN.
    4.next scan for available wireless networks

    # iw dev wlp3s0 scan | grep SSID

    5. connect to a network now with the SSID listed or you think is yours…

    # wpa_supplicant -B -i wlan0 -c <(wpa_passphrase "ssid" "psk")

    now for the above quotes yes SSSID is your wireless network identifier name
    and psk is the password for the same….
    check behind the box for a NETGEAR wi-fi router( i.e. again if you havent changed the password since you bought the router) and i think it should be the same with others…more or less the same….check with the vendor…..

    6. finally, assign an ip address to it…it can be set manually or automatically through dhcpd….

    # dhcpcd wlan0

    these are the only 6 simple steps you need to get your wifi up and running in slackware…..
    now, try browsing your browser without your wired network card….

    if it fails try the below steps….

    # echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf
    # wpa_passphrase "ssid" "psk" >> /etc/wpa_supplicant.conf
    # ip link set interface up
    # wpa_supplicant -B -D nl80211,wext -c /etc/wpa_supplicant.conf -i interface
    # dhcpcd -A interface

    so thats it from me for now….
    till next post happy slacking to you all too!!!

    free cache memory and system cache

    simply execute this command

    free && sync && echo 3 > /proc/sys/vm/dump_caches && free

    *more info on sync

    info coreutils ‘sync invocation’



    happy slacking…

    tinkering with freeBSD and its cool…helps to learn with another GUI with it…freeBSD 9.1 ix86 in vmware in slackware….

    slackware no file or directory while trying to run an application that is installed


    i have installed a new application or package say skype and all the related dependencies for it..then i try to run skype and i get

    /usr/bin/skype : no such file or directory

    when you navigate to your /usr/bin directory you see a file there with name skype and so now you are confused….file is listed there in the directory but error says no such file or directory…


    well to detail the issue out if the file exists then it is the issue where you run a slackware 64bit os and the file requested is trying to run some file compatible in the 32bit file systems….

    alien BOB a trusted contributor to slackware and slackbuilds for years has the resolution in the link below….


    i quote here again what he has quoted to make it clearer

    the multilib-enabled Slackware64 can compile 32bit binaries,
    if you add the right software to it

    so what we do here is actually making our slackware64 which is mltilib ready to start interacting with multiple libraries…..

    happy slacking!!!