All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: ismail d?nmez <ismail.donmez@gmail.com>
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
	Paul Fulghum <paulkf@microgate.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	olh@suse.org
Subject: Re: 2.6.8.1-mm1 Tty problems?
Date: Thu, 26 Aug 2004 16:02:04 -0700	[thread overview]
Message-ID: <20040826230204.GD12762@kroah.com> (raw)
In-Reply-To: <2a4f155d040817224449ef0874@mail.gmail.com>

On Wed, Aug 18, 2004 at 08:44:28AM +0300, ismail d?nmez wrote:
> On Tue, 17 Aug 2004 23:36:02 +0200, Martin Schlemmer <azarah@nosferatu.za.org> 
> > He has the wrong permissions in
> > /etc/udev/permissions.d/50-udev.permissions (or whatever), or no
> > entry for it, and his default_mode (in /etc/udev/udev.conf) is very
> > restrictive, or he does not use pam_console (or using it with a
> > display manager?), or add some other explanation.  Personally I would
> > just say that he/his_distribution should fix the shipped
> > udev.permissions.
> 
> I run Slackware 10 and got this in /etc/udev/permissions.d/udev.permissions :
> 
> # console devices
> console:root:tty:0600
> tty:root:tty:0666
> tty[0-9][0-9]*:root:tty:0660
> vc/[0-9]*:root:tty:0660
> 
> 
> But the real problem is not permissions but the fact that /dev/tty is
> a directory now not a character device. Is this intended? If yes this
> will break many userspace applications which will assume /dev/tty is a
> character device. Greg can you please comment?

/dev/tty is a char device on my system.  Perhaps your rules files are
making that not happen properly.

thanks,

greg k-h

  parent reply	other threads:[~2004-08-26 23:09 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
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 [this message]
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=20040826230204.GD12762@kroah.com \
    --to=greg@kroah.com \
    --cc=azarah@nosferatu.za.org \
    --cc=ismail.donmez@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.