Mark,

The link below fails for me: http://linuxvm.org/Info/#autoinst.

I did find it at: http://linuxvm.org/Patches/index.html#autoinst

I am also presuming that since the Starter is SLES 10 that the system
being installed will be a 10 and not 10 sp2. Is that correct?

So I would want the second selection below?
 
Generate a SLES10 AutoYaST Install File
(Last updated June 5, 2008)

Mark Post has created a script that will generate an autoinst.xml file
that can be used to automate a very minimal SLES10 install. 
autoinst.sp2.zip (for SLES10 Service Pack 2) 
autoinst.zip (for SLES10 GA) 

Thank you

Paul

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Wednesday, July 02, 2008 12:02 PM
To: [email protected]
Subject: Re: Question DASD on CLIENT from Start system instructions

>>> On Wed, Jul 2, 2008 at 11:37 AM, in message
<[EMAIL PROTECTED]>,
"Sienicki, Paul K" <[EMAIL PROTECTED]> wrote: 
> I am a little confused and want to ask to verify MDISK configuration 
> for CLIENT from pg 29 of SUSE Linux Enterprise Server Start System for

> System z. Installation Guide.
> 
> The Linux Mdisks are 150 through 152. The 150 disk is only 50
cylinders.
> This is the address 150 that is listed as the IPL volume but it is 
> only 50 cylinders. Is this really the case? As NOVSTARTs IPL volume 
> 150 is 3283.

Some people like to break /boot out into a separate partition, even on
System z.  It's not necessary, per se, since mainframe's don't have any
BIOS limitations to work around.  But, some people feel more comfortable
with it, or want their mainframe systems to look more like their
midrange ones.

Please note, that the sample client directory entry is just that, a
sample.  It's not necessarily even a recommended layout, although I'm
beginning to see people are taking it as gospel.  (I just had another
inquiry from someone who had a customer that thought they needed to use
*exactly* the layout in the doc and wanted to know *exactly* how to lay
out their file systems using it.)

My personal preference is to give guests whole volumes as minidisks
(1-END).  Then, put two partitions on one of them.  One to be used for
the root file system, and the second to be given to LVM.  Any other
volumes are given one partition, and the whole thing given to LVM.

If you want an automated way of doing this, look at
http://linuxvm.org/Info/#autoinst for a script that will generate
exactly that layout using one 3390-3 volume, as well as an extremely
stripped down set of software packages.


Mark Post

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to