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

help-circle
  • It’s true for any variation of Linux. Hell, the vulnerability (Mimikatz) that was crucial in the most expensive cyber security attack in history is still there in Windows.

    And for X11 to be exploited you would need to get and run malicious code in the first place. The Linux security model kicks in before you get to that point.









  • It uses Universal Blue, whereas Kinoite uses rpm-ostree.

    Aurora has a bit of DE customization, which is arguably more polished.

    It also leans heavily on Flatpack/Flathub.

    The other difference that I’m aware of is Aurora handles updates automatically by default, whereas Kinoite is a manual process.

    To be clear, I haven’t used Kinoite at all. But I have Aurora on a gaming system that I use as a kind of TV gaming console, and I’m setting it up for my elderly parents that get upset when an icon on Windows changes (that’s how tech illiterate they are).



  • enterprise type programs

    The idea of elderly people using windows only programs

    I don’t think these two groups overlap much, if at all.

    the general hodgepodge that Libre Office is

    What’s hodgepodge about LibreOffice? I use it daily in a corporate job. There are entire governments that use it.







  • If you install each OS with it’s own drive as the boot device, then you won’t see this issue.

    Unless you boot Windows via the grub boot menu. If you do that then Windows will see that drive as the boot device.

    If you select the OS by using the BIOS boot selection then you won’t see this issue.

    I was bitten by Windows doing exactly this almost 15 years ago. Since that day if I ever had a need for dual-boot (even if running different distros) each OS will get it’s own dedicated drive, and I select what I want to boot through the BBS (BIOS Boot Selection). It’s usually invoked with F10 or F11 (but could be a different key combo.


  • While I generally agree with that, that’s not what seems to be happening here. What seems to be happening is that anyone who boots Windows via grub is getting grub itself overwritten.

    When you install Linux, boot loaders like grub generally are smart and try to be helpful by scanning all available OSes and provide a boot menu entry for those. This is generally to help new users who install a dual-boot system and help them not think that “Linux erased Windows” when they see the new grub boot loader.

    When you boot Windows from grub, Windows treats the drive with grub (where it booted from) as the boot drive. But if you tell your BIOS to boot the Windows drive, then grub won’t be invoked and Windows will boot seeing it’s own drive as the boot drive.

    This is mostly an assumption as this hasn’t happened to me and details are still a bit scarce.