XEN. Interesting, following the VMWARE thread
Just saw this on /. http://developers.slashdot.org/article.pl?sid=03/10/02/1232235mode=nestedtid=106tid=126tid=156tid=185 (ewww, watch for wrap or skip to the real info) The Xen virtual machine monitor: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ - Mike
Re: CPU Limit
On Wed, Oct 01, 2003 at 03:19:59PM -0700, Wolfe, Gordon W wrote: How does one display running processes to see what the priority is? top shows it, or I like `ps -eflH` - Mike
Re: OT: Bumper Sticker for Linux users:
On Thu, Jul 24, 2003 at 03:23:14PM -0500, McKown, John wrote: Since I've already wasted your bandwidth, here are some more: Prepping for SHARE are we? Linux Bumperstickers sung to the tune of... (Some Called It Durn Silly)
Public Review for LSB arch specs for s390 and s390x
Just saw this on lwn: http://www.linuxbase.org/modules.php?name=Newsfile=articlesid=9 Thanks Mike -- Thou shalt not commit adulthood
The Hitchhiker's Guide to the Mainframe
New Mainframe article up on AceHardware.com, nothing most folks here don't already know. More interesting that it was on slashdot this morning: http://www.aceshardware.com/read.jsp?id=5318 Thanks Mike -- Thou shalt not commit adulthood
URL CORRECTION - Hitchhiker's guide to the mainframe
D'oh! I wasn't paying attention and posted the last page of the article. Here's the right url: http://www.aceshardware.com/read.jsp?id=5316 Thanks Mike -- Thou shalt not commit adulthood
dprobes and LTT paper available
Dynamic Probes (dprobes) is a tool that can be used to insert software probes, dynamically into executing code modules. Linux Trace Toolkit (ltt) is a suite of tools designed to extract program execution details from the Linux operating system and interpret them. dprobes can augment standard LTT tracing by logging events when a probe fires. The question often comes up How do we configure them to work together? and often times the answer required fixing up patches that didn't work together that nicely. To address this we've written a paper on configuring SLES-7 with dprobes and LTT (with pointers to patches that work together). Available online or in pdf format at: http://www-124.ibm.com/linux/pubs/?project_id=28 More information on dprobes can be found at: http://www-124.ibm.com/developerworks/oss/linux/projects/dprobes/ More information on LTT can be found at: http://www.opersys.com/LTT/index.html Thanks Mike -- Michael Grundy - [EMAIL PROTECTED] http://www.ibm.com/servers/eserver/zseries/os/linux/ldt/
R+D Journal
Just got the latest IBM Journal of Research and Development in the mail and it's the IBM eServer z900 issue! Some articles on the web: http://researchweb.watson.ibm.com/journal/rd46-45.html Thanks Mike -- If we blow up, whatever's left of me is kicking your butt!
Re: but is it right?
/lib64 was mentioned in the Linux Filesystem Standard as an example in footnote 12 from section 3.10 /libqual. Here's a link: http://www.pathname.com/fhs/pub/fhs-2.2.pdf Hope that helps Mike
[Announce] Dynamic Probes v3.6.3
Dynamic Probes v3.6.3 is released. Dynamic Probes is a generic and pervasive debugging facility that will operate under the most extreme software conditions such as debugging a deep rooted operating system problem in a live environment. Highlights of v3.6.3 include support for ppc, ppc64 and s390x architectures. Available at the project website: http://oss.software.ibm.com/developerworks/opensource/linux/projects/dprobes/ Thanks Mike Michael Grundy - [EMAIL PROTECTED] http://www.ibm.com/servers/eserver/zseries/os/linux/ldt/
Re: 2.4.17 Upgrade Problem
On Wed, Jul 03, 2002 at 10:47:09AM -0400, Geyer, Thomas L. wrote: I am trying to upgrade my SLES 2.4.7 kernel to 2.4.17. I have followed the procedure in the HOW-TO from linuxvm.org and in the Linux on zSeries and S390: Systems Management Redbook. When I try to boot the new kernel I get the following errors: Parallelizing fsck version 1.19a (13-Jul-2000) fsck.ext2: No such file or directory while trying to open /dev/dasdb1 It sounds like you have devfs enabled, I believe it is the default and a common stumbling block (I do it all the time). The easiest way to upgrade a SuSE kernel is to grab the config file from the original system by running the following in your source directory, e.g /usr/src/linux : gzip -dc /proc/config.gz .config This will give you the config of the running SuSE kernel, note that once you move to a kernel.org kernel you won't have the config.gz patch anymore. When I work with SLES-7 I like to create a separate directory in /boot for each new kernel I'm working with. Example: the default kernel is in /boot/k_deflt (or close to that, sorry my machines are down for the holiday) with /boot/kernel symlinked to the actual directory. So I'll create something like /boot/k_test match the files from my kernel tree into that directory, just like the default. So you wind up with image, listing, .config, System.map and maybe there were more. Then you just have to: rm /boot/kernel and ln -s /boot/k_test /boot/kernel Once this is done run zipl without any options. The *really* nice part of this is if I make a non-booting kernel recovery becomes three steps: 1) mount the drive on another system (or boot off installation media) 2) re-link /boot/kernel to a working kernel 3) run zipl (chrooted to the drive is best) We have a paper on installing DProbes and LTT that details the steps we use for installation and recovery. Of course, I don't have a copy available right now, as we are updating it to reflect changes in the new version of dprobes and the release version of LTT. I'll post a link as soon as we have it up. Hope that helps. Mike (from home, on vacation, why am I reading my mail?)
Re: Putting current in register
On Fri, Jun 21, 2002 at 12:23:19AM -0400, Pete Zaitcev wrote: PER appears to be used, I am not sure if that's actually the case. PER is definately used. PTRACE. DProbes uses it as well for single stepping the original instruction after a probe point is handled. Thanks Mike
Re: libpcap for S/390
On Thu, May 30, 2002 at 12:48:17PM -0400, Kittendorf, Craig wrote: Anyone install libpcap on Linux/S290? If so, where did you get the package and what is involved to install it? We have SuSE 7.0 install in an LPAR. Hi Craig - Like Mark said, it comes on that version of SuSE. It works ok, but you might want to upgrade to a newer version if you want to use Ethereal or anything that uses the callback interface for packet traces. There are some issues with older versions, not really bugs, just differences of opinion between some apps and the libs ;-) SuSE 7.0 also shipped with a libpcapn, which I think was a patched version of libpcap. I moved up to the latest version so Ethereal would work better. Here's a paper I wrote on the subject: http://www-1.ibm.com/servers/eserver/zseries/os/linux/ldt/netdebug.html Also, your previous question about promiscuous copy is answered in the paper (Sorry, I missed that question when you asked before) Hope that helps! Mike -- I don't need no booze or drugs I just chug-a-lug-o my coffee mug
Re: DevWorks CDs
On Tue, Apr 02, 2002 at 04:25:13PM -0500, William Raffloer wrote: I've got these CD's for Linux DevWorks. Does anyone have this?. When I look at the hardware reuirements for some of the software I am not sure what I should install for Linux390. I think you might have the IBM Software Evaluation Kit for Linux from the DeveloperWorks Toolbox ( http://www-106.ibm.com/developerworks/toolbox/ ) or some variation of the same. The packages are for Intel and won't work on S/390. Mike
