More "Paul Murphy" Anti-Linux FUD: SCO or Son of SCO Can Still Win

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News More "Paul Murphy" Anti-Linux FUD: SCO or Son of SCO Can Still Win
# 1  
Old 06-21-2010
More "Paul Murphy" Anti-Linux FUD: SCO or Son of SCO Can Still Win

Were you imagining that "Paul Murphy" was going to apologize for his attacks on Groklaw or for being so wrong in his support of SCO? Or that he'd keep his promise to stop blogging if SCO lost? Or that he'd finally admit SCO has no case?
Au contraire. He continues to insult, and he predicts SCO, or a new owner of Novell, will surely succeed yet in fulfilling SCO's plot, in what he believes, if I've understood him, will be a legal Hail Mary pass to go down in history. The new FUD is his article, Suicide by Victory: More on SCO, in which he predicts gloom and doom for Linux because Novell won at the jury trial in Utah.
I know. He's so funny. It makes no sense. But I'll answer him seriously anyway. I'm beginning to wonder if he and Marc Rochkind were the guys who cooked up this whole fiasco. Rochkind, you ask? Yes, he tells us what his "testimony" was, even though Rochkind never testified and his expert report for SCO was and is under seal. I don't know how that strikes you, but it strikes me that perchance "Murphy" has more of a direct connection to the SCOfolk than he tells us. If so, this article might represent a trial balloon, in which case it's worth responding to, in the hopes that the world will be spared the long version.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. SCO

sco unix backward compatibility on "max open file per process"

Hi How to increase maximum number of open file in "sco xenix binary" running in "sco unix openserver 5.0.7" ? I have changed "NOFILES" kernel parameter to 512, but xenix binray can't open more than 60. tnx (4 Replies)
Discussion started by: javad1_maroofi
4 Replies
Login or Register to Ask a Question
FUD(8)							      System Manager's Manual							    FUD(8)

 *

NAME
FUD - provide information about user mailboxes SYNOPSIS
fud [ -C config-file ] [ -U uses ] [ -T timeout ] [ -D ] DESCRIPTION
FUD is a long lived datagram daemon started from cyrmaster that provides information about when a user last read their mail, when mail last arrived in a user's mailbox, and how many messages are recent for that user. Note that for FUD to run properly you must set proto=udp in its cyrus.conf services entry. prefork=1 is also recommended. FUD will auto- matically proxy any and all FUD requests to the appropriate backend server if it is runing on a Cyrus Murder frontend machine. FUD reads its configuration options out of the imapd.conf(5) file unless specified otherwise by -C. OPTIONS
-C config-file Read configuration options from config-file. -U uses The maximum number of times that the process should be used for new connections before shutting down. The default is 250. -T timeout The number of seconds that the process will wait for a new connection before shutting down. Note that a value of 0 (zero) will dis- able the timeout. The default is 60. -D Run external debugger specified in debug_command. FILES
/etc/imapd.conf Default configuration file. /etc/cyrus.conf Cyrus Master process configuration file. BUGS
Though not really a bug, FUD will silently ignore any requests that it does not consider valid. Also not really a bug, FUD requires that the anonymous user has the 0 (zero) right on the mailbox in question. This is only a "bug" because 0 is not a standard IMAP ACL bit. FUD is an experimental interface meant to provide information to build a finger-like service around. Eventually it should be superceded by a more standards-based protocol. CMU
Project Cyrus FUD(8)