LSB Workgroup Meeting: Dec 10, 2003

RSVP

• George Kraft, IBM
• Kevin Caunt, IBM
• Marvin Heffler, IBM
• Mats Wichmann, Intel
• Stuart Anderson, FSG
• Matt Taggart, HP

Attendees

• George Kraft, IBM
• Kevin Caunt, IBM
• Marvin Heffler, IBM
• Mats Wichmann, Intel
• Stuart Anderson, FSG
• Jim Litchfield, Sun (Solaris group)
• Chris Yeoh, IBM (telephone at 8:30 AM)
• Andrew Josey, OpenGroup (telephone at 8:30 AM, and 1:50 PM)
• Doug Beattie, FSG (telephone at 8:30 AM)
• Matt Taggart, HP (telephoned at 1:45PM)
  

IBM Lab in Austin
11501 Burnet Road
Austin, TX 78758

Conf Room: 902/6D/14
Toll Free Number: 877-930-0325 (United States)
Toll Number: 712-421-9395 (International)

Wednesday December 10th, 2003

• Today Red Hat announce they LSB v1.3 certified RHEL v.3 for 5 architectures (IA32, IA64, PPC32, S390, S390X)!  We now have 28 LSB certified systems.
• Stuart submitted his grantor agreement for the LSB book
• Kevin asked Chris for information on how to do the autobuild.

• Multi Architectures
• lsb_release
• '-v' returns a colon separated list of profile-release-architecture.  For example,
• workstation-2.0-ia32:server-2.0-ia32
• ACTION: Official update of lsb_release.
• ACTION Matt: Determine how keystone packages are going to write to the /etc/lsb-release file.
  
• keystone packages / dependencies
• migrate from requiring basename "lsb" to "lsb-ia32", "lsb-ia64", "lsb-amd64", and "lsb-generic".
• "hello world" requires profilename "lsb-workstation-ia32=2.0", but how do we install on an LSB server?  We are stuck on this.
• We are leaning towards the yellow box as the lsb core in "Lots of Modules and Profiles"
  
• lsbdev (Mats): see #8
• appchk (Stuart) - there will not be an 'lsbappchk' that takes an architecture as an argument
• /lib, /lib64: already done in LSB

• Path needs to have architecture specific naming, opposed to the number of bits supported (ie., ppc64 versus bin64)
• ACTION: option #8 wins.  We need to change all of the LSB 2.0 packages!
  
• 1) /opt/lsb/bin-ppc -> /opt/lsb/bin (default)
• /opt/lsb/bin/ppc64
• Similar to #6
  
• 2) /opt/lsb-ppc -> /opt/lsb/ (default)
• /opt/lsb-ppc64
• No, because similar to #5.
  
• 3) /opt/lsb/bin/lsbappchk-ppc -> lsbapchk (default)
• /opt/lsb/bin/lsbappchk-ppc64
• Pain for a binary that calls another binary.  Complicates tools.
  
• 4) /opt/lsb/bin/lsbappchk  (front end, calls arch-specific version)
• Difficult to impose.
  
• 5) /opt/ppc/lsb/ -> /opt/lsb/ (default)
• /opt/ppc64/lsb/
• No, because: FHS, LANANA, and legacy issues
  
• 6) /opt/lsb /ppc/* -> /opt/lsb/*  (default)
• /opt/lsb/ppc6
• Can say '--prefix=/opt/lsb/ppc/'
  
• Preference #1
  
• 7) /opt/lsb/bin/ppc -> /opt/lsb/bin/  (default: magic executable  e.g. "ppc32")
• /opt/lsb/bin/ppc64
• Preference #2
• 8) /opt/lsb/2.0/ppc
• /opt/lsb/2.0/ppc64
• /opt/lsb/1.3/ppc
• /opt/lsb/1.3/ppc64
• /opt/lsb-apache/{sbin,bin,lib,etc}    (app-bat will stay in the top /opt/ directory)
• "lsb/2.0" is preferred to keep the descriptive version next to the lsb.
  
• 9) /opt/lsb/ppc/2.0
  

• Multiple LSB Versions
• lsb_release: see multi-arch above
• package dependencies: see  multi-arch above
  
• lsbdev (Mats)
• appchk (Stuart)

• Multiple Profiles (ie., LSB Server versus  LSB Workstation)
• lsb_release
• keystone packages: see multi-arch above
• package dependencies: see multi-arch above
  
• lsbdev: leave it up to the developer to deal with the profiles 
• appchk '-p': or try them all and have it list which ones it matches
• libchk '-p':  needs to know about the sets of ABIs per profile.  Stuart is going to add another table to the LSB DB.
  
• /libxx
• documentation review: (ALL)

• Spec Items
• IPv6
• C++ ELF
• PPC64 version
• pThreads

• Development Environment
• header files
• ACTION: ld wrapper  (ie., using the '-m' flag)?
• FUTURE: cross tools
  

• There appears to be different implementations of PAM on RH, SuSE, and Debian. 
• Thorsten will be making some changes to PAM_UNIX on SuSE to match our spec.  RH will need to do some similar changes.  
• ACTION: Some of our tests will need to change to match the spec, because some RH assumptions were made. 
• ACTION: We need to specify who can call PAM_Authenticate.
• We don't know the status of PAM on IA32.
• See PAM discussion in Spec Auth on Dec 3rd WRT to bugs 32 & 33.
  

• Doug has drafted a letter to the Linux distros about the default install for "LSB".

• LSB Book: "Building Applications with the LSB"
• Kristin Thomas is our editor at IBM
• Mark Taub is our publisher at Printice Hall
• The new due date for the book content completion is April 2nd, 2004.  This is a two month slip to accomidate LSB  v2.0.

• ACTION ITEMS
  
• lsbdev
• new paths (#8)
• add lsbld
• includes per version, but not per arch (but what about c++?  test this)
• packages
  
• base (headers - generic)
• arch (cc, c++, stubs)
  
• app-bat
• ignore paths outlined in #8
• deal with changes made to lsbdev and dependancy naming in spec files
  
• libchk
• check them all then have it list which ones it matches, or '-p' (check union)
• new paths per #8
  
• appchk
• (Stuart) add '-p' to now about the sets of ABIs per profile (check intersection)
• new paths per #8
  
• lsb_release
• publish update
  
• pkgchk
• dependency naming needs more testing
  
• runtime-test
• should go in /opt somewhere?
  
• lib-bat
• si
• needs to grow the multiple architecture support
• packaging uplift
• IPv6 (Stuart)
• C++ ELF (Stuart)
• PPC64 version: DONE
• pThreads (Kevin) test suite parameter setup, then figure out the spec stuff
• archLSB-PPC64: DONE glibc 2.3 symbols added
  
• archLSB-AMD64 (Kukuk): need an architecture champion to drive
• Spec DB
• fix kludges from post processing output from the DB
  
• evaluate overrides
• missing data?
• LSB 2.0 Pilot (Kevin, Doug): next meeting Jan 6th.  start piloting when the pieces are ready
  

LSB Workgroup Meeting: Dec 11, 2003

Attendees

• George Kraft, IBM
• Kevin Caunt, IBM
• Marvin Heffler, IBM
• Mats Wichmann, Intel
• Stuart Anderson, FSG
• Jim Litchfield, Sun (Solaris group)
• Andrew Josey, OpenGroup (telephone at 8:30 AM)
• Doug Beattie, FSG (telephone at 8:30 AM)

• Letter sent out to the Linux distros regarding default LSB install.