August 2002 - openSUSE Autoinstall - openSUSE Mailing Lists

REDUCING THE INSTALLATION DISKS
by Menkhoff, Malte 03 Sep '02

03 Sep '02

dear anas nashif, during my installation over net via nfs i have to use three disks [boot-disk, modules_1, modules_3]. is there any possibility to reduce to two disks or one cdrom? have you an idea to realise this facility? Mit freundlichen Grüßen Malte Menkhoff mailto:malte.menkhoff@telekom.de

5 5

ldap client problem
by Christian Stoltze 02 Sep '02

02 Sep '02

Hello, I want to use the ldap client feature during an automatic installation but nothing happens. Here are my config settings: <configure> ... <ldap> <ldap_domain>dc=inf,dc=uni-konstanz,dc=de</ldap_domain> <ldap_server>134.34.57.71</ldap_server> <ldap_v2 config:type="boolean" >false</ldap_v2> <start_ldap config:type="boolean" >true</start_ldap> </ldap> ... </configure> After the installation the files /etc/nsswitch.conf /etc/openldap/ldap.conf /etc/security/pam_unix2.conf are not prepared for ldap-client functionality. If I run "yast2 ldap_client" manually after the installation then I succeed in setting up a ldap client. Of course, I can write a shell script and put it in the <post-scripts> section, but I would rather use the ldap feature <ldap>. Regards Christian -- Christian Stoltze Computer Science, University of Constance (Lake Constance/SW-Germany) Email: Christian.Stoltze(a)uni-konstanz.de Voice: +49 (0)7531 88-4448 Fax: +49 (0)7531 88-3577

2 2

Suggestion for documentation change section 2.6.1
by Eric Whiting 29 Aug '02

29 Aug '02

http://www.suse.de/~nashif/autoinstall/autoyast2/x109.html Section 2.6.1 mentions: >Repeat this sequence for all other CDs. The directory can have 2 different >structures which can be used for installation: If I understand correctly these are the 2 methods: #1) copy all CDs to one dir and patch a .pkd file. #2) copy all CDs to different dirs I'd like to see added a third choice: #3) copy the DVD to one dir I like #3 because you don't have to patch the pkd file and you don't swap CDs as much. eric

1 0

interactive query in autoinstallation
by Menkhoff, Malte 29 Aug '02

29 Aug '02

dear anas nashif, after the installation of the new rpm of the yast2-module-autoinstall the creation of an extended partition was successfull. but after the package update and the modification of my inst-sys there will "blink" an interactive query during the installation process. the possibolities of answer are yes and no in an green window. can you give me an option to bear down this "pop-up"-window??? Mit freundlichen Grüßen Malte Menkhoff mailto:malte.menkhoff@telekom.de

2 1

RE: [suse-autoinstall] Yast Online Update
by Richard Bos 29 Aug '02

29 Aug '02

>===== Original Message From Kevin Ivory <Ivory(a)SerNet.de> ===== >Richard Bos wrote: >> For your information mozilla 1.1 is available via the Advanced Package Tool >> (APT) for SuSE. More about apt at http://linux01.gwdg.de/apt4rpm. > >Thank you for the interesting reply. You might want to send it >to the list as well. > >Kevin As adviced by Kevin, here it goes: For your information mozilla 1.1 is available via the Advanced Package Tool (APT) for SuSE. More about apt at http://linux01.gwdg.de/apt4rpm. Mozilla-1.1 must be obtained from a temporarely apt repository which can be accessed with the following uri in the sources.lsi file: rpm http://linux01.gwdg.de/apt4rpm/apt SuSE/8.0/i386 unstable -- Richard Bos -- Dit bericht is verzonden met Webmail van Freeler. Ook snel en betrouwbaar toegang tot internet? Meld je aan op http://www.freeler.nl

1 0

Yast Online Update
by Kai Hauser 29 Aug '02

29 Aug '02

Hello, I wonder why YOU in Suse8 doesn't list Mozilla 1.1 as update. There are only some updates for the 0.9.8 version. I tried to find out on the suse-website which Programms YOU updates but I couldn't find a answer. Mozilla is only a example, there are many other programms with newer versions released but YOU doesn't seem know about them. greetings Kai

