From 1ce0e2ad424bf38768094488774eff23b3871ccc Mon Sep 17 00:00:00 2001 From: Tom Ryder Date: Sat, 20 Aug 2016 00:43:35 +1200 Subject: Port all bash_profile.d scripts to POSIX sh Also require flag files in ~/.welcome for displaying or not displaying login stuff --- README.markdown | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'README.markdown') diff --git a/README.markdown b/README.markdown index 47197122..d6ace0d3 100644 --- a/README.markdown +++ b/README.markdown @@ -98,11 +98,10 @@ they should work in most `sh(1)` implementations. Individual scripts called by management. All of these boil down to exporting variables appropriate to the system and the software it has available. -My `.bash_profile` calls `.profile` and then runs subscripts in -`.bash_profile.d`. It then runs `.bashrc`, which only applies for interactive -shells; subscripts for that in turn are loaded from `.bashrc.d`. The contents -of the two directories changes depending on the host, so only specific scripts -in it are versioned. +My `.bash_profile` calls `.profile`, and then `.bashrc`, which only applies for +interactive shells. Subscripts for `.bashrc` are loaded from `.bashrc.d`. The +contents of the two directories changes depending on the host, so only specific +scripts in it are versioned. My interactive and scripting shell of choice is Bash; as a GNU/Linux admin who ends up installing Bash on \*BSD machines anyway, I very rarely have to write -- cgit v1.2.3