Pavel M. Penev writes:
> ...all new packages should be aware of the in-building of the command...
All POSIX shells do not provide 'kill' (ash, for example).
> ...and not use explicit paths (like "/bin/kill").
Scripts should rely neither on $PATH nor on bashisms.
--
John Hasler
[EMAIL PROTECTED]
I should of said "woody".
--
According to MegaHAL:
The emu is a mass of incandescent gas, a gigantic nuclear furnace.
On Fri, 21 Jul 2000, Eric G . Miller wrote:
> I seemed to have lost /bin/kill. Now, I have /usr/bin/kill, but "poff"
> (and possibily others) are looking for /bin/kill. I fixed poff, but I
> don't know what else might get broken due to the disappearance of
> /bin/kill. Anyway, I was wondering
Not sure which Debian version you're running, but in both potato and
slink it should be at /bin/kill according to the output of 'dpkg -L'.
In potato, /bin/kill is in the procps package, while in slink it's in
bsdutils. In both potato and slink there is also a /usr/bin/skill, and
it's in the procp
I seemed to have lost /bin/kill. Now, I have /usr/bin/kill, but "poff"
(and possibily others) are looking for /bin/kill. I fixed poff, but I
don't know what else might get broken due to the disappearance of
/bin/kill. Anyway, I was wondering if anyone can shed some light on the
"movement" of kil
5 matches
Mail list logo
