Hi, can someone point me in the right direction to add some bash aliases that will persist after reboots as well as change the existing ones there? I must be missing something obvious.

 

Thanks

Josh

Edited July 19, 20178 yr by JoshFink

Whatever action you take to set them up and make the changes needs to be put in a script and run at boot time, typically in the go file.

Thanks.. Looking into the go file though it seems pretty sparse. 3 lines maybe. 

 

Are there any examples? I'm assuming the go file doesn't translate 1:1 to the profile.

 

Thanks

I think we are on different thought paths.

 

I assumed you knew what to do to get the bash stuff to your liking, and were asking why it wasn't persisting after a reboot.

 

Whatever commands you typed at the command line to adjust your environment will need to be redone on every boot, since unraid is reinstalled to RAM every time. The go file is a convenient place to put commands that need to be done at boot time.

Hey...Thanks for the reply. 

 

Maybe I'm just being thick or missing something obvious. 

 

Let me start over. I know how to adjust the bash profile, set up the terminal, add aliases, etc. That's not the problem. However, like you said, it needs to be redone at boot because the files get recreated every time. 

 

Are you saying that I can put the alias and PS1 settings directly in the go file and then when I log in it will be available? if so, fantastic, but how would I go about setting up different aliases for different users? I could see it getting set up as root, possibly, but other users would seem a stretch.

 

Like I said, I know, just from typing this out that I'm missing something obvious. I'll keep looking around but I appreciate the help. 

It would be better to put all the commands in a text file so you only make one entry in the go file, a call to execute your text script that contains all the commands needed to set things up.

 

Keep in mind that unraid only has root as a linux user, all the "users" that are created in the GUI for security are only for SMB access. Creating new linux users may have unintended effects, and the first thing that anyone is going to ask you to do to help troubleshoot something is for you to undo all the stuff you are trying to do.

 

You are trying to bend unraid in a way that is not intended by limetech. You will be pretty much on your own if you bend it too far and it breaks.

1 minute ago, jonathanm said:

It would be better to put all the commands in a text file so you only make one entry in the go file, a call to execute your text script that contains all the commands needed to set things up.

 

Keep in mind that unraid only has root as a linux user, all the "users" that are created in the GUI for security are only for SMB access. Creating new linux users may have unintended effects, and the first thing that anyone is going to ask you to do to help troubleshoot something is for you to undo all the stuff you are trying to do.

 

You are trying to bend unraid in a way that is not intended by limetech. You will be pretty much on your own if you bend it too far and it breaks.

 

Thanks for the help. I'll keep that in mind about the root user. In all honesty, that's probably all I need to use anyways. Just habit of not logging in as root unless absolutely needed. 

1 minute ago, JoshFink said:

Just habit of not logging in as root unless absolutely needed. 

This is limetech's end goal. No command line access needed to run unraid. They consider any need to drop to the command line a failure on their part to some extent, except for like you said, absolutely needed, for advanced troubleshooting and recovery.