3 2

Full stop! - route
by Marcel Ritter 27 Aug '02

27 Aug '02

Hi again! Please ignore my last mail (at least the part concerning the route problem). I got another machine (with a different setup) and there it works fine - so I guess my config file is broken somewhere ... Thanx anyway! Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

1 1

RE: [suse-autoinstall] applying patches
by Kugelberg, Thorsten 27 Aug '02

27 Aug '02

Hello, I do not want to criticise your script, but: No only one little thing, to have the same sytax as the file on the DVD I just turned requires="$requires $req" into requires="$req $requires" and provides="$provides $prov" into provides="$prov $provides" Another thing I was wondering about, If there are two entries called aaa-base, which one is installed? Or are both installed? Reason for my question: There is always an entry for the foo.rpm and for foo.src.rpm with the entry RpmName: foo Wouldn`t it be better do change 'for pkg in `find $ser -name "*.rpm"`; do' to something like 'for pkg in `find $ser -name "*.rpm" | grep -v "src.rpm"` to ger rid of the SRCRPMs? Just thinking... Regards Thorsten -----Original Message----- From: Anas Nashif To: Kugelberg, Thorsten Cc: suse-autoinstall(a)suse.com Sent: 26.08.2002 18:40 Subject: Re: [suse-autoinstall] applying patches * Kugelberg, Thorsten <thorsten.kugelberg(a)realtech.de> [Aug 26. 2002 18:29]: > Hello, > > the script is nice, beside one little error: > There is no dir called "inst-sys" inside the suse directory... > so I changed it to setup/descr Well, this was my configuration :-) Anas -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

2 1

Re: [suse-autoinstall] LILO problems (still)
by Marcel Ritter 27 Aug '02

27 Aug '02

> On Mon, 2002-08-26 at 06:32, Marcel Ritter wrote: > > On Mon, 19 Aug 2002, Anas Nashif wrote: > > > > > Hope you can help. > > > Please try this patch which should be applied to > usr/lib/YaST2/modules/Boot.ycp > > > Let me know if it works for you! Yes it does! Thanx! > Regards, > Anas But I still got a little problem :-) I remember a posting - quite some time ago - about AutoYaST failing to set the (default) route. I'm running into the same problem now (and yes, I am using the updated yast network package). I'm trying to use AutoYaST in a completely DHCP free environment. Works fine so far - the only problem is, that the route settings are being ignored. It'd be no great deal to build the /etc/sysconfig/network/routes file in a script, but I guess this is a standard feature and it'd be nice if it worked without extra hacking ... Config seems to be passed quite fine: "routing":[$["destination":"default", "device":"-", "gateway":"192.168.0.1", "netmask":"-"]]] Any ideas? Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

1 0

LILO problems (still)
by Marcel Ritter 26 Aug '02

26 Aug '02

On Mon, 19 Aug 2002, Anas Nashif wrote: > * Marcel Ritter <Marcel.Ritter(a)rrze.uni-erlangen.de> [Aug 19. 2002 13:10]: > > Hi again! > > > > By adding a separate /boot partition the situation inproves. > > (lilo is installed), however the install location (I specified "mbr" here) > > was ignored (Yast had chosen "hda5" instead). > > > > So I changed "mbr" do "hda" and it worked... > > > > ... I think there's still some work to do - and some documentation to > > write :-) > > The autoyast2 documentation is not a replacement for other > documentation. The issue with the /boot partition is described > elsewhere. The autoyast2 documentation does not cover these topics, as > it is part of the general installation also. It may be necessary/useful to add a boot partition, however my problems cannot be solved by adding /boot (I tried). The problem seems to be related to the updated module yast2-module-autoinst-2.5.27-0 (hope this one is the latest). I tried the same setup with the original install filesystem (suse/images/root) and it works fine. As soon as I replace yast2-module-autoinst I can't get my system to reboot: I always end up with some LILO error message (currently LI, but I've seen other, too) Partitioning: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key/> <filesystem config:type="symbol">ext2</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/boot</mount> <size>50</size> <type>Linux native</type> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key/> <filesystem config:type="symbol">swap</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount/> <size>512</size> <type>Linux native</type> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key/> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/</mount> <size>max</size> <type>Linux native</type> </partition> </partitions> <use>all</use> </drive> </partitioning> Bootmanager: <bootloader> <activate config:type="boolean">false</activate> <linear config:type="boolean">false</linear> <parameters/> </bootloader> If I got it right, the problem lies in the call to /usr/lib/YaST2/bin/dolilo: According to y2log in the original version '/usr/lib/YaST2/bin/dolilo / -m /dev/sda -a /dev/sda1' is called. The same setup with the newer packages calls '/usr/lib/YaST2/bin/dolilo / -m ' The option -m should be followed by the boot device if I got the comments in dolilo right. Doesn't seem to work with the new code ... I tried to attach the according y2log files but they exceeded the 20000 byte limit on this mailing list. If you'd like to have them simply tell me ... Hope you can help. Ciao, Marcel > Anas > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

1 1

RE: [suse-autoinstall] applying patches
by Kugelberg, Thorsten 26 Aug '02

26 Aug '02

Hello, the script is nice, beside one little error: There is no dir called "inst-sys" inside the suse directory... so I changed it to setup/descr Regards Thorsten -----Original Message----- From: Anas Nashif To: Kugelberg, Thorsten Cc: suse-autoinstall(a)suse.com Sent: 26.08.2002 17:13 Subject: Re: [suse-autoinstall] applying patches * Kugelberg, Thorsten <thorsten.kugelberg(a)realtech.de> [Aug 26. 2002 17:01]: > Hello, > > is it also possible to install the updated packages from the beginning (without update)? Anything is possible... But this requires either a dirty workaround or a complete recreation of the package database avail. on the CDs. 1. dirty hack: Just overwrite the old packages with the new ones 2. create a new common.pkd (suse/setup/descr/common.pkd) This is a simple text based database which contains data from the packages. Using a simple shell script which queries the RPM package will do the job. I once written a script like that, not sure how compatible with current format though (http://www.suse.de/~nashif/makeCommon.sh which should be available online in 1 hour approx.) Anas > > All the systems I am installing via autoyast, are freshly installed once a week. So if I could just copy the updated rpms into the installation directory that would be the best way! > In case of using YOU it would take quite a long time to install all the packages and update them afterwards... > > Regards > Thorsten > > -----Original Message----- > From: Anas Nashif > To: ralonso(a)lis.state.oh.us > Cc: suse-autoinstall(a)suse.com > Sent: 21.08.2002 13:48 > Subject: Re: [suse-autoinstall] applying patches > > * ralonso(a)lis.state.oh.us <ralonso(a)lis.state.oh.us> [Aug 20. 2002 > 23:17]: > > I'd like to have the machines I build with autoyast to have the latest > > patches already applied. Obviously, I don't want to have to run > Online > > Update on each machine manually. Does anyone know of a way to apply > the > > patch rpms automatically? > > I have a a directory tree under /var/lib/YaST/patches/i386/update/8.0 > with > > all the patches for 8.0. Is there a way to use this directory to > patch the > > machines instead of running YOU on each? > > Please take a look at both these articles: > > http://sdb.suse.de/en/sdb/html/mlasars_yousync.html > http://sdb.suse.de/en/sdb/html/yast2_ncurses.html > > Regards, > Anas > > > > Thanks, > > Robert > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

2 1

RE: [suse-autoinstall] applying patches
by Kugelberg, Thorsten 26 Aug '02

26 Aug '02

Hello, is it also possible to install the updated packages from the beginning (without update)? All the systems I am installing via autoyast, are freshly installed once a week. So if I could just copy the updated rpms into the installation directory that would be the best way! In case of using YOU it would take quite a long time to install all the packages and update them afterwards... Regards Thorsten -----Original Message----- From: Anas Nashif To: ralonso(a)lis.state.oh.us Cc: suse-autoinstall(a)suse.com Sent: 21.08.2002 13:48 Subject: Re: [suse-autoinstall] applying patches * ralonso(a)lis.state.oh.us <ralonso(a)lis.state.oh.us> [Aug 20. 2002 23:17]: > I'd like to have the machines I build with autoyast to have the latest > patches already applied. Obviously, I don't want to have to run Online > Update on each machine manually. Does anyone know of a way to apply the > patch rpms automatically? > I have a a directory tree under /var/lib/YaST/patches/i386/update/8.0 with > all the patches for 8.0. Is there a way to use this directory to patch the > machines instead of running YOU on each? Please take a look at both these articles: http://sdb.suse.de/en/sdb/html/mlasars_yousync.html http://sdb.suse.de/en/sdb/html/yast2_ncurses.html Regards, Anas > > Thanks, > Robert > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

cannot find info-file
by Menkhoff, Malte 23 Aug '02

23 Aug '02

hi anas! i´m trying to install suse 8.0 via autoyast and a bootdisk. cause of techn. reasons it´s not possible zo use dhcp or bootp. the howto gives me the information that i have to create an info-file where infos `bout ip, nameserver, and so on will be given for the mini linux. but by every test the system found not the info-file. i named it info. what can i do to boot over disk with my info-file without dhcp or bootb? malte menkhoff

