Followed the guide and got Samba set up but having two minor problems.
From the Windows box, if I click on ‘network’, I don’t see my Antergos box. If I go into the Explorer windows and enter: \my ip\sharename, the share is accessible and I can view the movie files I shared out. How do I make my Antergos box, “browse-able”?
When I created the share in Nemo, I clicked the box to “allow others to create and delete files” but the Windows box can’t delete the files. Guessing I need to add permissions to some folder somewhere?!?!?
Attaching smb.conf file. (I added a few extra things in the Global section that I’ve carried over from the past.)
# This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # For a step to step guide on installing, configuring and using samba, # read the Samba-HOWTO-Collection. This may be obtained from: # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf # # Many working examples of smb.conf files can be found in the # Samba-Guide which is generated daily and can be downloaded from: # http://www.samba.org/samba/docs/Samba-Guide.pdf # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not made any basic syntactic errors. # #======================= Global Settings ===================================== [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH workgroup = MYGROUP # server string is the equivalent of the NT Description field server string = Samba Server # Server role. Defines in which mode Samba will operate. Possible # values are "standalone server", "member server", "classic primary # domain controller", "classic backup domain controller", "active # directory domain controller". # # Most people will want "standalone server" or "member server". # Running as "active directory domain controller" will require first # running "samba-tool domain provision" to wipe databases and create a # new domain. server role = standalone server # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the "loopback" interface. For more examples of the syntax see # the smb.conf man page ; hosts allow = 192.168.1. 192.168.2. 127. # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user "nobody" is used ; guest account = pcguest # this tells Samba to use a separate log file for each machine # that connects log file = /usr/local/samba/var/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Specifies the Kerberos or Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. ; passdb backend = tdbsam # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting. # Note: Consider carefully the location in the configuration file of # this line. The included file is read at that point. ; include = /usr/local/samba/lib/smb.conf.%m # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. ; interfaces = 192.168.12.2/24 192.168.13.2/24 # Where to store roving profiles (only for Win95 and WinNT) # %L substitutes for this servers netbios name, %U is username # You must uncomment the [Profiles] share below ; logon path = \\%L\Profiles\%U # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server ; wins support = yes # WINS Server - Tells the NMBD components of Samba to be a WINS Client # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both ; wins server = w.x.y.z # WINS Proxy - Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. ; wins proxy = yes # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The default is NO. dns proxy = no # These scripts are used on a domain controller or stand-alone # machine to add or delete corresponding unix accounts ; add user script = /usr/sbin/useradd %u ; add group script = /usr/sbin/groupadd %g ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u ; delete user script = /usr/sbin/userdel %u ; delete user from group script = /usr/sbin/deluser %u %g ; delete group script = /usr/sbin/groupdel %g usershare path = /var/lib/samba/usershare usershare max shares = 100 usershare allow guests = yes usershare owner only = yes map to guest = bad user create mask = 0777 directory mask = 0777 #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /usr/local/samba/lib/netlogon ; guest ok = yes ; writable = no ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles] ; path = /usr/local/samba/profiles ; browseable = no ; guest ok = yes # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /usr/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes # This one is useful for people to share files ;[tmp] ; comment = Temporary file space ; path = /tmp ; read only = no ; public = yes # A publicly accessible directory, but read only, except for people in # the "staff" group ;[public] ; comment = Public Stuff ; path = /home/samba ; public = yes ; writable = no ; printable = no ; write list = @staff # Other examples. # # A private printer, usable only by fred. Spool data will be placed in fred's # home directory. Note that fred must have write access to the spool directory, # wherever it is. ;[fredsprn] ; comment = Fred's Printer ; valid users = fred ; path = /homes/fred ; printer = freds_printer ; public = no ; writable = no ; printable = yes # A private directory, usable only by fred. Note that fred requires write # access to the directory. ;[fredsdir] ; comment = Fred's Service ; path = /usr/somewhere/private ; valid users = fred ; public = no ; writable = yes ; printable = no # a service which has a different directory for each machine that connects # this allows you to tailor configurations to incoming machines. You could # also use the %U option to tailor it by user name. # The %m gets replaced with the machine name that is connecting. ;[pchome] ; comment = PC Directories ; path = /usr/pc/%m ; public = no ; writable = yes # A publicly accessible directory, read/write to all users. Note that all files # created in the directory by users will be owned by the default user, so # any user with access can delete any other user's files. Obviously this # directory must be writable by the default user. Another user could of course # be specified, in which case all files would be owned by that user instead. ;[public] ; path = /usr/somewhere/else/public ; public = yes ; only guest = yes ; writable = yes ; printable = no # The following two entries demonstrate how to share a directory so that two # users can place files there that will be owned by the specific users. In this # setup, the directory should be writable by both users and should have the # sticky bit set on it to prevent abuse. Obviously this could be extended to # as many users as required. ;[myshare] ; comment = Mary's and Fred's stuff ; path = /usr/somewhere/shared ; valid users = mary fred ; public = no ; writable = yes ; printable = no ; create mask = 0765
@ricklinux Coming from the Mint world, I just found out that the way Cinnamon worked in Mint 19.0 (regarding typing a few letters of a program and having it pop up) was actually a bug in it popping up just the names of programs that started with those letters. Their 19.1 update brought a new version of Cinnamon that works the same way it does in Antergos… in that typing a few letters searches EVERYTHING … names AND file descriptions. So yep, I’m going to have to use Favorites as you suggested. Thanks for the reply!
That fixed it!!!
When I typed this command:
sudo pacman -S --needed nvidia-dkms linux-lts-headers linux-headers
I got this back: nvidia-dkms and nvidia are in conflict. Remove nvidia? [y/N]
At first, I entered ‘n’ and everything stopped.
Then I typed this:
sudo pacman -R nvidia-lts
… and got the same message. So the 2nd time around, I entered ‘y’ to remove nvidia.
Then I used the command from manuel and the drivers installed. I restarted my machine and I’m now booted into the LTS kernel!! The only thing I noticed was that my system took a tiny bit longer to get to the desktop but it loaded up just fine.
FWIW, I carried out another experiment and put a spare SSD into this same system and tried Manjaro and it resulted in the same outcome… black screen with the LTS kernel loaded. I won’t bother trying your fix with Manjaro as I like Antergos more.
Now the $64,000 question… being a newbie, can somebody break down what exactly the DKMS drivers might have fixed? Explain as if you’re talking to a small child. :)
Joe, I think originally, your first step had me (among other packages) install nvidia-lts vs nvidia-dkms. Is there any sort of performance penalty (gaming wise) using the Nvidia DKMS drivers? Are the DKMS drivers inferior in any way?
All in all, thank you all for the assistance! Another monetary donation headed your way!
@RoadHazard Interested in knowing the hardware. Motherboard brand, model, Memory type and size, Processor is a Xeon and Video card is Nvidia GTX 670?
Motherboard: ASRock Z77 Extreme 4
4, 8GB sticks for a total of 32 gigs of DDR3 RAM (generic low speed plain Jane stuff)
CPU: Intel® Core™ i5-3570K CPU @ 3.40GHz
GPU: Nvidia 670GTX
Not sure I’m explaining this right but using Antergos 19.4 and Cinnamon desktop.
If I click the ‘start’ button and type ‘ter’… I would expect it to bring up the ‘terminal’ icon so I can easily find it. Instead, at the top of the ‘search’ box is Chromium, Color, etc. I’d expect terminal at the top if I typed ‘ter’. Same for System Monitor. Typing ‘sys’ brings up a lot of things on the right side but ‘System Monitor’ is at the very bottom when I’d expect it to be at the top.
I’m almost positive there’s a way to change that behavior but for the life of me I don’t know how.
Brand new install of 19.4 Antergos. I picked the LTS option during the install… using an Nvidia 670GTX video card and have the nvidia-lts drivers installed. Cinnamon desktop.
Latest kernel boots perfectly fine but when I attempt to boot the LTS kernel, just a black screen. I can’t bring up a terminal no matter what. If I hit ctrl-alt-del, the system reboots and the latest kernel boots up fine. Looking through the logs, I see this:
Apr 30 17:04:29 roadhazardantergos systemd: Failed to start Light Display Manager.
Full log at https://pastebin.com/4zTzj0Ur
I switched to GDM and that made no difference.
PS I tried using that ptpb.pw site but I think it’s dead or gone?
Came here to say the same. Getting the following error when trying to sign into this site with Google:
- That’s an error.
The redirect URI in the request, https://sso.antergos.com/login/callback, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/1098900045599-n47ga3dgk4bvd5nv0dv1gkldil9trqe0.apps.googleusercontent.com?project=1098900045599
That’s all we know.