July 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

Patches
by Michael.Regner＠dbv-winterthur.de 15 Jul '03

15 Jul '03

Hello, I am trying to setup a SLES 8 using autoyast for servers. Using the original software coming on CD, the installation using autoyast works quite well. But I have no idea how to deal with the patch rpm files from the web. Should I copy them into the /install/sles/CD1 or /install/ul/CD[1,2,3] directory and run the create_package_descr ? Or what is the best way the install the new packages from the begin using using autoyast ? Or must I install the original software and after that perform an update ? How should I deal with the patches in generell ? I dont want to make a online update using the internet. What is the best way to keep a lot of servers up to date ? ThanX Michael

3 3

autoyast network installating without specifiying server IP address
by Fermín Galán 15 Jul '03

15 Jul '03

Hello, To specify where lives control file for an unattended SuSE 8.1 network installation, a switch is used. For example: autoyast=nfs://192.168.1.30/suse_profiles/ Note that the IP of the NFS server have to be staticly set in the switch. Is there any way of installing without specifing server IP address via DHPC? The fact is that programs as grub are capable of getting files without static server IP address configuration, so I wonder if autoyast can. Thanks in advance! ------------ Fermín

1 0

Keep clients updated
by Daniel Bertolo 11 Jul '03

11 Jul '03

Hello I would like to keep auto-installed clients updated, but without a user input. Can yast be configured to check for updates on boot? And what would be the best way to provide an update repository? Shall I mirror a SuSE-update-folder? Someone told me to use apt4rpm. What shall I prefer? YOU or atp4rpm? Thanks Daniel Bertolo

1 0

Re: [SLE] adding menu entires from an RPM install???
by Marc Christensen 11 Jul '03

11 Jul '03

Well, I ran into another snag. This is really upsetting. I have desktop menu entries for the RPMs that I have built in /etc/opt/gnome/SuSE/System/Configuration/myapp.desktop /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/Configuration/myapp.desktop /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/myapp.desktop /etc/opt/kde3/share/applnk/SuSE/Settings/myapp.desktop /etc/opt/kde3/share/applnk/SuSE/System/Configuration/myapp.desktop /etc/opt/kde3/share/applnk/SuSE/System/myapp.desktop (as stated in a previous followup). This works well when installed on an existing system. However, when these RPMs are installed during a network install, the entries are missing! linux:~ # rpm -V myapp missing /etc/opt/gnome/SuSE/System/Configuration/myapp.desktop missing /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/Configuration/myapp.desktop missing /etc/opt/gnome/share/gnome/distribution-menus/SuSE/System/myapp.desktop missing /etc/opt/kde3/share/applnk/SuSE/Settings/myapp.desktop missing /etc/opt/kde3/share/applnk/SuSE/System/Configuration/myapp.desktop missing /etc/opt/kde3/share/applnk/SuSE/System/myapp.desktop linux:~ # How do I work with the [SuSE] system to get menu entries in KDE and gnome?!#$%?!!! -- Marc C. Marc Christensen wrote: > Hi Eveyone, > > I have made an RPM for SLES 8 and need to add an entry to eveyone's > desktop (kicker) and gnome desktop menus. How do I do that? > > In my RPM, I have placed it here: > > /opt/kde3/share/applnk/System/myapp.desktop > > and > > /opt/gnome/share/apps/System/myapp.desktop > > I have not checked to see if the gnome desktop link actualy gets entered > however, the KDE one does not. It does appear here: > > K -> Configure Panel -> Add -> Button -> System -> myapp > > This is not where I want it to go. I need it here: > > K -> System -> myapp > > > How do I do this? > > Thanks > > -- > Marc C. -- Marc Christensen http://www.mecworks.com

1 0

Adding custom RPMs to an NFS install setup
by Marc Christensen 10 Jul '03

10 Jul '03

Hello everyone. I've set up an NFS install for SLES 8 & SuSE 8.1 according to chapter 6 ofAutoYast2 guide: http://www.suse.de/~nashif/autoinstall/8.1/autoyast2.pdf I am unclear how to modify this setup to install custom RPMs that I have created and need installed on workstations. Anyone done this? Thanks.

2 4

Re: [suse-autoinstall] Adding custom RPMs to an NFS install setup
by Anas Nashif 10 Jul '03

10 Jul '03

