Re: sles10 hostname
I corrected gateway (good catch, thank you) but problem is still the same. Could you email me parmfile which works for you and doesn't ask for hostname ? Thanks Marian --- Post, Mark K [EMAIL PROTECTED] wrote: If you cut and pasted this, as opposed to typing it in, I see a problem. Your Gateway specification has 6 octets instead of 4. I don't know if this would mess up the parsing of the Hostname or not, but it might. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marian Gasparovic Sent: Saturday, October 28, 2006 3:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: sles10 hostname ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb HostIP=129.40.178.130 Hostname=lat130.pbm.ihost.com Gateway=129.40.178.254.178.254 Netmask=255.255.255.0 Broadcast=129.40.178.255 Layer2=0 ReadChannel=0.0.0600 WriteChannel=0.0.0601 DataChannel=0.0.0602 Nameserver=129.40.106.1 Portname=dontcare Install=nfs://129.40.46.206/nfs/sles10/CD1 UseVNC=1 VNCPassword=123456 InstNetDev=osa OsaInterface=qdio OsaMedium=eth Manual=0 Everything is used correctly, vncserver starts, I connect there, set partitions, choose software, start install. After all needed files from CD1 are read, system is rebooted, then rest of files are read and then it asks for hostname and domain. So I don't enter any of these parameters anywhere during install, only hostname --- Post, Mark K [EMAIL PROTECTED] wrote: Marian, Could you show your whole parmfile? I might be able to take a look at it. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marian Gasparovic Sent: Friday, October 27, 2006 1:33 PM To: LINUX-390@VM.MARIST.EDU Subject: sles10 hostname Hello all, I install SLES10 with parameters in PARMFILE. Everything works nicely, only Hostname=xxx is not used, installer asks for it after first reboot. Am I doing something wrong ? Thank you === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. -- 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 __ Check out the New Yahoo! Mail - Fire up a more powerful email and get things done faster. (http://advision.webevents.yahoo.com/mailbeta) -- 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 Want to start your own business? Learn how on Yahoo! Small Business (http://smallbusiness.yahoo.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: sles10 hostname
Hmmm, it looks like Hostname from parmfile is not used at all. In documentation they mention it only once where they explain how to code parameters, but later where all possible parameters are listed, Hostname is missing. When I tried to setup without parameter file, I was not asked for hostname before VNC part, I was asked for all other parameters from parmfile. This is different from SLES9. Will anybody from SuSE/Novell comment ? Thank you --- Post, Mark K [EMAIL PROTECTED] wrote: If you cut and pasted this, as opposed to typing it in, I see a problem. Your Gateway specification has 6 octets instead of 4. I don't know if this would mess up the parsing of the Hostname or not, but it might. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marian Gasparovic Sent: Saturday, October 28, 2006 3:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: sles10 hostname ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb HostIP=129.40.178.130 Hostname=lat130.pbm.ihost.com Gateway=129.40.178.254.178.254 Netmask=255.255.255.0 Broadcast=129.40.178.255 Layer2=0 ReadChannel=0.0.0600 WriteChannel=0.0.0601 DataChannel=0.0.0602 Nameserver=129.40.106.1 Portname=dontcare Install=nfs://129.40.46.206/nfs/sles10/CD1 UseVNC=1 VNCPassword=123456 InstNetDev=osa OsaInterface=qdio OsaMedium=eth Manual=0 Everything is used correctly, vncserver starts, I connect there, set partitions, choose software, start install. After all needed files from CD1 are read, system is rebooted, then rest of files are read and then it asks for hostname and domain. So I don't enter any of these parameters anywhere during install, only hostname --- Post, Mark K [EMAIL PROTECTED] wrote: Marian, Could you show your whole parmfile? I might be able to take a look at it. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marian Gasparovic Sent: Friday, October 27, 2006 1:33 PM To: LINUX-390@VM.MARIST.EDU Subject: sles10 hostname Hello all, I install SLES10 with parameters in PARMFILE. Everything works nicely, only Hostname=xxx is not used, installer asks for it after first reboot. Am I doing something wrong ? Thank you === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. -- 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 __ Check out the New Yahoo! Mail - Fire up a more powerful email and get things done faster. (http://advision.webevents.yahoo.com/mailbeta) -- 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 Get your email and see which of your friends are online - Right on the New Yahoo.com (http://www.yahoo.com/preview) -- 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: Backing up zLinux
3590s come in SCSI and channel-attached varieties -- they can be one or the other but not both. There is a physically different controller card installed on the drive to differentiate the two variations. If you configure the drive as SCSI, then the traditional IBM operating systems can't use it. If you configure the drive as channel-attached, TSM on Linux can't use it. Brilliant thinking, isn't it? IMHO, if you're intending to use TSM on Linux, get some AIT3 or LTO drives and FCP attach them, or use the ones that your distributed guys already have. They're higher capacity, and a LOT cheaper. From: Linux on 390 Port on behalf of Spann, Elizebeth (Betsie) Sent: Fri 10/27/2006 5:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Backing up zLinux The TSM Administrator's Reference has a DEFINE DEVCLASS command for 3590 IBM devices. Betsie -- 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: Memory access error
On Friday 27 October 2006 22:53, Rich Smrcina wrote: The author asks that I get the Valgrind tool to attempt to debug this. The web site (http://www.valgrind.org) indicates that the tool runs on certain platforms (s390/s390x is not mentioned). No, Valgrind is currently not ported to the s390 platform. As valgrind uses a compiler-like method for code analysis it is not possible to just recompile the tool, we would need a complete backend. -- Mit freundlichen Grüßen / Best Regards Christian Borntraeger Linux Software Engineer zSeries Linux Virtualization -- 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: sles10 hostname
At this time, I can't. I'm waiting for some z/VM maintenance to go on so I can even IPL SLES10. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marian Gasparovic Sent: Sunday, October 29, 2006 7:06 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: sles10 hostname Hmmm, it looks like Hostname from parmfile is not used at all. In documentation they mention it only once where they explain how to code parameters, but later where all possible parameters are listed, Hostname is missing. When I tried to setup without parameter file, I was not asked for hostname before VNC part, I was asked for all other parameters from parmfile. This is different from SLES9. Will anybody from SuSE/Novell comment ? Thank you -- 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: Detection of DASD volume linked read only
Lee Stewart wrote: Depends on when you want to check it... After it's activated, look at /proc/dasd/devices 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 600840 blocks, 2347 MB 0.0.0190(ECKD) at ( 94:24) is dasdg (ro): active at blocksize: 4096, 19260 blocks, 75 MB Note 190 (/dev/dasdg) above is flagged (ro) since it's a read only device. (This is SLES9). In that case it's (ro) because the dasd driver has been told to activate it so. If the DASD driver has not been told RO, it will happily activate it as RW and then fail dismally with any attempted writes (the kernel errors Eric mentioned). I think what Eric requires is a way to determine if VM has given it to Linux RO, in order for Linux to activate it the right way... The hcp/vmcp methods mentioned will be the way to do this. Cheerio, Vic Cross -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: zLinux experience
Mark Perry wrote: Filesystems live in LVs and LVs in VGs which are made up from PVs(=Disks) 1) It is the LV that is striped and not the Filesystem. 2) A striped LV can be expanded providing it uses the same PVs in its VG. (This implies you did not fully utilize the PVs to begin with of course! and that is the real catch.) 3) A Filesystem can be dynamically extended providing there is room in the LV. Corollary to 2): a striped LV can be extended if the space in the VG into which the LV will be extended is carried by the same number of PVs as stripes in the LV. I think an example is required. :) A VG comprises 4 PVs. An LV is created that occupies all the space in the VG, with a stripe size of 4. Expanding the LV would require additional PVs to be added to the VG; the LV can be expanded if new PVs are added to the VG in multiples of 4 (the stripe size of the LV). If only two new PVs are added, the existing stripe=4 LV cannot be expanded into that new space, however a new LV with a stripe size of 2 could be created. I think the big issues with resizing striped LVs are captured somewhere in the LVM doco... Wrt performance gains from striping, you would need to be observant of your stripe size to see that files did indeed fall across stripe boundaries and were written across stripe members. Lots of small files might make this difficult and/or wasteful, but if you have large files you'd be okay. Cheerio, Vic Cross -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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
