From: Pete Zaitcev <zaitcev@redhat.com>
To: Panu Matilainen <pmatilai@welho.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 1279 mounts
Date: Sat, 27 Apr 2002 21:32:36 -0400 [thread overview]
Message-ID: <20020427213236.A20253@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020425162106.A30736@devserv.devel.redhat.com> <Pine.LNX.4.44.0204261120520.19032-100000@chip.2y.net>
> Date: Fri, 26 Apr 2002 11:25:33 +0300 (EEST)
> From: Panu Matilainen <pmatilai@welho.com>
> I've got quite a few users here who "need" this functionality and it's
> included in our RH-based custom kernels. Having it as a separate patch
> for 2.4 is no problem, for 2.5 I'm hoping we finally move to 32bit device
> numbers...
Mind, we only ship the unnamed majors part, but not the NFS part.
There is no word from util-linux maintainer about required
changes to mount(8), so I was cautious about doint that.
-- Pete
next prev parent reply other threads:[~2002-04-28 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 20:21 1279 mounts Pete Zaitcev
2002-04-26 8:25 ` Panu Matilainen
2002-04-28 1:32 ` Pete Zaitcev [this message]
2002-04-28 17:57 ` Panu Matilainen
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=20020427213236.A20253@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=pmatilai@welho.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