I think that applies to both of us. :)

> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Post, Mark K
> Sent: Friday, April 02, 2004 12:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] new disk for linux (CORRECTION)
>
>
> I think I'm getting my distributions confused again.  I think
> I've been
> arguing my point for SLES8 when it really applies to RHEL3.
> Sigh.  Time for
> some more sleep than I've been allowing myself lately.
>
>
> Mark Post
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Jim
> Sibley
> Sent: Friday, April 02, 2004 11:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: new disk for linux (CORRECTION)
>
>
> Ken Hall wrote:
>
> >Basically, you need an initrd if the boot-device
> drivers >aren't built into the kernel.  (You get this
> choice >during the kernel configure process.)  With
> the variety >of hardware on that platform, ifyou tried
> to include all >possible drivers in the actual kernel,
> it
> >would be huge.  So they make the drivers modules, and
> >load the ones they need.
>
> It appears that the SuSE and RedHat distributions use
> initrd on all platforms as a packaging technique to
> avoid having too many changes between kernels. That
> way they can have a standard kernel configuration.
> They then handle all the various device driver issues
> for each platform with initrd. That way, people can
> change hardware configurations without having to
> recompile the kernel.
>
> SuSE (SLES8) uses the $DASD parameter generated during
> the zipl process to set is dasd devices for zSeries.
> You need only change /etc/zipl.conf and zipl if you
> are adding devices that are already in initrd.
>
> Redhat (RHEL AS 3) has a different approach. They
> ignore the dasd parameters in /etc/zipl.conf and user
> /etc/modules.conf for
> their dasd list. The mkinitrd process reads /etc/modules.conf
> to build the
> dasd list. So, with RedHat, you have update
> /etc/modules.conf, run mkinitrd,
> then zipl.conf (to capture the new disk location of
> initrd...img). This has
> the curious affect that if you use the cio_ignore list, you
> have to update
> both /etc/modules.conf to change volumes needed and
> /etc/zipl.conf to change
> volumes to ignore.
>
> =====
> Jim Sibley
> RHCT, Implementor of Linux on zSeries
>
> "Computer are useless.They can only give answers." Pablo Picasso
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway
> http://promotions.yahoo.com/design_giveaway/
>
> ----------------------------------------------------------------------
> 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
>

==============================================================================

If you are not an intended recipient of this e-mail, please notify
the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it.

Click here for important additional terms relating to this e-mail.
     <http://www.ml.com/email_terms/>

==============================================================================

----------------------------------------------------------------------
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