All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter <p.spamcatcher@rimuhosting.com>
To: Nils Toedtmann <user-mode-linux-user@nils.toedtmann.net>
Cc: UML user list <user-mode-linux-user@lists.sourceforge.net>,
	xen-devel@lists.sourceforge.net
Subject: Re: [uml-user] NPTL/db4 problem with FC3
Date: Tue, 22 Mar 2005 16:27:49 +1200	[thread overview]
Message-ID: <423F9EC5.1030003@rimuhosting.com> (raw)
In-Reply-To: <1111437260.6437.26.camel@crusher.takatukaland.de>

(Me Too ++: I'm running into the same issues with a non-nptl DB4 and rpm 
on rhel4)

And making it even more interesting:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/as-x86/

"Red Hat Enterprise Linux 5 will no longer include support for 
LinuxThreads. Therefore, applications that require LinuxThreads support 
must be updated before they will be able to work properly on a Red Hat 
Enterprise Linux 5 system."

I would appreciate a description of what needs to be done in order for 
xen or UML to support the use of nptl inside the guest server.  And any 
info on progress towards trying to support it.

Regards, Peter

Nils Toedtmann wrote:
> This is a cross post to <xen-devel@lists.sourceforge.net> and <user-
> mode-linux-user@lists.sourceforge.net>
> 
> 
> Dear lists,
> 
> Anybody successfully running cyrus-imapd in FC2/3+Xen/UML? When i tried
> to run cyrus-imapd in a virtual FC3 (Xen or UML) i got lot's of
> 
>   DBERROR db4: Berkeley DB library configured to support only
>                DB_PRIVATE environments
>   DBERROR: dbenv->open '/var/lib/imap/db' failed: Invalid argument
>   DBERROR: init() on berkeley
> 
> It turned out to be a FC specific db4 problem with non-NPTL-aware
> ARCHes:
> 
>   <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91933>
> 
> Unfortunatly, RedHat closed this bug as WONTFIX, but it's still present
> with FC3 on ARCH={xen,um}. /lib/tls and /usr/lib/tls moved away, the
> LD_ASSUME_KERNEL workaround does not help, too.
> 
> So i followed the way of Radu Greab and rebuilt db4 using his patches
> and specfile
> 
>   <https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=100060>
> 
> It was tricky, but worked. As this is an ugly workaround (eg it bombs
> with apt/yum updating) i look for a better solution. 
> 
> Anybody?
> 
> /nils.
> --
> no sig
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> User-mode-linux-user mailing list
> User-mode-linux-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

           reply	other threads:[~2005-03-22  4:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1111437260.6437.26.camel@crusher.takatukaland.de>]

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=423F9EC5.1030003@rimuhosting.com \
    --to=p.spamcatcher@rimuhosting.com \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    --cc=user-mode-linux-user@nils.toedtmann.net \
    --cc=xen-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 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.