how can I specify a specific version of a package? (samba412) reddit / freebsd ---------------------------------------------------------------------- spacebass · 2020-08-10 23:17 Hey folks, I've got a new install of 12.1 RELEASE and I'm trying to sort through an issue with samba. Everything I'm finding online says 412 is current and is in the ports. However, when I do a pkg search samba I only see options for 410 and 411. Thanks! ---------------------------------------------------------------------- kmanv · 2020-08-11 01:29 That version is not in the ports tree yet. You may want to contact the port maintainer about this or try to create the port yourself. ---------------------------------------------------------------------- darkempath · 2020-08-11 05:03 I was happily using Samba 4.10 until I saw your post, but I'm now compiling 4.11 as I type (I prefer ports over pkg). Some applications can be ported to FreeBSD very quickly after they're released, but others require a lot of tweaks and configuration. Samba is a relatively large application who's devs assumes you're using linux. Other large apps (such as MySQL) have a history of needing to work consistently across mulitple platforms (e.g. Solaris, linux, \*BSD, even Windows) so they're less tied to a specific OS and require less porting. There are some versions of Samba that never make it to FreeBSD for various reasons. However, we may be able to address the issue you're having if you explain what it is. It may be something as simple as a typo in smb4.conf. I generally use ports so I can turn off unneeded features that may cause me trouble later on (or that may require additional supporting libraries be installed). EDIT: 4.11 finished compiling and installed flawlessly. It feeds movies and TV shows to my HTPC in the loungeroom, and provides access to music for various players around the house (including my phone). Tell us your troubles! We might be able to help! ---------------------------------------------------------------------- spacebass · 2020-08-11 21:38 Thanks for the thoughtful reply You correctly intuited that what I'm dealing with is more the result of being relatively new to FreeBSD and less the result of the version of SAMBA. The super high level challenge is: I have an infrastructure that's all MacOS and Linux (with BSD for routers in the form of pfSense). I use Open Directory for directory services today and it \_just works\_. However, Apple is sunsetting a lot of their server support. In my investigation of potential replacements, I'm heavily leaning towards Samba4 running as an AD domain controller on FreeBSD. FreeBSD because it's stable and solid and lighter weight than the current forms of Debian-based linux. Samba/AD because it seems to be better supported in MacOS than straight openLDAP (which still requires modifications to each client machine). The challenge I was having with Samba was a filesystem ACL issue. I found lot's of reports on the freeBSD mailing lists, but all seemed to reference Samba43 or Samba47. It took me an embarrassingly long time to understand those versions were older than 4.10 and 4.11. I went the ports path too with 4.11 and still had the ACL issue. Ultimately, I wiped the box and reinstalled and recompiled and it just worked. ¯\\\_(ツ)\_/¯ So, I was able to set up the Samba AD DC with kerberos and bind9 (also a challenge to compile correctly - owed entirely to being a FreeBSD novice). ... got the AD DC working. Today, however, I've got a new challenge. My working SSL config seems to have....well...stopped working over night. Now ldapsearch and openssl complain that the commercial certificate isn't valid. It's a LetsEncrypt cert and I managed to lock myself out of the number of daily issue attempts. So I'll have to wait until tomorrow to see I can get it resolved. On the whole, I feel several steps closer to having a potential replacement directory server. So, that's good! And, I'm enjoying learning FreeBSD. One thing I'm noticing is that neither ports nor package do much in the way of configuring new installs. Where apt takes care of modifying config files, etc, FreeBSD seems to deliver the software on the proverbial doorstep and leave it up to the user to take it from there. Overall, despite the learning curve, I think I prefer that. It's meant having to understand, more fully, how to- for instance- configure a new nginx host from scratch and get php working where I haven't had to always get into the weeds that deeply before. Good learning process!