yum-autoupdate on RHEL
I've discovered this on RHEL5-clone on another platform. I don't have a genuine RHEL system to confirm its presence on, so this could well be a red herring. I fell to wondering how it is that my system was getting updated without my say-so, so conducted an enquiry. Having discovered it, and that it's not easily removed, I then wondered how the big corporates etc feel about it. It looks as if it's not an after-market addition or a cloner's improvement, so I suppose it's a standard part of RHEL5. Good idea? Bad idea? Didn't know about it? -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Administration on RedHat
Hello Justin, Is there any chance this will be extended in the future? I do like the fact that it is possible to access all config from one point. And the the /etc/setuptool.d/ shows what tools there are and how to run them. Unfortunatly packagemanagement is not in there. So if I would want to do that in a UI I'm still stuck with system-config-packages aka pirut which requires X. Or do it myself with help of yum. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Justin Payne Sent: maandag 27 juli 2009 21:45 To: LINUX-390@VM.MARIST.EDU Subject: Re: Administration on RedHat While limited at the moment, there is the setup utility provided by the setuptool rpm. It combines all the tui based tools in one location and does not require X. -Justin Payne -- 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 ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2
Re: yum-autoupdate on RHEL
I've discovered this on RHEL5-clone on another platform. Looking at a RHEL 5.3 system, I don't see a yum-auto update. There is yum-updatesd, which can be controlled in the normal fashion: # chkconfig --list yum-updatesd yum-updatesd0:off 1:off 2:on3:on4:on5:on6:off Regards Mike -- 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: Administration on RedHat
There is definitely a chance for it to be extended. The setuptool package is in Fedora, so all it would take is to add package management functionality upstream (not specific to s390 arch either). Fedora is now using PackageKit, I think this will make adding it easier than previous releases. I know this will not help anyone on RHEL 4 or 5, and would only be possible in RHEL 6. Yum works fine for me, and IMO is much less cryptic than the older upd2date utility. -Justin On 07/28/2009 04:58 AM, van Sleeuwen, Berry wrote: Hello Justin, Is there any chance this will be extended in the future? I do like the fact that it is possible to access all config from one point. And the the /etc/setuptool.d/ shows what tools there are and how to run them. Unfortunatly packagemanagement is not in there. So if I would want to do that in a UI I'm still stuck with system-config-packages aka pirut which requires X. Or do it myself with help of yum. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Justin Payne Sent: maandag 27 juli 2009 21:45 To: LINUX-390@VM.MARIST.EDU Subject: Re: Administration on RedHat While limited at the moment, there is the setup utility provided by the setuptool rpm. It combines all the tui based tools in one location and does not require X. -Justin Payne -- 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: yum-autoupdate on RHEL
The yum-updatesd daemon only checks for available updates and notifies you via email, syslog or dbus. It will not update a system. Red Hat does not ship (nor has shipped) any package called yum-autoupdate. -Justin Payne On 07/28/2009 07:12 AM, Michael Grundy wrote: I've discovered this on RHEL5-clone on another platform. Looking at a RHEL 5.3 system, I don't see a yum-auto update. There is yum-updatesd, which can be controlled in the normal fashion: # chkconfig --list yum-updatesd yum-updatesd0:off 1:off 2:on3:on4:on5:on6:off Regards Mike -- 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
chccwdev never returning on SLES 11
Hello List, Has anyone seen the chccwdev -d command never return? Not only does it not return, but I can't kill it from another SSH session: gpok225:~ # ps -ef | grep chccwdev root 2901 2021 0 09:58 pts/000:00:00 /bin/sh /sbin/chccwdev -d 21b7 root 2943 2817 0 10:07 pts/100:00:00 grep chccwdev gpok225:~ # kill -9 2901 gpok225:~ # ps -ef | grep chccwdev root 2901 2021 0 09:58 pts/000:00:00 /bin/sh /sbin/chccwdev -d 21b7 root 2945 2817 0 10:07 pts/100:00:00 grep chccwdev Any help will be appreciated. Thanks. Mike MacIsaac mike...@us.ibm.com (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
Adding dasd technique
We are running Redhat V5 with z/VM V5.4 with all 3390 dasd. I need to add another volume to one of my servers. I also have 2 swap disk defined using Sine Nomine's swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local: chccwdev -e 700 mkswap /dev/dasd/0.0.0700/part1 swapon -p 2 /dev/dasd/0.0.0700/part1 chccwdev -e 701 mkswap /dev/dasd/0.0.0701/part1 swapon -p 1 /dev/dasd/0.0.0701/part1 /etc/modprobe.conf currently has: alias hsi0 qeth options dasd_mod dasd=200-205 lsdasd reports: 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, 582840 blocks, 2276 MB 0.0.0201(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0202(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0203(ECKD) at ( 94: 12) is dasdd : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0204(ECKD) at ( 94: 16) is dasde : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0205(ECKD) at ( 94: 20) is dasdf : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0700(FBA ) at ( 94: 24) is dasdg : active at blocksize 512, 524288 blocks, 256 MB 0.0.0701(FBA ) at ( 94: 28) is dasdh : active at blocksize 512, 131072 blocks, 64 MB To add a new volume I would add it to the VM directory and format it for VM and Linux. Then attach it to the server and bring it online in which case lsdasd would show a new line at the bottom: 0.0.0206(ECKD) at ( 94: 20) is dasdi : active at blocksize 4096, 600840 blocks, 2347 MB and I could create a physical volume (pvcreate /dev/dasdi) and extend the volume group (vgextend VolGroup00 /dev/dasdi1). So far so good. Now I need to add this new volume to modprobe.conf. If I just change 200-205 to 200-206 the new volume will come up as dasdg at next reboot and will probably destroy the volume group that was expanded. So I appear to need a new/better technique manipulate dasd and a better understanding. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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: Adding dasd technique
On Jul 28, 2009, at 9:18 AM, Bauer, Bobby (NIH/CIT) [E] wrote: We are running Redhat V5 with z/VM V5.4 with all 3390 dasd. I need to add another volume to one of my servers. I also have 2 swap disk defined using Sine Nomine's swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local: If you're running swapgen then you don't need to mkswap or swapon. You should probably put dasd=200-205,700-701. But you should also use the by-device-address form of talking about your dasd (rather than dasda, dasdb, and so on) in /etc/fstab precisely so you don't have to care as you add and subtract devices, as long as they stay at the same virtual addresses. Also don't forget to rebuild your initrd after every time you change dasd configuration. Adam -- 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: Adding dasd technique
When I ran into this I decided on a standard addressing scheme for all Linux clones. In /etc/modprobe.conf: Options dasd_mod 200-2ff,300-30f(diag) (Obviously, I'm using dasd_diag_mod) This allowes changes to LVM without a lot of headache. Patrick Carroll | Enterprise Technical Architect L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033 http://www.llbean.com | pcarr...@llbean.com | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Tuesday, July 28, 2009 10:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Adding dasd technique We are running Redhat V5 with z/VM V5.4 with all 3390 dasd. I need to add another volume to one of my servers. I also have 2 swap disk defined using Sine Nomine's swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local: chccwdev -e 700 mkswap /dev/dasd/0.0.0700/part1 swapon -p 2 /dev/dasd/0.0.0700/part1 chccwdev -e 701 mkswap /dev/dasd/0.0.0701/part1 swapon -p 1 /dev/dasd/0.0.0701/part1 /etc/modprobe.conf currently has: alias hsi0 qeth options dasd_mod dasd=200-205 lsdasd reports: 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, 582840 blocks, 2276 MB 0.0.0201(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0202(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0203(ECKD) at ( 94: 12) is dasdd : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0204(ECKD) at ( 94: 16) is dasde : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0205(ECKD) at ( 94: 20) is dasdf : active at blocksize 4096, 600840 blocks, 2347 MB 0.0.0700(FBA ) at ( 94: 24) is dasdg : active at blocksize 512, 524288 blocks, 256 MB 0.0.0701(FBA ) at ( 94: 28) is dasdh : active at blocksize 512, 131072 blocks, 64 MB To add a new volume I would add it to the VM directory and format it for VM and Linux. Then attach it to the server and bring it online in which case lsdasd would show a new line at the bottom: 0.0.0206(ECKD) at ( 94: 20) is dasdi : active at blocksize 4096, 600840 blocks, 2347 MB and I could create a physical volume (pvcreate /dev/dasdi) and extend the volume group (vgextend VolGroup00 /dev/dasdi1). So far so good. Now I need to add this new volume to modprobe.conf. If I just change 200-205 to 200-206 the new volume will come up as dasdg at next reboot and will probably destroy the volume group that was expanded. So I appear to need a new/better technique manipulate dasd and a better understanding. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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: chccwdev never returning on SLES 11
Hi, Is it a LVM volume your trying to deactivate? And are there any strange LVM related processes running? I experienced a lot of problem with after updating the LVM/device-mapper packages. Novell send me a ptf witch solved the problem. I experienced pvscan was blocking and strange device-mapper related processes also kept running... I could easily imagine that a blocking chccedew -d would following, when the system tries to take the device offline. Best, Klaus Michael MacIsaac wrote: Hello List, Has anyone seen the chccwdev -d command never return? Not only does it not return, but I can't kill it from another SSH session: gpok225:~ # ps -ef | grep chccwdev root 2901 2021 0 09:58 pts/000:00:00 /bin/sh /sbin/chccwdev -d 21b7 root 2943 2817 0 10:07 pts/100:00:00 grep chccwdev gpok225:~ # kill -9 2901 gpok225:~ # ps -ef | grep chccwdev root 2901 2021 0 09:58 pts/000:00:00 /bin/sh /sbin/chccwdev -d 21b7 root 2945 2817 0 10:07 pts/100:00:00 grep chccwdev Any help will be appreciated. Thanks. Mike MacIsaac mike...@us.ibm.com (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 -- 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: chccwdev never returning on SLES 11
Relevant-looking post from a Debian forum: http://www.mail-archive.com/debian-s...@lists.debian.org/msg02156.html ...apparently there's a bug with DASD devices being varied back on after they're varied off when they're listed in the dasd option for the dasd_mod kernel module. On Tue, Jul 28, 2009 at 10:32 AM, Klaus Johansen klu...@gmx.net wrote: Hi, Is it a LVM volume your trying to deactivate? And are there any strange LVM related processes running? I experienced a lot of problem with after updating the LVM/device-mapper packages. Novell send me a ptf witch solved the problem. I experienced pvscan was blocking and strange device-mapper related processes also kept running... I could easily imagine that a blocking chccedew -d would following, when the system tries to take the device offline. Best, Klaus Michael MacIsaac wrote: Hello List, Has anyone seen the chccwdev -d command never return? Not only does it not return, but I can't kill it from another SSH session: gpok225:~ # ps -ef | grep chccwdev root 2901 2021 0 09:58 pts/000:00:00 /bin/sh /sbin/chccwdev -d 21b7 root 2943 2817 0 10:07 pts/100:00:00 grep chccwdev gpok225:~ # kill -9 2901 gpok225:~ # ps -ef | grep chccwdev root 2901 2021 0 09:58 pts/000:00:00 /bin/sh /sbin/chccwdev -d 21b7 root 2945 2817 0 10:07 pts/100:00:00 grep chccwdev Any help will be appreciated. Thanks. Mike MacIsaac mike...@us.ibm.com (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 -- 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: chccwdev never returning on SLES 11
Michael MacIsaac wrote: Has anyone seen the chccwdev -d command never return? Not only does it not return, but I can't kill it from another SSH session: If you can't kill the chccwdev process, this is an indication that the process is currently waiting in a kernel function for a hardware response. There are two reasons why the kernel function wouldn't finish by itself: hardware error or kernel programming error. Are there any messages in the output of 'dmesg' that indicate that device 21b7 may have a problem? What is the output of 'lscss -d 0.0.21b7 --avail'? Regards, Peter Oberparleiter -- 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: Adding dasd technique
Bobby, swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local If you're using SWAPGEN you don't need the mkswap and swapon. SWAPGEN makes the swap space. If you have it in /etc/fstab, as with any other swap space, it will be turned on as part of normal Linux bootup. (doing that is described on page 106 of z/VM and Linux on IBM System z The Virtualization Cookbook for RHEL 5.2, SG24-7492, on the Web at http://www.redbooks.ibm.com/abstracts/sg247492.html) Also section 12.1 on page 181 describes adding a logical volume, then extending it. Hope this helps. Mike MacIsaac mike...@us.ibm.com (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: Adding dasd technique
Thanks Mike but the manual expects you to reboot to make the new disk available. Not always an option. It is the naming that I'm having trouble with. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael MacIsaac Sent: Tuesday, July 28, 2009 10:54 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd technique Bobby, swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local If you're using SWAPGEN you don't need the mkswap and swapon. SWAPGEN makes the swap space. If you have it in /etc/fstab, as with any other swap space, it will be turned on as part of normal Linux bootup. (doing that is described on page 106 of z/VM and Linux on IBM System z The Virtualization Cookbook for RHEL 5.2, SG24-7492, on the Web at http://www.redbooks.ibm.com/abstracts/sg247492.html) Also section 12.1 on page 181 describes adding a logical volume, then extending it. Hope this helps. Mike MacIsaac mike...@us.ibm.com (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 -- 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: Adding dasd technique
How do I use by-device-address? Don't find it on the Redhat site nor did Google tell me much. Fstab is built from the input of Anaconda when I build the server isn't it? Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Adam Thornton Sent: Tuesday, July 28, 2009 10:29 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd technique On Jul 28, 2009, at 9:18 AM, Bauer, Bobby (NIH/CIT) [E] wrote: We are running Redhat V5 with z/VM V5.4 with all 3390 dasd. I need to add another volume to one of my servers. I also have 2 swap disk defined using Sine Nomine's swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local: If you're running swapgen then you don't need to mkswap or swapon. You should probably put dasd=200-205,700-701. But you should also use the by-device-address form of talking about your dasd (rather than dasda, dasdb, and so on) in /etc/fstab precisely so you don't have to care as you add and subtract devices, as long as they stay at the same virtual addresses. Also don't forget to rebuild your initrd after every time you change dasd configuration. Adam -- 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: chccwdev never returning on SLES 11
Klaus, Is it a LVM volume your trying to deactivate? And are there any strange LVM related processes running? No and no. Christian, Relevant-looking post from a Debian forum: http://www.mail-archive.com/debian-s...@lists.debian.org/msg02156.html Thanks for that - sounds similar, but it does not describe the process hanging. Oh, and it hangs so badly that even shutdown -h now does not work - #CP LOG is the only option left :(( Mike MacIsaac mike...@us.ibm.com (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: chccwdev never returning on SLES 11
Peter, Thanks for the info. Are there any messages in the output of 'dmesg' that indicate that device 21b7 may have a problem? gpok225:~ # dmesg | grep 21b7 dasd(eckd): 0.0.21b7: 3390/0C(CU:3990/01) Cyl:500 Head:15 Sec:224 dasd(eckd): 0.0.21b7: (4kB blks): 36kB at 48kB/trk compatible disk layout dasd(eckd): 0.0.21b7: (4kB blks): 36kB at 48kB/trk compatible disk layout What is the output of 'lscss -d 0.0.21b7 --avail'? gpok225:~ # lscss -d 0.0.21b7 --avail Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs Avail. - 0.0.21b7 0.0.0018 3390/0c 3990/e9 yes c0 c0 ff 5070 good Mike MacIsaac mike...@us.ibm.com (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: Adding dasd technique
Bauer, Bobby (NIH/CIT) [E] wrote: Thanks Mike but the manual expects you to reboot to make the new disk available. Not always an option. It is the naming that I'm having trouble with. Adding the disk does not require a reboot. You can use chccwdev at the command line to enable the new disks. My apologies for not highlighting this point in the Redbook. -Brad Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael MacIsaac Sent: Tuesday, July 28, 2009 10:54 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd technique Bobby, swapgen macro in the profile exec for the server and the mkswap and swapon commands in rc.local If you're using SWAPGEN you don't need the mkswap and swapon. SWAPGEN makes the swap space. If you have it in /etc/fstab, as with any other swap space, it will be turned on as part of normal Linux bootup. (doing that is described on page 106 of z/VM and Linux on IBM System z The Virtualization Cookbook for RHEL 5.2, SG24-7492, on the Web at http://www.redbooks.ibm.com/abstracts/sg247492.html) Also section 12.1 on page 181 describes adding a logical volume, then extending it. Hope this helps. Mike MacIsaac mike...@us.ibm.com (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 -- 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 -- Brad Hinson bhin...@redhat.com Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- 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: Adding dasd technique
Bauer, Bobby (NIH/CIT) [E] wrote:
How do I use by-device-address? Don't find it on the Redhat site nor did Google
tell me much. Fstab is built from the input of Anaconda when I build the server
isn't it?
The /dev/disk/ directory contains links with other ways to access the
DASD. For example, on my system:
# ls -ld /dev/disk/*
drwxr-xr-x 2 root root 480 Jul 15 19:22 /dev/disk/by-id
drwxr-xr-x 2 root root 60 Jun 25 15:13 /dev/disk/by-label
drwxr-xr-x 2 root root 380 Jul 15 19:22 /dev/disk/by-path
drwxr-xr-x 2 root root 60 Jul 15 17:12 /dev/disk/by-uuid
# ls /dev/disk/by-id/ccw-0X3D2C* -l
lrwxrwxrwx 1 root root 11 Jun 25 15:13 /dev/disk/by-id/ccw-0X3D2C -
../../dasda
lrwxrwxrwx 1 root root 12 Jun 25 15:13 /dev/disk/by-id/ccw-0X3D2C-part1
- ../../dasda1
lrwxrwxrwx 1 root root 12 Jun 25 15:13 /dev/disk/by-id/ccw-0X3D2C-part2
- ../../dasda2
You can use these in /etc/fstab, but in your case with LVM, I don't
think it will help, since LVM entries in fstab are of the form
/dev/{volume_group_name}/{logical_volume_name}.
Going back to the original issue, the reason the new disk came up as
dasdg is because you're calling chccwdev/mkswap in /etc/rc.local. As
Adam, Pat, and Mike pointed out, you should use modprobe.conf for all
disks. Either:
options dasd_mod dasd=200-205,700-701
in which case any DASD you add after 701 will be dasdh. Or you could do
something like:
options dasd_mod dasd=200-20f,700-701
The latter is a preallocation of device nodes. You can add any DASD up
to 70f without needing to remake the initrd or rerun zipl.
-Brad
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Adam
Thornton
Sent: Tuesday, July 28, 2009 10:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding dasd technique
On Jul 28, 2009, at 9:18 AM, Bauer, Bobby (NIH/CIT) [E] wrote:
We are running Redhat V5 with z/VM V5.4 with all 3390 dasd. I need
to add another volume to one of my servers. I also have 2 swap disk
defined using Sine Nomine's swapgen macro in the profile exec for
the server and the mkswap and swapon commands in rc.local:
If you're running swapgen then you don't need to mkswap or swapon.
You should probably put dasd=200-205,700-701.
But you should also use the by-device-address form of talking about
your dasd (rather than dasda, dasdb, and so on) in /etc/fstab
precisely so you don't have to care as you add and subtract devices,
as long as they stay at the same virtual addresses.
Also don't forget to rebuild your initrd after every time you change
dasd configuration.
Adam
--
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
--
Brad Hinson bhin...@redhat.com
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
--
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: Adding dasd technique
On 7/28/2009 at 10:18 AM, Bauer, Bobby (NIH/CIT) [E] baue...@mail.nih.gov wrote: -snip- and I could create a physical volume (pvcreate /dev/dasdi) and extend the volume group (vgextend VolGroup00 /dev/dasdi1). So far so good. Now I need to add this new volume to modprobe.conf. If I just change 200-205 to 200-206 the new volume will come up as dasdg at next reboot and will probably destroy the volume group that was expanded. Not at all. LVM doesn't care what the underlying device names are. It looks at each device to see if it has LVM metadata written on it. If it does, and it has a UUID that it knows about, it just uses it. Mark Post -- 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: chccwdev never returning on SLES 11
On 7/28/2009 at 10:14 AM, Michael MacIsaac mike...@us.ibm.com wrote: Hello List, Has anyone seen the chccwdev -d command never return? Not only does it not return, but I can't kill it from another SSH session: I'd like to know where in the script it's hanging. Please do a sh -x chccwdev command. Also, what maintenance have you applied? I've got a stock GA system, and I don't see the same problem. Mark Post -- 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: chccwdev never returning on SLES 11
Mark,
I'd like to know where in the script it's hanging. Please do a sh -x
chccwdev command.
+ BUSIDLIST=0.0.21b7
+ '[' 0 -ne 0 ']'
+ '[' 0.0.21b7 = '' ']'
+ true
+ SAVEDATTRS=(${attrv...@]})
+ for BUSID in '$BUSIDLIST'
+ SYSPATH=/sys/bus/ccw/devices/0.0.21b7
+ '[' '!' -r /sys/bus/ccw/devices/0.0.21b7 ']'
+ CNT=0
+ '[' 0 -lt 0 ']'
+ '[' 0 '!=' '' ']'
+ IsOnline /sys/bus/ccw/devices/0.0.21b7 0
+ '[' '!' -f /sys/bus/ccw/devices/0.0.21b7/online ']'
++ cat /sys/bus/ccw/devices/0.0.21b7/online
+ '[' 1 -eq 0 ']'
+ return 1
+ '[' 0 -eq 1 ']'
+ echo 'Setting device 0.0.21b7 offline'
Setting device 0.0.21b7 offline
+ '[' '' '!=' '' ']'
+ echo 0
Also, what maintenance have you applied? I've got a stock GA system,
and I don't see the same problem.
None - also a stock GA system.
This occurs in a script, so there's lots that comes before it. I could
supply you with all the gory details if you're interested.
Mike MacIsaac mike...@us.ibm.com (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: Adding dasd technique
Am I missing something this isn't about the problem ,but helping me understan:
you said
options dasd_mod dasd=200-20f,700-701
The latter is a preallocation of device nodes. You
can add any DASD up
to 70f without needing to remake the initrd or rerun zipl.
Should that be 700-70f??
thanks and sorry about the confusion.
Mace
--- On Tue, 7/28/09, Brad Hinson bhin...@redhat.com wrote:
From: Brad Hinson bhin...@redhat.com
Subject: Re: Adding dasd technique
To: LINUX-390@VM.MARIST.EDU
Date: Tuesday, July 28, 2009, 12:48 PM
Bauer, Bobby (NIH/CIT) [E] wrote:
How do I use by-device-address? Don't find it on the
Redhat site nor did Google tell me much. Fstab is built from
the input of Anaconda when I build the server isn't it?
The /dev/disk/ directory contains links with other ways to
access the
DASD. For example, on my system:
# ls -ld /dev/disk/*
drwxr-xr-x 2 root root 480 Jul 15 19:22 /dev/disk/by-id
drwxr-xr-x 2 root root 60 Jun 25 15:13
/dev/disk/by-label
drwxr-xr-x 2 root root 380 Jul 15 19:22 /dev/disk/by-path
drwxr-xr-x 2 root root 60 Jul 15 17:12
/dev/disk/by-uuid
# ls /dev/disk/by-id/ccw-0X3D2C* -l
lrwxrwxrwx 1 root root 11 Jun 25 15:13
/dev/disk/by-id/ccw-0X3D2C -
../../dasda
lrwxrwxrwx 1 root root 12 Jun 25 15:13
/dev/disk/by-id/ccw-0X3D2C-part1
- ../../dasda1
lrwxrwxrwx 1 root root 12 Jun 25 15:13
/dev/disk/by-id/ccw-0X3D2C-part2
- ../../dasda2
You can use these in /etc/fstab, but in your case with LVM,
I don't
think it will help, since LVM entries in fstab are of the
form
/dev/{volume_group_name}/{logical_volume_name}.
Going back to the original issue, the reason the new disk
came up as
dasdg is because you're calling chccwdev/mkswap in
/etc/rc.local. As
Adam, Pat, and Mike pointed out, you should use
modprobe.conf for all
disks. Either:
options dasd_mod dasd=200-205,700-701
in which case any DASD you add after 701 will be
dasdh. Or you could do
something like:
options dasd_mod dasd=200-20f,700-701
The latter is a preallocation of device nodes. You
can add any DASD up
to 70f without needing to remake the initrd or rerun zipl.
-Brad
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu]
On Behalf Of Adam Thornton
Sent: Tuesday, July 28, 2009 10:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding dasd technique
On Jul 28, 2009, at 9:18 AM, Bauer, Bobby (NIH/CIT)
[E] wrote:
We are running Redhat V5 with z/VM V5.4 with all
3390 dasd. I need
to add another volume to one of my servers. I also
have 2 swap disk
defined using Sine Nomine's swapgen macro in the
profile exec for
the server and the mkswap and swapon commands in
rc.local:
If you're running swapgen then you don't need to
mkswap or swapon.
You should probably put dasd=200-205,700-701.
But you should also use the by-device-address form of
talking about
your dasd (rather than dasda, dasdb, and so on) in
/etc/fstab
precisely so you don't have to care as you add and
subtract devices,
as long as they stay at the same virtual addresses.
Also don't forget to rebuild your initrd after every
time you change
dasd configuration.
Adam
--
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
--
Brad Hinson bhin...@redhat.com
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
--
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: Adding dasd technique
LJ Mace wrote:
Am I missing something this isn't about the problem ,but helping me understan:
you said
options dasd_mod dasd=200-20f,700-701
The latter is a preallocation of device nodes. You
can add any DASD up
to 70f without needing to remake the initrd or rerun zipl.
Should that be 700-70f??
thanks and sorry about the confusion.
Mace
You could do that, too (preallocate devices for additional VDISK swap).
Depends on whether you're more likely to add ECKD DASD, VDISK swap, or
both in the future.
--- On Tue, 7/28/09, Brad Hinson bhin...@redhat.com wrote:
From: Brad Hinson bhin...@redhat.com
Subject: Re: Adding dasd technique
To: LINUX-390@VM.MARIST.EDU
Date: Tuesday, July 28, 2009, 12:48 PM
Bauer, Bobby (NIH/CIT) [E] wrote:
How do I use by-device-address? Don't find it on the
Redhat site nor did Google tell me much. Fstab is built from
the input of Anaconda when I build the server isn't it?
The /dev/disk/ directory contains links with other ways to
access the
DASD. For example, on my system:
# ls -ld /dev/disk/*
drwxr-xr-x 2 root root 480 Jul 15 19:22 /dev/disk/by-id
drwxr-xr-x 2 root root 60 Jun 25 15:13
/dev/disk/by-label
drwxr-xr-x 2 root root 380 Jul 15 19:22 /dev/disk/by-path
drwxr-xr-x 2 root root 60 Jul 15 17:12
/dev/disk/by-uuid
# ls /dev/disk/by-id/ccw-0X3D2C* -l
lrwxrwxrwx 1 root root 11 Jun 25 15:13
/dev/disk/by-id/ccw-0X3D2C -
../../dasda
lrwxrwxrwx 1 root root 12 Jun 25 15:13
/dev/disk/by-id/ccw-0X3D2C-part1
- ../../dasda1
lrwxrwxrwx 1 root root 12 Jun 25 15:13
/dev/disk/by-id/ccw-0X3D2C-part2
- ../../dasda2
You can use these in /etc/fstab, but in your case with LVM,
I don't
think it will help, since LVM entries in fstab are of the
form
/dev/{volume_group_name}/{logical_volume_name}.
Going back to the original issue, the reason the new disk
came up as
dasdg is because you're calling chccwdev/mkswap in
/etc/rc.local. As
Adam, Pat, and Mike pointed out, you should use
modprobe.conf for all
disks. Either:
options dasd_mod dasd=200-205,700-701
in which case any DASD you add after 701 will be
dasdh. Or you could do
something like:
options dasd_mod dasd=200-20f,700-701
The latter is a preallocation of device nodes. You
can add any DASD up
to 70f without needing to remake the initrd or rerun zipl.
-Brad
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu]
On Behalf Of Adam Thornton
Sent: Tuesday, July 28, 2009 10:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding dasd technique
On Jul 28, 2009, at 9:18 AM, Bauer, Bobby (NIH/CIT)
[E] wrote:
We are running Redhat V5 with z/VM V5.4 with all
3390 dasd. I need
to add another volume to one of my servers. I also
have 2 swap disk
defined using Sine Nomine's swapgen macro in the
profile exec for
the server and the mkswap and swapon commands in
rc.local:
If you're running swapgen then you don't need to
mkswap or swapon.
You should probably put dasd=200-205,700-701.
But you should also use the by-device-address form of
talking about
your dasd (rather than dasda, dasdb, and so on) in
/etc/fstab
precisely so you don't have to care as you add and
subtract devices,
as long as they stay at the same virtual addresses.
Also don't forget to rebuild your initrd after every
time you change
dasd configuration.
Adam
--
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
--
Brad Hinson bhin...@redhat.com
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
--
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
--
Brad Hinson bhin...@redhat.com
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
--
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
z Training: IBM System z Expo - Oct. 5-9, 2009 - Orlando
Cross-posted to IBM-MAIN, IBMVM, and Linux390 for those who are interested in technical training for System z, z/OS, z/VM, z/VSE, and Linux on System z. The next IBM conference for System z, IBM System z Expo, is open for enrollment and in case you didn't see an e-mail about it, there is an early bird discount of $300 (US) until July 31. IBM System z Expo October 5-9, 2009 Hilton Orlando (brand new) web: http://www.ibm.com/training/us/conf/systemz You'll enjoy updates and education on these favorite System z operating systems z/OS, z/VM, z/VSE and Linux on System z and concentrations on System z in general, systems storage, security, virtualization, performance, networking, and more. At a glance: The conference begins on Monday morning, Oct 5,with keynote sessions, followed by breakouts through Friday Oct 9 at noon. There is also a product expo with Monday and Tues evening receptions and Tues Wed after-lunch exhibit times so that you have time to visit with IBM System z 10 demoers, ISV and BP sponsors and exhibitors. Want to exhibit or sponsor ? Click the Sponsor/Exhibitor packages link on this page: http://www.ibm.com/training/us/conf/systemz Please look at a preliminary list of topics and abstracts on the web site, and please continue to visit the site as we're updating it on almost a weekly basis with revised sessions and abstracts. Click the sessions descriptions link off this page to see what is planned: http://www.ibm.com/training/us/conf/systemz We look forward to meeting you in Orlando. Regards, Your z Expo agenda architects Pam Christina, Glenn Anderson, and Julie Liesenfelt -- 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: Problems with SLES 11 and LVM
Did you CPFMTXA / dasdfmt all the 3390 dasd before installing Linux? -- Jay Brenneman -- 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: Problems with SLES 11 and LVM
Hi Jay Yes, I did that. When having not stressed the LV then it works fine. Only when it has higher activity on the volume this seems to happen. When I copy one big ISO file it is working ok. When there are several files such as coping the ISO to its directory structure as with installation of the SuSE Installation server this problem seems to happen. On Tue, Jul 28, 2009 at 9:04 PM, Robert J Brenneman bren...@gmail.comwrote: Did you CPFMTXA / dasdfmt all the 3390 dasd before installing Linux? -- Jay Brenneman -- 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 -- Best regards Florian Bilek -- 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: chccwdev never returning on SLES 11
On 7/28/2009 at 1:58 PM, Michael MacIsaac mike...@us.ibm.com wrote: -snip- + echo 'Setting device 0.0.21b7 offline' Setting device 0.0.21b7 offline + '[' '' '!=' '' ']' + echo 0 That's the line that is echoing a zero into the online pseudo file for the device. I would say it's time to get a real bug opened with Novell via your normal processes. Getting a dump first would probably be a good idea. Mark Post -- 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: yum-autoupdate on RHEL
Michael Grundy wrote: I've discovered this on RHEL5-clone on another platform. Looking at a RHEL 5.3 system, I don't see a yum-auto update. There is yum-updatesd, which can be controlled in the normal fashion: # chkconfig --list yum-updatesd yum-updatesd0:off 1:off 2:on3:on4:on5:on6:off yum-autoupdate is in Fedora. I don't know whether it can be removed, in SL removing it also removes yum. It seems the behaviour I see is specific to Scientific Linux 5. I'm generating some heat there, I don't see any justification for it in any likely environment for a RHEL clone. I for one don't want updates to any of my systems on Red Hat's say-so, and that's exactly what has been happening. A system like Microsoft's where one can opt-out would be fine. Opt-in would be better for EL IMV. -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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: Download directly to z/Linux server ?
Lionel Dyck wrote: Sigh - thanks - the use of shift-insert is not intuitive (guess rtfm would help :-) ) It's been around a long time, I used it in OS/2. -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
