Bonus points for using the mouse to copy/paste![]()
post
an hacker?
Yes. It's french
Trolling is a art.
An 'acker
Let's be reasonable: We were all at some point at the stage where doing anything at all in the terminal made us feel like a god.
It's weird to have grown up with things like bbc micro and MS-DOS and see how alien the terminal is to people who didn't.
Back then CLIs were all over, even like library catalog terminals, were CLI. TBF some still had card indexes though.
At university everyone had to ssh in to the email server from whatever tty client even on windows (nt4/nt5/98/2k/mackintosh PCs).
You definitely didn't feel like any hacker. The hacker level thing was to successfully connect via GUI mail client and actually have your emails update and sync properly - very few bothered.
Do you mean telnet?
Very possibly.
I vaguely remember using putty on port 22 which i thought was ssh, but maybe it was telnet. we were leaving the 90s by then, so I think ssh was around. Might also have been different protocol on the uni LAN vs WAN connections.
The libraries I remember might have been direct terminals to local server. Few catalogs were available even on the uni-wide LAN. No big deal really since you're going to have to go there to find the book anyway.
The catalog room was an acceptable place to have a chat or lament the size of the reading list.
We were all at some point at the stage where doing anything at all in the terminal made us feel like a god.
Some of us were at the point where GUIs weren't a thing and the terminal was the only option.
Until your shit got all fucked up because you added a third party repository. And then you have to manually remove lock files and fix the pkg database and mess with .conf files and manually uninstall specific versions of dependent packages, and then manually re-enable some remote repo.
Then you actually kind of do feel like a hacker.
Until youβve done it like 10 different times, then you are just annoyed. Still a better love story than Twilight.
You copy paste the command.
$ sudo apt update
-bash: sudo: command not found
$
Your distro doesn't set up/install sudo by default, so your first task is installing sudo, then understanding /etc/sudoers syntax and understanding why the command to atomically replace /etc/sudoers is visudo and why on a multiuser system there's value to atomic replacement. In the meantime, you probably learn about su and maybe, if your distro has disabled them, how to enable switching to the kernel virtual consoles on tty1 through tty7 so that in the meantime, you can do things as root while staying logged in. Also, you're going to learn about environment variables, so as to set EDITOR, and where your shell config files live, what a login shell is, and in what shells ~/.bash_profile, ~/.profile, and ~/.bashrc run. Also, you first try running visudo as a regular user, but your distro places visudo in /usr/sbin instead of /usr/bin, so you can't figure out why it's not installed and are going to learn about the FHS and mlocate and updatedb so that you can find /usr/sbin/visudo and dpkg -S so that you can figure out which package it's in and confirm that it's actually installed and learn about PATH.
shit got all fucked up because you added a third party repository
Dependency hell is always, always, self-inflicted.
apt is only SLSA1 or 2 anyway, so there's a lot more wiggle room.
We all have to start somewhere. I remember when that was me.
amen to that LMDE and use the GUI here
Even better the SECOND time you do it with the up arrow.
You know. Just your standard Hacker, hackin'.
$ !!
It keeps its handses on the home row.
sudo !! Is nice but I mostly use the up arrow to repeat something long and complicated I did 10 minutes ago. The joke there is sometimes that takes too long too. So that's where history | grep 'keyword' is nice
You may enjoy ctrl + r. It hasn't completely replaced grepping history for me but it's close.
history | grep 'keyword'
If it's bash, it's using readline, which is in emacs-like mode by default, and so you can probably use Control-R to do a reverse i-search (incremental search). Enter to invoke the command. Control-C to abort i-search.
If a search matches multiple candidates, tap Control-R multiple times to cycle back through results.
EDIT: Also, ! has a built-in search, so if you are sure of the starting string, you can just do that. I generally prefer to use the interactive search to confirm that I'm not invoking something wonky.
$ touch a
$ rm a
$ touch a
$ !rm
rm a
$
Start btop in another full screen terminal, and then run apt update. Then you're fully in the matrix.
Me when i fork dwl just to add a few patches that i did not create myself, just so i can make my own package for it.
"You know, i'm something of a developer myself."
good way to compromise your system
https://www.makeuseof.com/why-you-shouldnt-copy-paste-commands-from-internet/
Bitch please: curl install.sh | bash -
When i tell claude to change the filenames from spelled out dates to hyphenated dates XD

top 50 comments