From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Suitable USE flag name for stuff that requires non volatile memory
Date: Sat, 12 May 2007 17:36:28 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.05.12.17.36.27@cox.net> (raw)
In-Reply-To: 20070512161638.0bab56dc@uberlaptop.marples.name
Roy Marples <uberlord@gentoo.org> posted
20070512161638.0bab56dc@uberlaptop.marples.name, excerpted below, on Sat,
12 May 2007 16:16:38 +0100:
> 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.)
>
> 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. The -I <nothing> sounds like the better alternative, as from
your description elsewhere removing the duid would simply create new ones
each time, filling up the slots on the server unnecessarily, while the -I
disabling shouldn't use the functionality at all, which would be the same
as having it not compiled in.
With that caveat, having it on by default and the livecd thing turn it
off seems a bit more reasonable -- except then the livecds won't of
course work with ipv6 DHCP then, as it's required there. Given limited
space on the CD and a desire to use it on ipv6 nets, I don't see a way
around disabling it there 200 uses filling up garbage slots on the server
or not. Well, there's a hack, two in-path versions, a normal version
script stub that adds the appropriate deactivating -I and an ipv6 or
whatever version that doesn't, but that's a hack and not really
satisfactory.
Are any other LiveCDs using it yet or otherwise providing IPv6 DHCP
functionality? What do they do? Surely it's not just a Gentoo problem.
I still think IUSE=dhcp-uid is about as descriptive as it gets, and
coupled with a decent use.desc.local entry and perhaps an elog notice of
some sort, that should be fine.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-12 17:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 23:10 [gentoo-dev] Suitable USE flag name for stuff that requires non volatile memory Roy Marples
2007-05-12 7:13 ` [gentoo-dev] " Duncan
2007-05-12 10:47 ` [gentoo-dev] " Mike Frysinger
2007-05-12 11:34 ` [gentoo-dev] " Duncan
2007-05-12 12:11 ` Mike Frysinger
2007-05-12 15:16 ` Roy Marples
2007-05-12 17:36 ` Duncan [this message]
2007-05-12 18:10 ` Roy Marples
2007-05-12 12:37 ` [gentoo-dev] " Carsten Lohrke
2007-05-12 13:00 ` Mike Frysinger
2007-05-12 15:10 ` Roy Marples
2007-05-13 21:44 ` Mike Frysinger
2007-05-13 21:53 ` Roy Marples
2007-05-13 22:08 ` Mike Frysinger
2007-05-14 4:04 ` [gentoo-dev] " Steve Long
2007-05-14 16:04 ` [gentoo-dev] " Chris Gianelloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2007.05.12.17.36.27@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox