On Wed, 19 Apr 2000, Jim McBoyle wrote:

> Whilst I was pretending to study, Steven Grunza wrote:
> 
> > My standard by-pass for this problem is to drop into a shell before
> > installing, rename ping to ping.original, copy ls to ping, and then proceed
> > with installation.
> 
> I tried this, but there isn't enough space on the virtual disk to do this,
> using a sybolic or hard link to ls didn't work either, as the system
> doesn't seen to use the stuff you can play with in the way you'd expect..
> if there was a link called ping in /sbin then ping would be called...the
> _real_ ping, not ls-instead-of-ping, which confused me somewhat :-) It
> seems that the compiled in code takes preference to the *system* that is
> running in the virtual disk-space... how on earth this works is far
> beyond a non-programmer like me...in fact the way this seems to be working
> doesn't gel with anything I've come across..I'm stumped! :-) Unfortunatly
> this means I'm still stuck at the I-can't-get-past-the-pinging stage of
> sysinstall and am highly frustrated... Any help will be greatfully
> recieved!
>  

	All the binaries on a sysinst disk are crunched into one
	executable, that then decides behaviou based on the name by
	which its called.

	Another option might be
	'rm /sbin/ping'
	'echo exit 0 > /sbin/ping'
	'chmod 755 /sbin/ping'

	:)


		David/absolute