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 de/wm back to the rather humble jwm. and i'm quite pleasantly surprised. jwm replaces my current openbox + tint2 setup quite well, perhaps even better.. more efficient, quicker, smaller, faster, simpler and very customisable. jwm gives me everything i use in openbox and tint2 combined. i think this is the end of my openbox saga.
kernel compile debian way
1. prepare your system
verify you have sufficient diskspace. about 1g or so.
you do not need root. normal user can compile.
you do not need to compile on your own system. another system, with faster cpu, more memory, spare demand, etc can compile your kernel.
verify you have sufficient diskspace. about 1g or so.
you do not need root. normal user can compile.
you do not need to compile on your own system. another system, with faster cpu, more memory, spare demand, etc can compile your kernel.
using tmpfs
i find my ram usage doesn't go much over 512k. apart from some of my trusty older friends, most of my systems have ample ram left over. how do i make more efficient usage of extra ram?
ram is fast. disk is slow. move more operations from disk to ram, depending on how ram is spare.
ram is fast. disk is slow. move more operations from disk to ram, depending on how ram is spare.
most viewed
-
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 fr...
-
I have just discovered zram [2] :) woohoo... and what a thing that is! I was so sold on tmpfs , that I used it for everything I possibly ...
-
you won't see many docs about minimal netinstall slackware. indeed, you will see many experts saying there is no such thing. and your on...
-
debian kernels contain everything needed by everyone. customising your kernel is easy and highly recommended. i recommend using the same ker...
-
I decided to have another go at runit , this time on my gentoo . I had been thinking about this, since I noticed this on
-
this idea has been knocking around in my head for a while. i want to document it, while it is still there and to flush it out later.. i us...
-
vision: portable internet router, to carry on my travels, or use at home. openwrt on a portable (thin-client/netbook) device. internet sour...
-
I have no sound, on my recent gentoo install. LXQT Mixer wouldn't open. I don't even get any error/warning messages. This is not ...
-
ref: http://wiki.gentoo.org/wiki/portage Gentoo is Portage. Portage is Gentoo. Getting portage settings right is vitally important. It...
-
I noticed while updating my void that kernels were being updated, but old ones weren't being removed. Removing orphan packages didn'...