VM VSE linux/390 Employment Web Page

2004-04-22 Thread Dennis G. Wicks
Greetings; (Posted to VMESA-L and VSE-L and LINUX-390) - - Now in its sixth year! - - 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

End of SCO?

2004-04-22 Thread Marcy Cortes
Interesting article in eWeek: http://www.eweek.com/article2/0,1759,1569671,00.asp BayStar pulling its funding from SCO may be the end not just to SCO's anti-Linux litigation but to the company, says Linux Open Source Center Editor Steven Vaughan-Nichols. Marcy

WAS5.0.2 Application Server

2004-04-22 Thread Mike Lovins
I have an small web application that was developed on a laptop with WAS5.0 web studio and DB2. They decided to install it on my Z800 Linux LPAR running WAS 5.0.2 and DB2 8.1. It installed OK as best as I can tell. I set up the JDBC provider and the data source. I also setup the J2C

Re: WebSphere on SLES8-SP3

2004-04-22 Thread Wolfe, Gordon W
Betsie, While our CP (z/VM 4.4) is 64-bit, our release of SuSE SLES8 is 31-bit. This worked on SLES8, but doesn't with SLES8-SP3. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!'

more than 26 disks

2004-04-22 Thread Ken Vance
Hi, We were adding a large number of disks to our SuSE8 image. Normally, it adds the dasd as dasda, dasdb, etc. When we added disk 27, it adds the dasd as dasdaa. Here is the log when the devices were added: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338

Re: more than 26 disks

2004-04-22 Thread Betsie Spann
Ken, For any dasd greater than dasdz you must run mknod mknod -m 660 /dev/dasdaa b 94 104 mknod -m 660 /dev/dasdaa1 b 94 105 mknod -m 660 /dev/dasdab b 94 108 mknod -m 660 /dev/dasdab1 b 94 109 Get the major/minor node numbers from a cat of /proc/dasd/devices I don't create nodes for

udev on 2.6.5

2004-04-22 Thread Jim Sibley
I've been working with the SuSE SLES9 beta, which is a 2.6.5 kernel. The April 16, 2004, Device Drivers, Features and Commands for the IBM site talks about udev and how it can can provide alternate device names. Has anyone made it work for zSeries? Is there a sample of how to enter the command,

Re: more than 26 disks

2004-04-22 Thread Hall, Ken (IDS ECCS)
A couple of scripts have been posted to automatically take care of this. If nobody else has the short one handy, I'll try to find mine. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Betsie Spann Sent: Thursday, April 22, 2004 12:39 PM To: [EMAIL

Re: udev on 2.6.5

2004-04-22 Thread Ferguson, Neale
I've built the RPMs for udev (0.23) with 2.6.4. I've not done anything with the alternative device names, but out of the box it does a good job of populating /sysfs. Neale -Original Message- I've been working with the SuSE SLES9 beta, which is a 2.6.5 kernel. The April 16, 2004, Device

Re: udev on 2.6.5

2004-04-22 Thread Rich Smrcina
I must have missed that. Is it publicly available? Rich Smrcina - Original Message - From: Jim Sibley [EMAIL PROTECTED] Date: Thursday, April 22, 2004 12:32 pm Subject: udev on 2.6.5 I've been working with the SuSE SLES9 beta, which is a 2.6.5 kernel. The April 16, 2004, Device

Re: more than 26 disks

2004-04-22 Thread Richard Troth
tail +3 /proc/partitions \ | awk '{print mknod -m 600 /dev/ $4, b, $1, $2}' \ | sh -x -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the

Re: udev on 2.6.5

2004-04-22 Thread Jim Sibley
Neale, I guess I don't yet understand sysfs and all that. I have a 3390 device, say 5700, at /dev/dasdb, I would rather use the subchannel address. What would I have to set up to issue the command: mount -t reiserfs /dev/dasd/0.0.5700/disc/part1 /mnt/test ??? I get the message mount: special

Re: more than 26 disks

2004-04-22 Thread Post, Mark K
Ken, Which nodes in /dev/ come pre-defined is entirely up to the Linux distributor. In your case, SUSE decided to stop at /dev/dasdz?. As others have pointed out, that doesn't prevent you from defining your own. Just remember when you upgrade to a new platform that you need to check this to

Re: more than 26 disks

2004-04-22 Thread Post, Mark K
Note that this is a rather brute force method (it does not check to see if the nodes already exist), and that it will only define nodes for volumes that have already been dasdfmt'ed, and fdasd'd, and the appropriate DASD kernel modules loaded. Those caveats aside, it'll create what is needed.

Re: more than 26 disks

2004-04-22 Thread Hall, Ken (IDS ECCS)
Right. The script I wrote, which is a little less elegant, uses /proc/dasd/devices, and builds nodes for only active devices. # $Id: dasdnode,v 1.1 2003/05/19 17:36:03 root Exp $ grep active /proc/dasd/devices | while read DASDENT ; do DEV=${DASDENT:27:6} if [ ! -b /dev/$DEV -a ${DEV:0:4} =