From: Paul Fulghum <paulkf@microgate.com>
To: "ismail dönmez" <ismail.donmez@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-mm1 Tty problems?
Date: Tue, 17 Aug 2004 14:31:34 -0500 [thread overview]
Message-ID: <41225D16.2050702@microgate.com> (raw)
In-Reply-To: <2a4f155d04081712005fdcdd9b@mail.gmail.com>
ismail dönmez wrote:
> 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?
That does not look right.
Char dev 3 is the pty major.
This could be left over from running with the controlling-tty patch.
Try recreating /dev/tty as a char special file:
mknod -m 666 /dev/tty c 5 0
--
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2004-08-17 19:34 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 [this message]
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
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=41225D16.2050702@microgate.com \
--to=paulkf@microgate.com \
--cc=ismail.donmez@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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