Mailinglist Archive: opensuse-factory (422 mails)
|< Previous||Next >|
Re: [opensuse-factory] Feedback on the Yast installserver module
- From: Ladislav Slezak <lslezak@xxxxxxx>
- Date: Wed, 07 Jan 2009 17:34:56 +0100
- Message-id: <4964D9B0.9060408@xxxxxxx>
Birger Kollstrand wrote:
I don't get it. It sets up a ftp/http/nfs share and that's it.
Yes, the functionality is very basic, it sets up a selected network service and
copies CDs/ISOs to the shared directory.
A small add-on in SLP service configuration.
No information on how it's ment to be used on the booting client is given in
the yast module. Do I need a boot disk? If so , then there definately should
be a wizzard assisting with that.
You need to boot the target machines via different mechanism (mini-ISO, USB
local HDD, PXE...) and and use the install server as a package source.
It definately does not set up a network boot as I was expecting. there is
no atftp or tftp server set up. I would like to "Press F12 for network boot"
and install from there. We use this at work in conjunction with autoyast and
it's fabulous. but horribly hard to set up and maintain.
That's true :-(
Sorry that I did not test teis earlier and I do not think it looks usable for
anyone but hardcore users.
That's because to set up an installation server is complex and the
depends on the target machines (special boot parameters like vga=???). Autoyast
installation makes the config even more complicated.
We should find a compromise between simple but limited PXE config and generic
hard to use (and implement) approach.
Currently there is "Announce as Installation Service with SLP" check box. I
a new check box "Add to PXE boot config" there.
In short, these steps are required to setup the boot server:
- install needed packages (tftp, syslinux)
- configure tftp service and start it (yast2-tftp-server package can be reused
- copy PXELINUX to /tftpboot dir
- create initial PXELINUX config file
(Yast should check if the boot server has been already set up and should not
it in that case.)
These steps are needed when a new product is added
- copy the kernel and initrd from CD/ISO to /tftpboot (there might be more
available, ask user which should be added?)
- add a new boot entry to PXELINUX config (with possibility to edit the kernel
The PXELINUX config must be updated when
- a product is renamed (different path in the installation URL)
- the network service is changed (e.g. from NFS to FTP install server)
It looks not too hard to implement it yast instserver (I think that the PXELINUX
config update will be the most problematic part).
SUSE LINUX, s.r.o. e-mail: lslezak@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
|< Previous||Next >|