[GH-ISSUE #2923] include on the commandline #1825

Closed
opened 2026-05-05 08:29:40 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @rusty-snake on GitHub (Aug 22, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2923

for debuging it would be usefull to have the opportunity to use include on the command line.
Example:

firejail --noprofile --include=disable-programs --include=disable-common bash
firejail --profile=firefox --include=$HOME/temp-firefox.local
Originally created by @rusty-snake on GitHub (Aug 22, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2923 for debuging it would be usefull to have the opportunity to use `include` on the command line. Example: ``` firejail --noprofile --include=disable-programs --include=disable-common bash firejail --profile=firefox --include=$HOME/temp-firefox.local ```
gitea-mirror 2026-05-05 08:29:40 -06:00
Author
Owner

@smitsohu commented on GitHub (Aug 22, 2019):

I think you can use multiple --profile options, like

firejail --profile=firefox --profile=$HOME/temp-firefox.local

I couldn't find this documented though.

<!-- gh-comment-id:523999499 --> @smitsohu commented on GitHub (Aug 22, 2019): I think you can use multiple `--profile` options, like `firejail --profile=firefox --profile=$HOME/temp-firefox.local` I couldn't find this documented though.
Author
Owner

@rusty-snake commented on GitHub (Aug 22, 2019):

Except of that I need absolut paths for *.inc it works, don't no why my last try with multible --profile has failed 😕 .

Should we close?

<!-- gh-comment-id:524004519 --> @rusty-snake commented on GitHub (Aug 22, 2019): Except of that I need absolut paths for *.inc it works, don't no why my last try with multible `--profile` has failed :confused: . Should we close?
Author
Owner

@smitsohu commented on GitHub (Aug 25, 2019):

Intuitively most people probably first try --include on the command line. I recall myself trying this as well....

Parsing --include as --profile would be a trivial change. Maybe we could try to harmonize their behavior, if this is wanted. Are there any reasons why they should behave differently with regards to profile extensions?

<!-- gh-comment-id:524620368 --> @smitsohu commented on GitHub (Aug 25, 2019): Intuitively most people probably first try `--include` on the command line. I recall myself trying this as well.... Parsing `--include` as `--profile` would be a trivial change. Maybe we could try to harmonize their behavior, if this is wanted. Are there any reasons why they should behave differently with regards to profile extensions?
Author
Owner

@rusty-snake commented on GitHub (Aug 25, 2019):

Consider this:
Now: firejail --profile=2048-qt --profile=/etc/firejail/disable-xdg.inc 2048-qt
With --include: firejail --include=disable-xdg.inc 2048-qt

<!-- gh-comment-id:524621631 --> @rusty-snake commented on GitHub (Aug 25, 2019): Consider this: Now: `firejail --profile=2048-qt --profile=/etc/firejail/disable-xdg.inc 2048-qt` With `--include`: `firejail --include=disable-xdg.inc 2048-qt`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1825
No description provided.