• 1 Post
  • 14 Comments
Joined 4 months ago
cake
Cake day: July 21st, 2024

help-circle





  • Vittelius@feddit.orgtoLinux@lemmy.mlDistro and/or config for elderly person
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    edit-2
    2 months ago

    I would probably go with bluefin. KDE is great, I myself use aurora on one of my devices, but it can also be kinda fiddley with all of it’s options.

    The user has never even used a PC and therefore won’t profit from the familiarity that KDE’s default desktop layout provides. Gnome on the other hand offers a more simplified experience with few options and big icons. All of that might be an asset here. You can use menulibre to hide menu entries from the menu and use the official documentation to remove command line access: https://help.gnome.org/admin/system-admin-guide/stable/lockdown-single-app-mode.html.en

    Plus it’s still atomic which I actually think is helpful here. For once all the important system stuff is read only. Secondly if one manages to screw something up you can just rebase.


  • I considered that. Unfortunately silverblue doesn’t do live systems and aurora therefore doesn’t either. So a VM is the only way of trying it out. OP stated that they have someone to help with the actual installation so I left the whole create install medium for bare metal install out intentionally since I assume this person will be capable of helping with that.

    Also small Markdown help: If you use dashes lemmy will automatically format bulletpoints correctly. You can’t use •s for it. Doesn’t take anything away from your comment, etcher is still the best tool to create a bootable usb drive, but for the future consider using dashes.


  • Vittelius@feddit.orgtoLinux@lemmy.mlIs Linux (dumb)user friendly yet?
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    2 months ago

    You can try Linux out without installing it to get a feel for it before you make the jump. Set a weekend aside (or at least a couple of hours) to test drive a Linux distro and check if it is your cup of tea.

    This is one way of doing this:

    • Install Virtual Box on your (Widows) PC
    • head over to https://getaurora.dev/ and download the latest iso
    • In virtualbox create a new VM
      • set the OS Type to fedora (64 bit)
      • after that you can keep all the standard settings, just be aware that performance is not going to be representative of an actual install
    • Then select the newly created VM and open the settings panel
      • here you go to “Storage” and click on the slot under “Controler: IDE” labeled “empty”
      • click on the CD symbol on the right side of the window, in line with “optical drive” and select “choose a disk file”
      • pick the iso file you downloaded in step 2
    • close the settings window and start the VM
    • go through the installation wizard to install Aurora OS in your Virtual Machine
    • Profit

    I know that these instructions can seem daunting but it is easier than it reads, I promise.

    Why Aurora OS

    Aurora OS is based on Fedora Silverblue meaning that it is what is known as a immutable distro. That in turn means that it’s harder to mess stuff up and break your install. It also means that some things are harder to achieve. But I also think that you are probably not interested in the hard stuff anyway.

    Aurora uses the KDE Plasma Desktop, the same desktop used by Valve on the Steamdeck. It has a familiar Windows like layout by default but also allows you to customise it like crazy to fit your particular need (whatever that may be).

    Aurora flatpak as it’s app format. To see what kind of software is available for this distro you can check flathub.org . It’s not going to be as much software as Linux Mint for example (Mint uses flatpak and deb), but everything the average user needs should be there.




  • It’s bazzite with a custom UI instead of Steam Big Picture and no desktop mode. Their big claim seems to be that they say that they have solved anti cheat on Linux: the system generates a checksum of the kernel space, the anti cheat then compares this checksum with the one on file. No custom kernel module needed on the part of the anti cheat dev. At least in theory.