From: Karel Zak <kzak@redhat.com>
To: Jeff Epler <jepler@unpythonic.net>
Cc: LaMont Jones <lamont@debian.org>,
Roger Leigh <rleigh@codelibre.net>,
util-linux@vger.kernel.org
Subject: Re: Enable findmnt on kfreebsd
Date: Thu, 14 Mar 2013 11:22:09 +0100 [thread overview]
Message-ID: <20130314102209.GB7700@x2.net.home> (raw)
In-Reply-To: <20130314003946.GB4068@unpythonic.net>
On Wed, Mar 13, 2013 at 07:39:47PM -0500, Jeff Epler wrote:
> In a recent discussion on #debian-kbsd, rleigh brought up the fact that
> findmnt isn't available on kfreebsd; he feels it would be useful in
> initscripts.
Do you mean for fstab/mtab parsing? ... because I cannot imagine
anything else without Linux kernel.
> I had a look at what it would take to enable findmnt, which needs
> libmount. It turns out that not much is required: mostly, make a few
> bits of code return (-)ENOSYS. There were also a few more bits that
> needed tweaking before kfreebsd was happy (LIST_HEAD is also in some
> bsd-origin header, and of course <linux/posix_types.h> was not
> available).
>
> I'm not sure I correctly intuited where it was proper to return +ENOSYS
> and where it was proper to return -ENOSYS, so this merits further study.
Maybe you can #ifdef whole context{.c,_umount.c,mount.c} API. All you
need is probably fs.c tab*.c files. Maybe you can modify libmount/src/Makemodule.am
rather than code to create a minimalistic kernel independent libmount :-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2013-03-14 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 0:39 Enable findmnt on kfreebsd Jeff Epler
2013-03-14 1:06 ` Samuel Thibault
2013-03-14 2:02 ` Jeff Epler
2013-03-14 2:39 ` Samuel Thibault
2013-03-14 10:22 ` Karel Zak [this message]
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=20130314102209.GB7700@x2.net.home \
--to=kzak@redhat.com \
--cc=jepler@unpythonic.net \
--cc=lamont@debian.org \
--cc=rleigh@codelibre.net \
--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