Re: [suse-autoinstall] Network installation - kernel command line limitation
Hi Marion, As I've read in documentation, linuxrc just parsing autoyast.xml content and should get these lines without problems. This doesn't happens - but it can mount NFS and get file, and it can get content from HTTP, FTP, whatever. So, seems like this is one of few things in SLES9, which are "documented" but not exists in reality. IMHO it should be raised as request to Novell... Regards, Alexander Dubinin. 2005/10/18, Michael Marion <mmarion@qualcomm.com>:
On 18 Oct, Alexander Dubinin wrote:
Example 7.2. Linxurc options in the control file .... <install> .... <init> <info_file> <![CDATA[ ## Don't remove the following line: # start_linuxrc_conf # install: nfs://192.168.1.1/CDs/full-i386 textmode: 1 autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> ...... </install> ....
Someone can correct me if they've seen differently, but my experience in actually trying this is that it doesn't work. Why? Because the autoyast system has to mount the install path and load the secondary bits before autoyast itself starts and it ever even tries to load the xml profile file. It does seem to work if the xml file is on the boot media itself, but not if your autoyast and install variables point to NFS locations.
Recreation of initrd is not suitable - as I need to install SLES9 in many different locations (As I understand it's "Enterprize" Linux, isn't it? ;) and from different NFS servers. Even in one office, there are few LABs, located behind firewall, where addresses of NFS server are different.
Same here, which is why we created different info files per location and pass the info file argument to the kernel. Also use a custom rule with the new rules system that was added, and have different xml files based on site with the site specific installation bits.
-- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer Simpson: "To alcohol! The cause of, and solution to, all of life's problems." -- Simpsons
-- Regards, Alexander Dubinin
I don't think you're attempting to use it correctly. Yes, you can embed the info file within the autoyast profile, but if you do so, then the autoyast profile must be located in a place where an info file normally resides and it must be named appropriately. Just because you use the embed feature, doesn't change the locations where linuxrc looks for the info file. In your quote below, you show autoyast=file:///info, so that means the autoyast profile must be inside the initrd, located in the root directory, and named 'info'. Is that where you have it or are you trying to pass some other autoyast=<url> on the kernel command line?
Hi Marion,
As I've read in documentation, linuxrc just parsing autoyast.xml content and should get these lines without problems.
This doesn't happens - but it can mount NFS and get file, and it can get content from HTTP, FTP, whatever.
So, seems like this is one of few things in SLES9, which are "documented" but not exists in reality.
IMHO it should be raised as request to Novell...
Regards, Alexander Dubinin.
2005/10/18, Michael Marion <mmarion@qualcomm.com>:
On 18 Oct, Alexander Dubinin wrote:
Example 7.2. Linxurc options in the control file .... <install> .... <init> <info_file> <![CDATA[ ## Don't remove the following line: # start_linuxrc_conf # install: nfs://192.168.1.1/CDs/full-i386 textmode: 1 autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> ...... </install> ....
Someone can correct me if they've seen differently, but my experience in actually trying this is that it doesn't work. Why? Because the autoyast system has to mount the install path and load the secondary bits before autoyast itself starts and it ever even tries to load the xml profile file. It does seem to work if the xml file is on the boot media itself, but not if your autoyast and install variables point to NFS locations.
Recreation of initrd is not suitable - as I need to install SLES9 in many different locations (As I understand it's "Enterprize" Linux, isn't it? ;) and from different NFS servers. Even in one office, there are few LABs, located behind firewall, where addresses of NFS server are different.
Same here, which is why we created different info files per location and pass the info file argument to the kernel. Also use a custom rule with the new rules system that was added, and have different xml files based on site with the site specific installation bits.
-- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer Simpson: "To alcohol! The cause of, and solution to, all of life's problems." -- Simpsons
-- Regards, Alexander Dubinin
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Hi Joe, Yes, I've already found that it can only parse file on local media - either on floppy or in initrd. BTW - it seems to be huge logical gap in linuxrc, to not process XML from URL or NFS, supplied at "autoyast=". All components, required to make it working are in place: linuxrc can parse XML content to get it's own options, linuxrc can retrieve files from network (And doing this for further installation process). So, what is required - just combine these 2 pieces and make very good solution. Regards, Alexander Dubinin 2005/11/7, Joseph V Moss <jmoss@ichips.intel.com>:
I don't think you're attempting to use it correctly. Yes, you can embed the info file within the autoyast profile, but if you do so, then the autoyast profile must be located in a place where an info file normally resides and it must be named appropriately. Just because you use the embed feature, doesn't change the locations where linuxrc looks for the info file.
In your quote below, you show autoyast=file:///info, so that means the autoyast profile must be inside the initrd, located in the root directory, and named 'info'. Is that where you have it or are you trying to pass some other autoyast=<url> on the kernel command line?
Hi Marion,
As I've read in documentation, linuxrc just parsing autoyast.xml content and should get these lines without problems.
This doesn't happens - but it can mount NFS and get file, and it can get content from HTTP, FTP, whatever.
So, seems like this is one of few things in SLES9, which are "documented" but not exists in reality.
IMHO it should be raised as request to Novell...
Regards, Alexander Dubinin.
2005/10/18, Michael Marion <mmarion@qualcomm.com>:
On 18 Oct, Alexander Dubinin wrote:
Example 7.2. Linxurc options in the control file .... <install> .... <init> <info_file> <![CDATA[ ## Don't remove the following line: # start_linuxrc_conf # install: nfs://192.168.1.1/CDs/full-i386 textmode: 1 autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> ...... </install> ....
Someone can correct me if they've seen differently, but my experience in actually trying this is that it doesn't work. Why? Because the autoyast system has to mount the install path and load the secondary bits before autoyast itself starts and it ever even tries to load the xml profile file. It does seem to work if the xml file is on the boot media itself, but not if your autoyast and install variables point to NFS locations.
Recreation of initrd is not suitable - as I need to install SLES9 in many different locations (As I understand it's "Enterprize" Linux, isn't it? ;) and from different NFS servers. Even in one office, there are few LABs, located behind firewall, where addresses of NFS server are different.
Same here, which is why we created different info files per location and pass the info file argument to the kernel. Also use a custom rule with the new rules system that was added, and have different xml files based on site with the site specific installation bits.
-- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer Simpson: "To alcohol! The cause of, and solution to, all of life's problems." -- Simpsons
-- Regards, Alexander Dubinin
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Regards, Alexander Dubinin
On Thursday 10 November 2005 23:07, Alexander Dubinin wrote:
linuxrc can parse XML content to get it's own options,
no it can't The parser is very simple. It just searches for a specific comment as start line and reads until a specific comment that marks the end. This has nothing to do with XML parsing.
linuxrc can retrieve files from network (And doing this for further installation process).
that's true. We'll see if something is possible but at the moment the linuxrc expert is on vacation. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (3)
-
Alexander Dubinin -
Joseph V Moss -
Uwe Gansert