| 1 |
Roy Marples <uberlord@g.o> posted |
| 2 |
20070512001018.0eca154e@××××××××××××××××××.name, excerpted below, on Sat, |
| 3 |
12 May 2007 00:10:18 +0100: |
| 4 |
|
| 5 |
> dhcpcd-3.1 is [...] almost ready to be put into the tree. [N]ew |
| 6 |
> feature[:] generates a DUID-LLT [which should persist] across reboots. |
| 7 |
> I would like a nice USE flag name, so it can be compiled with or without |
| 8 |
> that support. My ideas so far. |
| 9 |
> |
| 10 |
> duid |
| 11 |
> duid-llt |
| 12 |
> (both descriptive, but doesn't actually mean anything to most users) |
| 13 |
> |
| 14 |
> livecd |
| 15 |
> (only a livecd is volative, even embedded devices have non volative |
| 16 |
> storage) |
| 17 |
> |
| 18 |
> volatile |
| 19 |
> |
| 20 |
> More are welcome :) |
| 21 |
> |
| 22 |
> For those that are interested in what a DUID is, read on. A DUID (DHCP |
| 23 |
> Unique IDentifier) is a unique identifier to the machine that should |
| 24 |
> never change and is used along with an IAID (Identity association |
| 25 |
> identifier). Simply put its a means of identifying the machine and the |
| 26 |
> interface. |
| 27 |
|
| 28 |
> It's also required for DHCP over infiniband and IPv6. |
| 29 |
> |
| 30 |
> The big downside is that it does require non volative storage[.] |
| 31 |
> Once you have a DUID, it should never change. |
| 32 |
|
| 33 |
ipv6 USE flag, since IPv6 requires it? It's not a perfect fit, but it's |
| 34 |
no worse than some others I've seen. An elog could then be used with a |
| 35 |
short explanation and possibly a link to something a bit longer. This |
| 36 |
works only if having it on by default is desired, since many profiles set |
| 37 |
+ipv6. |
| 38 |
|
| 39 |
d-uid or dhcp-uid? Unlike ipv6, this would be a local USE flag (as would |
| 40 |
be the parallel choices you suggested), so could be defaulted as desired, |
| 41 |
with a corresondingly less generic use.desc(.local) description. An elog |
| 42 |
would then be optional. UID should also have meaning to rather more |
| 43 |
users than duid does, and dhcp-uid would be quite descriptive at least to |
| 44 |
me, with or without additional information such as you provided above. |
| 45 |
|
| 46 |
I like dhcp-uid, personally. If that's Greek to someone, likely about |
| 47 |
anything else you chose would be as well, yet it still should make sense |
| 48 |
to anyone who has come across "UID" before. For those to whom it doesn't |
| 49 |
make sense, the use.desc.local entry should hopefully be sufficient, if |
| 50 |
they even bother to worry about it as against the defaults, whatever they |
| 51 |
may be. |
| 52 |
|
| 53 |
BTW, this is very useful information to me, and one of the big reasons |
| 54 |
I'm subscribed here, to get info such as this before I'm faced with it in |
| 55 |
the tree, and don't have a clue. Thanks! =8^) |
| 56 |
|
| 57 |
-- |
| 58 |
Duncan - List replies preferred. No HTML msgs. |
| 59 |
"Every nonfree program has a lord, a master -- |
| 60 |
and if you use the program, he is your master." Richard Stallman |
| 61 |
|
| 62 |
-- |
| 63 |
gentoo-dev@g.o mailing list |
Archives