On Thu, Jan 22, 2004 at 06:58:49PM +0100, Sven Luther wrote: > > at all to do with the architecture we're on, and everything to do with > > the flavor of kernel that was booted -- which is exposed through uname, > > which is already handled through kernel-installer. > And that it can easily be used by kernel-installer to choose the right > kind of flavor for your subarch/whatever. In this case, subarch could be > the processor kind used. > archdetect does some parsing of /proc/cpuinfo, and thus would be the > right place to do some processing of the /proc/cpuinfo or even uname > output, and then use the result easily afterward, either because it > would be filled in in some place in the debconf database, or because you > use it directly. > And since you were speakind of parsing the output of uname, it is only > natural that you would look at archdetect which is the right tool for > doing this. But then, if you like repeating unecessary work, you are > welcome. I'm not repeating unnecessary work: kernel-installer already has a general interface for handling uname. Are you planning to move all of this into archdetect? -- Steve Langasek postmodern programmer
Attachment:
pgpdNxskqZUs0.pgp
Description: PGP signature