An old cowpoke went riding out onme dark and windy day
Upon a ridge he rested as he went along his way
When all at once a mighty herd of red eyed cows he saw
A’plowing through the ragged skies and up the cloudy draw
Yippee-yi-yay-yippee-yi-yoh the ghost herd in the sky
Their horns were black and shiny and their hooves were made of steel
Their brands were still on fire and their hot breath he could feel
A bolt of fear shot through him as they thunder through the sky
For he saw the riders coming hard and he heard their mornful cry
Yippee-yi-yay-yippee-yi-yoh the ghost riders in the sky
Their faces gaunt their eyes were blurred their shirts all soaked with sweat
He’s riding hard to catch that herd but he ain’t caught them yet
‘Cause they’ve got to ride forever on that range up in the sky
On horses snorting fire as they ride on hear their cry
Yippee-yi-yay-yippee-yi-yoh the ghost riders in the sky
As the riders loped on my him he heard one call his name
If you want to save your soul from hell a-riding on our range
Then cowboy change your ways today or with us you will ride
Trying to catch the devil’s herd across these endless skies
Yippee-yi-yay-yippee-yi-yoh the ghost riders in the sky
Yippee-yi-yay-yippee-yi-yoh the ghost riders in the sky

— Ghost Riders in the Sky

What an odd thing to catch on TV, lol.

todo: 2008-11-23

finish nail config
finish changes to vimrc -> commit
check in my vim colour scheme
adopt colour scheme to gvim (which I use on winsucks) or find something comparable
update lj abut 2008-11-22
congratulation the new recruit
hash out keybinds for swat
check, if I currently have any in rvs lol
contemplate what we can do with the traditional tagfile format, and our old friends perl/python (muhauha)
dig through about 300 e-mails

*yawns a mile wide*

Linux distro family tree

http://kde-files.org/CONTENT/content-files/46315-linux_timeline_poster_v1.1.png

Special thanks to MetaCosm of #vim

Never knew suse was descended from good ol’slackware hehe.

Hmm, mission orders in troff?

You know, it would be interesting to write up my various tasking orders in troff, then generate the desired outputs.

That, or actually find the time to make a proper LaTeX document class and expand my personal style package… to cope with it lol. But troff would be faster.

Determined exhaustion

Very tired atm… but not wiling to give up yet!

For the past week, I’ve been going to bed > 0500R, past 3~4 days worth I’ve barely had any sleep at night… When trying to sleep, it’s more like time has passed with limited consciousness then ever actually sleeping, last night was the first dreaming I’ve dne in a awhile now. I’m hoping, with the weekend… I can stop going to bed so late, or at least sleep in for a change lol. I prefer 8 hours, but often live on <=5 :.
Been playing a bit of SWAT 4 lately, good to finally have some R&R. Spent a part of yesterday teaching a green player the ropes of the server, hopefully enough that they will survive working in an element, and be able to learn more with practice if desired. COT finally made Recruit, hopefully with a bright future. With Dukes help, I’m also getting ready to reintroduce keybinds into my mixture. I should still have my ‘English — Deutsch’ style keybinds backed up somewhere, but have been gaming without any textual keybinds since I reformatted sal1600. My controls are quite customized, and I am using the classic command interface for months, so the main problem is where to put things now lol.

sigh, already nearing midnight.

Hmm, arguably I have my bad days, and then I have my worse days…

Tomorrow can’t get much worse in terms of work, I hope : Nearly 0500R, so no time for a proper days log; I really need to stop staying up so late.

At the moment, I’ve nearly got nail configured to my needs. The addition of macros and IMAP support is a real improvement over the old Berkeley Mail program. With a little more adjusting, I just might be able to dig into my back-log of mail sometime lol. So far, I only have one major complaint – no line editing at the prompt beyond the most basic level (provided by the terminal). That’ not really a problem though, it allows that old ed like terseness, it’s easy to keep the commands short.

Software, like physical tools should empower users to get work done efficiently, A little bit of learning how to use the program, is worth it when the reward is productive.

One thing I’ve also come to enjoy, is a useful trick for generating HTML manual pages. The mail/heirloom-mailx port installs as /usr/local/bin/mailx on FreeBSD, corresponding manual page being /usr/local/man/man1/mailx.1.gz. Because nail has a big manual page, it’s worth while to use a web browser or a text editor with tabs, in place of the usual $PAGER used by man.

$ zcat /usr/local/man/man1/mailx.1.gz | groff -Thtml -man > ~/mail.1.html
$ firefox3 ~/mail.1.html &

which is much more fun then my shell alias:

alias   man-nail="man -M /usr/local/man mailx"

PC-BSD, 3 years of PBI corruption continues!

Username: mrhbit

Hi@

This is available in FreeBSD ports.

Here some screenshots.

http://www.ultimatestunts.nl/index.php?page=1&lang=en

regards Soeren

Username: mrhbit

Or a package for PC-BSD 7.x ?

Username: Gon

have done it. Gimme a week and i will approve it into pbidir.com

_________________
Gonzalo Martínez-Sanjuan Sánchez
PC-BSD Core Team Member

Problems with this:

  1. Getting a PBI approved is supposed to involve community testing, and review by those in charge of our PBI’safety (e.g. Gonzalo and a few others on the team page), which should also be impartial auditors – it’s called common sense.
  2. This would make Gonzalo a repeat offender in by-passing the normal approval procedures for his own PBIs, if he does what he says he will do.
  3. If he does as his record and choice of words suggests, this is a conflict of interest, which I deem unethical.
  4. This is not the first time. someone involved in the PC-BSD project has “bent” the PBIDir rules, or endorsed doing so… when they are supposed to be enforcing them, for everyone including themselves!
  5. In the past a number of PBI’s that have “skipped approval”, and have resulted in stinging users or violating the rules of the day (ref: Kris (Realplayer, Java, BSD4Win), Charles (Firefox, Thunderbird), Gonzalo (Gnome, …)), or just had half assed [lack of] testing that didn’t catch obvious problems (ref: the 2nd Amarok PBI, Gnome 2). Considering the state of Documentation (how many general users know how to extract PBI w/o install, or how to reach the scripts before they are run), users will not see the code executed when they install a PBI (and most woulnd’t understand it, or the implications), which IMHO is a major security risk — unaudited PBI.

Is it a wonder, that I never send patches to these people… I wouldn’t want my name associated with PC-BSD in any such capacity, period and end of quote. I remember I once compiled a list of the PC-BSD projects deficiencies, and took it up with one of the team members…. That was quite a while ago now; but no actual changes seem to have occured, beyond referencing revisions in the changelog for 7.0.1.

I think, if Gonzalo doesn’t go by the book, maybe I will just happen to go public with them this time — and expand the list!

I’ve had about enough of watching this chicken shit project. I may have mellowed in my increasing age, but not that far just yet.

Miscellaneous ponderings

/bin/ed isn’t so bad after all, but hey… knowing how to use ex, vi, and vim helps lol.

The old Berkeley mail interface is very interesting, but seems to lack mutts infinite configuration. Most of the time, I just use webmail. Google Chrome (Windows) or some thing from $BROWSER (*nix) is always open, so typically use that; but some times I do like to work from my terminal hehe. It even looks like the nail/heirlom-mailx program might add the stuff I desire.

TODO: inhale /usr/share/doc/usd/07.Mail (the reference manual), inhale nail documentation.