public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: Matthew Harrell  <mharrell-dated-1054037874.c3b3f2@bittwiddlers.com>
Cc: Martin Schlemmer <azarah@gentoo.org>,
	Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Strange terminal problem with 2.5.6[8-9]
Date: Thu, 22 May 2003 19:38:15 +0100	[thread overview]
Message-ID: <3ECD1917.4010408@vgertech.com> (raw)
In-Reply-To: <20030522121749.GA1173@bittwiddlers.com>

Hi!

Matthew Harrell wrote:
> : 2.5.68 and later have depreciated devpts support in devfs.  Thus
> : you have to enable:
> : 
> :  CONFIG_DEVPTS_FS=y
> : 
> : and mount it during boot.  Easy way is just to add to fstab:
> : 
> : ------------------
> : none	/dev/pts	devpts	defaults	0 0
> : ------------------
> 
> Sure enough that was it.  Darn it.  I must have missed that change entirely.
> I was compiling in devpts but still figured it was mutually exclusive with
> devfs (which I am using).
> 
> Thanks
> 

Now try:
# time ps auwx > /dev/null

Here it takes more than two seconds :) That's because ps is trying to 
access /dev/pts[0-9]+ first. That results in a attempt to insert a 
module for that device.

Because I was getting tired of this i made a quick hack:
     # some confusion with devfsd and devpts in 2.5. Quick hack:
     for i in `seq 0 512` ; do  ln -s /dev/pts/$i /dev/pts$i 2>&1 > 
/dev/null ; done 2>&1 > /dev/null

..in my init scripts.

Using devfs (and devfsd) and devpts.

This is "new" in 2.5.68 and 69 :)

Regards,
Nuno Silva



      reply	other threads:[~2003-05-22 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11  0:44 Strange terminal problem with 2.5.6[8-9] Matthew Harrell
2003-05-22  1:36 ` Matthew Harrell
2003-05-22  5:31   ` Martin Schlemmer
2003-05-22 12:17     ` Matthew Harrell
2003-05-22 18:38       ` Nuno Silva [this message]

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=3ECD1917.4010408@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --cc=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell-dated-1054037874.c3b3f2@bittwiddlers.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