search for: ip_auto_config_setup

Displaying 3 results from an estimated 3 matches for "ip_auto_config_setup".

2006 Feb 09
0
Repeated kernel "oops" / oom-killer with Ralph Passgang''s xen 3.0.0 Debian packages
...taur_init_cpu+0x8/0x10 [<c03eb958>] init_centaur+0x148/0x1e0 [<c03eb9f8>] centaur_init_cpu+0x8/0x10 [<c03eb9f8>] centaur_init_cpu+0x8/0x10 [<c03f5334>] kbd_init+0x64/0xa0 [<c014da0f>] do_no_page+0xaf/0x3c0 [<c03f5334>] kbd_init+0x64/0xa0 [<c03feb7c>] ip_auto_config_setup+0x1bc/0x230 [<c03feb7c>] ip_auto_config_setup+0x1bc/0x230 [<c014b269>] pte_alloc_map+0x49/0x1d0 [<c03feb7c>] ip_auto_config_setup+0x1bc/0x230 [<c014df90>] handle_mm_fault+0xf0/0x1d0 [<c03f5334>] kbd_init+0x64/0xa0 [<c03f0b64>] kmem_cache_init+0x294/0x330 [...
2003 Sep 14
2
FWD: Network Boot IP Configuration Dilemma
If you want eth0 to be used and no dynamic IP configuration request should not occur in the Linux kernel, specify *both* APPEND and IPAPPEND options like: APPEND ip=:::::eth0:none IPAPPEND 1 It's very tricky but it works, at least Linux 2.4.18 which I tested. The IP-PNP routine in the kernel doesn't modify values if the option values are not explicitly specified. IPAPPEND doesn't
2003 May 22
0
[PATCH 2.5.69 1/3] remove ipconfig support from the kernel
...ork configuration code in fs/nfs/nfsroot.c, - * originally Copyright (C) 1995, 1996 Gero Kuhlmann and me. - * - * BOOTP rewritten to construct and analyse packets itself instead - * of misusing the IP layer. num_bugs_causing_wrong_arp_replies--; - * -- MJ, December 1998 - * - * Fixed ip_auto_config_setup calling at startup in the new "Linker Magic" - * initialization scheme. - * - Arnaldo Carvalho de Melo <acme@conectiva.com.br>, 08/11/1999 - * - * DHCP support added. To users this looks like a whole separate - * protocol, but we know it's just a bag on the side of BOOTP. -...