132
This Week in Learning Linux (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
33 comments fedilink hide all child comments

I didn’t get to spend as much time tinkering and learning this week, but I still learned some new things!

  1. Wireguard is great! I had been using OpenVPN because when I initially set up my machine, my VPN had a bug with Wireguard. I was setting up a raspberry pi today for some more tinkering, and I decided to try Wireguard to see if the bug was fixed. Not only is it fixed, but Wireguard is much easier to work with. Not hating on OpenVPN, but I’ll definitely be preferring Wireguard going forward.
  2. Proper use of find, particularly with regex. This is ongoing. I’ve been using find for awhile, but not with full understanding of it’s options and syntax. I’m starting to get a better understanding of how to use it to find and manipulate the files I’m looking for. One of the biggest things that’s tripping me up with find and regex is designating the path.
  3. How to set up a new user. This was interesting. I already knew the basics, adduser -m username, sudo passwd username, but what I didn’t know anything about was --skel for copying over the skeleton shell config files. I didn’t even know the skeleton config files existed.
  4. The shell prompt can be customized. This was interesting. I was setting up a non root user on a vps that I have, and after creating the user, all I had was the $ prompt. No user@host, and no working directory. After some reading I found that adding PS1='$(whoami)@$(hostname):$(pwd)$ ' to ~/.profile will show a more traditional user@host:working/directory$ prompt. I’m sure this is not the only way to do this, and may not be the best way to do it, but based on my limited knowledge, it is the way that I’m currently doing it on my vps.
top 33 comments
sorted by: hot top new old
[-] [email protected] 24 points 1 year ago

As someone also starting to get into Linux I appreciate these posts

[-] [email protected] 5 points 1 year ago

I’m glad they’re useful for you!

[-] [email protected] 16 points 1 year ago

check fd-find, "A simple, fast and user-friendly alternative to 'find'". Really good trust me

[-] [email protected] 2 points 1 year ago

I will look into that. Thank you!

[-] [email protected] 14 points 1 year ago

If you code adding the current branch to your shell prompt will change your world.

Also, if you are getting good use out of find, you should learn to pipe the output to GNU parallel. Put those cores to work!

[-] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Depending on your distribution it may also just be called fd in the package manager

[-] [email protected] 14 points 1 year ago

Check out using something like oh-my-zsh if you want a deeply configurable shell experience that isn't super far off the stock bash path.

[-] [email protected] 16 points 1 year ago* (last edited 1 year ago)

I kinda like fish tbh. The dracula theme is much better and more features than stock zsh

[-] [email protected] 8 points 1 year ago

There's also oh-my-fish.

[-] [email protected] 7 points 1 year ago

Fish + starship is a killer combo.

[-] [email protected] 6 points 1 year ago

There's also oh-my-posh, which was originally a powershell prompt, but it was rewritten as a go application that works on (I think all) mainstream shells.

[-] [email protected] 1 points 1 year ago

I’ve heard of oh-my-zsh, but I haven’t wanted to deviate off of bash until I have a good grasp on bash first.

[-] [email protected] 1 points 1 year ago

The project aims to make Bash vs Zsh as similar as possible. There is little difference except for customization. Switching to Fish or Spaceship will jump that barrier.

[-] [email protected] 1 points 1 year ago

Interesting. I’ll give it a look.

[-] [email protected] 13 points 1 year ago

My advice: make your home directory a git directory. You can ignore everything in a gitignore, then make exceptions, like your vim configs, shell configay and so on. You have version control and on a new host you can just git clone and bam, you have your usual setup.

[-] [email protected] 16 points 1 year ago

Or simply create a dotfiles repo and symlink configs.

[-] [email protected] 5 points 1 year ago

Yes, this. Don't put your whole home directory in git.

[-] [email protected] 1 points 1 year ago

I’ve never used git to publish/make myself a repo before. That’s something I’ve been meaning to learn but haven’t quite gotten there yet. However, with the amount of tinkering, and breaking I’ve been doing, I think I’ll move it up on my priority list.

I’ve also got shell scripts I’ve been writing and tinkering with and having proper version control (versus script, script.copy, script.copy.bak…) would also be nice.

[-] [email protected] 2 points 1 year ago

It's not actually hard if you know some high level basics. I recommend to use a git GUI or tui, makes things even easier. I personally use lazygit.

[-] [email protected] 1 points 1 year ago

I’m diving in. I set up gitea on my server. Now I need to learn how to use git with gitea.

[-] [email protected] 2 points 1 year ago

Amazing. I've switched to forgejo, thr gitea projects are amazing and I'm awaiting federation.

[-] [email protected] 12 points 1 year ago

You might be interested in the ArchWiki page on prompt customization: https://wiki.archlinux.org/title/Bash/Prompt_customization

[-] [email protected] 2 points 1 year ago

Ohhh. Thank you. I will give that a read through!

[-] [email protected] 5 points 1 year ago

re 1: out of curiosity, do you encounter dnsleaks when using wireguard?

re 4: you can also check out https://starship.rs/, which helps configure shell prompt very intuitively with a toml file.

[-] [email protected] 1 points 1 year ago

DNS leaks don't depend on what VPN protocol you use. They only depend on how you configure your DNS resolver and routing.

[-] [email protected] 1 points 1 year ago

I didn’t k ow there were dms leak issues. I will investigate. If I’m finding that I’ll likely switch back to openvpn

[-] [email protected] 4 points 1 year ago

Regex is not the most oftenly used feature of find. Have you already learned how to use -exec, -delete, -print0 together with xargs?

[-] [email protected] 1 points 1 year ago

That’s what I’m finding. I’m not certain I need regex for what I want to accomplish with find. I’m reorganizing my media libraries, and I have a mix of mp4 and mkv files. I want to be able to find all mkv and mp4 files and move them using regex like '.+\.(mp4|mkv)'

I have learned how to use find with -exec and -delete, but I haven’t gotten to -print0 or xargs yet.

[-] [email protected] 2 points 1 year ago

You don't need a regex for that, you can write \( -name '*.mp4' -o -name '*.mkv' \).

[-] [email protected] 1 points 1 year ago

Thank you! That worked perfectly. I had to do some digging through the man page to find that -o flag!

[-] [email protected] 2 points 1 year ago

I really need to learn find.

How is the rust replacement?

[-] [email protected] 3 points 1 year ago

How is the rust replacement?

fd > find. It's a lot faster, and I find the syntax to be better.

[-] [email protected] 1 points 1 year ago

I’m not familiar with the rust replacement

this post was submitted on 01 Feb 2024
132 points (95.8% liked)

Linux

56005 readers
1072 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]