You review (and possible upload) the output from this directory:
/var/log/xwin
You could at least then confirm the xwin application is running, and starting
(even if it then crashes)...
I had issues after recent upgrades (probably over a year ago) because of what I
had in my local .startxwin...
>> We'd need mksh to network shares for homes first though.
>> My home is: ///gbravery and it really doesn't like it.
>The newly released mksh-39c-3 handles UNC paths correctly now.
Now that's much better! My #! stuff works and it copes with my home being a UNC
perfectly.
I've removed my home-spu
>>> If you want to use a ksh derivative, you are probably better
>>> switching to mksh, which is actively mantained.
>>> IOW, /etc/profile no longer supports pdksh. If you want to keep
>>> using it, you'll need to explicitely add support for it (as you've
>>> done already).
>>Agreed, however, th
>>> Basically, the escapes aren't working right (in XWindows at the very least).
>>>
>>> So I have now changed it to say:
>>> case "${KSH_VERSION}" in
>>> *MIRBSD*KSH* )
>>> PS1=$(print '^[]0;${PWD}\n^[[32m${USER}@${HOSTNAME}
>>> ^[[33m${PWD/${HOME}/~}^[[0m\n$ ')
>>> ;;
>>> *PD*KSH* )
Hi everyone,
I have a minor issue with the /etc/profile file in base files.
I fixed it a while back but the changes over the last few days broke it again
(which made me remember I had done it, which then made me tell you :-).
I still use KSH (generally pdksh) and there is a problem with how thi
5 matches
Mail list logo
