Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Regression bug: dbus messagebus user generation is wrong
Date: Thu, 22 Dec 2011 12:04:36 +0000	[thread overview]
Message-ID: <1324555476.24604.9.camel@ted> (raw)
In-Reply-To: <ABF02F6F-B5D0-425E-A568-B762D28A22D9@dominion.thruhere.net>

On Thu, 2011-12-22 at 11:26 +0100, Koen Kooi wrote:
> Op 22 dec. 2011, om 10:10 heeft Martin Jansa het volgende geschreven:
> 
> > On Thu, Dec 22, 2011 at 09:49:01AM +0100, Bernhard Guillon wrote:
> >> Hi all,
> >> we switched the way we chown /usr/libexec/dbus-daemon-launch-helper
> >> with this commit:
> >> 
> >> commit 46e6c3fa8034b12d178d605f3f5d7efe69671a13
> >> Author: Otavio Salvador <otavio@ossystems.com.br>
> >> Date:   Fri Oct 21 02:49:51 2011 +0000
> >> 
> >>     dbus: use useradd class to allow use in read-only filesystems
> >> 
> >>     Move creation of required user/groups to useradd class thus allowing
> >>     use with read-only filesystems and booting the initial boot.
> >> 
> >>     Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >> 
> >> 
> >> We changed the owner ship of the user on the device before this commit. 
> >> Now we change the owner ship on build time which is wrong. If we change 
> >> the owner ship on buildtime we cannot know the gid of the messagebus 
> >> group. On my system it is e.g 117 but on my targtet it is 997. There is no 
> >> standard mapping for gid to names so we need to switch back to change the 
> >> group on the device.
> > 
> > See http://bugzilla.pokylinux.org/show_bug.cgi?id=1711
> > but it's still broken in some cases (on my buildhost 3 from 5 machines
> > are broken, 2 are working after last opkg changes).
> > 
> > Good test is to enable testlab and run this in your deploy/images directory
> > find . ! -type l -name \*tar.gz`; do 
> >  echo $i; 
> >  tar -tvf $i | grep dbus-daemon-launch; 
> >  tar --numeric-owner -tvf $i | grep dbus-daemon-launch; 
> >  tar xzvpf $i ./etc/group; 
> >  grep messagebus ./etc/group; 
> > done | tee -a image.test
> > 
> > And working image needs to have not only messagebus as owner but also
> > matching GID in 2nd line and last line from packaged /etc/group. With
> > latest opkg fixes it seems to work, but only if there is messagebus in
> > packaged /etc/group at all, reported here:
> > http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014619.html
> > but probably got lost in other issues with new opkg, like this one
> > http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014654.html
> > (if D is not needed to be set from opkg then why was offlineroot_varname.patch
> > added in first place? and I have updated this after
> > offlineroot_varname.patch removal and new version is in shr branch)
> > 
> >> I can send a patch which reenables the postinstall owner ship change if 
> >> you like.
> > 
> > Such patch is already on ML from me, now I'm using .bbappend from my
> > layer 
> > http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=c08dfd5f5559902f6966648f75d6c6bfd2597a5b
> 
> I'm willing to put that into meta-oe till the problem is 100% fixed.

What I really need is help in understanding what is still breaking. If
someone can show me where things are going wrong I can help (and have
done so) but "there is a problem somewhere" isn't going to help get this
fixed :(

Cheers,

Richard




  reply	other threads:[~2011-12-22 12:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  8:49 Regression bug: dbus messagebus user generation is wrong Bernhard Guillon
2011-12-22  9:02 ` Richard Purdie
2011-12-22  9:10 ` Martin Jansa
2011-12-22 10:06   ` Bernhard Guillon
2011-12-22 10:26   ` Koen Kooi
2011-12-22 12:04     ` Richard Purdie [this message]
2011-12-22 12:08   ` Richard Purdie
2011-12-22 13:17   ` Martin Jansa
2011-12-22 15:52     ` Mark Hatle
2011-12-22 16:10       ` Martin Jansa
2011-12-22 18:02       ` Richard Purdie

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=1324555476.24604.9.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox