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}
[end]

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

Advertisements

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
here….
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)
ctrl_interface=/var/run/wpa_supplicant
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=0

# WPA protected network, supply your own ESSID and WPAPSK here:
network={
scan_ssid=1
ssid=”nest”
key_mgmt=WPA-PSK
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)
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[4]="nest" //replace nest with your wireless network name or essid of the wifi router
#WLAN_MODE[4]=Managed
#WLAN_RATE[4]="54M auto"
#WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | \
# set EncrypType=TKIP | \
# set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

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…..

https://wiki.archlinux.org/index.php/beginners%27_guide#Wireless

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!!!