public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: viro@math.psu.edu
Subject: RFC: Remove swap file support
Date: Sat, 07 Jul 2001 11:34:30 -0400	[thread overview]
Message-ID: <3B472C06.78A9530C@mandrakesoft.com> (raw)

Since you can make any file into a block device using loop,
is there any value to supporting swap files in 2.5?

swap files seem like a special case that is no longer necessary...

-- 
Jeff Garzik      | A recent study has shown that too much soup
Building 1024    | can cause malaise in laboratory mice.
MandrakeSoft     |

             reply	other threads:[~2001-07-07 15:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07 15:34 Jeff Garzik [this message]
2001-07-07 17:15 ` RFC: Remove swap file support arjan
2001-07-12  7:27 ` Fabbione
2001-07-12 13:54   ` Jeff Garzik
2001-07-17  5:36     ` Val Henson
2001-07-14  6:07 ` Eric W. Biederman
2001-07-14 14:44   ` jlnance
2001-07-14 16:12     ` Alan Cox
2001-07-14 17:28       ` Eric W. Biederman
2001-07-14 15:25   ` Chris Wedgwood
2001-07-14 17:35     ` Eric W. Biederman
2001-07-15  3:42       ` Chris Wedgwood
2001-07-17 11:59       ` Chris Wedgwood

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=3B472C06.78A9530C@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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