Re: some information for shadow 4.20.

On 8/13/26 4:04 PM, Bruce Dubbs ([email protected] via blfs-dev 
Mailing List) wrote:
> On 8/13/26 2:43 PM, Pierre Labastie ([email protected] via 
> blfs-dev Mailing List) wrote:
>> On Thu, 2026-08-13 at 13:00 +0800, Zhang Wen wrote:
>>> Bruce Dubbs <[email protected]> 于2026年8月13日周四
>>> 12:40写道：
>>>> When I am setting up a new build, the very first package I build in
>>>> chroot is sudo as
>>>> the root user.  I then do 'sudo su - <userid>'. Does that show the
>>>> same problem for you?
>>>>
>>>>     -- Bruce
>>>>
>>>> -- 
>>>> http://lists.linuxfromscratch.org/sympa/info/blfs-dev
>>>> Unsubscribe: See the above information page
>>> Yes,  'sudo su -  <userid>' does show the same problem.
>>>
>>
>> Have you tried to set /proc/sys/dev/tty/legacy_tiocsti to 0, as said in
>> one of the last comments of
>> https://github.com/shadow-maint/shadow/issues/1704
>> ?
>>
>> We could do that when mounting /proc
>
> That also changes the value for the host. I don't know if that is an 
> issue or not.
>
> I'm currently doing a full build with all tests and the latest shadow 
> version.
> I notice on my current kernel I have CONFIG_LEGACY_TIOCSTI=y so 
> /proc/sys/dev/tty/legacy_tiocsti is set to 1.  I didn't do that 
> explicitly.  It probably depends on the host distro.
>
> I'll see what the results are when it's done.  I'm building at -j4 for 
> timing so that will take a while. 

I ran into this a few weeks ago. It's because CONFIG_LEGACY_TIOCSTI is 
enabled
in the kernel. It should be safe to disable in the kernel. For running 
kernels
set /proc/sys/dev/tty/legacy_tiocsti to 0.

For sysv you can add "dev.tty.legacy_tiocsti = 0" to /etc/sysctl.conf

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page