3 2

applying patches
by ralonso＠lis.state.oh.us 21 Aug '02

21 Aug '02

I'd like to have the machines I build with autoyast to have the latest patches already applied. Obviously, I don't want to have to run Online Update on each machine manually. Does anyone know of a way to apply the patch rpms automatically? I have a a directory tree under /var/lib/YaST/patches/i386/update/8.0 with all the patches for 8.0. Is there a way to use this directory to patch the machines instead of running YOU on each? Thanks, Robert

3 2

AW: [suse-autoinstall] Modprobe for NIC's
by Kugelberg, Thorsten 20 Aug '02

20 Aug '02

Hello, well, since I stopped the service hotplug, the "Plug&Pray Manager" was gone! To get rid of the "Welcome Window" I configured the desktop like it should be, disabled the Welcome Message, and did everything for a my user. Then I made a tar archive of the Home-Directory and copied it to /etc. Now every time the X-Server starts, I untar the archive. This has the advantage, that after every login, the Desktop is initial again. This is done by editing the file /etc/X11/xdm/Xsetup . As is for an Internet Cafe Workststion, it is pretty nice and very useful!!! Regards Thorsten -----Ursprüngliche Nachricht----- Von: Marc Peter [mailto:marc.peter@avitech.de] Gesendet: Dienstag, 20. August 2002 09:12 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Modprobe for NIC's hi, i have succesfully made a custom cd with only needed packages. Is there a way to make a automatic configuration of the NIC maybe with "modeprobe" or "autoprobe". another question, how can i prevent on first login the "welcome window" and "pnp manager" to configure the NIC again. greetings marc -- ************************************************* Avitech Aviation Management Technologies GmbH Marc Peter Bahnhofplatz 1 D-88045 Friedrichshafen Phone: +49 7541/282-451 Fax: +49 7541/282-199 mailto:marc.peter@avitech.de ************************************************* -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Modprobe for NIC's
by Marc Peter 20 Aug '02

