VM & VSE & linux/390 Employment Web Page
Greetings; (Posted to VMESA-L and VSE-L and LINUX-390) - - Now in its fifth year! - - Now includes VSE and linux/390! I have set up a public service web page at http://www.eskimo.com/~wix/vm/ for posting positions available and wanted for VM, VSE and linux/390. Please visit the web page for more information and feel free to send me any info you would like to have posted. Please make VM or VSE or linux/390 the first word in the subject. Questions and comments welcome! (Text or html OK. No java, gifs, .DOC, etc. NO RESUMES or CVs!) Please check the web pages for examples before sending your ad! Good luck, Dennis VM & VSE & linux/390 Positions Available last updated Sep 18. VM & VSE & linux/390 Positions Wanted last updated Sep 5. 145971 10/17/02 00:05:02
Re: Free Software - triggers junk?
"!" in the subject field is one indicator of likely spam. We just have to not let ourselves get too excited about things. -jcf Webmaster of my domain http://www.chezford.com - Original Message - From: "Henry Schaffer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 5:38 PM Subject: Free Software - triggers junk? > >Hello from Gregg C Levine > >That's screwy. Mark, that decidedly important post of yours was flagged > >as "junk mail" by Outlook when it landed here. ... > > I'm wondering if the phrase "Free Software" does it. - Hence this > reply is a test of my guess. > > --henry schaffer > > P.S. If you are interested in this topic, our resource page may be > helpful, it is at: > http://www.ncsu.edu/it/open_source/ > >
Re: Marist Linux and OSA-Express
Anne, It would appear that OSA-E is not (at this time) supported by the Marist system. The problem you see is happening because your OSA-Express is not an OSA -- OSA refers to the pre-Express OSA cards, or an OSA defined in LCS mode. If there\'s not an option that says \"QDIO\" or \"OSA-Express\", you\'re out of luck. If you want to play with Marist on your OSA-Express, redefine it to use LCS rather than QDIO. This will require IOCDS work, and a port cannot be in LCS and QDIO mode simultaneously so you would not be able to do this if your port is used by another LPAR/guest. This is also not possible if you have the Gigabit Ethernet OSA-Express, as it *only* supports QDIO. Rather than changing your IOCDS, you could use CTC to link to another system and use that as your router to the outside world. (Of course if you don\'t already have CTC defined to that LPAR and would have to update the IOCDS to do so, you might as well change your OSA...) There\'s network voodoo involved, but nothing that this list couldn\'t get you through! ;) Best of luck, Vic Cross On 17.10.2002 at 05:36:53, \"Peticolas, Anne\" <[EMAIL PROTECTED]> wrote: > Hi, > I\'m trying to get my feet wet by bringing up Marist distribution from > tape in an LPAR environment. Cannot get network connectivity. (This seems > to be a common problem as I\'ve looked through the archives of this list, but > do not see an exact match to my problem, so . . . ) I\'m wondering now > whether I should be doing something different or whether OSA-Express is > supported by Marist. Any help/advice would be appreciated. > I\'ve tried several variations. Right now the device is configured in > the IOCDS as type OSE. When it comes up I see > > Detected device 0090 on subchannel 01C5 - PIM = 80 PAM = 80 POM = FF > Detected device 0091 on subchannel 01C6 - PIM = 80 PAM = 80 POM = FF > Detected device 009E on subchannel 01C7 - PIM = 80 PAM = 80 POM = FF > > and > > SenseID: device 0090 reports: Dev Type/Mod = 3088/60 > SenseID: device 0091 reports: Dev Type/Mod = 3088/60 > SenseID: device 009E reports: Dev Type/Mod = 3088/62 > > I answer 2) for osa ethernet to \"Select the type of your network device:\" > and > noauto=1 devno_portno_pairs=0x0090,0 to \"Please type in the options for the > lcs module:\" > > After answering network questions, I get > Bringing up interface lo >[OK] > Bringing up interface eth0 > > and it just hangs there forever. > > > Regards, >Anne Peticolas >Dept. of Veterans\' > Affairs >Austin, Texas >(512) 326-6105 >
Patches for the 3270 driver
A patch is now available at http://www.utsglobal.com for the 3270 driver. It is the merge of five patches as follows: 0. Fix 3270 console reboot loop 1. Recognize 3270 control unit type 3174 2. Fix tubfs kmalloc()s 3. Dynamically get 3270 input buffer 4. Get colors right on 3270 devices Details of each patch are given below. The patch is named patch-2.4.7-3270 and applies smoothly to the kernel tree built from SuSE kernel-source-2.4.7.SuSE-53.s390.rpm and RedHat kernel-2.4.9-37.src.rpm. To obtain this patch, go to www.utsglobal.com and click Products under Linux. Then scroll down and click GPL SOFTWARE. Click any DOWNLOAD link. Click "3270 Driver (patch 2.4.7)". Click through the GPL for a download screen. We do ask that you register and receive a password. Here's the diffstat: Documentation/s390/3270.ChangeLog | 28 +++ drivers/s390/char/tuball.c| 18 ++ drivers/s390/char/tubfs.c | 130 +++ drivers/s390/char/tubio.h | 13 + drivers/s390/char/tubtty.c| 25 ++ drivers/s390/char/tubttybld.c | 322 ++ 6 files changed, 400 insertions(+), 136 deletions(-) Richard Hitt [EMAIL PROTECTED] PATCH DETAILS - 0. Fix 3270 console reboot loop: In tubtty.c:tty3270_bh() avoid unconditional TUBLOCK(); it can hang the system on reboot. Instead use TUBTRYLOCK() and test device's ready and unready flags before proceeding. 1. Recognize 3270 control unit type 3174: This fix changes tuball.c to functionalize control-unit-type testing; the new function returns a boolean. Heretofore the driver has only recognized control unit type 327x; but 2074-connected tubes show up with type 3174. 2. Fix tubfs kmalloc()s: A recent patch (2.4.20-pre5-ac3) added a limit of 8192 to the kmalloc() length for fs3270_read() and fs3270_write(). This limit can be exceeded with oversize screen sizes (x3270 -oversize COLSxROWS). Patch 2 does this the right way, with Indirect Data Address Words and a maximum kmalloc() size of 0x800. 3. Dynamically get 3270 input buffer: Again with oversize screens, the buffer for the two-line input area may need to be larger than provided for. This patch dynamically acquires an area of the right size, after determining screen size. 4. Get colors right on 3270 devices: The ls(1) command typically colorizes filenames depending on their attributes; 3270 ESC processing to show these colors was broken and is fixed. Also, RedHat and SuSE bootup messages are tabbed and colored, and this fix makes them show up correctly on a 3270 console, when enabled. ESC sequence processing is fixed so that (1) a sequence may be gathered over multiple write() and put_char() calls and (2) the resulting 3270 order stream may be used as necessary across multiple write operations to the tube.
Re: NSS-Support for Linux Kernel under VM
Hello from Gregg C Levine Sorry!! Minor typo: " What is the NSS, and how does is it used by VM, and now by the Linux kernel.?" Should read, "What is the NSS, and how is it used by VM, and how by the Linux Kernel?" --- Gregg C Levine [EMAIL PROTECTED] "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda ) > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU] On Behalf Of > Gregg C Levine > Sent: Wednesday, October 16, 2002 3:48 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] NSS-Support for Linux Kernel under VM > > Hello from Gregg C Levine > Now I'm confused. What is the NSS, and how does is it used by VM, and > now by the Linux kernel. > --- > Gregg C Levine [EMAIL PROTECTED] > > "The Force will be with you...Always." Obi-Wan Kenobi > "Use the Force, Luke." Obi-Wan Kenobi > (This company dedicates this E-Mail to General Obi-Wan Kenobi ) > (This company dedicates this E-Mail to Master Yoda ) > > > > > -Original Message- > > From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU] On Behalf > Of > > Rick Troth > > Sent: Wednesday, October 16, 2002 3:37 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [LINUX-390] NSS-Support for Linux Kernel under VM > > > > > To make the bootstrap decide which ones are overrides > > > and which are additions is going to be ugly. I'm sure we > > > > The "bootstrap" does not decide that. > > > > > could make it very complicated, but we decided to simply > > > append the parameters from the IPL statement to what is > > > > Yes, a simple "append" is probably the best choice. > > That is what LILO does, and it seems to work. You get three places > > where the parm line is defined: initial (gen by LILO), "appened" > > in any LILO stanza, and then whatever is entered at boot time. > > > > > in the NSS already. Main reason to combine both is that > > > the 64 byte from the IPL statement is a bit small. > > > > Yes, small. But better than what we have now, which is nothing. > > > > > It's then up to the particular code in the kernel when > > > the same parameter occurs twice. > > > > Yes, just as things are in the LILO case. > > May not be perfect, but works well for PCs and would work well here.
Re: NSS-Support for Linux Kernel under VM
On Wed, 16 Oct 2002 15:11:34 -0500, Rick Troth <[EMAIL PROTECTED]> wrote: >NSS is "Named Saved System". >You can take a snap-shot of a running (or runnable) system on VM >which CP (the hypervisor part of VM) will store into a spool file. >You can then IPL that system by name, rather than boot by device. > >The syntax of the IPL command is (gross simplification) > >[hcp] ipl >[hcp] ipl [clear] >[hcp] ipl >[hcp] ipl [parm ] > >where 'hcp' is optional and would be how you issue CP commands >from Linux. If you're on a VM console, there is no 'hcp', >you might prefix with 'cp' instead on CMS, or you >might simply omit that prefix and let 'ipl' >be recognized as a hypervisor command. > >NSS is "virtual ROM" for a named system. >When booting from NSS, the system to be booted comes up instantly, >rather than going through the motions of booting from device. >With care, portions of a Named Saved System can be marked >READ ONLY so that CP (the hypervisor portion of VM) >can share that storage among several virtual machines. > >DCSS is related to NSS. >DCSS is a "Discontiguous Shared Segment", >can be read-only or read-write, can be shared or exclusive, >and appears to the guest operating system as attached storage. >(Need not be in the range of defined memory; that is, it can be >ABOVE the defined storage for your virtual machine.) >DCSS is not the same as NSS but is supported by the >same mechanisms within VM (CP). DCSSs are named, like NSSs, >but are "attached" by a DIAGNOSE code, not booted. The closest Linux parallel is an initrd, a ramdisk image which serves as the initial root disk. john
Re: NSS-Support for Linux Kernel under VM
NSS is "Named Saved System". You can take a snap-shot of a running (or runnable) system on VM which CP (the hypervisor part of VM) will store into a spool file. You can then IPL that system by name, rather than boot by device. The syntax of the IPL command is (gross simplification) [hcp] ipl [hcp] ipl [clear] [hcp] ipl [hcp] ipl [parm ] where 'hcp' is optional and would be how you issue CP commands from Linux. If you're on a VM console, there is no 'hcp', you might prefix with 'cp' instead on CMS, or you might simply omit that prefix and let 'ipl' be recognized as a hypervisor command. NSS is "virtual ROM" for a named system. When booting from NSS, the system to be booted comes up instantly, rather than going through the motions of booting from device. With care, portions of a Named Saved System can be marked READ ONLY so that CP (the hypervisor portion of VM) can share that storage among several virtual machines. DCSS is related to NSS. DCSS is a "Discontiguous Shared Segment", can be read-only or read-write, can be shared or exclusive, and appears to the guest operating system as attached storage. (Need not be in the range of defined memory; that is, it can be ABOVE the defined storage for your virtual machine.) DCSS is not the same as NSS but is supported by the same mechanisms within VM (CP). DCSSs are named, like NSSs, but are "attached" by a DIAGNOSE code, not booted.
Re: NSS-Support for Linux Kernel under VM
Hello from Gregg C Levine Now I'm confused. What is the NSS, and how does is it used by VM, and now by the Linux kernel. --- Gregg C Levine [EMAIL PROTECTED] "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda ) > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > Rick Troth > Sent: Wednesday, October 16, 2002 3:37 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] NSS-Support for Linux Kernel under VM > > > To make the bootstrap decide which ones are overrides > > and which are additions is going to be ugly. I'm sure we > > The "bootstrap" does not decide that. > > > could make it very complicated, but we decided to simply > > append the parameters from the IPL statement to what is > > Yes, a simple "append" is probably the best choice. > That is what LILO does, and it seems to work. You get three places > where the parm line is defined: initial (gen by LILO), "appened" > in any LILO stanza, and then whatever is entered at boot time. > > > in the NSS already. Main reason to combine both is that > > the 64 byte from the IPL statement is a bit small. > > Yes, small. But better than what we have now, which is nothing. > > > It's then up to the particular code in the kernel when > > the same parameter occurs twice. > > Yes, just as things are in the LILO case. > May not be perfect, but works well for PCs and would work well here.
Re: NSS-Support for Linux Kernel under VM
> To make the bootstrap decide which ones are overrides > and which are additions is going to be ugly. I'm sure we The "bootstrap" does not decide that. > could make it very complicated, but we decided to simply > append the parameters from the IPL statement to what is Yes, a simple "append" is probably the best choice. That is what LILO does, and it seems to work. You get three places where the parm line is defined: initial (gen by LILO), "appened" in any LILO stanza, and then whatever is entered at boot time. > in the NSS already. Main reason to combine both is that > the 64 byte from the IPL statement is a bit small. Yes, small. But better than what we have now, which is nothing. > It's then up to the particular code in the kernel when > the same parameter occurs twice. Yes, just as things are in the LILO case. May not be perfect, but works well for PCs and would work well here.
Marist Linux and OSA-Express
Hi, I'm trying to get my feet wet by bringing up Marist distribution from tape in an LPAR environment. Cannot get network connectivity. (This seems to be a common problem as I've looked through the archives of this list, but do not see an exact match to my problem, so . . . ) I'm wondering now whether I should be doing something different or whether OSA-Express is supported by Marist. Any help/advice would be appreciated. I've tried several variations. Right now the device is configured in the IOCDS as type OSE. When it comes up I see Detected device 0090 on subchannel 01C5 - PIM = 80 PAM = 80 POM = FF Detected device 0091 on subchannel 01C6 - PIM = 80 PAM = 80 POM = FF Detected device 009E on subchannel 01C7 - PIM = 80 PAM = 80 POM = FF and SenseID: device 0090 reports: Dev Type/Mod = 3088/60 SenseID: device 0091 reports: Dev Type/Mod = 3088/60 SenseID: device 009E reports: Dev Type/Mod = 3088/62 I answer 2) for osa ethernet to "Select the type of your network device:" and noauto=1 devno_portno_pairs=0x0090,0 to "Please type in the options for the lcs module:" After answering network questions, I get Bringing up interface lo [OK] Bringing up interface eth0 and it just hangs there forever. Regards, Anne Peticolas Dept. of Veterans' Affairs Austin, Texas (512) 326-6105
Re: NSS-Support for Linux Kernel under VM
At 01:48 16-10-02, Rick Troth wrote: >Presumably there would be a default "dasd=" parm there. >You would simply have the ability to override with > >ipl linux parm dasd=1b0-1bf root=1b1 > >or some such. >I never said we should stop using the other method. To make the bootstrap decide which ones are overrides and which are additions is going to be ugly. I'm sure we could make it very complicated, but we decided to simply append the parameters from the IPL statement to what is in the NSS already. Main reason to combine both is that the 64 byte from the IPL statement is a bit small. It's then up to the particular code in the kernel when the same parameter occurs twice.
Re: Antwort: Max number of dasd devices
At 10:04 16-10-02, Mark Perry wrote: >It would seem to me that LVM is really the way to go to avoid the headaches >Jim spoke of earlier, as it also allows FS's to span DASD too giving 3390-x >model independence (plus stripping etc.). ... maybe the way to go, but not very far I believe ... When I have understood the discussion on LKM correctly then LVM is not going to be around for long anymore. There seems to be growing interest in ESVM now.
Re: NSS-Support for Linux Kernel under VM
At 01:48 16-10-02, Rick Troth wrote:
>terribly easy to do. ("So why haven't you done it?" they ask.)
Not *terribly* easy... as you know the code to do this is in
the ISP/ASP redbook. That was on 2.2.16 and we reworked it
for 2.4 later. It turns out that 1 is not the best point
to save the NSS. We're trying to get the folks in Boeblingen
to pick it up.
Rob
Re: Shell script error
The problem turned out to the mount options. I had to add the 'exec' option to the mount command. mount -o exec /Disk1 I also chaned the fstab entry to the following: /dev/lvg1/srcdsk1 /Disk1reiserfs noauto,user,exec 1 2 James Johnson Email: [EMAIL PROTECTED] Systems Programmer Voice: 660-543-8065 Central Missouri State University Fax: 660-543-8123
Re: Shell script error
James, It's a little difficult to tell with the line wrap, but it looks as though the permissions on runInstaller are -rw-r--r--. No execute permissions. Either chmod some on, or execute it via "bash runInstaller" Mark Post -Original Message- From: James Johnson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 1:58 PM To: [EMAIL PROTECTED] Subject: Shell script error We have this application that is shipped on CD. To get the code into Linux I did the following as root 1: created a mount point in the root directory drwxrwxrwx6 root root 288 Oct 16 09:17 Disk1 2: add an entry to fstab /dev/lvg1/srcdsk1 /Disk1reiserfs noauto,user 1 2 Then I logon as the as the application installer and FTP the CD into the mounted directory drwxr-xr-x6 oracle oinstall 208 Oct 15 13:41 doc -rw-r--r-- 1 oracle oinstall 5330 Oct 15 13:58 index.htm drwxr-xr-x3 oracle oinstall 128 Oct 15 13:41 install drwxr-xr-x2 oracle oinstall 408 Oct 15 13:42 response -rw-r--r-- 1 oracle oinstall 1157 Oct 15 15:56 runInstaller drwxr-xr-x7 oracle oinstall 304 Oct 15 13:58 stage Whenever I try to run a shell scrip fron the Disk1 directory I get the following oracle@istestdb:~ > cd /Disk1 oracle@istestdb:/Disk1 > ./runInstaller bash: ./runInstaller: bad interpreter: Permission denied I must have an invalid premission defined somewhere but I do not see it. Any help would be appreciated. James Johnson Email: [EMAIL PROTECTED] Systems Programmer Voice: 660-543-8065 Central Missouri State University Fax: 660-543-8123
Re: Shell script error
On Wed, 16 Oct 2002 11:58:00 -0600, James Johnson wrote: >Whenever I try to run a shell scrip fron the Disk1 directory I get the >following >oracle@istestdb:~ > cd /Disk1 >oracle@istestdb:/Disk1 > ./runInstaller >bash: ./runInstaller: bad interpreter: Permission denied > >I must have an invalid premission defined somewhere but I do not see it. Does the install script have execute-permission ? Does the interpreter have execute-permission? regards, Per Jessen, Zurich http://www.enidan.com - home of the J1 serial console. Genius may have its limitations, but stupidity is not thus handicapped.
Shell script error
We have this application that is shipped on CD. To get the code into Linux I did the following as root 1: created a mount point in the root directory drwxrwxrwx6 root root 288 Oct 16 09:17 Disk1 2: add an entry to fstab /dev/lvg1/srcdsk1 /Disk1reiserfs noauto,user 1 2 Then I logon as the as the application installer and FTP the CD into the mounted directory drwxr-xr-x6 oracle oinstall 208 Oct 15 13:41 doc -rw-r--r-- 1 oracle oinstall 5330 Oct 15 13:58 index.htm drwxr-xr-x3 oracle oinstall 128 Oct 15 13:41 install drwxr-xr-x2 oracle oinstall 408 Oct 15 13:42 response -rw-r--r-- 1 oracle oinstall 1157 Oct 15 15:56 runInstaller drwxr-xr-x7 oracle oinstall 304 Oct 15 13:58 stage Whenever I try to run a shell scrip fron the Disk1 directory I get the following oracle@istestdb:~ > cd /Disk1 oracle@istestdb:/Disk1 > ./runInstaller bash: ./runInstaller: bad interpreter: Permission denied I must have an invalid premission defined somewhere but I do not see it. Any help would be appreciated. James Johnson Email: [EMAIL PROTECTED] Systems Programmer Voice: 660-543-8065 Central Missouri State University Fax: 660-543-8123
Re: If I tell you that I'll have to kill you:
> http://www.theregister.co.uk/content/4/27636.html Now *that's* got style... -- db
Re: dasd partition disappeared
Lon, We use dirmaint to allocate mdisks, so overwriting cylinder zero should not be an issue. Good suggestion, though. Michael Lambert Date:Tue, 15 Oct 2002 10:42:43 -0400 From:"Loren Charnley, Jr." <[EMAIL PROTECTED]> Subject: Re: Dasd partition disappeared Michael, Have you looked at the definition of the minidisk in the directory? If you have a VM label on the disk, it will be on cylinder 0. The minidisk should start on cylinder 1 or above or the VM label will be overwritten and the next time you IPL (reboot), LINUX will not be able to find the DASD because it will be looking for the VM label first. Just a thought, it has already happened to me. Loren Charnley, Jr. Tech Support Administrator Family Dollar Stores, Inc. Phone: (704) 847-6961 Ext. 2000
If I tell you that I'll have to kill you:
http://www.theregister.co.uk/content/4/27636.html -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: Antwort: Max number of dasd devices
Hello again, it now occurs to me why I had never used FS Labels. FS Labels can't be used for the root FS, and in our environment every other DASD/partition is placed under LVM control. LVM also solves the same problem, it doesn't matter what the DASD drive letter may be vgscan locates it, and the fstab simply contains /dev/VGNAME/xxx and is thus DASD drive letter independent. It would seem to me that LVM is really the way to go to avoid the headaches Jim spoke of earlier, as it also allows FS's to span DASD too giving 3390-x model independence (plus stripping etc.). The floor is now open to comments ;-) Ciao Mark -Original Message- From: Mark Perry Sent: 16 October 2002 09:28 To: Linux on 390 Port Subject: RE: Antwort: Max number of dasd devices Hi John, no one every pointed that out to me before I just looked it up and according to the docs your right it does the job. I need to try this but I assume one could do the following: dasdfmt -l cdl . fdasd -a . mkreiserfs -l label_for_vol1 .. mount -L label_for_vol1 . or place it in the fstab for a "mount -a": LABEL=label_for_vol1 Much or the doc refers to e2fs and e3fs and xfs, although mkreiserfs supports a label keyword - do you know if this works OK with reiserfs on SuSE SLES-7 s390 and/or s390x? Thanks again for the education ;-) Ciao Mark -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of John Summerfield Sent: 15 October 2002 23:22 To: [EMAIL PROTECTED] Subject: Re: Antwort: Max number of dasd devices On Tue, 15 Oct 2002, Mark Perry wrote: > I've been trying to understand the headache that Jim mentions relating to > the lack of devfs support in SuSE zinux. All that devfs buys you is the > ability to refer to the device address rather than some drive letter in > non-devfs, and the fact that drive letters get reallocated when device > addresses are removed and/or added. Thus the real issue is being able to use > an fstab that contains specific device addresses rather than drive letters, > right? Is there a problem filesystem labels cannot solve? -- Cheers John. Please, no off-list mail. You will fall foul of my spam treatment. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: Antwort: Max number of dasd devices
Hi John, no one every pointed that out to me before I just looked it up and according to the docs your right it does the job. I need to try this but I assume one could do the following: dasdfmt -l cdl . fdasd -a . mkreiserfs -l label_for_vol1 .. mount -L label_for_vol1 . or place it in the fstab for a "mount -a": LABEL=label_for_vol1 Much or the doc refers to e2fs and e3fs and xfs, although mkreiserfs supports a label keyword - do you know if this works OK with reiserfs on SuSE SLES-7 s390 and/or s390x? Thanks again for the education ;-) Ciao Mark -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of John Summerfield Sent: 15 October 2002 23:22 To: [EMAIL PROTECTED] Subject: Re: Antwort: Max number of dasd devices On Tue, 15 Oct 2002, Mark Perry wrote: > I've been trying to understand the headache that Jim mentions relating to > the lack of devfs support in SuSE zinux. All that devfs buys you is the > ability to refer to the device address rather than some drive letter in > non-devfs, and the fact that drive letters get reallocated when device > addresses are removed and/or added. Thus the real issue is being able to use > an fstab that contains specific device addresses rather than drive letters, > right? Is there a problem filesystem labels cannot solve? -- Cheers John. Please, no off-list mail. You will fall foul of my spam treatment. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
