Hi Mark,

Do you have an idea in what cases this wouldn't work? This method in
combination with the default dasd udev rules seems to be working for me in
SLES11.


Samir Reddahi




Mark Post <[email protected]>
Sent by: Linux on 390 Port <[email protected]>
08/01/2010 19:09
Please respond to
Linux on 390 Port <[email protected]>


To
[email protected]
cc

Subject
Re: sles11 - adding dasd & yast problem






>>> On 1/8/2010 at 07:52 AM, Samir Reddahi <[email protected]>
wrote:
-snip-
> You can also add an "options dasd_mod dasd=" line  to the
> /etc/modprobe.conf.local with all the dasd devices you want to get
online
> after IPL.  After that you run mkinitrd en zipl.
>
> for example:
> options dasd_mod dasd=200-202,203(diag),204-207,300-31F

That won't necessarily bring them _online_ in SLES11.  That's controlled
by udev rules, which is why Novell recommends using YaST, or the
dasd_configure script to set up your disks.  Both of those will handle all
the necessary pieces.


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



- Confidentiality Notice -

This communication and the information it contains is intended (a) for the 
person(s) or organization(s)
named above and for no other person or organization, and (b) may be 
confidential, legally privileged and
protected by law. Unauthorized use, copying or disclosure of any of it may be 
unlawful! If you receive
this communication in error, please notify us immediately, destroy any copies 
and delete it from your
computer system. Please consult our disclaimer on our site www.securex.eu
Thank you.

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