From: Martin Dalecki <dalecki@evision-ventures.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Jan Kara <jack@suse.cz>,
Nathan Scott <nathans@sgi.com>,
Linus Torvalds <torvalds@transmeta.com>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: Quota patches
Date: Fri, 24 May 2002 16:54:13 +0200 [thread overview]
Message-ID: <3CEE5415.7060906@evision-ventures.com> (raw)
In-Reply-To: <3CEE51A4.9010308@evision-ventures.com> <E17BHfh-0006lp-00@the-village.bc.nu> <20020524165514.A20631@infradead.org>
Uz.ytkownik Christoph Hellwig napisa?:
> On Fri, May 24, 2002 at 05:12:05PM +0100, Alan Cox wrote:
>
>>>>Of course you can. Even the latest OpenLinux release (shipping 2.4.13-ac)
>>>>uses a libc4/a.out based installer fo space reasons. Not to forget the
>>>>old quake1 binary from some redhat 4.x CD I run from time to time :)
>>>
>>>OK thanks for the *substantial* answer. That was the reason I was asking about.
>>>Somehow this is of course surprising me of course.
>>
>>So why didn't you -test- the theory before suggesting it. It btw goes beyond
>>Libc4. Currently we have almost 100% compatibility back to libc 2.2.2. The
>>dated libc before that doesn't work because we dropped some very very
>>early obscure versions of a few syscalls.
>>
>>Is it too much to ask that you go and look through the syscall tables of
>>old and new kernels ?
>
>
> For 2.5 I have some plans to make obsolete syscalls depend on CONFIG_COMPAT_*,
> this allows to compile big and bloated kernel for compatiblity and smaller
> kernels without that (e.g. for embedded devices). And in fact we have quite
> a loft of cruft that can go away for setups only having very modern userspace..
I second this!
next prev parent reply other threads:[~2002-05-24 16:03 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
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 [this message]
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=3CEE5415.7060906@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--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