20 Aug '02

hi, i have succesfully made a custom cd with only needed packages. Is there a way to make a automatic configuration of the NIC maybe with "modeprobe" or "autoprobe". another question, how can i prevent on first login the "welcome window" and "pnp manager" to configure the NIC again. greetings marc -- ************************************************* Avitech Aviation Management Technologies GmbH Marc Peter Bahnhofplatz 1 D-88045 Friedrichshafen Phone: +49 7541/282-451 Fax: +49 7541/282-199 mailto:marc.peter@avitech.de *************************************************

1 0

Re: [suse-autoinstall] LILO problems
by Marcel Ritter 19 Aug '02

19 Aug '02

> Hi Marcel. > > I'm a newbie and had this problem (01 01 01...). I got around it by > placing a /boot partition (1 cyl, 10Mb) on the primary HD and the rest > on the second HD. > > Hope this helps. Thanx - this could indeed be the problem. Other machines had a separate /boot partition and installed fine. The affected setup has no /boot entry. Anyhow - I think this is either a bug in the lilo configuration or it should be mentioned somewhere that you need to have a /boot partition to make lilo work. Ciao, Marcel > Graham > > On 15 Aug 2002 at 11:15, Marcel Ritter wrote: > > > And once again problems ... > > > > ... this time it's the bootloader. > > > > YaST2 seems to have problems if the install uses non-standard partitioning > > setups (such as installation on the second harddisk, or preserving an > > existing partition). At least I got this impression as it worked ok on all > > Systems with one "all Linux" harddisk. > > > > Now I only get things like > > > > LIL- > > or > > 01010101010101...(forever) > > or > > 08080808080808...(forever) > > > > and the lilo.conf is not based on the setup on my autoyast.xml > > > > I'd like to use a template or whatever to make things work. > > > > Perhaps there's even some option I could try, but unfortunately the > > docs are neither consistent nor up-to-date: > > > > According to "profile.elem.bootloader.html" bootloader only contains: > > (activate,linear,location,parameters), but in the example section there > > are several other things mentioned: > > > > <bootloader> > > <write_bootloader>true</write_bootloader> > > <location>mbr</location> > > <linear>false</linear> > > <lba_support>false</lba_support> > > <activate>true</activate> > > <kernel_parameters></kernel_parameters> > > <initrd_modules config:type="list" > > > <module>+++some kernel module name+++</module> > > </initrd_modules> > > </bootloader> > > > > I'd appreciate any hints and I'd be especially happy about a complete and > > up-do-date description of the available options. > > > > Ciao, > > Marcel > > > > ---- > > Marcel Ritter > > Linux Betreuer > > Regionales Rechenzentrum Erlangen > > ---- > > Unix _IS_ user friendly... It's just selective about who its friends are. > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

