Re:_16-CURRENT_non_root_users_unable_to_use_so und/beep_anymore_after_upgrade_to_a4ed783cee2a

On June 22, 2026 9:03:40 PM GMT+03:00, Bugs Beastie <bugsbeastie@gmail.com> wrote:
>Jun 22, 2026 19:48:04 Mark Millard <marklmi@yahoo.com>:
>
>> On 6/22/26 03:04, polyduekes@proton.me wrote:
...
>> I could imagine that, for now, it would be good if, at the very end of
>> its output, pkg upgrade or pkg install reported on how many *.pkgnew
>> files and/or *.pkgsave files had been had been generated, at least when
>> the number is positive. It would prompt to investigate.
>>
>+1 on the warning at the end of the pkg session!
>
>

one of the hardest things on upgrade is to having to investigate intermingled confing merge situations

it's much better if we have system and local user and group db and so on

system and local (open)ssh(d) config

and so on

it'a absolute nightmare to merge master.passwd

changes themselves are often fine and can be simply overridden from defaults (like swap sh back to csh)

but the sheer work of constantly merging files is horrible

right now i have etc overwriting overy i apply on top of stock etc on some systems, but now i have to merge the dist one into there

p.s.:
why was default csh swapped to sh without first porting all interactive goodies from csh to sh?
i mean i haven't joined church of csh or anything, it's just what was there in 4.6 and i kept using it, without knowing i should swap it out (like many said)