From: benh@kernel.crashing.org
To: Bastien Nocera <hadess@hadess.net>,
Urban Widmark <urban@teststation.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: problems with smbfs on 2.4.18 kernel (ppc)
Date: Mon, 4 Mar 2002 22:03:41 +0100 [thread overview]
Message-ID: <20020304210341.10387@mailhost.mipsys.com> (raw)
In-Reply-To: <1015293079.1830.55.camel@dozo>
>> Has smbfs worked for you with previous versions? A patch was added late to
>> 2.4.18 and it has caused a lot of crashes for people. I don't think it is
>> related, but since you mention 2.4.18 ...
>
>I never tried the previous versions of it.
Yes, smbfs used to work with recent version.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-04 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 17:11 problems with smbfs on 2.4.18 kernel (ppc) Bastien Nocera
2002-03-03 17:28 ` Urban Widmark
2002-03-05 1:51 ` Bastien Nocera
2002-03-04 21:03 ` benh [this message]
2002-03-05 16:50 ` Derrik Pates
2002-03-05 9:12 ` Urban Widmark
2002-05-01 15:49 ` Bastien Nocera
2002-05-03 2:06 ` Bastien Nocera
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=20020304210341.10387@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=hadess@hadess.net \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).