Hi,

I am writing few small BASH scripts thus developing a small console based application. I would appreciate if someone can help me on my below queries on customising CentOS 7

1. I need to customise the centos, boot screen, splash screen etc.
2. Especially images which appear at installtion times. How do I do that?
3. I need to store my .tgz file on the ISO and once the installation complete running install.sh bash script will install my application.

TIA

1 you need to look for a solution on the net, you will find it in 5 minutes. If you have any question regarding a solution please post.
2. the same
3. you ought to create an rpm. I do not suggest you to add it to an iso, but create a new package repo which can be configured and used to install that rpm. But obviously you can put this repo onto the CD too.

1 members found this post helpful.

Aside from the good advice pan64 gave you, the question I have is *WHY* you want to create your own 'customized CentOS'?? Why would I want your particular spin/distro of CentOS over the stock? What additional VALUE am I, the end user, going to get from downloading whatever it is you offer???

Because if it's just a few bash scripts, I'm not likely going to download 4GB+ to get them. Put them in an RPM file suitable for installation..bash scripts aren't limited to CentOS.

Well I wanted to give a complete customized look and feel hence looking for a change. However I did googled a lot for changing Snapshots but did not get a appropriate answer hence wondering if community can help or may be any link that you guys can aware of?

I'd think that search terms that include splash screen along with fedora, centos, red hat would provide answers for that. Usually it's an image that is called and many people have set it. The newer distro's have changed how video goes from boot to session so you may have to look at how you wish to boot. https://askubuntu.com/questions/7169...rs-mean/716966

However I get the feeling you wish to see some menu and that too may be an option. Or do you want some slide show?

Various distro's can handle how custom boot scripts are handled. At some point in some process you could run your script but this kind of goes back to maybe a menu choice if desired.

Again:

• What benefit is a 'complete customized look and feel', when all you've written are some bash scripts??
• Why would anyone download a respun version of CentOS, for nothing but some bash scripts?
• Why wouldn't you package your scripts/application as an RPM, so it can be installed in many other distros?

If you're having problems with packaging bash scripts in an RPM, auto-running at script at first boot, or changing a splash screen, are you sure you want to undertake the enormous task of repacking an entire distro??

Again, I find it **HIGHLY UNLIKELY** that anyone, anywhere, is going to download a 4+GB distro, just to get your bash script application. It's just not worth it. If you want anyone to use your app, package it. I sure wouldn't want to go through the hassle of installing/re-installing an entire distro just to get a SINGLE APP.

blason,

Believe it or not, many large vendors customize the install and boot process for their proprietary enterprise linux deployments.... For example, lets say there's a well known network software / hardware company that provides a hardware load balancing appliance. Their software is Java, but runs on CentOS or Red Hat. They don't wish to reveal those distro's from a graphical perspective so will modify the installation media... the below links can guide you in getting started with Anaconda and the boot menu for custom deployments

https://access.redhat.com/documentat...-customization
And for the branding to get started
https://access.redhat.com/documentat...aconda-visuals
Anaconda is a beast and can do a wild amount of things
https://access.redhat.com/documentat...on_guide/index


As for tar'ing and running your package post install, take a look at including a kickstart file in your custom install, you use the options for %post in the kickstart to essentially run those bash scripts. Alternatively, and my preference is if you know the server will have network access, then in your custom iso include keys so you get pull down your software from source control. This will add the benefits of tracking your code, but also lightening the size of the iso you'll be creating

1 members found this post helpful.