public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Olaf Hering <olh@suse.de>
Cc: "ismail dönmez" <ismail.donmez@gmail.com>,
	"Paul Fulghum" <paulkf@microgate.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-mm1 Tty problems?
Date: Wed, 18 Aug 2004 20:58:37 +0200	[thread overview]
Message-ID: <1092855516.8998.34.camel@nosferatu.lan> (raw)
In-Reply-To: <20040818064229.GD22332@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Wed, 2004-08-18 at 08:42, Olaf Hering wrote:
>  On Wed, Aug 18, ismail dönmez wrote:
> 
> > On Wed, 18 Aug 2004 08:22:10 +0200, Olaf Hering <olh@suse.de> wrote: 
> > > /dev/tty is supposed to be char c 5 0, /class/tty/tty/dev will tell udev
> > > how to create it, see man 4 tty.
> > > No idea who came up with the bright idea to put legacy bsd devices in a
> > > subdir. Documentation/devices.txt shows that my patch is ok, it handles
> > > up to 256 device nodes.
> > > If you are using udev, file a bugreport for your distros package. In the
> > > meantime, remove the offending line from your udev.rules file.
> > 
> > I don't think you understood me. /dev/tty is created as a char device
> > in 2.6.8.1 kernel. So I am sure udev is fine but it shows up as a
> > directory in 2.6.8.1-mm1 kernel and if I backup bk-driver-core.patch
> > its all normal again.
> 
> Works fine here.
> Check you udev.rules file if some rule matches the pattern ptyp0.

Hmm, Ok, so I see we have pty devices in there as well.  Ismail, what
tries to use /dev/tty anyhow?

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-18 18:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 14:08 2.6.8.1-mm1 Tty problems? ismail dönmez
2004-08-17 18:01 ` Paul Fulghum
     [not found]   ` <2a4f155d0408171116688a87f1@mail.gmail.com>
     [not found]     ` <4122501B.7000106@microgate.com>
2004-08-17 19:00       ` ismail dönmez
2004-08-17 19:31         ` Paul Fulghum
2004-08-17 19:37           ` ismail dönmez
2004-08-17 19:43           ` ismail dönmez
2004-08-17 20:05             ` Paul Fulghum
2004-08-17 20:52               ` ismail dönmez
2004-08-18  6:22               ` Olaf Hering
2004-08-18  6:34                 ` ismail dönmez
2004-08-18  6:42                   ` Olaf Hering
2004-08-18 18:58                     ` Martin Schlemmer [this message]
2004-08-19 17:28                       ` Tonnerre
2004-08-19 19:24                         ` Martin Schlemmer
2004-08-19 19:24                           ` Olaf Hering
2004-08-19 19:46                             ` Martin Schlemmer
2004-08-17 21:30             ` Martin Schlemmer
2004-08-17 21:04         ` Paul Fulghum
2004-08-17 21:36           ` Martin Schlemmer
2004-08-18  5:44             ` ismail dönmez
2004-08-18 18:43               ` Martin Schlemmer
2004-08-26 23:02               ` Greg KH
2004-08-17 21:00 ` Paul Fulghum
2004-08-18 12:22   ` Stephen Smalley
2004-08-18 13:05     ` Paul Fulghum
2004-08-18 13:27       ` ismail dönmez

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=1092855516.8998.34.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=ismail.donmez@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=paulkf@microgate.com \
    /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