From: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
To: "Ramón Rey Vicenteó® " <retes_simbad@yahoo.es>
Cc: aradorlinux@yahoo.es, bunk@fs.tum.de, jamagallon@able.es,
linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.22 released
Date: Wed, 27 Aug 2003 02:21:37 -0300 [thread overview]
Message-ID: <20030827022137.7cf9290e.vmlinuz386@yahoo.com.ar> (raw)
In-Reply-To: <1061950515.1166.41.camel@debian>
On Wed, 27 Aug 2003 04:15:16 +0200, Ramón Rey Vicenteó® wrote:
>El mié, 27-08-2003 a las 00:29, Diego Calleja García escribió:
>
>> > - it's easy to use ALSA even when it's not inside the kernel
>> > - within a few months 2.6.0 will be released with ALSA included -
>> > together with the point above I don't see a reason why ALSA would be
>> > badly needed in 2.4
>>
>> Those are valid points. Still I'd love to see ALSA in 2.4. I guess this is a
>> matter of opinion....the VM bits from Andrea are far more important (I've read
>> several bug reports from people who can't get big machines working ie: kswapd decides
>> to take all the cpu for 1 minute)
>
>I think VM are more important that any other things at this moment, but
>is not the only thing to take care of.
yes, it is more important the possible changes in the VM.
>From my small point of view we consider this:
ALSA: is very easy to configure it outside the kernel tree, without patching it.
I2C 2.8.0: (the same happens with alsa FIXME) (discussed in another thread).
XFS: the XFS needs yes or yes to patch kernel, is used enough in many instalations,
but as consequence modifies several archives of kernel, which does difficult to be able
to include some patch more after this, like for example some of security (lids, etc...).
Conclusion: I vote by VM (priority) and XFS.
chau,
djgera
--
Gerardo Exequiel Pozzi ( djgera )
http://www.vmlinuz.com.ar http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
next prev parent reply other threads:[~2003-08-27 5:23 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 11:48 Marcelo Tosatti
2003-08-25 8:11 ` Enrico Demarin
2003-08-25 13:23 ` Matthias Andree
2003-08-25 13:32 ` Christoph Hellwig
2003-08-25 13:35 ` Ramón Rey Vicente
2003-08-25 21:13 ` J.A. Magallon
2003-08-25 22:22 ` Adrian Bunk
2003-08-26 0:21 ` Ramón Rey Vicente
2003-08-26 21:49 ` Diego Calleja García
2003-08-26 21:55 ` Adrian Bunk
2003-08-26 22:29 ` Diego Calleja García
2003-08-27 2:15 ` Ramón Rey Vicente
2003-08-27 5:21 ` Gerardo Exequiel Pozzi [this message]
2003-08-27 1:20 ` Chuck Campbell
2003-08-27 1:48 ` David van Hoose
2003-08-27 1:55 ` David van Hoose
2003-08-27 3:28 ` Kurt Wall
2003-08-27 2:01 ` Ramón Rey Vicente
2003-08-27 4:12 ` Willy Tarreau
2003-08-26 22:29 ` Matthias Andree
2003-08-27 9:47 ` Bas Mevissen
2003-08-26 13:55 ` Matthias Andree
2003-08-25 13:38 ` Nick Piggin
2003-08-25 22:34 ` Bill Davidsen
2003-08-25 14:38 ` Yann Droneaud
2003-08-25 15:35 ` Krzysztof Halasa
2003-08-25 16:03 ` Luca Montecchiani
2003-08-25 19:18 ` Erik Andersen
2003-08-25 20:00 ` Edesio Costa e Silva
2003-08-25 20:10 ` Tom Rini
2003-08-26 13:19 ` Rene Rebe
2003-08-26 15:00 ` Alan Cox
2003-08-27 3:47 ` CaT
2003-08-26 16:11 ` Willy Tarreau
2003-08-26 19:32 ` Greg KH
2003-08-26 1:52 ` cryptoapi doesn't build Tom Vier
2003-08-26 10:23 ` James Morris
2003-08-27 21:49 ` Tom Vier
2003-08-27 22:03 ` Marc-Christian Petersen
2003-08-26 4:25 ` [PATCH-2.4] make log buffer length selectable Willy Tarreau
2003-08-27 20:09 ` Tom Rini
2003-08-27 20:48 ` Willy Tarreau
2003-08-25 16:25 linux-2.4.22 released Mikael Pettersson
2003-08-25 16:40 ` Marc-Christian Petersen
2003-08-25 16:53 Marcelo Tosatti
2003-08-25 17:20 Mikael Pettersson
2003-08-27 21:45 ` Marc-Christian Petersen
2003-08-26 22:25 John Bradford
2003-08-27 2:11 ` Ramón Rey Vicente
2003-08-27 6:10 John Bradford
2003-08-28 2:31 ` bill davidsen
2003-08-27 11:10 Vid Strpic
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=20030827022137.7cf9290e.vmlinuz386@yahoo.com.ar \
--to=vmlinuz386@yahoo.com.ar \
--cc=aradorlinux@yahoo.es \
--cc=bunk@fs.tum.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=retes_simbad@yahoo.es \
/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®