The installer makes no assumptions on it's own.
After all a high percentage of people run their own DNS daemon, etc...
and/or sometimes the user elects not to install dns/bind packages since they
are installing in a secondary machine on their network.
The NET tool on the other hand expects to be told which machine is the
resolver. It does not by itself set up your DNS.
Linuxconf handles DNS setup under separate entries, as it should.
It does a fairly good job of it too. The perennial problem with Linuxconf is
the abysmal documentation and help files.
Often exacting and differing syntax must be used in each of it's modules
(because they were written by different people) but the help/documentation
barely mentions ANYTHING.
As a result many people overlook Linuxconf and resort to circumventing it...
subsequently running into problems because they are not doing things the
Mandrake/Linuxconf way...
It's a nightmare for the newbie to wade thru this. The upside is that it
does make things easier to give help to newbies...
While I deem myself to know Linuxconf pretty well, there are still areas
that totally elude me... and others which are still in error.
Case in point: I discovered that the automatic update of DNS via the DHCPD
server for Windows Client allocation was attempting to write out the leases
file into the wrong directory.
This prevented DNS from getting update via the cron script that does this,
so while the leases would be allocated there were no corresponding DNS
additions or removals.
A simple symlink to the proper directory fixed this and now Linuxconf
correctly shows all allocations...
So WHERE are the docs for this?
As so typifies good coders, the Linuxconf authors can program with the best,
but can't write docs worth a damn.
-JMS
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mark Johnson
Sent: Wednesday, March 28, 2001 9:39 AM
To: LinuxNewbie (E-mail)
Subject: RE: [newbie] Linux is draggin' A$$
Is this actually the cannoncial way of setting up your machine:
> ... and add an entry for it in /etc/hosts, etc.
to add the machine name to your hosts file?
I'm just asking because I did that, but I just did it as a last resort. I
didn't know you *had* to do that and I was thinking I was just kludging my
system.
If that's the case, why doesn't the installer or the Net & Internet Conf
tool in DrakConf set this for your?
-----Original Message-----
From: Jose M. Sanchez [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 27, 2001 9:05 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [newbie] Linux is draggin' A$$
If you haven't set up "networking" properly (even if you don't have a LAN
card) everytime you start up a program, linux queries it's resolver to find
out if the terminal is authorized.
Since DNS/Resolver is unconfigured it takes 2 minutes for things to time out
waiting for the response that never comes.
You need to fix this!
Remember to assign the machine a hostname and domain and add an entry for it
in /etc/hosts, etc.
You might want to check the FAQ and erratta for complete instructions as
this is a common "newbie" mistake.
-JMS
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Kelly, Christopher
Sent: Tuesday, March 27, 2001 2:03 PM
To: 'Newbie'
Subject: [newbie] Linux is draggin' A$$
What would cause pauses in Linux? When ever I try to open something, be it a
program or a directory, it always pauses and it will take 2 mins to open. My
system is a PII 233 with 64megs of RAM. This should run fine from what I've
heard. Let me know what to check.
Thanks,
Moose
