How hard is the initial setup for this board? Is it a simple flash an sdcard and power it, or does it require manual kernel crosscompiling of some specific unmaintained github fork? I know Debian is working on offcial riscv support but I haven’t looked at how far its come along in a bit.
Yeah the preference is yours, at the end of the day, I don’t think it matters what tools you use as long as it works.
Worth noting is that a process not managed by pid 1 isn’t really a thing you want generally. If you use systemd to start the docker daemon, which then starts your container, its still managed by pid 1 eventually. Perhaps you prefer the tooling and interface of docker more than machinectl, or maybe podman just isnt working for you, they’re all just tools to interact with kernel namespaces and cgroups. For doing a little dabbling in another distro, installing docker is pretty heavy vs what the article is talking about.
systemd manages cgroups, a very well standardized kernel interface for process management, which I would say is something init should be able to do. The gap between that, and a container is mostly semantic.
You can also pipe yt-dlp into vlc if that suits your fancy.
I desperately hope they have some interaction, truly a meeting of the best dorks.
If the exclusive ownership of something, in order to sell it, is the primary choice driving factor of a project. Then you should just make it proprietary. Anything else would limit your margins, since someone else can just fork your project, change it and make it proprietary themselves. A dual license is sometimes used in this case as well.
In a hand wavy way, yes. You are just editing the settings of one suite of software, not really an OS “registry”. Closest to that in Linux is editing /etc, but even then, not all software is configured there.
Well Linux doesn’t have a registry, so an editor would also not exist, to be fair.
Not literally copy, as in have an extra set of keys. A spare key. A bank vault is total overkill. I just bought 2 fido2 keys and register both for the services that support them. Have one on your keychain and another in your desk. 2FA is often way over thought, any adversary needs both factors so something you know and something you own is plenty for most people.
A hardware device is a physical key. Its no different than backing up your home key. Get two keys and copy them. Keep one on you, and the other in a safe somewhere in case you lose the first.
struggling with Nvidia drivers
Depends on your hardware age, and whether or not you use proprietary drivers. Some distros handle it auto-magically for you so you don’t really need to do anything and it just works.
ultra fast GPU access to storage
For the time being, nothing on PC actually requires this, or uses it optionally for any perceived I provment in fidelity. Its super cool tech though, looking forward to this in the future.
HDR
Fair point, it is actively being worked on by a lot of big organizations and developers, so it will get better. Last I checked Window’s support of it isn’t incredible, but its better than the nothing Linux has at the moment.
I just want better support from developers. I’m fine with AMD being slower, but a ton of projects just don’t even run with AMD hardware. I wish there was a psuedo-vulkan style interface for AI, so that GPU makers and developers could target that in the same way game developers target vulkan/opengl.
While it sucks, I’ve had no trouble streaming to my phone with steam remote play. Since my phone can barely handle the game natively.
I feel it is highly opinionated because they only officially support a fairly small amount of packages. They’re not particularly more up-to-date than say openSuse Tumbleweed. A Debian netinstall is equally a barebones system I can install exactly what I am looking for, and don’t need to fiddle with third party repo’s like the AUR. As far as I know, almost every distro will let you do a barebones headless install, then build up your system yourself. Arch is certainly less opinionated than Ubuntu, but that’s not a big accomplishment these days.
If I were to desire a highly specific environment where I wanted to exactly manage each program’s dependency chain myself, Gentoo seems like a much better tool for the job. For example, Arch officially requires systemD, Gentoo does not. As far as I know Gentoo makes no assumptions on how your system is setup, from preboot to Wayland session.
I could just be out of date, as I use NixOS as my workstation and server OS, using Debian for some older servers I haven’t migrated yet. I get the impression from Arch, the few times I have used it, is that its niche is appealing to a particular kind of user, rather than being a good solution to a particular kind of problem. That’s not bad, its huge reason why its popular. Other distros do the same thing as Arch, sometimes better sometimes worse, but Arch is selling an aesthetic, rather than a tool.
From the symbol I would have thought that meant ‘less than or equal’, but its probably exactly equal. So 2:30:01 is not equal but it doesn’t show that to you.
Of all the main stream distros, I never liked Arch. I’ve been a big fan of and have used Debian and Fedora for years for different uses, I love all the work openSuse does for their GUI configuration, and I respect Slackware and Gentoo for what they are, though I’ve never use them myself.
Arch always gave me the impression that its fiddly, fragile, and highly opinionated. I think the AUR is a bandaid; its explicitly not supported, yet everyone says its the best reason to use Arch. If I want packages built from source, it just seems that Gentoo does it native to the whole OS and package manager. Nix does too. If I wanted closed-source binaries, flatpak seems like the way the ecosystem is moving and is pretty seemless for my uses. Keeping them with static libraries independent of the OS makes sense to me for something like Spotify, especially since disk space concerns are irrelevant to me.
Opinions on and around Arch are everywhere, both good and bad. I just have never found a situation where I see any benefit to using Arch over Debian for its stability, Alpine for its size, Gentoo for its source building support, or Nix for its declarative approach. So I have grown to loathe its atmosphere.
VPN’s are useful in keeping the ISP’s out of your business from snooping on all your websites that you visit, and all the traffic coming and going from your PC
A VPN isn’t a miracle cure-all. You are just transferring all your traffic from your local ISP to another. Usually the new one is by choice, so there is a lot more competition and thus more likely a better service provided.
VPN’s allow pirates to download torrented media, without advertisements, to be enjoyed offline, which streaming doesn’t always do.
Just for clearity, its not the VPN that’s enables this. /Some/ VPNs allow for this, and you have to do your due diligence or else you could just be handing all your data straight into a honeypot. VPN providers are rife with paid shills and bad actors.
Not picking on you specifically, but I’d hate to see a fresh recruit find some rando VPN from a youtube ad and think they’re in international waters when they’re really standing on dry land.
In my experience its mostly sane defaults and a mixed bag in terms of documentation. For anyone else reading this, https://search.nixos.org/options using this to search for all the built in options is usually a good enough starting point for installing something.
Nix does dependencies very differently, since every program and everything it needs are put into their own checksummed directory, then linked into your PATH as requested in your config. So far I’ve never needed to do anything other than nixos-rebuild --upgrade switch and only needed to reboot for kernel updates.
I mostly work in container spaces, so building things from source, or out-of-repo pkgs, while rare, are done in containers with podman. For example, running Automatic1111’s stable diffusion works perfectly for me in a container with an AMD GPU no less. Eventually I’d like to get into flakes, but their still marked experimental so I haven’t looked too much into it.
Overall the learning experience is figuring out the overall structure of the system, then taking advantage of all the super powerful tooling and consistency those tools offer.
No worries, UEFI is definitely a “milage may vary” kinda standard.
I’ve personally only used NixOS and not Nix on a different distro by itself so I’m less familiar with that setup. No system is perfect for all use cases, but that’s sorta the point in Unix-land. I personally have been gripped by NixOS and having to go back to Fedora for some of my old servers has been a pain. They use it like a buzzword all the time, but declarative administration is so awesome. It does have a heck of a learning curve though.
Pre-installed to the emmc I assume? That’s nice for the out of the box experience, but knowing the nature of SBCs I’d like to be able to at least get a copy of the image so I can burn a new boot device when something goes a little sideways.
Since you’ve worked with them before, are these the correct images? https://wiki.sipeed.com/hardware/en/lichee/th1520/lpi4a/3_images.html I did a little bit of digging from the link in the description of the video, if so then I’d gladly get a couple of these to play with. Dual Ethernet, and even PoE is awesome at this price point.