Re: Linux live CD for z/Linux?
Thanks, that was just the information I needed. Great. I'll check it out and see how it goes. - Kenneth On Tue, Apr 27, 2010 at 7:18 PM, Mauro Souza wrote: > Hi Holter, > > Lets name the things... Let's call DEAD the linux image with damaged system, > and RECOVERY our recovery system. > > You just have to logout DEAD to avoid data corruption, and logon RECOVERY. > On your 3270 console, issue this command: > LINK DEAD 100 200 MR > > CP will ask you the MR password (check USER DIRECT to get the password), and > give RECOVERY full control over disk 100 of DEAD, now mapped as disk 200 on > RECOVERY. > > Do it for any other disk from DEAD. > > Log on RECOVERY via ssh. > Use *chccwdev -e 200* to activate the disk 200, and *lsdasd* to see what is > 200's device name (eg. /dev/dasdk).\ > Create a mount point for this dasd, like /mnt/dead > Mount the dasd: *mount /dev/dasdk /mnt/dead* > > Enjoy! > > Mauro > http://mauro.limeiratem.com - registered Linux User: 294521 > Scripture is both history, and a love letter from God. > > > On Tue, Apr 27, 2010 at 4:43 AM, Kenneth Holter wrote: > >> Hi. >> >> >> I just came across this old post. We're about to create a disaster >> recovery plan using FDR/UpStream, and the setup described in your post >> below seems very interesting. Would you mind sharing info on how you >> set up your recovery system with regards to seeing both disks etc? >> >> >> Regards, >> Kenneth Holter >> >> >> >> On Tue, Jun 23, 2009 at 4:54 PM, Stewart Thomas J >> wrote: >> > We "rolled our own" recovery Linux system (aka "virtual live cd"). We >> simply created a guest with a minimal Linux install and no LVM. Then via the >> beauty of shared disk, if a system fails we just shut down the failed guest >> and link our recovery system's disk to the guest as well. We IPL from the >> recovery system's disk, but it is configured to see both it's normal disk >> and also mount up the LVM directories from the failed system. We use mdisk's >> in the 1xx range for the normal system and in the 2xx range for the recovery >> system - both are configured for the recovery system so he automatically >> brings them both online. >> > >> > Once up the recovery system can edit individual files on the failed >> system's LVM structure, or even perform a network restore. The cool part is >> you can even leave your recovery system up during normal operation so it can >> be backed up itself, get updates, etc. Then take it down and "swing" it onto >> another system when it needs to swoop in for a rescue. >> > >> > __ >> > Tom Stewart >> > Infrastructure Analyst >> > John Deere - z/OS Support Services >> > em: stewartthom...@johndeere.com >> > __ >> > >> > >> > >> > >> > -Original Message- >> > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of >> Kenneth Holter >> > Sent: Tuesday, June 23, 2009 12:35 AM >> > To: LINUX-390@VM.MARIST.EDU >> > Subject: Linux live CD for z/Linux? >> > >> > Hi all. >> > >> > >> > Does there exist any linux live CD's for z/Linux? I've found our CentOS >> live CD very useful on our x86 servers, and would like to have the same >> option available on z/Linux. >> > >> > Regards, >> > Kenneth Holter >> > >> > -- >> > For LINUX-390 subscribe / signoff / archive access instructions, send >> email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Info about users and groups
Regarding suse-ncc: http://mvidner.blogspot.com/2009/11/suse-ncc-user.html According to description of hacluster, it is some user to run heartbeat cluster processes. Messagebus is some special user for D-Bus message bus daemon. These users usually cannot login to the system, because of fake-shell for last two of them and I guess first one has no password. You can check that in /etc/shadow there is no password set for all of them. 2010/4/26 Victor Echavarry Diaz : > Does anybody knows the usage and purpose of the following users and groups. > > Users: > > suse-ncc:x:102:105:Novell Customer Center > User:/var/lib/YaST2/suse-ncc-fakehome:/bin/bash > hacluster:x:90:90:heartbeat > processes:/var/lib/heartbeat/cores/hacluster:/bin/false > messagebus:x:100:101:User for D-BUS:/var/run/dbus:/bin/false > > Groups: > > dialout:x:16:et33393,oracle,quality,support,psadmin,updates > suse-ncc:!:105: > video:x:33:et33393,oracle,quality,support,psadmin,updates > > Regards, > > Víctor Echavarry > System Programmer > Technology Systems & Operations Division > EVERTEC > > > > > > > - > CONFIDENTIALITY NOTE: This email communication and its attachments > contain information that are proprietary and confidential to > EVERTEC, INC., its affiliates or its clients. They may not be > disclosed, distributed, used, copied or modified in any way without > EVERTEC, Inc.’s authorization. If you are not the intended > recipient of this email, you are not an authorized person. Please > delete it and notify the sender immediately. EVERTEC, Inc. and its > affiliates do not assume any liability for damages resulting from > emails that have been sent or altered without their consent. > Moreover, EVERTEC, Inc. has taken precautions to safeguard its > email communications, but cannot assure that such is the case and > disclaim any responsibility attributable thereto. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- With best regards, Andrew -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
OSA problem: no network
Hello, I'm totally new in the mainframe topic, so I'm begging You for some patience :) I have 3 LPAR's on my system, each is prepared to run a Linux distribution (no VM). One is already running SLES 10, but other two are clear. I'm trying to install debian 4.0-r7 (old 2.6.18 kernel which is able to initialize my dasd) on the the second LPAR, but I can't get network during installation. After choosing OSA/Express (qeth) in debian installation I have to select "channels" (i.e. 0.0.1001-0.0.1002-0.0.1003, there are five choices but none of them works), then I set IP, gateway and so on, but still can't get network access. The SLES has no problem with networking; running debian installer on SLES LPAR (with SLES network configuration) also gives no problem, although the "channels'" addresses are different. The OSA which SLES is using is labeled as "Shared" in HMC and I don't know what to do to get these distributions to share connection. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Certifacte authority
I have a Website(test server) that needs to be HTTPS. I created a root CA and server crt and loaded them to my apache server. and the server comes up. I then created to user Certificate and send the rootCA and user Certificate to my workstation. The rootCA got loaded to Trusted Root Certificate. The problem is when is that the user Certificate get loaded to "other people" even I try to force it to Personal. Any suggestion? Thanks Please consider the environment before printing this email. Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux live CD for z/Linux?
Hi Holter, Lets name the things... Let's call DEAD the linux image with damaged system, and RECOVERY our recovery system. You just have to logout DEAD to avoid data corruption, and logon RECOVERY. On your 3270 console, issue this command: LINK DEAD 100 200 MR CP will ask you the MR password (check USER DIRECT to get the password), and give RECOVERY full control over disk 100 of DEAD, now mapped as disk 200 on RECOVERY. Do it for any other disk from DEAD. Log on RECOVERY via ssh. Use *chccwdev -e 200* to activate the disk 200, and *lsdasd* to see what is 200's device name (eg. /dev/dasdk).\ Create a mount point for this dasd, like /mnt/dead Mount the dasd: *mount /dev/dasdk /mnt/dead* Enjoy! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Tue, Apr 27, 2010 at 4:43 AM, Kenneth Holter wrote: > Hi. > > > I just came across this old post. We're about to create a disaster > recovery plan using FDR/UpStream, and the setup described in your post > below seems very interesting. Would you mind sharing info on how you > set up your recovery system with regards to seeing both disks etc? > > > Regards, > Kenneth Holter > > > > On Tue, Jun 23, 2009 at 4:54 PM, Stewart Thomas J > wrote: > > We "rolled our own" recovery Linux system (aka "virtual live cd"). We > simply created a guest with a minimal Linux install and no LVM. Then via the > beauty of shared disk, if a system fails we just shut down the failed guest > and link our recovery system's disk to the guest as well. We IPL from the > recovery system's disk, but it is configured to see both it's normal disk > and also mount up the LVM directories from the failed system. We use mdisk's > in the 1xx range for the normal system and in the 2xx range for the recovery > system - both are configured for the recovery system so he automatically > brings them both online. > > > > Once up the recovery system can edit individual files on the failed > system's LVM structure, or even perform a network restore. The cool part is > you can even leave your recovery system up during normal operation so it can > be backed up itself, get updates, etc. Then take it down and "swing" it onto > another system when it needs to swoop in for a rescue. > > > > __ > > Tom Stewart > > Infrastructure Analyst > > John Deere - z/OS Support Services > > em: stewartthom...@johndeere.com > > __ > > > > > > > > > > -Original Message- > > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Kenneth Holter > > Sent: Tuesday, June 23, 2009 12:35 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Linux live CD for z/Linux? > > > > Hi all. > > > > > > Does there exist any linux live CD's for z/Linux? I've found our CentOS > live CD very useful on our x86 servers, and would like to have the same > option available on z/Linux. > > > > Regards, > > Kenneth Holter > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Announcing Red Hat Enterprise Linux 6 beta
On Tue, Apr 27, 2010 at 3:48 PM, Ursula Braun wrote: > to clarify: it is not IUCV that is deprecated in RHEL6, just the netiucv > driver is deprecated. The base iucv-API and the af_iucv socket interface > continues to be available. deprecated !== removed I thought the concern was that the code was *removed* from RHEL6 after being deprecated for some time already. Last time I tried, the LCS support in Hercules was "experimental" so I guess I should verify that before even thinking about playing with RHEL6 in Hercules. Rob -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Announcing Red Hat Enterprise Linux 6 beta
On Mon, 2010-04-26 at 21:10 +0200, Xose Vazquez Perez wrote: > Brad Hinson wrote: > > > Below is the announcement for RHEL 6 beta, released this past Wednesday. > > It's currently available on RHN (https://rhn.redhat.com). > > be careful, "The CTC (channel-to-channel) and IUCV (inter-user communication > vehicle) are deprecated and are not supported in Red Hat Enterprise Linux" : > > http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Installation_Guide/#s1-s390-steps-hardware > to clarify: it is not IUCV that is deprecated in RHEL6, just the netiucv driver is deprecated. The base iucv-API and the af_iucv socket interface continues to be available. Regards, Ursula Braun (IBM Germany, Linux on System z development) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Announcing Red Hat Enterprise Linux 6 beta
I wrote this: > OK, we use *AF_IUCV sockets* all the time. So what is going away is the > ability to *install* using IUCV. That is understandable. Please let me clarify. After I sent the previous append I got an e-mail from another IBMer with words to the effect of: > It is only the "netiucv" driver that is deprecated in RHEL 6. The > "netiucv" driver is not used for communications in tools such as > the z/VM MAP Server and Terminal Server. These tools rely on the > "Base IUCV" driver and on the "AF_IUCV" driver that is on top of it. > These two drivers are not being deprecated. "Mike MacIsaac"(845) 433-7061 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Announcing Red Hat Enterprise Linux 6 beta
>> Ouch! We use IUCV all the time. Is there any reason for this? > AF_IUCV sockets which is definitely not going away any time soon. OK, we use *AF_IUCV sockets* all the time. So what is going away is the ability to *install* using IUCV. That is understandable. "Mike MacIsaac"(845) 433-7061 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux live CD for z/Linux?
Hi. I just came across this old post. We're about to create a disaster recovery plan using FDR/UpStream, and the setup described in your post below seems very interesting. Would you mind sharing info on how you set up your recovery system with regards to seeing both disks etc? Regards, Kenneth Holter On Tue, Jun 23, 2009 at 4:54 PM, Stewart Thomas J wrote: > We "rolled our own" recovery Linux system (aka "virtual live cd"). We simply > created a guest with a minimal Linux install and no LVM. Then via the beauty > of shared disk, if a system fails we just shut down the failed guest and link > our recovery system's disk to the guest as well. We IPL from the recovery > system's disk, but it is configured to see both it's normal disk and also > mount up the LVM directories from the failed system. We use mdisk's in the > 1xx range for the normal system and in the 2xx range for the recovery system > - both are configured for the recovery system so he automatically brings them > both online. > > Once up the recovery system can edit individual files on the failed system's > LVM structure, or even perform a network restore. The cool part is you can > even leave your recovery system up during normal operation so it can be > backed up itself, get updates, etc. Then take it down and "swing" it onto > another system when it needs to swoop in for a rescue. > > __ > Tom Stewart > Infrastructure Analyst > John Deere - z/OS Support Services > em: stewartthom...@johndeere.com > __ > > > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Kenneth > Holter > Sent: Tuesday, June 23, 2009 12:35 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Linux live CD for z/Linux? > > Hi all. > > > Does there exist any linux live CD's for z/Linux? I've found our CentOS live > CD very useful on our x86 servers, and would like to have the same option > available on z/Linux. > > Regards, > Kenneth Holter > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
