bash-me-up (Bash Startup Files Setup Made Easy)

[PackRat]

Working for my Void system - which also symlinks sh to dash

When I su to root I get the following errors:

Code Select Expand

-bash: pathprepend: command not found
-bash: pathprepend: command not found
-bash: pathprepend: command not found
-bash: pathappend: command not found
-bash: pathappend: command not found

but everything appears to be working.

[VastOne]

I did not try the new version but I am getting that same exact error when I log into any tty

tty1 shows that error and just shoots back to login:

tty2-6 let me log in

[hakerdefo]

@PackRat @VastOne
Anyone who installed V1 will have to remove the following two files manually before (preferable) or after installing V2,

Code Select Expand

sudo rm /etc/profile.d/extrapaths.sh

Code Select Expand

rm .xsession

Also remove any symbolic links in /root linking to .profile, .bash_profile, .bashrc, .bash_aliases, .bash_logout, .LESS_TERMCAP to your $HOME directory and those errors should be resolved.

If you never installed V1 then there is no need to do above.

Please test V2 on a clean system and give your feedback.

[hakerdefo]

Tested V2 of bash-me-up on a fresh install of 64-bit VSIDO, and guess what?
It works like a charm
No errors or problems on logging-in either via tty or LightDM
Also tested it on a live session of VSIDO, and it works as expected in live session too
So if you are still hesitant, boot live USB or CD of VSIDO and install bash-me-up and take it for a test drive

Cheers!!!

[PackRat]

That worked, and it works on a clean bash environment.

You need a README file in the tarball so a user can see what changes will be made prior to running the script.

This script is good for a clean, base install, but I can see where there will a rapid point of diminishing return - particularly since the $PATH is getting altered. Some applications (perl and python based come to mind) add custom PATH arguments to the bash environment, those would be lost when this script is run. Although VSIDO is based on Sid and your average Sid user will most likely figure it out, there are a lot of less experienced users these days installing Sid, Void, Arch etc ... becuase they want a rolling release they can tweak. Could lead to some frustration for them.

[VastOne]

Worked for me as well and I agree completely with PackRat.. One thing that gets altered is aliases and for me I depend heavily on the aliases I use

Getting old sucks especially trying to remember vague commands   

[hakerdefo]

python and perl modules don't add path to BASH environment. Python and Perl both have their own ways of sourcing their standard PATH.
Your custom bash aliases set in .bash_aliases will be available. I tested and all VSIDO bash aliases were available and usable, like 'q' for exit. Are you sure they are not working?
Cheers!!!

[VastOne]

I have not tested V2 yet.. I will a bit later today and let you know

[hakerdefo]

VastOne, please test V2. Your feedback is very important.

[VastOne]

Tested V2 on a brand new install of VSIDO and all seems perfect..

Will keep on testing... well done hakerdefo!

[PackRat]

Tested on a clean install of debian testing (upgraded to Sid).

Worked as advertised.

Some bash aliases that I find convenient for systemd.

[hakerdefo]

'staton' and 'statoff'  are essential if you are a tinkerer. Thanks for sharing them PackRat!