Linux

48143 readers

497 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

174

Best practices for navigating file structure via terminal? (lemmy.ml)

submitted 1 year ago by Father_Redbeard@lemmy.ml to c/linux@lemmy.ml

116 comments fedilink hide all child comments

I've just started my Linux journey earlier this year. As a goal to learn how to self-host applications and services that will allow me to take back some control of my data. Immich instead of Google Photos, for example.

I have a local server running Unraid and 22 docker containers now. And then a VPS (Ubuntu 20.04 LTS) running two apps. I've learned a ton but one thing I can't seem to wrap my brain around is navigation through the file structure using only terminal. My crutch has been to open a SFTP session in Cyberduck to the same device I'm SSH'd to and try to figure things out that way. I know enough to change directories, make directories, using Tree to show the file structure at different levels of depth. But I feel like I'm missing some efficient way to find my way to files and folders I need to get to. Or are y'all just memorizing it and know where everything is by now?

I come from a Windows background and even then I sometimes catch myself checking via explorer where a directory is instead of using CMD or PowerShell to find it.

I'd love to hear any tips or tricks!

you are viewing a single comment's thread
view the rest of the comments

[–] nathris@lemmy.ca 5 points 1 year ago (2 children)

I know there is probably a historical reason but I hate how find parses its arguments.

Any other app would be fine --name or find -n.

Every time I use it I have to spend a few minutes checking the results to make sure that it's actually doing what I want it to do.

[–] bellsDoSing@lemm.ee 4 points 1 year ago* (last edited 1 year ago)

That's one of the reasons why the more modern fd is a nice alternative: it accepts command line args as you'd expect.

[–] BaumGeist@lemmy.ml 2 points 1 year ago (1 children)

Also every other search program has the needle as a positional argument and either reserves a named parameter to specify haystack, or has the haystack come after.

Apparently the find devs thought users would spend more time using it as an alternative to ls -a than finding specific files

[–] brokenix@emacs.ch 1 points 1 year ago

@BaumGeist @nathris try zsh plugins/ widgets in term, that helped me