util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Reisner <d@falconindy.com>
To: kzak@redhat.com
Cc: util-linux@vger.kernel.org
Subject: swapon feature additions
Date: Thu, 27 Oct 2011 15:40:56 -0400	[thread overview]
Message-ID: <20111027194056.GN691@rampage> (raw)

Hi Karel,

I was interested in making a few changes to swapon, but I figured I'd
inquire as to whether or not they're welcome first.

1) Introduce optional libmount support. This involves first refactoring
reading of /etc/fstab to remove the duplicated code and use callbacks
instead. Breaking out the functionality into libmount-powered and
non-libmount-powered code is then much cleaner.
2) Teach swapon/swapoff to only look at files or partitions. The use
case in mind is specifically for unswapping only files at shutdown, as
partitions can remain mounted without harm.

Does this seem reasonable? Is this functionality wanted? Anything else I
should be aware of?

Thanks,
Dave Reisner

             reply	other threads:[~2011-10-27 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 19:40 Dave Reisner [this message]
2011-11-03 10:41 ` swapon feature additions Karel Zak

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=20111027194056.GN691@rampage \
    --to=d@falconindy.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).