• 0 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: August 24th, 2023

help-circle


  • Well, it seemed from your comment that you just expected this to work without tinkering. However, now you admit to be tinkering? This is a rather confusing story. When I’m tinkering, I’m exploring and expecting to run into edge cases or unsupported environments. Linux may be great, but it’s just a kernel with GNU on top to help build the larger OS. I believe the attitude towards linux is a bit misguided. It is a great tool, and its strengths mainly lie in the freedom of usage that allows for both fine-tune control and automatibility. I say windows and MacOS are strictly non automatable environments unless you venture into the developer side, and that will undoubtedly bring some with it some problems. As such, many systems that require the user to be more hands off and operate with high uptime will use Linux kernels. Being able to automate the process with minimal user input is essential in the performance and reliability of critical systems demand.

    Again, I did not wish to be condemning your actions and rather alert you to the differing problems these tools are made to solve. MacOs and thereby its hardware was geared towards being an apple only product that is only properly supported by apple, and the problem it solves is to be a tool for rich and self-conscious individuals.

    Windows was created to be a home and enterprise OS that can be used in almost any system that is quite an outstanding feat, but it really is because of the number of developers and users offer the ability for things to work. Mind you that even Windows was not made to be extremely automatable. yet there are tools being created to offer automating tasks, but many are closed source and tied to requiring funding. I even ran into some odd issues every once in a while.

    Linux was expressly made to be a minimal system that offered high uptime and high automatibility that was free for everyone to contribute or use. This allows users and admins to set up their systems to be more hands-off when it came to tasks that were extremely time-consuming or continually have to be worked on without deadline while keeping costs low. It is just recently that Linux-based distributions are able to make use of features and packages that are geared to users who need to make manual tasks. Wayland is finally being more stable, driver support from large manufacturers, and even emulation of Windows APIs with use of proton/wine is getting better. Thus offering users the ability to do manual tasks and mix custom made automated scripts/tools into their environments.

    Many see the hype and equate it to being able to use Linux systems like they did with the very much well funded manual systems that Windows and MacOS offered. Instead, Linux is just a tool and can be useful when it is needed.


  • You tried to install a non apple approved software(being the entire OS) on a Mac system. Imagine how hard it is for linux developers to support this blackbox hardware configuration?

    Try using something actually easier to program/use for running linux type OSes. I usually will suggest AMD.

    If you need a strong graphics card on a laptop, I think those frameworks will be more than capable of offering that kind of flexibility. The potential of packing it up so that if you feel like the power-hungry gpu will take too much battery, then it can be flexible in allowing you to remove the gpu without thinking about a screwdriver

    If you need ARM, then you should be mindful of the fact that the arm ecosystem is still quite new for pc users. There are not many software choices, but it does show some promise.

    If you think you need Mac hardware, then you don’t need to go around throwing linux on it. MacOS is already Unix like. You are going to live with the fact that no one outside of apple will have proper hardware support at the OS level. Let alone driver support.










  • Yes, but I usually add my public key to the authorized_keys file and turn off password authentication once i do login with a password. On top of that, I have a sshpass one line command that takes care of this for me. It’s much easier than trying to manually type a password for the next time. I save it and just run it every time I think about using password login. Next time I need to ssh, I know the password login is not necessary.

    sshpass -p ‘PASSWORD’ ssh USER@IP.ADDRESS “echo ‘`cat ~/.ssh/id_rsa.pub`’ > ~/.ssh/authorized_keys && echo ‘Match User !root
    PasswordAuthentication no
    Match all’ > /etc/ssh/sshd_config’ && exit” && ssh USER@IP.ADDRESS

    At the next reboot, your system will now only accept key logins, except for root. I hope the root user password is secure. I don’t require it for root because if a hacker does gain shell access, a password(or priv esc exploit) is all they need to gain root shell. It is also a safety net in case you need to login and lost your private key.