Did you set the font color as green or amber? It won't work otherwise!
this post was submitted on 21 Apr 2025
548 points (97.4% liked)
linuxmemes
24588 readers
1696 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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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 remove France.
founded 2 years ago
MODERATORS
Funny enough, I learned terminal commands initially on a green on black monitor. I can't use the terminal unless I set it to green on black. My brain literally won't remember any terminal commands for any flavor of Linux until I change the color scheme.
I'm not quite that bad but I definitely prefer green or amber on black terminals. That's how a command line is 'supposed' to look because that's what I learned on.
I learned on a Tandy, so I want color 7 on color 0.
Did you say "Im in" afterwards? Otherwise it doesnt count.
I'm so old we used to call it BackTrack and we burned it to CDs π
Was backtrack before or after whoppix?
After.
Whoppix was the first iteration followed by whax and then backtrack.
It went from Backtrack to Kali. I've never heard of whoppix tho.
I must be really old then!
Heh, I remember tinkering with linux waaay back in the day. I had a shitty Slackware install I farted around with, and something I was doing required bootstrapping gcc. I clung to that man page like it was the last lifeboat off the Titanic, but by the end when it worked I felt exactly like this.
In Uni I ran Gentoo as my daily driver. It was stupid, but I learned a lot.
Trying and failing to get a working desktop environment, using IRC on the command line to get help from people who knew what they were doing and could advise a dumb kid like me, following their advice and getting a working DE after a reboot was the most hackerman I ever felt. I was convinced I was real hot shit. In actuality, I'd followed the advice to tweak the kernel config to get working drivers :))
Haha, yep. My very first linux install I had to do similar because I had a fucky video card that X11 didn't support natively, ultimately I had to, er, acquire a commercial X server that did support it to make it work. It was a mess.
How I felt after adding encryption to my Immich server
Wifi is not working help :((((
me when I accidentally use the tree command on the root directory:
It has some of the most accurate hacking logic.
The plot on the other hand I disliked.
I know this one! You set your timezone then try again
Um... shouldn't it be:
sudo su;
apt-get update;
flatpak update;
Or am I missing something?
You should never use "sudo su". That's a big security no-no.
~$ sudo apt update
[sudo] password for {your user name}:
-command executes-
~$
Does that1 security no-no matter on a single-user system which (almost) never leaves the sight of said user? Or is that just a matter of 'don't do this on a server'?
It's not a good habit to get into. Even if you don't have anyone at homebto mess with your system, these kinds of habits tend to follow people around. You'll get comfortable at work and run something as root, but forget to deescalate permissions.
Just using sudo as your user runs only that command or script as root, then drops back to your limited user account.
Say you got busy or distracted and walked away, anyone who was able to access your system between the end of the command and the time your system auto locked would only have the access level of your user.
Use sudo -i instead, gives you an interactive shell without running the su binary with sudo, which is unnecessary
Edit: it's i not I
Thank you, that's a switch I hadn't looked at. I'll admit though, I'm on Mint, I have a nice built-in GUI that works nicely.
It's a really important switch for doing things like setting up wireguard, which has protected directories, you can't actually enter the directory for wireguard setup without sudo -i
(I mean technically you probably can with sudo su, too, but this is more elegant and less redundant)
My phones keyboard decided to capitalize, it's -i
Thanks, we suffered the same fate.
Sudo apt-get update && sudo apt-get (-y if you want it to do it automatically) upgrade
There's also
sudo apt update
if you only want to apply the superuser permission one specific command instead of a lot of commands
What's the problem exactly? There are many ways to do it, and I think saying you run apt-get update is quite fine even if you're not explicitly saying that you run it as root. And he may not have flatpaks.