[BUG REPORT] tty_job_control.rs: tty_check_change: orphaned pgrp read char failed: I/O error (os error 5)

[hbuxiaofei]

描述错误

[ WARN ] (src/syscall/mod.rs:381)        SYS_SIGALTSTACK has not yet been implemented
[ WARN ] (src/syscall/mod.rs:381)        SYS_SIGALTSTACK has not yet been implroot@DragonOS:/$ 
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)  tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
emented
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp
read char failed: I/O error (os error 5)
[ DEBUG ] (src/driver/tty/tty_job_control.rs:83)         tty_check_change: orphaned pgrp

请填写您的电脑的信息：

• 操作系统及版本：debian13
• DragonOS版本：d5158a0f
• DADK版本：dadk 0.4.0
• Rust版本：rustc 1.91.0-nightly (ca7750494 2025-08-09)

重现步骤 重现行为的步骤：

make run

或者

qemu-system-x86_64 \
    -name testvm \
    -m 512M \
    -M q35 \
    -accel kvm \
    -cpu host \
    -smp 1 \
    -nographic \
    -hda bin/disk-image-x86_64.img

屏幕截图

其他上下文 在此处添加有关问题的任何其他上下文。

系统日志

[fslongjin]

The issue is caused by dragonreach. I'll PR a fix shortly, changing the default init process to busybox init.

For now, we're not going to maintain dragonreach anymore. We initially introduced dragonreach because, back in the earlier days, busybox init wouldn't run, and we needed an init program. But that's no longer necessary.