Richard Bos wrote: > > > I'm doing it differently using suse-8.2, that I'll explain below. In my case > everytime after I run create_package_descr I need to refresh the installed > source by deleting and adding the source using yast that points to my > autoinstall source. That's because the cache /var/adm/YaST/InstSrcManager is > not updated with the info/files created by create_package_descr. Am I doing > something wrong or is it a bug? > Neither, this is the way it should go. If you put some packages on system and use the script, it does not imply that you also want to use the source for the running system., unless its the same version of course, you might need to do it. > My update method in short: > a update directory mirrors some directories from ftp.suse.com > renamed the suse dir to base > created a new dir called latest > linked this dir (latest) so suse > a script now links in the most recent packages from the update and base > directories into the latest directory (right format). After that the > create_package_descr is called. > Yast should actually be able to take the latest version if the same package exists with 2 versions. But this is not clean anyways. Anas

2 1

autoinstall when using two drives
by Debbie Velarde 09 Jul '03

09 Jul '03

I am trying to use AutoYast2 to install a system with two hard drives. I am using SLES8. I want to destroy all existing partitions on both drives and then create the following: sda: /boot, /swap, / (using default values) sdb: /data (which takes up the entire second drive) When I add the information to the partition section of the autoinstall.xml file, I get the following error: "Partition '/data' needs 2.00 MB more disk space. Please deselect some packages." Then if I click "OK", it continues with the installation and then returns another error: "Could not format /dev/sdb5" Here is the partition section of my latest autoinstall.xml: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <reuse>all</reuse> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> </partitions> </drive> <drive> <device>/dev/sdb</device> <reuse>all</reuse> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">true</format> <mount>/data</mount> <filesystem config:type="symbol">jfs</filesystem> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> </drive> </partitioning> Has anyone else seen this problem or know what I am doing incorrectly? Thanks, Debora

2 4

Re: [suse-autoinstall] autoinstall when using two drives
by Anas Nashif 09 Jul '03

09 Jul '03

Hi, According to the log files, yast can only see /dev/sda, no /dev/sdb!! /dev/sda is SCSI, 33.90 GB, /dev/sda, LSILOGIC-1030 IM But there is no mention of /dev/sdb, might be a kernel module problem, although mptscsih is loaded... What happens when you try to install manually? Anas Debbie Velarde wrote: > Anas, > > I've attached all the files in /var/log/YaST2/. > > I will also try changing the size of / to "max" and will send out another > email shortly. > > Thanks, > Debora > > On Wed, 9 Jul 2003, Anas Nashif wrote: > > >>Hi, >>Can you please send me the log files from /var/log/YaST2/*. >> >>Something else I have just noticed, the size of partitions other than >>boot on swap cant be given as "auto". So the size of the root partition >>must be set to "max". But this might not have an effect in your case >>cause the error is about /data. >> >>I have just tried the same configuration you sent, and it works for me, >>so logs will be appreciated.. >> >> >>Anas >> >> >> >>Debbie Velarde wrote: >> >>>Hi Anas, >>> >>>Thanks for replying so quickly. I tried replacing both of the >>><reuse>all</reuse> lines with <use>all</use>. >>>But I am still getting the same error. >>>Any more ideas? >>> >>>On Wed, 9 Jul 2003, Anas Nashif wrote: >>> >>> >>> >>>>Hi, >>>> >>>>Debbie Velarde wrote: >>>> >>>> >>>>>I am trying to use AutoYast2 to install a system with two hard drives. >>>>>I am using SLES8. >>>>>I want to destroy all existing partitions on both drives and then create >>>>>the following: >>>>>sda: /boot, /swap, / (using default values) >>>>>sdb: /data (which takes up the entire second drive) >>>>> >>>>>When I add the information to the partition section of the autoinstall.xml >>>>>file, I get the following error: >>>>>"Partition '/data' needs 2.00 MB more disk space. Please deselect some >>>>>packages." >>>>>Then if I click "OK", it continues with the installation and then returns >>>>>another error: >>>>>"Could not format /dev/sdb5" >>>>> >>>>> >>>>>Here is the partition section of my latest autoinstall.xml: >>>>> <partitioning config:type="list"> >>>>> <drive> >>>>> <device>/dev/sda</device> >>>>> <reuse>all</reuse> >>>> >>>>Try <use>all</use> instead. >>>> >>>> >>>> >>>>Anas >>>> >>>> >>>>-- >>>>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>>>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >>>> >>>> >>>> >> >> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> >> > >>

