From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: root@chaos.analogic.com
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: something funny about tty's on 2.6.4-rc1-mm1
Date: Tue, 02 Mar 2004 12:47:40 -0500 [thread overview]
Message-ID: <m3ishn5ef7.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0403021000250.19478@chaos> (Richard B. Johnson's message of "Tue, 2 Mar 2004 10:02:17 -0500 (EST)")
>>>>> "Richard" == Richard B Johnson <root@chaos.analogic.com> writes:
Richard> I think /dev/tty, used in the context of any process, always
Richard> refers to the current processes terminal. You should not have
Richard> to "hard-code" a particular terminal.
No, I obviously was ambiguous. I use:
export HISTFILE=~/.bash_history_${USER}_$(tty|sed s_^/dev/__|tr / _)
in my ~/.bashrc to ensure that each term has a unique and repeatable
HISTFILE. I do not see any alternative tuple that is unique and
repeatable.
This change makes that idiom useless, with no alternative available.
On a multi-user server the change is clearly the right thing to do,
but on a workstation, laptop or handheld, where few ptys are typically
allocated, the case isn't so clear.
-JimC
next prev parent reply other threads:[~2004-03-02 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 18:45 something funny about tty's on 2.6.4-rc1-mm1 Nuno Monteiro
2004-03-01 19:09 ` Richard B. Johnson
2004-03-02 5:47 ` H. Peter Anvin
2004-03-02 14:52 ` James H. Cloos Jr.
2004-03-02 15:02 ` Richard B. Johnson
2004-03-02 17:47 ` James H. Cloos Jr. [this message]
2004-03-02 16:54 ` H. Peter Anvin
2004-03-02 22:08 ` Andrew Morton
2004-03-03 2:29 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 19:04 Albert Cahalan
2004-03-02 19:54 ` H. Peter Anvin
2004-03-02 22:46 ` Edgar Toernig
2004-03-02 23:59 ` H. Peter Anvin
2004-03-03 4:12 Albert Cahalan
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=m3ishn5ef7.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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