From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Brian Henning <brian@strutmasters.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: smbfs in 2.6.8 SMP kernel
Date: Mon, 17 Jan 2005 20:41:28 +0000 [thread overview]
Message-ID: <1105984827.16096.10.camel@localhost.localdomain> (raw)
In-Reply-To: <41EC003B.7040606@strutmasters.com>
On Llu, 2005-01-17 at 18:13, Brian Henning wrote:
> Jesper Juhl wrote:
> > If I remember correctly there was some smbfs breakage a few releases back
> > - 2.6.8 sounds about right. I'd suggest you try a newer kernel like 2.6.10
> > or 2.6.11-rc1 and see if that works better.
>
> No luck with smbfs in 2.6.10 with SMP either; however, I discovered the
> existence of CIFS (which I previously did not know about), and it
> appears to work smoothly in place of smbfs.
2.6.10-ac fixes several problems with the later smbfs code but cifs is
probably the better choice
prev parent reply other threads:[~2005-01-17 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 15:08 smbfs in 2.6.8 SMP kernel Brian Henning
[not found] ` <Pine.LNX.4.61.0501171633140.20155@jjulnx.backbone.dif.dk>
2005-01-17 18:13 ` Brian Henning
2005-01-17 18:49 ` Jesper Juhl
2005-01-17 20:41 ` Alan Cox [this message]
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=1105984827.16096.10.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=brian@strutmasters.com \
--cc=linux-kernel@vger.kernel.org \
/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.