All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: leimaohui <leimaohui@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1]udev_182: creat a symbolic file /sbin/udevadm to fix haldaemon starts error.
Date: Mon, 23 Sep 2013 08:34:27 -0700	[thread overview]
Message-ID: <52405F83.8020205@linux.intel.com> (raw)
In-Reply-To: <00d501ceb5e6$ad9064f0$08b12ed0$@cn.fujitsu.com>

On 09/20/2013 02:49 AM, leimaohui wrote:
> On 20 September 2013 4:38 PM, Burton, Ross [mailto:ross.burton@intel.com] wrote:
>> On 20 September 2013 07:46, leimaohui <leimaohui@cn.fujitsu.com> wrote:
>>> The haldaemon requires /sbin/udevadm to start.
>>> So creat a symbolic file  /sbin/udevadm that links to /usr/bin/udevadm.
>>
>> Why not fix haldaemon to use the right path?
>
> But  according to  udev's changlog,I think it is better to add a symlink to
> udevadm.
>
> http://upstream-tracker.org/changelogs/libudev/182/changelog.html
>
> " The default install location of the 'udevadm' tool moved from 'sbin'
> to /usr/bin. Some tools expect udevadm in 'sbin', a symlink to udevadm
> needs to be manually created if needed, or --bindir=/sbin be specified."
>
As suggested by Ross, please patch haldaemon to use the the oecore location.

Thanks
	Sau!

> Best Regards,
> Maohui Lei
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


      reply	other threads:[~2013-09-23 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20  6:46 [PATCH 1/1]udev_182: creat a symbolic file /sbin/udevadm to fix haldaemon starts error leimaohui
2013-09-20  8:37 ` Burton, Ross
2013-09-20  9:49   ` leimaohui
2013-09-23 15:34     ` Saul Wold [this message]

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=52405F83.8020205@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=leimaohui@cn.fujitsu.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 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.