Re: 16-CURRENT non root users unable to use sound/beep anymore after upgrade to a4ed783cee2a

From: Alastair Hogge <agh_at_riseup.net>
Date: Mon, 22 Jun 2026 14:12:44 UTC
On 2026-06-22 21:08, Tomoaki AOKI wrote:
> On Mon, 22 Jun 2026 13:46:05 +0200
> Dag-Erling Smørgrav <des@FreeBSD.org> wrote:
> 
>> Tomoaki AOKI <junchoon@dec.sakura.ne.jp> writes:
>> > Please habitally confirm UPDATING. I believe it should be
>> > a good habit.
>> 
>> No, pkgbase users shouldn't need to read UPDATING.  We need to fix
>> config file merging.
>> 
>> DES
>> -- 
>> Dag-Erling Smørgrav - des@FreeBSD.org
> 
> Agreed. But the work may be hard and need time to implememt.
> 
> As far as keep on using diff3, which compares "line level",
> this doesn't seem to be fixable. Would need "field level"
> comparison and merge.
> 
> What I can imagine for now is:
>   Keeping database for "managed" /etc components that records
>   the file is a script (like rc.d/*) or database (like group,
>   master.passwd, ...). Maybe informations for data structures
>   including delimiters would be needed to be stored for this purpose.
> 
>   etcupdate to be modified to read the above-mentioned database
>   and merge scripts only, passing others to another program.
> 
>   The additional program treats files passed from etcupdate
>   as record and field based database, add, remove or modify
>   anything other than that local admins can modify.
> 
>   This means, the program needs to ignore user passwords,
>   configured shells for anything other than to-be-switched
>   on master.passwd (as in csh to sh transitions but the user
>   locally changed it to, say, zsh or something else),
>   and adding new group to group (this time, adding audio)
>   need ignoring configured users.
> 
> And anyway, IMHO, manual intervention cannot be avoided,
> as etcupdate or additional programs cannot know which user
> to be added to newly added group like audio, unless blindly
> adding all users there. Otherwise, things may be more complexed.

Or how about UCL for all of configuration data in /etc/, and host
specific configurations can go into a separate UCL? After a pkgbase
upgrade, databases can be rebuilt with the stock/system UCL and the host
specific UCL. Maintains a clean separation between the host and the
operating system then.