jpr's blog

slapd built and installed.

./configure --enable-dnssrv --enable-hdb --enable-ldap \

had xmms on pause overnight, clicked play/pause, then immediataly
skip-to-next-song, this caused the entire desktop to freeze. even warm
reboot didn't work. had to pull power. afterward booting took a long
time at grub stage 2. assume it was a currupted log/journal. after a
complete boot, the boot times returned to normal. had feared a bad disk.

http://mailman.u.washington.edu/pipermail/pubcookie-users/2004-May/000468.html

One (insecure) way of getting port 80 redirects to work for pubcookie.

did a poor job of recording tasks today. spent the afternoon split between two projects, storage and mlist. Started recording my namespace understands and wishes for the storage project and documented the home automounting config. Set up a test rss gw list feed for the mlist project.

[phpwiki]
Our home dirs are mounted by using nfs and the automounter and
leveraging hostname aliases in the DNS.

Each machine that is to mount the home directories needs to be capable
of being an NFS client (http://nfs.sourceforge.net/nfs-howto/client.html).

Once it is an NFS client we need to configure the automounting system.
The reason we use the automounter is to avoid a lot of permanent mounts
of network resources. This can get messy if the server providing the
resources crashes.

The file that does the magic is the /etc/auto.home file. It should look
like this:

# $Id: auto.home,v 1.1 2003/05/27 16:26:39 root Exp jpr $

http://www.mailbucket.org/

MailBucket is an experiment in alternative methods of email management.
The service is probably most useful to those who lurk on high-traffic
mailing lists, but it could also be used as a rudimentary bridge between
applications, with email as the transfer protocol.

bring up an nntp interface to the lists to help force the thinking about
the spread of the archives and what it means for authz issues in this
space. we'll have archive access on a list-specific page provided by the
listmgr tool, archives via a website (cms/forum/bboard system), archives
via nntp, archives via imap, archives via rss.

it should be possible to subscribe to any one of these services. the key
in the authz space is really to determine if you may subscribe.

i wouldn't mind having all or a lot of the content running across the
website also running across a list. so most of my posts should be going
to the devel list and then appearing on the site. this would enable
conversations to occur in any space (website or email). (thought. if you
subscribe to my blog you could almost think of it as subscribing to the
"jpr@uab.edu" or "jpr@lab.ac.uab.edu" list or channel.)

this also brings up the point that the website (posts and discussion
forums) are really more like nntp or even imap since your talking about
views into common message stores. the mail list traffic is really just the

the lists.u.washington login sequence is a simple wayf, if from
u.washington login here else login there. this type of
"enterprise&friends/others" wayf will be a typical user collection
senario.

thinking about the cosign implementation and comparing to pubcookie and
shib, you can think of them as an ever increasing scope of user bases.
pubcookie is single domain, cosign is two domains (enterprise and friends)
both "hosted" but the same site, and shib is a 2 or more solution though
the complexity of shib suggests you better have a lot to justify the work.

there was a stray = in the conditional check of user_access() that was
returning very inconsistent results for the role permissions query or
skipping it entirely. taking this out has fixed all the posting issues.
they question is: how did it sneak in?