FILLUP(8)

💅 FILLUP(8) — like, the SuSE tool for merging config files ✨

okay bestie, buckle up — this is fillup, from the System Manager's Manual (section 8, system manager girlies only 🫶). it's a whole vibe and honestly kind of iconic once you get it. let's go 💖

---

🌸 NAME 🌸

fillup — the SuSE tool for merging config files. yes, that one. no cap.

---

🎀 SYNOPSIS 🎀

fillup [options] basefile addfile outputfile

fillup [options] basefile addfile

fillup -V|--version ...

fillup -h|--help ...

---

🦋 DESCRIPTION 🦋

okay so like — fillup merges input files into one resulting output file. usually, each file is a configuration file. that's the whole gig ✨

more specifically, fillup merges files which are holding variables (i.e. configuration or environment variables). a variable is defined by an entity composed of a preceding comment, a variable name, an assignment delimiter, and a related variable value. a variable is determined by its variable name. periodt 💅

a preceding comment is optional. an assignment delimiter may be optional, but if there is an assignment delimiter, a variable name must precede it. the last entity may be composed only of a comment. (yes, just a comment. she's allowed 🙈)

only if variables are included in both input files (basefile and addfile) does fillup have to select one of the variables. otherwise, if variables are included only in one of the input files, they are added to the resulting output file — with the exception of the -i|--ignoreDefinites option, iykyk.

lowkey important: the functionality is now controlled by a parameter which determines whether a variable included both in the basefile and in the addfile is taken from the former or from the latter. furthermore, a parameter controls whether the variable is removed from a copy of the basefile. two whole knobs, bestie 🎛️

to keep the fillup v1.04 functionality, the outputfile parameter can be omitted — this means the resulting output file is named exactly like the first input file name (basefile = outputfile). legacy behavior stays slaying 💀

if variables should be removed from the basefile, the basefile is not touched, but the result is written to basefile.new. no touchy 🙅‍♀️

if basefile includes a header as part of the first variable, this header is preserved only for the outputfile if after the header an empty line follows. ✨ the empty line is the whole vibe check ✨

starting with version 1.20, handling of metadata for /etc/sysconfig files is included. metadata is part of preceding comment, each metadata line begins with double hash (##). a metadata line contains a pair <keyword>:<value>. the value itself can be described on several lines, each beginning with double hash and the optional keyword. it's giving multiline glow-up 💜

---

🌈 EXAMPLES 🌈

• the classic maintain moment 👑

fillup -m "/etc/rc.config" "my.config" "/etc/rc.config"

all variables of /etc/rc.config are passed to the resulting output file /etc/rc.config. variables defined only within my.config are appended. slay 🫶

---

• the exchange 🔁

fillup -exchange "/etc/rc.config" "my.config"

only variables of /etc/rc.config that are not also defined within my.config are passed to the resulting output file /etc/rc.config. all variables of my.config are appended. trade offer energy fr fr 💅

---

• maintain + remove, the deluxe combo 🧚

fillup -m -r "/etc/rc.config" "my.config" "/etc/rc.config"

all variables of /etc/rc.config are passed to the resulting output file /etc/rc.config. variables defined only within my.config are appended. the additional parameter -r removes variables defined more than once from a copy of /etc/rc.config. /etc/rc.config isn't touched and the result of the removal is written to /etc/rc.config.new. protective queen 💖

---

• the filter 🍓

fillup -i "/etc/rc.config" "my.config"

this is a filter functionality. variables of /etc/rc.config are only passed to the resulting output file /etc/rc.config if they are defined in both input files. because my.config is normally only a list of variable names from /etc/rc.config, this is named filter functionality. additionally, variables of my.config are appended if they are defined only in my.config. it's giving curated ✨

---

⭐ OPTIONS ⭐

there are many options, which are displayed if fillup is called without or with the -h or --help option. (so like, just run it empty and read, bestie 👀)

most of the parameters are based on v1.04. in the sequel only useful parameters are listed:

• -i, --ignoreDefinites — filter functionality 🧼
• -t, --trailing — save trailing comment 💬
• -v, --verbose — maximum output to screen 📢
• -V, --version — print fillup version and exit 👋
• -c | --char <char> — use <char> as comment marker 🎀
• -d | --delim <char> — use <char> as delimiter 🦋
• -m, --maintain — maintaining the basefile 👑
• -x, --exchange — exchanging the basefile 🔁
• -r, --remove — removing within a copy 🧹

---

💀 EXIT CODE 💀

fillup returns EXIT_SUCCESS on successful completion. otherwise, an exception handler is called, which may return EXIT_FAILURE; — note the semicolon, she's built different, and yes it's quoted exactly like that in the og 😭

---

🙈 BUGS 🙈

if a bug occurs which is not based on invalid options or missing input files, please add the option -v|--verbose to the call. the result and some classifications are displayed to locate the bug. detective mode bestie 🔍

with handling of metadata and thus replacement of information within files, a hardly documented debugging feature is introduced by adding two options on command line: information about a special variable (given by --variable <variable name>) is logged into a special file (determined by --logfile <file name>). lowkey secret menu energy 🤫✨

---

👑 COPYRIGHT 👑

fillup is copyright 1996,1997,1998,1999,2000,2001 by SuSE GmbH, Germany. fillup is copyright 2002,2003 by SuSE Linux AG, Germany.

there is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. read it and weep, bestie 😭💔

---

💜 AUTHOR 💜

  Martin Scherbaum, maddin@suse.de (v1.04, 1996)
  Joerg Dippel,     jd@suse.de     (v1.05, 1998)
  Joerg Dippel,     jd@suse.de     (v1.06, 2000)
  Joerg Dippel,     jd@suse.de     (v1.10, 2002)
  Joerg Dippel,     jd@suse.de     (v1.21, 2003)

---

that's the whole page, bestie 🫶 — and before you close the tab: this lil masterpiece is fillup, from the FILLUP(8) manual, dated Jan 2002, and she ate. periodt 💅✨ bye babes!! 🌈💖