Page 1 of 2

Samba4 Basic for Tahrpup,Precise,Slacko,Lupu,variants (6 MB)

Posted: Mon 29 Jun 2015, 14:59
by fr33land
.

Posted: Mon 29 Jun 2015, 15:25
by gcmartin

Posted: Fri 03 Jul 2015, 22:14
by fr33land
Thanks for the above link. But I notice that several Puppies with built-in Samba were omitted. Was this an oversight?

I am disappointed that you did not give your endorsement to Samba4 Basic, even though it is 30% smaller and has complete documentation.

Posted: Sat 04 Jul 2015, 06:48
by gcmartin
@MikeB's version is equivalent in size, but has modern features for todays newer LAN units (including PCs) with same or improved performance with no downside penalty. His version is the "true" full "SAMBA version 4+"; not a fork. The full SAMBA community is very active to insure security for SAMBA LAN users.

His version has been made available to the PUPPY developer and user community, here, recently.

Please don't be disappointed in my not mentioning your SAMBA-TNG you reference in your opening post. I think it is covered well in the link you reference. Works!

Hope this is helpful

Posted: Sat 04 Jul 2015, 10:36
by rcrsn51
I think that you have misread something. Samba4 Basic is NOT Samba-TNG. It is a NEW project based on Samba 4.1.9.

Posted: Mon 06 Jul 2015, 22:01
by rcrsn51
Pemasu's Dpups can run Samba4 Basic.

For Squeeze 5.X.3.6.2, install tahrpup-4.1.9.pet, samba4_control-1.1.pet and samba4_patch_lupu-5.2.8.pet.

For Wheezy 3.5.2.11, install samba4_basic_tahrpup-4.1.9.pet, samba4_control-1.1.pet and samba4_patch_precise-5.7.1.pet.

--------------------------

Posted: Tue 07 Jul 2015, 10:12
by rcrsn51
Forum member rg66 has built a series of Puppies with the Xfce desktop environment. They contain Samba-TNG which is managed by the Simple File Sharing applet.

These Puppies can be upgraded to Samba4 Basic. For example, X-Slacko would require samba4_basic_tahrpup-4.1.9.pet, samba4_control-1.1.pet and samba4_patch_slacko-5.7.0.pet.

Because X-Pups keep their startup scripts in a different location than standard Puppies, there is an extra step.

1. Open the file /usr/sbin/samba4-control in a text editor.
2. At lines 51, 52 and 55 change $HOME/Startup/samba-autostart to /usr/bin/samba-autostart

From the Network menu, run Samba4 Basic Control Panel instead of Simple File Sharing.

------------------------

Posted: Tue 07 Jul 2015, 19:19
by rcrsn51
Peebee's family of LxPups can run Samba4 Basic. As usual, install samba4_basic_tahrpup-4.1.9.pet and samba4_control-1.1.pet. LxPupTahr will work OOTB. For older Ubuntu variants, install samba4_patch_precise-5.7.1.pet. For Slackware variants, use samba4_patch_slacko-5.7.0.pet.

Posted: Wed 08 Jul 2015, 03:51
by rcrsn51
TahrNOP is gray's version of Tahrpup with the Xfce desktop environment. It needs samba4_basic_tahrpup-4.1.9.pet, samba4_control-1.1.pet and samba4_patch_precise-5.7.1.pet.

Posted: Thu 09 Jul 2015, 00:15
by rcrsn51
Deleted.

Posted: Fri 10 Jul 2015, 11:59
by rcrsn51
666philb's vivid-6.5_PAE has an older version of libgnutls. So it needs samba4_basic_tahrpup-4.1.9.pet, samba4_control-1.1.pet and samba4_patch_precise-5.7.1.pet.

Posted: Sun 12 Jul 2015, 03:06
by rcrsn51
Deleted.

Posted: Sun 12 Jul 2015, 11:59
by rcrsn51
Samba4 Basic Server

Note: The Samba4 Control Panel setup creates a ready-to-use share /root/SambaShare. It requires authentication by a client - with the "guest" user (for read-only) or with "root" (for read-write).

This is a guide for managing Samba4 Basic through its Control Panel. Here are some quick-start instructions:

1. Click the Config button. It loads the configuration file /etc/samba/smb.conf into your default text editor.
2. To change the server name as seen by clients, edit Line 7. See the image below.
3. To change the share name, edit Line 13.
4. To change the path to the folder you want to share, edit Line 14.
5. To add other shares, copy and paste Lines 13-15.
6. If you mess up your configuration file, there is a backup copy in /etc/samba.

After editing the smb.conf, restart the server from the Control Panel. Avoid making changes to the server while clients are connected. This can cause hangups that will require rebooting to clear. If Samba starts to behave strangely, shut down any client machines and restart the Samba server.

------------------------

From a Linux client, you can access the server with YASSM. Be aware that running a firewall on the client or server may cause problems.

On a Windows client, create a shortcut on the desktop and make the location \\SambaServer. Note that this name starts with two back-slashes.

---------------------------

In the default configuration, all the shares you create are public. But you might want to give each user their own private folder on the server. For example:

1a. Create the Linux user "fred" with System Tools > Add new user.
1b. Open the "/home" folder. Change the properties of the "fred" folder so the owner has sole access.
1c. Assign a Samba password to "fred" with "smbpasswd -a fred".

2. Add a share entry to smb.conf:

Code: Select all

[fred]
path =  /home/fred
writable = yes
valid users = fred
3. Restart the Samba server. Go to a client machine and create a new YASSM share where you login as fred.

4. If you plan to have multiple users, replace Step 2 with the single entry:

Code: Select all

[homes]
writable = yes
In the YASSM shares, leave the Share field blank. It will be automatically assigned to the user.

------------------------------

You may want a setup with a read-only public folder.

Code: Select all

[music]
path = /mnt/sdXY/music
read only = yes
public = yes
--------------------------------

You can also assign an external drive as a share. The drive must be mounted BEFORE starting the Samba server.

Code: Select all

[USB-Drive]
path = /mnt/sdb1
writable = yes
# To make the share writable, NTFS and FAT drives need the next line
force user = root
---------------------------

To complete your Samba server, you may want a common upload area where users can share their files.

1. Create the shared folder and give it a full set of permissions.

Code: Select all

mkdir /mnt/sdXY/upload
chmod 1777 /mnt/sdXY/upload

2. Add an smb.conf entry

Code: Select all

[upload]
path = /mnt/sdXY/upload
writable = yes
public = yes

All users have permission to write to the share. They can read each other's files but cannot delete them.

----------------------------------

To auto-start the Samba server at bootup, use the control panel. It has a script in /root/Startup that waits until your network is active, then runs samba-start. You can also use the script to mount any drives that you want to share.

-------------------------

A Samba server can share its attached printer(s) with clients on the network. But it's probably simpler to run a separate P910nd print server instead.

-------------------------------

Posted: Tue 14 Jul 2015, 11:37
by rcrsn51
Deleted.

Posted: Sun 06 Dec 2015, 19:14
by Argolance
Bonsoir,
Great! But how to get all this work in French or other any other language than English?

Cordialement.

Posted: Sun 06 Dec 2015, 19:52
by rcrsn51
It looks like you are running the testparm tool. Samba4 Basic is built from a Samba package out of the Slacko repo. I checked and it does not have an NLS PET. So I looked in the Samba sources and they don't appear to have any NLS data either.

Posted: Mon 07 Dec 2015, 09:10
by Argolance
:(
...Yes, I noticed the same thing contrary to the 3.xx versions,
Strange indeed: what a pity!

Cordialement.

Posted: Sun 01 May 2016, 16:11
by fr33land
Deleted.

samba4_basic_tahrpup-4.1.9.pet link

Posted: Wed 31 May 2017, 00:48
by WiZard
Can someone point me to a download source for samba4_basic_tahrpup-4.1.9.pet. The link on page 1 seems to be broken.

Thanks

Posted: Wed 31 May 2017, 14:30
by rcrsn51
Which version of Tahrpup are you using? The recent ones already contain a Samba server package.