Someone that hasn't discovered tilde yet.
rotopenguin
joined 2 years ago
I think the problem with xournal is that it cannot ask a file portal to give it access to two related files at once. "I want to let the user pick foo.pdf.xournal, and also give me access to foo.pdf". So the next best thing is to give it the "access any damned file" permission, and let Xournal grab whatever it wants. You get the same problem with video players - you could take away their permission to open-any-file, but then they won't be able to pick up a related subtitle file.
Localsend only does files/pictures/a quickie bit of text, but I find it more convenient and reliable than kdeconnect. Localsend's iphone app is in better shape too, if you need that.
It's one of those Windows features that I would accidentally click once, and then immediately go hunting for how to disable it.
640x480 sounds like the typical fallback if there is no EDID/DDC data and the card is going ahead with the most bare-minimum signal that any screen should accept. Maybe there's dumb state sitting around in the video card. Maybe, because everything is now so smart that it's stupid, the monitor itself is the one remembering weird state. Maybe it doesn't like the text-mode flip or a DPMS command at the end of an update-reboot cycle, so its EDID responder loses the plot. Who the fuck knows what goes on in all this garbage firmware?
Linux bootloaders discover the correct linux volume by UUID (which is in the filesystem), or PARTUUID (which is in the GPT table). It'll look at every drive, and when it sees the matching one it'll look in that partition, find the kernel & initrd, suck them into ram, and launch the kernel.
The main problem with moving drives around is - where is the EFI firmware looking for the bootloader in the first place? If you read efibootmgr, the efi data is pretty simple and very much tied to a hardware port. The EFI takes the most preferred bootloader entry, goes to that drive, and runs a file like "\EFI\grub\grubx64.efi". If that file isn't right there, the EFI isn't going to look elsewhere for it.
There is one bootloader name that EFI will pluck out of the blue and (smash the Fx key) offer to you as a boot option - "\EFI\BOOT\BOOTX64.EFI". Self booting usb installers use that, but you could use it too. Put all the other files that go along with the bootloader in with that boot folder, and rename the appropriate .efi to bootx64.efi.
One thing that I've done on odd setups is to put rEFInd on the efi partition as the boot\bootx64.efi loader. It'll do a pretty fancy job of detecting what's bootable (may need an additional filesystem_driver.efi), or even chain into grub to finish the startup.
The "AI boom" means that Intel is going to take die space from the GPU and give it to an NPU. That's how you get Windows 11®️ CoPilot™️ cetified.
Lol I guess they could mount the deck to show as a scoreboard.
Frick, I'm going to have to check out Farmer Was Replaced.
It exists because, long ago in a galaxy far far away, a sysadmin ran out of space on a drive. The system was split between two 10MB(?) drives, one was / and one was mounted at /usr, for User data. They moved some of the programs to a folder for a dummy user, /usr/bin, and put that in everybody's PATH.
Everybody kept on doing things that way ever since. Social momentum is funny that way.
I've done pretty much that, by way of debootstrap. It's a fun way to set up a system.
I think that live-task-non-free-firmware-pc (gotta have the nonfree apt.sources tho), linux-image-amd64, sudo, and systemd-timesyncd are just enough to get started. Then add gdm3(which pulls in a bunch of gnome), and a terminal (I like kitty & ptyxis).