For a live CD which should be able to mount partitions on the host computer,
it's easy to zap that policy file (it's just an rm in the .ks file for the live
CD). But beware not to use that live CD on computers with older GNU/Linux
distributions which don't support the latest ext3 features installed.
not realy
that would work with FC6 and probably below but not with FC7. the default value is set that you don`t see the partitions.. it doesn`t mather if you have that 99 policy or not in that case.. it mathers when you want to ENABLE it. then the value needs to be chanmged and that can be done serveral ways.. the easiest is editing the 99 file but it is also possible in the thing that is actually mounting it (hal or udev)
2007/5/12, Kevin Kofler <kevin.kofler@xxxxxxxxx>:
Another good argument which hasn't been cited in this thread yet is that the
locations the device mounts to aren't (or weren't when this was introduced,
maybe this has improved) guaranteed to stay constant across reboots.
And in addition, automounting an ext2/ext3 partition from an older version of
Fedora or RHL (or another older distribution) can make that system fail to boot
due to new ext3 features like extended attributes getting enabled, which the
old kernel can't deal with.
IMHO, fixed devices are really what /etc/fstab is for. This also gives you the
advantage that you can pick any mount point you wish (for example /c for C: if
you dual-boot that proprietary OS which still uses drive letters in 2007)
instead of getting something like /media/VOLUME_LABEL or /media/DISK_1 or
whatever automatically assigned.
For a live CD which should be able to mount partitions on the host computer,
it's easy to zap that policy file (it's just an rm in the .ks file for the live
CD). But beware not to use that live CD on computers with older GNU/Linux
distributions which don't support the latest ext3 features installed.
Kevin Kofler
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
