My original unRAID build just came back to me from a friend so I decided to use it to backup some "uncritical" shares that I hadn't bothered to backup before. So now I have 2 servers. I am looking for ideas on differentiating the interfaces of these servers. I have come up with 3 simple things and 2 of them work fine but I'm having a little trouble getting the 3rd one to stick.

 

1) Different banners and dynamix color schemes. My main server is set white and my backup server is set black.

 

2) Different putty color schemes. Black on white for main and white on black for backup.

 

3) Different Midnight Commander color schemes. This is where I am having a little trouble. If you run

mc -b

you get a monochrome version of mc so I thought I would do this on my backup server. I didn't want to have to remember to type it that way all the time so I

alias mc="mc -b"

In order to make this stick between logins and reboots I tried

echo 'alias mc="mc -b"' >>/root/.bashrc

and if that survived a logout then I would put it in go, but it doesn't seem to work.

 

I could probably spend a lot of time googling but bash isn't my native tongue and I am sure there are others here who can do this simple thing in their sleep so I thought I would ask.

 

What can I do to make 3) stick?

 

Also, any other ideas for differentiating between server interfaces?

why not add the alias to your go script

why not add the alias to your go script

 

In order to make this stick between logins and reboots I tried

Code: [select]

echo 'alias mc="mc -b"' >>/root/.bashrc

and if that survived a logout then I would put it in go, but it doesn't seem to work.

 

I think trurl thought of that...

why not add the alias to your go script

 

In order to make this stick between logins and reboots I tried

Code: [select]

echo 'alias mc="mc -b"' >>/root/.bashrc

and if that survived a logout then I would put it in go, but it doesn't seem to work.

 

I think trurl thought of that...

OK. I got it. Do this instead

echo 'alias mc="mc -b"' >>/root/.bash_profile

 

So, now that I've started this thread, anybody else doing anything to make them think twice before doing something on the wrong server?

Different passwords, that would definitely you stop and think..

 

 

why not add the alias to your go script

 

In order to make this stick between logins and reboots I tried

Code: [select]

echo 'alias mc="mc -b"' >>/root/.bashrc

and if that survived a logout then I would put it in go, but it doesn't seem to work.

 

I think trurl thought of that...

maybe I'm out to lunch here, but isn't everything in /root lost upon a reboot?

 

here's an option

 

Create a file on your flash drive called mc

 

#!/bin/bash
/usr/share/mc/bin/mc-wrapper1.sh -b

 

Add to your go file:

 

mv /usr/share/mc/bin/mc-wrapper.sh /usr/share/mc/bin/mc-wrapper1.sh
cp /boot/mc /usr/share/mc/bin/mc-wrapper.sh
chmod +x /usr/share/mc/bin/mc-wrapper.sh

 

 

why not add the alias to your go script

 

In order to make this stick between logins and reboots I tried

Code: [select]

echo 'alias mc="mc -b"' >>/root/.bashrc

and if that survived a logout then I would put it in go, but it doesn't seem to work.

 

I think trurl thought of that...

maybe I'm out to lunch here, but isn't everything in /root lost upon a reboot?

 

here's an option

 

Create a file on your flash drive called mc

 

#!/bin/bash
/usr/share/mc/bin/mc-wrapper1.sh -b

 

Add to your go file:

 

mv /usr/share/mc/bin/mc-wrapper.sh /usr/share/mc/bin/mc-wrapper1.sh
cp /boot/mc /usr/share/mc/bin/mc-wrapper.sh
chmod +x /usr/share/mc/bin/mc-wrapper.sh

Yes I already got the part about adding it to go to make it survive reboot. The part I was having trouble with was making it actually do anything when you login. I just put

echo 'alias mc="mc -b"' >>/root/.bash_profile

in go and it works.

Different passwords, that would definitely you stop and think..

Would make me think long enough to login I suppose. Then I would forget all about it. I need a lot more than that with these old brain cells.