Re: Eterm
> > > hi, > > when updated my box from 5.3 to 5.4 / -STABLE i ran into probs with > > Eterm ... transparancy still works but "--tint" option does not > > produce usable results: my Eterm is alway blue - no matter which > > color i specify :( > > > i did several cvsups and rebuilds of the base system and the ports > > but with no luck so far > > > anybody else seeing this behaviour? anybody using eterm with --trans > > --tint--shape successfully on 5.4 / -STABLE ? > > Had this happen several months ago (February). Try recompiling Eterm > with "-DWITH_MMX". today i tried -DWITH_MMX on my box with the eterm prob - et voila :) ... everything works fine now :) open question: why is this option necessary at all now (after updating from 5.2.1)? before this update eterm worked on this box as expected ... wired ... thx regards, stan -- "Perfection is achieved, not when there is nothing left to add, but when there is nothing left to take away." --- Antoine de St. Exupery, Wind, Sand, and Stars, 1939 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Eterm
hi, when updated my box from 5.3 to 5.4 / -STABLE i ran into probs with Eterm ... transparancy still works but "--tint" option does not produce usable results: my Eterm is alway blue - no matter which color i specify :( i did several cvsups and rebuilds of the base system and the ports but with no luck so far anybody else seeing this behaviour? anybody using eterm with --trans --tint--shape successfully on 5.4 / -STABLE ? Had this happen several months ago (February). Try recompiling Eterm with "-DWITH_MMX". There was a thread on bsdforums about this: http://www.bsdforums.com/forums/showthread.php?t=28875 -- Paul Boehmer [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Eterm
hi, when updated my box from 5.3 to 5.4 / -STABLE i ran into probs with Eterm ... transparancy still works but "--tint" option does not produce usable results: my Eterm is alway blue - no matter which color i specify :( i did several cvsups and rebuilds of the base system and the ports but with no luck so far anybody else seeing this behaviour? anybody using eterm with --trans --tint --shape successfully on 5.4 / -STABLE ? thx regards, stan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Neither aterm, eterm, nor rxvt can su to root in 4.3
On 06-Apr-2001 Steve Watt wrote: > >I have a fresh install of 4.3 here which exhibits the same problem. What > >version of X are you using? > >(both xterm and eterm exhibit it) > Make sure you've rebuilt rxvt/xterm/whatever; I saw this once (on > another OS) when the tty headers changed a wee tad. A quick glance > at the recent commits doesn't tell *me* anything that might have hit > here, but one can never be 100% certain... I don't think this is the case.. I am seeing this problem after installing FreeBSD 4.3 and then building everything on this machine (ie rxvt, xterm etc). --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: SOLVED: Neither aterm, eterm, nor rxvt can su to root in 4.3
On 06-Apr-2001 Larry Librettez wrote:
> Problem solved. Turns out my use of "nonstandard"
> characters in my root password (like ^*&(@$#) were the
> cause of the problem. Specifically, use of the '('
> character somehow was causing authentication problems
> with rxvt in X, thus disallowing su to root and the
> error "BAD SU to root on ttyp*". After changing my
> root password to no longer use the ( character, I now
> can su to root in rxvt, eterm, and aterm in 4.3RC.
> And thus the wild goose chase finally comes to an end.
>
> Again, strange that this was not causing difficulty
> with 4.2-STABLE, I only noticed it in 4.3-BETA and now
> in 4.3-RC1 and 4.3-RC2.
>
> Thank you all for your helpful suggestions, it helps
> to eliminate potential problems one by one.
You know I have a weird problem with aterm (which uses the rxvt core AFAIK)..
When I run tclsh8.2 (or maybe 8.3?) on my 4-STABLE, XFree86 4 system either ( or )
(I can't remember which) generates a backspace (!)
Related?
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
SOLVED: Neither aterm, eterm, nor rxvt can su to root in 4.3-RC2
Problem solved. Turns out my use of "nonstandard"
characters in my root password (like ^*&(@$#) were the
cause of the problem. Specifically, use of the '('
character somehow was causing authentication problems
with rxvt in X, thus disallowing su to root and the
error "BAD SU to root on ttyp*". After changing my
root password to no longer use the ( character, I now
can su to root in rxvt, eterm, and aterm in 4.3RC.
And thus the wild goose chase finally comes to an end.
Again, strange that this was not causing difficulty
with 4.2-STABLE, I only noticed it in 4.3-BETA and now
in 4.3-RC1 and 4.3-RC2.
Thank you all for your helpful suggestions, it helps
to eliminate potential problems one by one.
Larry
--- "Warren W. Gay VE3WWG" <[EMAIL PROTECTED]> wrote:
> I am not having su problems, but perhaps our
> problems are related
> somehow, since the "login" process is involved...
>
> I am running Exceed under Win98 to access my FreeBSD
> with xterm,
> to my now "4.3-RC2" box.
> It now hangs waiting to login (using the rlogin
> method).
>
> From my other FreeBSD machine (4.2-RELEASE),
> if I try to rlogin to my 4.3-RC2 box,
> it also hangs for a long time after I enter the
> password (approx
> 2-3 minutes). Then it finally plunks me into the
> shell as expected.
>
> From an existing session, the ps display shows that
> the login process
> is hung up waiting for something.
>
> Otherwise, its a mystery, and I cvsup-ed again
> today, hoping the problem
> would be fixed, but not so yet... here's hoping for
> tomorrow..
>
> Warren.
>
> Alfred Perlstein wrote:
> >
> > * Larry Librettez <[EMAIL PROTECTED]> [010405
> 09:42] wrote:
> > > With 4.3-RC2, I cannot su to root in X using
> either
> > > aterm, eterm, or rxvt terminals. However, in
> xterm or
> > > gnome-terminal or at a plain console, I am able
> to do
> > > so. (This was not a problem with 4.2-STABLE
> where I
> > > could su to root in any type of terminal in X.)
> >
> > What does "id" say in aterm? what about on
> console?
> >
> > --
> > -Alfred Perlstein -
> [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
> > Represent yourself, show up at BABUG
> http://www.babug.org/
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-stable" in the body of
> the message
>
> --
> Warren W. Gay VE3WWG
> http://members.home.net/ve3wwg
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of
> the message
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Neither aterm, eterm, nor rxvt can su to root in 4.3-RC2
I am not having su problems, but perhaps our problems are related somehow, since the "login" process is involved... I am running Exceed under Win98 to access my FreeBSD with xterm, to my now "4.3-RC2" box. It now hangs waiting to login (using the rlogin method). >From my other FreeBSD machine (4.2-RELEASE), if I try to rlogin to my 4.3-RC2 box, it also hangs for a long time after I enter the password (approx 2-3 minutes). Then it finally plunks me into the shell as expected. >From an existing session, the ps display shows that the login process is hung up waiting for something. Otherwise, its a mystery, and I cvsup-ed again today, hoping the problem would be fixed, but not so yet... here's hoping for tomorrow.. Warren. Alfred Perlstein wrote: > > * Larry Librettez <[EMAIL PROTECTED]> [010405 09:42] wrote: > > With 4.3-RC2, I cannot su to root in X using either > > aterm, eterm, or rxvt terminals. However, in xterm or > > gnome-terminal or at a plain console, I am able to do > > so. (This was not a problem with 4.2-STABLE where I > > could su to root in any type of terminal in X.) > > What does "id" say in aterm? what about on console? > > -- > -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] > Represent yourself, show up at BABUG http://www.babug.org/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Warren W. Gay VE3WWG http://members.home.net/ve3wwg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Neither aterm, eterm, nor rxvt can su to root in 4.3-RC2
`id` is identical at both aterm, eterm, rxvt, and console: uid=1001(lipshitz) gid=1001(lipshitz) groups=1001(lipshitz), 0(wheel) --- Alfred Perlstein <[EMAIL PROTECTED]> wrote: > * Larry Librettez <[EMAIL PROTECTED]> [010405 > 09:42] wrote: > > With 4.3-RC2, I cannot su to root in X using > either > > aterm, eterm, or rxvt terminals. However, in > xterm or > > gnome-terminal or at a plain console, I am able to > do > > so. (This was not a problem with 4.2-STABLE where > I > > could su to root in any type of terminal in X.) > > What does "id" say in aterm? what about on console? > > > -- > -Alfred Perlstein - > [[EMAIL PROTECTED]|[EMAIL PROTECTED]] > Represent yourself, show up at BABUG > http://www.babug.org/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
