Is there a way to break out of autoyast? We have a vendor cd that has a bunch
of xml files defined and we want to install cd WITHOUT those. Can we NOT have
those execute off cd?
David M. Dean
-
Please see the following link for the
Has anyone had any success in using Autoyast to perform automated
upgrade/installs?
I have made a couple of attempts with zero success
Thanks!
Jeremy
--
For LINUX-390 subscribe / signoff / archive access instructions,
send
>>> On 5/20/2014 at 09:54 AM, "Dean, David (I/S)" wrote:
> Is there a way to break out of autoyast? We have a vendor cd that has a
> bunch of xml files defined and we want to install cd WITHOUT those. Can we
> NOT have those execute off cd?
I sort of understand
MARIST.EDU
Subject: Re: autoyast
>>> On 5/20/2014 at 09:54 AM, "Dean, David (I/S)" wrote:
> Is there a way to break out of autoyast? We have a vendor cd that has
> a bunch of xml files defined and we want to install cd WITHOUT those.
> Can we NOT have those execute off
ct. We
> have successfully installed a base RedHat OS and a Window OS to
> insure that the encryption is working correctly, we now need to see
> if it is sles or the vendor. On a side note, the sles11.3 iso DVD2
> download will not fit on a DVD!
I did not check, but you normally can giv
, etc.
That doesn't sound like AutoYast, rather someone used SUSE Studio to build an
appliance. But of course I could be wrong since I don't have the media on hand.
> We would like to just do a
> "standard" OS only install with this cd. Why? Originally we installed this
--Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Wednesday, May 21, 2014 2:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: autoyast
>>> On 5/21/2014 at 08:29 AM, "Dean, David (I/S)" wrote:
> Mark,
> Yes, it is a vend
>>> On 5/22/2014 at 11:01 AM, "Dean, David (I/S)" wrote:
> I guess I did wander a bit from z, did not think about it.but thanks,
> anyway.
No problem, of course.
> Latest: the problems all emanated from the GRUB loader, and where it was
> installing, a known situation if you google " B
I have successfully installed Linux onto a z/VM virtual machine using
kickstart with help from Brad Hinson. Thank you for all the replies. I
am interested in installing Linux onto a z/VM virtual machine using
autoyast now. How do I format the dasd attached to the virtual machine,
when cpfmtxa
Can anyone point me to a document that describes the autoyast syntax for the
tag and all its related tags.
I have found the following:
http://www.suse.com/~ug/autoyast_doc/index.html
on the suse site but it does not describe the tags and it appears these
are required for z/vm autoinst
Hello,
I am trying to create autoyast config files to automate the installation
process and avoid using the yast GUI for future installs. The AutoYast
packages and RPMs are not installed on my system (Sles 9 w/ SP2). Has
anyone done this before and/or knows how to?
The RPM I need are: yast2
Has anybody in the list ever attempted an autoyast upgrade.
I've done that sort of stuff with kickstart but haven't found anything
meaningfull googling or in the autoyast mailing archives..
thanks for any leads..
Lior.
--
Peace Love and Penguins -
>>> On 10/21/2009 at 2:21 PM, Thang Pham wrote:
> I have successfully installed Linux onto a z/VM virtual machine using
> kickstart with help from Brad Hinson. Thank you for all the replies. I
> am interested in installing Linux onto a z/VM virtual machine using
> au
I have the flag true for each of my
disks, but it seems that my 0101 disk is not being formatted. After going
through the AutoYast UI, and rebooting the z/VM virtual machine, I see the
following on bootup:
dasd(eckd): 0.0.0101: (4kB blks): 2403360kB at 48kB/trk compatible disk
layout
dasdb:VOL1
>>> On 10/21/2009 at 4:29 PM, Thang Pham wrote:
> I have the flag true for each of my
> disks, but it seems that my 0101 disk is not being formatted. After going
> through the AutoYast UI, and rebooting the z/VM virtual machine, I see the
> following on bootup:
>
>
:
LINUX-390@VM.MARIST.EDU
Date:
10/21/2009 04:35 PM
Subject:
Re: Autoyast question
Sent by:
Linux on 390 Port
>>> On 10/21/2009 at 4:29 PM, Thang Pham wrote:
> I have the flag true for each of
my
> disks, but it seems that my 0101 disk is not being formatted. After
goin
I also notices that on the Linux installed with AutoYast, it is missing
/dev/disk path. This may explain why I cannot logon. What could cause
this?
Thanks,
-
Thang Pham
IBM Poughkeepsie
-
From:
Mark Post
To:
LINUX-390
>>> On 10/21/2009 at 5:00 PM, Thang Pham wrote:
> I also notices that on the Linux installed with AutoYast, it is missing
> /dev/disk path. This may explain why I cannot logon. What could cause
> this?
Those are directories and symbolic links created by udev when the
Thang Pham wrote:
I cannot putty to the Linux. On the 3270 session, I see a lot of these
messages:
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=9.60.18.134
DST=239.255.255.253 LEN=
94 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=36942 DPT=427 LEN=74
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=9
al
installation, one of the yast stage2 panels allows you to toggle it "open"
but not sure if this happens automatically with an autoyast install (I
think it depends on whether you code it in specifically with a
section in the autoinst.xml).If you can log in on the console you
should be
We're in the processes of testing out using the autoyast facility to build
repeatable linux servers. We built a SLES11 server through the normal
install process, customized it, and then produced the autoyast.xml file for
use with building replica systems. However we are having a hard
>>> On 5/14/2010 at 03:08 PM, Eric Spencer wrote:
> Can anyone point me to a document that describes the autoyast syntax for the
> tag and all its related tags.
It would be easier to work with http://linuxvm.org/Patches/#autoinst to
generate a working XML file as a starti
PROTECTED] On Behalf Of
Marvin H Green
Sent: Thursday, October 13, 2005 4:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: AutoYast configuration
Hello,
I am trying to create autoyast config files to automate the installation
process and avoid using the yast GUI for future installs. The AutoYast
packages and
>Has anybody in the list ever attempted an autoyast upgrade.
>I've done that sort of stuff with kickstart but haven't found anything
>meaningfull googling or in the autoyast mailing archives..
>thanks for any leads..
>Lior.
There is a presentation on using and configuri
autoinst.xml file to run an automatic install. The autoyast
installer runs through the install. Next the machine is rebooted. The guest
states sshd is started so I should be able to connect to the machine. The IP
address is registered in the vswitch and I can ping the machine. But I can’t
access the
I've uploaded to linuxvm.org two new versions of the bash script that will
generate an AutoYaST file for a minimal installation. These versions are for
SLES10 Service Pack 3 and SLES11 GA. The SLES11 version asks for some more
network information to accommodate changes in the way Aut
Hi all,
there was a thread in here in 2009 dealing with lvm2 initialisation on bootup:
http://www.mail-archive.com/linux-390@vm.marist.edu/msg52937.html
but we are running lvm2-2.02.84-3.25.5 now.
I am now preparing a SLES11 SP2 autoyast profile for initial server
installation using an LVM
The presentation, "z/VM: Linux AutoYast Demo" has been added to
http://linuxvm.org/Present/
It's at the very top, under the "Miscellaneous (Unrelated to any
specific date)" heading.
Thanks to Marvin H. Green, and IBM for providing this to the community.
Mark Po
T.EDU
Subject: [LINUX-390] SLES12 SP3 autoyast install
Hi All,
I am installing a new SLES 12 SP3 system. So first I run a manual install.
After install is completed the machine is rebooted. So far no problem. After
reboot the system is accessible as expected. So now I run yast2 clone_system to
c
Marcy,
I don't think that's the problem. I can't connect, not even from a Linux guest
on the same vswitch/vlan.
The gateway is set in the PARMFILE used during install, both for the manual
install and the autoyast installation. This should be included in the Linux
configuration
Did it maybe start SuSEFirewall?
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of van
Sleeuwen, Berry
Sent: Tuesday, December 19, 2017 8:52 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SLES12 SP3 autoyast install
Marcy,
I don't
kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy
Cortes
Sent: Tuesday, December 19, 2017 5:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES12 SP3 autoyast install
Did it maybe start
kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen
-Original Message-
From: van Sleeuwen, Berry
Sent: Tuesday, December 19, 2017 6:03 PM
To: LINUX-390@VM.MARIST.EDU
Subject: RE: SLES12 SP3 autoyast install
Yes, it does. Just like it does during manual install. The same goes for
SLES 1
ay, December 19, 2017 6:03 PM
To: LINUX-390@VM.MARIST.EDU
Subject: RE: SLES12 SP3 autoyast install
Yes, it does. Just like it does during manual install. The same goes for
SLES 12 SP2. The configuration is included in the xml file. So if anything,
the firewall should be configured the same in both ways of ins
Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
mpost
Sent: Tuesday, December 19, 2017 9:49 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES12 SP3 autoyast install
Please be sure to file a bug report for this.
Mark Post"van Sleeuwen, Berry" wrote:
>>> "van
I am trying to get autoyast working with sles12 on a ECKD install. SUSE
support has suggested that I need a driver update (dud=???). How should that
parm look and where is the driver?
TERM=dumb manual=0 DASD=0100
ReadChannel=0.0.0600 WriteChannel=0.0.0601 DataChannel=0.0.0602
InstNetDev=osa
>>> On 9/9/2010 at 02:53 PM, John Dome wrote:
> Having difficulty using the autoyast installation method for SLES11 SP1,
> after the
> initial install when rebooting eth0 fails with this message:
-snip-
>
>
> static
>
Subject
Re: SLES11 SP1 autoyast qeth error
09/09/2010 03:05
PM
Please respond to
Linux on 390 Port
Having to interfaces specifications for one interface looks wrong to me.
My autoinst.xml
>>> On 9/9/2010 at 03:11 PM, John Dome wrote:
> Yes, Layer2. Yes, I noticed both stanza and tried consolidating those
> along with
> several other changes all fail with the same result.
>
> Are you suggesting that it won't work, or should I open an issue with
> support?
You should be able to d
>>> On 7/9/2012 at 08:16 AM, Tobias Doerkes wrote:
-snip-
> I am now preparing a SLES11 SP2 autoyast profile for initial server
> installation using an LVM layout.
>
> /dev/disk/by-path/ccw-0.0.0201-part1 to /boot
> /dev/disk/by-path/ccw-0.0.0201-part2 is an lvm partiti
Hello Mark,
the issue is solved.
We included information for SLES10 into autoyast.xml. There seems
to be a change at SLES 11. We had to remove all storage related modules form
. Now we simply add vmcp and vmur as modules to our initrd.
Kind regards,
Tobias Doerkes.
All,
An updated version of the bash script that will generate an AutoYaST file for a
more-than minimal installation has been added to the Patches page. This version
is for SLES10 Service Pack 2.
Note that "more than minimal" is not overstating things. A good number of
packages t
I have played with autoyast and quickstart on intel
installs a bit.
On s/390, there is no nice splash screen to announce
your intentions. Logging on during the install process
immediately invokes anaconda for both distributions.
Assuming the configuration files for intel and s/390
are similar
Chris,
When I needed to install with a patched rpm called
yast2-s390-3.1.22-6.1.8918.0.PTF.937340.s390x.rpm, in order to fit within
80 characters, I renamed it to yast2.rpm and used ...
dud=nfs://8.40.33.191/installroot/yast2.rpm
I'd think your "modules" in /srv/nfs/aut
Mike,
I am trying an autoyast automatic installation. I don't have any issues on a
manual install. The messages I am getting (can't get screen prints) are as
follows. I have tried multiple versions of the dud including
dud=nfs://10.96.1.186/srv/nfs/autoyast/yast2-s390-3.1.22-6.1
ST.EDU
Date: 12/02/2015 08:31 AM
Subject:Re: Having issues with sles12 autoyast install
Sent by:Linux on 390 Port
Mike,
I am trying an autoyast automatic installation. I don't have any issues on
a manual install. The messages I am getting (can't get screen pr
>>> On 12/2/2015 at 09:19 AM, "Will, Chris" wrote:
> I am trying to get autoyast working with sles12 on a ECKD install. SUSE
> support has suggested that I need a driver update (dud=???). How should that
> parm look and where is the driver?
You would get the DU
' not found by storage backend
I hit OK
Error
Error while configuring partitions.
Try again.
I hit OK
VNC session ends and I get this prompt in the 3270 session.
0) <-- Back <--
1) Start Installation
2) Settings
3) Expert
4) Exit or Reboot
>>> On 12/18/2015 at 08:44 AM, "Will, Chris" wrote:
> Well it has been a week and I have not made any progress on this with SUSE
> support. I have tried it with SLES 12 and SLES 12 SP1 (with and without the
> provided DUD files) and it still fails. Either it will not work with ECKD
> disk or
-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Friday, December 18, 2015 2:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Having issues with sles12 autoyast install
>>> On 12/18/2015 at 08:44 AM, "Will, Chris" wrote:
> Well it has
>>> On 12/18/2015 at 02:51 PM, "Will, Chris" wrote:
> I have tried it with the following combos.
>
> SLES11 GA
> SLES11 GA with DUD files
> SLES11 SP1
> SLES11 SP1 with DUD files (I just tried it just in case)
>
> None have worked and all give the same error sequence below.
I'm hoping you mean
stems Software
(313) 549-9729 Cell
cw...@bcbsm.com
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Friday, December 18, 2015 3:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Having issues with sles12 autoyast install
>>> On 12/18
>>> On 12/21/2015 at 08:11 AM, "Will, Chris" wrote:
> Yes I meant SLES12. I have reported back that the fix did not work and have
> been waiting for a response from SUSE. I am not sure if this is a bug but
> the first prompt should not happen on an automated install (message about "No
> hard
I'm experimenting with AutoYaST trying to build a guest which has a zFCP
SCSI disk as its boot volume. Ideally, I'd like to pass the WWPN and LUN
for the boot volume to the SLES installation system. Not sure how to do
this.
Is this something that could be passed via a linuxrc paramete
I don't believe that autoyast understands zfcp syntax today, only dasd.
Tony Kubinski wrote:
I'm experimenting with AutoYaST trying to build a guest which has a zFCP
SCSI disk as its boot volume. Ideally, I'd like to pass the WWPN and LUN
for the boot volume to the SLES inst
ECTED] On Behalf Of
Michael MacIsaac
Sent: Friday, January 27, 2006 12:20 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: From LPAR to Virtual Servers in 2 Days
Mark,
> I must have a _tremendous_ amount of character in that case. :)
I don't know - I think using autoyast is cheating :))
On a
I am having trouble getting autoyast to work on 11SP2. The problem
occurs sometime during the disk buildout. It insists it cannot build a
LVM with that size - i am using as a template the .xml dropped by the
first system i built. I have already dropped the portion
significantly; so that'
>>> On 12/10/2010 at 02:18 PM, Daniel Tate wrote:
> I am having trouble getting autoyast to work on 11SP2.
I'm assuming you actually mean SLES11 SP1.
> The problem
> occurs sometime during the disk buildout. It insists it cannot build a
> LVM with that size - i am us
