However, it may be likely that the DHCP/non-DHCP thing comes again
into discussion.
I may even predict some reviews with comments like Debian mimics
Microsoft Windows and decides that DHCP is the standard...:-)
Hence, I suggest we consider adding a special boot parameter for
thisĀ :
Stefan Tibus wrote:
Personally I don't think another boot parameter is a good idea. Specially
if it is meant for the non-expert users...
I'd prefer making the DHCP/static question high priority in this case.
Um, how about *medium* priority? It would be nice to have three levels:
basic (almost
On Mon, Mar 22, 2004 at 08:59:57AM +0100, Stefan Tibus wrote:
However, it may be likely that the DHCP/non-DHCP thing comes again
into discussion.
I may even predict some reviews with comments like Debian mimics
Microsoft Windows and decides that DHCP is the standard...:-)
Hence, I
On Mon, 22 Mar 2004 08:59:57 +0100 (MET), Stefan Tibus wrote:
Hence, I suggest we consider adding a special boot parameter for
this : static would feed netcfg/get_method with Static addressing
(manual).
Personally I don't think another boot parameter is a good idea. Specially
if it is meant
On Sun, Mar 21, 2004 at 09:51:37PM -0500, Joey Hess wrote:
Jeremy D. May wrote:
what about adding something to the installer where it activly asks the
user if they wouold perfer manual config or dhcp. in some cases the user
may have dhcp but want to use manual config.
just a
Christian Perrier wrote:
Hence, I suggest we consider adding a special boot parameter for
thisĀ : static would feed netcfg/get_method with Static addressing
(manual).
If netcfg/get_method were turned into a boolean question (it only has 2
choices), and renamed to netcfg/use_dhcp, then it would
Quoting Joey Hess ([EMAIL PROTECTED]):
If netcfg/get_method were turned into a boolean question (it only has 2
choices), and renamed to netcfg/use_dhcp, then it would be easy to
boot: linux netcfg/use_dhcp=false
You can't imagine how hard it is to type this when using an AZERTY
french
what about adding something to the installer where it activly asks the
user if they wouold perfer manual config or dhcp. in some cases the user
may have dhcp but want to use manual config.
just a suggestion!
--jeremy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Jeremy D. May wrote:
what about adding something to the installer where it activly asks the
user if they wouold perfer manual config or dhcp. in some cases the user
may have dhcp but want to use manual config.
just a suggestion!
boot: expert
--
see shy jo
signature.asc
Description:
ok, but what about the not so expert user that wants to do that?
--jeremy
Jeremy D. May wrote:
what about adding something to the installer where it activly asks the
user if they wouold perfer manual config or dhcp. in some cases the user
may have dhcp but want to use manual config.
just
Jeremy D. May wrote:
ok, but what about the not so expert user that wants to do that?
I've added a FAQ entry explaining our reasoning.
http://wiki.debian.net/index.cgi?DebianInstallerFAQ
--
see shy jo
signature.asc
Description: Digital signature
Let me second Jeremy's suggestion.
I keep DHCP turned on on my router because my printer needs it, but
I much prefer to have everything (except the printer -- sigh!) have
statically assigned IP addresses. I know I could do that with
DHCP, but why bother if I don't have to?
Enjoy!
Rick
On
Here's a larger question:
Why do I have to subject myself to the full-monty expert mode when
I just want one tiny feature that isn't completely covered by
normal mode? Shouldn't it be possible to dip down into expert
territory for just the parts you need fine control over, and return
to
Quoting Rick Thomas ([EMAIL PROTECTED]):
Here's a larger question:
Why do I have to subject myself to the full-monty expert mode when
I just want one tiny feature that isn't completely covered by
normal mode? Shouldn't it be possible to dip down into expert
territory for just the parts
14 matches
Mail list logo