Automating a Linux setup with Bash

Let's customize a fresh install of Linux with a Bash script, and talk about how automating a Linux setup with Bash could be a great, and fast way to set up multiple systems

--Mind, the mental health charity--------------------------------
Mind
For better mental health

--INFO----------------------------------­------------------------------

#Bash
#Software
#Linux
#BashScripting
#LearnBash

[lightninguru]

I enjoyed this. I would like to see more bash scripting like this. It is scripts like this that help people find the rabbit hole.

[BrucesWorldofStuff]

Good stuff! I have tried several times and I just can't get a script to make my coffee... LOL
You do have some good ideas. This is a good series so keep them coming...
I have a few scripts running around that I have started but not finished as I get off to other things more shiny... :-(
Oh! I heard the poking about making respins... Remember don't and I mean, don't poke the bee's Nest unless you want stung... LMAO
Thanks for the video!
LLAP

[lqlarry]

Keep up the shell scripting, please. It gives us some good ideas.

[custardflux]

Nice job, will have to give it a go. What icon theme are you using?

[hadeseye]

I had such script when I was testing multiple ubuntu based distros years ago.
I've learn a neat trick:
echo -e "\n" | [commands you want to start automatically, like] apt upgrade -y

Passing \n this way is nothing else than passing enter. Which in our case will confirm upgrade by itself.

But now you made me think to write a new version that will have case statement:

echo="Choose: a) arch d) debian f) fedora s) suse x) cancel:"

This way I can have one script that will be applied on multiple distros.
Those are good to auto-remove unwanted software and replace it with thing you really use. Like these unwanted duo: Rhythmbox + Parole and replace it with Clementine + VLC.

[Kwales]

Great stuff. Is it possible to run a script via the GUI ?

[humicbeast]

Bash script love it good to be lazy and not do the same thing all the time

[custardflux]

in your previous bash video you put ./ before the script, but this time you just dropped it into the terminal and pressed enter - am i missing something?