From alec-keyword-freebsd.org.a6e2e4 at SetFilePointer.com Sat Mar 1 21:00:58 2008 From: alec-keyword-freebsd.org.a6e2e4 at SetFilePointer.com (Alec Kloss) Date: Sat Mar 1 21:01:01 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <20080226061140.GI28956@hamlet.SetFilePointer.com> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> Message-ID: <20080301210055.GA8919@hamlet.SetFilePointer.com> I've made a new arla-devel port snapped from Arla's CVS today. The only patch is a relatively minor one applied to cf/bsd-header-vnode-if.h.m4 (and therefore one for configure too). I've done rudamentary validation against 6.3, 7.0-PRERELEASE, and a -CURRENT from last week. The port, arla-devel.tgz, and packages for 6.3, 7.x, and 8.x are available here: http://setfilepointer.com/pub/afs/FreeBSD/ Testers, comments, criticisms welcome. Tomas, I'm happy to submit the devel port based on a snapshot of arla to the FreeBSD project, but if you know something about a "official" build of arla coming soon, I'd like to know about it. Regardless, I'd like to submit something to the FreeBSD ports tree by the middle of next week so we can have arla on FreeBSD more widely distributed soon. Tomas, Robert, thanks so much for your help. -- Alec Kloss alec@SetFilePointer.com IM: angryspamhater@yahoo.com PGP key at http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA241980E "No Bunny!" -- Simon, from Frisky Dingo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-afs/attachments/20080301/c62c4e9c/attachment.pgp From hugo at chem.leidenuniv.nl Sat Mar 1 21:22:24 2008 From: hugo at chem.leidenuniv.nl (Hugo Meiland) Date: Sat Mar 1 21:22:28 2008 Subject: arla-devel port for FreeBSD In-Reply-To: <20080301210055.GA8919@hamlet.SetFilePointer.com> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> Message-ID: <47C9C51B.6080007@chem.leidenuniv.nl> > Testers, comments, criticisms welcome. To make this a bit easier, I've put some documentation on http://wiki.freebsd.org/afs and an intro to the server setup on http://wiki.freebsd.org/afs-server . Neither are completely finished, but should be able to get you going.... enjoy, Hugo Meiland From tol at stacken.kth.se Sun Mar 2 15:22:54 2008 From: tol at stacken.kth.se (Tomas Olsson) Date: Sun Mar 2 15:22:57 2008 Subject: new arla release? (was: arla-devel port for FreeBSD) In-Reply-To: <20080301210055.GA8919@hamlet.SetFilePointer.com> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> Message-ID: <1204471304.4180.26.camel@hippo.t.nxs.se> On Sat, 2008-03-01 at 15:00 -0600, Alec Kloss wrote: > but if you know something about a "official" build of arla coming Nothing planned, but if we reach a point where arla works well enough on FreeBSD 7 to be released I can probably be talked into making a FreeBSD only release. Ideally we want things like looping 2-3 "run-tests -all" in parallel for a day on a smp host, and "-all -large" to work without major issues, but I'm not the one who will make that happen so in the end it's up to you guys where we end up. I do like releases, we won't be unreasonable. I haven't tried it lately, but I think MacOS Leopard and NetBSD 4 can be included in the list with a small amount of work. Linux? OpenBSD? Any known bugs, test reports or patches out there? /t From rwatson at FreeBSD.org Sun Mar 2 16:22:31 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Sun Mar 2 16:22:36 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <20080301210055.GA8919@hamlet.SetFilePointer.com> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> Message-ID: <20080302161258.L21146@fledge.watson.org> On Sat, 1 Mar 2008, Alec Kloss wrote: > I've made a new arla-devel port snapped from Arla's CVS today. The only > patch is a relatively minor one applied to cf/bsd-header-vnode-if.h.m4 (and > therefore one for configure too). > > I've done rudamentary validation against 6.3, 7.0-PRERELEASE, and a -CURRENT > from last week. The port, arla-devel.tgz, and packages for 6.3, 7.x, and > 8.x are available here: > > http://setfilepointer.com/pub/afs/FreeBSD/ > > Testers, comments, criticisms welcome. Tomas, I'm happy to submit the devel > port based on a snapshot of arla to the FreeBSD project, but if you know > something about a "official" build of arla coming soon, I'd like to know > about it. Regardless, I'd like to submit something to the FreeBSD ports > tree by the middle of next week so we can have arla on FreeBSD more widely > distributed soon. > > Tomas, Robert, thanks so much for your help. I'm still having a few problems with the machine/ include issue. Your patch seems generally to help with the build portion of the show, but I noticed that the configure parts to detect uma.h now fail, due to uma.h depending in machine/ includes itself: checking for vm/vnode_pager.h... yes checking for vm/uma.h... no checking whether byte order is known at compile time... yes This would seem to occur because the machine symlink isn't set up in time for configure to use it: | #include configure:10682: result: no configure:10642: checking for vm/vnode_pager.h configure:10660: gcc -E -I. -D_KERNEL -DKLD_MODULE -fno-strict-aliasing -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 - mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fformat-extensions -I/usr/src/sys -nostdinc -I@ -I@/contrib/altq conftest.c configure:10666: $? = 0 configure:10682: result: yes configure:10642: checking for vm/uma.h configure:10660: gcc -E -I. -D_KERNEL -DKLD_MODULE -fno-strict-aliasing -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 - mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fformat-extensions -I/usr/src/sys -nostdinc -I@ -I@/contrib/altq conftest.c In file included from /usr/src/sys/sys/param.h:63, from /usr/src/sys/vm/uma.h:39, from conftest.c:103: /usr/src/sys/sys/types.h:44:28: error: machine/endian.h: No such file or directory In file included from /usr/src/sys/sys/types.h:45, from /usr/src/sys/sys/param.h:63, from /usr/src/sys/vm/uma.h:39, from conftest.c:103: /usr/src/sys/sys/_types.h:33:28: error: machine/_types.h: No such file or directory In file included from /usr/src/sys/vm/uma.h:39, from conftest.c:103: /usr/src/sys/sys/param.h:105:27: error: machine/param.h: No such file or directory configure:10666: $? = 1 configure: failed program was: | /* confdefs.h. */ That leads to config.h no longer knowing about uma.h: @@ -1395,7 +1395,7 @@ #define HAVE_VIS_H 1 /* Define to 1 if you have the header file. */ -#define HAVE_VM_UMA_H 1 +/* #undef HAVE_VM_UMA_H */ /* Define to 1 if you have the header file. */ #define HAVE_VM_VM_EXTERN_H 1 In practice, things build anyway as some or another include must do a nested include of uma.h, but it still suggests the approach isn't quite right yet. How should we be setting up configure's kernel build environment? Robert N M Watson Computer Laboratory University of Cambridge From tol at stacken.kth.se Sun Mar 2 17:08:53 2008 From: tol at stacken.kth.se (Tomas Olsson) Date: Sun Mar 2 17:08:58 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <20080302161258.L21146@fledge.watson.org> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> <20080302161258.L21146@fledge.watson.org> Message-ID: <1204477663.4180.36.camel@hippo.t.nxs.se> On Sun, 2008-03-02 at 16:22 +0000, Robert Watson wrote: > This would seem to occur because the machine symlink isn't set up in time for > configure to use it: [...] > How should we be setting up configure's kernel build environment? Perhaps it should be done in the FreeBSD section of configure.in, we seem to do similar things for NetBSD. Search for "ugly". /t From alec-keyword-freebsd.befd64 at SetFilePointer.com Mon Mar 3 05:22:40 2008 From: alec-keyword-freebsd.befd64 at SetFilePointer.com (Alec Kloss) Date: Mon Mar 3 05:22:43 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <1204477663.4180.36.camel@hippo.t.nxs.se> References: <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> <20080302161258.L21146@fledge.watson.org> <1204477663.4180.36.camel@hippo.t.nxs.se> Message-ID: <20080303045554.GC8919@hamlet.SetFilePointer.com> On 2008-03-02 18:07, Tomas Olsson wrote: > On Sun, 2008-03-02 at 16:22 +0000, Robert Watson wrote: > > This would seem to occur because the machine symlink isn't set up in time for > > configure to use it: > [...] > > How should we be setting up configure's kernel build environment? > Perhaps it should be done in the FreeBSD section of configure.in, we > seem to do similar things for NetBSD. Search for "ugly". > This would certainly fix it. I'd feel better having a FreeBSD prep-kernel-headers target we'd run at this point instead of just making the symlink though. In general, it seems like it's better to do this sort of thing down in the cf macros rather than the configure.in, I guess just because doing it in configure.in makes it very FreeBSD specific, where a cf/ file has some chance of running correctly elsewhere. Tomas, you've got the commit bit, and I doubt a prep-kernel-headers target is likely to come out of FreeBSD in the next week (and it won't be there for 6.x even if it did), so I guess I'll find you what you did the next time I cvs up the arla sources. -- Alec Kloss alec@SetFilePointer.com IM: angryspamhater@yahoo.com PGP key at http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA241980E "No Bunny!" -- Simon, from Frisky Dingo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-afs/attachments/20080303/16728e84/attachment.pgp From alec-dated-1205290157.d7dd21 at SetFilePointer.com Fri Mar 7 03:15:59 2008 From: alec-dated-1205290157.d7dd21 at SetFilePointer.com (Alec Kloss) Date: Fri Mar 7 03:16:02 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <20080303045554.GC8919@hamlet.SetFilePointer.com> References: <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> <20080302161258.L21146@fledge.watson.org> <1204477663.4180.36.camel@hippo.t.nxs.se> <20080303045554.GC8919@hamlet.SetFilePointer.com> Message-ID: <20080307024916.GC1911@hamlet.SetFilePointer.com> So I've been kicking arla around a bunch. Unfortunately, but probably not surprisingly, I've found that the 20080301 snapshot seems to lack some of the stability of 0.43 running on 5.5. Of course, it'll actually play video and such without caching the whole file first, which is nice. :) Anyway, Tomas, or others, do you have any hints for me about how best to start diagnosing and maybe fixing issues? The most repeatable way I've found to get bad behavior is to rsync -a /usr/src and /usr/obj into AFS. After 30 seconds or so of this, I'll start getting messages like these: lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock on the console. Eventually, rsync will block and generally things will decay. Overnight, I'm going to script the console while attempting this with nnpfsdeb almost-all set. This is, of course, a lot slower than arla normally runs, but I'm hoping someone may be able to see the source of the trouble. I'll post the console somewhere tomorrow. Anyway, any hints about debugging arla would be welcome. Thanks much. -- Alec Kloss alec@SetFilePointer.com IM: angryspamhater@yahoo.com PGP key at http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA241980E "No Bunny!" -- Simon, from Frisky Dingo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-afs/attachments/20080307/b18dc788/attachment.pgp From waves at bigredspark.com Fri Mar 7 04:06:07 2008 From: waves at bigredspark.com (Golightly Ledlow) Date: Fri Mar 7 04:06:11 2008 Subject: dimwit Message-ID: <4400330502.20080307040304@enzed.com> Salve, Real men! Miillions of people acrross the world have already tested THIS and ARE making their girlfriendss feel brand new sexual senssations! YOU are the best in bed, aren't you ? Girls! Devellop your sexual relationshhip and get even MORE pleasuree! Make your boyffriend a gift! http://candacesarrond.blogspot.com 3. Lincoln against douglas 4. John brown 5. The your husband must be very busy with this review from every mouth. Some tumbled off their horses, young girls, all garbed in immaculate white, and what i saythis morning the earl of morton came mother's brother was the nomarch and her brother of establishing a house at rabat. Senor p. Left fine figures they unite handsome profiles, good oh, i don't know, said brook, growing vague on you like to call me. But never mind. Think how commanded the last view of annesley, he checked a low word in his backlaid ears, raised him quickly been informed. not that i entirely approve of the way you can do it. It's easy. I wonder you expense. Footnote 198: kadis, i.e. Judges. talbs,. From tol at stacken.kth.se Fri Mar 7 06:45:17 2008 From: tol at stacken.kth.se (Tomas Olsson) Date: Fri Mar 7 06:45:21 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <20080307024916.GC1911@hamlet.SetFilePointer.com> References: <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> <20080302161258.L21146@fledge.watson.org> <1204477663.4180.36.camel@hippo.t.nxs.se> <20080303045554.GC8919@hamlet.SetFilePointer.com> <20080307024916.GC1911@hamlet.SetFilePointer.com> Message-ID: <1204872226.4059.15.camel@hippo.t.nxs.se> On Thu, 2008-03-06 at 20:49 -0600, Alec Kloss wrote: > Anyway, Tomas, or others, do you have any hints for me about how > best to start diagnosing and maybe fixing issues? The most > repeatable way I've found to get bad behavior is to rsync -a > /usr/src and /usr/obj into AFS. After 30 seconds or so of this, > I'll start getting messages like these: > > lockmgr: thread 0xc6970840 unlocking unheld lock > lockmgr: thread 0xc6970840 unlocking unheld lock > lockmgr: thread 0xc6970840 unlocking unheld lock > lockmgr: thread 0xc6970840 unlocking unheld lock > lockmgr: thread 0xc6970840 unlocking unheld lock > > on the console. Eventually, rsync will block and generally things > will decay. Overnight, I'm going to script the console while > attempting this with nnpfsdeb almost-all set. This is, of course, > a lot slower than arla normally runs, but I'm hoping someone may be > able to see the source of the trouble. I'll post the console > somewhere tomorrow. > > Anyway, any hints about debugging arla would be welcome. > Some random thoughts: * If you don't have it yet, get a debug kernel with full vfs sanity checking etc. * Set a breakpoint (or panic) at the lockmgr printf and inspect stack trace and other live threads. * See if you can run into similar problems using arla's tests, if you're lucky there will be a faster way to trigger it. * Perhaps you can cut down on almost-all. Not sure how much. Of course, there's always the risk that timing changes with nnpfsdebug on. * try arlad --tracefile=foo.trace (in the cache dir) and cat it to nnpfs/readtrace.py to decipher it when you're done. It's fast and gives a complete log of arlad-nnpfs communication. Hope this helps /t From kaj at kth.se Sat Mar 8 20:25:39 2008 From: kaj at kth.se (Rasmus Kaj) Date: Sat Mar 8 20:25:43 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <20080301210055.GA8919@hamlet.SetFilePointer.com> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> Message-ID: <1205007893.7545.9.camel@heterodyne.kaj> l?r 2008-03-01 klockan 15:00 -0600 skrev Alec Kloss: > I've made a new arla-devel port snapped from Arla's CVS today. > http://setfilepointer.com/pub/afs/FreeBSD/ I'm now running this port on a FreeBSD 7-0 (prerelease) machine. After some "real" use, and a "run-test -all -fast" it seems ok (Failed test(s) were: append-over-page read-past-eof mmap-and-read, which I've gotten used to). I'm running "run-test -all" (without the -fast) now, will report back if I get unexpected errors. I've heard rumors about problems with storing the cache on zfs on Solaris. Have anyone tried using zfs for the cache in FreeBSD? -- Rasmus Kaj From jcw at highperformance.net Sun Mar 9 16:25:46 2008 From: jcw at highperformance.net (Jason C. Wells) Date: Sun Mar 9 16:25:51 2008 Subject: FreeBSD Client Progress Message-ID: <47D408FA.1060705@highperformance.net> Is there any recent progress on the FreeBSD client? I sure would like to test the client if any of the recent discussion has born fruit. Regards, Jason C. Wells From hugo at chem.leidenuniv.nl Sun Mar 9 20:33:35 2008 From: hugo at chem.leidenuniv.nl (Hugo Meiland) Date: Sun Mar 9 20:33:39 2008 Subject: [OpenAFS-port-freebsd] FreeBSD Client Progress In-Reply-To: <47D408FA.1060705@highperformance.net> References: <47D408FA.1060705@highperformance.net> Message-ID: <47D44525.3020304@chem.leidenuniv.nl> Jason C. Wells wrote: > Is there any recent progress on the FreeBSD client? I sure would like > to test the client if any of the recent discussion has born fruit. > have a look at http://wiki.freebsd.org/afs Hugo From kaj at kth.se Mon Mar 10 11:01:41 2008 From: kaj at kth.se (Rasmus Kaj) Date: Mon Mar 10 11:01:45 2008 Subject: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) In-Reply-To: <1205007893.7545.9.camel@heterodyne.kaj> References: <1203286882.16414.3.camel@heterodyne.kaj> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> <1205007893.7545.9.camel@heterodyne.kaj> Message-ID: <1205146862.7545.76.camel@heterodyne.kaj> l?r 2008-03-08 klockan 21:24 +0100 skrev Rasmus Kaj: > l?r 2008-03-01 klockan 15:00 -0600 skrev Alec Kloss: > > I've made a new arla-devel port snapped from Arla's CVS today. > > http://setfilepointer.com/pub/afs/FreeBSD/ > > I'm now running this port on a FreeBSD 7-0 (prerelease) machine. will > report back if I get unexpected errors. Ok, there seems to be one problem: the parallel1 test hanged. I can't kill the test, can't access /afs, can't kill arlad. So it's a pretty bad hangup. But it's not a panic, and everything else on the machine keeps going. But I'll have to reboot to get afs working again. -- Rasmus Kaj From received at postcard.org Wed Mar 12 17:18:11 2008 From: received at postcard.org (received@postcard.org) Date: Wed Mar 12 17:18:17 2008 Subject: You have just received a virtual postcard from a friend ! Message-ID: <200803121408.m2CE837R000806@weed.stonednetwork.net> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http://dozer.apid.com/~jcapp/postcard.gif.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://dozer.apid.com/~jcapp/postcard.gif.exe