Vallish Vaidyeshwara wrote:
> NFS Version 3 mounts negotiate a security mode when
> the server returns an array of security modes. The
> client picks the first mode in the array that is
> supported on the client. In negotiations, an NFS
>
OK, I just got the mail. The bug is 6828396
Its odd that the Solaris bug reporter doesn't actually assign a number until
later. Other bug reporters (Apple's, for example) give you a number as soon as
you hit "submit". Does a human actually look at the bug before it is given a
number?
Drew
Thanks for confirming that it is not just me.
I've filed a bug, just in case nobody else has (don't know the bug id yet).
Regards,
Drew
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.or
Hi,
I recently BFU'd a system in my home lab from snv_106 to
snv_111, and now I cannot access things as a user from my
Linux NFS server using NFSv3 because Solaris NFS is sending my
uid as 65534. The only workaround I've been able to find is to use
an NFSv2 mount. The same machine worked fine for
I do device drivers, and I like to have a recent version of OpenSolaris
available for testing. Unfortunately, I don't have the time to learn all the
quirks of the Solaris build process, yet I would like to be able to keep up
with the latest OpenSolaris build easily.
I've been using BFU on top
> system completely. I know whenever I saw network
> activity, the
> machine started to sort of stutter (the mouse was
Have you tried running intrstat and checking for interrupt storms when this
happens?
Drew
This message posted from opensolaris.org
The MXGE project is an effort to port a proprietary, vendor supplied
Solaris GLDv2 ethernet driver for the Myricom 10GE NIC to an
OpenSolaris GLDv3 driver.
This project will start with the vendor's GLDv2 driver and integrate
it into OpenSolaris. Once the driver is part of OpenSolaris, we will
por