From: John Robert LoVerso <loverso@osf.org>
To: Rich Salz <rsalz@osf.org>
Cc: gray@nas.nasa.gov, rc@archone.tamu.edu
Subject: Re: rc, HP-UX, VUE, and me
Date: Thu, 3 Nov 1994 09:19:41 -0500 [thread overview]
Message-ID: <199411031419.KAA20096@postman.osf.org> (raw)
In-Reply-To: Message from Rich Salz <rsalz@osf.org> <9411030155.AA04337@sulphur.osf.org> .
In message <9411030155.AA04337@sulphur.osf.org> you write:
> I took a closer look. I have /bin/csh in /etc/passwd but my .vueprofile
One problem with that approach is that you still end up running vuelogin,
which sits around consuming a few Mbs of your swap area. You are best
off turning it off and just using normal xdm. With this approach, I
deleted my .vueprofile, which is the best solution!
John
next prev parent reply other threads:[~1994-11-03 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-03 1:55 Rich Salz
1994-11-03 14:19 ` John Robert LoVerso [this message]
1994-11-03 17:26 ` Scott C. Gray
-- strict thread matches above, loose matches on Subject: below --
1994-11-02 19:02 rc archive on www Rich Salz
1994-11-02 21:06 ` rc, HP-UX, VUE, and me Scott C. Gray
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=199411031419.KAA20096@postman.osf.org \
--to=loverso@osf.org \
--cc=gray@nas.nasa.gov \
--cc=rc@archone.tamu.edu \
--cc=rsalz@osf.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;
as well as URLs for NNTP newsgroup(s).