linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Alexander Newald <alexander@newald.de>
Subject: Re: [uml-devel] Kernel 2.6.1 uml 2.6.1-1 build failed with module support
Date: Sat, 31 Jan 2004 17:03:37 +0100	[thread overview]
Message-ID: <200401311703.37848.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <028501c3e1e2$aefcd6d0$6f01a8c0@alex>

Alle 19:57, venerdì 23 gennaio 2004, Alexander Newald ha scritto:
> Hello,

> I've updated to the latest uml patch,
> enabled module support
For now disable module support. That does not work in the releases on the site 
(yet).
The needed patches have already been written and will be included in the next 
release, so you can wait for that (but *disable CONFIG_MODVERSIONS* with 
that).

Or you can try this URL:
http://web.tiscali.it/no-redirect-tiscali/blaisorblade/linux/archives/UML/2.6.1-v1/

use the combo -v1 from that page. If you want absolutely to use the split 
patches, take at least the C-02 and G-02 ones.

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-31 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 18:57 [uml-devel] Kernel 2.6.1 uml 2.6.1-1 build failed with module support Alexander Newald
2004-01-31 16:03 ` BlaisorBlade [this message]

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=200401311703.37848.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=alexander@newald.de \
    --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