• 78 Posts
  • 373 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle








  • Great comment!

    There’s similar legal issues with the “right to a private copy” many European countries have. Those laws were made to allow people to make a copy of their media, in case the original breaks. Important to note is that those private copies weren’t allowed to be distributed to anyone, not even lent to a friend.

    This worked well at the time for cassettes and VHS, which did break occasionally.

    But at some point most CDs came with copy protection, which got broken pretty quickly. But at least in Germany, they are still considered “working copy protection” and thus are illegal to circumvent, even for a otherwise legal private copy.

    The same is the case with Switch games: Copyright owners use copy protection to make otherwise legal use cases illegal.

    E.g. Nintendo made it so that Switch games can only be played by decrypting the ROMs, which is illegal for anyone except Nintendo.

    At least that’s their standpoint which was never tested in court but it’s not unlikely that it’d be accepted.




  • Chewy@discuss.tchncs.detoLinux@lemmy.mlImmutable Distro Opinions
    link
    fedilink
    arrow-up
    12
    arrow-down
    2
    ·
    edit-2
    4 months ago

    NixOS is immutable and atomic, but it isn’t image-based.

    Immutable simply refers to how the running system configuration can’t be changed by simply putting a file somewhere (e.g. copy a binary to /bin, which is a bad idea).

    For example, Fedora Atomic and derivatives are image based, although they are more flexible than the A/B types like SteamOS.

    OpenSUSE MicroOS uses btrfs snapshots to apply updates atomically, and is more flexible than most image based immutable distros.

    Edit: But I don’t think those terms have a single definition, so how would you differentiate these terms?





  • Yes, ~/.local/share/flatpak includes all user installed flatpaks, while /var/lib/flatpak includes all system wide installed flatpaks. Both include repository information and required runtimes (i.e. dependencies).

    This does not include user data, which is stored in ~/.var/app.

    Make sure to test your backup just in case on another system/VM.







  • Analogue likely doesn’t emulate the hardware at the transistor level, as it’s far more difficult than doing what most software emulators do.

    From an interesting (altough non-conclusive) HN-thread [1].

    Without seeing the code, it’s impossible to know where Analog’s implementation falls on the spectrum of software emulation vs hardware simulation. There is nothing magical about FPGAs that automatically makes anything developed with them a 1:1 representation of real hardware. In fact, there are plenty of instances where the FPGA version of a particular console is literally just a representation of a popular emulator only in verilog/vhdl. In many instances, even the best FPGA implementations of some systems are still only simulating system level behavior. Off the top of my head, one famously difficult case is audio, where many chips have analog circuitry that cannot be fully simulated.

    [1] https://news.ycombinator.com/item?id=37901381