linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jose Luis Alarcon Sanchez" <jlalarcon@chevy.zzn.com>
To: armin@xos.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6-test4 latencey problems + howto compilation
Date: Sat, 6 Sep 2003 21:01:24 +0200	[thread overview]
Message-ID: <A340D5F1860783E4BBC9E429C5A7DAFD@jlalarcon.chevy.zzn.com> (raw)

---- Begin Original Message ----

From: Armin Obersteiner <armin@xos.net>
Sent: Sat, 6 Sep 2003 19:17:44 +0200
To: linux-kernel@vger.kernel.org
Subject: 2.6-test4 latencey problems + howto compilation

hi!

Congratulations for the 2.6 kernel, it seems more mature than 2.4 test
kernels!
 
My 2.6 experience (linux-2.6.0-test4) is basically *very* good, but
some remarks:

1) Documents/Changes should be updated to:

    module-init-tools      0.9.13                  # depmod -V

  Earlier module-init-tools do not work. at least nor for me.

.......

---- End Original Message ----


  Hi Armin.

  I don't know why the previous module-init-tools don't work
for your system. I am using the 2.6.0-test4 kernel (with the
Nick Piggin ideas about schedule patched) and i can manage
modules perfectly. This is my depmod -V output:

module-init-tools 0.9.10

  Maybe you can have another thing broken?.

  Regards.

  Jose.


http://linuxespana.scripterz.org

FreeBSD RELEASE 4.8.
Mandrake Linux 9.1 Kernel 2.6.0-test4 XFS.
Registered BSD User 51101.
Registered Linux User #213309.
Memories..... You are talking about memories. 
Rick Deckard. Blade Runner.


Get your Free E-mail at http://chevy.zzn.com
__________________
http://www.zzn.com

             reply	other threads:[~2003-09-06 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-06 19:01 Jose Luis Alarcon Sanchez [this message]
2003-09-06 19:55 ` 2.6-test4 latencey problems + howto compilation Armin Obersteiner
  -- strict thread matches above, loose matches on Subject: below --
2003-09-06 17:17 Armin Obersteiner

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=A340D5F1860783E4BBC9E429C5A7DAFD@jlalarcon.chevy.zzn.com \
    --to=jlalarcon@chevy.zzn.com \
    --cc=armin@xos.net \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).