Is it OK to simply dd the 128GB disk to the 32GB disk using count to stop after the 16GB partition was cloned?

I think it would work, but it seems a little overcomplicated, you can just use the partition paths as if and of of dd directly, as long as the output partition is not smaller than the input partition. For example dd if=/dev/sdc1 of=/dev/sdd1 bs=4M status=progress

Your method would also copy the partition table I suppose, which might be something you want under specific circumstances, but then it would be a little harder to get the count right, just taking the size of partition 1 would be wrong, because there is some space before it (where the partition table lives) and dd would start at 0. You’d need to add up the start position and the size of partition 1 instead.

Personally I would prefer making a new partition table on the new eMCC, and create a target partition on it. Then you clone the content of the partition (i.e. the file system). This way the file system UUID will still be the same, and the fstab should still work because these days it usually refers to mounts by filesystem UUID in my experience.

If you make the target partition larger than the source partition, and you intend to use the full partition going forward you will additionally need to resize the filesystem to fit the new larger partition, for example with resize2fs.

In laptops the internal screen is usually attached over embedded Displayport (eDP) could be the same here. “native” doesn’t really say much.

Because we humans are very bad at putting in an accurate search such as: name:“60w” and description:“standby”.

I actually really like to do that. These days that only seems to work for flights and hentai though.

Maybe if it was more available and people were taught to use it it could be a little more popular. I think fundamentally it’s not such a foreign concept to say that you want specific things from specific categories. People do that kind of thinking routinely when searching for homes or cars.

If Qt or Java is doing it, then that’s still your program and not the WM, though?

The server is used for hole punching, to open up a P2P connection thorugh NATs and Firewalls. If it doesn’t work the server also relays the traffic between the clients.

Getting an end to end connection through todays internet is unfortunately not easy for an average user.

Using modern UEFI booting with a 1GB shared ESP and grub2 has worked just fine for me in the last 8 years. os-prober has always just found the Windows install and generated the necessary boot entry for grub. Windows has never trespassed into the Fedora or Ubuntu folder of the ESP as far as I can tell.

A microkernel teaching OS by Andrew S. Tanenbaum.

In 2017 the world (including Tanenbaum) found out that the Intel Management Engine uses Minix internally. Intel just kind of did that silently. So Minix is still around.

nix-darwin is kind of nice too, but only really for CLI tools. You can let nix-darwin manage your homebrew for GUI stuff, if you want.

I’d still take linux if I could though. macOS is just work mandated.

Mine sure doesn’t. I send it to sleep (since you can’t send it directly to hibernate like a normal OS), and the next day the battery is empty and it won’t start. This happens about once a month, and I haven’t found the common variable yet.

I wrote a script to turn the power of the the Wifi+Bluetooth chip off, then enumerate the PCIe bus again to start it back up.

The chip sometimes hung itself when using both. I looked for the bug and even found an Intel engineer on some mailing list admitting that they had issues with coexistance mode.

Just turning the wireless off and back on wasn’t enough I needed to reeinitialize the hardware and that was the best way I knew.

Programming in C and C++ just seemed way easier on Linux at the time.

The assistants at university would frequently distribute virtualbox images with Ubuntu within which we were supposed to do the homework. At some point I decided that just putting Ubuntu on my laptop directly would be easier because GCC is just right there in the repos, plus I was a little interested anyway.

Then it just kept being easy, for Java, Haskell, Scala, Python, everything was just supported nicely. The network simulators we used were Linux native, the course where we were reverse engineering binaries used GDB, Android development was simple with the tools and simulator being in the repos.

That said for gaming I still use Windows. And my workplace forces me to use macOS.

I generally do mention that I like my Fedora KDE, but I’m a little worried about SELinux. I have had two or three run-ins with it, and I think that would be hard to diagnose for a noob.

deleted by creator

so, my alarm company replaced it. installed the new smoke detector yesterday and… it just went off again.

Nice theory but it’s disproven by OP’s initial text

A language for noobs

That assertion surprises me; I find C easier to use than Rust.

Bring back skins in applications.

I love the Cristal Disk Mark / Info applications for this. Some cool Japanese guy, going by hiyohiyo, develops them as free software. And he is not afraid to make editions decorated with presumably his favourite Anime girls

Unfortunately the article of the post directly contradicts your point about ZLUDA improving:

ZLUDA appears to be floundering now, with both AMD and Intel having passed on the opportunity to develop it further

Following the links and searching around, I found this: Andrzej “vosen” Janik, the lead dev, says in his FAQ:

What’s the future of the project?
With neither Intel nor AMD interested, we’ve run out of GPU companies. I’m open though to any offers of that could move the project forward. Realistically, it’s now abandoned and will only possibly receive updates to run workloads I am personally interested in (DLSS).

I’m also using btrfs, but I originally wanted ZFS before seeing that it was only available through FUSE on my distro.

That’s why I even noticed ZFS was one of the features of Proxmox :)

They both use KVM in the end, so they are both Type 1 hypervisors.

Loading the KVM kernel module turn your kernel into the bare metal hypervisor.

It’s really just Debian with more packages preinstalled

And a custom kernel with ZFS support