2 2

Install with various NIC's = Problem
by Alexander.Gehrig＠RSD.rohde-schwarz.com 19 Aug '02

19 Aug '02

Hi All I use Autoyast2 to make an unattened installation of SUSE 8.0 in my company. I just have a problem, perhaps there is someone who can help me. I boot from floppydisk, the installationfiles are on a nfsserver. The PC-Systems have different hardware, so this systems have differnet NIC's too. What to do that autoprobe will install and config this NIC before the installation, after this autoyast2 is avaiable to mount a directory on a nfsserver. What i have to do that all 3 Moduledisk will be loaded? Thanks! bye Alexander Gehrig

2 1

RE: [suse-autoinstall] Still problems with <kernel_parameters> -tag in autoinstall.xml
by Kugelberg, Thorsten 16 Aug '02

16 Aug '02

Hello, I had quite a similar problem: I was trying not to install a bootloader by setting <activate config:type="boolean">false</activate> . That does not work! Lilo is installed into the MBR! Propably there is something wrong with the bootloader option... Regards Thorsten -----Original Message----- From: bernd.ronecker(a)t-online.de To: suse-autoinstall(a)suse.com Sent: 16.08.2002 12:13 Subject: [suse-autoinstall] Still problems with <kernel_parameters> -tag in autoinstall.xml Hi there, during my automatic installation (SuSE 8.0, Autoyast2) I want to setup LILO with a special kernel-parameter. I am trying to do this via the <kernel_parameter>-tag in the bootloader-section in the autoinstall-xml-file. Regardless of which kernel-parameter I try to pass, the lilo.conf won't change at all. Am I doing something wrong or is there any other way to modify the LiLo BEFORE the first reboot during the installation? Here is a snippet from my autoinst.xml-file --------8<-------- <bootloader> <activate config:type="boolean">true</activate> <linear config:type="boolean">false</linear> <location>mbr</location> <kernel_parameters>ramdisk_blocksize=1024</kernel_parameters> </bootloader> --------8<-------- Regards Bernd. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Still problems with <kernel_parameters> -tag in autoinstall.xml
by bernd.ronecker＠t-online.de 16 Aug '02

16 Aug '02

Hi there, during my automatic installation (SuSE 8.0, Autoyast2) I want to setup LILO with a special kernel-parameter. I am trying to do this via the <kernel_parameter>-tag in the bootloader-section in the autoinstall-xml-file. Regardless of which kernel-parameter I try to pass, the lilo.conf won't change at all. Am I doing something wrong or is there any other way to modify the LiLo BEFORE the first reboot during the installation? Here is a snippet from my autoinst.xml-file --------8<-------- <bootloader> <activate config:type="boolean">true</activate> <linear config:type="boolean">false</linear> <location>mbr</location> <kernel_parameters>ramdisk_blocksize=1024</kernel_parameters> </bootloader> --------8<-------- Regards Bernd.

