make installkernel help required. (ANSWER... sort of)
Phil Payne
phil at sal-n-phil.net
Wed Sep 22 09:58:12 PDT 2004
On Wed, 2004-09-22 at 16:33, Kevin D. Kinsey, DaleCo, S.P. wrote:
> Phil Payne wrote:
>
> >On Wed, 2004-09-22 at 15:18, Giorgos Keramidas wrote:
> >
> >
> >>On 2004-09-22 13:44, Phil Payne <phil at sal-n-phil.net> wrote:
> >>
> >>
> >>>On Wed, 2004-09-22 at 13:15, Giorgos Keramidas wrote:
> >>>
> >>>
> >>>>Weird. Everything seems ok but you seem to be bumping on a problem
> >>>>related to the shell in use :-/
> >>>>
> >>>>
> >>>Weirder... installed Eterm... and I can installkernel & install ports
> >>>fine. So looks like its only aterm & xterm that have given me a problem.
> >>>
> >>>
> >>Hmmm. What's your login shell? Is it really invoked as a "login shell"
> >>by your xterms/aterms (i.e. with the -ls option of xterm)?
> >>
> >>
> >
> >I use /bin/tcsh. It's not invoked by any aterm/xterm options, its just
> >set in /etc/passwd. Is that what you meant?
> >
> >Phil.
> >
> >
>
> That's the first part. xterm doesn't {by default} set up your shell
> as a "login" shell ... therefore it doesn't get certain environment
> variables, and probably there are a few other things I don't know
> about ...
>
> A simple test: try typing "logout" to exit your xterm. If it responds
> "not a login shell", then, well, it's not. Starting xterm with -ls should
> help with the problem, as Giorgos stated.
>
> Now, to further support the theory Giorgos has here, Eterm *does*
> seem to use its "-l" option by default, so when using Eterm the terminal
> would invoke tcsh as a login shell ... and things should work.
I believe you're correct about it being a login shell issue. Using xterm
and using "su -" instead of "su" fixes the issue.
Not sure what's different in the environment that makes a full login
shell work though.
Anyway, many thanks to all who helped sort this out.
Thanks,
Phil.
> HTH,
>
> Kevin Kinsey
More information about the freebsd-questions
mailing list