Re: J2EE and JBoss
J2EE, J2SE and J2ME are all collections of specifications. You have to look at the specifications to determine what they are. In effect, J2SE is the Java Virtual Machine and Java language which is the foundation for the other specifications. J2ME modifies the library routines of J2SE (same Java language) for the embedded space. J2EE is the specification of servers that are Java based. These may be web servers like Tomcat or application servers like JBoss. J2SE is roughly analogous to MVS. J2EE is roughly analogous to CICS running on MVS. Because J2EE is Java based, all you need to run a J2EE app server (in addition to the app server itself) is the underlying JVM and libraries supplied by a J2SE compliant implementation. The downloads mentioned should be sufficient to run JBoss. Harold Grovesteen Jim Elliott wrote: I guess that's where I am confused. Are J2EE and the IBMJava2-SDK the same thing -or- is J2EE part of the IBMJava2-SDK -or- is J2EE another package dependent on the IBMJava2-SDK? If a separate entity, I don't see it on the download site. J2EE is one of three defined Java specs (J2SE for Standard Edition, J2EE for Enterprise Edition and J2ME for Java 2 Micro Edition). The IBM downloads are all for the J2SE SDK. I have never needed anything more so I don't know how you get the full J2EE. See http://www-106.ibm.com/developerworks/java/newto/ for more info. Jim -- 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: 3270 console in Slack390 9.1
Now how did you know I was using Hercules. In Hercules one starts a TN3270 session using the IP address of the PC that is running Hercules and specifies port 3270. I'm doing this but I'm not getting anything. It sounds like Hercules is not a supported platform so maybe I'll stumble onto the answer. -- 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
SLES9 and 3270
Has anyone gotten 3270 devices to work on SLES9 ? I can't get beyond the config3270.sh It doesn't create the script in /tmp that it did on SLES 8 Gary Ernst -- 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: VM Shutdown
Do you add this to the file /boot/zipl/parmfile and the run the zipl command and reboot. -Cameron Seader -Original Message- From: Malcolm Beattie [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 15, 2004 15:12 To: [EMAIL PROTECTED] Subject: Re: VM Shutdown Post, Mark K writes: Depending on what version of z/VM and Linux you're running, updating /etc/inittab to have something like this: # What to do at the Three Finger Salute. ca::ctrlaltdel:/sbin/shutdown -t5 -r now Change that -r (meaning reboot) into -h (meaning halt) so that the SIGNAL SHUTDOWN magic described elsewhere in this thread behaves as expected. For cleanliness, it's also good to include vmpoff=LOGOFF into the kernel parmline so that when the guest finishes shutting down and does a halt -p (a power-off halt), the kernel will do a CP LOGOFF. This logs the guest off; CP then knows that the guest has finished its signal shutdown processing cleanly and will log a nice message to say so. [The vmpoff assumes that your distribution uses a halt -p in its shutdown scripts, as SLES does. If your distribution ends up doing a halt without the -p then the relevant parmline addition would be vmhalt=LOGOFF. I usually add both...belt and braces.] --Malcolm -- Malcolm Beattie [EMAIL PROTECTED] Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself -- 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 This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. -- 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
FCP SCSI Lun Allocation
We are moving to FCP and SCSI disks soon for our Linux Guests and i am wondering if anyone has encountered this before? and what kind of lun sizing did you go with? what kind of lun sizing scheme did you come up with? What did you use for you paging file? vdisk? Please post any helpful info to point me in the right direction. If you have any experiences please share. Thanks, Cameron Seader This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. -- 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: 3270 console in Slack390 9.1
Well, it's not like there are _any_ supported platforms for Slack/390, unless you're willing to spend some money. I'm putting this out largely so that people don't have to spend money. LPAR mode and z/VM I know from personal experience, and can usually answer questions about them. Since this is really a Hercules questions, I would suggest posting it to the Hercules mailing list. Those guys have been dealing with Linux/390 in that environment for quite a while now. It's entirely possible this has been dealt with many times before. If they do have the answer, I'd appreciate a pointer to it (if it's in their archives) being posted here, or an explanation if it is not in their archives. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Tuesday, September 28, 2004 8:37 AM To: [EMAIL PROTECTED] Subject: Re: 3270 console in Slack390 9.1 Now how did you know I was using Hercules. In Hercules one starts a TN3270 session using the IP address of the PC that is running Hercules and specifies port 3270. I'm doing this but I'm not getting anything. It sounds like Hercules is not a supported platform so maybe I'll stumble onto the answer. -- 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: SLES9 and 3270
H Tried that. Didn't work out real well. Never got the prompt back so did a ctl-c. Did a cat on .../online and it had a 1. It seemed liked I would need a getty process for it but I didn't know what to put in inittab for the getty or do I need an fstab entry similar to /dev/pts ? At any rate I tried to just dial it and the kernel oops'd and the virtual mach entered a disabled wait. Gary Ernst Christian Borntraeger wrote: Has anyone gotten 3270 devices to work on SLES9 ? I can't get beyond the config3270.sh It doesn't create the script in /tmp that it did on SLES 8 Gary Ernst If you just want to use your VM console in 3270 mode, it should suffice to add conmode=3270 to your parameter line in /etc/zipl.conf, rezipl and reipl. If you want to add additional GRAFs you have to activate them in sysfs. e.g. echo 1 /sys/bus/ccw/drivers/3270/devno/online before you can use them. -- 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: FCP SCSI Lun Allocation
Uhh, encountered _what_ before? You didn't say, exactly. If you're just looking for information, try these: http://linuxvm.org/present/SHARE100/S9333NFa.pdf http://linuxvm.org/present/SHARE103/S9259vs.pdf Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Seader, Cameron Sent: Tuesday, September 28, 2004 10:34 AM To: [EMAIL PROTECTED] Subject: FCP SCSI Lun Allocation We are moving to FCP and SCSI disks soon for our Linux Guests and i am wondering if anyone has encountered this before? and what kind of lun sizing did you go with? what kind of lun sizing scheme did you come up with? What did you use for you paging file? vdisk? Please post any helpful info to point me in the right direction. If you have any experiences please share. Thanks, Cameron Seader -- 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: 3270 console in Slack390 9.1
On Tue, 28 Sep 2004, Richard Pinion wrote: Now how did you know I was using Hercules. Plenty of us do; it probably wasn't a difficult guess... ;) In Hercules one starts a TN3270 session using the IP address of the PC that is running Hercules and specifies port 3270. That's the Hercules equivalent of plugging in a 3270 terminal. Oh, and switching it on, of course. I'm doing this but I'm not getting anything. Are you running a program against the device that represents your 3270? If you want to log in via your 3270, check that a getty or equivalent (mgetty, mingetty) is running for the device. These are usually started from inittab, but you could test just by starting it manually from the command line of another (working) session. You'll need to know the device node name (the /dev/ name) of your 3270 and specify that on the getty command. Cheers, HTH, Vic Cross -- 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: 3270 console in Slack390 9.1
Theoretically, that's all supposed to be taken care of by the config3270.sh script, and the /tmp/mkdev3270 script that it creates. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Vic Cross Sent: Tuesday, September 28, 2004 11:04 AM To: [EMAIL PROTECTED] Subject: Re: 3270 console in Slack390 9.1 -snip- If you want to log in via your 3270, check that a getty or equivalent (mgetty, mingetty) is running for the device. These are usually started from inittab, but you could test just by starting it manually from the command line of another (working) session. You'll need to know the device node name (the /dev/ name) of your 3270 and specify that on the getty command. -- 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: FCP SCSI Lun Allocation
encountered moving from DASD eckd to FCP SCSI? BTW that is good information that you provided here. I am looking more for information on how people are setting up their lun sizes for each guest. Are they doing it by a guest per guest basis or do they have one guest with a 10 gig lun size and one with a 20 and so on. What is everyone doing? -Cameron -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 08:54 To: [EMAIL PROTECTED] Subject: Re: FCP SCSI Lun Allocation Uhh, encountered _what_ before? You didn't say, exactly. If you're just looking for information, try these: http://linuxvm.org/present/SHARE100/S9333NFa.pdf http://linuxvm.org/present/SHARE103/S9259vs.pdf Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Seader, Cameron Sent: Tuesday, September 28, 2004 10:34 AM To: [EMAIL PROTECTED] Subject: FCP SCSI Lun Allocation We are moving to FCP and SCSI disks soon for our Linux Guests and i am wondering if anyone has encountered this before? and what kind of lun sizing did you go with? what kind of lun sizing scheme did you come up with? What did you use for you paging file? vdisk? Please post any helpful info to point me in the right direction. If you have any experiences please share. Thanks, Cameron Seader -- 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 [INFO] -- Access Manager: This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A2 -- 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: FCP SCSI Lun Allocation
We define the entire Open Systems side of our ESS boxes as 4 Gig luns. It seemes to be a nice allocation amount which is much more useful than a mod-3 but not so large as a mod-9 We use either LVM or RAID 0 to stripe them together into larger filesystems. If you will be needing huge ( on the order of 1 TB ) filesystems, you may want to allocate it in 20 Gig luns so that you don't have to string together so many volumes to get the space you need. It's a balancing act between flexibility / efficiency and ease of managment / possible overallocation. It's rather similar to choosing a block size for a new disk in that respect. Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] Seader, Cameron [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 09/28/04 11:56 AM Please respond to Linux on 390 Port To [EMAIL PROTECTED] cc Subject Re: FCP SCSI Lun Allocation encountered moving from DASD eckd to FCP SCSI? BTW that is good information that you provided here. I am looking more for information on how people are setting up their lun sizes for each guest. Are they doing it by a guest per guest basis or do they have one guest with a 10 gig lun size and one with a 20 and so on. What is everyone doing? -Cameron -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 08:54 To: [EMAIL PROTECTED] Subject: Re: FCP SCSI Lun Allocation Uhh, encountered _what_ before? You didn't say, exactly. If you're just looking for information, try these: http://linuxvm.org/present/SHARE100/S9333NFa.pdf http://linuxvm.org/present/SHARE103/S9259vs.pdf Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Seader, Cameron Sent: Tuesday, September 28, 2004 10:34 AM To: [EMAIL PROTECTED] Subject: FCP SCSI Lun Allocation We are moving to FCP and SCSI disks soon for our Linux Guests and i am wondering if anyone has encountered this before? and what kind of lun sizing did you go with? what kind of lun sizing scheme did you come up with? What did you use for you paging file? vdisk? Please post any helpful info to point me in the right direction. If you have any experiences please share. Thanks, Cameron Seader -- 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 [INFO] -- Access Manager: This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A2 -- 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: FCP SCSI Lun Allocation
Are you partitioning your linux paging file into thse luns as well? What type of partitioning are you doing as far as the filesystem goes? -Cameron -Original Message- From: Robert J Brenneman [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 10:06 To: [EMAIL PROTECTED] Subject: Re: FCP SCSI Lun Allocation We define the entire Open Systems side of our ESS boxes as 4 Gig luns. It seemes to be a nice allocation amount which is much more useful than a mod-3 but not so large as a mod-9 We use either LVM or RAID 0 to stripe them together into larger filesystems. If you will be needing huge ( on the order of 1 TB ) filesystems, you may want to allocate it in 20 Gig luns so that you don't have to string together so many volumes to get the space you need. It's a balancing act between flexibility / efficiency and ease of managment / possible overallocation. It's rather similar to choosing a block size for a new disk in that respect. Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] Seader, Cameron [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 09/28/04 11:56 AM Please respond to Linux on 390 Port To [EMAIL PROTECTED] cc Subject Re: FCP SCSI Lun Allocation encountered moving from DASD eckd to FCP SCSI? BTW that is good information that you provided here. I am looking more for information on how people are setting up their lun sizes for each guest. Are they doing it by a guest per guest basis or do they have one guest with a 10 gig lun size and one with a 20 and so on. What is everyone doing? -Cameron -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 28, 2004 08:54 To: [EMAIL PROTECTED] Subject: Re: FCP SCSI Lun Allocation Uhh, encountered _what_ before? You didn't say, exactly. If you're just looking for information, try these: http://linuxvm.org/present/SHARE100/S9333NFa.pdf http://linuxvm.org/present/SHARE103/S9259vs.pdf Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Seader, Cameron Sent: Tuesday, September 28, 2004 10:34 AM To: [EMAIL PROTECTED] Subject: FCP SCSI Lun Allocation We are moving to FCP and SCSI disks soon for our Linux Guests and i am wondering if anyone has encountered this before? and what kind of lun sizing did you go with? what kind of lun sizing scheme did you come up with? What did you use for you paging file? vdisk? Please post any helpful info to point me in the right direction. If you have any experiences please share. Thanks, Cameron Seader -- 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 [INFO] -- Access Manager: This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A2 -- 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 [INFO] -- Access Manager: This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A2 -- 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: VM Shutdown
On Tue, 28 Sep 2004 08:05:21 -0600, Seader, Cameron [EMAIL PROTECTED] wrote: Do you add this to the file /boot/zipl/parmfile and the run the zipl command and reboot. The parmfile is generated by zipl, so any changes to the kernel command line must be in the /etc/zipl.conf and then run zipl before reboot. -- Rob van der Heij rvdheij @ gmail.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
Re: VM Shutdown
If you use /etc/zipl.conf. I don't. The multi-boot stuff might convince me to change that if I ever get a chance to play with it, but for now I don't use it. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Tuesday, September 28, 2004 2:06 PM To: [EMAIL PROTECTED] Subject: Re: VM Shutdown On Tue, 28 Sep 2004 08:05:21 -0600, Seader, Cameron [EMAIL PROTECTED] wrote: Do you add this to the file /boot/zipl/parmfile and the run the zipl command and reboot. The parmfile is generated by zipl, so any changes to the kernel command line must be in the /etc/zipl.conf and then run zipl before reboot. -- Rob van der Heij rvdheij @ gmail.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 -- 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: FCP SCSI Lun Allocation
Are you partitioning your linux paging file into thse luns as well? What type of partitioning are you doing as far as the filesystem goes? -Cameron We use vdisk for linux paging - it will be faster than real disk when possible, and at least take advantage of VM's wide paging hierarchy when it needs to. We usually just allocate one partition on a 4 Gig lun for the entire filesystem, and then add more luns if things like /opt or /home need to grow. We usually dont create more than one partition on a lun since we are using 4 Gig luns. If you went with something like a 20 Gig lun then you'd probably want to have seperate partitions for /usr, /var, /home or whatever. Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] -- 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: FCP SCSI Lun Allocation
On Tue, 28 Sep 2004, Robert J Brenneman wrote: We usually dont create more than one partition on a lun since we are using 4 Gig luns. If you went with something like a 20 Gig lun then you'd probably want to have seperate partitions ... Hear here! Indeed! Not only use just one partition but also use partition zero. This seems to get misunderstood. What I mean is, where partitioning is not required, don't do it. This is completely reliable where the underlying media is fixed-block (as SAN/SCSI is). You only save a few kilobytes, perhaps, but it's the principle of the matter. Don't partition where it's not needed. Where the device is /dev/sda and you use the whole thing as /dev/sda1 just skip the partitioning and use /dev/sda itself instead. I like the term partition zero because it is minor number zero of that set, which no one has argued against. (Though some have complained about the partition zero terminology.) -- R; HCPMCV1459E -- 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
SAMBA install of SLES9
I am trying to install SLES9 from directories on a Windows machine that is part of a Windows domain. The first part of the install proceeds without problems up until it's time to select packages to install in yast. At that point I'm getting the message: Cannot read package data from installation media. Media error? The directory structure was created using the install.bat file provided on CD1 and the shares were done as per the instructions in the release notes. I would assume that this couldn't be a networking issue since the 1st part of the install (including loading the root system from the install media on the Windows machine) works. I've reported this to SuSE, but they don't seem to be able to reproduce the problem. Has anyone else had this problem and, if so, how did you get around it? Mark Gillis. -- 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
