2010/12/2 Auke Kok <[email protected]>: > On 12/02/10 08:56, Andrew Flegg wrote: >> >> On Thu, Dec 2, 2010 at 16:42, Arjan van de Ven<[email protected]> >> wrote: >>> >>> On 12/2/2010 8:26 AM, Andrew Flegg wrote: >>>> >>>> I'd suggest coming up with a name (or a comment at the top of the >>>> file) which suggests this is something very different to the machine's >>>> *name* (i.e. /etc/hostname). "People" might try customising it. >>>> >>>> /etc/machinetype, perhaps, or /etc/archtype? >>> >>> /etc/boardname >> >> Yeah, I like that. (FWIW) > > I like this, especially since on x86 we rely mostly on sysfs dmi boardname > values. We can come up with something for ARM that gives us the same > resolution (from w/e proc/cpuinfo or other info available). > > Carsten, I'll setup a gitorious project named "boardname" where we can start > coding, do you want to own the ARM specific parts of this? >
Yes, count me in - I'll probably have to provide the first N900 code for it anyway.. I wonder how specific we have to be with board names.. I mean, I have a Vendor: LENOVO , Board name: Caucasus2 here. Should we do LENOVO Caucasus2 in a board file or? /Carsten _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
