this post was submitted on 18 Mar 2026
8 points (100.0% liked)
Linux
63857 readers
930 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 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’m not familiar with the -p flag on Firefox but in general, adding
&to the end of your command backgrounds it anddisowndetaches it from your shell so it doesn’t close.firefox -p &; disownshould do what you’re looking for, if I’m understanding you rightYou don't need disown if you're closing the terminal. Just
I swear I have done these kindsof things without having an option that was a word. maybe just & im not sure. I just recall doing it and never recall using disown.
~$ firefox -p &; disown bash: syntax error near unexpected token `;'
just omit the
;firefox -p & disownLooks like I’ve gotten too spoiled with zsh, I guess that doesn’t work with bash. Doing it in two separate commands should work tho, ie
firefox -p &and thendisown~~it should be enough to put a space between
∧like this:firefox -p & ; disownbut I'm not 100% sure.~~I'm also very spoiled by zsh, and I also remember encountering this issue.
I actually started up bash to test this when op first responded, and the space had the same problem
Thanks for the correction.
I read the bash documentation and I think you simply don't need the
;. The & is already a command separator, just like ;Tested with bash:
sleep 100 & echo testprints right away.https://www.gnu.org/software/bash/manual/bash.html#Lists