I have to make sure that users can not interrupt the auto installation.
I am hoping that someone can tell me the right way to do this or offer any
advice.
So far I have:
-disabled the abort button.
-added noshell=1 to the boot options.
-removed the reboot if crl-alt-del is pressed in inittab in the root image
(however, it will still reboot from tty3 or 4...which leads me to believe my
change is not doing anything)
my current remaining issues are that:
you can kill X with ctrl-alt-backspace and kill the installation
you can reboot with ctrl-alt-del on tty3 and 4 (I would prefer that these were
not even accessable...I tried removing the other tty*
from /etc/sysconfig/keyboard in the root image but it had no affect)
Thanks a lot for your time!
Lee Hartley
Hi,
I have a problem setting up autoyast with NLD9.
I have setup a NLD installation FTP server (ftp://192.168.0.195) running
SLES 9. Files from the NLD CDs copied over and setup accordingly. I have
also verified that the manual FTP installation works.
Thereafter I create a autoinst.xml file (as attached) from the Autoyast
in the NLD client and put in under ftp://192.168.0.195/autoinst.xml with
read permissions to all.
Next I try an autoinstallation using the following steps:
1) Boot from NLD Installation Disk 1
2) Choose Installation
3) Add in the options "autoyast=ftp://192.168.0.195/autoinst.xml
install=ftp://192.168.0.195"
4) The graphical YaST interface loads and indicates it is starting
Autoinstallation.
5) However, at the step where it reads the autoinst.xml, it throws an
error saying that the profile for this machine cannot be found and ask
me for a new location.
Does anyone have a clue what happened?
Thanks in advance.
Cheers
Onn Chee
Hi,
I'm making a autoinst.xml with SUSE 9.3.
1) I found out that some packages are missing from the SUSE CDs (eg.
phpMyAdmin), but they exist on the SUSE site and mirror. Anyone knows
why?
2) I configure a share in the samba server area, do a save to file and
the only thing that is saved is a line with "<samba-server/>". Where did
all the samba config go?
Any 1?
Andre
Just tried the SLES9 SP2 CD for booting. It ignores netsetup=1 and always
tries to configure network using dhcp. it's the same when using hostip and
gateway instead. Can anybody confirm this? linuxrc broken? What else can I
do to start autoinstall from the SP2 CD needing manual network
configuration?
Regards
--
Stephan Dühr
dass IT GmbH
http://www.dass-IT.de
Hi
This is a little different query from that posted by Hans Deragon (http://lists.suse.com/archive/suse-autoinstall/2004-May/0056.html ).
By default, sles9 autoinstallation uses dhcpcd client, how do i configure autoinstall to use dhclient if the installation server is not SuSe (e.g fedora or debian etc) ? please note that the " DHCLIENT_BIN variable in /etc/sysconfig/network/dhcp" applies only if the installation server is a SuSe distribution.
any comments/direction is greatly appreciated.
thanks in advance
kanji
---------------------------------
Sell on Yahoo! Auctions - No fees. Bid on great items.
Hi All,
I'm still having the problem described below... someone already have a
sucessfully SLES9 CD customization where YOU functions without any problem???
Please, any tip will be apreciated...
Regards,
Fabiano Felix
---------- Mensagem reenviada ----------
Subject: [suse-autoinstall] Problems with YOU using a SLES9 Custom CD
Date: Seg 27 Jun 2005 10:38
From: Fabiano Felix <felix(a)getnet.com.br>
To: suse-autoinstall(a)suse.com
Hi All,
I make a Custom CD using SLES9, where I create new package description using
only my package selection. I also updated kernel image that is used at
installation process, using the same that are at SP1.
All process works fine, and all services functions without any problem...
but, when I try to do an On-line Update, I only can see SUSE-SLES packages.
The most important packages are at SUSE-CORE selection (probably an
inheritance from UnitedLinux CD's model...).
I tried to add this update option using YaST2 (and copying from a "normal"
SLES9 install), but I can't have success...
Two questions:
- Someone has some idea to correct this?
- What's the best form to customize SLES9 CD's and don't have this problem
again? (I believe that it have some relation with "media.N", "yast dir at CD
root" and "contents" file...)
With best regards,
Fabiano Felix
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
-------------------------------------------------------
hello,
i know this has been addressed on the list in the past but it just
doesn't seem to work.
in autoyast on suse 9.1 or 9.3 when i go into the partitioning section
there are no drives defigned. when i select "add partition" i get the
"select a drive first" dialog. so i add a drive, zero out the device
entry and select initialize drive. i then go about adding partitions and
i save the config. when i boot the machine it gets to the partitioning
section and fails.
if anyone actually has partioning with specifying a drive working i'd
really appreciate if you'd post the section.
this is the partioning section from the xml config.
<partitioning config:type="list">
<drive>
<device></device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/</mount>
<partition_id config:type="integer">131</partition_id>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">ext2</filesystem>
<filesystem_id config:type="integer">131</filesystem_id>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/boot</mount>
<partition_id config:type="integer">131</partition_id>
<partition_type>primary</partition_type>
<size config:type="integer">67108864</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/usr</mount>
<partition_id config:type="integer">131</partition_id>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/var</mount>
<partition_id config:type="integer">131</partition_id>
<partition_type>primary</partition_type>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/srv</mount>
<partition_id config:type="integer">131</partition_id>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>swap</mount>
<partition_id config:type="integer">130</partition_id>
<size config:type="integer">653262848</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
--
Darin Perusich
Unix Systems Administrator
Cognigen Corp.
darinper(a)cognigencorp.com
Hi Darin,
Try erasing the "<device></device>" line.
André Assis Guimarães
-----Original Message-----
From: Darin Perusich [mailto:Darin.Perusich@cognigencorp.com]
Sent: segunda-feira, 11 de Julho de 2005 14:54
To: suse-autoinstall(a)suse.com
Subject: [suse-autoinstall] partitioning without device specification
hello,
i know this has been addressed on the list in the past but it just doesn't seem to work.
in autoyast on suse 9.1 or 9.3 when i go into the partitioning section there are no drives defigned. when i select "add partition" i get the "select a drive first" dialog. so i add a drive, zero out the device entry and select initialize drive. i then go about adding partitions and i save the config. when i boot the machine it gets to the partitioning section and fails.
if anyone actually has partioning with specifying a drive working i'd really appreciate if you'd post the section.
this is the partioning section from the xml config.
<partitioning config:type="list">
<drive>
<device></device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/</mount>
<partition_id config:type="integer">131</partition_id>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">ext2</filesystem>
<filesystem_id config:type="integer">131</filesystem_id>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/boot</mount>
<partition_id config:type="integer">131</partition_id>
<partition_type>primary</partition_type>
<size config:type="integer">67108864</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/usr</mount>
<partition_id config:type="integer">131</partition_id>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/var</mount>
<partition_id config:type="integer">131</partition_id>
<partition_type>primary</partition_type>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>/srv</mount>
<partition_id config:type="integer">131</partition_id>
<size config:type="integer">2147483648</size>
</partition>
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<mount>swap</mount>
<partition_id config:type="integer">130</partition_id>
<size config:type="integer">653262848</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
--
Darin Perusich
Unix Systems Administrator
Cognigen Corp.
darinper(a)cognigencorp.com
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
Hello, all
The FTP option is offered in the installation profile dialog, but has no effect.
The following patch works for me, maybe it can be fixed in the next SP, or
anyone else can use it.
Oliver
--- /usr/share/YaST2/include/autoinstall/profileDialogs.ycp 2005-02-03 18:56:58.000000000 +0100
+++ /tmp/cramfs/linux/UnitedLinux/i386-ul1/y2update/include/autoinstall/profileDialogs.ycp 2005-06-30 16:12:36.000000000 +0200
@@ -86,6 +86,7 @@
protocol == "nfs" ||
protocol == "tftp" ||
protocol == "http" ||
+ protocol == "ftp" ||
protocol == "device"
)
{
Hello,
I got an sel-file and suse 9.3.
Is it possible to tell yast to install/uninstall the packages on an
existing installation according to this sel-File?
I could run
yast sw_single
to go directly to the software module.
But I also would like to automate the choosing of the sel-file.
Any ideas?
Best regards
Cornelius