Hello,
I need help with my two last pacnew files. Managed to deside about 23 others, but these two are to hard for me, even after searching for similar posts.
I never installed or removed shells, started with Manjaro KDE in 2018, so I dont know what to do with these two files, merge or delete the pacnew or replace the shells file with the pacnew version:
Then it’s the same with the vmtoolsd file, they look too different, the only thing I can think of is that I don’t seem to miss the settings in the pacnew file. I run this Manjaro installation in a VMware Player on Windows 11:
As for /etc/shells:
the .pacnew doesn’t have anything new in it - the shells in line 8 and 9 are already in the file on the left
so:
there is nothing to do
I have no idea about the second one since I don’t use that software.
Logically though, if you have not altered the original yourself, it was the default that got installed some time ago -
and now there is a new default.
Therefore I’d replace the original with the .pacnew
You can always create backups of the files so that you can go back, should you need to.
Whilst @Nachlese is correct, I would take the opportunity to tidy up the file and bring it in line with the pacnew. The order doesn’t matter, I just stuck with the pattern I saw in the pacnew.
# Pathnames of valid login shells.
# See shells(5) for details.
/bin/sh
/bin/zsh
/bin/bash
/bin/rbash
/usr/bin/sh
/usr/bin/zsh
/usr/bin/bash
/usr/bin/rbash
/usr/bin/git-shell
/usr/bin/systemd-home-fallback-shell
I don’t use open-vm-tools either.
However the syntax looks different so you should use the pacnew, and if necessary figure out how to re-apply any custom config.
The software will be expecting the pacnew version from now on. Sticking with the old version should work for a while, but it may eventually break.
As previously mentioned having a backup is a wise choice.
I think you only need that one if you use systemd-homed, which is not configured in either Arch proper or Manjaro. It doesn’t even have a man page, and I just tried it with the --help option to see whether it could offer some information, but it threw an error message.
That sounds reasonable, I replaced the file.
Besides that I saved some files and their pacnew versions before altering, the nice thing about a VM is that you can copy it. Takes two minutes.
Thanks for the replies, I now have a pacnew-free system