On Sun, 2002-12-08 at 16:13, Rob Lahaye wrote: > Darren Freeman wrote: > > On Sun, 2002-12-08 at 15:38, Rob Lahaye wrote: > > > >>Darren Freeman wrote: > >> > >>>Aaah crap, my /bin/sh is a symlink to bash =) No wonder =) > >>> > >>>OK so reading the above, what's the sh way of doing these things? Since > >>>I don't even have sh it explains why I don't have the manpage... > >> > >>What funny OS are you using? > > > > > > Mandrake Linux 9.0 =) > > Aha, I've got that on another PC here with Mandrake 9.0. > So...let me see...ah, yes indeed: "/bin/sh -> bash". > Hmmm, wonder why Mandrake has that? > > Anyway, the conflict arises when using the /bin/sh on my FreeBSD system. > > >>Instead of "you writing semi-sh script and having me testing it for you", > >>I suggest you install the real "sh" on your OS and write & test the script > >>yourself :) Wouldn't that be more sensible? > > > > > > it might but I was hoping it wouldn't take long to fix those two > > things.. and up until now I thought I was using sh.. Mandrake tricked me > > into thinking I had compatibility =( > > Right. Only is, that I have no time for it now. I'm jumping in a plane > soon, have to prepare a few presentations before that. I won't be "on-line" > until second week of January. I hope you or someone else can deal with these > minor problems. > > But I like your script and the way it eases the procedure to get a backtrace. > It should go into some subdir of CVS any time soon.
Thanks for the feedback. Have a good time, I'll sort it out sometime. Just means reading the manual for sh, if what I do is in there then I can probably just wait for the testers to tell me if something weird happens. It'll either die right away or probably keep on working on sh. Or I can get off my arse and download sh. Naaaahhhh =) > Cheers, > Rob. Darren
