Thanks to all, I found my trivial problem.... To answer the several... -- I add the kernel parm to zipl on zSeries Linux (SLES9/10) because the loop module is in the kernel. (Works like a charm.)
-- It turns out that loop is one of a number of modules that we on the mainframe have come to expect to be in the kernel, but on Intel, they're loaded (modprobe.conf). I made the mistake of assuming that SLES (not SLED as my tired fingers mistakenly hit) was the same on zSeries and on Intel... Dumb mistake... And since it wasn't in the kernel, all my various attempts to pass the parm to the kernel worked, but had no effect. -- Adding the options statement to modprobe.conf.local and rebooting gave me the 64 loop devices I was after. -- And yes, after I found it was loaded I could have removed and reloaded it, but I was hoping for an automatic solution with every boot... Again, thanks to all... I'll now go write on the blackboard 100 times "I will not assume."... Lee -- Post, Mark K wrote:
According to the comments in the source, that capability has been around for almost 7 years: * Maximum number of loop devices now dynamic via max_loop module parameter. * Russell Kroll <[EMAIL PROTECTED]> 19990701 * * Maximum number of loop devices when compiled-in now selectable by passing * max_loop=<1-255> to the kernel on boot. * Erik I. Bols, <[EMAIL PROTECTED]>, Oct 31, 1999 I guess the question I have is: Does SLED10 have the loop driver compiled into the kernel, or as a module? If it's a module, you'll need to pass the parameter when the module is loaded, not as a boot-time kernel parm. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Lee Stewart Sent: Thursday, October 05, 2006 7:57 PM To: [email protected] Subject: Grub - only slightly off topic Hi... I have my new SLED10 Intel system that I want to use for my FTP server for z installs, but... Trying to run the installation tree script it says I need more loop devices. OK, shouldn't be a big deal, I've done that on several z SLES9 systems... Just add max_loop=64 to the kernel parms in zipl.conf, run zipl, reboot and it's fixed.. First I tried adding it to the kernel parms for the boot loader via Yast. I can see where that changed the menu.1st file in /boot/grub, and from /var/log/boot.msg I see where it's passed as part of the kernel command line -- then a little while later I see "loop: loaded (max 8 devices). Anyone have any experience with Grub and SLED10 and adding loop devices? Thanks, Lee -- ---------------------------------------------------------------------- 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
-- Lee Stewart, Senior SE Sirius Enterprise Systems Group Phone: (303) 798-2954 Fax: (720) 228-2321 [EMAIL PROTECTED] www.siriuscom.com ---------------------------------------------------------------------- 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
