From: bash@tware.com (Paul Bash) Subject: Re: [solved]:apparent stack corruption with 0.99.10 kernel Date: Wed, 23 Jun 1993 13:57:48 GMT
In article <1993Jun22.201442.5371@nynexst.com> hjl@nynexst.com (H.J. Lu) writes:
>In article <1993Jun22.151400.493@tware.com>, bash@tware.com (Paul Bash) writes:
>|> In article <1993Jun21.173306.19836@tware.com> I wrote:
>|> >
>|> >I'm running the SLS 1.01 distribution on top of which I've installed
>|> >the 0.99.10 kernel, libc-4.4 and net-2. Everthing appears to work well with
>|> >the exception of the uname() library function.
>|> >
>|>
>|> Thanks to Linus for this tip.
>|>
>|> The problem was that when unpacking inc-4.4.tar.z, I did so with / as the
>|> current directory (as I did with image-4.4.tar.z and extra-4.4.tar.z).
>|> Unfortunately, inc-4.4.tar.z expects /usr as the current directory. This
>|> is completely undocumented but I should have noticed had I paid a bit
> ^^^^^^^^^^^^^^^^^^^^^^^^
>
>Have you ever read release.libc-4.4? BTW, I will change that in libc 4.4.1.
>Watch out for release.libc-4.4.1.
>
>
>H.J.
No, I completely missed seeing release.libc-4.4.
Now, if you would put release.libc-4.4 _inside_ the xxxx-4.4.tar.z files as
well as outside, you would assure they wouldn't get accidently seperated and
cause more confusion. In my case, I just missed seeing the release.libc-4.4
file at tsx-11. I can imagine a scenario, though, where someone passes
the xxxx-4.4.tar.z files to a friend but forgets to include the release
doc.
I'm also glad you will be changing the way the archive is created. It
certainly makes more sense to create all of the archives relative to the root
directory (but without absolute paths, of course). At least it simplifies
installation quite a bit by making things consistent.
Thanks.
-- Paul Bash Techware Design bash@tware.com Boulder, CO U.S.A.