public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jan Kara <jack@suse.cz>
Cc: Nathan Scott <nathans@sgi.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: Quota patches
Date: Fri, 24 May 2002 16:10:11 +0200	[thread overview]
Message-ID: <3CEE49C3.4050202@evision-ventures.com> (raw)
In-Reply-To: <20020523091626.GA8683@atrey.karlin.mff.cuni.cz> <Pine.LNX.4.44.0205231002460.1006-100000@home.transmeta.com> <20020524123510.A180298@wobbly.melbourne.sgi.com> <20020524145817.GC31925@atrey.karlin.mff.cuni.cz>

Uz.ytkownik Jan Kara napisa?:
>   Hi all,
>   
> 
>>On Thu, May 23, 2002 at 10:03:50AM -0700, Linus Torvalds wrote:
>>
>>>On Thu, 23 May 2002, Jan Kara wrote:
>>>
>>>>... . If he has newer tools
>>>>(<3.05) he has to decide depending on format he wants to use...
>>>
>>                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>>
>>>This makes me pretty certain we just do not want to have the backwards-
>>>compatibility layer in 2.5.x
>>>
>>>Are there _any_ reasons to use the old stuff, if the fix is just to
>>>upgrade to a newer quota tool?
>>
>>Moving to newer interfaces implies use of the new ondisk format
>>for the quota files (exclusively) - I'd imagine that's the main
>>reason behind providing a choice.  Whether or not that reason is
>>sufficently compelling though... dunno.  If one wanted to be able
>>to switch between booting either 2.4 (unpatched) and 2.5+, and
>>also maintain quota information on filestystems, then the choice
>>would be useful in that situation.
> 
>   Latest quota interface is able to handle both formats together
> (structures passed throught Q_GETQUOTA, Q_SETQUOTA,... are independent
> of quota format and Q_QUOTAON takes as an argument in 'id' the quota format
> number). So if user wants to stay at old format he can...
>   So I think Linus is right here that there's no real reason for keeping
> compatibility code in 2.5... Linus, I'll send you the patch which kicks
> out the compatibility stuff.

As a side note:

If we can do it for quota - we could possible remove the
IPC_OLD variant away as well. It's looong overdue by now,
becouse the IPC_OLD was not standard conformant anyway.

I would be really really glad to do it iff ACK-ed.


  reply	other threads:[~2002-05-24 15:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 13:55 Quota patches Jan Kara
2002-05-20 14:07 ` Christoph Hellwig
2002-05-20 15:38   ` Jan Kara
2002-05-22 19:46 ` OGAWA Hirofumi
2002-05-22 19:57   ` Jan Kara
2002-05-22 23:30   ` Nathan Scott
2002-05-23  0:59     ` Nathan Scott
2002-05-23  1:56       ` Alan Cox
2002-05-23  1:55         ` Nathan Scott
2002-05-23  9:16         ` Jan Kara
2002-05-23 17:03           ` Linus Torvalds
2002-05-24  2:35             ` Nathan Scott
2002-05-24  3:46               ` Linus Torvalds
2002-05-24 14:58               ` Jan Kara
2002-05-24 14:10                 ` Martin Dalecki [this message]
2002-05-24 15:43                   ` Alan Cox
2002-05-24 14:31                     ` Martin Dalecki
2002-05-24 15:43                       ` Christoph Hellwig
2002-05-24 14:43                         ` Martin Dalecki
2002-05-24 16:12                           ` Alan Cox
2002-05-24 15:55                             ` Christoph Hellwig
2002-05-24 14:54                               ` Martin Dalecki
2002-05-24 16:18                               ` Alan Cox
2002-05-24 16:14                       ` Alan Cox
2002-05-24 16:01                         ` David Woodhouse
2002-05-24 18:41                         ` Thunder from the hill
2002-05-24 15:07             ` Alan Cox
     [not found] <20020523154249.X180298@wobbly.melbourne.sgi.com>
2002-05-23  8:53 ` Jan Kara

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=3CEE49C3.4050202@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=torvalds@transmeta.com \
    /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