Re: [SLE] NFS dog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 31 August 2004 15:03, Chadley Wilson wrote:

> I am not getting any problems from my logs at all,
>
> The strange thing here is that if I run "service named stop" then nfs
> works.
>
> I manufacture PCs and you will be happy to know that I have already built
> approx 4000 systems loaded with FC1 / 2 Linux this year. To speed up the
> installations via the network I setup a dns server and a dhcp to assign IPs
> and host names to the computers. The problem I am faced with is possibly a
> config problem in my dhcp file. The server is not assigning the host names,
> I also can't use mac address statements because the PCs are always new. In
> other words I want the dhcp to assign an IP on a random basis, if for
> example the IP is 192.168.2.1 then make that PCs hostname
> station1.domainname. If a PC is unplugged from the network then it must
> make that IP immediatley available again.
>
> Here is my dhcpd.conf file could someone please give me a hint:
>
> +++++++++++++++++++++++++++++++++++++++++++++++
> ddns-update-style ad-hoc;
> default-lease-time 30;         # 30 seconds
> max-lease-time 7200;            # 2  hours
>
>         option domain-name "teq.pinteq";
>         option domain-name-servers 192.168.2.1;
>         option broadcast-address 192.168.2.255;
>         option routers 192.168.2.1;
>         option subnet-mask 255.255.255.0;
>
> subnet 192.168.2.0 netmask 255.255.255.0
>  {
>   range 192.168.2.10 192.168.2.50;
>  }
> +++++++++++++++++++++++++++++++++++++++++++++++++++
>
> -------------------------------------------------------
This is ridiculous;
OK so I decided to setup http based installations out of desperation,
I copied the install dir fc1 to my http folder .
I forgot to edit the ks.cfg (kickstart file) which is set to nfs, the line is:
nfs --server=192.168.2.1 --dir=/fc1

Booting from cdrom I use the option:
linux ks=http://192.168.2.1/fc1/ks.cfg
and then it mounts my nfs share /fc1 and the install rocks on.

So I figured that nfs has mysteriously decided to work so I try 
linux ks=nfs:192.168.2.1:/fc1/ks.cfg
and it fails to mount the share.
So I know it is a problem between named and dhcp but what is the problem.


Please can someone give me a clue
PS:clues do not include man pages or google I have read and can't see the 
light.



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux