Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!psgrain!qiclab!percy!agora!rgrimes From: rgrimes@agora.rain.com (Rodney Grimes) Newsgroups: comp.os.386bsd.bugs Subject: Re: Note for syscons users with patchkit 0.2.2 Message-ID: <C4FLy5.21p@agora.rain.com> Date: 25 Mar 93 06:27:40 GMT Article-I.D.: agora.C4FLy5.21p References: <1993Mar24.090026@axion.bt.co.uk> <1993Mar24.100324.21660@gmd.de> <JKH.93Mar25015704@whisker.lotus.ie> Organization: Open Communications Forum Lines: 20 jkh@whisker.lotus.ie (Jordan K. Hubbard) writes: >>Is it possible to have a mechanism in the next patchkit version which reports >>the current patch level by a version string and a defined symbol? >>Something like the following: >> >> [ details deleted ] >I don't see why not. Let me look at how best to do this (I.E. "_what_ file?"). Humm, had some more thought's on this one. It needs to be in an existing file, otherwise if someone tries to compile the code on a stock 0.1 system with an include <sys/patchlevel.h> the file won't be there and the compile well fail. -- Rod Grimes rgrimes@agora.rain.com Accurate Automation Company All opinions belong to me and my company! Get your free copy of 386bsd from agate.berkeley.edu:/pub/386BSD via ftp! An out of work contractor... You need unix work done.... Send me your project!