I don’t know bash scripting
if [ -d ~/.bashrc.d ]; then
for rc in ~/.bashrc.d/*; do
if [ -f "$rc" ]; then
. "$rc"
fi
done
I asked chatgpt and it said this is non standard? There is no bashrc.d directory on my home folder, I have uncommented the lines for now but dont know if this is benign or malignant
It sources (includes) any file found in ~/.bashrc.d/ so check that directory.
but there is no such directory
Then it does nothing.
Then it should have no effect.
This is just a nice way to define file-discrete .rc scripts. Like, maybe you have one for shell stuff, one for your custom collection of command aliases, one for initializing pyenv+pyenv-virtualenv, etc. That way, you have domain-constrained .rcs, and it’s easier to scan through things to see if something funny is going on / is broken or whatever.
It just checks to see if there is anything in a bash.d folder, if there isn’t it moves on. Just somebody being preemptively helpful to check for other locations
Check
/etc/skel/.bashrc, if it’s in there as well, it was set up by your distro.What it does is check for the existence of
~/.bashrc.dand, if it finds one, sources all the files inside it. This effectively means that you can create script files like~/.bashrc.d/myfile.shand they will have the same effect as if they had been put directly into.bashrc. Some people prefer having one file for each “bashrc thing” whilst some prefer just having one big file. Ultimately it’s personal preference.Ugh, I hate ChatGPT. If this is Bash (which it is, because it’s literally looking for files in a directory called
~/.bashrc.d), then it should god damned well be using syntax and language features that we’ve had for at least twenty fucking years. Specifically, if you’re writing for Bash (and not POSIX shell), you better be using[[ ]]rather than[ ]. This wiki is my holy book I use to keep the demons away when writing Bash, and it does a simply fantastic job of explaining why you should use God damned double square brackets.ChatGPT writes shitty, horrible, buggy ass Bash. This is relatively decent for ChatGPT (it even makes sure the files are real files and not symlinks), but I’ve had to fix enough terrible fucking shitty AI Bash to have no tolerance for even the smallest misstep from it.
Sincerely, A senior developer who is known as the Bash wizard at work.
EDIT: Sorry, OP. ChatGPT did not, in fact, write this code, and I am going to leave my comment here as a testament to what a big smelly dick I was here.
I think you misread both the question and how they used ChatGPT Mr Bash Wizard
oh fuck I did misread it. Man, now I sound like a big ol’ asshole. Sorry, OP :/ I had a bad week thanks to some ChatGPT code and just kinda jumped out when I saw the word “ChatGPT” next to Bash.
Hey man you’re human! Mistakes! Everyone makes them! At least you admit it, right :D
Looks like this is in the standard Fedora
/etc/skel/.bashrc.It first checks if
~/.bashrc.dis an existing directory. If this it the case it then iterates over all entries in that directory. In this iteration it checks if the entry is a file and if this is the case it sources that file using the bash-internal shorthand.forsource.So it basically executes all scripts in
~/.bashrc.d. This makes it possible for you to split your bash configuration into multiple files. This quite common and a lot of programs already support it (100% depends on the program, though).This is absolutely harmless as it is. But: if you or a program places anything in the directory
~/.bashrc.dit WILL be sourced everytime you start a bash.A slightly better variant would be iterating over
~/.bashrc.d/*.shinstead of just~/.bashrc.d/*to make sure to only grab files with the.shsuffix (even if suffixes are basically meaningless from a technical point of view) and also test for the file being executable (-xinstead of-f).This would make sure that only files that are ending with
.shand that are executable are sourced. The “attack vector”, if you want to call it like that, would then be a bit more narrow than just placing a file in a directory.As for why it’s there: Did you ever touch your
.bashrc? If not, maybe it is there since the beginning because it’s in the so-called skeleton (see/etc/skel/.bashrc) that was used to initialize certain files on user account creation.Damn, now I want this too!
As others have said, all it does is pull in any other config files in that may be in that folder. And storing them separately like that is much better for backup and portability.
Ubuntu doesn’t do this.
Definitely non-standard, but I have something almost identical that I very consciously added and really simplifies a lot of things.
Share it
Let me hazard a guess:
if [ -d ~/.mybashconfig.d ]; then for rc in ~/.mybashconfig.d/*; do if [ -f "$rc" ]; then . "$rc" fi done
I couldn’t say how it got there, but it’s a standard & common Unix pattern and unlikely to be malicious. It will have no effect if the
~/.bashrc.ddirectory doesn’t exist. If it does exist, then each file in the directory will be sourced.i don’t know much bash, so anyone else who responds is probably more right, but since no one has responded, here’s my 2 cents: it appears to be a script to run all scripts in .bashrc.d. That would be similar to how some apps will let you separate a configuration file into multiple files in a directory conf.d. If there is no .bashrc.d, then it should be fine.
seems similar to the set up for systemd snippets, where you can avoid changing default config files for systemd units and instead use a drop in file in that created .d dir to load and overwrite the defaults on boot for whatever specific thing. don’t know anything that uses this for bashrc, tho. most likely harmless, especially if there’s no created bashrc.d yet.
