From: Jeff Dike <jdike@addtoit.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Testing needed for terminal handling patches
Date: Tue, 10 Aug 2004 01:15:30 -0400 [thread overview]
Message-ID: <200408100515.i7A5FUQW027590@ccure.user-mode-linux.org> (raw)
I've posted a set of patches that fiddle with UML's handling of terminal modes
to http://user-mode-linux.sourceforge.net/patches.html
I'd like people to try them out and report bad experiences, especially if you
saw the 'netdevice 0' hang or stairstepping output during boot. They are the
catch-eintr, bb-raw, and clean-raw patches.
In particular, I removed the complain argument to raw, which means that it
will always complain if something failed. The reason it was there in the
first place is that a long, long time ago, in a universe far, far away, I
saw a failure there on stdout call printk, which would recurse through the
same code, causing the same failure, reporting it through printk again, ad
infinitum. I'm curious as to whether this infinite recursion was sparked
by an EINTR or something else.
Also, TCSACRAIN is always used instead of TCSANOW. I don't see any reason
that I need NOW instead of DRAIN.
Jeff
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-08-10 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 5:15 Jeff Dike [this message]
2004-08-10 18:49 ` [uml-devel] Testing needed for terminal handling patches Allen Chan
2004-08-10 21:22 ` Jeff Dike
2004-08-11 6:53 ` Matt Clay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408100515.i7A5FUQW027590@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox