| 1 |
On Wed, Jan 21, 2015 at 9:28 AM, Douglas J Hunley <doug.hunley@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Tue, Jan 20, 2015 at 5:43 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 4 |
>> |
| 5 |
>> Maybe you can add a response to my bug report here? |
| 6 |
>> |
| 7 |
>> https://bugs.gentoo.org/show_bug.cgi?id=536988 |
| 8 |
> |
| 9 |
> |
| 10 |
> I have the same issue and my comment would look almost exactly like |
| 11 |
> bitlord's comment on that bug. To fix it, I changed: |
| 12 |
> mount -t proc none /proc |
| 13 |
> to: |
| 14 |
> busybox mount -t proc none /proc |
| 15 |
> |
| 16 |
> and the problem went away. However, I don't think that should be needed as |
| 17 |
> the script is run by #!/bin/busybox |
| 18 |
> |
| 19 |
|
| 20 |
For those not following the bug report there was a change introduced |
| 21 |
by the busybox package maintainer wherein the 1.21 ebuild changed from |
| 22 |
allyesconfig to defconfig. I never used 1.21 so I didn't see it until |
| 23 |
we got a stable upgrade. |
| 24 |
|
| 25 |
The change I made was adding |
| 26 |
|
| 27 |
/bin/busybox --install -s |
| 28 |
|
| 29 |
immediately before my mount commands. Please note that without the |
| 30 |
explicit /bin/busybox the busybox binary wasn't found and nothing was |
| 31 |
fixed. |
| 32 |
|
| 33 |
Thanks for your help. |
| 34 |
|
| 35 |
Cheers, |
| 36 |
Mark |
Archives