mer6g@uvaarpa.virginia.edu (Marc E. Rouleau) (02/17/88)
Recently we replaced the 4.3BSD kernel on a MicroVax with the enhanced 4.3BSD kernel from Mt. Xinu. As I understand it, the main difference between the two is that the Mt. Xinu kernel supports NFS. Anyway, ksh, which we ported over from our AT&T toolchest, no longer works very well. In particular, the ENV variable (ENV=.kshrc) is broken. Upon login, ksh executes the user's .profile, but not the .kshrc. Also, history doesn't work at all, even when you set the HISTFILE variable. Has anyone had this problem? Has anyone solved it? Does anyone care? -- Marc Rouleau (marc@virginia.edu)
gwyn@brl-smoke.ARPA (Doug Gwyn ) (02/18/88)
In article <18@uvaarpa.virginia.edu> mer6g@uvaarpa.Virginia.EDU (Marc E. Rouleau) writes:
-Recently we replaced the 4.3BSD kernel on a MicroVax with the enhanced
-4.3BSD kernel from Mt. Xinu. ...
-Anyway, ksh, which we ported over from our AT&T toolchest, no longer
-works very well. In particular, the ENV variable (ENV=.kshrc) is broken.
-Upon login, ksh executes the user's .profile, but not the .kshrc.
-Also, history doesn't work at all, even when you set the HISTFILE variable.
Sounds very much like you're not running ksh at all, but the ordinary
Bourne shell. Check your /etc/passwd entry.
You might try calling Mt. Xinu...dan@rna.UUCP (Dan Ts'o) (02/18/88)
In article <18@uvaarpa.virginia.edu> mer6g@uvaarpa.Virginia.EDU (Marc E. Rouleau) writes:
)-Recently we replaced the 4.3BSD kernel on a MicroVax with the enhanced
)-4.3BSD kernel from Mt. Xinu. ...
)-Anyway, ksh, which we ported over from our AT&T toolchest, no longer
)-works very well. In particular, the ENV variable (ENV=.kshrc) is broken.
)-Upon login, ksh executes the user's .profile, but not the .kshrc.
)-Also, history doesn't work at all, even when you set the HISTFILE variable.
Your copy of ksh could still be using dup(fd|DUPFLAG, fd1) rather than
dup2(). Check for occurances of DUPFLAG and replace with dup2() calls.