Void Linux discussion
 help / color / mirror / Atom feed
From: sth <li...@nvsbl.org>
To: voidlinux <void...@googlegroups.com>
Subject: Re: Network setup twice during void installation?
Date: Fri, 8 Jan 2016 17:16:54 +0100	[thread overview]
Message-ID: <3A792A0B-9F2A-48AA-83A5-6F8EB044451C@nvsbl.org> (raw)
In-Reply-To: <fec1ec1e-5b9a-4593-83af-0d4dce525ea0@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

I think PRs are gladly accepted, if you have time to look into this. 

--seth

> On 08 Jan 2016, at 15:25, Donald Allen <donald...@gmail.com> wrote:
> 
> 
> 
>> On Wednesday, September 16, 2015 at 8:38:29 AM UTC-4, Donald Allen wrote:
>> Running void-installer, one of the early items is 'Network'. I dutifully set up the network (in the install I just did, I set up the ethernet interface with a static IP address). The next step in the install relates to where the installation files are coming from (I've forgotten the exact wording in the menu). When you select that, you have two options: local and network. If you select 'network' it asks you to set up the network again. As an experiment, as this point I set it up to use dhcp, to see if the second setup over-rode the first. It does, as evidenced by the system coming up post-install with an assigned IP address, rather than the static address I'd previously specified. What is going on here? On the face of it, asking twice for the network setup makes no sense and I have not yet found any documentation explaining what the installer thinks it's doing. Is there a sensible rationale for this or is it a bug?
>> 
>> /Don Allen
> 
> Any idea when this will be fixed? It really is pretty bogus and I'm surprised that it hasn't been addressed in the four months since I originally posted this. I would think that asking the question "has the network already been configured?" and skipping the request to set it up again (and then, after collecting the information, failing -- a new behavior since I last tried Void, which is even more annoying; this is like calling your credit card company, being asked to type in the account number and then when a human comes on the line, asks for your account number) would not be difficult.
> 
> /Don Allen 
> -- 
> You received this message because you are subscribed to the Google Groups "voidlinux" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+...@googlegroups.com.
> To post to this group, send email to void...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/fec1ec1e-5b9a-4593-83af-0d4dce525ea0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3035 bytes --]

      reply	other threads:[~2016-01-08 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 12:38 Donald Allen
2015-09-17 14:11 ` Juan RP
2015-09-17 22:00   ` Donald Allen
2015-09-20  2:29   ` Donald Allen
2016-01-08 14:25 ` Donald Allen
2016-01-08 16:16   ` sth [this message]

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=3A792A0B-9F2A-48AA-83A5-6F8EB044451C@nvsbl.org \
    --to="li..."@nvsbl.org \
    --cc="void..."@googlegroups.com \
    /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;
as well as URLs for NNTP newsgroup(s).