I am pleased to confirm that the below problem is rectified in this
morning's new 7.1 beta.

HOWEVER:

1.  The gnome-manual package stops the install with "an error
occurred".  Ctl+Alt+F3 shows a report that it is a bad package.

2.   After returning from that Ctl+Alt+F3 the system is frozen -->
hard reset.

3.   The installer in upgrade mode on normal final exit has neglected
to unmount both the hd install partition and the target partition,
leading to long fix runs the next time those partitions are accessed.

4.   I suspect that configuration data is being reset in upgrade
mode, for example /etc/fstab is totally reinitialised.    It should
be left alone, likewise the mount points arrangements.  If there is
no /mnt/floppy and /mnt/cdrom, it erroneously recreates them without
reference to /etc/fstab to see if they are wanted.  (I use
/mnt/local/cdrom and /mnt/local/floppy in order to distinguish them
from the cdrom and floppy of other machines on the network, all of
which are mountable).

5.   The installer seems to collect all the FAT partitions it can
find and provide mount points and icons for them, indeed, it mounts
them (pointless and highly undesirable).   But why does it not do the
same for all the ext2 (and reiserfs?) partitions it can find?

6.   The very longstanding problem of kernel corrupting /etc/fstab by
replacing the devices with one down or one up numbers, totally
corrupting device names longer than 4 characters, and changing hdd 5
to hd19, for example, when any change is made to the partitioning, or
drives are added or removed, STILL persists in this beta.    This
makes the Linux partitions either unbootable or booting mounts the
incorrect partition!   Imagine the utter confusion!.   BTW, setting
/etc/fstab read-only does not stop this critically severe problem. 
Quite simply, the kernel should NEVER attempt to write /etc/fstab.


Ron Stodden wrote:
> 
> I tried to update yesterday's virgin install of yersterday's 7.1 beta
> download with today's beta download using hd.img.  It is a customised
> development with default packages vanilla install.
> 
> Immediately after OKing the package selection dbox with no changes I
> got:
> 
> An error occurred
> Division by zero

-- 

Regards,

Ron. [AU, Mandrake Linux].

Reply via email to