Re: Root filesystem error switches to ReadOnly
Fargusson.Alan wrote: Unless this changed in 2.6 the block devices go through VFS, and the blocks get cached by the VFS layer. VFS only comes into play when a filesystem (on a block device) is mounted. If you access a block device directly (not via a path of the mountpoint) then VFS is not involved. The block device is a direct entry to the device driver, you are dealing with blocks and not filesystems at this level. The buffer cache may be used, but this is not filesystem aware, it just caches previously read/written blocks. The point remains that doing a dd of the /dev/dasdn while mounted can lead to a copy that is in a inconsistent state. mark -- 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: Support dates for IBM products on new releases of SLES
I can't speak for the products Marcy has listed, but there are factors that often prevent support from day 1: 1) The schedule is Novell's and not IBM's 2) The Schedule can slip even for beta releases causing testing delays. 3) IBM Testing is not complete until you have tested on a Novell GA release. 4) There have been last minute changes from Novell that caused confusion about what is GA (SLES9 SP4 found a major bug which caused a delay.) While all major vendors will of course be involved in the Beta testing of any new Novell release, I would think it reasonable to assume that any vendor may not fully certify/support a new Novell GA release for at least a few weeks following the GA release date, 2-6 depending on problems found. mark Stephen Frazier wrote: Normally, for most products, IBM tests them on the new release before the availability date. If it runs with no problems then it is supported from day 1. If they have to change something then support may be later. If it is easy to fix they may support it (with the fix) from day 1. Marcy Cortes wrote: Have to do some 2009 planning... How long is it typically between the availability of the next release of SLES (or RHEL for that matter) before IBM will support WAS, DB2, MQ Series on it? Marcy -- 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: List FAQ etc
Klein, Robert (NIH/CIT) [C] wrote: I recently joined this list. The welcoming email gave a couple of URLs for such things as FAQs, but when I tried to access the urls, I got a page not found message. If these pages still exist somewhere else, could someone please provide the new urls. Also, the owner of the list might want to update the welcoming email. Thanks. There should be a separate email address of the owner; some list owners listen, some don't. I think the owner of this list actually reads it, though he doesn't actually write very often. Generally 1. Be nice:- 3. Prune irrelevant material, as I just did. 4. On most lists, respond in context to the points you want to address rather than responding at the top, with the attendant risk of leaving readers guessing which point you're talking about. Venture off-topic carefully. Discussing a war in the middle east is risky, but you might get away with a reference or two to mainframes of the 60s and 70s. Oh, try to solve your problem(s) yourself first, and make it clear by describing what you have done. Links in my sig offer other advice on this. People on this list and others like it are here because it's fun and they like helping. Few, if anyone, are paid to help people here. Finally, a problem description like this, My computer won't boot, may well be ignored. People need details to make a sensible guess at what might be wrong. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Differece in RED Hat and Suse
Mark Post wrote: like YaST, and wish Red Hat had a similar one place to go to for administration functions. I've been arguing that one for years, before I'd even encountered YAST. Brad? I reckon that some of the RH admin tools are there just so RH can mark checkboxes, Got that. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Problem with chccwdev and SuSE SLES10 SP2
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 24.08.2008 16:53:44: When I do now a e.g. chccwdev -e 0.0.3210 it is working, I can use the disk. Then I do a unmount, chccwdev -d 0.0.3210 and a vmcp detach. Later, when I want to do a second time this exercise, chccwdev retruns a fail and a retcode 1. This is not only for this device but for any other I link and enable with chccwdev later. When I recycle the Linux Guest, it is working again one time. I suspect the 0.27 kernel but I have to prove this. Does somebody have the same expericene? This is a known kernel problem. A fix is available and should be integrated in the next kernel update. The reference Novell bugzilla number for the fix is 411871. Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on System z Development IBM Deutschland Research Development GmbH -- 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: IPL parms
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 22.08.2008 23:30:24: On 8/22/2008 at 4:45 PM, in message [EMAIL PROTECTED], Alan Altmark [EMAIL PROTECTED] wrote: -snip- That's the error you get when the virtual machine hasn't activated the integrated linemode console interface. I know this isn't (necessarily) your area of expertise, but do you have any idea how to activate that from Linux? (Or however it's done?) You can force the use of the linemode console while running under VM by putting 'conmode=sclp' on the kernel command line. Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on System z Development IBM Deutschland Research Development GmbH -- 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: IPL parms
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 22.08.2008 20:40:25: Interesting.. I grabbed that from the device drivers reference (maybe old link): download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l390dd03.pdf (p. 27, pdf p. 39) It mentions: To resolve this problem, the hardware console uses an escape character (%) under VM to distinguish between upper and lower case characters. This behavior and the escape character (%) are adjustable at build-time by editing the driver sources, or at run time by use of the ioctl interface. Note that this description of the hardware console does not apply to the zipl boot menu. For the latter, there's no way to specify upper-case letters as all input will be converted to lower-case. Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on System z Development IBM Deutschland Research Development GmbH -- 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: Distribution ages, was: Linux version
Well, for sure, some things stand out more when you look at the code on paper. Sometimes, scrolling up and down on a screen tends to obfuscate the code. This is more so (at least for me) with assembler code (which I'll admit to not knowing as well as C). Kevin From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Wooster Sent: Friday, August 22, 2008 1:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version I always liked doing my own keypunching -- and I can **still** code better if I scribble the corrections on a fanfold listing! (multiprocessing: two 360-30's with 14KB (!) DOS supervisors which everybody said was too big) Douglas Re: [LINUX-390] Distribution ages, was: Linux version Evans, Kevin R to: LINUX-390 08/22/2008 09:20 AM Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU Didn't you mean that someone else could make punching mistakes for you? Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Friday, August 22, 2008 8:39 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Distribution ages, was: Linux version Mark Perry wrote: Evans, Kevin R wrote: This is getting like Monty Python g. One guy says When we were young, we used to eat the leather from our shoes. The other guy says You had shoes?. OS/360 - some of you guys make me feel young, thanks ;-) You must be around 60, either that or your systems were old at the time ;-) I started on 370s (135,138,145,148,158,168 - 3033, 4341, 3081, 3084 etc.) This didn't seem the time to mention what I used before I was promoted (public service) to an IBM shop. Operating systems there were SCOPE, MSOS and MASTER. We wrote our assembler on punched cards and were happy to do so, And you try and tell the young people of today that . they won't believe you. I found coding sheets easier, then someone else could punch holes in cards. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [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 -- 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 attachment: image001.gif
Re: List FAQ etc
I don't believe that everyone believes in pruning out everything. Many people reply at the top. If for no other reason than replies can be kept in context. I don't want to start a war about email etiquette here, just to say that I believe that not everyone agrees with points 3 4 below. BTW, what happened to point #2? Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Monday, August 25, 2008 2:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: List FAQ etc Klein, Robert (NIH/CIT) [C] wrote: I recently joined this list. The welcoming email gave a couple of URLs for such things as FAQs, but when I tried to access the urls, I got a page not found message. If these pages still exist somewhere else, could someone please provide the new urls. Also, the owner of the list might want to update the welcoming email. Thanks. There should be a separate email address of the owner; some list owners listen, some don't. I think the owner of this list actually reads it, though he doesn't actually write very often. Generally 1. Be nice:- 3. Prune irrelevant material, as I just did. 4. On most lists, respond in context to the points you want to address rather than responding at the top, with the attendant risk of leaving readers guessing which point you're talking about. Venture off-topic carefully. Discussing a war in the middle east is risky, but you might get away with a reference or two to mainframes of the 60s and 70s. Oh, try to solve your problem(s) yourself first, and make it clear by describing what you have done. Links in my sig offer other advice on this. People on this list and others like it are here because it's fun and they like helping. Few, if anyone, are paid to help people here. Finally, a problem description like this, My computer won't boot, may well be ignored. People need details to make a sensible guess at what might be wrong. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [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: Distribution ages, was: Linux version
Evans, Kevin R wrote: Well, for sure, some things stand out more when you look at the code on paper. Sometimes, scrolling up and down on a screen tends to obfuscate the code. This is more so (at least for me) with assembler code (which I'll admit to not knowing as well as C). Code? We had hex dumps about 8+ inches thick (today there would probably be a company policy about lifting so much weight)- just tear and twist a corner for a bookmark (maybe with comment), and use a highlighter pen for the interesting data on a page. Of course the backside of the continuous sheet output could be used for disassembly/comments/diagrams etc. ;-) Then we would work out an amaspzap fix. Kids today... mark -- 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: List FAQ etc
Evans, Kevin R wrote: I don't believe that everyone believes in pruning out everything. Many people reply at the top. If for no other reason than replies can be kept in context. There are arguments for and against top or bottom replies. In this reply I have chosen below, but then I have pruned the whole email thread from your posting. There is the point, we are not exchanging emails, we are posting to a common thread within a mailing-list. When posting to a mailing list there is no need to re-post data that is already available within the mailing list. You only need to leave the relevant text that you wish to refer to. SNIPING is encouraged! With SNIPING and bottom replies you can read the whole post from top to bottom in a logical manner. If you can't recall the previous post, you can always refer back to the mailing list archives. mark -- 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: List FAQ etc
Actually, sniping is discouraged. Snipping is encouraged. :) MA On Mon, Aug 25, 2008 at 6:52 AM, Mark Perry [EMAIL PROTECTED]wrote: SNIPING is encouraged! mark -- 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: List FAQ etc
-Original Message- From: Linux on 390 Port On Behalf Of Mark Perry When posting to a mailing list there is no need to re-post data that is already available within the mailing list. You only need to leave the relevant text that you wish to refer to. SNIPING is encouraged! Er, um, more than just a spelling faux pas, sniping is an entirely different word than snipping. :-) -jc- -- 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: List FAQ etc
Yes, I know there are arguments for and against. I wasn't trying to start a war (it's been discussed before ad nauseum). I thought that a newbie poster might not realize this. In my case, I tend to read a post, then reply or not, then delete the email. Therefore to me, I find it easier to be able to go back through and see the original post sometimes which one cannot do if it has been snipedg. Sometimes these posts can last for over a week...I can't always remember the original posted question. Plus, Outlook defaults to reply at the top! Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Monday, August 25, 2008 6:53 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: List FAQ etc Evans, Kevin R wrote: I don't believe that everyone believes in pruning out everything. Many people reply at the top. If for no other reason than replies can be kept in context. There are arguments for and against top or bottom replies. In this reply I have chosen below, but then I have pruned the whole email thread from your posting. There is the point, we are not exchanging emails, we are posting to a common thread within a mailing-list. When posting to a mailing list there is no need to re-post data that is already available within the mailing list. You only need to leave the relevant text that you wish to refer to. SNIPING is encouraged! With SNIPING and bottom replies you can read the whole post from top to bottom in a logical manner. If you can't recall the previous post, you can always refer back to the mailing list archives. mark -- 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
Rename vol label
Hi all, How the volume label can be changed for the Z/linux machine which is cloned . Thanks all [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: List FAQ etc
Mary Anne Matyaz wrote: Actually, sniping is discouraged. Snipping is encouraged. :) http://wilk4.com/humor/doh.htm mark -- 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: List FAQ etc
Evans, Kevin R wrote: Sometimes these posts can last for over a week...I can't always remember the original posted question. You do look at the archives by thread, right? example: http://www.mail-archive.com/linux-390@vm.marist.edu/ mark -- 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: List FAQ etc
I rarely look at the archives. I check my email constantly and handle any replies directly from my inbox. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Monday, August 25, 2008 8:55 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: List FAQ etc Evans, Kevin R wrote: Sometimes these posts can last for over a week...I can't always remember the original posted question. You do look at the archives by thread, right? example: http://www.mail-archive.com/linux-390@vm.marist.edu/ mark -- 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: List FAQ etc
-Original Message- From: Linux on 390 Port On Behalf Of Mark Perry Mary Anne Matyaz wrote: Actually, sniping is discouraged. Snipping is encouraged. :) http://wilk4.com/humor/doh.htm Previously spelled Duh, uttered most often by Moose in the Archie comic books. -jc- -- 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: Two Different YaST2 Control Center displays
No. They still look different. System A shows all the elements on a scrolling screen. System B shows just the elements for the active category. System A gets these messages: # yast2 lnxm500:~ # ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3492:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:3492:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name ALSA lib conf.c:3492:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3961:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2111:(snd_pcm_open_noupdate) Unknown PCM default System B does not get these messages. Both work, but system B looks better and is faster. I can send pictures if you like. Ray Mrohs -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, August 21, 2008 5:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Two Different YaST2 Control Center displays On 8/6/2008 at 3:04 PM, in message [EMAIL PROTECTED] V, Mrohs, Ray [EMAIL PROTECTED] wrote: We have 2 SLES10 SP1 servers. When I start yast2 on the first linux, the xterm screen shows a long scrolling list of selections, and its slow. On the second linux, the Control Center display is compact and all on one screen, and its faster. Where should I look for the cause of the differences? Did you ever get this figured out? While I can't say I recommend running X or VNC applications on System z, they should still work properly. Mark Post -- 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: List FAQ etc
I don't believe that everyone believes in pruning out everything. Many people reply at the top. If for no other reason than replies can be kept in context. I don't want to start a war about email etiquette here, just to say that I believe that not everyone agrees with points 3 4 below. I think more of us have simply given up trying to get people to do 3 4. Most of the modern workstation mail readers make it quite difficult to do in a reasonable manner, and those of us still reading mail with MAILBOOK and Pine (with proper mail editors like Emacs) just can't stem the tide. There are times where I really miss low bandwidth communications, where the size of transfers actually mattered. That drove most of the reasoning behind pruning out unnecessary stuff, and I think it helped the clarity of the conversation. But, I'm old and cranky now, so I'll shut up. -- db -- 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: Rename vol label
How the volume label can be changed for the Z/linux machine which is cloned . Use minidisks. Then you don't have to change 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: Rename vol label
David's is the best answer, but if you must, use fdasd -l to change them. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, August 25, 2008 8:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Rename vol label How the volume label can be changed for the Z/linux machine which is cloned . Use minidisks. Then you don't have to change 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 -- 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: Rename vol label
If you have a zOS system that can access your drives, then you can have the zOS systems programmer clip your volume serial number. David Boyes wrote: How the volume label can be changed for the Z/linux machine which is cloned . Use minidisks. Then you don't have to change 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 -- 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: Rename vol label
ICKDSF on VM can do it too. If you're cloning, though, you *want* the volume ids that the guest sees to be the same, so that they truly ARE clones. The only way to do that is to give the guest minidisks rather than full volumes. Losing 150K of disk space vs having to hand-hack each guest, or figure out how to automate it -- it's a no brainer. Disk is cheap; people aren't. -- 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
100 Vim commands every programmer should know
Fairly nice quick reference type summary. http://www.catswhocode.com/blog/web-development/100-vim-commands-every-p rogrammer-should-know-11 -- 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: Differece in RED Hat and Suse
John Summerfield wrote: Mark Post wrote: like YaST, and wish Red Hat had a similar one place to go to for administration functions. I've been arguing that one for years, before I'd even encountered YAST. Brad? I reckon that some of the RH admin tools are there just so RH can mark checkboxes, Got that. (treading carefully as to not spark YaST a holy war..) Red Hat evaluated YaST long ago when it was proprietary, but by the time it was open sourced, we had written Anaconda and decided to fully focus on it. Since then, we've considered some all-in-one tools like system-config-control: http://www.indianoss.org/modules/wfdownloads/viewcat.php?cid=10 which is a front-end to the system-config-* GUIs, but this hasn't made it to RHEL. I haven't used YaST much recently, but it seems like a good tool. But we don't want to just add a YaST clone to RHEL (YaYaST?) :) Instead, we're focusing on our current system-config tools, like system-config-network for example, which got a huge z/Linux update for RHEL 5.2. -Brad -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Brad Hinson [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL parms
On 8/25/2008 at 4:12 AM, in message [EMAIL PROTECTED], Peter 1 Oberparleiter [EMAIL PROTECTED] wrote: Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 22.08.2008 23:30:24: On 8/22/2008 at 4:45 PM, in message [EMAIL PROTECTED], Alan Altmark [EMAIL PROTECTED] wrote: -snip- That's the error you get when the virtual machine hasn't activated the integrated linemode console interface. I know this isn't (necessarily) your area of expertise, but do you have any idea how to activate that from Linux? (Or however it's done?) You can force the use of the linemode console while running under VM by putting 'conmode=sclp' on the kernel command line. Hmm. After one test I can definitively say that is a far less attractive option than using 3215 _or_ 3270 mode for the console. I really _don't_ want to have to prepend #cp vi vmsg to every console input from boot until shutdown. Ugh. Might I suggest that the commands and device driver manual be updated to _not_ show the issuing of bash commands as the examples of how to use this facility, and add some of the downsides? From what I can see, this is only really useful at the zipl boot menu. After that, no sane person would want to have to deal with it. Mark Post -- 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: IPL parms
On 8/25/2008 at 4:24 AM, in message [EMAIL PROTECTED], Peter 1 Oberparleiter [EMAIL PROTECTED] wrote: Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 22.08.2008 20:40:25: Interesting.. I grabbed that from the device drivers reference (maybe old link): download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l390dd03.pdf (p. 27, pdf p. 39) It mentions: To resolve this problem, the hardware console uses an escape character (%) under VM to distinguish between upper and lower case characters. This behavior and the escape character (%) are adjustable at build-time by editing the driver sources, or at run time by use of the ioctl interface. Note that this description of the hardware console does not apply to the zipl boot menu. For the latter, there's no way to specify upper-case letters as all input will be converted to lower-case. Could that also be put (somewhere) in the commands and device drivers manual? Until you posted this, I was under the same impression that Brad was that this worked in all cases, _especially_ at the zipl boot menu. Mark Post -- 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: List FAQ etc
On Mon, 25 Aug 2008, David Boyes wrote: Hi, I don't believe that everyone believes in pruning out everything. Many people reply at the top. If for no other reason than replies can be kept in context. I don't want to start a war about email etiquette here, just to say that I believe that not everyone agrees with points 3 4 below. I think more of us have simply given up trying to get people to do 3 4. Most of the modern workstation mail readers make it quite difficult to do in a reasonable manner, I have found that it's corporate setups that make this hard as most MUAs still support proper quoting. and those of us still reading mail with MAILBOOK and Pine (with proper mail editors like Emacs) just can't stem the tide. There are times where I really miss low bandwidth communications, where the size of transfers actually mattered. That drove most of the reasoning behind pruning out unnecessary stuff, and I think it helped the clarity of the conversation. But, I'm old and cranky now, so I'll shut up. So what about a good old usenet news group instead of a mailing list? Are news readers better? I mean I have no idea. rtin 's the most modern I know (ignoring the netscape3 I have forgotten about). We could also do the weekly FAQ post there (not that we could not do here if someone would volunteer to write it), to come back to the original subject. Cheers, Bjoern -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. -- 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
APAR Opened and workaround
FYI, an apar has been opened (below) and a workaround is presented for an XRC suspend that occurs when formatting a VM minidisk. Mary Anne APAR= OA26125 SER=MS MSGANTX5104E XRC ANTX5104E RC=0901 DURING FORMAT OF A VM MINIDISK STAT= OPEN FESN0565517- CTID= TU0260 ISEV= 2 SB08/08/13 RC08/08/14 CL PD SEV= 2 PE= TYPE= F RCOMP= 5695DF117SYSTEM DATA MOV RREL= R1K0 FCOMP= PFREL= F TREL= T ACTION= SEC/INT= N DUP/ USPTF= PDPTF= DUPS 0 ERROR DESCRIPTION: ANTX5104E RC=0901 occurs while formatting a VM minidisk that is a primary in a XRC session, where XRC parameter PavVolumes is greater than 1. KEYWORDS: ANTX5104E RC=0901 NRFITF NRF NO RECORD FOUND ITF INVALID TRACK FORMAT MSGANTX5104E RC=901 RC0901 RC901 LOCAL FIX: 1. Change the PavVolumes parameter to 1 in the XRC parmlib member for future sessions, and use the XSET command to change the value of PavVolumes to 1 for the current sessions. - or - 2. Remove the pair from the XRC session before performing a format, then readd the pair after the format is complete. (recommended) -- 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
Self inflicted bad file system
I recently did a lvreduce on a 4.5GB logical volume by 2GB and created a second logical volume. I never got around to recreating the file system on the original logical volume. This weekend when the system got shutdown it died on the restart because of this. It is running fsck and I have been looking at and clearing screens full of y for hours. How long might this take and what are my options for punting. I can recover the data so that isn't a concern. -- Bill Dodge email: [EMAIL PROTECTED] Phone: (703)627-2455 If you don't know where you are going, any road will take you there. Lewis Carroll If you don't know where you are, a map won't help Unknown -- 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: Self inflicted bad file system
On 8/25/2008 at 1:28 PM, in message [EMAIL PROTECTED], Bill Dodge [EMAIL PROTECTED] wrote: I recently did a lvreduce on a 4.5GB logical volume by 2GB and created a second logical volume. I never got around to recreating the file system on the original logical volume. This weekend when the system got shutdown it died on the restart because of this. It is running fsck and I have been looking at and clearing screens full of y for hours. How long might this take and what are my options for punting. I can recover the data so that isn't a concern. If this is _not_ your root file system _and_ you get the zipl boot menu when you start up your system, you should be able to boot into runlevel 1, then do a mkfs on the logical volume. Then do a telinit 3 to get into run level 3 and restore from backup. If this _is_ your root file system, then you're looking at booting from the installation kernel, activating your DASD, getting to a shell, and running the mkfs command. Mark Post -- 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 confusion
On 8/24/2008 at 8:28 AM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: On Sunday 24 Aug 2008, Mark Post wrote: On 8/23/2008 at 12:26 PM, in message So, what does ls -l /dev/tty* show you? Also, what does your hercules configuration file look like? # ls /dev/tty* /dev/tty /dev/tty10 /dev/ttyS1 /dev/ttyS3 /dev/ttyS5 /dev/ttyS7 /dev/tty1 /dev/ttyS0 /dev/ttyS2 /dev/ttyS4 /dev/ttyS6 /dev/ttysclp0 Ok, I got things working on my hercules system, but I'm not sure it's going to satisfy you. From what I can tell, you can't get a 3270 effect on the actual hercules console. You have to use a TN3270 connection to the TCP/IP port specified by CNSLPORT. The kernel that comes pre-SP1 does _not_ compile the 3270 support into the kernel, but as modules. This gets fixed later on, as I indicated previously. There's a bug in hercules that prevents me from booting up a SP1 kernel or later, so I'm not entirely sure just what level fixed it. If you're forced into running a pre-SP1 kernel as well, then there are a couple of things you'll want/need to do: - Update /etc/zipl.conf so that you have insmod=tty3270 on the kernel parm line. - Update /etc/sysconfig/kernel to add tty3270 to the list of modules to be built into the initrd. - Re-run mkinitrd. - Re-run zipl. - Update /etc/init.d/boot.local to add this command: /sbin/chccwdev -e 0.0. where is the device number assigned to your console. In your particular case, that would be /sbin/chccwdev -e 0.0.001f - chkconfig boot.local on - Make sure /etc/inittab still has a mingetty entry for /dev/tty0.0.001f in it. - Halt your Linux system - Connect to port 3270 (or whatever you have defined for CNSLPORT) with your TN3270 emulator. You should see the hercules greeting screen - Boot your linux system At some point, you should see the login prompt on your TN3270 session. Mark Post -- 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: Two Different YaST2 Control Center displays
-Original Message- From: Mrohs, Ray [mailto:[EMAIL PROTECTED] No. They still look different. System A shows all the elements on a scrolling screen. System B shows just the elements for the active category. System A gets these messages: # yast2 lnxm500:~ # ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' On systems A and B, what is the difference in output from these two commands, if any? echo $TERM chkconfig alsasound ok r. -- 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: Self inflicted bad file system
Thanks Mark. Sometimes the pain from the bullet in the foot makes it hard to see the simple solutions. Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote: On 8/25/2008 at 1:28 PM, in message [EMAIL PROTECTED], Bill Dodge [EMAIL PROTECTED] wrote: I recently did a lvreduce on a 4.5GB logical volume by 2GB and created a second logical volume. I never got around to recreating the file system on the original logical volume. This weekend when the system got shutdown it died on the restart because of this. It is running fsck and I have been looking at and clearing screens full of y for hours. How long might this take and what are my options for punting. I can recover the data so that isn't a concern. If this is _not_ your root file system _and_ you get the zipl boot menu when you start up your system, you should be able to boot into runlevel 1, then do a mkfs on the logical volume. Then do a telinit 3 to get into run level 3 and restore from backup. If this _is_ your root file system, then you're looking at booting from the installation kernel, activating your DASD, getting to a shell, and running the mkfs command. Mark Post -- 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 -- Bill Dodge email: [EMAIL PROTECTED] Phone: (703)627-2455 If you don't know where you are going, any road will take you there. Lewis Carroll If you don't know where you are, a map won't help Unknown -- 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 confusion
On Tuesday 26 Aug 2008, Mark Post wrote: Ok, I got things working on my hercules system, but I'm not sure it's going to satisfy you. From what I can tell, you can't get a 3270 effect on the actual hercules console. You have to use a TN3270 connection to the TCP/IP port specified by CNSLPORT. Obviously, that's what I have been doing. The kernel that comes pre-SP1 does _not_ compile the 3270 support into the kernel, but as modules. This gets fixed later on, as I indicated previously. There's a bug in hercules that prevents me from booting up a SP1 kernel or later, so I'm not entirely sure just what level fixed it. The kernel started using a Diagnose instruction not supported by Hercules. The problem is fixed in the CVS code. If you're forced into running a pre-SP1 kernel as well, then there are a couple of things you'll want/need to do: - Update /etc/zipl.conf so that you have insmod=tty3270 on the kernel parm line. - Update /etc/sysconfig/kernel to add tty3270 to the list of modules to be built into the initrd. - Re-run mkinitrd. - Re-run zipl. I am now using the same kernel as you: 2.6.16.54-0.2.8-default. I now see # zgrep 3270 /proc/config.gz CONFIG_TN3270=y CONFIG_TN3270_TTY=y CONFIG_TN3270_FS=y CONFIG_TN3270_CONSOLE=y which shows all the modules are built-in. - Update /etc/init.d/boot.local to add this command: /sbin/chccwdev -e 0.0. where is the device number assigned to your console. In your particular case, that would be /sbin/chccwdev -e 0.0.001f This is the critical point. I made this change (and nothing else) and then then it all 'Just Worked (TM). Dave Jones sent me a copy of ned which installs without problems. However, it seems you must code; ned -T /dev/tub0.0.001f filename This has been a magnificent effort on your part, Mark. Hopefully it has helped people with more funds at their disposal than me. I guess that we are all a bit more enlightened about a not very well documented feature. Now to graft the technique onto Gentoo... Cheers -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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: Differece in RED Hat and Suse
Brad Hinson wrote: John Summerfield wrote: Mark Post wrote: like YaST, and wish Red Hat had a similar one place to go to for administration functions. I've been arguing that one for years, before I'd even encountered YAST. Brad? I reckon that some of the RH admin tools are there just so RH can mark checkboxes, Got that. (treading carefully as to not spark YaST a holy war..) Red Hat evaluated YaST long ago when it was proprietary, but by the time it was open sourced, we had written Anaconda and decided to fully focus on it. Since then, we've considered some all-in-one tools like system-config-control: http://www.indianoss.org/modules/wfdownloads/viewcat.php?cid=10 which is a front-end to the system-config-* GUIs, but this hasn't made it to RHEL. I haven't used YaST much recently, but it seems like a good tool. But we don't want to just add a YaST clone to RHEL (YaYaST?) :) Instead, we're focusing on our current system-config tools, like system-config-network for example, which got a huge z/Linux update for RHEL 5.2. It's not YAST that's important, it's the idea. Yast is much more than an installer, and it's specially nice that if one tries to configure (say) a web server and the needed software's not installed, it offers to install it. Mandrake 7 or so had a similar idea, there was a KDE folder-like object containing the configuration tools gnome-control-center, control-centre implement the same idea for GNOME and KDE respectively, Apple's System Preferences, Windows' Control Panel all provide a centralised set of configuration tools. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: List FAQ etc
Evans, Kevin R wrote: I don't believe that everyone believes in pruning out everything. Many people reply at the top. If for no other reason than replies can be kept On most lists, top replies attract flames. in context. I don't want to start a war about email etiquette here, just to say that I believe that not everyone agrees with points 3 4 below. If you replied in context, I'd not need to scroll down to see what you're talking about. BTW, what happened to point #2? Data check. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: List FAQ etc
Evans, Kevin R wrote: Yes, I know there are arguments for and against. I wasn't trying to start a war (it's been discussed before ad nauseum). I thought that a newbie poster might not realize this. In my case, I tend to read a post, then reply or not, then delete the email. Therefore to me, I find it easier to be able to go back through and see the original post sometimes which one cannot do if it has been snipedg. Sometimes these posts can last for over a week...I can't always remember the original posted question. Plus, Outlook defaults to reply at the top! OTOH I don't delete one by one, I have a view that only shows threads containing unread. If I want to, I can create a filter that deletes (or moves to another folder) read mail that is older than some number of days, 7, 70, 170, 370 - my choice, and I find that's easier than deleting individual messages. I keep stuff around because I find it convenient to do so. Starting at the top, to choose points to reply to is sensible. I don't trust any email client to decide where I should start my reply. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: List FAQ etc
David Boyes wrote: There are times where I really miss low bandwidth communications, where the size of transfers actually mattered. That drove most of the Size still matters; until I moved house a year ago, I was pulling 4 Gbytes/month through my modem, and I really begrudged those who insist in padding out their replies by including an alternative, HTML version. reasoning behind pruning out unnecessary stuff, and I think it helped the clarity of the conversation. But, I'm old and cranky now, Me to. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Linux on Debian
Hi. I posted this to the debian-s390 list, but so far no one there has bitten. Can anyone here help me? --- Can anyone out there give me a little nudge in the right direction for getting Debian running on a Z9 in an LPAR? I have tried both Etch and Lenny without any success. I am trying to install from a tape image that I can IPL. I have had not problems in creating the tape image, or in getting it to IPL. The problem has come in with the network adapter. With Etch, when the kernel boots from tape, no network adapters seem to be detected. With Lenny, I get farther, but the network adapter that I need to use still does not appear to get detected. The adapter that I need to use is an OSA adapter in LCS mode. Lenny detects another OSA adapter on the system that is running in QDIO mode, but I cannot use that one because it does not have connectivity to the world. I cannot seem to come up with the right kernel parameters for the kernel parameter file to make it load the driver for the OSA adapter in LCS mode. The installer does not detect the LCS adapter, and that is not even a choice presented to me by it. I was able to get a Slackware kernel to find the OSA adapter (the one in LCS mode), but the kernel parameters (or how I need to specify them) seem to be different, because the parameters that worked with Slackware got me nowhere with Debian. As I initially asked, can someone nudge me in the right direction? I have read through what documentation that I can find looking for the answer, to no avail. Tom Delany -- 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: Linux on Debian
On Aug 25, 2008, at 7:57 PM, Tom Delany wrote: Hi. I posted this to the debian-s390 list, but so far no one there has bitten. Can anyone here help me? --- Can anyone out there give me a little nudge in the right direction for getting Debian running on a Z9 in an LPAR? ... The adapter that I need to use is an OSA adapter in LCS mode. REALLY? I'mamazed that you can get an LCS OSA on a z9. Tell me more about this OSAlike, how did it get in a z9? Adam -- 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 confusion
On 8/25/2008 at 7:38 PM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: -snip- The kernel started using a Diagnose instruction not supported by Hercules. The problem is fixed in the CVS code. So I discovered. Getting the CVS code to build is another matter. When I tried to run autoconf, it barfed on a number of things in configure.ac, resulting in an unusable configure script. Mark Post -- 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 confusion
On 8/25/2008 at 7:38 PM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: On Tuesday 26 Aug 2008, Mark Post wrote: -snip- - Update /etc/init.d/boot.local to add this command: /sbin/chccwdev -e 0.0. where is the device number assigned to your console. In your particular case, that would be /sbin/chccwdev -e 0.0.001f This is the critical point. I made this change (and nothing else) and then then it all 'Just Worked (TM). That should not be necessary on a kernel with all the 3270 support compiled in. It may simply be that you need to add conmode=3270 to your parameters in /etc/zipl.conf and re-run zipl. Since I can't get the CVS version of hercules to build, I cannot verify that. Mark Post -- 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: Linux on Debian
On 8/25/2008 at 9:14 PM, in message [EMAIL PROTECTED], Adam Thornton [EMAIL PROTECTED] wrote: -snip- I'mamazed that you can get an LCS OSA on a z9. Tell me more about this OSAlike, how did it get in a z9? They can be configured to be in QDIO or LCS mode. Few people use the latter, however. For those that do, getting them to work with Linux has always been a pain, from what I can tell. Mark Post -- 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: linuxvm.org down ?
Mark Post wrote: I guess that, after all, I'll have to figure out git ! You could just send the diff to the Linux Kernel Mailing List (LKML). Learning git wasn't that hard ;).. I wanted to have a properly formatted and possibly retrievable patch ready.. (ok.. The patch was a 1 liner.. but still) .. now.. Actually, I found out (still learning) that posting to LKML by itself is usually not enough (although sending a copy to LKML for the record seems to be the Right Thing(tm) to do).. It would have been better and faster if I had also sent it to the maintainer (Martin Schwidefsky) and the linux-s390 ML too.. Lesson : RTFM Ivan ! (for that matter Documentation/SubmittingPatches.txt).. Hopefully, Frans Pop picked it up, forwarded to the right people, the patch was reviewed, Stefan Weinhuber found an even better solution and.. Voila ! A fix is in Linus' 2.6.27-rc4-git4[1] (so it should make into 2.6.27, and possibly 2.6.26 and 2.6.25 (when the problem was introduced [1]) since it was CC'd to stable too).. Thanks, --Ivan [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=49fd38bdaa96f093fcad3176a781a4d0de8f8602 -- 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 confusion
Mark Post wrote: Since I can't get the CVS version of hercules to build, I cannot verify that. Uh ? What's wrong with it ? (if you don't mind telling me of course !) --Ivan -- 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 confusion
On Tuesday 26 Aug 2008, Mark Post wrote: - Update /etc/init.d/boot.local to add this command: /sbin/chccwdev -e 0.0. where is the device number assigned to your console. In your particular case, that would be /sbin/chccwdev -e 0.0.001f This is the critical point. I made this change (and nothing else) and then then it all 'Just Worked (TM). That should not be necessary on a kernel with all the 3270 support compiled in. It may simply be that you need to add conmode=3270 to your parameters in /etc/zipl.conf and re-run zipl. Since I can't get the CVS version of hercules to build, I cannot verify that. Well, before it didn't work, now, after adding the chccwdev command, it does. -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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
