

One or two Linux distros were (are?) UNIX certified, though.
One or two Linux distros were (are?) UNIX certified, though.
I think mplayer
has an ASCII output mode (VLC, too?), and I believe youtube-dl
can output to stdout.
The rest is, as they say, left as an exercise to the reader.
Haha yeah that was the counter example I was thinking of. I agree completely — you could make a Gentoo from source beginner distro, and I think you could make it reasonably “idiot proof,” but it would still be a bad user experience most likely (too much time spent compiling).
If your distro can’t be forked into a “beginner distro” then it’s fundamentally flawed IMHO.
To be clear, I’ve used Arch as my daily drivers for a while, and while it’s not the best fit for my needs (I use Debian mostly), there’s nothing that I experienced that was incompatible with a “beginner” distro.
You can also drop cache for debugging by running something like echo 3 | sudo tee /proc/sys/vm/drop-caches
But remember that the kernel knows best — this RAM will automatically be freed up when needed and you should never run this except for debugging (or maybe benchmarking).
I switched from raspberry pi and orange pi to a cheap Intel NUC, and I think it’s just a much nicer experience.
The pi is great fun, but the HW transcoding on a NUC “just works,” and the SSD and 16GB RAM opens a lot of doors. My N100 NUC was less than $150, and it included everything (case, power supply, 500GB SSD).
My pi found new life as an off-site backup: attach a big HDD, set up WireGuard, and have a cronjob do daily rsync and snapshots. I have it set up at in-laws, and it works great.
You can turn it off, at least for ext4: https://lwn.net/Articles/784041/
Although you can use case insensitive filesystems with Linux, and case sensitive filesystems with macOS. I believe the case sensitivity is a function of the specific filesystem — but yeah, practically, the root for Linux is always case sensitive, and APFS ain’t is only if you ask it to be ( https://support.apple.com/lv-lv/guide/disk-utility/dsku19ed921c/mac ).
I would bet that if you remux BBB to an mkv and play that through JF, it won’t transcode — I think it will just remux it back to mp4. Just a guess…
Interesting — I wonder if it only displays the first reason for having to mess with the stream, e.g., if it’s really that it’s an unsupported container, video, and audio codec.
Possible to try playing an h264 mkv (maybe Big Buck Bunny)? Since your screenshot is h265 I wonder if it indeed needs to transcode because that’s unsupported (in addition to mkv).
unless everyone is using hardware acceleration
I think that’s what (almost) everyone does. My little N100 works just fine with QSV.
Is it definitely transcoding? JF can remix without transcoding iirc.
IIRC chvt
is a privileged command, which makes sense (if an unprivileged user could execute this command they could effectively brick the computer for a local user).
That said, my understanding is that modern DE’s are given a lot of access, so presumably chvt
is allowed (and in this case, is required because as others mentioned, password is required). So the only other option is to fail unlocked, which is all kinds of Bad.
proxmox nudes
No judgement here, you just keep doing what makes you happy.
Not sure why you’re saying Python forces everything to be object oriented…?
awk(1)
ward
FTFY
And environment — DISPLAY
and PATH
in particular.
For very simple tasks you can usually blindly log in and run commands. I’ve done this with very simple tasks, e.g., rebooting or bringing up a network interface. It’s maybe not the smartest, but basically, just type root
, the root password, and dhclient eth0
or whatever magic you need. No display required, unless you make a typo…
In your specific case, you could have a shell script that stops VMs and disables passthrough, so you just log in and invoke that script. Bonus points if you create a dedicated user with that script set as their shell (or just put in the appropriate dot rc file).
EulerOS, a Linux distro, was certified UNIX.
It’s UNIX 03 compliant https://en.m.wikipedia.org/wiki/Single_UNIX_Specification