On Tue, Aug 19, 2014 at 8:10 PM, Cyril Brulebois wrote:
> Steven Chamberlain (2014-08-20):
>> On 14/08/14 18:32, Cyril Brulebois wrote:
>> > Now, I think there are several questions to answer:
>> > 1. What were the reasons for having arch-dependent dhcp clients?
>>
>> I'd speculate because udhcpc
Steven Chamberlain (2014-08-20):
> On 14/08/14 18:32, Cyril Brulebois wrote:
> > Now, I think there are several questions to answer:
> > 1. What were the reasons for having arch-dependent dhcp clients?
>
> I'd speculate because udhcpc from busybox is very small, and
> isc-dhcp-client-udeb was ab
On 14/08/14 18:32, Cyril Brulebois wrote:
> Now, I think there are several questions to answer:
> 1. What were the reasons for having arch-dependent dhcp clients?
I'd speculate because udhcpc from busybox is very small, and
isc-dhcp-client-udeb was about 2 MiB. It targets (currently only builds
Hi,
On Thu, Aug 14, 2014 at 07:32:22PM +0200, Cyril Brulebois wrote:
> Now, I think there are several questions to answer:
> 1. What were the reasons for having arch-dependent dhcp clients?
> 2. Are those reasons still valid?
>
> => Maybe think about moving to a single client if possible, at le
Hi,
Steven Chamberlain (2014-08-13):
> On 13/08/14 18:05, Cyril Brulebois wrote:
> > What I'd like to get figured out is what changed between images that
> > weren't hitting this problem, and the newly published ones.
>
> What changed is dhclient from isc-dhcp-client-udeb gained a signal
> handl
On Wed, Aug 13, 2014 at 07:05:47PM +0100, Steven Chamberlain wrote:
> On 13/08/14 18:05, Cyril Brulebois wrote:
> > What I'd like to get figured out is what changed between images that
> > weren't hitting this problem, and the newly published ones.
>
> What changed is dhclient from isc-dhcp-client
On 13/08/14 18:05, Cyril Brulebois wrote:
> What I'd like to get figured out is what changed between images that
> weren't hitting this problem, and the newly published ones.
What changed is dhclient from isc-dhcp-client-udeb gained a signal
handler that responds to SIGKILL by releasing the DHCP l
Steven Chamberlain (2014-08-13):
> On 13/08/14 02:56, Cyril Brulebois wrote:
> > So, using debian-jessie-DI-b1-kfreebsd-amd64-netinst.iso with DHCP,
> > an error is shown right after the mirror selection, since network
> > configuration obtained through DHCP is lost at this point. It would
> > be
On 13/08/14 02:56, Cyril Brulebois wrote:
> So, using debian-jessie-DI-b1-kfreebsd-amd64-netinst.iso with DHCP, an
> error is shown right after the mirror selection, since network
> configuration obtained through DHCP is lost at this point. It would be
> nice to make sure what triggered this issue
Package: debian-installer
Version: 20140802
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
I know this is tracked as #757711 but I'm trying to get a comprehensive
list of issues affecting kfreebsd-*, along with possible solutions for
those using images.
So, using de
10 matches
Mail list logo
