The game title is a little bit unfortunate.
I’m here to stay.
The game title is a little bit unfortunate.
The older the Kernel gets, the more Rust it will get.
It makes no sense to cite a little part of the US DMCA law if the discussion was based on Japanese laws. If you look at https://www.law.cornell.edu/uscode/text/17/1201 , its much more complicated than one sentence. As for the DMCA, this is the next paragraph after the cited above one:
(B) The prohibition contained in subparagraph (A) shall not apply to persons who are users of a copyrighted work which is in a particular class of works, if such persons are, or are likely to be in the succeeding 3-year period, adversely affected by virtue of such prohibition in their ability to make noninfringing uses of that particular class of works under this title, as determined under subparagraph ©.
I admit not really to understand, as the language is hard to read for me. It would even be hard in my native language. Does the Japanese law have such clauses and exceptions?
I assume its this one: https://flathub.org/apps/org.virt_manager.virt-manager but its unverified and not directly from the actual developers.
The standard session requires root, and for some reason this means that VMs couls harm your system more or something
VMs don’t have access to the host, so even if the virtual machine emulator Qemu and libvirt require root access, the encapsulated guest virtual machine have no access to the host. They can’t harm your system.
But this is still to be discussed, because if the emulator does not circumvent any copy protection and the games are dumped with the protection in place, and the copy protection is reverse engineered, then the games would play with the copy protection decrypting. It does not circumvent the protection, it actively “uses” it. So from that standpoint making backup copies is not illegal in theory. Now would this hold in court? I don’t know. Nintendo does not know either and rather like to take things out of court. Because if Nintendo looses such a case, it would be devastating.
I’m in Germany too and the right to a private copy is exactly what I had in mind too. Not all copy protection measures were accepted for the right to not copy. What I mean is, there was some extremely simple protection mechanisms that were not accepted as a working and effective copy protections, and you were allowed to do a copy; even with the so called copy protection in place. Therefore it effectiveness was kind of important to the discussion too. I guess the Switch has a much more advanced one, so its probably not an exception.
It makes sense from argumentation standpoint, because Nintendo argues that there are protection mechanisms in the Switch that is illegal to ignore, in emulators. I don’t know if this is true and you don’t know either, because this was not tested in court. Nintendo never ever said that ALL emulation is illegal, which i stated in my initial reply. Otherwise Nintendo would go and take down ALL emulators. Not every kind of emulation is the same.
In example the Dolphin emulator ships with keys extracted from the console. Some say its illegal to distribute these keys, others argue keys are not copyrighted and its not illegal to share, but it was never tested in court either. If Nintendo had a case, they would definitely go against that emulator, as the keys are in the source code in the open public. Nintendo never said that Dolphin or Wii and Gamecube emulation is illegal. Or any other prior console and emulator of Nintendo systems. Nintendo console emulators exist in the public since the 90s.
Its much more nuanced than people are making or understanding. And lot of articles, like the one stated before, are plain and simple wrong and cite without context. And people who don’t understand the situation take this and believe it.
Those articles are wrong. Nintendo says Switch emulation is illegal, not all emulation is illegal.
Nintendo never said that all emulation is illegal. Nintendo just does not like that their current gen is being emulated and lot of games are easily available on pirate sites for everyone. Otherwise Nintendo would have tried to shutdown emulators for previous systems too. They were especially worried about the Switch 2 being emulated easily with current emulators, as it doesn’t seen too different. I think that’s all to it.
However, there are still a number of ways that emulators can violate the law. For example, the Nintendo Switch has certain “technical restriction measures” that prevent it from playing pirated games. If a Switch emulator seeks to bypass those measures, it opens itself up to legal trouble.
Which law exactly? There are exceptions for making personal backup copies. So its not really court tested law and we don’t know if it violates the law. As the article said, these cases never went to court and we don’t have a decision by law. Nintendo did all of that out of court.
That’s a lot. But that also means your system is not very secure, as you are missing ton of security patches for the packages.
34 days without booting? Are you using a Debian system and don’t update often? You should, for security patches at least. I’m on an Arch based system and update every day. Sometimes there are updates that require a reboot, so all services are up to date. My system is often up for a few days, sometimes even for a week.
Small tip, logging out and in will have a semi clean environment without a full boot. That means the uptime won’t reset.
Agreed. This term “unixporn” bugs me. I cannot recommend those platforms to anyone, because of the direct use of “porn” term. Its like kiddies made up the term unixporn or something…
Removed by mod
I watched this video yesterday too and it inspired me to write an article (not the longest article, its mainly to provide download links for those NES games): Nintendo Family BASIC Type-in Programs Collection (homebrew roms for NES)
The video itself is as you say, surprisingly interesting. But to be honest, I expected that. This channel has often interesting content like this. BTW Masahiro Sakurai, the creator of Kirby and game designer of Smash Bros., had posted a video about this system too. Its very interesting watch as well: Family BASIC [Programming & Tech] by Masahiro Sakurai on Creating Games
TL;DR: My desktop PC uses EndeavourOS and the only immutable experience I have is SteamOS 3. I can’t say one approach is better than the other, but I like having the newest software and packages in my system. And that’s best provided with a rolling release. I also think that sandbox systems like Flatpak and the several alternative installation methods besides the system package manager is an added complexity for a new user in Linux.
I don’t mind using an immutable system (BTW another term that describes this kind of system is Atomic, which comes from Fedora), as long as it is designed around it and works well. The only immutable system I use is on my Steam Deck with the pre-installed SteamOS 3. My generic desktop personal computer is using an Archlinux derivative EndeavourOS with a rolling-release, where I have much greater control over the system.
Both systems have their strengths. I don’t think that my mutable and always up to date system is breaking more often than the other system. The best part of it is, its always up to date and I get the newest applications. I try to not use much Flatpaks or AppImages (but do for certain apps, where I have no other choice for ease of use). And an immutable system naturally basically asks me to use Flatpaks and other user space package formats that is not handled by the distribution itself.
Even though I have some thoughts on it, I am not excluding one approach. Many say that immutable distributions are good for new users to Linux. I think this adds some complexity and problems, because they need to use sandbox systems like Flatpak. And that’s if they know that they are using Flatpak, because sometimes the app distribution gives options like AppImage and custom installer scripts as well. This is all confusing for someone who just starts with Linux. On top of it, the sandbox of Flatpak requires some additional setup and configuration for some apps, to access certain hardware or filesystems in example.
All in all, I tend to like the traditional “mutable” distribution system as a rolling release model the most. But I’m an not excluding any other and would use a good “immutable” one; I just didn’t try any other than the one in my Steam Deck.
This only means programmers of Linux itself can use Rust to program the Kernel. In example if Rust programmers are good at it, they can use the language over something they are not good at it like C in example. You as the end user does not see any direct difference. Like with any other application if its written in Rust or in C, it does not matter much if you use the binary executable.