Goals for 0.3.0

[Kay Sievers]

On Thu, 2004-07-22 at 15:55 -0400, Joe Shaw wrote:
> On Thu, 2004-07-22 at 21:25 +0200, David Zeuthen wrote:
> > There were some discussion about this some time ago and I proposed that
> > in the worst case you can always use the parents udi appended with
> > something otherwise unique or at least something that doesn't clash with
> > your siblings. By induction this provides unique UDI's [1].
> > 
> > Specifically for drives you can use partition numbers in lack of UUID or
> > label. Maybe even an MD5 of the first couple of sectors or something.
> 
> Yeah, but how do we make them unique across invocations of HAL such that
> things can reliable depend on them?

A bootloader update writes the first sector, so we may checksum the
partition map, but two usb-sticks may have the same. How about "back-
map" the id's of the first patition, if we have nothing else?

Should I prepare something, that can read the serial numbers of
ide/scsi-drives we have native access to? 

> > > Similar topic:
> > > Should the network-adapter udi's should use the MAC address instead of
> > > the device id's?
> >
> > Yeah, that's an excellent idea.
> 
> The ones without parents (ie, directly under Computer) already do this.
> Check out the compute_udi function in net_class_device.c  I'm not sure
> there's much reason to otherwise, since it tends to use the UDI from the
> PCI device.

What about pcmcia-cards, usb-wireless? They don't necessarily have the
same parent over the time?

Kay

_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal