I have a problem with automatic installation of SuSE Linux 8.1 and 8.2.
I need to select czech language but english (US) keyboard map. Generated
XML file contains
<keyboard>
<keymap>english-us</keymap>
</keyboard>
<language>cs_CZ</language>
but the system is installed with czech keyboard map anyway. Is there
a way to use czech language but english-US keyboard map?
Michal Kubecek
I wonder if there is a way to set up an automatic YOU-style update of the
packages to work with AutoYast. The idea is to keep the packages on the
install server as current as possible, thus shortening the cycle of
(1) install system with certain combination
(2) patching it via auto YOU from the central mirror to get it up to date
I would much rather update the non-critical stuff like desktop install sources
directly (I'd be more careful with server builds ;-). Having run Auto YOU
for over a year on a couple of test systems I have found the patch release
process and quality good enough to trust.
= P =
Hi Kurt,
I suggest you do two things:
1- in your info file change :
AutoYaST:ftp://autoinst.xml
to
AutoYaST:ftp://XX.XX.XX.XX/autoinst.xml
where XX.XX.XX.XX stands for the ftp server ip address.
2- You can either check dierctly by adding
AutoYaST=ftp://XX.XX.XX.XX/autoinst.xml in your current command line .
if your command line is; for example
kernel (nd)/linux install=nfs://192.168.0.59/home/suse82/ ip=192.168.0.230
netmask=255.255.255.0
change it to :
kernel (nd)/linux autoyast=ftp://XX.XX.XX.XX/autoinst.xml
install=nfs://192.168.0.59/home/suse82/ ip=192.168.0.230
netmask=255.255.255.0
where XX.XX.XX.XX stands for the ftp server ip address.
It works on my system.
Best regards,
Damien.
---------------------------------------------------------------
Damien Selles
Kurt Kronschnabl <k.kronschnabl(a)ica-intercom-akademie.de>
ica-intercom-akademie.de
29/08/2003 14:06
To:
suse-autoinstall(a)suse.com
cc:
Subject:
[suse-autoinstall] Placing autoinst.xml onto the nfs-server?
Hi all,
normally autoinst.xml resides on the floppy.
In the autoyast docu I found the description of the info file. There is
an entry which seems to describe the location of autoinst.xml file.
I tried to put a line in "info" (which resides in the root on the floppy):
AutoYaST:ftp://autoinst.xml
A ftp deamon (vsftpd) is running on the server which allows an anonymous
login. autoinst.xml will be presented in the ftp ano-root directory. I
assume that the same IP-Adress will be used as for the nfs-Server
because there is no field in the info file which allows me to provide a
separate ftp IP-Adresss.
When yast2 tried to locate the autoinst.xml file I get an interactive
dialog which offers me to choose several.
I can type in what I want (nfs, tftp) autoinst.xml will not be found.
nfs is running ok, otherwise yast2 will not go so far.
Who can help me please?
Regards, Kurt
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
Hi all,
normally autoinst.xml resides on the floppy.
In the autoyast docu I found the description of the info file. There is
an entry which seems to describe the location of autoinst.xml file.
I tried to put a line in "info" (which resides in the root on the floppy):
AutoYaST:ftp://autoinst.xml
A ftp deamon (vsftpd) is running on the server which allows an anonymous
login. autoinst.xml will be presented in the ftp ano-root directory. I
assume that the same IP-Adress will be used as for the nfs-Server
because there is no field in the info file which allows me to provide a
separate ftp IP-Adresss.
When yast2 tried to locate the autoinst.xml file I get an interactive
dialog which offers me to choose several.
I can type in what I want (nfs, tftp) autoinst.xml will not be found.
nfs is running ok, otherwise yast2 will not go so far.
Who can help me please?
Regards, Kurt
Dear list,
sorry if this question has been answered before, but I could not find any
real answer on the achives.
I have a SuSE 7.2 system and would like to upgrade to 8.2. Can I do this
"online" just using YaST or YaST2? I do not have physical access to the
system
which is why I cannot boot from the 8.2 CD and upgrade "offline".
Extra question: If this is not possible: What would be the difference
between updating or manually updating the kernel and updating all packages
via
YaST?
Torsten
Hi,
I've created a customised bootable cd that starts an autoyast installation
procedure.
Is it possible to update the kernel (image) that is used when booting from
the installation cd?
> Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards,
>
H.J. ten Berge
Test Engineer
HITT Traffic
Oude Apeldoornseweg 41-45
P.O. Box 717
NL-7300 AS, APELDOORN
The Netherlands
Telephone +31-55-543 26 34
Fax +31-55-543 25 53
E-mail mailto:berge@hitt.nl
Internet http://www.hitt-traffic.nl
cheers !
-----Message d'origine-----
De : Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de]
Envoyé : mercredi 27 août 2003 16:23
À : suse-autoinstall(a)suse.com
Objet : Re: [suse-autoinstall] textmode was: Re: partition problems with
AutoYast / boot pr oblems with Intel onboard pro/100 VE
I got it!!!
It's only nessecary to put a info fileon the grub floppy with the single
line "textmode:1", then it works: yast2 runs in ncursesmode!!
Thank you for all the input!
Regards, Kurt
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
Hi!
I'm using the current autoyast2 (2.7.19) on a SuSE 8.2 Professional system.
The problem I got is that the gfxmenu line for grub offered by autoyast2 is
syntactically wrong. It looks like
gfxmenu (hd0,5)hd0,5)/boot/message
^^^^^^
here's the error
The partition (hd0,5) itself is correct, but I can't think of any reason why
the redundant stuff, leading to a syntactically incorrect line, is in here.
Sure, I can click on "Booting" and manually edit the line so that it's
correct and gets included in the grub config of the installed system, but
that's kind of awkward. If I don't edit the line and instead leave it as it
is, it won't be included in the menu.lst file and I will thus have a textual
boot menu instead of the desired GUI one.
My question thus is: Why does this happen and how can I prevent it from
happening again during future autoyast2 install sessions?
Thanks in advance for any info/suggestions!
Below you'll find my autoinst.xml file which, apart from the issue
just mentioned, works flawlessly:
-----------------------------------------------------------------------
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "autoyast-dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
<configure>
<networking>
<dns>
<domain>local</domain>
<hostname>servunit</hostname>
</dns>
<interfaces config:type="list">
<interface>
<bootproto></bootproto>
<device>eth0</device>
<ipaddr>192.168.0.1</ipaddr>
<netmask>255.255.255.0</netmask>
<startmode>onboot</startmode>
</interface>
</interfaces>
<!--
<routing>
<routes config:type="list">
<route>
<destination></destination>
<device></device>
<gateway></gateway>
<netmask></netmask>
</route>
</routes>
</routing>
-->
</networking>
<!-- runlevels needs to be inserted here -->
<scripts>
<post-scripts config:type="list">
<script>
<filename>txspost.sh</filename>
<interpreter>shell</interpreter>
<source>
<![CDATA[
#!/bin/sh
# run txs support script
cd /opt/txs-support/install
./install.sh
# insserv aladdin
insserv /etc/init.d/aladdin
# mark device with MBR as bootable
sfdisk -A1 $(grep " / " /etc/fstab | awk '{print $1}' | sed 's/[0-9]//')
# reboot system
#reboot
]]>
</source>
</script>
</post-scripts>
</scripts>
<security>
<console_shutdown>ignore</console_shutdown>
<displaymanager_remote_access>yes</displaymanager_remote_access>
<gid_min>500</gid_min>
<kdm_shutdown>root</kdm_shutdown>
<passwd_use_cracklib>yes</passwd_use_cracklib>
<permission_security>easy</permission_security>
<run_updatedb_as>nobody</run_updatedb_as>
<uid_min>500</uid_min>
</security>
<users config:type="list">
<user>
<username>root</username>
<user_password>6efyaD43bst2Q</user_password>
<encrypted config:type="yes">true</encrypted>
</user>
</users>
<x11>
<color_depth config:type="integer">16</color_depth>
<configure_x11 config:type="boolean">true</configure_x11>
<display_manager>kdm</display_manager>
<enable_3d config:type="boolean">false</enable_3d>
<monitor>
<display>
<height config:type="integer">1024</height>
<max_hsync config:type="integer">80</max_hsync>
<max_vsync config:type="integer">75</max_vsync>
<min_hsync config:type="integer">31</min_hsync>
<min_vsync config:type="integer">50</min_vsync>
<width config:type="integer">1280</width>
</display>
<monitor_device>1280X1024@75HZ</monitor_device>
<monitor_vendor> VESA</monitor_vendor>
</monitor>
<resolution>1280x1024</resolution>
<start_x11 config:type="boolean">true</start_x11>
</x11>
</configure>
<install>
<bootloader>
<activate config:type="boolean">true</activate>
<location>mbr</location>
</bootloader>
<general>
<clock>
<hwclock>UTC</hwclock>
<timezone>Europe/Berlin</timezone>
</clock>
<keyboard>
<keymap>english-us</keymap>
</keyboard>
<language>en_US</language>
<mode>
<confirm config:type="boolean">true</confirm>
<forceboot config:type="boolean">false</forceboot>
<interactive_boot config:type="boolean">true</interactive_boot>
<reboot config:type="boolean">false</reboot>
</mode>
<mouse>
<id>probe</id>
</mouse>
</general>
<partitioning config:type="list">
<drive>
<device></device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<filesystem config:type="swap"></filesystem>
<format config:type="boolean">true</format>
<mount>swap</mount>
<size>auto</size>
</partition>
<partition>
<crypt_fs config:type="boolean">false</crypt_fs>
<crypt_key></crypt_key>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<mount>/</mount>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
<report>
<errors>
<log config:type="boolean">true</log>
<show config:type="boolean">true</show>
<timeout config:type="integer">10</timeout>
</errors>
<messages>
<log config:type="boolean">true</log>
<show config:type="boolean">true</show>
<timeout config:type="integer">10</timeout>
</messages>
<warnings>
<log config:type="boolean">true</log>
<show config:type="boolean">true</show>
<timeout config:type="">10</timeout>
</warnings>
</report>
<software>
<base>TXS</base>
<packages config:type="list">
<package>aladdin</package>
<package>txs-support</package>
</packages>
</software>
</install>
</profile>
-----------------------------------------------------------------------
Greetings,
Holger
I think the correct line is :
Textmode: 1
You have to put this line in the 'info' file on the floppy, whenever you use
it...
Antoine
-----Message d'origine-----
De : Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de]
Envoyé : mercredi, 27. août 2003 14:53
À : suse-autoinstall(a)suse.com
Objet : Re: [suse-autoinstall] partition problems with AutoYast / boot
pr oblems with Intel onboard pro/100 VE
Berge, Harry ten schrieb:
>
>
>>-----Original Message-----
>>From: Kurt Kronschnabl [mailto:k.kronschnabl@ica-intercom-akademie.de]
>>Sent: Wednesday, August 27, 2003 2:31 PM
>>To: suse-autoinstall(a)suse.com
>>Subject: Re: [suse-autoinstall] partition problems with
>>AutoYast / boot
>>pr oblems with Intel onboard pro/100 VE
>>
>>
>>
>>chapter 4.10, page 29 :-)
>
>>Succes!
>
>Perfect! The script is part of autoinst.xml All clear!
>
Perhaps you know another miracle: Where should I put the "textmode=1"
command for yast2 to avoid long X11 startup times? The manual (yes, I
read this section! :=)) explains to put it on the yast2 command line.
But I have no access to the command line.
Regards, Kurt
>
>
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
I got it!!!
It's only nessecary to put a info fileon the grub floppy with the single
line "textmode:1", then it works: yast2 runs in ncursesmode!!
Thank you for all the input!
Regards, Kurt