[opensuse] samba packaging gurus - what's the correct translation for spec file options to samba ./configure options?
Guys (Lars), I'm building an updated samba (3.5.6) for an old 10.3 box (to run in standalone mode) and wanted to make sure I got the configure options as close as possible to the spec file options. I think I have the basic options correct, but want to check if there are any additional options I should set/change to make sure that there are no conflicts with any other packages that may rely on the samba files being in any one particular place. I don't think there is any way to build an rpm from the spec due to non-existent dependency packages. From picking through the last 10.3 spec from discontinued/update it looks like the following will work: ./configure \ --prefix=/usr \ --localstatedir=/var \ --docdir=/usr/share/doc/packages \ --with-privatedir=/etc/samba \ --with-lockdir=/var/lib/samba \ --with-logfilebase=/var/log/samba \ --with-statedir=/var/run/samba \ --with-swatdir=/usr/share/samba \ --with-configdir=/etc/samba \ --enable-cups \ --with-libsmbclient \ --with-winbind Anybody see any missing or wrong options? Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Dec 27, 2010 at 12:14:49AM -0600, David C. Rankin wrote:
I'm building an updated samba (3.5.6) for an old 10.3 box (to run in standalone mode) and wanted to make sure I got the configure options as close as possible to the spec file options. I think I have the basic options correct, but want to check if there are any additional options I should set/change to make sure that there are no conflicts with any other packages that may rely on the samba files being in any one particular place. I don't think there is any way to build an rpm from the spec due to non-existent dependency packages.
From picking through the last 10.3 spec from discontinued/update it looks like the following will work:
Check the openSUSE Build Service repository network:samba:STABLE package samba at https://build.opensuse.org/package/view_file?file=samba.spec&package=samba&project=network%3Asamba%3ASTABLE for the line defining CONFIGURE_OPTIONS As these package source build for all SUSE products I expect it to work with openSUSE 10.3 as well. Please keep in mind openSUSE 10.3 isn't longer feed with security updates. Cf. http://en.opensuse.org/Lifetime Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 12/27/2010 07:20 AM, Lars Müller wrote:
Check the openSUSE Build Service repository network:samba:STABLE package samba at https://build.opensuse.org/package/view_file?file=samba.spec&package=samba&project=network%3Asamba%3ASTABLE for the line defining CONFIGURE_OPTIONS
As these package source build for all SUSE products I expect it to work with openSUSE 10.3 as well.
Please keep in mind openSUSE 10.3 isn't longer feed with security updates. Cf. http://en.opensuse.org/Lifetime
Thank you Lars, This box is an old AMD K6-2/450 that just serves as an internal machine for rsync backups, and as a fax server. It has no external ports so, while concerned about security, this box is low risk. I keep planning on retiring it, but it just keeps working... The samba build from source went fine. (although it did take 3:02 for configure and make to complete). I'll check out the spec file and give it a go. Thanks again for the help. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi - Wonder if anyone has set up a split DNS server running on a single system, with two NICs, under openSuSE? If so, did you rework any of the daemon scripts to start a second named daemon? How did you reorganize the named directories in the chrooted dir /var/lib/named? Looking at the scripts this looks rather hairy, so if someone has already done this, sure could use some pointers and reworked scripts... Marc Chamberlin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/27/2010 04:12 PM, Marc Chamberlin wrote:
Hi - Wonder if anyone has set up a split DNS server running on a single system, with two NICs, under openSuSE? If so, did you rework any of the daemon scripts to start a second named daemon? How did you reorganize the named directories in the chrooted dir /var/lib/named? Looking at the scripts this looks rather hairy, so if someone has already done this, sure could use some pointers and reworked scripts...
Have a look at dnsmasq: http://www.thekelleys.org.uk/dnsmasq/doc.html It's in the repos too. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/27/2010 4:40 PM, Lew Wolfgang wrote:
On 12/27/2010 04:12 PM, Marc Chamberlin wrote:
Hi - Wonder if anyone has set up a split DNS server running on a single system, with two NICs, under openSuSE? If so, did you rework any of the daemon scripts to start a second named daemon? How did you reorganize the named directories in the chrooted dir /var/lib/named? Looking at the scripts this looks rather hairy, so if someone has already done this, sure could use some pointers and reworked scripts...
Have a look at dnsmasq:
http://www.thekelleys.org.uk/dnsmasq/doc.html
It's in the repos too.
Regards, Lew
Thanks Lew for this pointer... I like the idea of DHCP being integrated with DNS but given the complexity I have already faced getting DHCP to work properly in our environment, for example to assign static addresses to systems with dual boot OS's using the same MAC addresses, not sure I want to try and tackle a whole new tool set. I will keep it in mind as a possible alternative... From my research, I need to run split DNS servers so that domain names that are known externally, from the internet, can also be used internally. It appears I either have a choice of running two (split) DNS servers, or find a router that will do inside to inside NAT/PAT. Not an easy task as none of the router manufacturers advertise such capability and so far I have had no luck getting answers to questions I sent some of em... So am looking at split DNS servers instead... Marc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/27/2010 05:09 PM, Marc Chamberlin wrote:
On 12/27/2010 4:40 PM, Lew Wolfgang wrote:
Have a look at dnsmasq:
http://www.thekelleys.org.uk/dnsmasq/doc.html
It's in the repos too.
Regards, Lew
Thanks Lew for this pointer... I like the idea of DHCP being integrated with DNS but given the complexity I have already faced getting DHCP to work properly in our environment, for example to assign static addresses to systems with dual boot OS's using the same MAC addresses, not sure I want to try and tackle a whole new tool set. I will keep it in mind as a possible alternative...
From my research, I need to run split DNS servers so that domain names that are known externally, from the internet, can also be used internally. It appears I either have a choice of running two (split) DNS servers, or find a router that will do inside to inside NAT/PAT. Not an easy task as none of the router manufacturers advertise such capability and so far I have had no luck getting answers to questions I sent some of em... So am looking at split DNS servers instead...
Hi Mark, You should really take a quick look at dnsmasq. I've used it for networks that sound similar to your situation, and serving static and dynamic DHCP-assigned IP's is trivially easy. All is configured from one file in /etc. I've used it in a production environment with maybe 100-hosts on an inside, non-IP-forwarded subnet, and in small natted subnets similar to a home cable-modem networks. It just works. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Dec 27, 2010 at 10:09 PM, Marc Chamberlin
but given the complexity..
you may want to try this http://www.shorewall.net/SplitDNS.html Hint, if it gets too complicated, you are most of the time doing it wrong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Dec 27, 2010 at 04:12:28PM -0800, Marc Chamberlin wrote:
Hi - Wonder if anyone has set up a split DNS server running on a single system, with two NICs, under openSuSE? If so, did you rework any of the daemon scripts to start a second named daemon? How did you reorganize the named directories in the chrooted dir /var/lib/named? Looking at the scripts this looks rather hairy, so if someone has already done this, sure could use some pointers and reworked scripts...
Last time I had to use this it worked. And the DNS server is still in
operation.
Even if you have to serve several networks with fitting zone files this
is mainly a question of the named runtime configuration. There is no
need to modify the init script as it is packaged.
Store your settings in /etc/named.d/
On 12/28/2010 10:00 AM, Lars Müller wrote:
On Mon, Dec 27, 2010 at 04:12:28PM -0800, Marc Chamberlin wrote:
Hi - Wonder if anyone has set up a split DNS server running on a single system, with two NICs, under openSuSE? If so, did you rework any of the daemon scripts to start a second named daemon? How did you reorganize the named directories in the chrooted dir /var/lib/named? Looking at the scripts this looks rather hairy, so if someone has already done this, sure could use some pointers and reworked scripts... Last time I had to use this it worked. And the DNS server is still in operation.
Even if you have to serve several networks with fitting zone files this is mainly a question of the named runtime configuration. There is no need to modify the init script as it is packaged.
Store your settings in /etc/named.d/
.conf and ensure to include this file in the /etc/sysconfig/named:NAMED_CONF_INCLUDE_FILES If this doesn't work for you please file a bug report.
Lars Thanks Lars, Cristian, Lews for your help. I did not have to use dnsmasq or set up a second DNS server after all. Turns out the latest version of Bind, which is 9, has a new feature called Views. These allow the DNS server to answer queries based on who is asking the question, and that is exactly why I needed a split DNS server. So using Views allowed me to accomplish what I was after... Pretty NEAT!
That said, there is not much in the way of good documentation/examples on how to use Views, so anyone wanting to do so, you are going to have to do some trial and error methods. Will offer a few pointers and suggestions for any openSuSE developer who happens to be reading this- 1. Do NOT use the Yast DNS server tool to do any configuration for you, if you wish to use Views. It is braindead about both views and include mechanisms and will simply trash your work on you, I don't think it can handle em yet. 2. The organization of files for the named server is somewhat difficult to comprehend. It is not really clear what files get copied out of the /etc directory over to the chroot directory /var/lib/named and what don't without grokking the scripts. What is worse is that all the config and include files exist in a flat space in /etc. This could use some reorganization so that all named files exist under a single root directory, IMHO, so as to make it easier to comprehend what files go where. In particular the built in include mechanism does not assume anything about exactly where to find include files, and if one uses it as I did, to create separate directories to hold the config files for each view, then it will force you to run the rcnamed script from the /etc directory. The fact that the rcnamed script will prepend the chroot dir path to the source file/dir name when creating the target dir, for these copy operations, forces one to use relative paths names, which is why rcnamed can only then be used from within the /etc directory once include files are defined. This is either a poor design of this script or a file model is being used that is not well documented or intuitive to understand, again IMHO! 3. Last, be careful of using rcnamed when restarting the server. It can and will delete files and directories in the /var/lib/named area without doing any kind of backup first. That is poor programming on someone's part also and breaks a fundamental rule of good computer science - NEVER delete or change user data without backing it up first and making sure you have a good backed up copy before making such changes, or deleting it!!!... Marc Chamberlin.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/31/2010 4:52 PM, Marc Chamberlin wrote:
3. Last, be careful of using rcnamed when restarting the server. It can and will delete files and directories in the /var/lib/named area without doing any kind of backup first. That is poor programming on someone's part also and breaks a fundamental rule of good computer science - NEVER delete or change user data without backing it up first and making sure you have a good backed up copy before making such changes, or deleting it!!!...
Its supposed to do that. The files you configure do not live in that directory. If you were making changes down in /varl/lib you were in the wrong place. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Dec 31, 2010 at 04:52:53PM -0800, Marc Chamberlin wrote: [ 8< ]
Thanks Lars, Cristian, Lews for your help. I did not have to use dnsmasq or set up a second DNS server after all. Turns out the latest version of Bind, which is 9, has a new feature called Views. These allow the DNS server to answer queries based on who is asking the question, and that is exactly why I needed a split DNS server. So using Views allowed me to accomplish what I was after... Pretty NEAT!
That said, there is not much in the way of good documentation/examples on how to use Views, so anyone wanting to do so, you are going to have to do some trial and error methods. Will offer a few pointers and suggestions for any openSuSE developer who happens to be reading this-
1. Do NOT use the Yast DNS server tool to do any configuration for you, if you wish to use Views. It is braindead about both views and include mechanisms and will simply trash your work on you, I don't think it can handle em yet.
Which bug report have you filed? ID please.
2. The organization of files for the named server is somewhat difficult to comprehend. It is not really clear what files get copied out of the /etc directory over to the chroot directory /var/lib/named and what don't without grokking the scripts.
Sorry, here I'm not able to follow you. /etc/sysconfig/named clearly states what's done. If the documentation isn't clear or straight enough file a bug report. Discussiong an issue on a list isn't a bug report. ;)
What is worse is that all the config and include files exist in a flat space in /etc. This could use some reorganization so that all named files exist under a single root directory, IMHO, so as to make it easier to comprehend what files go where.
Then you have to rename and reorganize the structure of the named %files section. And this results in changing the location of files. This includes the risk to break running configurations. Unfortunately moving configuration files which are tagged as %config(noreplace) in the %files section of the spec file isn't that easy.
In particular the built in include mechanism does not assume anything about exactly where to find include files, and if one uses it as I did, to create separate directories to hold the config files for each view, then it will force you to run the rcnamed script from the /etc directory.
Either the implemantation is broken or you've not read the comments in /etc/sysconfig/named Please consider to open a bug report for this particular include issue.
The fact that the rcnamed script will prepend the chroot dir path to the source file/dir name when creating the target dir, for these copy operations, forces one to use relative paths names, which is why rcnamed can only then be used from within the /etc directory once include files are defined. This is either a poor design of this script or a file model is being used that is not well documented or intuitive to understand, again IMHO!
And this sounds like you've not read the comments in the sysconfig file. Either use relative path names or fully qualified file/ path names.
3. Last, be careful of using rcnamed when restarting the server. It can and will delete files and directories in the /var/lib/named area without doing any kind of backup first. That is poor programming on someone's part also and breaks a fundamental rule of good computer science - NEVER delete or change user data without backing it up first and making sure you have a good backed up copy before making such changes, or deleting it!!!...
This is covered by which bug ID? No report in bugzilla = no issue. Which files are deleted or overwritten? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 1/3/2011 4:15 AM, Lars Müller wrote:
On Fri, Dec 31, 2010 at 04:52:53PM -0800, Marc Chamberlin wrote: [ 8< ]
1. Do NOT use the Yast DNS server tool to do any configuration for you, if you wish to use Views. It is braindead about both views and include mechanisms and will simply trash your work on you, I don't think it can handle em yet. Which bug report have you filed? ID please.
Lars - I will be happy to file a bug report, but protocol dictates that I first discuss an issue here on the newsgroup before doing so. So am waiting to hear what everyone thinks first, and if the consensus is to file it as a bug report, then I will do so...
2. The organization of files for the named server is somewhat difficult to comprehend. It is not really clear what files get copied out of the /etc directory over to the chroot directory /var/lib/named and what don't without grokking the scripts. Sorry, here I'm not able to follow you. /etc/sysconfig/named clearly states what's done. If the documentation isn't clear or straight enough file a bug report.
Discussiong an issue on a list isn't a bug report. ;)
It certainly is not clear to me, but then I didn't write the scripts and code so grokking is a bit tougher... One thing I have finally figured out is that specifying .conf files to be included for a view, in /etc MUST use an absolute path specification. A relative path name in an include statement will force the user to execute the rcnamed script from within the /etc directory. This of course means that these files will end up under /var/lib/named/etc/... I can live with that but it wasn't exactly what I was expecting or hoping for...
What is worse is that all the config and include files exist in a flat space in /etc. This could use some reorganization so that all named files exist under a single root directory, IMHO, so as to make it easier to comprehend what files go where. Then you have to rename and reorganize the structure of the named %files section. And this results in changing the location of files. This includes the risk to break running configurations.
Unfortunately moving configuration files which are tagged as %config(noreplace) in the %files section of the spec file isn't that easy. Hmmm now I don't follow you, think you are talking about something else.. What %files section? What do you mean by tagged as %config(noreplace)? I have not seen anything in the Bind/Named documents talking about this!
In particular the built in include mechanism does not assume anything about exactly where to find include files, and if one uses it as I did, to create separate directories to hold the config files for each view, then it will force you to run the rcnamed script from the /etc directory. Either the implemantation is broken or you've not read the comments in /etc/sysconfig/named
Please consider to open a bug report for this particular include issue. Well as I said, I tried to read, but didn't grok... see above comments...
The fact that the rcnamed script will prepend the chroot dir path to the source file/dir name when creating the target dir, for these copy operations, forces one to use relative paths names, which is why rcnamed can only then be used from within the /etc directory once include files are defined. This is either a poor design of this script or a file model is being used that is not well documented or intuitive to understand, again IMHO! And this sounds like you've not read the comments in the sysconfig file. Either use relative path names or fully qualified file/ path names.
3. Last, be careful of using rcnamed when restarting the server. It can and will delete files and directories in the /var/lib/named area without doing any kind of backup first. That is poor programming on someone's part also and breaks a fundamental rule of good computer science - NEVER delete or change user data without backing it up first and making sure you have a good backed up copy before making such changes, or deleting it!!!... This is covered by which bug ID? No report in bugzilla = no issue.
Which files are deleted or overwritten?
Lars Initially, I had tried to set up relative path includes for the .conf files that describe each of my views. So for example, I set up files such as /etc/internal/internal_zones.conf and /etc/external/external_zones.conf. My include statements read like: include "internal/internal_zones.conf" where I was hoping it would end up at /var/lib/named/internal/internal_zones.conf. As I mentioned above I have subsequently determined that this forces one to execute rcnamed from within the /etc directory otherwise the includes will fail.
But that said, I then wanted to place all of my zone domain configuration files within the internal or external directories so as to keep them associated with the aforementioned .conf files. So for example, my internal_zones.conf file could have a zone specified like - zone "marcchamberlin.com" in { file "internal/marcchamberlin.com"; type master; ... }; and it was these zone domain configuration files that got deleted on me... (the file "internal/marcchamberlin.com" contains all the actual DNS record specifications) I don't know how to set things up so that these zone domain configuration files could get copied from /etc though I tried to fool around with it a bit... Anywise, for now I have separated the .conf files so they are in the /var/lib/named/etc directory and my zone domain configuration files are in /var/lib/named/internal and /var/lib/named/external. I can edit those directly now and not worry about them being clobbered.. Am willing to file a bug report, as I mentioned, if that is the group consensus. I also admit that I do not fully grok the architecture and file structure intention yet, for this server, so I may be missing something and wanted to discuss it first... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/27/2010 07:20 AM, Lars Müller wrote:
On Mon, Dec 27, 2010 at 12:14:49AM -0600, David C. Rankin wrote:
I'm building an updated samba (3.5.6) for an old 10.3 box (to run in standalone mode) and wanted to make sure I got the configure options as close as possible to the spec file options. I think I have the basic options correct, but want to check if there are any additional options I should set/change to make sure that there are no conflicts with any other packages that may rely on the samba files being in any one particular place. I don't think there is any way to build an rpm from the spec due to non-existent dependency packages.
From picking through the last 10.3 spec from discontinued/update it looks like the following will work:
Check the openSUSE Build Service repository network:samba:STABLE package samba at https://build.opensuse.org/package/view_file?file=samba.spec&package=samba&project=network%3Asamba%3ASTABLE for the line defining CONFIGURE_OPTIONS
As these package source build for all SUSE products I expect it to work with openSUSE 10.3 as well.
Please keep in mind openSUSE 10.3 isn't longer feed with security updates. Cf. http://en.opensuse.org/Lifetime
Lars
Lars, Just a follow up. samba-3.5.6 rpms built fine on both 10.3 and 11.0 from the spec file. The only file I had to find to meet dependencies was ctdb-devel (rebuilt from a srpm). The rest of the packages are available in the discontinued repos. Thanks again. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Cristian Rodríguez -
David C. Rankin -
John Andersen -
Lars Müller -
Lew Wolfgang -
Marc Chamberlin