From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: chattr not found?
Date: Mon, 17 Jan 2011 10:44:03 +0100 [thread overview]
Message-ID: <4D340F63.60505@nedap.com> (raw)
In-Reply-To: <4D305F0D.4000107@mentor.com>
Tim,
Thanks!
But...
at boot I get:
update-alternatives: Error: cannot register alternative chattr to
/usr/bin/chattr since it is already registered to /bin/chattr
Not a big deal, I guess...
Jaap
On 01/14/2011 03:34 PM, Tom Rini wrote:
> On 01/14/2011 02:57 AM, Jaap de Jong wrote:
>> Hi All!
>>
>> for some reason chattr is linked to chattr.e2fsprogs instead of
>> ../usr/bin/chattr.e2fsprogs
>>
>> # ls -l /bin/chattr*
>> lrwxrwxrwx 1 root root 16 2011-01-14 10:37 /bin/chattr -> chattr.e2fsprogs
>>
>> # ls -l /usr/bin/chattr*
>> -rwxr-xr-x 1 root root 7304 2010-12-10 01:12 /usr/bin/chattr.e2fsprogs
>>
>> I have no time to investigate this.
>> Look simple...
> I'm pushing a fix for this now, thanks for the report.
>
next prev parent reply other threads:[~2011-01-17 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 9:57 chattr not found? Jaap de Jong
2011-01-14 14:34 ` Tom Rini
2011-01-17 9:44 ` Jaap de Jong [this message]
2011-01-17 15:13 ` Tom Rini
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=4D340F63.60505@nedap.com \
--to=jaap.dejong@nedap.com \
--cc=openembedded-devel@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