Changeset f53dc4c for README.BLFS
- Timestamp:
- 04/09/2012 10:17:30 AM (12 years ago)
- Branches:
- ablfs
- Children:
- d721466
- Parents:
- d6f2ebf
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README.BLFS
rd6f2ebf rf53dc4c 274 274 commands that require root privileges are run using sudo. Also make sure 275 275 necessary root privilege commands are visible in your PATH. Or use 276 the `Defaults secure_path=' in /etc/sudoers. Also, the scripts use a 277 fragile construct: 278 sudo bash -c '<commands to be executed as root>' 279 which fail if the commands to be executed contain themselves a ' or access 280 a bash variable $XXX. So carefully review them. When you want to use 281 environment variables, it is sometimes better to replace simple quotes 282 with double quotes, but beware the construct is even more fragile. 283 Carefully check it... 276 the `Defaults secure_path=' in /etc/sudoers. 277 For commands necessitating root privileges, the generated scripts wrap 278 them with the construct: 279 sudo -E sh << ROOT_EOF 280 <commands to be executed as root with `$', ``', and `\' escaped> 281 ROOT_EOF 282 The -E switch ensures the whole environment is passed to the 283 commands to be run with root privileges. It is effective only if the 284 /etc/sudoers file contains `Defaults setenv', or SETENV in the user 285 attributes. If you think it is a security issue, you may forbid this 286 flag in /etc/sudoers, but then, you have to un-escape `$' for variables 287 coming from the environment in the instructions. 288 Although this construct is rather strong, it can fail in some corner 289 cases, so carefully review those instructions. 284 290 285 291 Due to book layout issues, some sudo commands may be missing.
Note:
See TracChangeset
for help on using the changeset viewer.