"J. Greenlees" <[EMAIL PROTECTED]> writes:
> seems logical to assume that with larger dirtibution size and
> better compression used in the packages that the time taken will
> be substantially larger, no a mathematical progression but more a
> logarythmic progression. the install is doing more wo
>
>
>
>But I multiplied by three to account for this?
>
>Merci beaucoup,
>Don Parsons
>
>
hmm 590.9 mb for mandrake 6.1 on cd. ( just put old cd in drive and
checked the size )
2100 mb or thereabouts for mandrake 9 download edition, substantially
more than three times in size, plus the higher c
On 26 Sep 2002 17:46:34 +0200
Guillaume Cottenceau <[EMAIL PROTECTED]> wrote:
> Donald F Parsons <[EMAIL PROTECTED]> writes:
>
> > i) resolv.conf can not be written. Happened with both rc2 and rc3.
> > Work around: go to text console 2 and rm /mnt/etc/resolv.conf
> > and repeat network
Donald F Parsons <[EMAIL PROTECTED]> writes:
> i) resolv.conf can not be written. Happened with both rc2 and rc3.
> Work around: go to text console 2 and rm /mnt/etc/resolv.conf and
> repeat network configuration. For some reason resolv.conf is link
> to /etc/ppp/resolv.conf on my
> Why is install about 8 times longer than it should be?
Dependency checks I guess, causing a roughly exponential increase in time
instead of your linear extrapolation. In the pre-configured cases, the
RPMS could be installed using --nodeps if that is not already done and
fixing the dependency inf
i) resolv.conf can not be written. Happened with both rc2 and rc3.
Work around: go to text console 2 and rm /mnt/etc/resolv.conf and
repeat network configuration. For some reason resolv.conf is link
to /etc/ppp/resolv.conf on my 8.2 Oh, I see problem, the absolute
links are i
