Hi Mark, Actually, I liked the "good old days" of VM (prior to SES) better. You simply accessed your disks (source, PUT, local mods, object code) and could just FILELIST by module name, or by PTF number (it was the filetype). I don't need all the overhead of SES and have never really liked it. Besides, when you build a text deck on VM there SHOULD be comments in the text showing which PTF's were applied, so you can usually look right in the object text deck to see what's been applied.
Just my opinion, I know a lot of people (now!) love SES. I've just never really become one of them. Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-3123 [EMAIL PROTECTED] -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 10:11 AM To: [EMAIL PROTECTED] Subject: Re: Samba causes kernel to abend I can hear the boos and hisses already, but this is where something like SMP/E and SES comes in handy. This reminds me of the bad old days of VM when the only way to figure out what fixes you had on was to look at the source code files. Ugh. Mark Post -----Original Message----- From: Michael MacIsaac [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 9:41 AM To: [EMAIL PROTECTED] Subject: Re: Samba causes kernel to abend > How can I tell what patches are already on if any? Hmm - good question - write it down somewhere and don't lose that paper :)) (that is only slightly sarcastic) A few more hints: 1) The command uname -a or more specifically uname -v tells you when the kernel was last rebuilt: # uname -v #1 SMP Fri Nov 23 19:45:36 CET 2001 2) SuSE has the directory /usr/src/linux-2.4.7/Documentation/s390 which has the files: # ls *.readme linux-2.4.7-s390-1.readme linux-2.4.7-s390-kerntypes.readme linux-2.4.7-s390-2.readme linux-2.4.7-s390.readme >From this we inferred that patches 0, 1 and 2 are applied 3) Look for patch files in /usr/src - of course this does not tell you if they have been applied or if the kernel has been rebuilt. # ls /usr/src/*.diff /usr/src/linux-2.4.7-s390-3.diff /usr/src/linux-2.4.7-s390-4.diff Then you can at least try to apply the diffs to see if they've already been applied. There's gotta be a more scientific way - I defer to the more powerful wizards on this list. -Mike MacIsaac, IBM [EMAIL PROTECTED] (845) 433-7061
