Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*freebsd\s+port\s+for\s+2\.6\.1\s+b0rked\?\s+\[solved\]\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*freebsd\s+port\s+for\s+2\.6\.1\s+b0rked\?\s+\[solved\]\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: freebsd port for 2.6.1 b0rked? [solved] (score: 1): Author: Angelo Höngens <A.Hongens AT netmatch DOT nl>; Date: Sun, 22 Feb 2009 15:01:43 +0100; And I got back an immediate answer that solved it: -- With kind regards, Angelo Höngens Systems Administrator -- NetMatch tourism internet software solutions Ringbaan Oost 2b 5013 CA Tilburg T: +31 (; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2009-02/msg00141.html (13,152 bytes)
2. Re: freebsd port for 2.6.1 b0rked? [solved] (score: 1): Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>; Date: Sun, 22 Feb 2009 18:51:08 -0500; On Sun, Feb 22, 2009 at 9:01 AM, Angelo Höngens <A.Hongens AT netmatch DOT nl> wrote: Good news! Jun is on top of his business. Amgetconf is now available on the client, so it makes sense to include; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2009-02/msg00142.html (11,442 bytes)

Current List: 1 - 2
Page: [1]