public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Paul Fulghum <paulkf@microgate.com>
Cc: "ismail dönmez" <ismail.donmez@gmail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	olh@suse.org, "Greg KH" <greg@kroah.com>
Subject: Re: 2.6.8.1-mm1 Tty problems?
Date: Tue, 17 Aug 2004 23:36:02 +0200	[thread overview]
Message-ID: <1092778561.8998.18.camel@nosferatu.lan> (raw)
In-Reply-To: <412272C8.6050203@microgate.com>

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

On Tue, 2004-08-17 at 23:04, Paul Fulghum wrote:
> ismail dönmez wrote:
> 
> > On Tue, 17 Aug 2004 13:36:11 -0500, Paul Fulghum <paulkf@microgate.com> wrote:
> > 
> >>Even if a feature is not be enabled,
> >>backing out a patch can verify it does not
> >>touch code outside of the feature.
> >>
> > 
> > 
> > Indeed backing up selinux-revalidate-access-to-controlling-tty.patch
> > fixed "less" problem. But some other problems remain and the real
> > issue is /dev/tty is a directory now! :
> > 
> > 
> > cartman@southpark:~$ ls -al /dev/tty
> > total 0
> > drwxr-xr-x   2 root root     0 2004-08-18 00:52 ./
> > drwxr-xr-x  15 root root     0 2004-08-17 21:53 ../
> > crw-------   1 root root 3, 10 2004-08-18 00:52 s
> > crw-------   1 root root 3,  0 2004-08-18 00:52 s0
> > crw-------   1 root root 3,  1 2004-08-18 00:52 s1
> > crw-------   1 root root 3,  2 2004-08-18 00:52 s2
> > crw-------   1 root root 3,  3 2004-08-18 00:52 s3
> > crw-------   1 root root 3,  4 2004-08-18 00:52 s4
> > crw-------   1 root root 3,  5 2004-08-18 00:52 s5
> > crw-------   1 root root 3,  6 2004-08-18 00:52 s6
> > crw-------   1 root root 3,  7 2004-08-18 00:52 s7
> > crw-------   1 root root 3,  8 2004-08-18 00:52 s8
> > crw-------   1 root root 3,  9 2004-08-18 00:52 s9
> > 
> > 
> > And this breaks many applications. Any idea why /dev/tty is a directory now?
> 
> Olaf, Greg:
> 
> The addition of pty devices to sysfs in bk-driver-core.patch
> of 2.6.8.1-mm1 seems to be causing the problem described above.
> See the rest of this thread for more details.
> 

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.

Apart from above, I cannot say anything is wrong with the addition of
tty's to sysfs, and if its the same in functionality as the old patch
from Greg, then I ran it for months no problem.


-- 
Martin Schlemmer

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

  reply	other threads:[~2004-08-17 21:32 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 [this message]
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=1092778561.8998.18.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox