Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!tfs.com!tfs.com!julian From: julian@tfs.com (Julian Elischer) Subject: Re: new SCSI drivers -also New interim release of 386bsd- Message-ID: <1992Dec6.203232.20507@tfs.com> Organization: TRW Financial Systems References: <wf8YMrK00VQwI6Rl14@andrew.cmu.edu> Date: Sun, 6 Dec 1992 20:32:32 GMT Lines: 62 In article <wf8YMrK00VQwI6Rl14@andrew.cmu.edu> dd2x+@andrew.cmu.edu (David Eugene Dwiggins) writes: >I keep seeing references to the new scsi drivers on ref.tfs.com, but >can't seem to find them anywhere. > >Where are they? > look on ref in ~julian/sharfiles they are the last posted sharfiles for the scsi and bootblocks there is also a directory 'scsi' that contains newer versions of some of the files for the scsi release (none of the patches however) look also in /sys to see the same files installed. >Thanks in advance, > >David regarding the new 'interim release' people are talking about I have a couple of points: I can supply more room on ref for this. also: we need a standard as to how ported packages are delivered so they can be installed onto a system easily I have a directory on ref /usr/othersrc/public (in the std release) In that directory, each 'package' should have a separate directory (with no Version info... that comes later) e.g. mtools or xview That directory in turn has in it a Makefile that knows how to install the package, and the package source directory itself. That way we don't need to patch instalation code into the makefiles of the package itself, but rather can put it and cleanup code in the top level makefile while leaving the form of the lower level makefile alone. There is a problem in how to handle thecase where two different versions of a package install different binaries, maybe we need a different subdir for each versions to hold a different install makefile for each.. /usr/othersrc/public/mtools /usr/othersrc/public/mtools/Makefile /usr/othersrc/public/mtools -> mtools-2.05 ( the one we are istalling) /usr/othersrc/public/mtools/mtools-2.05 /usr/othersrc/public/mtools/mtools-2.05/Makefile /usr/othersrc/public/mtools/mtools-2.05/<source><-- basically unmodified /usr/othersrc/public/mtools/mtools-2.04 /usr/othersrc/public/mtools/mtools-2.04/Makefile /usr/othersrc/public/mtools/mtools-2.04/<source><-- basically unmodified as far as the kernel goes: I have still some things I'd like to add to the kernel tree on ref (for example sources for the enw console driver(s) and for the lpr driver) it is patched up with the new beta patchkit to about level73 or so and when that seems stable it should be a good source. julian