From: Kyle Davenport <kdd@tvmax.net>
To: Urban Widmark <urban@teststation.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux 2.4.25 crashes windows
Date: Sun, 04 Apr 2004 23:57:17 -0500 [thread overview]
Message-ID: <4070E72D.7090702@tvmax.net> (raw)
In-Reply-To: Pine.LNX.4.44.0404042132201.28197-100000@cola.local
Urban Widmark wrote:
>On Sun, 4 Apr 2004, Kyle Davenport wrote:
>
>
>
>>No joke. 64-bit Windows Advanced Server 2003 blue-screens on file share
>>access. I was using Samba 3.0 on RH8 to routinely access windows
>>shares. When I upgraded from 2.4.22 to 2.4.25, any attempt to access a
>>sub-directory of a share mounted from 64-bit Win2003, immediately
>>crashes windows. I rolled back to 2.4.22 and no crash. I tried 2.4.25
>>against a 32-bit 2003 Win2003, and no crash. I didn't test different
>>versions of Samba. But on 2.4.25, trying to ls a sub-directory of the
>>mounted share or cd to that sub-directory, instantly and repeatedly
>>blue-screens windows.
>>
>>
>
>When you say mount, does that mean smbfs?
>
>
yes.
>2.4.25 allows you to enable the cifs unix extensions in smbfs. Perhaps
>turning those off makes a difference?
>
>The other change is that smbfs in 2.4.25 has large file support. smbfs in
>2.4.24 should behave like 2.4.22.
>
ok, I'll try that tomorrow. Any idea what those directives are?
--
Kyle Davenport - unix sys admin consultant - Dallas TX
_____________________________
You can lead a horse to knowledge, but you can not make him learn it.
next prev parent reply other threads:[~2004-04-05 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 17:03 linux 2.4.25 crashes windows Kyle Davenport
2004-04-04 19:46 ` Urban Widmark
2004-04-05 4:57 ` Kyle Davenport [this message]
2004-04-22 17:34 ` Urban Widmark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4070E72D.7090702@tvmax.net \
--to=kdd@tvmax.net \
--cc=linux-kernel@vger.kernel.org \
--cc=urban@teststation.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.