On Sat, 12 May 2007 11:34:10 +0000 (UTC) Duncan <[EMAIL PROTECTED]> wrote:
> Mike Frysinger <[EMAIL PROTECTED]> posted > [EMAIL PROTECTED], excerpted below, on Sat, 12 May > 2007 06:47:38 -0400: > > > On Friday 11 May 2007, Roy Marples wrote: > >> livecd > >> (only a livecd is volative, even embedded devices have non volative > >> storage) > > > > i would use that myself ... perhaps even tie in USE=netboot ... > > Except that livecd is entirely unsuitable. The description says it's > for internal use only, not to be set on a standard installation, > while Roy's post specifically stated that those merging the package > for use on IPv6 will probably want the functionality on. Although it's a requirement for IPv6 DHCP, it's recommended for IPv4 these days too. It is a requirement for IPv4 DHCP over infiniband as that has MAC address sizes that are great than what DHCP messages originally allowed. So no, in this case the ipv6 USE flag would be bad for this. I also implies IPv6 support which it won't have for some time yet. > (I OTOH, would want it off, for the same reason I'm running the > macchanger module, have cookies off by default, and block the likes > of doubleclick. I like my IP address actually changing once in > awhile, certainly more frequently than my ISP tends to change it > given the same MAC address every time. My ISP may be able to > associate my IP with my name and account based on the records for the > cable modem registered in my name, but that doesn't mean I want every > doubleclick and google.com doing it, at least not without going to a > bit of trouble. Thus, using a non-transparent flag such as livecd > and defaulting it to on, or simply hard-deping it, isn't a > particularly nice option either.) You can disable it's use at runtime by giving the -I option a null argument. This is unsuitable for live cd users as they won't do that by default. Or you can always remove the file /var/lib/dhcpcd/dhcpcd.duid and it will make a new one for you. Thanks Roy -- [EMAIL PROTECTED] mailing list
