I'm using the modified.xml method of dynamic autoinstall control files.
One of the things I wanted dynamic was the interactive or not choice,
controlled by:
<mode>
<confirm config:type="boolean">false</confirm>
If this was set to true, it should be interactive. I have this being
set in modified.xml, however it does not take effect. Is this option
checked BEFORE the pre-scripts run?
--
Jesse Keating RHCE
Pogo Linux -- Linux Systems Engineer
tel: (888) 828-7646 ex: 436
Hi list,
I successfully installed my suse 9.2 servers via PXE boot, autoyast and
an XML file. Now one of the machines seems to have trouble during the
install - it just hangs (perhaps a bug in my test xml file).
To avoid this in situations where I have no physical access to the
machine I tried: usessh=1 and sshpassword=password as kernel parameters.
(just to have a "backdoor" to reset the machine if it hangs...)
When I now start an automated install the machine boots but WAITS for
the ssh user to log on and start yast by hand, which isn´t quite
practically during automated install ;-)
How do I get access via SSH during install and still have fully
automatic install?
Thanks for your help!
Daniel
Hi group again,
my fiddling with the autoyast configuration options continues.
I have the following entry in my xml file:
<ldap>
<base_config_dn>dc=mydomain,dc=de</base_config_dn>
<create_ldap config:type="boolean">true</create_ldap>
<file_server config:type="boolean">false</file_server>
<ldap_domain>dc=mydomain,dc=de</ldap_domain>
<ldap_server>ldap</ldap_server>
<ldap_tls config:type="boolean">false</ldap_tls>
<ldap_v2 config:type="boolean">false</ldap_v2>
<member_attribute>member</member_attribute>
<pam_password>crypt</pam_password>
<start_ldap config:type="boolean">true</start_ldap>
</ldap>
The server "ldap" is resolvable via our DNS server.
Autoyast triggers the "ldap" authentication (/etc/nsswitch.conf contains a
"passwd_compat: ldap" line), but the ldap configuration itself is done just
half-way. The file /etc/ldap.conf is created with follwing contents (comment
lines removed):
host 127.0.0.1
base dc=example,dc=com
ldap_version 3
pam_password crypt
ssl start_tls
pam_filter objectclass=posixAccount
nss_base_passwd dc=mydomain,dc=de
nss_base_shadow dc=mydomain,dc=de
nss_base_group dc=mydomain,dc=de
>From the last three lines I can see that there is "something" configured in
the file, but why are the "host" and "base" lines kept unusable? They are
clearly defined in my XML config. Is this something I did wrong or is it
just one more bug of autoyast?
Best regards
Ole
--
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
Hello,
we are installing SLES8 with SP3 through HTTP. Although we specified grub as
the boot loader we still get lilo installed by default and have to replace
it with grub in our post install script.
<bootloader>
<location>mbr</location>
<loader_type>grub</loader_type>
<loader_device>/dev/cciss/c0d0</loader_device>
<kernel_parameters>acpi=off 3</kernel_parameters>
<initrd_modules config:type="list">
<module></module>
</initrd_modules>
</bootloader>
Hardware are HP server with /, /boot and /var mounted on normal partitions
(HW RAID 1) and /home, /tmp and /usr mounted to LVM volumes (same RAID 1).
All file systems are XFS.
Kernel and initrd in tftp directory are from SP3, we have the driverupdate
file from SP3 CD1 linked to our SLES8 installation root (/autoyast/SLES8),
in yast/order the paths to SP3 CD1 and CD2 are listed as the first entries.
Regards,
Oliver Schwabedissen
--
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
___________________________________________________
Have your own email and web address for life.
http://www.homemaster.net - Homemaster. Come Together. Online.
> > we are installing SLES8 with SP3 through HTTP. Although we specified
> grub
> > as the boot loader we still get lilo installed by default and have to
> > replace it with grub in our post install script.
> >
> > <bootloader>
> > <location>mbr</location>
> > <loader_type>grub</loader_type>
> > <loader_device>/dev/cciss/c0d0</loader_device>
> > <kernel_parameters>acpi=off 3</kernel_parameters>
> > <initrd_modules config:type="list">
> > <module></module>
> > </initrd_modules>
> > </bootloader>
> Try "tabooing" LILO and selecting GRUB in the package selection, it should
> help.
The package list only contains GRUB, no LILO at all...
Oliver
--
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
I have a control file to automate a SLES9 SP1 installation using autoyast. However, I want yast to wait for the user to accept the end user license agreement before proceeding. Waiting 10 seconds and then automatically accepting the license seems to be the default behavior. Is there a way to disable this?
--John
---------------------------------
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
Hi List,
Does anybody have recommendations for installing a bunch of perl modules
that aren't in RPM? We have a few that require some custom compile
settings. Currently, I'm doing a painful process of installing on a
clean machine, compiling and installing, then making a tar ball from the
output of "make install". Then during post-install, copying and
un-tarring them onto the new system.
This gets us by for now, but is horribly non-maintainable for future
upgrades. What's the "best practice" for installing custom-compiled
perl modules, or modules that are not pre-packaged in RPM's.
Thanks!
-- Ryan