Rebuild instructions for amd64 systems
I am installing FreeBSD 7.2 / amd64 on a new server (HP DL370 G6) with 2 quad Xeon processors and 16GB memory. I have worked with the i386 versions since version 3.x, but this is the first server large enough to need amd64. I have been trying to determine the correct procedures for rebuilding the world and kernel. I have not been able to find a location that had step by step instructions, similar to the handbook, for properly working with the amd64 version. Searches have turned up so many fragments of what needs to be done, that I cannot feel confident trying to put the pieces together. I need instructions for the command line compile options, conf file additions, and any special instructions. If anyone can point me to some applicable links or some specific instructions, it would be appreciated. TIA Richard -- Richard D. Gehlbach Gehlbach Consulting Services rdgeh...@gehlbach.com 3321 Pepperhill Ct. 859.269.6658 Fax 859.266.7446Lexington, KY 40502 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Drop in replacement for imap-UW?
Joe in MPLS wrote: I've been running imap-UW on FreeBSD 6.x STABLE for a while. Clients are mostly Thunderbird, TREOs and Horde (running on the same box. I'm having issues when multiple clients try to access the same user's mailbox. Typically the TREO will do a scheduled check for new mail while Thunderbird has it already open. Research indicates that this is a limitation of the UW imapd implementation. We ran into this problem on shared access to mail, and found it was an issue with locks against the mailbox. Take a look at the mbx format in the UW's formats.txt file - http://www.washington.edu/imap/documentation/formats.txt.html - and the FAQ at http://www.washington.edu/imap/IMAP-FAQs/index.html#4.5. I understand that not all clients support this format. We are using it successfully with Thunderbird and Squirrelmail. It allows simultaneous mail access, deletions, etc. Can anyone recommend a good and secure imapd implementation that won't require a ton of reconfiguration? Mostly I'd like the replacement to be able to use all the existing end-user imap folders and mail spools. All users have accounts and mail spools on the box. There's no virtual users or database authentication backends to deal with. TIA ...jgm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Richard D. Gehlbach Gehlbach Consulting Services [EMAIL PROTECTED] 3321 Pepperhill Ct. 859.269.6658 Fax 859.266.7446Lexington, KY 40502 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