1 0

LILO problems
by Marcel Ritter 15 Aug '02

15 Aug '02

And once again problems ... ... this time it's the bootloader. YaST2 seems to have problems if the install uses non-standard partitioning setups (such as installation on the second harddisk, or preserving an existing partition). At least I got this impression as it worked ok on all Systems with one "all Linux" harddisk. Now I only get things like LIL- or 01010101010101...(forever) or 08080808080808...(forever) and the lilo.conf is not based on the setup on my autoyast.xml I'd like to use a template or whatever to make things work. Perhaps there's even some option I could try, but unfortunately the docs are neither consistent nor up-to-date: According to "profile.elem.bootloader.html" bootloader only contains: (activate,linear,location,parameters), but in the example section there are several other things mentioned: <bootloader> <write_bootloader>true</write_bootloader> <location>mbr</location> <linear>false</linear> <lba_support>false</lba_support> <activate>true</activate> <kernel_parameters></kernel_parameters> <initrd_modules config:type="list" > <module>+++some kernel module name+++</module> </initrd_modules> </bootloader> I'd appreciate any hints and I'd be especially happy about a complete and up-do-date description of the available options. Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

1 0

RE: [suse-autoinstall] Login incorrect
by Kugelberg, Thorsten 14 Aug '02

14 Aug '02

Hello Guido, the password has to be encrypted in the xml file. just use 'htpasswd -n <user>' or 'htpasswd -nb <user> <passwdord>' example: ls3512:~ # htpasswd -n root New password: Re-type new password: root:ZHMzHMSmxYFIE or ls3512:~ # htpasswd -nb root root123 root:raPDr65tuS91Q Then you have to copy the password into the XML file like: <users config:type="list" > <user> <encrypted config:type="boolean" >true</encrypted> <user_password>raPDr65tuS91Q</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean" >true</encrypted> <user_password>pZzfg8kdfCbIY</user_password> <username>sms</username> </user> </users> root is root123 sms is sms123 just like in your example... Regards Thorsten -----Original Message----- From: Guido Frohn To: suse-autoinstall(a)suse.com Sent: 14.08.2002 11:53 Subject: [suse-autoinstall] Login incorrect My first try to install a SuSE Linux test system via AutoYast2 was near successfully. After installing automatically the system boot up correct and pop up the login screen, but a login fails (Login incorrect) with both accounts (see autoinst.xml). I have used the standard SuSE 8.0 CD Roms and the autoinst.xml file was saved on a floppy. I am shure that I have entered the passwords correct and CapsLock was not active -: ) Here a part of the autinst.xml created with AutoYast2 : ... <users config:type="list" > <user> <encrypted config:type="boolean" >true</encrypted> <user_password>root123</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean" >true</encrypted> <user_password>sms123</user_password> <username>sms</username> </user> </users> ... Thanks! Guido Frohn <<ATT558521.txt>>

1 0

Login incorrect
by Guido Frohn 14 Aug '02

14 Aug '02

My first try to install a SuSE Linux test system via AutoYast2 was near successfully. After installing automatically the system boot up correct and pop up the login screen, but a login fails (Login incorrect) with both accounts (see autoinst.xml). I have used the standard SuSE 8.0 CD Roms and the autoinst.xml file was saved on a floppy. I am shure that I have entered the passwords correct and CapsLock was not active -: ) Here a part of the autinst.xml created with AutoYast2 : ... <users config:type="list" > <user> <encrypted config:type="boolean" >true</encrypted> <user_password>root123</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean" >true</encrypted> <user_password>sms123</user_password> <username>sms</username> </user> </users> ... Thanks! Guido Frohn

2 1

AW: [suse-autoinstall] No user interrupt during automatic installation
by Kugelberg, Thorsten 11 Aug '02

11 Aug '02

Hey, killing the shells works fine. But what about the 'abort installation' buttons during the installation... Can I disable them as well?! That would be really nice... Regards Thorsten -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Freitag, 9. August 2002 15:22 An: Kugelberg, Thorsten Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] No user interrupt during automatic installation * Kugelberg, Thorsten <thorsten.kugelberg(a)realtech.de> [Aug 07. 2002 20:23]: > Hallo, > > I am planning to install an Iternet Cafe workstation on SuSE 8.0 via the = > yast2 autoinstall. > The only thing I do not like is, that the user could abort the installati= > on and that the shell on tty 3,5 and 6 are open.=20 > Is there a way to dissallow this interaction?! > I think there was such an option with the autoinstall from SuSE 7.2... You can always kill the shells on the ttys concerned using the a pre-script. In new linuxrc we have added NoShell keyword to disable those shells during boot time. Anas > > Regards > Thorsten > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

1 0

How to recover 2 GB of HD space after I install and uninstall SuSE
by Angshuman Mukherjee 10 Aug '02

10 Aug '02

Hi, Recently I got SuSE linux installed on the extended partition on the only disk of my laptop which has XP installed in the primary partition(NTFS). Before SuSE installation the size of primary as shown by XP was 18 GB, and that of extended was 12 GB which makes sense as my laptop has a 30 GB hard disk. After installation, XP shows the size of C drive i.e. the primary partition as 16 GB. Where did the other 2 GB go ? And I just uninstalled SuSE, and got the extended partition formated to NTFS using XP's disk management utility. Even then the sizes are 16 and 12 GB. Now, the question how do I recover the other 2 GB ? And what's the root cause of this problem ? Thanks in advance Angshuman

1 0

changing ramdisk_blocksize using xml file
by bernd.ronecker＠t-online.de 09 Aug '02

09 Aug '02

Hi, I need to resize my ramdisk blocksize in order to boot the new installed linux. In the xml file under <bootloader>you can add <kernel_parameters>value</kernel_parameters>. For "value" I use: ramdisk_blocksize=1024 which works fine at the lilo prompt. Which further depencies are there or what kind of sysntax should I use for the kernel parameters tag? For any hints I would be happy, Thanx Bernd

2 2

CDROM not in FSTAB
by Werner.Beck＠Lidl.de 09 Aug '02

09 Aug '02

I am using the auto-installation of YAST1. When I install with a CDROM everything is fine. If I use the same files over NFS, the CDROM is missing in the FSTAB. The value CDROM_DEVICE /dev/hdc is in the info file.

1 0

crypted filesystems
by Peeter Russak 09 Aug '02

09 Aug '02

Hi, I noticed the possibility to create crypted file system and wanted to give it a try on one of my data partition. I checked crypt checkbox for one of ext3 partitions, entered password two times and noticed that crypting information was even written correctly into XML-file, but Ifter installing I can't find any visible sign of crypted file system. Nothing different in fstab/mount. Do I search signs from wrong places or crypting really doesn't have to work this time? -- Peeter

2 1

Re: [suse-autoinstall] Partitioning again ...
by Marcel Ritter 09 Aug '02

09 Aug '02

> On Mon, 2002-08-05 at 09:24, Marcel Ritter wrote: > > Hi again! > > > > I'd like to get some further information on the <use> and <reuse> > > statements (partitioning/drive). > > > > According to the documentation it is possible to (re)use certain > > partitions for installation. But there's no example of how to do it. > > > > I tried several forms but none worked (This should reuse partitions 2 and > > 3) > > > > <reuse>2 3</reuse> > > > > Try <use> instead of <reuse>. I have just noticed there is an error in > the documentation. I tried both - none worked. How should autoyast behave if one of this partitions is missing? Which is the correct syntax - separated by spaces, commas? I had a look at the sources but I'm not familiar with the language used in the .ycp files. Ciao, Marcel > Sorry, > Anas ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

2 3

No user interrupt during automatic installation
by Kugelberg, Thorsten 09 Aug '02

09 Aug '02

Hallo, I am planning to install an Iternet Cafe workstation on SuSE 8.0 via the = yast2 autoinstall. The only thing I do not like is, that the user could abort the installati= on and that the shell on tty 3,5 and 6 are open.=20 Is there a way to dissallow this interaction?! I think there was such an option with the autoinstall from SuSE 7.2... Regards Thorsten

2 1

No user interrupt during automatic installation
by Kugelberg, Thorsten 07 Aug '02

