> At least from looking at the Linux 2.2.18 code, if you get EROFS back
> from the Linux server, the actual set of access bits you get back won't
> have the right bits set; "nfsd_access()" just jumps to "out:" if it gets
> a "read-only file system" error, and that doesn't set "*access" to the
> re
I can attest to the fact that Slot A thunderbirds do exist. I own 3 of
them (one 900 and 2 700 MHz). I guess I was fortunate that my Slot A
thuderbirds worked properly (all running FreeBSD) in the MBs (MSI and
Abit) that I have, though I have also heard that problems exist with
some MBs
Bob
On F
> Any suggestions would be greatly appreciated
not yet supported.
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Hi
I am running FreeBSD 4.2-STABLE (cvsup'd 21 Jan) on an Intel Easton
(D815EEA) board with onboard sound and am having problem getting the
on-board sound working. The sound is reported to be AC'97 v1.03 compliant. I
have included the following (from LINT) in my kernel configuration
file..
#
Folks,
I'm seeing this behaviour too, as of my make world of today (using up to
date CVSup'd sources). Has anyone found the source of the problem.
It's bloody annoying. I've had to kill syslogd.
Regards,
Tony.
On Sun, 21 Jan 2001 02:10:40 -0500, you wrote:
>Folks,
>
>After the last of a ver
On Wed, Jan 24, 2001 at 10:42:16AM -0800, Guy Harris wrote:
> If you do want to work around the Linux bug, you'd probably have to send
> another ACCESS request over the wire, with the write bits turned off;
> I'm not sure whether that's worth the effort or not.
An alternative patch is
*** vfs.c.
On Wed, Jan 24, 2001 at 03:17:07AM -0800, Mike Smith wrote:
Content-Description: nfs_vnops.diff
> --- /sys/nfs/nfs_vnops.c Fri Jan 12 14:15:00 2001
> +++ nfs_vnops.c Wed Jan 24 03:01:52 2001
> @@ -387,6 +387,14 @@
>*/
> nfsstats.accesscache_
:
:On Wed, Jan 24, 2001 at 10:28:02AM -0800, Matt Dillon wrote:
:> This particular problem, however, is entirely Linux's problem to fix.
:
:Umm, could somebody *PLEASE* show me *ANY* place where I argued that it
:wasn't a Linux bug? I can show at least one mail message where I
:said it *WAS*
On Wed, Jan 24, 2001 at 10:28:02AM -0800, Matt Dillon wrote:
> This particular problem, however, is entirely Linux's problem to fix.
Umm, could somebody *PLEASE* show me *ANY* place where I argued that it
wasn't a Linux bug? I can show at least one mail message where I
said it *WAS* a Linux
All this discussion over the right way to do ACCESS is moot. The NFSv3
protocol docs are absolutely clear on how ACCESS is supposed to work, and
if Linux wants to be NFSv3 interoperable it has to follow the protocol.
The FreeBSD client is following the protocol properly... it just
On Wed, Jan 24, 2001 at 03:04:54AM -0800, Mike Smith wrote:
> I'm not sure that the v3 specification actually cares about telling the
> client "why",
It doesn't, which I think may have been a mistake.
> > For example, a UNIX "open()" call that calls an "access" vnode operation
> > couldn't, if
On Tue, 23 Jan 2001, Kris Kennaway wrote:
> Nope. There are security implications to doing this anyway..this would
> partly defeat the protection afforded by OTP schemes.
I presume the security implications are algorithmic to the S/Key system, and
not just the risk associated with N "good" pas
> Luc Morin wrote:
>
> Hi,
>
> I have recently started experiencing network problems on my -stable box.
>
> The last cvsup dates a few weeks back, and everything was working fine up until a
>few days ago.
>
> Strangest thing is that everything works just fine under Win98, and that when I
>re
Hi,
I have tested a few more times by rebooting my box
and pinging a known good host.
Every time I see the same pattern. it works for a
few minutes, then stops working completely.
Attached is a text file with various system
information.
thanks,
Luc Morin
uname -a ouput:
FreeBS
14 matches
Mail list logo
