[Sheflug] Re: major crash ++ shells

[Matt Fairtlough <xxxxx [at] xxxxxxxxxxxxxx>]

Matt Fairtlough wrote:

> Can anyone cast any light on the following trace from 
> /var/log/messages (crash with suspicious
> problems on rebooting: took several attempts)? 
> this is a brand new Gigabyte GA-7DXR+ board with AMD XP 1800+ and 
> 512MBytes DDR (from Dane-elec(?)
> replacing my previous, defunct main board.

<lots of guff deleted>

thanks to everyone who made suggestions about this.  I've not since had 
any trouble with booting or running linux.

Just a wierd glitch I suppose.

Now I've another question about SuSE 7.3/KDE2.2.1/shells which is 
driving me up the wall.  I'm trying to set my path ($path) on login.

You'd have thought that would be easy, but it doesn't seem so.

My login shell is tcsh.  Set using YAST control centre.  And indeed I am 
running tcsh in all shells when I log in.  So you'd have thought
that /etc/csh.login would be sourced.  And that sources 
/etc/csh.login.local in which I set my path to (/some/new/path $path). 
 But no.
(I've tested it: it echos a message and I see nothing)

Now if I force a tcsh login shell with > tcsh -l
then the path is as it should be.  So: where the *** IS my tcsh login 
shell when I start KDE?  And what kind of shell is running when
I start the KDE shell tool?  Or does KDE just not provide a login shell?

One of my problems is that I don't understand the difference between 
upper case and lower case environment variables.
But if I set path to something sensible that seems to be the path 
searched by tcsh and it works.

Oh well, I can always get myself a login shell manually.  But I am going 
to forget this and then wonder where my executables have gone.

Matt.

>
>



___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.