Date: Mon, 14 Apr 2008 07:55:04 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Ed Schouten <ed@80386.nl> Cc: arch@freebsd.org Subject: Re: f_offset Message-ID: <5287.1208159704@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 14 Apr 2008 09:47:10 %2B0200." <20080414074710.GI5934@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20080414074710.GI5934@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@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5287.1208159704>