When I now in Yast2 choose "Change source of installation" and point it to the fileserver either via NFS or via mounting the directory and choosing "Harddisk" as installation, I get the following error message; "Could not mount the source medium. mount: filur:/mnt/projects/suse/CD8 failed, reason given by server: No such file or directory"
Of course there is no CD8..... At least my dist came with 7 CD's. I've grepped for anything mentioning a CD8 but cannot find anything.
I'm beginning to doubt that Yast2 actually can set installation medium after initial installation. Gah!
My 8.0 Pro is working fine. I tar'd everything from a single dist DVD to an NFS exported filesystem (host 192.168.0.1, the contents of the dist in /export/install/suse/i386/8.0, and my custom control file(s) in /export/install/suse/i386/8.0_Profiles - the NFS server exports /export/install/suse/i386 read only to the install client(s) with anon=0). Then, I boot from CD #1 on the install client, obtain the IP through DHCP, and for the linuxrc/kernel arguments when the boot prompt comes up I enter: autoyast=nfs://192.168.0.1/export/install/suse/i386/8.0_Profiles/controlfilename install=nfs://192.168.0.1/export/install/suse/i386/8.0 (those two directives are all on one line, of course). I do, however, vaguely recall reading something about if you copy from CD's, to not only copy them all to one, single directory, but that you might also have to edit a file - the problem is, I don't remember which... I *think* it was something like [base-dir]suse/setup/descr/info or [base-dir]/.S.u.S.E-disk-001.2002040316 (or a similar name). The idea being that that particular file is different on each CD, and you need one that pretends to just be the first CD, or something like that. Sorry I can't remember where I saw that, but you might be able to figure it out based on this idea. The dist does only come with 7 CDs, but at least in the U.S., there is also a DVD, as well. Your [base-dir] (mine is /export/install/suse/i386/8.0) should look something like: .S.u.S.E-disk-001.2002040316 LIESMICH autorun.inf ARCHIVES.gz LIESMICH.DOS disks COPYING README docu COPYING.tex README.DOS dosutils COPYRIGHT SuSEgo.ico ls-lR.gz COPYRIGHT.yast TRANS.TBL pubring.gpg ChangeLog _special_ suse INDEX.gz autoinst.xml unsorted and the package dir, [base-dir]/suse, should look essentially like: INDEX d2 gnm3 kde3 sec1 tex2 xsrv4 INDEX.english d3 gnm4 kde4 sec2 x1 xv1 INDEX.german d4 gra1 n1 sec3 x2 xwm1 MD5SUMS doc1 gra2 n2 setup x3 xwm2 TRANS.TBL doc2 gra3 n3 sgm1 x3d1 xwm3 _site_rpms_ doc4 ham1 n4 sgm2 x3d2 yast1 a1 doc5 han1 pay1 snd1 xap1 yast2 a2 e1 images pay2 snd2 xap2 zkm1 ap1 e2 j2 pay3 snd3 xap3 zq1 ap2 emu1 k2de1 pay4 spl1 xdev1 ap3 fun1 k2de2 pay5 spl2 xdev2 ap4 fun2 k2de3 pay6 tcl1 xdev3 ap5 fun3 k2de4 perl1 tcl2 xsrv1 beo1 gnm1 kde1 perl2 tcl3 xsrv2 d1 gnm2 kde2 perl3 tex1 xsrv3
Oh, and by the way... Yast2 always segfaults when I close it. Don't know if it has anything to do with the above problem but this is what it says;
/sbin/yast2: line 149: 27487 Segmentation fault /usr/lib/YaST2/bin/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" -style="$Y2_STYLE" -fn $Y2_XFONT
I don't know about that, but I do know that I had a similar error show up after an error about package selection or something like that, and the install would stop dead right there. It was because I had a problem in my control file - using <!-- ## some text ## --> as a comment. For comments, it seems the following is better: <!-- Some comment. --> I'm fairly new to XML, so this may not be news to others, but the point here is that something funny in the control/autoyast2 file can give you strange results. -John