Now, let’s accept the fact that we are humans, that we have emotions and the way we talk is just a normal consequence. The initial post from Norman Richards was a perfectly polite and articulate talk in which he was raising real issues about most H.R. practices.

But instead of listening to the (really interesting) message, someone (who is not an isolated case) focused to the form of the message. I think it is a shame and that is why I loved the provocative answers. In the end, we do not care whether Norman Richards has an attitude or not, what is important is that he brought up important issues.

I believe that it is what we should focus on.

I fail to see why treating people like crap helps in any situation whatsoever. Care to elaborate ?

  _session().close()
  session_maker.remove()

@mathieu: I was talking about the perfect’ish Ruby, but Brainfuck would have been a candidate as well if it were more popular

Are you talking about Brainfuck?

Seriously, it gives me a good overview of the tools I might need for rainy days when I want to try something different than ruby.

1. On the shell, do:
sudo apt-get install awstats

2. Edit /etc/awstats/awstats.conf
- change the line SiteDomain=”YOUR_SITE_DOMAIN_NAME_HERE”
- change the line with /var/log/apache/access.log, this is wrong, change to /var/log/apache2/access.log

3. Back on the shell, do:
/usr/lib/cgi-bin/awstats.pl -config=YOUR_SITE_DOMAIN_NAME_HERE -output > /var/www/stats.html

4. Now on the browser, go to:
http://YOUR_SITE_DOMAIN_NAME_HERE/stats.html

Thanks for the poste!

The 1M$ question I have is how do we measure that technical debt in such a way is to make it clear that its not just some off the cuff number that the (probably defensive) development team will try to discredit, and will at the same time speak to a product owner?

Different measures have been proposed. (1) James Shore suggests the spag (http://jamesshore.com/Blog/An-Approximate-Measure-of-Technical-Debt.html), (2) I (and you) have disscussed the the gap between today’s code base and and its envisioned production-worthy future, (3) even measurements of the impact on a teams velocity. All seem like good ideas, the first and last at least use measurable metrics. The second is tricky, I have seen teams very quickly deploy crap into production environments – sometimes said crap does not smell for quite some time.

I still can help but feel that in a concrete sense, the idea of technical debt is as hard to measure as its nemesis “clean code”.

One thing that I think needs to be done is for our industry to stop glorifying “the hacker”, the lone wolves of old who where praised for being able to decipher the cryptic messes they themselves wrote. We should start praising those who write code their grandmothers can understand (or at the very least a SME). This shift in culture at least will open the door to an era in which young developers stop being proud of what they can read, but rather what they can write.

so please maski, how did you get about the bug????

The main problem was that there were missing foundations (hald, udev, etc) and they were constantly doing dirty hacks to lure the user into thinking that the desktop was ready. Now that things are way smoother, that aplications can subscribe to network events, that automounts work correctly, etc, we can definitely say that the user experience is better.

Well.. my opinion is that it’s the same for system administration. You can create UIs to hide the mess, but if you really want to go forward, at some point, you need to fix the mess. And I am pretty sure that it would open the door to much more innovation…

For encrypted root: ubuntu makes it easy/sexy/reliable.

uw-imapd doesn’t seem to work well with horde3/imp4. (or so the pkg. main. say)

A quick change over to dovecot fixed the problem with authentication for mail and everything works perfect now!

Thanks!!!!

thanks

Are you still using the old eth0, eth0:1, eth0:2 notation? If so, try to use “ip addr add 1.2.3.4/32 dev eth0″ instead.

the path in /etc/horde/horde3/conf.php must be changed to value ‘/horde3′ (was ‘/horde’)

cheers,

martin

This is for the people having the error:

“Failed to import Horde configuration: Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share/doc/horde3/README.Debian.gz on how to allow access.”

You need to not only remove exit(0); but comment out the text above that. So just put a // before the echo statement at the top of the config.php

Example:

// echo “blahblahblah read the README.debian.gz that doesn’t tell you jack”

hehe…man, debian developers are great…but their documentation lacking in content to say the least. I’m all for the little guys trying to port themselves away from the Microsoft giant (booo to ms! unless ur finding new ways to screw with their kernel haha)

Khayjake

Debian Sid
Slackware 11.0
Fedora Core 6
HP-UX
AIX

Thanx a lot, I just edited /etc/horde/horde3/conf.php and the horde works perfectly!!

Cheers!

Are you using pure permissions or ACL permissions ?

what are the permissiosn of /etc/horde ?

Can anyone know how to deal with this error? I’ve already followed whole instructions above but it returns error message below.

“Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system.”

Please help….

After installing and generating the horde3 conf i cannot log into the horde system, same as you reported.
You claimed to have solved the problem but didn’t mention how you did so.
Could you please share your solution?
Thanks in advance