[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Before you release....





I hear Disk Drake from mandrake is open source and reviewers talk highly of it.
In terms of newbie-frendliness the advantage is that the FIPS step can be
omitted because it can resize FAT partitions as part of the install process.





Jon347@flashmail.com on 19/01/2000 20:53:23

Please respond to independence-l@independence.seul.org

To:   independence-l@independence.seul.org
cc:

Subject:  Re: Before you release....




> IIRC, Indy is based on the RedHat 6.0 install, so I guess that the same
> would apply to Indy's install. But, in my experience most Linux systems
> give you the option to create a boot disk. Everytime I install a Linux
> system, I create a boot disk, and use that instead of over writting the
> MBR. I currently don't dual boot on any of my machines, but none of them
> have anything useful in the MBR, they all boot direct from a floppy.
> Granted I do only reboot my boxes to install/play with the hardware,
> install a UPS or similar, so I'm probably not the user Indy's aimed at,
> but I can't see why this solution shouldn't be usable by 'normal' users.
> Infact if Indy 6.1-0.8 uses the same install manager (more or less) as
> 6.0-0.8, then it DOES ask/prompt/allow the creation of a boot disk; my
> current Indy system boots from the floppy.
>
> Perhaps we should add this into the docs, or install process?

The problem is just redhat's installation or any other installation I've
seen,  never lets users know of the problem. Redhat's partition wizard just
says the partition is too big when you try to partition a linux native above
the 1024 sector.  When you try redhat's fdisk it says you might have
problems. And lilo's installation doesn't check.  Never does it say, "you
have a problem because of this, skip lilo installation and just use a
bootdisk and you'll be ok." I have never seen redhat's actual
documentation - im a more wing it type of guy :) - but i think the
installation should at least present whats going on.  Also the problem of
getting redhat's partion tool to work with the bug there.

In short.. We have to notify users of the problem more easily.... not tucked
away in some howto or from some guy in a chat room.

~Jon








This E-mail message is private and confidential and should only be read
by those to whom it is addressed.

If you are not the intended recipient, you are hereby notified that any
dissemination, distribution, copying, reproduction, modification or
publication of this communication is strictly prohibited.  Please delete
the message from your computer and destroy any copies.

This message is not intended to be relied upon by any person without
subsequent written confirmation of its contents.  This company therefore
disclaims all responsibility and accepts no liability of any kind which
may arise from any person acting, or refraining from acting, upon the
contents of the message without having had subsequent written
confirmation.

If you have received this communication in error, or if any problems
occur in transmission please notify us immediately by telephone on
+44 (0)2476 425474