[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
RE: Broken System After Update[Solved]
To
: <
debian-user@lists.debian.org
>
Subject
: RE: Broken System After Update[Solved]
From
: Ogya Chief <
ogyachief@hotmail.com
>
Date
: Sun, 5 Feb 2012 16:16:51 +0200
Message-id
: <
[🔎]
BAY163-W14AB1F4FC33EEADC634CA5BE770@phx.gbl
>
In-reply-to
: <
[🔎]
BAY163-W6F0694A7C8D3F76CE8F13BE770@phx.gbl
>
References
: <
[🔎]
BAY163-W2784638246437A831B0796BE760@phx.gbl
>,<
[🔎]
20120205004813.GB31606@hysteria.proulx.com
>,<
[🔎]
BAY163-W61E18B6F8A568BB0B76271BE770@phx.gbl
>,<
[🔎]
CAJPUTwh4p8GnoawE0MXSFbg6z=5dYdEBh6xiY-sfV=ArkBW1pQ@mail.gmail.com
>,<
[🔎]
BAY163-W6F0694A7C8D3F76CE8F13BE770@phx.gbl
>
Hi There,
I found a solution by Michael Tokarev which addressed BusyBox bug# 646284. It required updating BusyBox and running update-initramfs in a chroot environment.
Thank you all for your suggestions.
Regards,
Ogya
Reply to:
debian-user@lists.debian.org
Ogya Chief (on-list)
Ogya Chief (off-list)
References
:
Broken System After Update
From:
Ogya Chief <ogyachief@hotmail.com>
Re: Broken System After Update
From:
Bob Proulx <bob@proulx.com>
RE: Broken System After Update
From:
Ogya Chief <ogyachief@hotmail.com>
Re: Broken System After Update
From:
Carlo Borelli <carlo.borelli@gmail.com>
RE: Broken System After Update
From:
Ogya Chief <ogyachief@hotmail.com>
Prev by Date:
[OT] Re: GNU/Debian Linux vs. facebook, Twitter and other proprietary social media
Next by Date:
Re: accounting software
Previous by thread:
RE: Broken System After Update
Next by thread:
Regression when I try to get connected to a network server
Index(es):
Date
Thread