If you have this version of opkg 0.1.6+svnr522-r19* and seen busybox upgrade

Then your image won't probably start after reboot!

There is fix for it already
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=09a79a497f9c362bf899a8be2295178c3ed18836
so if you'll see upgrade from 0.1.6+svnr446* to 0.1.6+svnr522-r20.4 then you're 
probably safe

How to check/fix this manually:

* if there is link /usr/lib/ipkg -> /usr/lib/opkg, then merger will
  create backups of "both" alternatives directories, but they will be
  both the same /usr/lib/opkg/alternatives, then it will try to merge
  with output that every file is the same, sofar no real harm.
* Problem is after successfull merge, when it removes
  /usr/lib/ipkg/alternatives which is in this case the right
  alternatives in opkg :/
* If you've already this problem on your target then

*   # Check that /usr/lib/ipkg is really link to /usr/lib/opkg
    # That /usr/lib/opkg/alternatives is almost empty or the files there
    # have usually less lines than /usr/lib/opkg/alternatives-backup
    # equivalents

This is right one:
cat /usr/lib/opkg/alternatives/init
/sbin/init
../bin/busybox 50
/sbin/init.sysvinit 60

Bad one doesn't have sysvinit line

*   # Restore old alternatives
*   rm -rf /usr/lib/opkg/alternatives
*   cp -ra /usr/lib/opkg/alternatives-backup /usr/lib/opkg/alternatives
*
*   # Regenerate links with right alternatives available
*   opkg install -force-reinstall busybox

Sorry for inconvenience

Kind regards,

On Sun, Feb 28, 2010 at 10:21:56PM +1300, Andrew Stephen wrote:
> On Sun, Feb 28, 2010 at 2:05 AM, Joachim Ott <[email protected]> 
> wrote:
> > After a reboot, it kept saying
> >
> > can't open /dev/S
> > can't open dev/z6
> > ...
> >
> > Yes, /sbin/init was a link back to busybox. Luckily I could boot from
> > SD card and link it back to init.sysvinit. And all things in /bin,
> > /sbin, /usr/bin and /usr/sbin, that were linked to coreutils or
> > util-linux-ng are again a link to busybox. This will take some time to
> > cleanup. Whom can I bash with this?
> 
> I had a similar problem, except that boot stalled after the "g_ether"
> warning messages and got no further.  I chose to re-flash mine with
> SHR-U.
> 
> -- 
> Andrew Stephen
> http://www.evil.geek.nz/
> 
> It is absurd to divide people into good and bad. People are either
> charming or tedious.
>   - Oscar Wilde
> _______________________________________________
> Shr-User mailing list
> [email protected]
> http://lists.shr-project.org/mailman/listinfo/shr-user

-- 
uin:136542059                jid:[email protected]
Jansa Martin                 sip:[email protected] 
JaMa                         
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel

Reply via email to