linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Gerd Knorr <kraxel@bytesex.org>
Subject: Re: [uml-devel] Re: uml-patch-2.6.0
Date: Tue, 20 Jan 2004 20:42:17 +0100	[thread overview]
Message-ID: <200401202042.17851.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <87vfn7yikh.fsf@bytesex.org>

Alle 18:06, lunedì 19 gennaio 2004, Gerd Knorr ha scritto:
> BlaisorBlade <blaisorblade_spam@yahoo.it> writes:
> > Module support fix is trivial, and does not depend on anything
> > controversial, until you don't enable CONFIG_MODVERSIONS. So apply the
> > patch. I've also infos (and some code) about fixing the panic you get on
> > startup with it enabled.
>
> Uhm, no.  Applied and builds for me, but doesn't work, insmod
> complains about *plenty* of unknown symbols.

It works for me, maybe either you didn't apply some patch or a make clean 
ARCH=um is needed.

> G-02-LinkScriptCleanup.patch removes various ksymtab stuff from
> common.lds.S (which is in the RODATA #define these days), that one
> looks like it could be needed too to make modules work ...

Those repeated sections are harmless, only ugly; the big change is for 
/proc/kallsyms. However, modules worked without that (it helps also for 
modversions, but not completely: with that I get no panic but versions 
mismatch, and I know why).

I've not been very careful in testing separate patches one-by-one. I've tested 
the whole set minus the H-03 and H-04 one, but not together.

Bye
-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.23/2.6.0 on an i686; Linux registered user n. 292729
EOSIGN



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-01-20 19:39 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  5:05 [uml-devel] uml-patch-2.6.0 Jeff Dike
2004-01-13  5:18 ` [uml-devel] uml-patch-2.6.0 Jeff Dike
2004-01-13 10:19 ` Sven Köhler
2004-01-13 18:55   ` Gerd Knorr
2004-01-16  2:33     ` Jeff Dike
2004-01-16 10:03       ` M A Young
2004-01-16 11:42         ` Gerd Knorr
2004-01-17 16:10           ` BlaisorBlade
2004-01-16 17:27         ` Jeff Dike
2004-01-16 21:56           ` Gerd Knorr
2004-01-17 21:12           ` M A Young
2004-01-18  4:47             ` Jeff Dike
2004-01-16 23:47       ` Sven Köhler
2004-01-17 19:09       ` BlaisorBlade
2004-01-17 19:50         ` Jeff Dike
2004-01-17 20:03           ` BlaisorBlade
2004-01-18  4:51             ` Jeff Dike
2004-01-18 16:21       ` Ingo Molnar
2004-01-18 21:06         ` [uml-devel] uml 2.6.1 kbuild simplifications Ingo Molnar
2004-01-19  0:08           ` [uml-devel] " Jeff Dike
2004-01-19  7:34             ` Ingo Molnar
2004-01-20 17:40               ` Jeff Dike
2004-01-18 23:57         ` [uml-devel] Re: uml-patch-2.6.0 Jeff Dike
2004-01-19  7:53           ` Ingo Molnar
2004-01-19  8:28             ` Ingo Molnar
2004-01-20  0:19               ` M A Young
2004-01-20  0:23                 ` Ingo Molnar
2004-01-20  0:41                   ` M A Young
2004-01-23 21:52                   ` [uml-devel] tt mode tls/glibc crash with 2.6 (Was: Re: uml-patch-2.6.0) M A Young
2004-01-23 23:52                     ` [uml-devel] " M A Young
2004-01-24 12:25                       ` M A Young
2004-01-24 18:20                         ` Jeff Dike
2004-01-24 19:31                           ` M A Young
2004-01-28 11:35                             ` Ingo Molnar
2004-02-05 12:30                             ` Ingo Molnar
2004-02-05 12:45                               ` M A Young
2004-02-05 13:13                                 ` Ingo Molnar
2004-02-05 13:28                                   ` M A Young
2004-02-05 18:36                                 ` Ingo Molnar
2004-02-05 19:15                                   ` M A Young
2004-02-05 19:22                                     ` Ingo Molnar
2004-02-05 19:15                                   ` Ingo Molnar
2004-02-05 19:50                                     ` Ingo Molnar
2004-02-06  7:42                                       ` Ingo Molnar
2004-01-20  1:27                 ` [uml-devel] Re: uml-patch-2.6.0 Jeff Dike
2004-01-20 17:22               ` Jeff Dike
2004-01-20 19:59                 ` Ingo Molnar
2004-01-17 19:09 ` [uml-devel] uml-patch-2.6.0 BlaisorBlade
2004-01-17 19:51   ` Jeff Dike
2004-01-18 13:49     ` Ingo Molnar
2004-01-18 13:58       ` [uml-devel] uml-patch-2.6.1-1: VFS: Cannot open root device "ubd0" or unknown-block(0, 0) Ingo Molnar
2004-01-18 14:04         ` [uml-devel] " Ingo Molnar
2004-01-18 23:48           ` Jeff Dike
2004-01-17 20:32   ` [uml-devel] uml-patch-2.6.0 M A Young
2004-01-19 17:06   ` [uml-devel] uml-patch-2.6.0 Gerd Knorr
2004-01-20 19:42     ` BlaisorBlade [this message]
2004-01-20 21:30       ` Gerd Knorr
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18 18:46 M A Young

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=200401202042.17851.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=kraxel@bytesex.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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