All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Zeimetz <bernd@bzed.de>
To: sparclinux@vger.kernel.org
Subject: Re: unkillable dpkg-query processes
Date: Tue, 30 Oct 2007 00:47:33 +0000	[thread overview]
Message-ID: <47267F25.2090501@bzed.de> (raw)
In-Reply-To: <20071024223332.GA24557@keid.carnet.hr>


> 	mount -t devpts none /dev/pts

mount --bind /dev /thechroot/dev
is what I use here, running udev in a chroot is no fun.

> So, it's a lot more than just running the appropriate debootstrap
> command.

I'm almost done with a howto which is cut&paste for 95% to debootstrap
and boot a debian system, unfortunately it doesn't boot as the klibc
(which is used in the initramfs) is broken on sparc again...
So I'll modify it to setup a proper chroot only, it should also allow to
boot into it if you use the Kernel/initrd form Ubuntu.
This should allow Josip and you to setup a complete chroot.

> I have done a GCC package build and am now running a libc6 build under
> this lenny chroot and haven't hit any problems yet.

The following things also like to crash here (on Etch, not in a chroot):
- running aptitude -u several times (at least with libnss-db installed)
- since I've installed 2.6.24-rc1: vgdisplay (with and without active
libnss-db)


> BTW, in your buildroot, can you do something like:
> 
> 	strace -o x.log dpkg-query -S libc.so.6

there're some comparisons of the strace of aptitude -u in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bugC3187#102
Probably interesting as there're futexes in the game.

The interesting thing is that it didn't crash the machine while running
under strace.

-- 
Bernd Zeimetz
<bernd@bzed.de>                         <http://bzed.de/>

  parent reply	other threads:[~2007-10-30  0:47 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 22:33 unkillable dpkg-query processes Josip Rodin
2007-10-24 22:58 ` David Miller
2007-10-24 23:28 ` Josip Rodin
2007-10-24 23:36 ` David Miller
2007-10-25  6:41 ` David Miller
2007-10-25 14:58 ` Josip Rodin
2007-10-25 15:07 ` Josip Rodin
2007-10-25 16:43 ` Josip Rodin
2007-10-26 11:30 ` David Miller
2007-10-26 12:23 ` Bernd Zeimetz
2007-10-26 12:30 ` Bernd Zeimetz
2007-10-26 22:01 ` David Miller
2007-10-26 22:30 ` Bernd Zeimetz
2007-10-26 22:32 ` Josip Rodin
2007-10-26 22:33 ` Josip Rodin
2007-10-26 22:37 ` Bernd Zeimetz
2007-10-26 22:40 ` Bernd Zeimetz
2007-10-27 18:09 ` Bernd Zeimetz
2007-10-27 18:46 ` Bernd Zeimetz
2007-10-28  3:03 ` Bernd Zeimetz
2007-10-28  3:40 ` David Miller
2007-10-28  4:24 ` David Miller
2007-10-28 12:20 ` Bernd Zeimetz
2007-10-28 12:58 ` Bernd Zeimetz
2007-10-28 13:02 ` Bernd Zeimetz
2007-10-28 13:38 ` Sébastien Bernard
2007-10-29  0:01 ` Bernd Zeimetz
2007-10-29  0:19 ` Bernd Zeimetz
2007-10-29  0:41 ` David Miller
2007-10-29  1:18 ` Bernd Zeimetz
2007-10-29  1:39 ` David Miller
2007-10-29  2:06 ` Bernd Zeimetz
2007-10-29  2:18 ` David Miller
2007-10-29 12:06 ` seb
2007-10-29 23:37 ` Josip Rodin
2007-10-29 23:45 ` David Miller
2007-10-30  0:30 ` Josip Rodin
2007-10-30  0:47 ` Bernd Zeimetz [this message]
2007-10-30  0:50 ` Bernd Zeimetz
2007-10-30  0:51 ` Bernd Zeimetz
2007-10-30  1:24 ` David Miller
2007-10-30  1:35 ` David Miller
2007-10-30  1:54 ` Bernd Zeimetz
2007-10-30  2:11 ` David Miller
2007-10-30  2:43 ` Bernd Zeimetz
2007-10-30  2:49 ` David Miller
2007-11-01 21:40 ` Josip Rodin
2007-11-01 22:01 ` David Miller
2007-11-01 22:47 ` Bernd Zeimetz
2007-11-02  4:55 ` David Miller
2007-11-02 15:37 ` Bernd Zeimetz
2007-11-02 16:21 ` Josip Rodin
2007-11-04  5:10 ` David Miller
2007-11-04  8:07 ` David Miller
2007-11-04 19:55 ` Bernd Zeimetz
2007-11-04 21:51 ` David Miller
2007-11-04 23:14 ` Bernd Zeimetz
2007-11-05  0:03 ` Bernd Zeimetz
2007-11-06  3:51 ` Bernd Zeimetz
2007-11-06 11:13 ` David Miller
2007-11-06 13:30 ` Bernd Zeimetz

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=47267F25.2090501@bzed.de \
    --to=bernd@bzed.de \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.