• 1 Post
  • 451 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle

  • utopiah@lemmy.mltoLinux@lemmy.mlbest professional server Distro option?
    link
    fedilink
    arrow-up
    2
    arrow-down
    3
    ·
    edit-2
    6 days ago

    if you need new things before it’s ready for a new version it’ll be pain

    Like what?

    Also if you need something before Debian is ready for it… you’re weird. I don’t mean this in a derogatory fashion, solely that you are doing something our of the ordinary. Consequently you should first question WHY you do that in the first place.

    Finally if you do need something very specific, containers are there to … contain that. Running Debian as the host distribution doesn’t mean you’re limited to it for your applications, servers included.





  • Few seem to address the issue here : it does not work 100% of the time for you.

    It might work for everybody else but that doesn’t help you much. You have your setup, no theirs.

    So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check https://lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and journalctl logs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g. dmesg.

    They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate :

    • what’s your crime scene? Your laptop and it’s log files
    • what’s the crime? It didn’t suspend properly
    • where are the traces? In the logs
    • where are the logs? Using journalctl or dmesg and typically in /var/log/
    • what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using grep and other tools

    You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window.

    TL;DR : grep logs






  • It’s a pragmatic compromise. The assumption is that Google is not literally evil, solely a very large advertisement company which subsidize very cool hardware in order to sell more ads. It’s the same principle as using a rooted Meta Quest when one doesn’t even have a Facebook or WhatsApp account.

    I imagine than everybody who is into that situation will move to Motorola or Valve Frame when those will become available. Until then the bet is that the hardware does not have hardware backdoors because so far nobody disclosed any.

    If you really are into trusting hardware I recommend checking https://precursor.dev/ and similar initiatives.

    I did mention Linux phones too but again that’s not for everyone.

    IMHO it’s much better to use a GrapheneOS deGoogle Android device today, knowing the limitation, than using a Googled Android device today, Pixel or not, and complaining about all the limitations about it while waiting for a theoretical better solution that is simply not yet available.



  • Yes, I have a PinePhone and PinePhone Pro both with PostMarketOS so doing this is as easy as few sudo apk add packagename or sudo apk del firefox.

    Now… if you want a daily driver then as few others hinted at, it’s much harder. I would instead, if deGoogle Android is an acceptable compromise for you, get a 2nd hand Pixel 8 or above, install GrapheneOS on it, remove the browser and that’s pretty much it already since it doesn’t come with an app store or equivalent. Well, there’s the GrapheneOS equivalent but there are ~10 apps on it at most last time I checked.


  • utopiah@lemmy.mltoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    20 days ago

    I don’t think it actually is. It’s only like that the very first time when you haven’t you this specific distribution itself. Once you know how the few extra step and understand the core principle, it’s trivial.

    PS: I did tinker with NixOS, SteamOS and ROCKNIX.


  • I’m not sure.

    I’m a professional tinkerer and I run Debian stable. OK ok it’s not an immutable distro but my point is that I do tinker, just NOT with my main OS.

    I’ll tinker in containers, in VMs, in my ~/bin etc but NOT in what hosts all that.

    So I would argue that what’s important for tinkerers is to establish clear boundaries on what they want to tinker on and what they do NOT want to tinker on, what can change vs what should never.