Hi thanks it's good to be here!
@both repliers: Yes sorry I ommitted that the home dir files ended up in / but I just moved them back (no filename conflicts with original /* stuff).
@Tinkster: it seemed to work, in that it moved everything from that folder back into /, I could see that with an ls -lA.
My issue is just I am scared that if I reboot it (soon or in the far future) it may not come back up becuase of something I overlooked/do not know about like proc files etc I have no idea really which is why I asked here where I consider there are some people who know a lot more than me about Linux files and the boot process/ssh requirements etc.
The host does not back up this machine automatically, that's down to us really (it is backed up, I would just rather it not have downtime).
I think I executed ld-2.11.3.so because the original fix command
I found on the forum did not work, becuase the executable was a symlink:
/lib/ld-linux.so.2 -> /lib32/ld-linux.so.2
It gave me an error and I shat myself becuase I did not know what it would be called, I had no working ls.
So in desperation and thinking the system is dead for sure, why not try:
srv:/home/username# /home/username/lib/ld-*.so --library-path /home/username/lib /home/username/bin/mv /home/username/* /
Which seemed to work (I am not assuming of course, hence this original post).
So overall, any tips to make sure it will boot and run net & sssh etc?
I know that's vague but is there like a checklist or a command I can run to test bootup files/scripts etc or anything?
If not I'll probably reboot it & prepare for the worst at the weekend when there's less load on it to see/fix.