Red Hat Bugzilla – Bug 146058
Have Anaconda detect and mount vfat partions
Last modified: 2013-03-13 00:47:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
I would be great if Anaconda would detect and mount vfat partions.
This would save some energy, and would be very nice for newbies. I
have a script here which I setup to do such a thing:
I did it becuase FC3 marked the third time I would have had to do it
manually. This would serve as a nice optional step at least.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start install FC3
2. Run and complete Anaconda
3. Boot system
Actual Results: vfat partions must be manually setup
Expected Results: vfat partions could be automatically setup
This should be being taken care of by hal.
I don't understand the comment about hal. Can you explain? Also,
what are the chances of getting vfat driver update disks to be
detected and used?
> I don't understand the comment about hal. Can you explain?
The code in the initial post is not good since it just relies on the
MSDOS partition type and thus won't work on other arches where the
native partitioning format is different (think ppc) - you really need
to look at each partition in detail, e.g. look for file system
This is more difficult that it sounds, as e.g. various IDE RAID drives
has their RAID signature in weird places so it looks like a VFAT
partition when it really isn't. Mounting such a partition will work
too, but result in scary data loss / corruption.
However, HAL will do this for FC4 since we've just got some code to
detect IDE RAID partitions. Stay tuned.
> Also, what are the chances of getting vfat driver update disks to be
> detected and used?
I don't think this question has anything to do with this bug.
Ok thanks for clarifing. I too was curious about the hal comment. But
I understand now. So is it safe to explect FC4 to auto-setup my linux
> So is it safe to explect FC4 to auto-setup my linux
That is indeed the plan, yeah.
Many thanks in advance.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.