Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Mark Hatle : util-linux: use new update-alternatives
Date: Thu, 28 Jun 2012 15:32:07 -0500	[thread overview]
Message-ID: <4FECBF47.2000209@windriver.com> (raw)
In-Reply-To: <20120628200607.GA3961@jama.jama.net>

On 6/28/12 3:06 PM, Martin Jansa wrote:
> On Thu, Jun 28, 2012 at 02:43:28PM -0500, Mark Hatle wrote:
>> On 6/28/12 2:12 PM, Martin Jansa wrote:
>>> On Wed, May 30, 2012 at 11:05:32AM +0000, git@git.openembedded.org wrote:
>>>> Module: openembedded-core.git
>>>> Branch: master
>>>> Commit: 55c01de28a28a4cfe16d36663c190a874ef2e85d
>>>> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=55c01de28a28a4cfe16d36663c190a874ef2e85d
>>>>
>>>> Author: Mark Hatle <mark.hatle@windriver.com>
>>>> Date:   Mon May 21 12:42:34 2012 -0500
>>>>
>>>> util-linux: use new update-alternatives
>>>>
>>>> In addition to switching to the new update-alternatives, it was discovered
>>>> that the sln, shutdown, halt, reboot and related commands were never generated.
>>>> Remove these from the list.  (These appear to have been removed from util-linux
>>>> some time ago.)
>>>>
>>>> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>>>
>>> This seems to break u-a for reset while upgrading from older image:
>>>
>>> update-alternatives: Error: cannot register alternative reset to
>>> /bin/reset since it is already registered to /usr/bin/reset
>>
>> Can you figure out what registered it as /usr/bin/reset?  As far as I'm aware
>> the reset command should be in /bin...  (Sounds like this may simply be an
>> ordering thing.)
>
> seems like busybox did..
>
> SHR root@Nokia-N900 / $ cat /var/lib/opkg/alternatives/reset
> /usr/bin/reset
> ../../bin/busybox 50

Is that the current busybox?  If so, then util-linux is incorrect.  It should be 
matching the behavior of busybox -- unless of course busybox has a bug.  ;)


But when I set this up originally, the intent was to follow what BB was doing.

--Mark

> Cheers,
>
>>
>> --Mark
>>
>>> anyone seen it too?
>>>
>>> Cheers,
>>>
>>>>
>>>> ---
>>>>
>>>>    meta/recipes-core/util-linux/util-linux.inc       |  212 +++++----------------
>>>>    meta/recipes-core/util-linux/util-linux_2.21.1.bb |    2 +-
>>>>    2 files changed, 45 insertions(+), 169 deletions(-)
>>>>
>>>> Diff:   http://git.openembedded.org/?p=openembedded-core.git/?a=commitdiff;h=55c01de28a28a4cfe16d36663c190a874ef2e85d
>>>>
>>>> _______________________________________________
>>>> Openembedded-commits mailing list
>>>> Openembedded-commits@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
>>>
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>





  reply	other threads:[~2012-06-28 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120530110534.15D7110219@opal>
2012-06-28 19:12 ` [oe-commits] Mark Hatle : util-linux: use new update-alternatives Martin Jansa
2012-06-28 19:43   ` Mark Hatle
2012-06-28 20:06     ` Martin Jansa
2012-06-28 20:32       ` Mark Hatle [this message]
2012-06-28 20:52         ` Martin Jansa
2012-07-20 10:49   ` [PATCH] util-linux: register reset u-a to bindir like busybox does Martin Jansa
2012-07-21  0:22     ` Saul Wold

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=4FECBF47.2000209@windriver.com \
    --to=mark.hatle@windriver.com \
    --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