| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
SFU & MKS
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 SFU & MKS - Oct. 25, '02, 11:11:07 AM
|
|
|
WenSBau
Posts: 8
Joined: Oct. 24, '02,
Status: offline
|
After installing MKS I opened a SFU C shell
and was given the following error:
csh: No entry fo terminal type " nutc"
csh: using dumb terminal settings.
I' d like to know:
1) What is causing this issue?
2) How do I fix the problem?
THANKS!!!!
|
|
|
|
|
RE: SFU & MKS - Oct. 28, '02, 11:23:28 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
quote:
ORIGINAL: WenSBau
After installing MKS I opened a SFU C shell
and was given the following error:
csh: No entry fo terminal type " nutc"
csh: using dumb terminal settings.
How did you start the C shell? did you do it as " csh" or as " csh -l" or did you start it from the " Start Menu" ?
If you started from within an MKS shell then the C shell is started with the environment variables left unchanged, including the TERM environment variable. " nutc" is the TERM setting for Nutcracker/MKS. " interix" is the TERM setting for Interix/SFU.
If you' re trying to use the two products together you should start each of them from the " Start Menu" separately and avoid running programs for one in the other' s environment.
Why do you need both at the same time?
|
|
|
|
|
RE: SFU & MKS - Oct. 28, '02, 1:30:19 PM
|
|
|
WenSBau
Posts: 8
Joined: Oct. 24, '02,
Status: offline
|
I started the C shell by using the C shell icon located in the start->programs->windows services for Unix.
The real issue is that I loaded MKS after SFU and the MKS software changed my SFU environment variables. As a result when I start my SFU C shell I get the error posted earlier. However, when I start a MKS C shell everything is fine. How do I fix this problem?
I need both SFU and MKS due to customer requirements
|
|
|
|
|
RE: SFU & MKS - Oct. 28, '02, 2:01:28 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
It would seem that MKS has set as a system environment variable TERM.
The easiest work-around is to edit the file " /etc/csh.lcl" and add the following code at the bottom of the file. This will switch the TERM to " interix" from " nutc" . This is an over-ride.
if ($?TERM) then
if ($TERM == " nutc" ) then
setenv TERM interix
endif
endif
This will work for the shell started from the Start Menu and when the shell is started as " csh -l" . If you start the shell just as " csh" then the system config files aren' t used. In that case you can add the above code to you " ~/.cshrc" file.
Something similar will need to be done for sh/ksh too. That code will look like (in /etc/profile.lcl or ~/.profile):
if [ " $TERM" == " nutc" ]; then
export TERM=" interix"
fi
|
|
|
|
 RE: SFU & MKS - Oct. 28, '02, 4:02:19 PM
|
|
|
WenSBau
Posts: 8
Joined: Oct. 24, '02,
Status: offline
|
THANKS THAT WORKED!!!!!!!
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
