# What is correct way to add new binary to be available in %pre section of kickstart

**URL:** <https://forums.rockylinux.org/t/what-is-correct-way-to-add-new-binary-to-be-available-in-pre-section-of-kickstart/10669>\
**Category:** Rocky Linux Help & Support\
**Created:** [July 12, 2023, 1:31pm UTC](https://forums.rockylinux.org/t/what-is-correct-way-to-add-new-binary-to-be-available-in-pre-section-of-kickstart/10669 "2023-07-12T13:31:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ccnav](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@ccnav](https://forums.rockylinux.org/u/ccnav)\
**Post date:** [July 12, 2023, 1:31pm UTC](https://forums.rockylinux.org/t/what-is-correct-way-to-add-new-binary-to-be-available-in-pre-section-of-kickstart/10669/1 "2023-07-12T13:31:45Z")

</div>

I want to make the common cli tool `bc` available in the %pre section of the kickstart. This tool has no dependencies beyond `glib` so will link/work nicely right out of the box if there was jsut a way of:

- open up isolinux/vmlinuz
- drop `bc` into `/usr/bin`
- seal up isolinux/vmlinuz

I can’t seem to find the correct way to approach this? I suppose the alternative way is to just open up the `bc*.rpm` from inside the `pre` section since i have access to the to-be-installed rpms and `cpio`? I could just extrapolate the file?

I was just hoping for a slick way to just have the tool present all the time.

Thoughts/Advice?