All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Sean Neakums <sneakums@zork.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET] Linux 2.4.20-jam0
Date: Sat, 30 Nov 2002 16:02:52 +0100	[thread overview]
Message-ID: <20021130150252.GG2517@werewolf.able.es> (raw)
In-Reply-To: <6u3cpj3xzx.fsf@zork.zork.net>; from sneakums@zork.net on Sat, Nov 30, 2002 at 15:58:42 +0100


On 2002.11.30 Sean Neakums wrote:
>commence  J.A. Magallon quotation:
>
>> Thanks, I will add it...
>> BTW, who puts names to options ? Wouldn't be more intuitive to add options
>> like 'ialloc_std' or 'ialloc_orlov' ? Too late to change this ?
>
>There isn't exactly a whole lot of contention in the mount-options
>namespace.  And neither orlov not ialloc_orlov is in any way
>"intuitive".  However, orlov is more guessable, to my mind, than
>ialloc_orlov.
>

Well, what I think is more understandable when you see a /etc/fstab
would be something like 'inode_allocator=std' or 'inode_allocator=orlov' or
'inode_allocator=xxxxx' if something new appears.

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-jam0 (gcc 3.2 (Mandrake Linux 9.1 3.2-4mdk))

  reply	other threads:[~2002-11-30 14:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 23:38 [PATCHSET] Linux 2.4.20-jam0 J.A. Magallon
2002-11-30  0:47 ` Andrew Morton
2002-11-30 14:45   ` J.A. Magallon
2002-11-30 14:58     ` Sean Neakums
2002-11-30 15:02       ` J.A. Magallon [this message]
2002-11-30 22:15     ` Andrew Morton
2002-11-30  6:36 ` hugang
2002-11-30 14:58   ` J.A. Magallon
2002-11-30 17:07     ` Mike Galbraith
2002-11-30 17:50 ` Andrea Arcangeli
2002-11-30 23:36   ` J.A. Magallon
2002-12-01  1:55   ` J.A. Magallon

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=20021130150252.GG2517@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sneakums@zork.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.