Re: problems when running mksles9root.sh for SP4
On Oct 28, 2008, at 10:57 AM, Bernard Wu wrote: Thanks Adam, Add options loop max_loop=64 (or up to 255, I think) in /etc/ modules.conf But there is no /etc/modules.conf . There is a modprobe.conf and a modprobe.conf.local. A grep of loop on modprobe.conf shows : alias block-major-7 loop Maybe this explains why it fails when I try to mount loop8. Well, why it's failing is that you only have 8 devices. Block-major should indeed be 7. If you add "options loop max_loop=64" to modprobe.conf.local that should be all you need, I think. (once you rmmod and reload the module) Adam -- 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
Re: problems when running mksles9root.sh for SP4
This is what I got from IBM support. In the 2.6 kernel for SLES 9, the loop module has been compiled into the kernel. You will need to edit your /etc/zipl.conf and add the following: max_loop=16 Then run zipl Then reboot. That fixed it. Thanks to all who replied. Bernie Wu The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: problems when running mksles9root.sh for SP4
On Tuesday 28 October 2008 11:57, Bernard Wu wrote: >But there is no /etc/modules.conf . >There is a modprobe.conf and a modprobe.conf.local. A grep of loop on >modprobe.conf shows : > >alias block-major-7 loop > >Maybe this explains why it fails when I try to mount loop8. Nope. That 7 is the *major* device number associated with the loopback device driver. Each loopback device uses a *minor" device number to differentiate it. Do a "ls -l /dev/loop*" and you will see that all have major device 7 and the minor devices differ. You can just make more device nodes if your system doesn't have the max_loop thing. - MacK. - Edmund R. MacKenty Software Architect Rocket Software, Inc. Newton, MA USA -- 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
Re: problems when running mksles9root.sh for SP4
On Tuesday 28 October 2008 11:14, Adam Thornton wrote: >Maximum of 8 loop devices. > >Easy to fix. > >Add options loop max_loop=64 (or up to 255, I think) in /etc/ >modules.conf. > >You will need to rmmod and then modprobe loop again, so it may be >simpler just to reboot. Or, change max_loop and manually create the new device nodes you need if you want to avoid a reboot. This little loop will do the trick: n=8; while [ $n -lt 64 ]; do mknod /dev/loop$n b 7 $n; n=$((n+1)); done - MacK. - Edmund R. MacKenty Software Architect Rocket Software, Inc. Newton, MA USA -- 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
Re: problems when running mksles9root.sh for SP4
Thanks Adam, > Add options loop max_loop=64 (or up to 255, I think) in /etc/ modules.conf But there is no /etc/modules.conf . There is a modprobe.conf and a modprobe.conf.local. A grep of loop on modprobe.conf shows : alias block-major-7 loop Maybe this explains why it fails when I try to mount loop8. The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: problems when running mksles9root.sh for SP4
I noticed in your earlier post that mount | grep loop showed a DVD iso mounted on loop0 -- but your losetup -a shows loop0 being mounted as the CD1 iso ..Have you tried umounting the DVD iso? It looks like an NFS mount .. Just wondering if something is mucked up -- what does df -h show after you do the manual mounts?Is the DVD still showing up? Also - have you already tried rebooting? Scott Rohling On Tue, Oct 28, 2008 at 9:39 AM, Bernard Wu <[EMAIL PROTECTED]> wrote: > >I'm wondering if it's being run as root? > > Yes, the script is run by root. > > > The information contained in this e-mail message is intended only for > the personal and confidential use of the recipient(s) named above. This > message may be an attorney-client communication and/or work product and > as such is privileged and confidential. If the reader of this message > is not the intended recipient or an agent responsible for delivering it > to the intended recipient, you are hereby notified that you have > received this document in error and that any review, dissemination, > distribution, or copying of this message is strictly prohibited. If you > have received this communication in error, please notify us immediately > by e-mail, and delete the original message. > > -- > 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
Re: Connect to DB2 with PHP
Hello! Russ, typically Slack contains a command to translate those RPM files into TGZ ones. Look for the rpm2tgz command, and follow its instructions. As for your question regarding PHP and DB2, on that issue I'm not sure. I do know that PHP does support the MySQL database product. -- Gregg C Levine [EMAIL PROTECTED] "The Force will be with you always." Obi-Wan Kenobi > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, > Russell > Sent: Tuesday, October 28, 2008 10:24 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Connect to DB2 with PHP > > All of the documentation that I have found indicates that the DB2 > Application Development Client needs to be installed before php can be > built with Db2 support. I am struggling to get the development client > installed because it is in rpm format and my Slack system does not use > rpm's. Can anyone verify if the DB2 Application Development Client is > the only way to achieve a php to DB2 connection? Is it required to use > the DBI support mentioned below? > > Thanks, > > Russell Jones > ANPAC > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > David Boyes > Sent: Thursday, October 23, 2008 3:36 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Connect to DB2 with PHP > > Yes. Use the DBI support for PHP; that makes your code generic to > arbitrary databases. > > > -Original Message- > From: Linux on 390 Port on behalf of Jones, Russell > Sent: Thu 10/23/2008 3:15 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Connect to DB2 with PHP > > Does anyone have any experience using php on linux to access DB2 on MVS? > Can it be done? > > Thanks in advance, > > Russell Jones > ANPAC > System Programmer > > -- > 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 > > -- > 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
Re: problems when running mksles9root.sh for SP4
On Oct 28, 2008, at 10:07 AM, Bernard Wu wrote: OK. Looks like something is wrong with the devices. I tried it manually and this is what I got : # mount -o loop,ro SLES-9-SP4-CD-s390x-RC7-CD3.iso sles9xsp4root/sp4/ CD3 mount: could not find any free loop device Maximum of 8 loop devices. Easy to fix. Add options loop max_loop=64 (or up to 255, I think) in /etc/ modules.conf. You will need to rmmod and then modprobe loop again, so it may be simpler just to reboot. Adam -- 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
Re: problems when running mksles9root.sh for SP4
>I'm wondering if it's being run as root? Yes, the script is run by root. The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: problems when running mksles9root.sh for SP4
I'm wondering if it's being run as root? Sent from my iPhone On Oct 28, 2008, at 8:35 AM, Michael MacIsaac <[EMAIL PROTECTED]> wrote: But "losetup -a" comes up empty handed. Hmm, you were showing at least /dev/loop0 being used earlier. Try making 6 mount points and mounting the 6 ISO images manually. If this fails then something may be wrong with you loopback devices. If it succeeds then something may be wrong with the script. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 -- 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
Re: problems when running mksles9root.sh for SP4
OK. Looks like something is wrong with the devices. I tried it manually and this is what I got : ***796*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-s390x-RC5a-CD1.iso sles9xsp4root/sles9/CD1 ***797*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-s390x-RC5-CD2.iso sles9xsp4root/core9/CD1 ***798*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-s390x-RC5-CD3.iso sles9xsp4root/core9/CD2 ***799*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-s390x-RC5-CD4.iso sles9xsp4root/core9/CD3 ***800*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-s390x-RC5-CD5.iso sles9xsp4root/core9/CD4 ***801*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-s390x-RC5-CD6.iso sles9xsp4root/core9/CD5 ***802*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-SP4-CD-s390x-RC7-CD1.iso sles9xsp4root/sp4/CD1 ***803*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-SP4-CD-s390x-RC7-CD2.iso sles9xsp4root/sp4/CD2 ***804*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # mount -o loop,ro SLES-9-SP4-CD-s390x-RC7-CD3.iso sles9xsp4root/sp4/CD3 mount: could not find any free loop device ***805*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** # losetup -a /dev/loop0: [fd02]:343406 (SLES-9-s390x-RC5a-CD1.iso) /dev/loop1: [fd02]:343398 (SLES-9-s390x-RC5-CD2.iso) /dev/loop2: [fd02]:343402 (SLES-9-s390x-RC5-CD3.iso) /dev/loop3: [fd02]:343403 (SLES-9-s390x-RC5-CD4.iso) /dev/loop4: [fd02]:343404 (SLES-9-s390x-RC5-CD5.iso) /dev/loop5: [fd02]:343405 (SLES-9-s390x-RC5-CD6.iso) /dev/loop6: [fd02]:343394 (SLES-9-SP4-CD-s390x-RC7-CD1.iso) /dev/loop7: [fd02]:343395 (SLES-9-SP4-CD-s390x-RC7-CD2.iso) ***806*** [EMAIL PROTECTED]:/nfs/iso] *** uid=0 *** Guess I will open up a PMR. Michael MacIsaac <[EMAIL PROTECTED] om>To Sent by: Linux on 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject Re: problems when running mksles9root.sh for SP4 10/28/2008 10:35 AM Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> > But "losetup -a" comes up empty handed. Hmm, you were showing at least /dev/loop0 being used earlier. Try making 6 mount points and mounting the 6 ISO images manually. If this fails then something may be wrong with you loopback devices. If it succeeds then something may be wrong with the script. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 -- 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 The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: problems when running mksles9root.sh for SP4
> But "losetup -a" comes up empty handed. Hmm, you were showing at least /dev/loop0 being used earlier. Try making 6 mount points and mounting the 6 ISO images manually. If this fails then something may be wrong with you loopback devices. If it succeeds then something may be wrong with the script. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 -- 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
Re: Connect to DB2 with PHP
All of the documentation that I have found indicates that the DB2 Application Development Client needs to be installed before php can be built with Db2 support. I am struggling to get the development client installed because it is in rpm format and my Slack system does not use rpm's. Can anyone verify if the DB2 Application Development Client is the only way to achieve a php to DB2 connection? Is it required to use the DBI support mentioned below? Thanks, Russell Jones ANPAC -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, October 23, 2008 3:36 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Connect to DB2 with PHP Yes. Use the DBI support for PHP; that makes your code generic to arbitrary databases. -Original Message- From: Linux on 390 Port on behalf of Jones, Russell Sent: Thu 10/23/2008 3:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Connect to DB2 with PHP Does anyone have any experience using php on linux to access DB2 on MVS? Can it be done? Thanks in advance, Russell Jones ANPAC System Programmer -- 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 -- 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
Re: problems when running mksles9root.sh for SP4
Thanks Ed, But "losetup -a" comes up empty handed. So does "fuser /dev/loop?" on all 16 devices. The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: problems when running mksles9root.sh for SP4
On Tuesday 28 October 2008 09:25, Bernard Wu wrote: >Hi List, >When I run mksles9root.sh I encounter this problem : ... >Mounting SLES9 SP4 ISO images loopback ... > Mounting sles9xsp4root/sp4/CD1/ ... > Mounting sles9xsp4root/sp4/CD2/ ... >mount: could not find any free loop device >Cleaning up mount points ... It looks to me like mksles9root.sh used up your last two loop devices, so it then failed when trying to loopback-mount CD3. Use "losetup -a" to see the status of your attached loopback devices. You can use "losetup -d /dev/loopX" to detach whatever is attached to a particular loopback device. Make sure it is unmounted and not needed before you detach it, though. - MacK. - Edmund R. MacKenty Software Architect Rocket Software, Inc. Newton, MA USA -- 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
Re: problems when running mksles9root.sh for SP4
Hi Mike, I did a "fuser /dev/loop?" on all 16 and it came back clean. However , the "mount | greep loop " produced this : # mount | grep loop /nfs/iso/SLES-10-SP2-DVD-s390x-GM-DVD1.iso on /nfs/sles10sp2/dvd1 type iso9660 (rw,loop=/dev/loop0) "df -h shows" : /nfs/iso/SLES-10-SP2-DVD-s390x-GM-DVD1.iso 2.6G 2.6G 0 100% /nfs/sles10sp2/dvd1 If loop0 is being used, why is "fuser /dev/loop0" coming up clean. Besides there are 15 other devices for the script to use. The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Re: problems when running mksles9root.sh for SP4
Bernard, So you have 16 loopback devices. But I see the error: > mount: could not find any free loop device So I wonder how many of the 16 are available for use. What does "mount | grep loop" return? (I'm not sure of another way of telling which loopback devices are being used). Here's an example: # mount | grep loop /nfs/rhel5.2/RHEL5.2-Server-20080430.0-s390x-DVD.iso on /nfs/rhel5.2/dvd type iso9660 (ro,loop=/dev/loop0) /nfs/sles10sp2/SLES-10-SP2-s390x-GMC-DVD1.iso on /nfs/sles10sp2/CD1 type iso9660 (rw,loop=/dev/loop1) /nfs/rhel5/RHEL5-Server-20070417.0-s390x-DVD.iso on /nfs/rhel5/dvd type iso9660 (ro,loop=/dev/loop2) /nfs/sles10sp1/SLES10-SP1-DVD-s390x-RC5-DVD1.iso on /nfs/sles10sp1/dvd type iso9660 (ro,loop=/dev/loop3) /nfs/sles10sp2/SLES-10-SP2-s390x-GMC-DVD1.iso on /nfs/sles10sp2/dvd1 type iso9660 (ro,loop=/dev/loop4) Another thought would be to preface the mksles9root.sh command with "sh -x" and see if that gives any more hints. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 -- 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
problems when running mksles9root.sh for SP4
Hi List, When I run mksles9root.sh I encounter this problem : # ./mksles9root.sh s390x -m Making a SLES9 install tree ... SP4 ISO images found ... The tree named sles9xsp4root/ will be SLES9 + SP4 ... Making the directory structure ... Mounting ISO images loopback ... Mounting sles9xsp4root/sles9/CD1/ ... Mounting sles9xsp4root/core9/CD1/ ... Mounting sles9xsp4root/core9/CD2/ ... Mounting sles9xsp4root/core9/CD3/ ... Mounting sles9xsp4root/core9/CD4/ ... Mounting sles9xsp4root/core9/CD5/ ... Mounting SLES9 SP4 ISO images loopback ... Mounting sles9xsp4root/sp4/CD1/ ... Mounting sles9xsp4root/sp4/CD2/ ... mount: could not find any free loop device Cleaning up mount points ... umount: sles9xsp4root/sp3-9/CD2/: not found umount: sles9xsp4root/sp3-9/CD3/: not found umount: sles9xsp4root/sp4/CD4/: not mounted Cleaning up remains of sles9xsp4root ... Cleaned up - exiting You may need more loopback devices When I look at /dev/loop? , I see: # ls -ld loop* brw-rw 1 root disk 7, 0 Nov 21 2005 loop0 brw-rw 1 root disk 7, 1 Nov 21 2005 loop1 brw-rw 1 root disk 7, 10 Nov 21 2005 loop10 brw-rw 1 root disk 7, 11 Nov 21 2005 loop11 brw-rw 1 root disk 7, 12 Nov 21 2005 loop12 brw-rw 1 root disk 7, 13 Nov 21 2005 loop13 brw-rw 1 root disk 7, 14 Nov 21 2005 loop14 brw-rw 1 root disk 7, 15 Nov 21 2005 loop15 brw-rw 1 root disk 7, 2 Nov 21 2005 loop2 brw-rw 1 root disk 7, 3 Nov 21 2005 loop3 brw-rw 1 root disk 7, 4 Nov 21 2005 loop4 brw-rw 1 root disk 7, 5 Nov 21 2005 loop5 brw-rw 1 root disk 7, 6 Nov 21 2005 loop6 brw-rw 1 root disk 7, 7 Nov 21 2005 loop7 brw-rw 1 root disk 7, 8 Nov 21 2005 loop8 brw-rw 1 root disk 7, 9 Nov 21 2005 loop9 Looks like I should have sufficient loopback devices for mksles9root.sh. What am I missing ? The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
