- Joined
- Mar 4, 2019
Didn't systemd have some rube goldberg contraption for that, because that really sounds like a job for PID 1, you know.
It's exactly as bad as it sounds.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Didn't systemd have some rube goldberg contraption for that, because that really sounds like a job for PID 1, you know.
What do you use for shared drives? I sometimes resort to ExFAT or even FAT32 because pretty much any OS you'd care to use supports one or both of them.I have local $HOME on every system, but they also mount my main file server and a symlink in $HOME goes there so I also have access to shared files. I have wildly different OSes across my systems so sharing home itself would be a pain.
NFS.What do you use for shared drives? I sometimes resort to ExFAT or even FAT32 because pretty much any OS you'd care to use supports one or both of them.
..and shit like this just tries to obfuscate that fact and create a svchost.exe so that people don't have to read scary manpages to understand how anything about their computer works. Did they also leave it rough around the edges and half-assed it just to basically abandon development midway and be dismissive at every bug report made about it? That's the systemd way!
It's exactly as bad as it sounds.
PXE is still a thing. It's mostly thought of as an install mechanism but you can run without any local storage without any problems. Either NFS or iSCSI is common. It's one of the blackest of the black arts though. These days about the only people screwing with it for home use are Raspberry Pi users. If your Network Interface Card/MB doesn't support PXE natively you can use a stub loader off a USB stick to handle it.Yes, you can basically have your entire Linux OS on an NFS share, to make things simple for modern systems you could make a kernel with EFI stub and initramfs that mounts the NFS share(s) and then jumps into whatever init is in that share. Don't even need GRUB in that case (which I think actually can't do it). Could probably boot such a system off a floppy disk if you can get a modern kernel+busybox small enough. From that extreme you can take it down to every variation. Unixoids were made with multi-user networking in mind. That's like, their bread and butter.
I have some ancient MediaGX (Cyrix/National Semiconductor and finally AMD who then based their Geode SoCs on it) thinclients who have very reduced firmware and basically only can boot via network like this. I've not have gotten the nerve to try it out and from my research it's actually easier to just give them a fully-fledged BIOS and hack an IDE header in. That black. They're cool DOS machines because of their compatibility, low power consumption and decent speed for DOS applications/games. (they're basically Cyrix 5x86 cores on steroids with Soundblaster+OPL3+Gameport and VGA adapter built-in)PXE is still a thing.
I have one of those modem/router things that can share from a USB stick but that's rarely practical for more than critical shared files. It seems to handle most everything. I usually prefer to have something mounted directly and if every possible OS that needs it can, great.Linux NTFS sucks, but it works well enough for file exchange/shared files as I usually keep a USB filesystem with my entire home directory from my file server when I travel.
Does there happen to be any release notes?It's out
https://releases.ubuntu.com/22.04/
https://cdimage.ubuntu.com/kubuntu/releases/22.04/release/
https://cdimage.ubuntu.com/lubuntu/releases/22.04/release/
https://cdimage.ubuntu.com/xubuntu/releases/22.04/release/
https://cdimage.ubuntu.com/ubuntu-mate/releases/22.04/release/
https://cdimage.ubuntu.com/ubuntu-budgie/releases/22.04/release/
play -n synth noise
For people who want slightly more out-of-the-box solutions can check out "Sunshine" and "Moonlight" (no, I haven't tried either of them)I attempted years ago to encode the entire desktop via ffmpeg and stream it via netcat to the target computer, all in hardware. Hardware encoding was utterly broken years ago and all that did then was make my AMD GPU lock up. Now it works fine, HEVC encoding/decoding is supported by both machines in hardware and at the resolution of the laptop screen with 30 FPS the streaming is completely fluent and with little to no noticeable (for me) latency and doesn't even task the weak celeron laptop much. (playback is with mpv via "low latency" profile in fullscreen) Keyboard/mouse input I do via a homebrew uinput solution, which basically works like a KVM which switches the output hard to the target machine. (and listens to a specific key combination to switch back) I know there are more high level solutions for X but I found them to be buggy sometimes, uinput works at kernel level, X isn't even required.
I take issue with this, I don't have an IBM laptop, my "free" system is a Dell Wyse Cx0 C90LEW; a 32 bit monocore computer with an IDE interface for hard drives and 1 GB of ram. IBM Laptops are overrated.Also,