![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
How did you get into TSA Pre without providing fingerprints? I tried once, and they strictly refused to let me apply because I wouldn’t give fingerprints.
How did you get into TSA Pre without providing fingerprints? I tried once, and they strictly refused to let me apply because I wouldn’t give fingerprints.
I suppose mine would be Proton/Steam/Mate Desktop/Gnu/Linux
This is false. X is not less secure than Wayland. It does have a different security model, which can become insecure if you misuse it. I don’t think people really care about situations where multiple user accounts access the same display.
In my opinion, the benefits of xdotool far outweigh any benefits gained by Wayland’s security model. It’s impossible to make xdotool in Wayland, because of its security model.
I never got Proton working on my main distro (Debian), so I probably fall into this category. I did use Wine, but Wine is a lot harder to set up, and never ran games as well as Proton did.
Here is my major gaming history, since I started on Linux in 2007. Yes, I really could focus on a single game for years back then.
Today, I still prefer native Linux games. I mostly only use Proton when peer pressure for a multiplayer game required it. But I never use Wine any more.
Some of those games sound like Simon Tatham’s Portable Puzzle Collection
Available for Linux, Windows, web browser (javascript or java applet), Android, IOS, and… uh, Palm OS apparently.
The thing with coloured bubbles could be several things here. The network thing is probably net or netslide. The thing with the lasers and the grid is probably blackbox
A couple months ago, I made a Palworld server box out of a spare motherboard assembly (mobo, processor, ram) from a computer I had recently upgraded.
I didn’t have any spare drives lying around, so I plugged in 7 USB flash drives and made them into a RAID array. Not a true RAID array, but a BTRFS filesystem with volumes spread onto each flash drive, with the data redundancy set to raid1, and the metadata redundancy set to raid1c3.
It worked… in the sense that I never lost any data. It certainly didn’t work in the sense of having good uptime.
The first problem was getting it to boot right. The boot line in GRUB had “root=UUID=…” instead of a specific drive named. That is normal. However, in BTRFS multi-volume filesystems, all the volumes have the same UUID. So the initrd was only waiting for a single drive matching that UUID, then trying to mount it as the root filesystem. This failed, because the kernel had not yet set up the other 6 USB drives, and this BTRFS filesystem needs all 7 volumes present. Maybe 6, if you used the “degraded” mount option.
The workaround was to wait for this boot process to fail, at which point you get dropped into an initrd shell. Then, you look at all the drives and make sure they’re all there. And then… I don’t exactly remember what happened next. I think it was some black magic that erases your mind in the process. I somehow got it booted from the initrd shell.
Installing Steam and the Palworld server worked ok, and it even ran for a few hours before crashing overnight.
The next morning, I tried rebooting it. Unfortunately, the USB drives weren’t all appearing. Turns out the motherboard had some bad USB ports, some sometimes-bad USB ports, and a maybe-bad PCIe bus, because the PCIe USB expansion card I plugged in had weird problem that it had never had before.
I found the most reliable ports and plugged the drives in there. But you can’t just replug them in the initrd. It doesn’t have USB hotplug support. So each time it tried to boot with not all the drives there, I restarted it again until one time I finally had all the drives.
I changed the GRUB boot line to “root=/dev/sdg1” . This made it wait for all the drives to load, in any order, and whichever one was last would be mounted as the root filesystem (but the kernel would automatically include all the others too, since they were successfully initialized).
The bad USB ports kept bringing down the server every day or two. I bought a cheap NVMe drive and added it to the BTRFS filesystem, and then removed all the USB drives except the largest. That fixed the reliability. It’s been like that since.
Now, to boot the server, all I have to do is change the GRUB boot line to “root=/dev/sdb1” . Since the NVMe drive is much faster than the USB drive, it always initializes first. If the initrd waits for sdb2, then it will always have both drives initialized when it tries to mount the root filesystem.
I could add that to the grub.cfg, or come up with some other more permanent solution, but I’m not planning on rebooting this server ever again. My friends fell off Palworld, and I gave a shutdown date that’s about a week away. And the electricity is pretty reliable here.
The good news is: the error shown there was a PCIe bus error, which means the error is somewhere between the NVME controller and your processor’s PCIe interface. Also good news: the errors you experienced were fully corrected, so you probably lost no data.
So the flash memory in the drive isn’t failing. That’s good because if the flash memory starts failing, it’s probably only going to fail more. In this case, your errors may be correctable: by replacing the motherboard, by replacing the processor, by reseating the NVME drive in its slot, by verifying that your power supply is reliable…
However, if your NVME controller actually does fail, it will be little consolation to tell you that your data is all still there on the flash chips, but with no way to get it. So now might be a good time to make a backup. Any time is a good time to make a backup, but now is an especially good time.
If you keep getting these errors at the same rate, then you probably don’t need to do anything, since the errors are being corrected. If you’re worried, you could use BTRFS and enable checksumming of data.
Using a VPN (like Tailscale or Netbird) will make setup very easy, but probably a bit slower, because they probably connect through the VPN service’s infrastructure.
My recommended approach would be to use a directly connected VPN, like OpenVPN, that just has two nodes on it – your VPS, and your home server. This will bypass the potentially slow infrastructure of a commercial VPN service. Then, use iptables rules to have the VPS forward the relevant connections (TCP port 80/443 for the web apps, TCP/UDP port 25565 for Minecraft, etc.) to the home server’s OpenVPN IP address.
My second recommended approach would be to use a program like openbsd-inetd on your VPS to forward all relevant connections to your real IP address. Then, open those ports on your home connection, but only for the VPS’s IP address. If some random person tries to portscan you, they will see closed ports.
You know that stuff that appears on the screen before the operating system? That is the computer’s firmware. Sometimes it shows a brief memory check, sometimes it has a silly error message like “No keyboard detected. Press F1 to continue.” Sometimes it’s just a big image of the motherboard’s manufacturer’s logo. That firmware exists independently of the operating system, and will run even if you don’t have any operating system installed.
Most people refer to the firmware as the “BIOS”, but technically, BIOS refers to an API between the firmware and the operating system. About a decade ago, some people decided that “BIOS” was going to be replaced by “UEFI”, and operating systems would start having a new way to boot. What ended up happening is: the firmware on all recent computers supports both UEFI and BIOS interfaces (and everyone still calls it “BIOS”). Recent Windows versions seem to only boot in UEFI mode, but most Linux distros can boot in either UEFI or BIOS mode. The GRUB bootloader can also start itself up in either UEFI or BIOS mode.
USB live operating systems are limited in size and may have less functionality than other operating systems, so maybe they are only able to boot in one method or another. Try looking around in the firmware (or “BIOS” if you prefer) to see if you can change the boot method to allow both UEFI and BIOS operating systems.
It may help if you can take a picture of some of the firmware’s boot configuration menus.
I’m not using your phone app unless you pay for the cost of a burner phone.
I’ll just stick a hotdog in the fingerprint scanner.
So are you able to view content, but pay to download? If that’s the case, I could probably write a scraper for the site.
If you have to pay to even see the content, then you may have a bigger problem. Try pooling resources with some of your fellow students, to have one person download all the content, and then make it available to everyone else.
Another option is to expose your instructors. There’s a high probability that they are getting kickbacks, especially if this is at college level. Maybe in the form of 10% of each dollar spent by one of their students. Or, they might be getting free equipment or content from Docsity, in exchange for forcing students to use it, and offloading the costs to students.
When I was in college, one of my instructors used these “clickers” that cost students $40 per semester to rent. They used radio to allow submitting realtime quiz answers during class. Students were scored on how many questions they answered, not whether they were correct. If you didn’t pay the clicker fee, you lost that 10% of your final grade.
I was suspicious, so I looked into it. It wasn’t hard. The clicker manufacturer advertised kickbacks on their own website.
In many cases, they will cherrypick security fixes and other major bugfixes from the bleeding edge version, and put those fixes in the old versions of the software.
This is the same thing the PHP folks would do while the old PHP is supported. Once the old PHP is out of support but Ubuntu LTS is still in support, then the Ubuntu folks have to put in the extra work to do the cherrypicking.
You are correct that the Desktop Environment and Package Manager are the most important part of any distro. Of those, the Desktop Environment is the most important. Switching between Ubuntu with KDE Plasma and Arch with KDE Plasma is less visible of a change than switching from KDE Plasma to Gnome in any distro.
Most distros include all the major Desktop Environments: Mate, Gnome, KDE Plasma, and probably several more.
The biggest missing feature between Mint/Ubuntu/Debian is Container-based package management. This is an additional installation method, for “application”-like programs, usually proprietary. Debian has the infrastructure to run these, but you have to find or make the containers yourself. Mint has more support, in the form of a graphical package manager installed by default.
There’s really not much difference in the feature set of distros. Debian, Ubuntu, and Mint have a lot more in common than they have differences.
Desktop environments usually include a full set of these. I just use whichever comes with it.
Linux usually has the drivers already set up right away on first boot. You shouldn’t need to install any drivers. There’s very little bloat. Any superfluous packages are likely consuming no CPU time, just drive space. Every default installation comes with a media player and file archiver, but you can install VLC or RAR if you like them better.
They probably had a bad experience with one or more qt-based programs, or got a negative response when they filed a bug report to a qt program or library. Or, they were using some weird mix of old and new software, and ended up in a weird dependency loop that blocked a large set of packages on their system.
Probably. The most common distros will have the most community support.
Spend most of your effort choosing a Desktop Environment. Fortunately, this can be changed after installation.
Still no Linux support. Lazy fucks are just using Steam Play to get Steam Deck verified.
draw .io is closed source.