-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add nano, dhcp client, sshd start to bash history #1306
Conversation
Some handy command the help me getting (debug) things done, in the Rear recovery environment.
@ProBackup-nl No objections against it - so I approve/accept it |
Alignded the trailing comments to same column to keep the look as it was before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I found out how to do
simple changes directly in the
pull request so that I aligned the
comments to the same column
to keep the look.
@jsmeix
I though the convention here, is to make comments that fit within 80 characters. That is why I didn't left align them. Should the 80 character rule(r) comment be kept or removed? |
I think that comment is more a hint that a strict rule |
This pull request is somehow related to |
…3154) Create an empty usr/share/rear/skel/default/root/.vimrc to fix #3151 Furthermore in build/GNU/Linux/130_create_dotfiles.sh dynamically generate .bash_history entries depending on whether or not 'nano' and 'vi' are available, see #3151 (comment) and see #1306 regarding nano and #1298 when vi is not available.
…ear#3154) Create an empty usr/share/rear/skel/default/root/.vimrc to fix rear#3151 Furthermore in build/GNU/Linux/130_create_dotfiles.sh dynamically generate .bash_history entries depending on whether or not 'nano' and 'vi' are available, see rear#3151 (comment) and see rear#1306 regarding nano and rear#1298 when vi is not available.
…ear#3154) Create an empty usr/share/rear/skel/default/root/.vimrc to fix rear#3151 Furthermore in build/GNU/Linux/130_create_dotfiles.sh dynamically generate .bash_history entries depending on whether or not 'nano' and 'vi' are available, see rear#3151 (comment) and see rear#1306 regarding nano and rear#1298 when vi is not available.
Some handy command the help me getting (debug) things done, in the Rear recovery environment.