I wanted to prove if I was right or wrong.
Well, I've gone and done, proved myself right or wrong. The verdict is in...
Guilty as charged
Hey, at least I am admitting it.
The "remove all data" and the "manually partition" screen does indeed appear
for the server option. After seeing it displayed, I now remember seeing it
and chosing the manual option. What made me back out if there was Disk Druid.
I hate that program. It is a bear to use because it just can't get it right
(more on that in a little bit). I don't know what made me go back and use
the remove all data option. The help on the left did say that it will remove
all data from your DRIVE. Note the singular drive. Unlike the manual, I
don't remember it saying that it will remove all partitions/data from ALL
installed drives. That is a simple thing to add, if it really isn't there.
Yep, it was a major mistake to take the wrong path. It went and did what
it said it was going to do.
What I'd like to know is why RedHat feels that it is necessary to destroy
all partitions on all drives? What if the system was not a new system and
that the main disk had to be rebuilt because of a crash, or other problem?
But the other disks that were in the system are OK. There is really no
need to remove all partitions from all drives. It is strongly suggested
that the partitionin option screen be changed to the following choices:
automatic partitioning
manually partitioning
When automatic is taken, the user is then presented with a list of available
hard drives, which the user would then place check marks next to, signifying
which drives are to be used for the automatic partitioning, thereby allowing
the good drives to be left along. As an added bonus, the drives that are
to be left alone could be listed on a following page asking where they
should be mounted (if at all). Once that is done, then the automatic
partitioning should take place. Mount points would be created for those
drives marked as such and entries placed in the fstab file. I feel this
would be a great improvement for the installer. I don't think that a person
should have to open the chassis and disconnect hard drives before doing an
install. Yes, it can be avoided by choosing the custom option. But, it
can be avoided under all options.
As for Disk Druid, it still has a problem. The problem is that
it still doesn't know how to do math. After creating two partitions, it told
me that I had 4886 MB left. So, I made /usr to be 4886. But, DD took
the swap partition (or maybe /) out of the list and said there wasn't enough
space. But wait... it just told me that I had 4886 and I used 4886, but it
didn't like it. By playing games, I go it within 1MB of what I wanted.
At the time, I didn't know what the Grow To Fill option was all about. Now
it seems all I had to do was select a smaller size and check the box and it
would have made it larger to fill the disk. I'll know that for next time.
Any particular reason why fdisk is no longer available as an option to those
of use who prefer that method of disk partitioning? And, why did DD fall over
when it told me that I had 4886 left and used that amount, only to get an
error? Fix this simple problem and DD will be improved some more. It is
getting better. To the point where even I'll start using it.
So, in conclusion, I goofed. I'm sure Tom is happy to read that I am admitting
that. My dislike of Disk Druid led to part of my downfall.
Let's keep these suggestions in mind and move forward. This is a bad
experience that we all need to forget.
MB
--
e-mail: [EMAIL PROTECTED]
Bart: Hey, why is it destroying other toys? Lisa: They must have
programmed it to eliminate the competition. Bart: You mean like
Microsoft? Lisa: Exactly. [The Simpsons - 12/18/99]
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.