Always remove the French language pack from the root dir
this post was submitted on 11 Nov 2023
240 points (84.5% liked)
linuxmemes
21611 readers
1606 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
fr
Gotta delete the French language pack
Last September I installed Debian 12 in my laptop with an encrypted LVM. Then I tried to add a secondary SSD, also as an encrypted volume, by following some random tutorial I found (spare me, it was my first time fiddling around with an encrypted installation). The next thing I remember is that I was in an initramfs shell trying to fix the boot process 😅🤣. Since I was running low on patience (and it was like 3 AM) I simply decided to nuke the install and start again. Eventually I was able to configure the SSD correctly, but this event reminded me how easily is to brick your system if you're not careful enough. Fun times.
It's things like this that prevent me from using Linux more.
I force myself to use it for projects where it's an option because I feel I need to learn it better but I kind of dread it every time.
Inevitably I'm stuck frustrated reading conflicting guides from years ago and wondering just how badly I'm going to fuck things up this time.
Sometimes it all feels so esoteric.
I've always loved Linux, even when it was kicking my ass. I can't imagine approaching it with the attitude "Ugh, I have to force myself to use this thing, and I know that it's going to frustrate me".
That sort of thing is a self-fulfilling prophecy, because everybody has cognitive biases. Since you expect it to be frustrating, you're going to remember all the times that it is and forget the times when it isn't.
It's a chicken and egg situation.
It's frustrating because I don't know it, and I don't learn it because it's frustrating.
Get on it. If you can manage to daily drive it for a few months I think you'll learn a lot. When I jumped ship I only knew basic commands like cd and ls.
Can't, really. Have several critical Windows only apps.
What kind of things do you need to do? For software development my experience is that it's just install and you can start working. Maybe one tutorial to get kubernetes running locally.
Generally deploying some kind of service.
Excuse me, but that type of foolishness requires -- no-preserve-root nowadays
Not in this case. It's */ here so it expands to directories at current location. I'm sure that's a typo though
I'm not brave enough to test it on my distro, so I'll take your word on that lol
You can do echo */ and echo /* to see how they expand. Also rm -rf / already is enough without the * as it already is recursive
* is there to bypass the need for --no-preserve-root
rm -rf / needs --no-preserve-root on GNU coreutils, I think.
yes
why do they even have that lever
Originally, rm would merrily nuke your whole filesystem if you told it to. At some point, someone thought that was a pretty stupid default behaviour, so they added that flag to change the default to not nuke your entire filesystem. However, they made the change backwards compatible in case someone still needed the old behaviour. I can imagine in a container or throwaway environment, it might be vaguely reasonable to expect to be able the blat /.
See also:
Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure.
-- Eric Allman
I'm aware of how recursive force remove works. I'm just kidding around.
Anybody brave enough to tell the MS rep this on patch night??
(You have backups, right?)
it's/*
The one time when misstyping your password was a good thing
You emptied your home directory?
Depending on where that terminal is open, you probably haven't really done much damage
Do people actually do this?
im gonna have to obtain an testing laptop for this
make a snapshot of it and then just run the command to your heart's content
Wouldn't rm -rf / eat /home, too? That doesn't get backed up in a snapshot...