html code snippets

use <code>...</code> for inline code snippets
use <pre>...</pre> for block code snippets

debian stretch kernel compile

debian kernels contain everything needed by everyone. customising your kernel is easy and highly recommended. i recommend using the same kernel version/source, to comply with debian security/updates.

ubuntu phone touch emulator

disappointed with android bloatware getting worse, incompatible releases, and an unstable roadmap, i am seriously considering a proper linux mobile device.

wpa_gui

how did i not discover this earlier :? such an efficient tool! no loitering binary/cryptic config files all over the system, or bloatware dependencies like networkmanager.

NetworkManager (again) and Xubuntu

I now recommend Xfce to n00bs yet undecided on exactly which WindowManager they need.
NetworkManager seems to be very temperamental, if you do use that Gnome bloatware!

grub rescue btrfs ubuntu

to play more seriously with yet another distro, i needed to install it. so i had some fun resizing/moving partitions around to clear some freespace for a new partition. during this, the partition numbering changed. i couldn't boot ubuntu's btrfs partition. i didn't understand why, till i discovered that partition numbers are hardcoded into the grub boot record.. even though grub cfg contains only labels or uuids. tsk tsk! yet another reason why i seem to be going off grub2.

slackware netinstall

you won't see many docs about minimal netinstall slackware. indeed, you will see many experts saying there is no such thing. and your only option is to download the entire lot. sad, i know!

the official slackware recommendation is to install everything, even if you want a minimal system, and then uninstall what you don't want. the recommendation is to download the install dvd(?) or a few cds. there are no docs (or i couldn't find any) for netinstall.

slackware can be installed over the network without downloading that humunguous recommended dvd. not everyone wants gnome, kde, etc. netinst is most efficient, particularly if you need a minimal install and know what you want.

if you don't have a dvd-drive to boot, then you are not left with much choice. you also need to consider, if bandwidth is an issue. do you need to download that whole dvd content, if you are only installing a minimal system?

however, if you are a slackware newbie, you might install multiple times before you get it right. in that case, a one-time download might be more efficient. still, unless one is installing all the bells n whistles, an entire dvd is still is a bit ott!

slackware netinstall

choose a nearby mirror from http://mirrors.slackware.com/mirrorlist/
ps: the main mirrors - slackware.org | slackware.org.uk - are throttled and may ban you, if you connect multiple times. so choose another mirror.

on your chosen mirror, navigate directories to /slackware-current/usb-and-pxe-installers/

download usbboot.img

read README_USB.TXT
ignore everything it says, except the how-to create usb bootable slackware installer and do so.

boot from this usb, and start setup.

when asked to choose your install source media, select "4 Install from FTP/HTTP server"



server is your mirror from above. for eg, http://slackware.org.uk

location is the directory containing PACKAGES.TXT. for eg, /slackware/slackware-current/slackware/

that's it!

extlinux (syslinux) debian style

my path away from grub2 took me via lilo to extlinux. i stayed with lilo for a while. syslinux was on my mind, but for something rather trivial/straightforward i couldn't crack. i finally got my head around it, and my usb sticks were the first ones to get it.

next stop was debian on my laptop, which has just been converted. the below steps are for debian systems only. if you want a how-to for other systems, let me know.

debian no systemd

debian testing jessie was steam rolling in to stable with talks of this oh-so-wonderful systemd. it all sounded so good.. then i wanted a preview at the internals of systemd, and took arch for a spin. and o boy, what a spin that was.. for my poor head! that was when i decided not to let that garbageware into my stables. it never was (and still isn't) stable, is it? this long love affair with debian, seems to be coming to an end with this episode!

systemd - the shameful episode in debian annals - forcing the debian tc (technical committee) to make a dodgy decision without giving them proper choices or time - three of the five tc resign soon after, and the debian founder allegedly commits suicide after having received death-threats! wonder who's pulling the debian strings??

lilo

grub2 has become bloatware afaiac, and i'd been meaning to move away for a while. i just didn't have the time, patience, and redundancy on my systems.

if you've been following me, you might have noticed that i like to trash bloatware. i'm always seeking smaller packages, and removing bigger ones. bloatwares are not just unnecessary resource hogs, but security concerns (malware?) too. bigger the code base, the easier it is to hide malware traits.

jwm

i seem to have come full circle, through quite a lot of wm/de back to the rather humble jwm. and i'm quite pleasantly surprised. jwm replaces my current openbox/tint2 setup quite well, and perhaps even better.. more efficient, smaller, faster, simpler and very customisable. i think this is the end of my openbox saga.

i installed jwm, and themed it to look & feel almost exactly the same as my crunchbang waldorf with openbox/tint2. it took a lot less effort. and it uses quite a lot less of resources too. purging that redundant lot reclaimed some resources too. all on the journey towards reclaiming resources from bloatwares, and all those big-is-beautiful fanatics!

the only reason we seem to need to buy bigger/faster hardware is just to keep up with bigger/slower software. in the end, you still end up with about the same memory, and processing power leftover to do what you actually procured a computer for. more efficient/smaller systems which can perform the same/better is what i expect on a development lifecycle of things getting better. i should be able to use the same old hardware much better with newer software, or i'm moving backwards. can you think back about a decade, and check whether your computer was faster than now?

i for one will continue on my quest. i don't have a need to show-off, or prove to anyone else. i'm happy using older hardware, and my systems are much quicker/faster than my neighbour's latest toy. guess i should re-title this post!?

to get back on topic. this one single simple file is a replacement for quite a few complicated (directories of) config files littered in various directories all over the filesystem. compared to all those various openbox/related config files, this is so beautiful.

vi ~/.jwmrc





sylpheed

iceweasel -private
iceweasel

lxterminal -e tmuxj
leafpad


lxterminal -e plink -v -ssh localhost
virtualbox
transmission-qt
xcalc
skype --disable-api
sigil

/etc/jwm/debian-menu


leafpad ~/.profile
leafpad ~/.xinitrc
lxappearance
sudo shutdown -r -t5 now
sudo shutdown -h -t5 now


leafpad ~/.jwmrc






root:1
showdesktop



xload -nolabel -bg black -fg gray70 -hl yellow


gsimplecal



Conky








Lxterminal





Iceweasel





Sylpheed




Sans-8
1

gray80
black:gray20
gray20


gray50
black:gray10
gray10




Sans-10
black
gray80
0.1






gray70
black
grey80
gray20



none
gray20
gray10
gray30
black
gray50



Sans-9
gray80
gray10
black
gray70:gray50



Sans-8
gray20
yellow
black





up
down
right
left
left
down
up
right
select
escape

close
maximize

desktop#
showdesktop
next
prev
nextstacked
prevstacked

root:1
root:1
window

exec:lxterminal -e alsamixer
exec:amixer set Master 0
exec:amixer set Master 5%+
exec:amixer set Master 5%-

exec:gmrun
exec:dmenu_run -i -nb black -nf gray
exec:xkill
exec:lxterminal -e htop

exec:firefox
exec:firefox -private-window
exec:sylpheed
exec:lxterminal -e bash
exec:lxterminal -e tmuxj
exec:thunar
exec:geany
exec:leafpad
exec:lxterminal -e alsamixer

exec:jwm -restart
exec:jwm -exit

exec:sudo shutdown -r -t 5 now
exec:sudo shutdown -h -t 5 now



that doesn't show correctly on here! any tips on how to embed some code snippets on this blog?

most viewed