Trash plug-in for SpaceFM

For people who like to use a trash can in their file manager: there is a (Corbeille=) Trash plug-in developed for Spacefm:
Download it here.
Install it by opening Spacefm and going to Plugin section, install file, go to download folder and file and give root password.

Usage

Corbeille-SpaceFM consists of 9 commands (available in the SpaceFM menu Plugins | Trash if installed with root protection). Note that there's no command confirmation dialog before proceeding to the selected action.

    Move to Trash: you must select at least one file outside the trash directory to have this command enabled. Selected files will be moved to the trash.

    The keyboard shortcut Shift+Delete moves to the trash the selected files.

    Restore: you must select at least one file in the trash directory to have this command enabled. Selected files will be moved to their original location. If the original location already exists, the file won't be moved and an error will be displayed.

    Delete Permanently: you must select at least one file in the trash directory to have this command enabled. Selected files will be deleted permanently, so they will no longer be recoverable in the trash.

    Go to Trash: this command is always enabled. It will open the trash directory in a new tab in the current SpaceFM window. Also, if top directory trashes are detected (for example, a trash in a removable device), they will be open each in a new tab.

    Display Properties: this command is always enabled. It will open a pop-up dialog displaying the number of files in the trash and the total size of the trash.

    Empty Trash: this command is always enabled. It's just a convenient way to delete permanently all files in the trash. You can get the same result by selecting all files in the trash and choose to delete them permanently.

    Limit the Size of the Trash: this command is always enabled. It allows to reduce the trash to a given size. The files are deleted in ascending order of date of trashing (older trashed files are deleted first).

    Delete Old Files: this command is always enabled. It allows to delete files moved to the trash for a given number of days.

    Delete Big Files: this command is always enabled. It allows to delete files moved to the trash and whose size is greater than or equal to a given size.

More info on the plug-in: http://www.jpfleury.net/en/software/corbeille-spacefm.php

fortune zippy

Yow!  Now I get to think about all the BAD THINGS I did to a BOWLING BALL when I was in JUNIOR HIGH SCHOOL!

OK, I  admitted it; Zippy the Pinhead is my only guru.
Gotta get your guru, guru (Eric).
So install
pacman -S fortune-mod
and ask the WISE MAN, our oraclae for your instant enlightenment.
And type once: fortune zippy
and contemplate and then arrow up and enter and contemplate and arrow up, enter and comntemplate and so on, ad infinitum.

Toes, knees, NIPPLES.  Toes, knees, nipples, KNUCKLES ...
Nipples, dimples, knuckles, NICKLES, wrinkles, pimples!!

Could we understand that life is meaningless and life is beautiful at the same head moment.

 I have a TINY BOWL in my HEAD

Opening Firefox maximized using rc.xml

Just add some lines to the application section in your /home/user/.config/rc.xml file; it is at the end of the file.
For code look here. post18.

LVM logical volume manager

This post raised my interest in knowing more about LVM.

The whole concept of partitioning is changed to another level, with different keywords and rules. What is important of LVM is its flexibility that it provides to the user.

From the Arch Wiki:

With LVM you can more easily handle your partitions (logical volumes) than normal hard drive partitions. For example, you can:

• Use any number of disks as one big disk(VG)
• Have partitions(LV) stretched over several disks (they can be as big as all of your disk storage together)
• Resize/create/delete partitions(LV) and disks(VG) as you like (it does not depend on position of the logical volumes within volume groups as with normal partitions)
• Resize/create/delete partitions(LV) and disks(VG) online (filesystems on them still need to be resized, but some support online resizing)
• Name your disks(VG) and partitions(LV) as you like
• Create small partitions(LV) and resize them "dynamically" as they get more filled (growing must be still done by hand, but you can do it online with some filesystems)

So this is a very interesting offering.
Also taking snapshots of your system can be done in a much more space efficient way. The obvious disadvantage that it makes things more complex. If you want grub legacy you need to make a separate /boot partition as it cannot read from LVM volumes. And:

When choosing mountpoints, just select your newly created logical volumes (use: /dev/mapper/Volgroup00-lvolhome).
Do NOT select the actual partitions on which logical volumes were created (do not use: /dev/sda2). 

