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 11:34:10 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.05.12.11.34.09@cox.net> (raw)
In-Reply-To: 200705120647.39160.vapier@gentoo.org
Mike Frysinger <vapier@gentoo.org> posted
200705120647.39160.vapier@gentoo.org, 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.
(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.)
--
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 11:37 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 ` Duncan [this message]
2007-05-12 12:11 ` [gentoo-dev] " Mike Frysinger
2007-05-12 15:16 ` Roy Marples
2007-05-12 17:36 ` Duncan
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.11.34.09@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