1 0

RE: [suse-autoinstall] Problem after creating new package db
by Berge, Harry ten 09 Jul '03

09 Jul '03

This is almost the 'default' problem when you do a 'create_package_descr'. What you must do is a create_package_descr -d /install/suse -l german -l english -x /usr/share/autoinstall/EXTRA_PROV This will do the works! Regards Harry > -----Original Message----- > From: Daniel Bertolo [SMTP:daniel.bertolo@kinderheim-buehl.ch] > Sent: Wednesday, July 09, 2003 9:31 AM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Problem after creating new package db > > Hi > > I would like to update my repository with some updated RPMs. As > described in the autoyast howto, I run > "/usr/lib/YaST2/bin/create_package_descr -d /install/suse -l german -l > english". The package describtions will be created and stored in > "./setup/descr". But when I would like to configure the packages in > autoyast, hundreds of dependencies failed, starting with "missing > /bin/awk; missing /bin/bash" etc. > > The only way I found to fix it was to recopy the repository from the > DVDs. But then I still have the old packages. > > What do I do wrong? > > By the way: What is the best way in order to keep the repository > up-to-date. Is there a way that the clients always boot over the network > in order to check for updates? I would like the clients to do the > following during boot: > > - Boot over network using PXE > - Check if there is a local linux installation > - If no -> install > - If yes -> compare the installed packages to the repository > - If there are updates -> install the updated packages -> local boot > - If there are no updates -> local boot > > This is what the SuSE Smart Client Framework does. But how do I implant > this? There is no howto and the consultants I know do not want to tell > me how to do it unless they can do it. > > Thanks for help. > Daniel Bertolo > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

AW: [suse-autoinstall] Problem after creating new package db
by Daniel Bertolo 09 Jul '03

09 Jul '03

> -----Ursprüngliche Nachricht----- > Von: Richard Bos [mailto:richard.bos@xs4all.nl] > Gesendet: Mittwoch, 9. Juli 2003 10:39 > An: Daniel Bertolo > Betreff: Re: [suse-autoinstall] Problem after creating new package db > > On Wednesday 09 July 2003 09:31, Daniel Bertolo wrote: > > Hi > > > > I would like to update my repository with some updated RPMs. As > > described in the autoyast howto, I run > > "/usr/lib/YaST2/bin/create_package_descr -d /install/suse -l german -l > > english". The package describtions will be created and stored in > > "./setup/descr". But when I would like to configure the packages in > > autoyast, hundreds of dependencies failed, starting with "missing > > /bin/awk; missing /bin/bash" etc. > > > > The only way I found to fix it was to recopy the repository from the > > DVDs. But then I still have the old packages. > > > > What do I do wrong? > > What SuSE version? > Did you include the EXTRA_PROV file, located in /usr/share/autoinstall/ SL 8.2. Yes, I include the EXTRA_PROV file (for a Java-RPM). This worked before. The problem I described appears if I replace an original RPM in the repository (in my case, I replaced yast2-ldap-client-2.7.6 with yast2-ldap-client-2.7.7). Afterwards, I do the create_package_descr and the new descriptions will be written to /install/suse/setup/descr/packages[.lang]. When I open yast2 and click on "add software" for the local machine, all dependencies are good and the updated packages are shown. But as soon as I run "yast2 autoyast" and configure the package selections, hundreds of dependencies fail. But the new packages are shown, too. What do I do wrong. Should I better let the original repository as is and use EXTRA_PROV also for updates? > > > By the way: What is the best way in order to keep the repository > > up-to-date. Is there a way that the clients always boot over the network > > in order to check for updates? I would like the clients to do the > > following during boot: > > > > - Boot over network using PXE > > - Check if there is a local linux installation > > - If no -> install > > - If yes -> compare the installed packages to the repository > > - If there are updates -> install the updated packages -> local boot > > - If there are no updates -> local boot > > Is this during installation or operation? > I do this with apt. Just put "apt-rpm -y upgrade" in the boot sequence > and in > a crontab (n case the system is not booted) and the system will be kept up > to > date nicely. You can create a local apt repository with apt4rpm. As > spinoff > of that tool you can keep your installation package up to date keep easily > as > well (only a ver small additional script is needed). > I would like to put this in the boot-sequence in order to update the clients during boot. I will have a look for a apt-howto on the net. Guess there are some, aren't there? But thank you for the idea. > -- > Richard Bos

1 0