f_offset

Poul-Henning Kamp phk at phk.freebsd.dk
Mon Apr 14 07:55:11 UTC 2008


In message <20080414074710.GI5934 at hoeg.nl>, Ed Schouten writes:

>I'm experiencing similar problems with implementing read() and write()
>inside my mpsafetty branch for TTY's. Just like the current TTY
>implementation, my implementation will do strange things when two
>threads call read() or write() at the same time. Data could end up mixed
>together.

The write side of this will break quite a lot of stuff, starting
with syslogd(8), write(1), wall(1) and similar, all which expect
to be able to spam terminals coherently.

The read side will probably mostly cause trouble for programs that
try to take input from /dev/tty, usually passwords.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


More information about the freebsd-arch mailing list