Hi all,
Just a follow-up note to let you know how I solved (with your help)
the problem. The simplest solution was to just change #!/bin/sh to
#!/bin/ash. However in terms of a permanent fix If the maintainer of
the package did this it would break it for every body that does not
have a /bin/ash. Not so good
My second solution was to reset the original /bin/sh -> /bin/ash and
then set my default shell in /etc/passwd to /bin/bash. In terms of a
permanent fix I believe this is the best as it is just about what you
would expect in a full linux distro. The maintainer of the package
would just have to the /bin/sh -> /bin/ash file and let every one
know that they should update their /etc/passwd or type bash from the
command line.
As a temporary fix (a bit harder than the permanent one would be)
this is what I did.
1) Create a file /var/lib/lrpkg/bash.local which contains:
I bin/sh
I var/lib/lrpkg/bash.*
2) Upodate /etc/passwd to :
root:x:0:0:root:/root:/bin/bash
3) ln -s /bin/ash /bin/sh
4) Backup etc and bash using partial to fd0.
Hope this is informative,
Robert
>Hi all,
>
>Thank you for the answer. At least I know what the problem is. I am
>running bash. When I start up with out it everything works out
>great. I tried loading bash at the end but had the same problem. I
>think that what is happening is that /bin/sh in the scripts points
>to /bin/bash. I will try changing the scrips to /bin/ash and see
>what happens. That will have to wait till tomorrow though. I will
>let you know how it goes.
>
>Thanks again, Robert
>
>>On Sat, 06 Apr 2002 16:21:23 -0800
>>"Robert Williams" <[EMAIL PROTECTED]> wrote:
>>
>>> Hi all,
>>> I just added another computer to my network and decide to install
>>> tinydns instead of updating all of those host files. I am using DS CD
>>> 1.2. However tinydns doesn't seem to work. I am using it straight out
>>> of the box. the only changes I have made was to add entries to the
>>> "/etc/tinydns-private/root/data". I am sure I am missing something
>>> incredibly simple, but if you could point it out to me I would
>>> sincerely appreciate it.
>>>
>>> Thanks Robert
>>>
>>> firewall: /root # svi tinydns restart
>>> /etc/init.d/tinydns: UID: readonly variable
>>
>>Are you using bash as your shell? In ash, UID isn't a readonly variable.
>>In bash, it is. I had to use daemontls.lrp to start my dnscache on Bering
>>when I switched my shell to bash. It may be the same problem you are
>>having. The only other way I know to get UID to be set to something else
>>(which it needs to be to have any of the djb tools run as their proper
>>user instead of root) is to use su or something like it (envuidgid - part
>>of the bering daemontls.lrp package) to actually change the user before
>>the program is run. The djb stuff expects the UID environment variable to
>>be set to the user it is supposed to run as.
>>
>>Thanks,
>>Chad Carr
>
>
--
Unix is a lot more complicated of course -- the typical Unix hacker
never can remember what the PRINT command is called this week -- but
when it gets right down to it, Unix is a glorified video game.
-Ed Post, "Real Programmers Don't Use Pascal"
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
