Lately ive noticed that i was wanting to do certain things on Windows that just seemed much easier and more intuitive on Linux, based in the OS specific solutions i would see to problems i encountered. And i was more frequently using software where Windows support seemed like an after thought.

A couple days ago i finally sat down and tried to install Mint. The installer didnt recognize my windows partition so it didnt offer any assistance. And a stroke of fate saw my internet connection dieing at the exact same time. Yes, i cant believe it either.

So i decided to live dangerously and just try to wing the installation with no outside help. It seems like creating a second EFI partition was not the right call. The install failed, and I couldn’t get back onto windows.

I wound up just using a live ubuntu image for a few days while i wrestled with repairing the boot loader. I didnt succeed. Eventually i just made a windows recovery disk from my Desktop with an intact copy of windows, and had to reinstall windows.

Then i did manage to successfully install Debian, and ive been having such a great time with it so far. I feel like i probably didnt even need to keep a windows partition, especially since i could have just used my desktop if i REALLY needed windows. I havent had this much fun just using the computer since i was a kid.

    • Tempy@lemmy.temporus.me
      7·
      10 months ago

      I mean for most Linux derivatives, getting SSH setup for outgoing connections is usually install the openssh package from your distros repos, though I imagine many preinstall it, no reboot should be necessary, and you just type ssh user@hostname into a terminal to connect to the remote ssh server to access stuff on that computer. There shouldn’t be a need to reboot for installing app that’s not a service.

      Wanting to enable ssh access to the computer you are using so a remote client can connect to it? Well the same openssh package should have come with sshd which acts as the server to allow remote ssh client to connect. It’d probably need enabling (so it’s run automatically on boot) and starting (so you don’t have to reboot to have it going), on distributions using systemd that’s usually just systemctl enable sshd.service (which makes sure the sshd daemon will be started on next boot) followed by systemctl start sshd.service to start it immediately so it’s running straight away, (or systemctl enable sshd.service --now to roll both steps into one).