Details on the necessary configuration you can read on the wiki page. But it is definitely good to know what LVM has to offer because it offers solutions in all kind of situations and scenarios.

Openbox resources are already mentioned before.
Today I found an old list on the Crunchbang forums.
This one is a classic: the Urukrama guide.
What I notice in a lot of descriptions of Openbox (an example) of new users of it, that its true power, the extensive use of the keybindings is not realy discovered and exploited; the true productivity power of Openbox is negated because most Windows educated pc users  are people, that are disabled by the crippling mouse use they are accustomed to. They even don't realize they have to unlearn certain bad habits to become an real openbox power user.

You leave out the best part of Openbox.
What you forgot to mention is the most important way to start programs in openbox; it is with keybindings that you define in one rather simple rc.xml file.
For instance Super+w start webbrowser; Super+t starts terminal etc.
I also use keybindings to manipulate my windows:http://stillstup.blogspot.com/2010/06/keybindings-to-manipulate-windows.html
Dmenu is my second program starter; its advantage compared to gmrun is that you get a list with all the installed programs and if you don’t know the name exactly you can select it from the list.
This all together makes you super productive as you don’t have to use your mouse anymore like before. Not only will that reduce RSI risk but you will notice how disabling the mouse use is compared to keyboard driven pc use.

Grub error 17 and 15 after installation Arch

I installed the March Archbang iso today on a old pc and all went very well regarding Archbang but there were two grub errors, first error 17.
I was replacing an older Arch installation that I hadn't updated in more then a year but functioned flawlessly. The grub error 17 was a result of a changed partition table.
How to fix that is clearly described here .
But after doing that my problems weren't over.

The only change was that error 17 was now replaced by error 15.

The renaming of the booting items issue led to numerous grub 15 questions on the Arch forums: Solution

Modify /boot/grub/menu.lst so vmlinuz26 is vmlinuz-linux, kernel26.img is initramfs-linux.img and kernel26-fallback.img is initramfs-linux-fallback.img

But his was also not the problem;
I changed two aspects of my /boot/grub/menu.lst.
The reason this sort of problems is difficult to solve is that there are so many scenarios people use regarding making a dedicated booting partition or not, how the root folder is designated in /etc/fstab.
Anyway in etc/fstab my root partition was designated by the UUid that you can find by typing in the terminal
blkid.
Changing
kernel /boot/vmlinuz-linux root=/dev/sda6 ro
to
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/xxx6840d-8769-41f4-xxxxxx ro

was one part of the solution. If in the fstab /dev/sda6 was mentioned I would have had to change the menu.lst to sda6; what I conclude is that naming should be identical in fstab and menu.lst.

Second issue
Use an absolute path to vmlinuz and initramfs.img

The fact that I don't use a separate boot partition means I had to change the default

kernel /vmlinuz-linux root=/dev/disk/by-uuid/xxx ro
initrd /initramfs-linux.img

to

kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/xxx ro
initrd /boot/initramfs-linux.img

There are a lot more reasons why you can get the error 15; forgetting to add the "ro" at the back of the line for example, but maybe somebody can use this solution.

Don't use packer for installing non-AUR packages

The problem is the breakage that can develop between fully updated Arch repositories and the mostly much slower reacting AUR packages.
So for your own good it is useful to get aware what is from AUR and not
And not mixing the two in your mind as if they are packages of equal quality.
You should go for the official package unless you have strong reasons to use an AUR package and be critical to use elementary packages like kernel builds from AUR sources.
Always install an official, non-AUR package with pacman and consider a system update always when installing a package.
When thinking about installing an important or bigger new package always be conscious of what dependencies it has and consider if it is not a good moment to update first with
pacman -Syyu
(and not packer -Syyu!!) and then install your new package with pacman.
Remember that if you are curious and only do pacman -Syy, it is risky to install only a package and not do a total system upgrade as that might lead to mixing different dependencies that are not in sync ( the update of one package also needs the update of another package).
Start using your system and when everything is OK after a reboot, only then do packer -Su.
At least this is the way I manage to avoid breakage on my system for already a rather long time.