From owner-freebsd-questions Sun Oct 15 11:11:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 5561A37B502 for ; Sun, 15 Oct 2000 11:11:52 -0700 (PDT) Received: from jayk3 (user-2ini8bs.dialup.mindspring.com [165.121.33.124]) by smtp6.mindspring.com (8.9.3/8.8.5) with SMTP id OAA09164; Sun, 15 Oct 2000 14:11:17 -0400 (EDT) From: jay.krell@cornell.edu Message-ID: <004701c036d3$269c49f0$8001a8c0@jayk3> Reply-To: To: "Matthew Emmerton" Cc: Subject: Re: FreeBSD 3.x->4.1, my experience, Samba, dhcpd, ppp, nat, dns, named Date: Sun, 15 Oct 2000 11:09:45 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 x-mimeole: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > it's all a matter of background knowledge Yes, I agree somewhat. I have a big background setting up NT clients. I have never done large scale NT deployment, I only know in my little two machine network that Win2k was easy. I still take issue with how hard lone Unix systems are to get working. The book "Phil and Alex's Guide to Web Publishing" describes it well I think. Unix being really awful to setup and configure, but n machines being no harder than one machine. > /etc/rc.local vs. /usr/local/etc/rc.d/dhcpd.sh ?so the right thing to do here is basically rm /etc/rc.local -- /usr/local/etc/rc.d/dhcpd.sh -- #!/bin/sh # # For example, in /etc/rc.conf put # dhcpd_enable="YES" # and optionally # dhcpd_flags="-q" # to not print out the verbose copyright message. # # Start Dynamic Host Configuration Protocol Daemon, so # that other machines on the local net don't need # hardcoded IP address or DNS server addresses or anything. # if [ "X${dhcpd_enable}" = X"YES" ]; then echo -n ' dhcpd' ${dhcpd_program-"/usr/local/sbin/dhcpd"} ${dhcpd_flags} fi -- /usr/local/etc/rc.d/dhcpd.sh -- I'll try that. I knew rc.local was obsolete but at the time it seemed the easiest thing. I noticed NetBSD includes isc dhcpd and they have a document up describing very close to what I was after. They have a more complicated dhcpd.conf, but still pretty sample. The wide-dhcp docs were talking about "relay agents" and setting up two .conf files, I had no clue.. > starting Samba I kind of thought perf was better in general running stuff under inetd, fewer processes, but maybe that's only until the service is used. There's a more general problem of installing ports/packages reporting a lot of stuff you don't need to know, a little that you do need, and the scrollback on the console being tiny, installing multiple things, etc.. I always set the scrollback to 9999 on NT, should look into how that might be on on FreeBSD, or use X and some xterm clone, or tee.. Some of my attempts at starting smbd and nmbd resulted in a bunch of nmbd processes, like until problems set in, but I didn't bother to characterize what I'd done. - Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message