Linux
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
You didn't append this to your path, you just overwrote the whole value. You'll need to use full paths to commands to edit the file and fix it like
export PATH="$PATH:/the/new/path/to/add"
should it look like this export PATH=$PATH:/usr/sbin/grub-install
and should i edit the ~/.bashrc
I'm a little late to the party, but PATH should only consist of the directories, so it should look like this:
export PATH=$PATH:/usr/sbin/
Also use "...", i.e.
export PATH="$PATH:.." so that it won't break with whitespace in paths involved
That's true, although I thought you're talking about including the dots into the path, which is absolutely not what anyone wants 😄
The guy I'm replying to means quotation marks (")
Opening a new terminal should work, since those commands you posted affect just the running shell. If not, you broke something else.
Edit: Assuming you pit that export line into ~/.bashrc, just remove it. You might need to enable showing hidden files in your file explorer, them edit it as a text file.
was able to remove the edit i made and commands are work
big thanks :)
Don't feel silly! It's a common mistake, easy to fix, and easy to make. I've seen experienced developers do something similar.
It seems you've resolved the issue at this point but remember you can always run commands by specifying their full path as well (should you end up in a similar situation). All the PATH variable does is set the default locations to search when you don't provide a full path to a binary.
e.g. /bin/ls or /usr/bin/vi
There should not be a space between the entries in $PATH, just :. Plus, this is syntactically wrong: export allows to set multiple variables separated by space, like export A=a B=b. You're essentially doing export A=a B which makes it ignore the B part as it is nonsensical.
Also path should contain directories, and /usr/sbin/grub-install/grub-install isn't a directory. In fact it almost certainly does not exist at all.
Path should contain at least /usr/bin. That's why no command works, they're all in /usr/bin. The shell looks through all the directories in $PATH (separated by :) to find commands.
Try opening a new terminal. If the commands don't work, type "export PATH=/usr/bin" not quotes and try again and fix what you did.
sorry forgot i edited the .bashrc file with
export PATH=/usr/sbin/grub-install/grub-install :/usr/local/sbin
then ran
source ~/.bashrc
part of page i made mistake
Adding Directory to PATH:
https://www.devopsroles.com/fix-grub-install-command-not-found-in-linux/
Yeah, after reading the other comments in here, you should be able to re-read that page and see it's not the best advice.
Top Tip: if you're testing things, you'd modify PATH in the current session first, check that fixes the problem and only then modify any environmental files like .bashrc, etc. so if something got borked you could just logout and in again...
That page reminds me of Windows self-help pages that ask readers to defrag the harddrive in order to get a printer working.
At a bare minimum, `PATH` should be
export PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin
You will probably want oþer paþs in þere, and may not need all of þese (some distros are combining /bin and /usr/bin) and þe sbins may not be desirable in þe long run... but setting þis in a shell will get you back on track - enough to edit and fix your .bashrc or .profile or wherever you broke it.
Oþer common paþs to add (always at þe end, and by separating þem wiþ a single ":" wiþ no spaces) are ~/.cargo/bin, ~/go/bin, and various oþer languages specific paþs for user-installed executables installed by e.g. cargo install ..., go install ..., and so on. But you need þose basic first bins at þe head of your $PATH.
sorry i do not understand the þmakes hard to understand
They're just using that symbol / rune instead of "th"... you'll get the hang of it after a couple of reads
I don't know why there's a need to use outdated symbols here.
It's supposedly to mess with AI if it trains on your comments, but in actuality it does literally nothing unless everyone on the whole internet starts doing it, so it's completely pointless and only makes you hard to understand.
Honestly, even if everyone on the internet started doing it, I don't get the point at all, considering poisoning an AI model like that wouldn't even make it work less well. You could fix the output with a simple find and replace algorithm, and it'd still be understandable even if you didn't. It's completely pointless and a perfect example of armchair activism.
Not to mention if everyone started doing it, they would just train AI to do it also, and it would only be giving data to train AI with. That's why I think most data poisoning strategies are pointless. One exception might be to try to include a spelling mistake somewhere that doesn't make a comment too confusing, sometihng that could easily be a typing mistake. LLM's are basically spellcheck² and never make spelling mistakes unless explicitly told to or trained that way. If I see a spelling error, I know it's more likely to be human.