Re: exec issue in tcsh?

On Sat, 25 Aug 2001, Jim Bryant wrote: Wow. Why not use xdm? 8) Too lazy? Heh. You just uncomment one line in /etc/ttys and HUP init. It's not compilicated. -- Never put off until tomorrow what you can do today. There might be a law against it by that time. -- /usr/games/fortune,

Re: exec issue in tcsh?

Date: Sun, 26 Aug 2001 02:43:56 -0400 (EDT) From: Brandon D. Valentine [EMAIL PROTECTED] On Sat, 25 Aug 2001, Jim Bryant wrote: Wow. Why not use xdm? 8) Too lazy? Heh. You just uncomment one line in /etc/ttys and HUP init. It's not compilicated. Indeed. However, there are some

Re: exec issue in tcsh?

Wow. Why not use xdm? 8) Too lazy? Heh. You just uncomment one line in /etc/ttys and HUP init. It's not compilicated. Indeed. However, there are some differences in startup of which to be aware (.xinitrc vs. .xsession). I just hard-link the two files together. :) Nate To

Re: exec issue in tcsh?

In message [EMAIL PROTECTED] Jim Bryant writes: : Wow. Why not use xdm? 8) : : Too lazy? vi /etc/ttys; s/off/on on xdm line; kill -1 1 Too lazy to do even that? Wow! That's Lazy :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the

Re: exec issue in tcsh?

David Wolfskill wrote: Date: Sun, 26 Aug 2001 02:43:56 -0400 (EDT) From: Brandon D. Valentine [EMAIL PROTECTED] On Sat, 25 Aug 2001, Jim Bryant wrote: Wow. Why not use xdm? 8) Too lazy? Heh. You just uncomment one line in /etc/ttys and HUP init. It's not compilicated. Indeed.

Re: exec issue in tcsh?

Nate Williams wrote: Wow. Why not use xdm? 8) Too lazy? Heh. You just uncomment one line in /etc/ttys and HUP init. It's not compilicated. Indeed. However, there are some differences in startup of which to be aware (.xinitrc vs. .xsession). I just hard-link the two files together.

Re: exec issue in tcsh?

* Jim Bryant [EMAIL PROTECTED] [010823 01:33] wrote: i noticed this after a build from -current of about 24 hours ago: due to problems getting kde-2.2 to compile under -current, I am currently using windowmaker and doing a `exec startx /dev/null` to get into X without leaving a

exec issue in tcsh?

i noticed this after a build from -current of about 24 hours ago: due to problems getting kde-2.2 to compile under -current, I am currently using windowmaker and doing a `exec startx /dev/null` to get into X without leaving a console shell open... the problem i have is that when i switched

exec issue with tcsh?

Please DISREGARD my previous message on this topic... I have issued myself a severe boot to the head in the true tradition of tai-kwan-leap as a result of sending that, so if you must, please remember that I booted myself in the head first, and was enlightened by the experience. jim -- ET