[Bug 260628] FreeBSD 12.3-Release got stuck during the boot process after the update (maybe nsswitch issue?)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260628

--- Comment #9 from Dylan <djimeha@yahoo.ca> ---
Apologies, the '2nd' thing was that 12.4-RELEASE-p1 and bash-5.2.15 don't seem
to agree.  Bash dies with this, which is, at a glance, something that showed up
in bash 4-ish, but FreeBSD 10.4-p3 had bash 4.4.23 and worked:

    $ uname -a
    FreeBSD <hostname here> 12.4-RELEASE-p1 FreeBSD 12.4-RELEASE-p1 GENERIC 
amd64

    $ pkg info | grep bash
    bash-5.2.15                    GNU Project's Bourne Again SHell

    $ /usr/local/bin/bash
    ld-elf.so.1: Undefined symbol "rl_sort_completion_matches" referenced from
COPY relocation in /usr/local/bin/bash

Was added here:
https://github.com/akamai/bash/blob/no-function-forward/CHANGES#L2249


Why is this error relevant here?  Switching to 'bash-static' works, but doesn't
play nice with nss_ldap, so prompts for remote (Pulled from LDAP) users result
in:

    [I have no name!@<your server name> <Current path>]$

A 'whoami' shows them correctly mapped, so I just switched the default shell to
/bin/sh for now until I can find a fixed version of bash.

Example I found of someone else noting bash-static didn't work with LDAP
mapping:
https://lists.freebsd.org/pipermail/freebsd-stable/2014-March/077852.html

So, not relevant if your LDAP client doesn't use bash for root or users, but
heads up if they do that it may not play nice with 12.4-p1.

-- 
You are receiving this mail because:
You are the assignee for the bug.