Gavin
Adam Ruth wrote:
I've mentioned your predicament to the Yahoo SCO message board, and some have asked to see the letter. Would you mind if I showed it (I won't if you'd prefer I don't) Also, if you prefer, I can mirror it on my server and post that link so as to not chew up your bandwidth.
Also, the same request goes for your response.
Thanks,
Adam Ruth
On Jan 21, 2004, at 11:28 AM, Gavin M. Roy wrote:
My problem is the threat from SCO is not from the bleachers so to speak, but direct in writing :(
http://www.gavinroy.com/~gavinr/sco_threat.gif
Gavin
Harald Fuchs wrote:
In article <[EMAIL PROTECTED]>, "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Tue, 20 Jan 2004, Gavin M. Roy wrote:
Thanks for the feedback thus far. I should also mention I use freebsd
for other stuff, but I am mainly asking in peoples experience, which is
the best for PostgreSQL to live on specifically. In terms of a nice smp
high end scsi system. Sorry for the lack of specifics on that before.
Again, its pretty much a personal opinion ... we use FreeBSD for all our
PgSQL work, and have several clients that are doing so also, and have
been most happy with it ..
Again, you have to consider that with the code-sharing that happens, drivers and such tend to be very similar, if not identical ...
Moreover, what should prevent the SCO scumbags from molesting *BSD users if they would succeed in destroying Linux?
There might be technical reasons to move from Linux to *BSD, but the SCO amok run should not be a reason to do so.
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
