From: Thomas Molina <tmolina@copper.net>
To: Nathan Scott <nathans@sgi.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
<linux-kernel@vger.kernel.org>,
Anders Gustafsson <andersg@0x63.nu>, Steve Lord <lord@sgi.com>
Subject: Re: [RELEASE] module-init-tools 0.8
Date: Thu, 28 Nov 2002 20:24:33 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0211282009540.895-100000@lap.molina> (raw)
In-Reply-To: <20021129014500.GB546@frodo.melbourne.sgi.com>
On Fri, 29 Nov 2002, Nathan Scott wrote:
> > Steve? Changing the prefix on xfs or elf seems equally painful (xfs
> > because it'll be a big patch, elf because it's standardized and been
> > like that forever).
>
> We changed XFS when this problem first came up. Linus hasn't yet
> pulled from Christoph's bitkeeper tree though, so we're a bit out
> of sync at the moment.
Sounds like I need to drop back and punt. I probably need to wait for the
syncing to happen and bk to be updated. I need to have 2.4 kernels
working (specifically RedHat). I'm doing this testing on my laptop, which
because I'm going to be moving, will be my only machine for the next month
or so. I want to get 2.5 working, but module loading doesn't work and
modutils-2.4.21-4.i386.rpm and
modutils-2.4.21-5.i386.rpm break 2.4 kernels.
next prev parent reply other threads:[~2002-11-29 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0211272325370.924-100000@lap.molina>
2002-11-29 0:59 ` Rusty Russell
2002-11-29 1:45 ` Nathan Scott
2002-11-29 2:24 ` Thomas Molina [this message]
2002-11-29 2:50 ` Keith Owens
2002-11-29 3:41 ` Thomas Molina
2002-11-28 2:28 Rusty Russell
2002-11-28 16:16 ` Gerd Knorr
2002-11-28 17:09 ` Bill Davidsen
2002-11-28 18:22 ` Tomas Szepe
2002-11-28 23:47 ` Christoph Hellwig
2002-11-28 22:49 ` Jan-Benedict Glaw
2002-11-28 18:23 ` Gerd Knorr
2002-11-28 20:52 ` Marco d'Itri
2002-11-29 3:18 ` Rusty Russell
2002-11-29 2:38 ` Rusty Russell
2002-11-29 10:00 ` Rusty Russell
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=Pine.LNX.4.44.0211282009540.895-100000@lap.molina \
--to=tmolina@copper.net \
--cc=andersg@0x63.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.com \
--cc=nathans@sgi.com \
--cc=rusty@rustcorp.com.au \
/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®