I have heard less about phone chargers failing catastrophically. They also handle much less power (except the fancy ones), and I haven’t seen a hot phone charger adapter yet, but plenty laptop chargers of which some were just very warm, and some so hot just on its outsides that it was uncomfortable to hold it in hand.

this is why I’m more worried about laptop chargers

I would assume that landfill laptop manufacturers are trying to minimize costs even harder on the charger.

but what timeframe do you mean with “anymore”? laptops made in this decade, or the last 10 years, or something else? there’s plenty of old laptops that fitinto OPs category.

I think 5W probably can’t be achieved, maybe with chromebook-like hardware, but I guess GPIO could be solved with a USB accessory

in my opinion the bigger problem is the fire hazard of an unsupervised charger. I have seen enough that runs super hot, and even if it doesn’t, I just can’t trust them.

but what will fix the fire hazard of the charger? how will you be able to keep it plugged in 24/7?

fdisk cannot convert the partition structure, but gdisk can, though you better have a full backup bedore attempting to do it

MBR can be converted to GPT. gdisk can do it, in fact if you run it for an MBR structured disk it will automatically do the conversion in memory, and you can check the results before writing it out. windows also has a tool for that.

It’s probably the MIT licensed rust reimplementation of coreutils and sudo-rs

KDE 7 is already on the horizon? 6 os still pre-release, isn’t it?

well I guess it cannot run medium sized AI models or something. but also, the question arises what is their price for a mid level phone

did you make these yourself? if not, could you cdo an ls -l /dev/mapper? it shows which name corresponds to which dm device

how did you add grub to the windows bootloader’s menu? I thought microsoft made this impossible, along with adding older windows versions

do you know that use device mapper? what kind of device is /dev/dm-1 ?

“dmsetup info” might help

did you check it /proc/cmdline if the params were taken into account? perhaps you edited the config but didn’t update the initramfs

that’s only the X11 “driver” for it. nouveau is built into the kernel, the way to “uninstall” it is to make it not get loaded, by blacklisting it

https://wiki.archlinux.org/title/Nouveau

but this does not seem to be the problem

what does fit well with the youtube interface though?

oh, that’s right, sorry. it must have changed in recent years.

so I haven’t either found a definitive answer to whether it is a default mount option, but the closest I found is almost it: man mount says to look in man ext4, and there itsays the defaults are determined by the filesystem superblock.

the superblock’s settings can be viewed with tune2fs -l /dev/your_blockdev, and according to the “default mount options” line I indeed have acl enabled by default on all my ext4 filesystems.

so in the end, the default is determined by the tool that makes the filesystem. mkfs.ext4 reads them from /etc/mke2fs.conf if not overridden with an argument. on my system tue acl option is right there in this file.

and that also means that this depends not on your current system, but on the system where the filesystem was created.

that sounds to ge good advice, but I’m pretty sure they would yave done that themselves, if they had a backup.

and, if you read the whole post, you’ll know that they are physically unable to keep a backup.

So does it wait until it has found all the matches to run the command as a giant batch instead of running it as it finds matches?

almost. it runs the command in batches, if you have few enough files it may only run it once. this shouldn’t make it slower, but actually faster.

and yes, linux does not use ACLs by default. on ext4 usage of ACLs is not even enabled by default, but only if you set it up with the right mount option

an exception to that is the initramfs that the bootloader uses. its creator adapts it to your system so that it can be smaller.

hmm I’m not sure, I think that would throw sequential read/write performance out of the window, surely on HDD, maybe even on SSD to an extent. but, such a thing can probably be added with a device mapper device.