From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: jassi_singh_brar@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: An idea .... with code
Date: Tue, 26 Aug 2008 14:44:54 +0400 [thread overview]
Message-ID: <20080826104454.GA13455@x200.localdomain> (raw)
In-Reply-To: <87tzd89oap.fsf@basil.nowhere.org>
On Tue, Aug 26, 2008 at 10:24:30AM +0200, Andi Kleen wrote:
> jassi brar <jassi_singh_brar@yahoo.com> writes:
>
> > Lately a question has been bugging me: Why do we keep complicated(specific ioctls to set up and set free)
>
> Can you please expand a bit why you think losetup is that complicated
> and what the problem is with it?
>
> AFAIK you're essentially just moving a minimal version of losetup
> (with missing features like no offsets etc.) into the kernel and
> frankly I fail to see the beauty in that. Or rather if you start with
> losetup, why stop at mount, modprobe, ifconfig, mkfs, fsck, ls[1], ...?
>
> For me it seems more that most of the file system based command
> interfaces (/proc/mtrr comes to mind) are quite hard to use
Name four.
> and I prefer a proper command line tool with a manpage and --help
> and a real parser any day.
Go write mtrrctl(1) and a manpage. You'll need it in case of
ioctl-based interface anyway.
next prev parent reply other threads:[~2008-08-26 10:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 8:53 jassi brar
2008-08-25 12:22 ` Jochen Voß
2008-08-25 20:53 ` Marcin Slusarz
2008-08-26 2:47 ` Bill Davidsen
2008-08-26 8:24 ` Andi Kleen
2008-08-26 10:44 ` Alexey Dobriyan [this message]
2008-08-26 11:08 ` Andi Kleen
2008-08-27 7:24 ` jassi brar
2008-08-27 7:47 ` Andi Kleen
2008-08-27 9:57 ` David Newall
2008-08-27 10:01 ` Andi Kleen
2008-08-27 12:38 ` jassi brar
2008-08-27 12:47 ` Andi Kleen
2008-08-27 14:49 ` Kasper Sandberg
2008-08-27 15:02 ` Andi Kleen
2008-08-28 1:24 ` jassi brar
2008-08-28 9:41 ` Kasper Sandberg
2008-08-30 2:57 ` Bill Davidsen
2008-08-27 0:44 jassi brar
2008-08-27 2:27 jassi brar
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=20080826104454.GA13455@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=andi@firstfloor.org \
--cc=jassi_singh_brar@yahoo.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
all inboxes | Powered by JetHome®