Messages in this thread |  | | | Date | Tue, 26 Aug 2008 14:44:54 +0400 | | From | Alexey Dobriyan <> | | Subject | Re: An idea .... with code |
| |
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.
|  |