• 12 Posts
  • 199 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle







  • Yeah, I like it too. My only issue is ollama’s lack of intel support. I have been looking at issue 1590 on their GitHub. For now I have a 1050ti in a cardboard box PC with other hardware being 10+ years old and a mixed set of RAM totalling 12G. It also has a 100Mbit nic, so I can’t take advantage of full internet speed when downloading models. The worst part is they can support intel, but haven’t merged the solution because of an issue with the windows intel drivers. Linux is fine but I can 't have it. I wasn’t planning to rant, but I already typed it so… enjoy?







  • HumanPerson@sh.itjust.workstoLinux@lemmy.mlM1 Macbook Air
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    2 months ago

    It’s not great. I have one, and I am able to use it, but there are some issues. Battery life is the main one. It will probably get 6 hours or so of active use, but they don’t have good idle power management, so you don’t get much more by turning it off.

    Their performance isn’t bad. It wasn’t ever all that great though. It was mainly ppw that people liked, and you wouldn’t really get that benefit with asahi because of the previously mentioned power management issues. Newer AMD laptops will absolutely outperform it.

    Another issue that you didn’t ask about, but I feel is worth mentioning: apple’s build quality is bad. On mine, the display flashes pink sometimes. It did this before I ever put asahi on it. There are many reports of other users with the same issue. When I fist noticed it, it only happened once a month or so. Now I notice it 5-10 times a day, and I don’t use it that much (maybe an hour or so a day).

    Also, according to Louis Rossmann, there is a data line next to a power line on the motherboard that can easily be shorted out in humidity. He has pointed out many design issues, and usually they persist for quite some time before apple does anything, if they ever do.

    I know I am coming across as very biased against apple, but keep in mind that I bought one. I thought that M1 was a large step forward in the quality of their products, and thought it was worth it to get one. I was wrong.



  • They said they want a local backup so they don’t have to redownload because bandwidth is expensive. I think a RAID makes more sense. I also don’t think btrfs is a great idea for a boat. Power failures will probably be somewhat common, and btrfs is not the most stable, so I don’t think I would trust it in weird conditions. Documentation is definitely a great idea though.


  • For hardware, I would go with sata ssds for storage. I also would recommend a separate boot drive as it makes re installing without loosing data a breeze. You could go with a new processor from intel or amd, and make sure it has onboard graphics. You should also go into the BIOS, enable xmp (always do that. It’s free performance), and look for power saving settings. You could go for arm, but most arm computers lack expansion options and that can mean you use USB for drives which is unreliable. I think dc atx power supplies are a thing, but I know nothing about them. I would recommend doing ext4 and a raid, ideally 6 or 10. That will give you stability (from filesystem issues) and good reliability. I know RAID is not a backup, but in this case it may be what you want. RAID is for uptime, and it would be able to usually buy you enough time to finish your trip, or you could even have spare drives onboard and fix it while you’re out in like 10 minutes. Also, I would highly recommend researching how to power it well. Starting an engine can mess with the power and could fry a computer. I don’t know if a dc ups is a thing, but if it is, get it.

    For software, use whatever you want, mostly. I always use debian for servers, but proxmox would probably be fine. You can use powertop to make sure it runs efficiently.





  • Openhab is a project like HomeAssistant. Both are basically websites that offer pre made smart home functionaility and can run on your own server. Openhab doesn’t set a password by default (iirc), and when people expose it to the internet they end up with random bored people in another country somewhere flipping their lights on and off or adjusting their thermostat, though they could also get hacked. The openhab example was one of what not to do. I could have been more clear about that.

    Security is an issue that people in this community are fairly opinionated on. Try to build up a practical knowledge of every tool you use (like tools for remotely managing your server). Think about how much access that tool gives you, and how easy it is to get. Ssh gets you basically full access to the system, except for bios level settings and things, but it is generally quite secure, and you can use keys instead of passwords. Cockpit, a remote management tool you can access from your browser, offers you a full terminal, so functionally the same access as ssh. However, hackers nearly got a back door into openssh (ssh is the protocol, openssh is the software on linux that implements that protocol), and cockpit is much less thoroughly looked at. Also cockpit doesn’t let you use keys.

    You’re website will be static, which decreases the complexity and makes it easier to make it secure, so don’t worry too much. Here are some links that might be useful: https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server

    https://www.cyberciti.biz/tips/linux-security.html (this one seems to be geared more towards enterprise stuff, so not all of it is relevant, but a decent amount is.)

    Edit: This one is good too. I recommend at least skimming it before the one above this. It will help you figure out which of the points in the link above are worth paying much attention to. https://owasp.org/www-community/Threat_Modeling