From: Pavel Machek <pavel@suse.cz>
To: Paul.Clements@steeleye.com
Cc: Edward Muller <emuller@learningpatterns.com>,
linux-kernel@vger.kernel.org
Subject: Re: Current NBD 'stuff'
Date: Thu, 6 Dec 2001 13:02:20 +0000 [thread overview]
Message-ID: <20011206130220.B49@toy.ucw.cz> (raw)
In-Reply-To: <1007402546.3824.9.camel@akira.learningpatterns.com> <Pine.LNX.4.10.10112041644170.17617-400000@clements.sc.steeleye.com>
In-Reply-To: <Pine.LNX.4.10.10112041644170.17617-400000@clements.sc.steeleye.com>; from kernel@steeleye.com on Tue, Dec 04, 2001 at 05:26:06PM -0500
Hi
>
> > Anyone know where I can find the latest NBD stuff? Esp. client/server
> > code?
>
> I have the same question. Maybe the user-level stuff is not being
> actively maintained?
>
> However, since we couldn't find current versions of this stuff,
> my colleagues and I patched nbd-server and the nbd kernel module
> to fix a few bugs and to make them a little more robust. I'll
> attach my versions of those files (which I think are derived from
> Pavel's .14.tar.gz versions).
Do not comment code by //. Kill if it you want to.
You added clean way to stop nbd. Good.
DO NOT USE ALL CAPITALS not even in printks().
Fix those and patch looks ike good idea for 2.5.
Look at nbd.sf.net. If you have patches against that, mail them to me. If
you are willing to co-develop stuff at nbd.sf.net, I guess we can arrange
something.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-12-06 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 18:02 Current NBD 'stuff' Edward Muller
2001-12-04 22:26 ` Paul Clements
2001-12-04 23:12 ` Edward Muller
2001-12-05 16:14 ` Paul Clements
2001-12-05 16:44 ` Peter T. Breuer
2001-12-05 21:02 ` Peter T. Breuer
2001-12-05 22:30 ` Paul Clements
2001-12-06 13:02 ` Pavel Machek [this message]
2001-12-06 22:13 ` [PATCH] " Paul Clements
2001-12-22 19:48 ` David Chow
2001-12-06 12:54 ` Pavel Machek
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=20011206130220.B49@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=Paul.Clements@steeleye.com \
--cc=emuller@learningpatterns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox