What commands are needed to run to get help?

Install neofetch for basic hardware info.

Additional as a new ARCH user, I found this cheat-sheet online that has been helpful:

Pretty good overall description. If you got to do it in one page this would be it. Here’s my Arch cheat sheet:

pacman -Sy # Sync package list
pacman -Ss # Search for package
pacman -Si # Info for package
pacman -S # Add package
pacman -U # Update package
pacman -Q # List installed
pacman -Ql # Package files
pacman -Qo /path/file # File belongs to?
pacman -Rs # Remove pkg/deps
pacman -Syu # Sync and Upgrade
pacman -Qdtq # Unneeded deps.
pacman -S --asdeps # Install pkg as dep.

Remove unneeded dependencies:

pacman -Rs $(pacman -Qtdq)

Making List of Installed Packages for Reinstall

pacman -Qqet | grep -v “$(pacman -Qqg base)” > pkglist

Reinstall from Package List

pacman -S $(cat pkglist)

AUR

yaourt (uses same syntax as pacman)

ABS

pacman -S abs
abs

Local

/var/abs/local

It’s dangerous to run makepkg as root.
Add regular user to be able to add package dependencies:

visudo
USER_NAME ALL=(ALL) NOPASSWD: /usr/bin/pacman

Makepkg are regular user and add dependencies:

makepkg -s

Add package to system with:

pacman -U -pkg.tar.gz

What? Me Worry! I know what I know because I know it …

Typically, you should not sync your local package database without upgrading, too. While syncing the local package database is not harmful in itself, installing any new packages on an outdated system with a synced local package database will result in what is called a “partial update scenario”, where new packages may have outdated dependencies. This can lead to all sorts of issues, ranging from mild annoyances to unbootable system.

So, whenever you sync your local package database, you should update as soon as possible, lest you forget that your package database is new, but your system is outdated, and you install something new. Or simply put, never run -Sy but always -Syu.

1 Like

Thanks! I appreciate your heads up.

Since I’ve been running EndeavourOS I believe that I’ve been syncing and then upgrading. I have done that quite often in a shot time.

But, a reminder is very useful. Once again, thank you!!!

That’s quite the old list you’ve come across. Yaourt hasn’t been a thing for a rather long time.

And I second @Kresimir , please be very careful using -Sy flag.

2 Likes

As a new user I found this old chest-sheet online. Might be ancient, but has been helpful at the moment. However, basic help for pacman can been found running pacman – help in cli: Don’t know if that’s what you are after?

As follows:

pacman {-h --help}
pacman {-V --version}
pacman {-D --database} <package(s)>
pacman {-F --files} [options] [package(s)]
pacman {-Q --query} [options] [package(s)]
pacman {-R --remove} [options] <package(s)>
pacman {-S --sync} [options] [package(s)]
pacman {-T --deptest} [options] [package(s)]
pacman {-U --upgrade} [options] <file(s)>

Hopefully this help, that is not what you are seeking, please info, and I’ll dig deeper!

Thanks! I’ve been warned about “using -Sy flag.”

What? Me Worry! I know what I know because I know it …

Just added a new button to Welcome: Logs for troubleshooting.

With that button you can select many different logs about your system, send them to pastebin, and show the returned URL here. Then others have better chances to help you.

The button runs the eos-log-tool, which lets you choose what logs you want to show.
The default set of logs are already selected, but you may choose a completely different set of logs.

logs

tool

If new log items are needed, just let us know! :sweat_smile:

10 Likes

Excellent work!!!

1 Like

Nice!

1 Like

Thanks for the heads up!

@manuel awesome work, that sounds like it could help all of us a whole lot. That’s fantastic!

1 Like

Very nice!

There should be a pinned post or a tooltip or something somewhere that could help with general troubleshooting for newbies and forgetful people.

Just saw a post and wanted to ask for hardware details, but I totally forgot how the command is. Just this is how I am, if I don’t use something for a few weeks I just forget. It could save a lot of time if people knew what to post and what to check and try before posting.

It’s not good if it’s on another part of the site, most people don’t check the wiki for sure.
Almost every post starts like this: please post journal and hardware and whatnot.

edit: I just saw the pinned post, mentions a lot of other things and there’s only one command. Still think there should a dedicated post with a few commands. Hardware info, journal if it doesn’t boot, dmesg if freezes etc.

Been here more than a year, opened that menu too once or twice, it never registered in my mind, it’s a little bit hidden away in my opinion. Pinned post is more visible. I just see the posts and the basic logs are missing most of the time.

I agree.

Right. However, they could be “ignored” as well, oftentimes :wink: :sweat_smile:

Honestly I didn’t know where to look, this kind of general info could have helped, at least me a few times. I would have noticed it, if it was pinned for sure. A short post for general troubleshooting with a few commands, rest of it in the wiki.

Anyway this just occurred to me, while trying to remember that inxi command. I didn’t even know what the command is called not just the options. For some reason it’s hard for me to remember command names that don’t really make sense in my mind, just like phone numbers. If I use it often I remember it, otherwise I have to spend like 5 minutes googling the right command.

1 Like

You are not alone. I am right there with you :slightly_smiling_face:

inxi has a lot of options as well which perhaps doesn’t make it that “memory friendly”.

For getting a general picture inxi -Faz should be enough though in most cases.

I found it by now and used it multiple times before. Only 8 characters, yet I couldn’t even ctrl+r in my terminal cuz didn’t know what to search for.

1 Like

It’s called the wiki? Top bar in the forum! :wink: