Thanks for the fast reply.
On Thu, Dec 14, 2000 at 05:45:15PM -0500, David E. Cross wrote:
As for "client" vs. "server", that is quite tricky since WRT NFS locking
they are both client and server. The "server" side is done and requires no
modifcations to the kernel. However a FreeBSD
-current is hanging during boot - right after "mounting root from ufs"
things stall for a second - then you start getting those old microuptime
warnings spewing on the console forever - I gave it about 10 minutes or
so hoping it would work its way out of it - no dice.
FYI
Mark Hittinger
The other day, on a whim, I decided to try running an old binary
of SimCity (the same one found in the 'commerce' directory on
many FBSD cds), and it failed in a odd way...
/usr/libexec/ld.so: Undefined symbol "___error" called from
sim:/usr/X11R6/lib/aout/libX11.so.6.1 at 0x20160644
# ldd sim
In the last episode (Dec 16), Axel Thimm said:
Wouldn't that mean, that you might cause data corruption if, say, I
was to read my mail from a FreeBSD box over an NFS mounted spool
directory (running under OSF1 in our case), and I decided to write
back the mbox to the spool dir the same moment
Andrzej,
did you receive a response regarding your email the Intel
Pro 10/100B/100+ Ethernet being unresponsive after running windows?
i seem to have the same problem.
jmb
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Andrzej,
did you receive a response regarding your email the Intel
Pro 10/100B/100+ Ethernet being unresponsive after running windows?
i seem to have the same problem.
I'm working on the (longer-term) solution to this at the moment. In the
meantime, it's going to need a driver
On Sat, Dec 16, 2000 at 04:26:58PM -0600, Dan Nelson wrote:
That's why dotlocking is recommended for locking mail spools. Both
procmail and mutt will dotlock your mail file while it's being
accessed.
Or Maildirs.
--
Jos Backus _/ _/_/_/"Modularity is not a hack."
