mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: summer@os2.ami.com.au
To: "Peter Wächtler" <pwaechtler@loewe-komp.de>
Cc: summer@os2.ami.com.au,
	Linux kernel <linux-kernel@vger.kernel.org>,
	summer@numbat.os2.ami.com.au
Subject: Re: BOOTP and 2.4.14
Date: Fri, 16 Nov 2001 07:50:13 +0800	[thread overview]
Message-ID: <200111152350.fAFNoDI08622@numbat.os2.ami.com.au> (raw)
In-Reply-To: Message from Peter =?iso-8859-1?Q?W=E4chtler?=  <pwaechtler@loewe-komp.de> of "Thu, 15 Nov 2001 22:13:55 +0100." <3BF43013.30433D08@loewe-komp.de>

> summer@os2.ami.com.au schrieb:
> > 
> > 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.
> > 
> 
> 
> Uh, how about to specify a NAME.DOMAIN.COM instead of an 
> dotted IP. Check your bootp configuration.


The IP address being offered does not need to resolve; if I configure 
it to update my DNS, then at the time it's offered it will not resolve.

Here's the stanza from /etc/dhcpd.conf

                host banana
                        {
                                fixed-address 192.168.1.20;
                                option host-name "banana";
                        }


BUT the stanza's not required at all.

> 
> > 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.




      reply	other threads:[~2001-11-16 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15  6:28 summer
2001-11-15 15:11 ` David S. Miller
2001-11-15 19:01   ` summer
2001-11-15 21:13 ` Peter Wächtler
2001-11-15 23:50   ` summer [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=200111152350.fAFNoDI08622@numbat.os2.ami.com.au \
    --to=summer@os2.ami.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwaechtler@loewe-komp.de \
    --cc=summer@numbat.os2.ami.com.au \
    /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

all inboxes | Powered by JetHome®