Operation Manual
TIP
Consider announcing your repository via OpenSLP if your network setup
supports this option. This saves you from entering the network installation
path on every target machine. The target systems are just booted using
the SLP boot option and nd the network repository without any further
conguration. For details on this option, refer to Section 1.4, “Booting
the Target System for Installation” (page 32).
7
Upload the installation data. The most lengthy step in conguring an installation
server is copying the actual installation media. Insert the media in the sequence
requested by YaST and wait for the copying procedure to end. When the sources
have been fully copied, return to the overview of existing repositories and close
the conguration by selecting Finish.
Your installation server is now fully congured and ready for service. It is auto-
matically started every time the system is started. No further intervention is re-
quired. You only need to congure and start this service correctly by hand if you
have deactivated the automatic conguration of the selected network service
with YaST as an initial step.
To deactivate a repository, select the repository to remove then select Delete. The in-
stallation data are removed from the system. To deactivate the network service, use the
respective YaST module.
If your installation server needs to provide the installation data for more than one
product of product version, start the YaST installation server module and select Add in
the overview of existing repositories to congure the new repository.
1.2.2 Setting Up an NFS Repository
Manually
Setting up an NFS source for installation is basically done in two steps. In the rst step,
create the directory structure holding the installation data and copy the installation
media over to this structure. Second, export the directory holding the installation data
to the network.
14 Reference