From: Nelson Castillo <nelsoneci@gmail.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] 2.6.13 / cannot set up LDT for thread-local storage
Date: Fri, 16 Sep 2005 08:01:07 -0500 [thread overview]
Message-ID: <2accc2ff050916060122acc08b@mail.gmail.com> (raw)
In-Reply-To: <2accc2ff0509160423743a1ed6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On 9/16/05, Nelson Castillo <nelsoneci@gmail.com> wrote:
> On 9/13/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
> sysvinit should have a way to add a variable to the
> environment. Can it be done in intitab?
I just fixed the patch for the FAQ. It's much simpler
(and correct, I hope) now.
-------------
I tried with the patched init/main.c and:
inittab:
1:2345:respawn:/usr/bin/env LD_ASSUME_KERNEL=2.4.1 /sbin/getty 38400 tty1
(w/o the LD_ASSUME_KERNEL=2.4.1 the entry in
/etc/environment).
And it dies just after I log in, but I don't get a panic,
just another password prompt. So I guess it's bash
who is not taking the environment that /sbin/init
sets...
And that's why things work when I set
the variable in "/etc/environment"
(and also send a modified environment to
/sbin/init .... with LD_ASSUME_KERNEL=2.4.1.
You must do both, I said that setting
/etc/environment was enough in my previous
email and I was quite wrong. Sorry).
Regards.
--
Homepage : http://geocities.com/arhuaco
The first principle is that you must not fool yourself
and you are the easiest person to fool.
-- Richard Feynman.
[-- Attachment #2: faq.html.patch --]
[-- Type: text/x-patch, Size: 1226 bytes --]
538a539,574
> <a name="kernel Panic, cannot set up thread-local storage"/><table width="100%" bgcolor="#e0e0e0">
> <tr>
> <td>
> <b>
> <font color="black">kernel Panic, cannot set up thread-local storage</font>
> </b>
> </td>
> </tr>
> </table>
> <blockquote>
> Your UML kernel doesn't support Native Posix Thread Library and the binaries
> you're running are being dynamically linked to the NTPL libraries.
> <br><br>
> You can boot moving the NTPL libraries away.
> <ul>
> <li> <font color="black"># mount root_fs mnt-uml/ -o loop</font>
> <li> <font color="black"># mv mnt-uml/lib/tls mnt-uml/lib/tls.away</font>
> <li> <font color="black"># umount mnt-uml</font>
> </ul>
> If you're running Debian, you might prefer to use dpkg-divert.
> <pre><font color="black">
> # export LD_ASSUME_KERNEL=2.4.1
> # mount root_fs mnt-uml/ -o loop
> # chroot mnt-uml
> # mkdir /lib/tls.off
> # cd /lib/tls
> # pwd
> # for f in *;
> do
> dpkg-divert --divert --local --rename --divert /lib/tls.off/$f --add /lib/tls/$f;
> done
> # exit
> # umount mnt-uml
> </font></pre>
> </blockquote>
>
next prev parent reply other threads:[~2005-09-16 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2accc2ff0509111117747e8639@mail.gmail.com>
[not found] ` <200509131952.22631.blaisorblade@yahoo.it>
2005-09-16 11:23 ` [uml-devel] Re: [uml-user] 2.6.13 / cannot set up LDT for thread-local storage Nelson Castillo
2005-09-16 13:01 ` Nelson Castillo [this message]
2005-09-16 20:01 ` Rob Landley
2005-09-16 19:04 ` Blaisorblade
2005-09-16 20:53 ` Henrik Nordstrom
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=2accc2ff050916060122acc08b@mail.gmail.com \
--to=nelsoneci@gmail.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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