1 |
On Wed, Oct 25, 2017 at 9:45 PM, Andrew Lowe <agl@×××××××.au> wrote: |
2 |
|
3 |
> On 25/10/17 11:28, Andrew Lowe wrote: |
4 |
> > Hi all, |
5 |
> > My machine went feral which resulted in me having to kill the power |
6 |
> > to kill it. Upon reboot everything looked good, fsck did it's job, |
7 |
> > [ok]'s scrolled up the screen etc and then I got the login prompt. I |
8 |
> > entered my username & password and then the fun began. |
9 |
> > |
10 |
> > I got: |
11 |
> > |
12 |
> > -bash: .: /etc/profile.env: cannot execute binary file |
13 |
> > |
14 |
> > If I tried any command, say ls, I got: |
15 |
> > |
16 |
> > -bash: ls: no such file or dir |
17 |
> > |
18 |
> > I've now rebooted the machine using a relatively recent sysrescueCD |
19 |
> > and had a look at profile.env and it's binary but I thought it should |
20 |
> > have been text!!!! In the top line or so it mentions "ld" for some |
21 |
> > reason. I checked the same file on the boot disk and it's text. One or |
22 |
> > two I found on line are also text. |
23 |
> > |
24 |
> > Does anyone have any idea as to what's going on here? Should I just |
25 |
> > grab the profile.env from the boot disk and drop it into the /etc dir? |
26 |
> > Or should I go through the whole process of chroot off a gentoo disc and |
27 |
> > then run env-update as it says in the header of the text versions I'v |
28 |
> seen? |
29 |
> > |
30 |
> > Thoughts greatly appreciated, |
31 |
> > |
32 |
> > Andrew |
33 |
> > |
34 |
> > |
35 |
> |
36 |
> Well, I managed to work this out. I grabbed profile.env from a |
37 |
> laptop |
38 |
> running gentoo and using sysrescuecd booted the desktop and dropped |
39 |
> profile.env into it's /etc dir. Fiddled the permissions and rebooted. |
40 |
> This time after the reboot, it only told me that it couldn't find |
41 |
> commands, ls, cd etc. Obviously pathing wasn't working. I found out |
42 |
> where env-update lived, /usr/sbin/env-update, providing the full path to |
43 |
> it, ran it then kicked over into another terminal, logged in and hey |
44 |
> presto, things are good. A reboot and this was confirmed. |
45 |
> |
46 |
> The cause - I have no idea. It now works so I'm happy. Thanks for |
47 |
> the |
48 |
> suggestions people provided, |
49 |
> |
50 |
> Andrew |
51 |
> |
52 |
> |
53 |
Posting your query on the gentoo-portage-dev mailing list might get you a |
54 |
more informed response as to why this happened in the first place. |