The driver can't be broken ; firstly because I built it !!!!! :-) secondly
because only specific RPMs are always stuck ; and I can install other RPM
and do lots of network stuff before every retry.
Can it be that the RPM installer tries performing other stuff than copying
the files in the package and updating it's database in /var/lib/rpm ? maybe
/proc stuff ? or dns or gateways checks ?
other RPM that is stuck is also bash.... - what is in common between bash
and rootfiles RPMs ?
p.s. regarding my former mails about checksum error in kernel 2.0.34 ; the
problem is that I'v used CHECKSUM_HW which returns bad checksum in the udp
layer. Instead we should use CHECKSUM_NONE which performs the right
what is the differnce between CHECKSUM_HW and CHECKSUM_NONE ; does
CHECKSUM_NONE makes kernel perform checksum on the 4 octets of the ethernet
Ralf Baechle wrote:
> On Thu, Feb 17, 2000 at 08:55:14PM -0500, Rabeeh Khoury wrote:
> > I'm trying to install RPM on my embedded system over NFS ; when I try
> > installing some of the RPM's the system starts transmitting endless
> > lookup requests over the NFS and it doesn't stop. for example the RPM
> > rootfiles-1.5-3.noarch.rpm
> > did any one see problem like this in the past ?
> Nope, seems you invented a new bug :-)
> Maybe your driver is broken and you're just re-transmitting the same
> requests again and again but the server keeps droping them because
> they corrupted? Like that.