Once I figure this out, I thought I'd enter as little information on this "command line" as was needed and put everything else in the info file. Bad move on my part. After trying unsuccessfully for many, many times to get the networking information to work in the info file, I finally gave up the info file and decided to enter all the information on the "command line" in syslinux.cfg (see above). Voila, it worked like a charm. So the only information I ended up putting in the info file was the "insmod tulip" line (this was recognized by linuxrc, so I knew that it actually found and parsed t! he info file). There is no example in the documentation for what the entries in the info file should look like. Should they be like this?:
ip=x.x.x.a server=x.x.x.b nameserver=x.x.x.c etc.
or should they look like this?:
ip x.x.x.a serever x.x.x.b nameserver x.x.x.c etc.
or should they look like something else? Neither one of these syntaxes worked, so it must be entered some other way. But you wouldn't know what the syntax should be, because there are no examples of what it should look like. Could someone clue me in on this, please?
I tried entering the key/value pairs with the syntax given in this webpage, but it still didn't work. I'm just going to rely on entering all information on the command line.
documenation says that it works with nfs as well tftp. I called the name of the control file 1A2B3C4D (random hex numbers for illustration) but yast didn't recognize it for the machine with the given target ip number. I used capital hex digits like it says in the documentation. Does it require the .xml suffix? Any help would be appreciated.
No xml suffix needed. just the hex string. The autoyast keyword must then point to a directory.
Okay, this doesn't work for me, either, then.
Second, I would like to configure my hosts.allow and hosts.deny configuration files within the autoinstall process. There was an email in the archives of the mailing list from a user who experienced the same problems that I had, but there were no posted solutions. I typed the xml directives in my control file as explained in Section 4.13, because there is no facility to add them from within yast2. When I loaded the control file back into yast2's configuration module, it changed the entries I had typed in to add /etc/hosts.allow.
was replaced by <listentry> and the <files config:type="list" > <listentry>
sshd: x.x.x.a sshd: x.x.x.b sshd: x.x.x.c sshd: x.x.x.d sshd: x.x.x.e sshd: x.x.x.f ]]>
/etc/hosts.allow </listentry> <listentry>ALL:ALL
]]>
/etc/hosts.deny </listentry> </files>Any suggestions on how to modify this, so that yast will actually write these configurations to /etc?
Ok, checking on this.
Please let me know when you have more information for me. This is a feature I would really like to use.
Last of all, I would like to add an rpm file to the installation that is not present in the current distribution. I found an email similar to this in the mailing list archive, but the links that were given on the subject no longer existed. I would appreciate a section in the documentation on how to do this. This is what I tried to do. In the directory $Install_root/suse/setup/descr on the nfs server, there is a file, common.pkd, with entries for all the rpm packages in the installation. I added this entry to this file:
##----- gromacs ----- Filename: gromacs-3.1.4-1.i386.rpm RpmName: gromacs Series: custom InstPath: 01 /custom/ Size: 7581000 2735235 Buildtime: BuiltFrom: Flag: RpmGroup: Custom Copyright: AuthorName: Version: 3.1.4-1 Requires: libsfftw.so.2 libsrfftw.so.2 Provides: do_dssp editconf eneconv ffscan g_anaeig g_analyze g_angle g_bond g_bundle g_chi g_cluster g_clustsize g_confrms g_covar g_density g_dielectric g_dih g_dipoles g_disre g_dist g_dyndom g_enemat g_energy g_gyrate g_h2order g_hbond g_helix g_lie g_mdmat g_mindist g_morph g_msd g_nmeig g_nmens g_order g_potential g_rama g_rdf g_rms g_rmsdist g_rmsf g_rotacf g_saltbr g_sas g_sgangle g_sorient g_tcaf g_traj g_velacc genbox genconf genion genpr gmxcheck gmxdump grompp highway luck make_ndx mdrun mk_angndx ngmx pdb2gmx protonate tpbconv trjcat trjconv trjorder wheel x2top xpm2ps xrama
I also created the directory, custom, in the $Install_root/suse directory. I placed the gromacs-3.1.4-1.i386.rpm file in this directory (custom). I also made sure the fftw package was installed. Also, in the custom directory, I added this file:
nfsserver:# cat INDEX.english gromacs-3.1.4-1.i386.rpm: GROMACS molecular dynamics package
Then, in the control file, I added an entry as directed in Section 4.6.3. Here is the snippet:
custom <packages config:type="list"> <package>gromacs</package> </packages>The installation failed when it tried to install gromacs. This is the message I got:
gromacs.rpm: file not found
Do I need to add a flag to the entry in common.pkd? Other than that, I have no idea why it doesn't work. Any insights would be appreciated.
You dont need to add the package data to the common.pkd file if you use
. Using common.pkd mean that you have to handle the package as a distribution package and not extra.
Okay, I removed the entry I put in common.pkd and modified my entry in the
control file. Instead of trying to use a shortname for the rpm file, I wrote
the full name of the rpm file, minus the rpm suffix, and it worked
perfectly. The control file now looks like this:
I hope that this will be helpful to others who have also tried to use autoinstall, but ran into similar problems.
Thanks for the detailed report. Anas
Sid
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- Anas Nashif
, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com