Does anyone know if it is possible to use the 'dirinstall' from the command
line?
For instance i would like to be able to do something like:
# yast dirinstall -d /someroot -s mypackages.sel
If i do yast -h it says:
"Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]"
But is there a way to find out what 'module specific parameters' are available
for a specific module?
Thanks,
Teun
On Monday 13 March 2006 16:25, Klaus Kaempf wrote:
> > you are right, yast/order and yast/instorder will not work for SLES10
> > I'll try to find out how the new resolver wants that now.
>
> This will be defined by jsrain(a)suse.cz
> He's already working on the new specification.
I'll announce the solution here on the mailinglist as soon as the
specification is ready.
--
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany
e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0,
Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Hi,
I'm trying to move deployments from SLES9 SP1 to SP3 using the same
control file. Here's a snippet of xml I'm having trouble getting to work
with SP3:
<interfaces config:type="list">
<interface>
<bootproto>static</bootproto>
<broadcast>172.30.192.255</broadcast>
<device>eth0</device>
<ipaddr>172.30.192.12</ipaddr>
<netmask>255.255.255.0</netmask>
<network>172.30.192.0</network>
<startmode>onboot</startmode>
</interface>
</interfaces>
With SP1, after the install, my network comes up fine whether I'm using
a static IP or DHCP assigned. Installing with SP3, the interfaces never
get configured and the ifcfg-ethX files aren't written out to disk.
I have a workaround that I'm applying right now where I write the
ifcfg-ethX files out via a post install script embedded in the xml but I
would much rather not hack it in.
Any help is appreciated.
-Matt
What is the best way to set the default keyboard layout to english-us in an
AutoYaST installation? (SLES9)
It appears my keyboard map is correct, but my X11 setup isn't.
Thanks,
David Bellis
Hello,
This issue occured both with SLES 9 SP2 and SLES 9 SP3
on an IBM x346.
We have different hardwaremodels (IBM x306m, IBM x346,
...). To install SLES9 SP2 on an IBM x306m we needed
to provide a diskette with the driverupdate for the
raid controller. I added this driver in the
driverupdate from SLES 9 SP2 (used scripts on site of
Uwe Gansert to do this).
Installation of my testserver (which is an IBM x346)
goes fine. However the server hangs when i reboot the
server after logging in. (install uses the default sp2
kernel. reboot is needed to activate the bigsmp
kernel). During reboot the server hangs after the
message "Please stand by while rebooting the
system...". Since nothing happens I press CTRL-ALT-DEL
in order to try to reboot and then the message
"shutdown: warning: cannot open /var/run/shutdown.pid"
appears and the server doesn't continue. I actually
have to hold the power button for 4 sec to shutdown
the server.
I've reinstalled the server, logged in, then removed
the unused kernelmodule of the x306m raidcontroller
and then rebooted the server. Reboot works fine after
this. I would assume that a loaded kernelmodule that
is not in use, wouldn't cause such a problem.
Anybody who has an idea of what's going wrong?
Rgds,
Johan
Hello,
I am trying to build a custom boot cd that will use a static IP address to
connect to a HTTP installation source. I can get the boot cd to work with a
DHCP configuration, but no matter what I do I cannot get it to use a static
IP address.
Has anyone done this successfully? Any help or examples would be greatly
appreciated.
Thanks,
David Bellis
Hello list,
does autoyast support the initrd_module TAG?
This is in my xml file:
<initrd_modules config:type="list">
<initrd_module>
<module>ext3</module>
</initrd_module>
<initrd_module>
<module>forcedeth</module>
</initrd_module>
</initrd_modules>
But :
> cat /etc/sysconfig/kernel | grep INITRD
INITRD_MODULES="sis5513 sata_sis processor thermal fan reiserfs dm_mod"
does not contain them.
Testet on SuSE 10.1 beta8
regards,
Martin
Sorry, sp3, you're right.
As for the init-script. I added the debug line like you suggested and it's not
hitting that file.
I'm also teeing the output of my script to a file, and it's not getting created
either.
~Paul
-----Original Message-----
From: Uwe Gansert [mailto:ug@suse.de]
Sent: Thursday, March 30, 2006 7:07 AM
To: suse-autoinstall(a)suse.com
Subject: Re: [suse-autoinstall] init scripts
On Thursday 30 March 2006 01:17, discip(a)pjm.com wrote:
> I am using SLES9 sp5,
SP5 does not exist. SP3 is the latest one.
> my autoinstall.xml looks like this:
looks good.
> Has anyone else had any luck with this?
I'm sure init-scripts on SP3 are working without any problems. Add a line like
"touch /tmp/init_was_here" as first line to your init-script
to check if it has started.
> Do I need a different
> profile.dtd (can I get a newer one somewhere?)?
a new profile.dtd would not change anything.
--
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany
e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0,
Fax: +49-(0)911-74053-476, Web: http://www.suse.de
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
The documentation on Novell's website states that starting with SLES9, the
init-scripts tag is available.
http://forgeftp.novell.com/yast/doc/SL10.0/autoinstall/createprofile.script…
l#init.scripts
I am using SLES9 sp5, however, xmllint is not happy about the init-scripts tag
(surprise surprise) and the installer ignores it.
my autoinstall.xml looks like this:
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<configure>
<scripts>
<init-scripts config:type="list">
<script>
<source><![CDATA[
/root/fixSuSE 2>&1 | tee /root/fixSuSE.out
echo "SuSE Patched for US..."
sleep 5
]]>
</source>
</script>
</init-scripts>
</scripts>
...
Has anyone else had any luck with this? Do I need a different profile.dtd (can
I get a newer one somewhere?)?
Thanks,
Paul
I ran into a snag with using autoyast to get printers preconfigured
during installation. I took an already-configured SuSE 10 machine,
set up the printers as desired, and ran the Autoinstallation portion
of YaST to get a reference configuration file. I chopped out the
part where the printers were defined and grafted it into an already
existing autoyast file. Xmllint showed no problems with the syntax,
but no printers were defined on the computer that I autoinstalled.
Is there a problem with my methods?
I can supply the chunk of the autoyast file that had to do with
printing, if that helps.
Thanks in advance!
--
- Peter Schwenk
- CITA-3, Systems Administrator
- Mathematical Sciences
- University of Delaware
- (302) 831-0437
- schwenk _at_ udel _dot_ edu
- http://www.math.udel.edu/~schwenk
