Well, finally got it working. HTTP source works, NFS does not. I won't try to figure out what's wrong with it, I will now be able to move to autoyast ;) Thanks for your attention, François On Tuesday 13 June 2006 16:40, Francois Uldry wrote:

Some additionnal informations :

- Network Installation Server root folder cannot be used for Software Installation, although individual folders in it can.

I have the feeling that if I had a way to tell YaST, well the packages are in those 2 subfolders (SLES9 and CORE9) but the install root is there, that would solve my problems.

Is there a way to do that ?

François

On Tuesday 13 June 2006 15:22, fraser_bailey@agilent.com wrote:

...

I found that I had to boot from the SP3 CD, once SP3 was in my depot. Booting from the base distro CD filaed, although I can't now remember what the error was.

-----Original Message----- From: Francois Uldry [mailto:fu-laptop@hors-la-loi.ch] Sent: Tuesday, June 13, 2006 12:28 PM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] Network Installation nightmares

Hello,

This is driving me nuts, I am trying to get a simple Network Installation Server (over NFS) to work.

What I have done : - Through the control centre, on a SLES 9 SP3, used the control panel to create a SLES Network Installation Image as documented, used the SLES 9 original CDs as delivered by Novell. Added the SP 3 CDs to the tree. - Configured DHCP and TFTP to allow network boot. (that works perfectly fine)

I have : /install/SLES9, which is the root of the exported filesystem.

My problem : - Booting from the network, Yast cannot find package description.

Has anyone had that much trouble just getting to a network installation server ?

Any help, question, idea welcome !

Best regards, François

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com