SOLVED: Re: recompiling kernel
- To: firstname.lastname@example.org
- Subject: SOLVED: Re: recompiling kernel
- From: "G. Crimp" <email@example.com>
- Date: Wed, 6 May 1998 17:37:19 -0700
- Message-id: <19980506173719.21911@humble>
- In-reply-to: <19980505120230.G10667@gandalf>; from Bill Leach on Tue, May 05, 1998 at 12:02:30PM -0400
- References: <19980418222810.30234@humble> <19980419233952.13139@flora> <19980505002540.48179@humble> <19980505120230.G10667@gandalf>
On Tue, May 05, 1998 at 12:02:30PM -0400, Bill Leach wrote:
> Hi Gerald;
> Though I noticed your original posting I did not then comment for it
> being too much of a 'blind leading the blind' situation.
More like the blind leading the stupid... Read on.
> What I did notice is that the lines you quoted:
> should work. I am most assuredly not a shell guru but the command
> 'hash' is a bash internal command. _I_ would expect that shells other
> than bash should work correctly because the 'hash' command itself
> would not exist and that would be an error.
Your talk of shells other than bash made something click that should
have clicked before. Bash is the shell I use. However, not so long ago, I
changed the /bin/sh symlink from bash to ash so that netscape helper apps
would not get screwed up by the double parantheses problem.
I keep a log of changes to and maintainance on my system. When I
saw this symlink change, I reasoned that root's shell is bash, and since I
never saw any #!/bin/sh as the first line of any of the files I looked
through, bash would be used. I never gave it a second thought.
Thanks for coming forward. And thanks to all those who offered
help. I'll likely be back as I have compiled but things are not working as
smoothly as they might. But I am going to go back to the docs first.
Thanks again to all.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com