here's the (very simple) partition part of the kickstart file I am
fooling around with:
part /boot --size 50 --ondisk hda
part / --size 1000 --ondisk hda
part raid.01 --size 500 --ondisk hda
part raid.02 --size 500 --ondisk hdc
raid /storage --level 1 --device md0 raid.01 raid.02
in this situation, /boot and / are formatted xfs, the raid device is
formatted ext2. basically, just now I tried to add the --fs xfs option:
raid /storage --fs xfs --level 1 --device md0 raid.01 raid.02
but anaconda barfs when parsing the file (--fs: unknown option). either
I'm using the option incorrectly or that's another clue to the problem.
...
the other oddity, one I think I've seen mentioned on the list before -
when attempting a graphical install (via nfs), the X server can't start,
it dies with (hand-copied):
Gdk-Error **: Fatal IO error 104 (Connection reset by peer) on X server
:1
At first I thought this was just occurring with the intel-815 integrated
agp motherboard we have here, but it is the same with an asus
motherboard w/ onboard agp. on the other hand I have seen it work
recently on a sis chipset/amd motherboard with onboard agp (sorry for
the lack of specifics).
I just reverified, at least with the 815, that the normal RH 7.1
installer works fine.
...
one last little difference between installers: in the xfs-modified
version, when installing on the 815 (specifically an intel d815eeal), I
am always prompted as it brings the network up to choose the ethernet
module type to insert (intel etherexpress pro, onboard); the normal
rh7.1 install doesn't bother me with this.
Matt
|