07 Aug '02

Hallo, I am planning to install an Iternet Cafe workstation on SuSE 8.0 via the = yast2 autoinstall. The only thing I do not like is, that the user could abort the installati= on and that the shell on tty 3,5 and 6 are open.=20 Is there a way to dissallow this interaction?! I think there was such an option with the autoinstall from SuSE 7.2... Regards Thorsten

1 0

How can I configure additional packages
by Jibin Huang 06 Aug '02

06 Aug '02

Hi, all: I want to install the xntp via autoyast. And it should be configuriert in the file /etc/ntp.conf after the Installation.By the way the file /etc/cups/client.conf should also be configured. Could somebody help me ? Is it possible, that I set the /etc/ntp.conf and /etc/cups/client.conf via post-scripts ? Regrads Jibin

2 1

general questions from a beginner
by Ashley 06 Aug '02

06 Aug '02

Hello, Can I use AutoYaST2 to install SuSE 7.2? If so, do I need to update all the YaST packages as well as getting yast2-config-autoinst? Can I use just a boot floppy to start AutoYaST2 for an nfs install, or must I boot from CD? -- -ashley One of these days I'm going to completely organize my life.

2 1

SuSe 8.0 distribution
by Kenneth Asbury 05 Aug '02

05 Aug '02

I purchased SuSe 6.4 a couple of years ago and have decided to upgrade to 8.0. The full 8.0 distribution was downloaded but I can't seem to find any information regarding how to create installation CD's. I was able to burn a bootable 8.0 startup CD but the install from FTP fails. While I am able to load the network module for my DLink NIC, I can't seem to get IP working. Anyway, how can I create installation CD's? Thanks. --------------------------------- Do You Yahoo!? Yahoo! Health - Feel better, live better

1 0

Partitioning again ...
by Marcel Ritter 05 Aug '02

05 Aug '02

Hi again! I'd like to get some further information on the <use> and <reuse> statements (partitioning/drive). According to the documentation it is possible to (re)use certain partitions for installation. But there's no example of how to do it. I tried several forms but none worked (This should reuse partitions 2 and 3) <reuse>2 3</reuse> or <reuse>2,3</reuse> Both did not work. Can someone tell me how to do this??? Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

1 0

Re: [suse-autoinstall] [HELP] Can not find installation source
by Peeter Russak 01 Aug '02

01 Aug '02

Hi Anas, I entered your line exactly into boot command line but still autoyast reports the same error: Please insert CD 1. Could not mount the source medium. mount:/dev/hdb already mounted or /var/adm/mount busy mount: according to mtab, /dev/hdb is already mounted on /var/adm/mount Does anyone else have had better luck? Can anyone explain by what rule does boot parameters appear in boot commandline? There's some command line parameters for every boot option in isolinux.cfg but only 'Installation - Safe settings' parameters show up on bottom line when selected. It would be good to be able to look every option's parameters and edit if needed. For some guys who still have problems with setup not recognizing their CD as valid install source. I had same problem yesterday and appeared that the problem was with using bs= parameter for dd when extracting iso from CD. Doing just a simple dd < /dev/cdrom > plaa.iso cured everything. So the good command sequence is: dd < /dev/cdrom > suse1.iso mkdir susedir mount -o loop suse1.iso susedir mkdir mydir cp -a susedir/* mydir/ umount susedir cp ~/autoinst.xml mydir/ mkisofs -r -T -J -pad -no-emul-boot -boot-load-size 4 -boot-info-table \ -b suse/images/boot/isolinux.bin -c suse/images/boot.catalog \ -A SuSE-Linux-Professional-INT-i386-8.0.0#0 -V SU8000.001 -o myinstall.iso mydir Now if anybody could explain me how to make this CD boot, read configuration file and install all from same CD I would be saved from offering floppies to customer. Please:) -- Peeter On Wed, 31 Jul 2002, Anas Nashif wrote: > > i'm trying to prepare a custom cd. what is the correct path description for the > > installation source on cd? > > > > maybe... > > > > install=file:// > > Try this: > put the control file in the root of the CD image and name it > autoinst.xml > and add the following to isolinux.cfg > > autoyast=default instmode=cd usedhcp=0 > > Anas

2 1