• 0 Posts
  • 36 Comments
Joined 5 months ago
cake
Cake day: July 6th, 2024

help-circle
  • Most normal people are nervous interacting with a GUI pop-up that gives them two options

    Sadly no. They should be nervous if it’s about making changes to their system. In reality however Windows conditioned them to just click the button labeled “Yes” or “Okay” without even reading the pop-up in the first place.




  • But a huge part is conditioning because people are forced to use Windows early and get used to it.

    I have made the exact same “oh, this just works and is quite intuitive and convenient”-experience with Linux installs… for people lacking that prior forced contact with Windows (say older relatives with their first PC for example…).


  • Ooops@feddit.orgtolinuxmemes@lemmy.worldWhat you rather?
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    13 days ago

    The wiki is actually good for beginners, too. As you are often forced to reallylly read through subpages and cross-referenced topics until you somewhat understand why you are doing something instead of just how. Doesn’t make it easy ofc but a beginner can totally handle the wiki, it just takes more time.






  • That sounds like the non-techies would be able to fix it themselves on Windows without you being around, which in my experince isn’t the case.

    It might be different for you with a lot of tech-affine people in your family. But for those of us being forced to be the tech support anyway, it can really make a difference if you have to fix a Linux issue once in a while or have to reinstall Windows for the 5th time this year…



  • ARM is shit at hardware discovery in general. So no, chromebooks don’t need a special distro. They however need a kernel adapted to the specific hardware, often down to the model (that’s also the reason Android updates take so long on phones and there is very time limited support… there’s always someone needed to adapt new updates to the specific hardware for each device, so they don’t bother for anything but their latest products).


  • Decryption isn’t a problem if you use the systemd hooks when creating your initrams. They try to decrypt every given luks volume with the first key provided and only ask for additional keys if that fails.

    I have 3 disks in a btrfs raid setup, 4 partitions (1 for the raid setup on each, plus a swap partition on the biggest disk), all encrypted with the same password.

    No script needed, just add rd.luks.name=<UUID1>=cryptroot1 rd.luks.name=<UUID2>=cryptroot2 rd.luks.name=<UUID3>=cryptroot3 rd.luks.name=<UUID4>=cryptswap to your kernel parameters and unlock all 4 with one password at boot.


  • Ooops@feddit.orgtolinuxmemes@lemmy.worldOne big happy family.
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    3 months ago

    Linux is Linux.

    We should send all those people, pages and guides suggesting distros to hell.

    And then instead we suggest update-schemes (fixed, rolling, slow-roll), package managers and Desktop environments. People with enough brain cells to start a computer are then absolutely able to chose a distro fitting them based on that. Everything else coming with a distro is just themeing/branding anyway…

    (and just for the use statistic: Archlinux, Opensuse (Leap and Kalpa), Debian here…)


  • I’ve been using Arch and Manjaro for couple years each and in my experience they both break regularly. But, for some weird reason, Arch Linux is praised, when Manjaro is shamed upon.

    No, there is not some weird reason but actual very good ones.

    Things can break on a bleeding edge update scheme. That’s to be expected from time to time. But the questions are “why did it break” and “what is done to fix it”.

    If something breaks on Archlinux it’s because of some new package with a issue that escaped testing. Then the fix come out as fast as possible (often within minutes even, but let’s assume hours as those things need to move through mirrors first…).

    If something breaks on Manjaro it’s either because of the exact same reason as above, but 2 weeks later. Because Manjaro keeps back updates for two weeks “for stability reasons”, yet doesn’t do anything in those 2 weeks. So they just add the same problem later, completely defeating the argumant about stability. Oh, and fixes are of course kept back for 2 weeks, too, because… reasons.

    Or it breaks because they fucked up their internal QA. For example by letting their certificates expire again and again and again and again… of by screwing up their very own pacman-wrapper and then ddos’ing the AUR for all users, not only Manjaro ones.

    Or -speaking about the AUR- it breaks because they give their users full access to the Arch User Repository (without any warnings about user content being less reliable and used at your own risk) pre-installed. Also they do it on a system generally out-of-date because it lags 2 weeks behind. Which is not what AUR packages are build for (they assume up-to-date systems) and is a straight path to dependency hell and breakings… not because something went wrong but because the whole concept of an out-of-date system not running their own also 2-weeks behind version onf the AUR is idiotic. On the “plus” side they have an easy fix: blame the user, because he should obviously know that an pre-installed part of Manjaro is conceptionally flawed and shouldn’t be trusted.






  • When you say system drive this will also have your efi system partition (usually FAT-formated as that’s the only standard all UEFI implementations support), maybe also a swap partition (if not using a swap file instead) etc… so it’s not just copiying the btrfs partition your system sits on.

    Yes clonezilla will keep the same UUID when cloning (and I assume your fstab properly uses UUIDs to identify drivees). In fact clonezilla uses different tools depending on filesystem and data… on the lowest level (so for example on unlocked encrypted data it can’t handle otherwise) clonezilla is really just using dd to clone everything. So cloning your disk with clonezilla, then later expanding the btrfs partition to use up the free space works is an option

    But on the other hand just creating a few new partitions, then copying all data might be faster. And editing /etc/fstab with the new UUIDs while keeping everything else is no rocket science either.

    The best thing: Just pick a method and do it. It’s not like you can screw up it up as long if your are not stupid and accidently clone your empty new drive to your old one instead…