microsoft / microsoft/shell-intune-samples
invoking sudo sh not working
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 305
- PR merge metrics
- No merged PRs in 30d
Description
I had to change my process to sudo bash ./...
why is the script using #!/usr/bin/env bash versus #!/bin/bash.
Is one better than the other? If we are using tools like landscape to push this how would that work? All my other scripts start with #!/bin/bash. Is 26.04 requiring something different? Other scripts i use worked fine so just looking for clarification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the affected sample script's shebang and reproducing the reported sudo sh versus sudo bash ./... invocation in the Intune deployment context. Done would require a documented, project-specific explanation of the shebang choice and how the script should be invoked through tools such as Landscape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, shell
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100