On Mon, 16 Jul 2018, Roy Marples wrote:
> Sadly, all my machines are x86 based. I have an ERLITE mips router where I
> also run dhcpcd, and it doesn't stamp on routes there either, so I'm pretty
> sure this isn't an arch issue ... but I could be wrong.
The only route that was an issue was the
On 15/07/2018 23:54, John D. Baker wrote:
On Sun, 15 Jul 2018, Roy Marples wrote:
But have we considered an alternative? The in kernel DHCP client as
I see it is just to handle network booting yes? Once userland is
netmounted, dhcpcd can then take over? If so, does the kernel DHCP
This seems
On Sun, 15 Jul 2018, Roy Marples wrote:
> But have we considered an alternative? The in kernel DHCP client as
> I see it is just to handle network booting yes? Once userland is
> netmounted, dhcpcd can then take over? If so, does the kernel DHCP
This seems to be a condition unique to x86
On 15/07/2018 12:16, Robert Elz wrote:
| The only other concern I have with this is that if we have two
| interfaces and dhcpcd receives the same short hostname on both but only
| a domain on one of them, then the hostname will flip-flop between short
| and long hostnames.
I'm not
On Sun 15 Jul 2018 at 18:16:15 +0700, Robert Elz wrote:
> The test "language" was very badly defined (ie: not at all really.)
>
> To avoid problems with that, there are very specific rules about
> where to look for operators depending upon just how many args
> exist - with those rules, it is
On Thu 05 Jul 2018 at 10:52:12 +0300, Andreas Gustafsson wrote:
> MLH wrote:
> > Boot Options are:
> > Hard Drive, CDROM, USB-FDD, USB-ZIP, USB-CDROM, USB-HDD, Legacy LAN
>
> A USB memory stick emulates a hard drive, so USB-HDD should work.
A USB stick formatted like a hard drive *should*
"Farid Joubbi" wrote:
=> I tried the install CD for the latest HEAD-201807121210Z.
=> It can see both the NICs, but they don't work.
=> Trying to configure them with DHCP, it looks as if the NIC is sending a
=> DISCOVERY but timing out never receiving anything back (I doubt that it is
=> actually
Date:Sun, 15 Jul 2018 11:18:22 +0100
From:Roy Marples
Message-ID:
| If we're going to test that, then we need to check the converse for
| ${hsort} && [ "$hostname" = "${hostname%%.*}" ]
First irrelevant comment, the %%.* instead of #*. is an irrelevant
On 15/07/2018 11:18, Roy Marples wrote:
On 15/07/2018 03:37, Robert Elz wrote:
As with most client/server systems, there are two separate things that
need
to be made to work - the server has to send the data that you want it to
send (which might mean altering what the client requests, or
On 15/07/2018 03:37, Robert Elz wrote:
As with most client/server systems, there are two separate things that need
to be made to work - the server has to send the data that you want it to
send (which might mean altering what the client requests, or server config,
or ...) and then the client
I tried the install CD for the latest HEAD-201807121210Z.
It can see both the NICs, but they don't work.
Trying to configure them with DHCP, it looks as if the NIC is sending a
DISCOVERY but timing out never receiving anything back (I doubt that it is
actually sending anything on the wire).
Then
11 matches
Mail list logo
