You are not logged in.
Pages: 1
Hello everyone, i'm new here as you can see and i have a quite simple question.
I use archlinux to patching Apple MacBook Pros with failing GPU's. Mostly the GPU still works and i can see something on the screen. But now I have one here not showing any sign of screen output. So i thought about remote SSH. First i checked the MacBook is working with an OSX installation with remote access and yes, i could take the screen of it an do some stuff.
So now i tried SSH from another computer to the failing MacBook Pro. I made a USB stick using this manual: https://realmacmods.com/macbook-2011-ra … u-disable/ and bootet from it. But when i try to connect via SSH i get the message: ssh: connect to host 192.168.1.193 port 22: Connection refused
So after some googling i found to edit the /etc/ssh/sshd_config, done that, reboot.... and the changes are gone. So somehow it wont save the changes i made to the stick. What did i do wrong? Is the USB installation read only? What can i do to make the changes permanent?
Also tried to save some new files to the stick, but also after a reboot they are gone.
Offline
Welcome to the boards, see the following wiki article on how to make a proper installation on an USB key:
Offline
I made a USB stick using this manual: https://realmacmods.com/macbook-2011-ra … u-disable/ and bootet from it. But when i try to connect via SSH i get the message: ssh: connect to host 192.168.1.193 port 22: Connection refused
That's all exactly as expected. You've just created a standard installation USB which doesn't have ssh enabled.
So after some googling i found to edit the /etc/ssh/sshd_config, done that, reboot.... and the changes are gone. So somehow it wont save the changes i made to the stick. What did i do wrong? Is the USB installation read only? What can i do to make the changes permanent?
Also tried to save some new files to the stick, but also after a reboot they are gone.
You haven't done anything wrong, the standard installation USB that you've created runs from a read-only filesystem, all changes you make happen in RAM and are lost when you reboot.
In your case though there is no need to reboot just to force sshd to reload its configuration, as it isn't even started you can just run...
systemctl start sshdafter making your config changes.
Bear in mind that you'll also need to set a password for the root user before being able to ssh in...
https://wiki.archlinux.org/index.php/Install_from_SSH
Offline
Pages: 1