Date: Fri, 31 May 2002 23:46:58 +0200 From: "Daniel Blankensteiner" <db@traceroute.dk> To: "Terry Lambert" <tlambert2@mindspring.com> Cc: <freebsd-arch@freebsd.org> Subject: Re: FreeBSD daemon configurations redesign Message-ID: <01bf01c208ec$b11a7380$6800a8c0@rafter> References: <F67gL6wxvw0IDT8zAJ90000d078@hotmail.com> <00c601c2082d$bc531ff0$6800a8c0@rafter> <3CF6B300.145E0CD9@mindspring.com> <011201c20832$34404750$6800a8c0@rafter> <3CF6CC39.BFC0A232@mindspring.com> <011001c20885$6dc3db60$6800a8c0@rafter> <3CF7E342.C351A12E@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Terry Lambert" <tlambert2@mindspring.com> > > I am only talk about config files, the binaries and log should not be in > > here. > > I'm also taling about config files. > > Seperate config files is a bad idea. We tolerate it now because > a lot of things wouldn't fit into rc.conf (like the sendmail > configuration data). For things that can, they should. Your > examples were all things that can. I don't understand the > benefit of breaking them up, except to have more files to worry > about, and more things that need to be writeable (or symlinked > and moved, when / isn't writeable). I think it is easier to setup, let's say FTP, if you know ALL the config files are in /etv/daemons/ftp. And the only place to start the ftpd from when booting, is from /etc/daemons/startup. When you add a user, you have to grand him or deny him access to services. This you do by changing a lot of config files, maybe forgetting some? So a central access file, is maybe not so bad. When more services are added, /etc will "explode". We already got /etc/mail and /etc/ssh, why not /etc/ftp? And then put them in /etc/daemons/, it makes more sence. db db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01bf01c208ec$b11a7380$6800a8c0>