How to install samba 413 on FreeBSD 13R-p8 reddit / freebsd ---------------------------------------------------------------------- loziomario · 2022-05-02 11:20 Hello. I would like to install samba413 instead of samba412 on FreeBSD 13R-p8,but unfortunately I can't because a problem of wrong dependencies. Can someone help me to understand how to do that ? thanks. ​ #pkg remove samba412 : Installed packages to be REMOVED: dolphin: 21.12.3 fusefs-smbnetfs: 0.6.1_4 gvfs: 1.46.2_2 kio-extras: 21.12.3 samba412: 4.12.15_4 thunar: 4.16.11 xfce: 4.16 xfce4-desktop: 4.16.0 #pkg install samba413 Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: samba413: 4.13.17_1 Number of packages to be installed: 1 The process will require 75 MiB more space. Proceed with this action? [y/N]: y #pkg install xfce Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. The following 6 package(s) will be affected (of 0 checked): New packages to be INSTALLED: gvfs: 1.46.2_2 ----> samba412: 4.12.15_4 thunar: 4.16.11 xfce: 4.16 xfce4-desktop: 4.16.0 **as u can see xfce needs samba 412,but I want samba413. I need xfce so I can't install samba413.** ---------------------------------------------------------------------- 11B_Geek_with_gun · 2022-05-02 11:35 Not 100% about this one: Can you ln -s the 413 library as 412? ---------------------------------------------------------------------- grahamperrin · 2022-05-02 12:09 Related (unansweredin Reddit): I gained advice from developer *tcberner* in IRC: > `SAMBA_DEFAULT` is `4.12` > > and everything using `USES=samba` will depend on that > > `DEFAULT_VERSIONS+=samba=4.13` in `/etc/make.conf` will get you that ---------------------------------------------------------------------- loziomario · 2022-05-02 13:28 I'll try as soon as I can and I will mark the question as resolved if it will work. ---------------------------------------------------------------------- celestrion · 2022-05-02 14:33 > DEFAULT_VERSIONS+=samba=4.13 in /etc/make.conf will get you that OP is using `pkg`, not ports. Changes in `/etc/make.conf` are only meaningful when using ports, not `pkg`. That said, moving to ports is usually the only reasonable path forward when a site's specific needs differ to the decisions made by the package team. ---------------------------------------------------------------------- loziomario · 2022-05-02 15:07 so. Tell me if my plan is correct. I will try to remove samba412 and then I will add "DEFAULT_VERSIONS+=samba=4.13 in /etc/make.conf" and then I will try to compile samba413 from ports,that's right ? Doing like this can I install xfce from pkg ? or I should install it from ports,also ? ---------------------------------------------------------------------- grahamperrin · 2022-05-02 15:36 > and then I will try to compile samba413 from ports,that's right ? No, as far as I know you'll need to build and install the things that would otherwise depend upon `net/samba412`. For there to be no conflict when you subsequently attempt installation of `net/samba413`. Compare the shortlist (bullet points) at the foot of with your opening post here. You'll need to build and install (at least) `devel/gvfs` and `devel/kio-extras`. ---------------------------------------------------------------------- grahamperrin · 2022-05-02 15:43 > … I would like to install samba413 instead of samba412 … Is this just *curiosity*, or is there ***certainty*** that ` 4.13.17_1` will do something, for your use case, that ` 4.12.15_4` can not? ---------------------------------------------------------------------- loziomario · 2022-05-02 16:04 So,If I have understood well,I should compile these applications from ports ? dolphin: 22.04.0 fusefs-smbnetfs: 0.6.1_4 gigolo: 0.5.2 gvfs: 1.46.2_2 kde-baseapps: 22.04.0_1 kde5: 5.24.4.22.04.0 kio-extras: 22.04.0 mate: 1.26.0 nautilus: 41.2 pluma: 1.26.0_3 thunar: 4.16.11 thunar-archive-plugin: 0.4.0_1 thunar-media-tags-plugin: 0.3.0_1 thunar-vcs-plugin: 0.2.0_2 xfce: 4.16 xfce4-desktop: 4.16.0 xfce4-goodies: 4.16 that's because I'm using all of these packages,that I need,that they will be changed with their respective ports,so I need to remove the packages first of all. what's the benefit of doing all this work ? actually I'm not sure that I will do it,since I've configured and Im running sshfs. ---------------------------------------------------------------------- loziomario · 2022-05-02 16:07 exactly. I'm not sure that samba 4.13 will allow me to mount a shared disk created in Windows where I have installed the samba server,using the protocol smb 2 or 3. Because that's the point. I can't use smb. v.1 with the command "mount\_smbfs",as explained here : [https://forums.freebsd.org/threads/how-to-access-smb-cifs-share-of- my-windows-11-bhyve-vm-from- freebsd.84886/post-564165](https://forums.freebsd.org/threads/how-to- access-smb-cifs-share-of-my-windows-11-bhyve-vm-from- freebsd.84886/post-564165) ---------------------------------------------------------------------- grahamperrin · 2022-05-02 16:14 Not all. A subset. For example, Dolphin does not depend upon Samba. Dolphin's runtime dependencies include `devel/kio-extras`. ---------------------------------------------------------------------- celestrion · 2022-05-02 17:45 > I will add "DEFAULT_VERSIONS+=samba=4.13 in /etc/make.conf" and then I will try to compile samba413 from ports,that's right ? Doing like this can I install xfce from pkg ? No, this will get you back to where you are now--you'll have Samba 4.13 installed, and you'll be trying to install things that want to install 4.12 instead. The things that want 4.12 are the things that need to be built after changing `make.conf`. Also, it's generally a really bad idea to have a system where some things are installed from ports and some things are installed from `pkg`. It's possible that a package maintainer will change the default options for some package in a way that will conflict with what you've installed from ports. You should uninstall all packages and rebuilt from `/usr/ports` everything you've added through `pkg install`. There are [tools that make this a little easier](https://www.freshports.org/ports- mgmt/portmaster/), but now is a good time to consider whether moving to Samba 4.13 is worth the effort. Some day, it will be the default Samba version, and the other ports will expect it without any intervention from you. ---------------------------------------------------------------------- loziomario · 2022-05-02 18:08 I'm not sure that samba 4.13 will allow me to mount a shared disk created in Windows where I have installed the samba server,using the protocol smb 2 or 3. Because that's the point. I can't use smb. v.1 with the command "mount_smbfs",as explained here : https://forums.freebsd.org/threads/how-to-access-smb-cifs-share-of-my- windows-11-bhyve-vm-from-freebsd.84886/post-564165 ---------------------------------------------------------------------- celestrion · 2022-05-02 18:38 > mount_smbfs Pretend that this command does not exist. Remove it from your system, if it makes this easier. Samba has supported SMBv3 since 4.1. It is possible that there is no reasonable way to mount SMBv3 shares on FreeBSD. SMB isn't just a file-sharing protocol; it makes all sorts of assumptions about other aspects of system management, which is why Samba is such a large piece of software. Generally speaking, Windows clients mount shares from FreeBSD servers--not the other way around. ---------------------------------------------------------------------- loziomario · 2022-05-02 19:07 this is exactly the point. I don't want that freebsd acts as samba server and Windows as client,because doing in this way,I will share the content of a drive inside the windows 11 bhyve VM. But since it runs on a 1440x900 window,it will be not comfortable for me. I want to do the opposite. I want to start the samba server on Windows and I want to share the drive in Windows so that I can show its content in FreeBSD,where I have a larger screen,at 1920x1080. In addition,the disks that I Want to share are formatted with the NTFS fs and they are mounted inside the Windows 11 bhyve VM. ---------------------------------------------------------------------- celestrion · 2022-05-02 20:05 What you want (FreeBSD mounting Windows shares) is totally understandable, but the software might not support it because it is not the most common use-case. Features do not exist until someone puts in the effort to make them, and they do not persist if people don't keep putting effort into maintenance. ---------------------------------------------------------------------- loziomario · 2022-05-02 20:20 so ok. there is no need for me to remove samba412 doing all the job by installing the ports compatible with samba413. This thread ends here. ---------------------------------------------------------------------- DimestoreProstitute · 2022-05-03 04:42 Does your installed fusefs-smbnetfs package not work for this? ---------------------------------------------------------------------- grahamperrin · 2022-05-03 05:57 > … it's generally a really bad idea to have a system where some things are installed from ports and some things are installed from `pkg`. … Mixture is **not** a bad idea. *mixture by design* an example. /u/loziomario as you asked under , > … maybe I can use latest instead of quarterly ? Yes. ---------------------------------------------------------------------- loziomario · 2022-05-03 08:53 yeah,I know. I don't do a mixture. I do 99% packages,1% or even less of ports...and yes,I use latest version of ports from a lot of time. ---------------------------------------------------------------------- loziomario · 2022-05-03 10:15 good point. It worked at the beginning but after some time it stopped working. You can give a look below to understand why : https://forums.FreeBSD.org/threads/how-to-access-smb-cifs-share-of-my- windows-11-bhyve-vm-from-freebsd.84886/post-564942 ---------------------------------------------------------------------- celestrion · 2022-05-03 13:47 > Mixture is **not** a bad idea. We're going to have to agree to disagree there. Mixing ports and packages is a great way to subtly break things where the only way out is to undo the site-local customization that was presumably put there for a reason. > *mixture by design* Citing yourself is not really evidence. > *an example* 1. Have you followed any of OP's threads? This is not a situation where setting up a poudriere server is a reasonable course of action. 2. A poudriere setup where someone builds a whole set of packages with their site-local settings applied and then builds the occasional bit from ports and lets poudriere fetch a set of packages upstream if they meet poudriere's compatibility rubric is *not* the same as blindly installing from the upstream package repositories, smashing stuff found on stackoverflow into `/etc/make.conf` and building random bits from whatever happens to be checked out in `/usr/ports`--which is what is generally meant by "mixing ports and packages" because of the sort of desperation that tends to lead someone to that point. If someone uses existing tooling to blend their infrastructure in ways that tooling is guaranteed to keep sane, of course that's reasonable. That's using the tools as they're intended to be used. ---------------------------------------------------------------------- grahamperrin · 2022-05-03 16:40 > Citing yourself is not really evidence. It's the design of poudriere, not my design; don't shoot the messenger :-) ---------------------------------------------------------------------- loziomario · 2022-05-04 08:58 mixture rarely produced problems to me.