This is bad and harmful parenting to me and should be condemned in an age where we know better.
Compared to what?
Quite literally in the age immediately prior to this one, the method of teaching the lesson would’ve been direct physical punishment of the go-get-me-a-switch variety.
OK, but… if a device presents a UI of some kind, with a control that is presented to the user to perform some action, and the device fails to perform that action when the control is operated, then the problem is NOT with the user. There is either a system failure, or a design failure.
Bluntly, if the situation is “I pressed the button and it didn’t do the thing”, that is the correct time to involve tech support. It should do the thing when the button is pressed, that’s what the button is for.
Easy, we’ll just power cycle the entire building. All current problems will go away.
Sorry, best I can do is 1 million more lines of LLM-generated sloppy spaghetti code that will be reviewed by no one, but implemented immediately to meet management’s target metrics for AI use.
Until the trash gets picked up.
OK, so if you can pass the host root filesystem to a container and then write files or execute code with root privileges on that filesystem, I would definitely consider that a container escape. You’re executing arbitrary code on the host from within a container.
On affected Omarchy systems, this means that the default user and all processes launched in that user session have access to root.
Hmm, maybe I’m misunderstanding. Does “all processes launched in that user session” not include containerized apps?
Once more for the people in the back:
CONTAINERS ARE NOT A SECURITY BARRIER
If you are relying on the container system to isolate and protect the OS from containerized apps, you are wrong.
I generally feel more comfortable having /home as a separate partition. It makes editing my partitions with external tools like gparted very easy, and I can just wipe /root whenever I like without having to think too much about. Also, are we considering btrfs to be reliable now? Last time I looked at it, it was still in the prototype/unstable phase and I chose ZFS for my server instead.
Another reason I keep /home separate is that I have systems with multiple Linux versions installed. Each has their own /root, and they share /boot, /swap and /home.
You’re welcome, and yeah growing pains every time with a new install. But you do it a little better each time.
One recommendation - when you do reinstall, don’t use the default/automatic partitioning. Manually set up your /home directory as a separate partition from /root. This lets you reinstall the OS without having to touch your user files. When you reinstall again, all you have to do is select the existing /home partition to use as the new install’s home (and make sure not to format it). This makes your install a lot more flexible, and your OS a lot more disposable.
If you do manual partition configuration, don’t forget to also create a /swap partition that is at least 1.5x the size of your RAM.
I could probably backup most of my important data to a flash drive but I’d rather not.
You should ALWAYS back up any important/irreplaceable data before making any changes to your hard drives, even if you think the risk is low. Accidents happen.
You can move the drive from one slot to the other, the drive’s UUID should not change. You’ll just need to change the boot drive selected in UEFI. Physically swapping the drives will be faster, easier and less failure-prone than trying to move your boot and root partitions between drives.
For editing drive formats and partitions, the best tool is gparted: https://gparted.org/
It’s convenient to have gparted installed on a USB drive so that you can live boot it and use it to make changes to the system drive(s). With gparted you can simply erase the Windows drive and create a new partition formatted for Linux (probably ext4).
If you are not already familiar with editing disk partitions and formats, you should read some tutorials first: https://gparted.org/articles.php
As for encryption, some Linux installers have this as a selectable option during the install process. If Mint does, you should consider reinstalling anyway to use that, as you are more likely to have it working properly.
If you just want to encrypt your data partition(s) you can implement LUKS with cryptsetup: https://linuxvox.com/blog/linux-luks-encryption/
Note that this is the most basic use, it does not cover FDE. If you want to also encrypt /boot so that your computer will not start without being unlocked, that is more complicated to set up:
!! YOU SHOULD READ A LOT OF INFORMATION BEFORE ATTEMPTING THIS !!
https://askubuntu.com/questions/1470391/luks-tpm2-auto-unlock-at-boot-systemd-cryptenroll
https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html
Be aware that doing anything wrong in this process is likely to leave you with an unbootable system, and unable to recover any data from the encrypted partition/drive. You need to be sure that the steps you’re going to take are relevant for your hardware and OS before you start, and that you have all of the necessary utilities installed.
Again, if Mint has a selectable option for this in its installer, you will have much better chances of success reinstalling with that.
Don’t skip the backup.
Nice. There’s probably nothing in there but an adapter board and a ROM chip running just enough of the firmware to report the drive as 16TB.
Where did you buy this at? Name & shame the seller?
Whoa, that looks like trash. Are you getting a refund for that?
Can you send a picture of the bottom of the drive with the control board?
Also what adapter / enclosure are you using?
Curiosity, mostly. And yes, it could be a “factory second” labeled for local sale.
A SMART report would be interesting too. Perhaps it’s a relabeled old drive.
@stumu415@lemmy.zip Actually, thinking about this a little more, it’s possible that you have a used data center drive which was pulled due to test failure. Data center drives get replaced all the time when they show any minor signs of failure, or sometimes just because they reach a certain number of operating hours, even if there’s no issue. If the capacity checks out, and SMART shows minor issues or just long operating hours, this might be an entirely usable drive (in an array with some redundancy).
A suggestion - plug it into a USB SATA adapter/enclosure and check it with ValiDrive: https://www.grc.com/validrive.htm
(unless you’re just going to return it without opening the ESD bag)
And /e/OS, which is available pre-installed on some devices sold by Murena.
And yet, somehow Microsoft can’t figure out how to monetize video games.
Every single generative model in existence was produced by stealing the work of artists for training data.
There is no nuance to this. Never mind the argument about generative AI taking away potential future work from artists. The training of these models is theft now. To use these models is to be complicit in the theft.
Edit: the people who downvote this while making no counterargument are doing so because they wish to remain in denial, so that they do not have to admit to themselves that they are complicit in the theft.
This is what happens when you don’t unionize.