So I've not posted since 15 April when I mucked up networking on Hydrogen.

I've been up to quite a lot personally and with Gentoo. The non-gentoo exploits mainly involve applying for a visa to enter the United Kingdom to have a Civil Partnership with my lovely fianc

How to muck up a system in style.

A plain link

Oops. lol

edit: change link style, apparently the gallery is FUBAR?

Democrat for Senate: Death penalty for practicing 'gays'

What's worrying is that he's collected enough signatures to get himself in on the running.

When this package was added it was intended as a stopgap measure, really. There was no good PHP API for the memcached daemon. The only good one was the Perl one, (now Cache::Memcache) written by the memcached author.

There was later a PHP API written in C, part of the PECL, which would inherently be faster. It's now the recommended API (SO USE IT, AND DISTCC! </subtle).

So now the slow, buggy, unsupported API is gone. Rejoice!

Cos I'm about two seconds away from comitting UOAMhub, an unofficial Linux port of the Win32 only UOAMsvr.

UOAM is a program designed to act as a kind of GPS within the UO world. Various guilds and groups of friends use UOAM to keep track of everyone's position, which, coupled with voice communication (such as TeamSpeak) helps in coordination of events.

Belxan's UOAM protocol is proprietary and the uoamhub daemon has reverse engineered it.

I'll be testing the daemon today and stress testing it this week with my own guild.

I posted on the -dev mail list late last month about removing this API. It's buggy, and the source files aren't even on SRC_URI. There was 0 response to my -dev post and 0 favourable response to my post to memcached mail list.

So if you're going to use Memcached with PHP please use the PECL version. dev-php5/pecl-memcache or something. ;)

Google Error
We're sorry...

... but we can't process your request right now. A computer virus or spyware application is sending us automated requests, and it appears that your computer or network has been infected.

We'll restore your access as quickly as possible, so try again soon. In the meantime, you might want to run a virus checker or spyware remover to make sure that your computer is free of viruses and other spurious software.

We apologize for the inconvenience, and hope we'll see you again on Google.

What rubbish!!

In my years using Gentoo I've learned a lot. I'm going to share it with everyone (whether you like it or not):

In no particular order...

1. It isn't necessary to completely wipe clean your disk to fix a perceived problem in your installation (even if you allocate only 4gb instead of 40 for /).
2. Never downgrade glibc.
3. Always use Google when you've got a problem.
4. ALWAYS use Bugzilla
5. Join Gentoo:)
6. Ignore flamewars
7. Don't ignore -core mail or you'll miss out on important data, like, Gentoo is a foundation? And it's got a council? *g*
8. Disable root logins, ssh version 1, and password logins in sshd_config; force ssh key access
9. Backup your data
10. ADMIT NOTHING!!!!!!!
11. Don't take things too seriously
12. Take the serious things seriously

There's so much more, but it would take far too long to list.

As much as I'd love to see SLP integrated with Distcc I've come to the realisation that Gentoo isn't the place for the patch to be implmented and tested. Rather, it should be applied to the source tree UPSTREAM for the entire user base to test, likewise with all other patch enhancements.

Obiously it's different if the package has no maintainer and hasn't seen the loving hand of a programmer in years or if the patch is to fix a serious Gentoo-specific bug, like the TMPDIR issues in distcc from a year or two ago.

You write a shite CMS in Bash and PHP!

It's called CMS580 cos all told it is 580 lines in length. lol

It's buggy, has barely any 'CMS' features, but it uses mod_rewrite, which was kind of the goal.

What did I learn about mod_rewrite? Save yourself the trouble and just send everything to a prg: map.

Anyways, if you're morbidly curious feel free to laugh, at the code in cvs. The mod_dir bits are commented in .htaccess because of bug 11843.

Or rather, I'm infamous!!!
See also here

I've had a cluster idea in mind for a long time now. Basically stuff a bunch of Mini-ITX boards into a full size ATX case with a bunch of hard disks, netboot and play. I finally got around to putting down in electrons what I would use for such a box.

I reckon the box will run between

Truthfully that would be kind of nice. I could really trim down the distcc documentation and the ebuild to remove the stuff that is only present to deal with pre-bootstrap.

With Bug 80219 we're going to be adding SLP support to distcc. It will be a boon for those people with large clusters of volunteers.

Right now it seems to work. The daemon starts (./distccd -p 3666 --listen 192.168.0.254 -a 192.168.0.0/24 -P /home/lisa/projects/distcc/distcc-2.18.3/src/distccd.pid --verbose --log-level=debug --log-file=./log.log --daemon) and the tool works (./distccenv ---> DISTCC_HOSTS="lithium:3666 ").

I wonder if the portage guys could do a test to see if slpd is running and use that to set DISTCC_HOSTS with the distccenv program: export `distccenv`. I haven't done any compilation tests just yet.

On Distcc and bootstrap:

One of the major problems with using distcc during installation from stage 1 is that the user must manually add the distcc user before issuing the emerge distcc command. When the user later (after stage 2) installs distcc the shadow package is available for useradd.

I'd love to just make it so the user has to re-emerge distcc after bootstrap. I think I may have found a MAJOR brain fart: Currently the distcc use is required during emerge to change the permissions of /var/run/distccd to that user so the init script can put the pid file there, owned by distcc:daemon. Inside the init script the directory is chmodded again for the distcc user. Why add do it in the ebuild when it can be done in the init script? *duh* I'll test that with the SLP stuff.

I finally inherited my fianc

Well I'm back in New York, as of the 12th. I suppose a short update is in order...

Everything in Trinidad went well. Thank you to everyone for your help, you know who you are.

Anne and I are scheduled to fly back to England on the 24th of October. This will go ahead if I have my passport! A critical piece of evidence was a week late in getting into my hands and so the State Department has 5 business days plus Saturday to get my passport to me. *gulp* Good thing I asked for expedited service.. I know they received my application on the 13th at midday in Philly. Should be enough time (she tells herself...).

Anyways.

Once I get back to England I will likely inherit Anne's laptop which will be put to UO usage so my desktop can return to its Linux glory cos frankly Windows is irritating.

I've got lots of motivation and really want to (finally) test SLP support in Distcc. I'll have to set up Hydrogen (our fileserver) to use the correct toolchain as Lithium (my desktop) and Helium (our general purpose server box) to have matching configs for glibc, distcc, and gcc. Fun! ;)

okay
in the past i've made references to surgery... my fiancee and i registered a domain http://www.helpmyfiancee.com please read and pass it on.

thank you

if anyone has questions pm me on irc.

Link: http://blogs.sun.com/roller/page/ThinGuy?entry=the_war_on_terror_as

Highly amusing.

Those that know me know that I have surgery scheduled for this October 4th of this year. My fianc

In 3 years, 200 days, 23 hours, and 39 minutes Gentoo got 100.000 bugs.
That's 77.1613620909 bugs per day.
The first bug on record is How do I attach an ebuild. (at 2002-01-04 02:39 PDT) and the 100.000th is clanlib 0.7.8-r1 can't emerge (xargs: environment is too large for exec) (at 2005-07-23 03:18 PDT). As of this post we are up to 100.109 bugs. The off-by-one in the counting is because the first bug is #2. And as we all know 100.002-2 = 100.000!

I wonder how many of these are due to people using crazy CFLAGS?

Edit: Random wanker Daniel Hancock's comment is deleted and his IP is 218.101.84.118 for future reference.