Re: [RFC/P] Port System Re-Engineering (Repost from -ports@)

2007-12-03 Thread Andrew Reilly
On Mon, Dec 03, 2007 at 09:19:15AM -0500, Aryeh M. Friedman wrote: > 1. What is more important to your personal use of FreeBSD (the ports > system, the underlaying OS, some other aspect)? Yes. (i.e., mu) > 2. How frequently do you interact with the ports systems and what is > the most common int

Re: congrlations to the freebsd developers

2007-11-19 Thread Andrew Reilly
> 3. The issues with nvidia kernel module on amd64 (alternativelly > does anyone know how hard it would be to get bettern 1024x768 with nv?) I used to be able to get nv to do 1280x1024, with my 6600LE graphics card. I could never convince it to do 1600x1200, the native resolution of my LCD pa

Re: Don't buy AMD products (was Re: Xorg and ATI card query.)

2007-03-15 Thread Andrew Reilly
On Wed, Mar 14, 2007 at 11:55:20AM -0400, Sean Bryant wrote: > Try the 'vesa' xorg driver. It may not be fancy or all that accelerated > but it works quite well. I have an nvidia card and cannot get it to work > for the life of me. the drive attached, but nothing happens after that. > It might b

Expected speed of firewire-attached drive?

2007-03-13 Thread Andrew Reilly
Hi there, I don't do a whole lot of benchmarking: mostly my computer's speed is "perfectly adequate", and working reliably is key. At the moment, though, I'm curious. I'm sitting here while I attempt to restore a file from a level-0 dump, and it's taking a while. The backup medium is one of tho

Re: Don't buy AMD products (was Re: Xorg and ATI card query.)

2007-03-13 Thread Andrew Reilly
On Tue, 13 Mar 2007 14:17:00 -0800 (PST) Doug Ambrisko <[EMAIL PROTECTED]> wrote: > One thing that is a plus with nv is that X has some support for it, > whereas, the newer ati cards have no support :-( I was a fan of ati > since it was easier to get support. Now I'm starting to lean towards >

Re: Don't buy AMD products (was Re: Xorg and ATI card query.)

2007-03-13 Thread Andrew Reilly
On Tue, 13 Mar 2007 14:17:00 -0800 (PST) Doug Ambrisko <[EMAIL PROTECTED]> wrote: > One thing that is a plus with nv is that X has some support for it, > whereas, the newer ati cards have no support :-( I was a fan of ati > since it was easier to get support. Now I'm starting to lean towards >

Re: Hardware Console Redirection

2006-10-31 Thread Andrew Reilly
On Tue, Oct 31, 2006 at 06:18:22PM -0500, Brian A. Seklecki wrote: > I have noticed that the "Phoenix BIOS" console redirection feature on both > discontinues to operate once the kernel has booted (however, the 1st/2nd > stage boot loaders work fine). Why is that a problem? The BIOS doesn't use

ataraid/fsck glitch on upgrade from 5.5 to 6-stable?

2006-09-21 Thread Andrew Reilly
Hi all, I ran into an unexpected problem today, when I tried to do an in-place upgrade from FreeBSD 5.5 (actually RELENG_5) to 6-STABLE, following the procedure in /usr/src/UPDATING. The buildworld and buildkernel went without a hitch, and installkernel was fine, too. When I rebooted to single-u

Re: [bugs] SMP, KDE3 and OpenOffice

2006-07-16 Thread Andrew Reilly
On Sun, Jul 16, 2006 at 03:12:49PM +1000, Rob Hurle wrote: > I'm trying to set up FreeBSD on my box, which has an Intel > D945GNT motherboard, two 3.2GHz processors, 1GB memory. The system > installs OK and I've been able to use cvsup to upgrade everything, > remake the kernel (for SMP), bui

rpcbind: connect from 127.0.0.1 to dump() ??

2006-04-04 Thread Andrew Reilly
Hi there, I'm running an NFS server on one of my FreeBSD-6-STABLE systems, and it keeps putting that message into my /var/log/auth.log file. When I say keeps, there are thousands of such logs per day, sometimes separated by seconds, sometimes by many minutes or hours. I can't find anything on th

Programming question: fcntl(...,O_ASYNC) on device?

2004-05-27 Thread Andrew Reilly
Hi, oh gurus, I'm venturing into a realm of Unix programming that I had previously been able to avoid: asynchronous event processing, with or without threads. Can anyone suggest why the following test-case program always produces: $ ./test-case test-case: can't set O_ASYNC on device: Invalid ar