BOOTP and 2.4.14

BOOTP and 2.4.14

Post by sum.. » Sat, 17 Nov 2001 00:50:11



I'm trying to configure a system to boot with root on NFS. I have it
working, but there are problems.

The most serious are that the DNS domain name is set wrongly, and NIS
domain's not set at all.

The IP address offered and accepted in 192.168.1.20.

The DNS domain name being set is 168.1.20, and the host name 192.

I'm looking at the ipconfig.c source, around line 1324 where I see this
code:
                        case 4:
                                if ((dp = strchr(ip, '.'))) {
                                        *dp++ = '\0';
                                        strncpy(system_utsname.domainname, dp, __NEW_UTS_LEN);
                                        system_utsname.domainname[__NEW_UTS_LEN] = '\0';
                                }
                                strncpy(system_utsname.nodename, ip, __NEW_UTS_LEN);
                                system_utsname.nodename[__NEW_UTS_LEN] = '\0';
                                ic_host_name_set = 1;
                                break;

I can see how the dnsdomain name's being set, and it does not look
right to me.

If someone can prepare a patch for me, I'll be delighted to test it.

--
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my
disposition.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

BOOTP and 2.4.14

Post by sum.. » Sat, 17 Nov 2001 04:50:11


Quote:

> Set your kernel command line correctly, the format is:

>    HOSTNAME.NIS_DOMAINNAME

> It has been like this since ancient times :-)

I don't understand. According to nfsroot.txt all I need is this:


default linux
prompt 1
timeout 1
label linux
        kernel vmlinuz
        append  root=/dev/nfs ip=bootp initrd=initial.dsk

The kernel messages say it's got the domain name, but by the time it
gets to init (I altered /etc/rc.d/rc.sysinit to see) it's using the IP
address for host/domain names, and that's what I see in the code I
cited.

The nis domain's not being set, but I've not established the kernel's
at failt.

According to the debugging code which I've enabled, it's seeing
extensions 1, 3, 6, 55, 45, 46 and 15.

1 looks like the netmask, 3, 6, 44 and 45 are all the IP address of the
server (it does several things so that's probably okay), 46 has the
value 08 and 15 is the DNS domain name.

The client's IP address isn't reported by the debugging code, but is
set to the value I expect.

I see the extensions are parsed in ic_do_bootp_ext which silently
ignores 44, 45 & 46.

Here are some kernel messages from booting the client:
Nov 16 02:46:51 192 kernel: IP-Config: Entered.
Nov 16 02:46:52 192 kernel: IP-Config: eth0 UP (able=1, xid=46e93477)
Nov 16 02:46:52 192 kernel: Sending BOOTP requests .DHCP/BOOTP: Got
extension 1: ff ff ff 00
Nov 16 02:46:52 192 kernel: DHCP/BOOTP: Got extension 3: c0 a8 01 01
Nov 16 02:46:52 192 kernel: DHCP/BOOTP: Got extension 6: c0 a8 01 01
Nov 16 02:46:52 192 kernel: DHCP/BOOTP: Got extension 44: c0 a8 01 01
Nov 16 02:46:52 192 kernel: DHCP/BOOTP: Got extension 45: c0 a8 01 01
Nov 16 02:46:52 192 kernel: DHCP/BOOTP: Got extension 46: 08
Nov 16 02:46:52 192 kernel: DHCP/BOOTP: Got extension 15: 4f 73 32 2e
41 6d 69 2e 43 6f 6d 2e 41 75
Nov 16 02:46:52 192 kernel:  OK
Nov 16 02:46:52 192 kernel: IP-Config: Got BOOTP answer from
192.168.1.1, my address is 192.168.1.20
Nov 16 02:46:52 192 kernel: IP-Config: Complete:
Nov 16 02:46:52 192 kernel:       device=eth0, addr=192.168.1.20,
mask=255.255.255.0, gw=192.168.1.1,
Nov 16 02:46:52 192 kernel:      host=192.168.1.20,
domain=Os2.Ami.Com.Au, nis-domain=(none),
Nov 16 02:46:52 192 kernel:      bootserver=192.168.1.1,
rootserver=192.168.1.1, rootpath=

By the time init passes control to ins initialisation script, the
hostname command reports 192 and dnsdomainname reports 168.0.1.

--
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my
disposition.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Unwanted Swapping in 2.4.14-pre8, no swapping in 2.4.14-pre6aa1

Yes. Currently, the kernel "tries" to keep the LRU list of pages with 90%
of mapped pages and 10% of cache when there is memory pressure.

By looking at mm/vmscan.c::shrink_cache() you can see:

        int max_scan = nr_inactive_pages / priority;
        int max_mapped = nr_pages << (9 - priority);

"max_scan" is the max. number of pages the kernel will scan on the
inactive list (the inactive list is usually 1/3 of the total amount of
pages) each time "shrink_cache()" is called.

"max_mapped" is the (roughly) maximum number of non-cache (anonymous)
pages the kernel will scan _before_ it tries to search for data to map to
swap. So basically right now we will scan

You should try to increase "max_mapped" to "nr_pages << (10 - priority)"
and so on until you get good tuning for your workload.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. how to create child window in gtk+/gtk-- ?

3. Memory accounting problem in 2.4.13, 2.4.14pre, and possibly 2.4.14

4. sun ar complaints

5. VM test on 2.4.14pre3aa2 (compared to 2.4.14pre3aa1)

6. hate gui login

7. Wake On Lan broken since kernel version 2.4.14

8. databases shareware

9. VM tests on 2.4.14-pre3 and 2.4.13-ac3

10. SB 5.1 driver doesn't load, kernel 2.4.14

11. RH 7.2 w/ 2.4.14 kernel, can't access certain web sites

12. Oops in kmem_cache_free with 2.4.14

13. Announce: XFS split patches for 2.4.7 to 2.4.14