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
Hello,
I think there is a typo in AutoInstallRules.ycp (version 1.34.4.9
that comes with SLES9 SP2): the xsltproc to merge classes is called
with the following param there (line 733):
--param dontmerge \"'package, addon'\"
and I'm quite sure that it sould be:
--param dontmerge \"'package'\" --param dontmerge2 \"'addon'\"
The result of this typo is that neither <package> nor <addon> are
correctly aggregated, which is the desired effect I believe and I
also hope.
Quick demonstration:
idhpb02:/ # cat /tmp/a.xml
<?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">
<install>
<software>
<addons config:type="list">
<addon>addon-A</addon>
</addons>
<packages config:type="list">
<package>package-A</package>
</packages>
</software>
</install>
</profile>
idhpb02:/ # cat /tmp/b.xml
<?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">
<install>
<software>
<addons config:type="list">
<addon>addon-B</addon>
</addons>
<packages config:type="list">
<package>package-B</package>
</packages>
</software>
</install>
</profile>
Calling it the wrong way:
idhpb02:/ # xsltproc --novalid --param replace "'false'" --param
dontmerge "'package, addon'" --param with "'/tmp/b.xml'" /usr/share/
autoinstall/xslt/merge.xslt /tmp/a.xml
<?xml version="1.0"?>
<ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns" xmlns="http://
www.suse.com/1.0/yast2ns">
<ns1:install>
<ns1:software>
<ns1:addons config:type="list">
<ns1:addon>addon-B</ns1:addon>
</ns1:addons>
<ns1:packages config:type="list">
<ns1:package>package-B</ns1:package>
</ns1:packages>
</ns1:software>
</ns1:install>
</ns1:profile>
Calling it the (as I think) right way:
idhpb02:/ # xsltproc --novalid --param replace "'false'" --param
dontmerge "'package'" --param dontmerge2 "'addon'" --param with "'/
tmp/b.xml'" /usr/share/autoinstall/xslt/merge.xslt /tmp/a.xml
<?xml version="1.0"?>
<ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns" xmlns="http://
www.suse.com/1.0/yast2ns">
<ns1:install>
<ns1:software>
<ns1:addons config:type="list">
<ns1:addon>addon-A</ns1:addon><ns1:addon>addon-B</ns1:addon>
</ns1:addons>
<ns1:packages config:type="list">
<ns1:package>package-A</ns1:package><ns1:package>package-B</
ns1:package>
</ns1:packages>
</ns1:software>
</ns1:install>
</ns1:profile>
Could this be fixed? Or is it already known and possibly a workaround
in existance?
Thanks in advance,
-Luzian
Anyone have a link to docs or an explanation of what I need to do to
deploy SP3 onto an existing install server layout, assuming I need to do
this by hand, and cannot use YaST2 (since the server is a different
platform altogether)?
I assume that simply replacing CD1 with the SP3 CD1 is incorrect...
--
cg
narrowed the issue down to: alsasound is not started on boot.
If I do that manually, sound works for root as the permssions require a
normal user to be part of the audio group.
I set the permissions on /dev/snd/* to a+rw with a script as I have
22000 potential users that I can not all add to the audio group.
-----Original Message-----
From: Uwe Gansert [mailto:ug@suse.de]
Sent: donderdag 26 januari 2006 15:45
To: suse-autoinstall(a)suse.com
Subject: Re: [suse-autoinstall] Auto detection of sound card in 10.0 ?
On Thursday 26 January 2006 10:50, Frank van Tol wrote:
> I can not get the autodetect working with suse 10.0 to produce sound
> in gnome/kde.
seems to be hardware related because it's working here.
--
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
Hi,
this is just for your information. SUSE Linux 10.1 beta2 is ready.
Feel free to download it:
http://www.opensuse.org/Development_Version
A list of changes in autoyast can be found here:
http://www.suse.de/~ug/autoyast_changes.html
The last three changes:
* one can clone a system more than one time now with the UI
* proof readed texts for the UI (thanx Rebecca)
* pre, chroot and post scripts can show feedback now in a popup
will be available in beta3, not in the current beta2
--
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
# From: Colin Topliss [mailto:Colin.Topliss@three.co.uk]
# Sent: Thursday, January 26, 2006 9:24 AM
# To: Uwe Gansert; suse-autoinstall(a)suse.com
# Subject: RE: [suse-autoinstall] SPAM: Partioning problems, SLES9 RC5.....SOLVED!
#
# Hi Uwe,
#
# It was a cut'n'paste problem.....
#
# However, I had a blinding inspiration.......
#
# I was playing with some rules a while ago, and I had two files still in
# the rules directory. The install appears to pick these files up (not
# sure which one, had one called cciss_36.xml and one called rules.xml).
# Moved them out, tried again and it worked!
#
# These rules were there from testing with SuSE 9.2 (which never did show
# this particular problem).
See the documentation regarding "rules.xml":
http://forgeftp.novell.com///yast/doc/SL10.0/autoinstall/rulesandclass.html
Hi Uwe,
It was a cut'n'paste problem.....
However, I had a blinding inspiration.......
I was playing with some rules a while ago, and I had two files still in
the rules directory. The install appears to pick these files up (not
sure which one, had one called cciss_36.xml and one called rules.xml).
Moved them out, tried again and it worked!
These rules were there from testing with SuSE 9.2 (which never did show
this particular problem).
Thanks for taking the time to look at this.
Colin.
-----Original Message-----
From: Uwe Gansert [mailto:ug@suse.de]
Sent: 26 January 2006 15:48
To: suse-autoinstall(a)suse.com
Subject: Re: [suse-autoinstall] SPAM: Partioning problems, SLES9
RC5.....
On Thursday 26 January 2006 16:39, Colin Topliss wrote:
> The partition part is as follows:
>
> <partitioning config:type="list">
> <drive>
> <device>/dev/cciss/c0d0</device>
> <partitions config:type="list">
> <partition>
> <filesystem config:type="symbol">reiser</filesystem>
> <format config:type="boolean">true</format>
> <mount>/boot</mount>
> <partition_id config:type="integer">131</partition_id>
> <partition_nr config:type="integer">1</partition_nr>
> <size>300mb</size>
> </partition>
> <partition>
> <filesystem config:type="symbol">swap</filesystem>
> <format config:type="boolean">true</format>
> <mount>swap</mount>
> <partition_id config:type="integer">130</partition_id>
> <partition_nr config:type="integer">2</partition_nr>
> <size>4gb</size>
> </partition>
> <partition>
> <partition_id config:type="integer">15</partition_id>
> <partition_nr config:type="integer">3</partition_nr>
> <size>max</size>
> </partition>
drop the partition above from the profile. Don't configure the extended
partition.
> <partition>
> <filesystem config:type="symbol">reiser</filesystem>
> <format config:type="boolean">true</format>
> <mount>/</mount>
> <partition_id config:type="integer">131</partition_id>
> <partition_nr config:type="integer">5</partition_nr>
> <size>1gb</size>
> </partition>
> <partition>
> <filesystem config:type="symbol">reiser</filesystem>
> <format config:type="boolean">true</format>
> <mount>/home</mount>
> <partition_id config:type="integer">131</partition_id>
> <partition_nr config:type="integer">6</partition_nr>
> <size>300mb</size>
> </partition>
> <partition>
> <partition>
why two times "partiton"? copy and paste bug?
> Can anyone see anything obvious I'm missing?
that's all I saw by quickly browsing your data. Fix that and if that
does not help, post your complete profile.
--
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
________________________________________________________________________
This e-mail message (including any attachment) is intended only for the personal
use of the recipient(s) named above. This message is confidential and may be
legally privileged. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error, please notify
us immediately by e-mail and delete the original message.
Any views or opinions expressed in this message are those of the author only.
Furthermore, this message (including any attachment) does not create any legally
binding rights or obligations whatsoever, which may only be created by the exchange
of hard copy documents signed by a duly authorised representative of Hutchison
3G UK Limited..
________________________________________________________________________
Hi all,
I have a problem with partitioning under SLES9, x86_64 (on a DL380-G4).
I'm using a SLES9 RC5 disk to boot from, then I am attempting an install
via an http server.
The install fails when trying to set up the partition plan (an error
occurred while trying to create the partitioning plans. Make sure the
control file has the correct syntax and values) - trouble is it doesn't
appear to indicate why (or else I'm not looking for the info in the
correct place). I certainly couldn't see anything obvious in the y2log.
The partition part is as follows:
<partitioning config:type="list">
<drive>
<device>/dev/cciss/c0d0</device>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/boot</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">1</partition_nr>
<size>300mb</size>
</partition>
<partition>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<mount>swap</mount>
<partition_id config:type="integer">130</partition_id>
<partition_nr config:type="integer">2</partition_nr>
<size>4gb</size>
</partition>
<partition>
<partition_id config:type="integer">15</partition_id>
<partition_nr config:type="integer">3</partition_nr>
<size>max</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">5</partition_nr>
<size>1gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/home</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">6</partition_nr>
<size>300mb</size>
</partition>
<partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/opt</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">7</partition_nr>
<size>2gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/tmp</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">8</partition_nr>
<size>1gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/usr</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">9</partition_nr>
<size>3gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/var</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">10</partition_nr>
<size>2gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/var/opt</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">11</partition_nr>
<size>1gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/var/log</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">12</partition_nr>
<size>1gb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/var/tmp</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">13</partition_nr>
<size>1gb</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
I also tried to use a profile created by yast autoyast - but I get the
same error. I even tried a minimal partition definition - and got the
same error. I tried different combinations of syntax from the AutoYaST
guides with no success. No matter what I try I get this partition error.
Its driving me crazy!
Xmllint isn't showing up any problems with the profile in general.
Can anyone see anything obvious I'm missing? Or has anyone got a working
example? If not, I'm facing the possibility of an error elsewhere in the
(rather long) config :-(
Thanks.
Colin Topliss
________________________________________________________________________
This e-mail message (including any attachment) is intended only for the personal
use of the recipient(s) named above. This message is confidential and may be
legally privileged. If you are not an intended recipient, you may not review, copy or
distribute this message. If you have received this communication in error, please notify
us immediately by e-mail and delete the original message.
Any views or opinions expressed in this message are those of the author only.
Furthermore, this message (including any attachment) does not create any legally
binding rights or obligations whatsoever, which may only be created by the exchange
of hard copy documents signed by a duly authorised representative of Hutchison
3G UK Limited..
________________________________________________________________________
After I made some changes, not related at all to display etc, autoyast
starts of with the normal graphical install, showing the slides etc but
after the reboot, phase 2 is suddenly in text mode.
It still installs as before but I can't figure out why it changed it's
behaviour ? What determines which installer UI you get ?
Happy to attach autoyast.xml if that helps..
Best regards
Frank
I can not get the autodetect working with suse 10.0 to produce sound in
gnome/kde.
Tried this without success.
<configure>
...
<sound>
<autoinstall config:type="boolean">true</autoinstall>
<configure_detected
config:type="boolean">true</configure_detected>
</sound>
...
</configure>
However,
Yast sound add and yast sound playtest work just fine.