Though there is someone point out that "dud=http://......" or something alike is not supported by SLES10SP2.
But I still want to know that when I remaster a SLES10SP2 DVD that support the new RAID controller on my new server.
When I insert a dud(a vfat img file) into initrd(copy from SLES10SP2 DVD), and want linuxrc load this driver update disk by passing a command line parameter like "dud=file:///dd.img",but linuxrc just didn't notice that.
I am just wonder it is there any chance to insert a dud into initrd( /boot/i386/loader/initrd), and let linuxrc know that there is a dud to load.
I have to do it that way because I have no network around, So anyone can help me to figure it out.Thank you!
-- Man kann alles,was Man will.
on Tuesday 27 October 2009 Jung Wilhelm wrote:
I am just wonder it is there any chance to insert a dud into initrd( /boot/i386/loader/initrd), and let linuxrc know that there is a dud to load.
I have to do it that way because I have no network around, So anyone can help me to figure it out.Thank you!
in your initrd create a directory structure like this: linux/suse/i386-sles10/inst-sys/
the architectury must fit to your system of course.
everything you put in the inst-sys directory will appear in the root filesystem of the inst-sys. The content of the "inst-sys" directory will be copied to the root directory ("/") of the inst-sys
you dont have to tell linuxrc then about it. You dont need a driverupdate file either.
Thanks for your instant replay! Through some code-reading effort last night, finally I have resolve this problem,here is what I have done:
I just extract the pre-made "driverupdate",and put the contents into initrd, and got a "linux" directory who's structure just a little different from what you have described. like: linux `-- suse `-- i386-sles10 | -- install | | -- update.post | | -- update.pre | ` -- update.tar.gz ` -- modules ` -- xxxx.ko
But anyway linuxrc load the driver normally.
And another question, if I want to put the autoyast.xml into the initrd, Then how can I do to make linuxrc load it. Thank you.
2009/10/27 Uwe Gansert ug@suse.de:
on Tuesday 27 October 2009 Jung Wilhelm wrote:
I am just wonder it is there any chance to insert a dud into initrd( /boot/i386/loader/initrd), and let linuxrc know that there is a dud to load.
I have to do it that way because I have no network around, So anyone can help me to figure it out.Thank you!
in your initrd create a directory structure like this: linux/suse/i386-sles10/inst-sys/
the architectury must fit to your system of course.
everything you put in the inst-sys directory will appear in the root filesystem of the inst-sys. The content of the "inst-sys" directory will be copied to the root directory ("/") of the inst-sys
you dont have to tell linuxrc then about it. You dont need a driverupdate file either.
-- ciao, Uwe Gansert
Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/%7Eug
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Wednesday 28 October 2009 Jung Wilhelm wrote:
And another question, if I want to put the autoyast.xml into the initrd, Then how can I do to make linuxrc load it. Thank you.
first of all, linuxrc is not loading the autoyast.xml at all - but that's nitpicking ;) put it in the inst-sys directory that I described in my previous post and refer to it as autoyast=file:///...
Hi all,
I have to use an HP-UX server for DHCP on our VLAN. I would like to keep our SLES server as the autoyast server for the BOOTP NFS etc for the autoyast clients.
Has anyone had any experience with configuring HP-UX to pass off the client to the SLES server?
Currently, on HP-UX 11.23 I have;
root@123:/opt/ignite/boot/LINUX# file * elilo-3.12-ia64.efi: data elilo-ia64.conf: ascii text elilo-ia64.efi: data images: directory
root@123:/opt/ignite/boot/LINUX# cat elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=images/SuSE11/Linux label=SuSE11 description="Install SuSE Enterprise 11" initrd=images/SuSE11/initrd append="install=nfs://10.205.8.145/pxelinux.0 read-only
root@123:/opt/ignite/boot/LINUX#
However, I later changed the file to read: # cat /opt/ignite/boot/LINUX/elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=sles11_i586/linux label=SLES11_i586 description="Install SuSE Enterprise 11" initrd=initrd append="initrd=initrd ramdisk_size=65536 install=nfs://10.205.8.145/export/sles11-dvd1-i586 hostip=10.205.8.254/24 autoyast=nfs://10.205.8.145/export/generica-sles11_i586-autoinst.xml netdevice=eth0 textmode=1 insmod=bnx2" read-only
HP-UX /etc/bootptab reads as;
autoyast:\ ht:=ethernet:\ hn:\ sm=255.255.252.0:\ gw=10.205.8.1:\ bf=/opt/ignite/boot/LINUX/elilo-ia64.efi:\ bs=61
Not that this made a blind bit of difference because a /nettl/ (HP-UX version of tcpdump) of the client's request was for this file: ../opt/ignite/boot/boot_lif.octet.tsize.0
Cheers, S.
Hi all,
I have to use an HP-UX server for DHCP on our VLAN. I would like to keep our SLES server as the autoyast server for the BOOTP NFS etc for the autoyast clients.
Has anyone had any experience with configuring HP-UX to pass off the client to the SLES server?
Currently, on HP-UX 11.23 I have;
root@123:/opt/ignite/boot/LINUX# file * elilo-3.12-ia64.efi: data elilo-ia64.conf: ascii text elilo-ia64.efi: data images: directory
root@123:/opt/ignite/boot/LINUX# cat elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=images/SuSE11/Linux label=SuSE11 description="Install SuSE Enterprise 11" initrd=images/SuSE11/initrd append="install=nfs://10.205.8.145/pxelinux.0 read-only
root@123:/opt/ignite/boot/LINUX#
However, I later changed the file to read: # cat /opt/ignite/boot/LINUX/elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=sles11_i586/linux label=SLES11_i586 description="Install SuSE Enterprise 11" initrd=initrd append="initrd=initrd ramdisk_size=65536 install=nfs://10.205.8.145/export/sles11-dvd1-i586 hostip=10.205.8.254/24 autoyast=nfs://10.205.8.145/export/generica-sles11_i586-autoinst.xml netdevice=eth0 textmode=1 insmod=bnx2" read-only
HP-UX /etc/bootptab reads as;
autoyast:\ ht:=ethernet:\ hn:\ sm=255.255.252.0:\ gw=10.205.8.1:\ bf=/opt/ignite/boot/LINUX/elilo-ia64.efi:\ bs=61
Not that this made a blind bit of difference because a /nettl/ (HP-UX version of tcpdump) of the client's request was for this file: ../opt/ignite/boot/boot_lif.octet.tsize.0
Cheers, S.
PS. Please presume that we can only have one DHCP server per VLAN. PPS. Please ignore the earlier Email with the wrong title.
Hi,
I think that the bootptab is the wrong file and I ought to have looked into the /etc/dhcptab on HP-UX 11.23. This has more useful information and may explain why the client was being passed the wrong .efi file.
I have prepared this new entry, but am unsure what the class-id ought to be set to. Its is currently : class-id="PXEClient:Arch:00002":\ Does any one know which class-ids should be used for Linux/SLES?
dhcp_pool_group:\ re:\ pool-name=LINUX_BOOT:\ ncid:\ addr-pool-start-address=10.222.8.254:\ addr-pool-last-address=10.222.8.254:\ allow-bootp-clients=TRUE:\ class-id="PXEClient:Arch:00002":\ bf=/opt/ignite/boot/LINUX/elilo-ia64.efi:\ hn:\ gw=10.222.8.1:\ ds=10.222.18.10 10.222.18.11:
Simon Loewenthal/NL/Tele2 wrote:
Hi all,
I have to use an HP-UX server for DHCP on our VLAN. I would like tokeep our SLES server as the autoyast server for the BOOTP NFS etc for the autoyast clients.
Has anyone had any experience with configuring HP-UX to pass off the client to the SLES server?
Currently, on HP-UX 11.23 I have;
root@123:/opt/ignite/boot/LINUX# file * elilo-3.12-ia64.efi: data elilo-ia64.conf: ascii text elilo-ia64.efi: data images: directory
root@123:/opt/ignite/boot/LINUX# cat elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=images/SuSE11/Linux label=SuSE11 description="Install SuSE Enterprise 11" initrd=images/SuSE11/initrd append="install=nfs://10.205.8.145/pxelinux.0 read-only
root@123:/opt/ignite/boot/LINUX#
However, I later changed the file to read: # cat /opt/ignite/boot/LINUX/elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=sles11_i586/linux label=SLES11_i586 description="Install SuSE Enterprise 11" initrd=initrd append="initrd=initrd ramdisk_size=65536 install=nfs://10.205.8.145/export/sles11-dvd1-i586 hostip=10.205.8.254/24 autoyast=nfs://10.205.8.145/export/generica-sles11_i586-autoinst.xml netdevice=eth0 textmode=1 insmod=bnx2" read-only
HP-UX /etc/bootptab reads as;
autoyast:\ ht:=ethernet:\ hn:\ sm=255.255.252.0:\ gw=10.205.8.1:\ bf=/opt/ignite/boot/LINUX/elilo-ia64.efi:\ bs=61
Not that this made a blind bit of difference because a /nettl/ (HP-UX version of tcpdump) of the client's request was for this file: ../opt/ignite/boot/boot_lif.octet.tsize.0
Cheers, S.
PS. Please presume that we can only have one DHCP server per VLAN. PPS. Please ignore the earlier Email with the wrong title.
Hi Simon
Check out RFC 4578 on page 3 http://tools.ietf.org/html/rfc4578#page-3
I can only confirm that booting a HP-UX IA64 system from a SLES DHCP server (the other way around) works. This is what I use in dhcpd.conf:
option arch code 93 = unsigned integer 16; if option arch = 00:00 { # x86 filename "pxelinux.0"; next-server [sles-bootserver]; } else { # IA64=00:02 filename "/opt/ignite/boot/nbp.efi"; next-server [hpux-bootserver]; }
Cheers, Michael
-----Ursprüngliche Nachricht----- Von: Simon Loewenthal/NL/Tele2 [mailto:simon.loewenthal@klunky.co.uk] Gesendet: Mittwoch, 28. Oktober 2009 12:45 An: opensuse-autoinstall@opensuse.org Betreff: Re: [opensuse-autoinstall] HP-UX DHCP and SLES bootp/nfs server co-existance
Hi,
I think that the bootptab is the wrong file and I ought to have looked into the /etc/dhcptab on HP-UX 11.23. This has more useful information and may explain why the client was being passed the wrong .efi file.
I have prepared this new entry, but am unsure what the class-id ought to be set to. Its is currently : class-id="PXEClient:Arch:00002":\ Does any one know which class-ids should be used for Linux/SLES?
dhcp_pool_group:\ re:\ pool-name=LINUX_BOOT:\ ncid:\ addr-pool-start-address=10.222.8.254:\ addr-pool-last-address=10.222.8.254:\ allow-bootp-clients=TRUE:\ class-id="PXEClient:Arch:00002":\ bf=/opt/ignite/boot/LINUX/elilo-ia64.efi:\ hn:\ gw=10.222.8.1:\ ds=10.222.18.10 10.222.18.11:
Simon Loewenthal/NL/Tele2 wrote:
Hi all,
I have to use an HP-UX server for DHCP on our VLAN. I would like tokeep our SLES server as the autoyast server for the BOOTP NFS etc for the autoyast clients.
Has anyone had any experience with configuring HP-UX to pass off the client to the SLES server?
Currently, on HP-UX 11.23 I have;
root@123:/opt/ignite/boot/LINUX# file * elilo-3.12-ia64.efi: data elilo-ia64.conf: ascii text elilo-ia64.efi: data images: directory
root@123:/opt/ignite/boot/LINUX# cat elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=images/SuSE11/Linux label=SuSE11 description="Install SuSE Enterprise 11" initrd=images/SuSE11/initrd append="install=nfs://10.205.8.145/pxelinux.0 read-only
root@123:/opt/ignite/boot/LINUX#
However, I later changed the file to read: # cat /opt/ignite/boot/LINUX/elilo-ia64.conf chooser=textmenu message=hplinux.msg prompt
image=sles11_i586/linux label=SLES11_i586 description="Install SuSE Enterprise 11" initrd=initrd append="initrd=initrd ramdisk_size=65536 install=nfs://10.205.8.145/export/sles11-dvd1-i586 hostip=10.205.8.254/24 autoyast=nfs://10.205.8.145/export/generica-sles11_i586-autoinst.xml netdevice=eth0 textmode=1 insmod=bnx2" read-only
HP-UX /etc/bootptab reads as;
autoyast:\ ht:=ethernet:\ hn:\ sm=255.255.252.0:\ gw=10.205.8.1:\ bf=/opt/ignite/boot/LINUX/elilo-ia64.efi:\ bs=61
Not that this made a blind bit of difference because a /nettl/ (HP-UX version of tcpdump) of the client's request was for this file: ../opt/ignite/boot/boot_lif.octet.tsize.0
Cheers, S.
PS. Please presume that we can only have one DHCP server per VLAN. PPS. Please ignore the earlier Email with the wrong title.
autoinstall@lists.opensuse.org
-
Jung Wilhelm -
Michael.Leu＠mgb.ch -
Simon Loewenthal/NL/Tele2 -
Uwe Gansert