Samba server in SFS

Configuration wizards, scanners, remote desktop, etc.
Message
Author
User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Samba server in SFS

#1 Post by shinobar »

For precise Puppies:
samba-4.0.9-precise.sfs
http://shino.pos.to/party/bridge.cgi?puppy/precise/opt/

For the Lucid Puppy:
samba-4.0.9-lucid.sfs
http://shino.pos.to/party/bridge.cgi?puppy/lupu/opt/

Code: Select all

./configure --prefix=/opt/samba --localstatedir=/var/samba --with-configdir=/etc/samba --target=i486-pc-linux-gnu

(Older versions)
A SFS file of more recent stable version of samba.
For Slacko, there is a samba sfs made by 01micko:
http://www.smokey01.com/01micko/slacko/ ... .6.1-s.sfs

For all Puppy 5.x
Get samba-3.5.6-w5.sfs from here. (Upload: 13 Feb 2011)
Note that the config file position is moved as for this sfs:
Find /etc/samba/smb.conf.sample, copy it and edit as /etc/samba/smb.conf.
From the virtual terminal, type: /etc/init.d/smb restart
The examle is guest account = spot, and the directory /root/spot is sharable from the public.
See /etc/samba/README-samba-3.5.6-w5.txt.

This sfs is large, includes all the development files, swat and documents.
Concider to use rcrsn51's Samba-TNG if you like a small pet.

For Puppy-4.x
samba-3.0.26-3-{sfs4,sfs3}.sfs from here
Note: the config file is at /etc/opt/samba/smb.conf

You may find PET package but be caution: This size of PET easily fills up your RAM.
Using the PET on 512MB RAM PC without swap may corrupts. Also note that it consumes 130MB pupsave space.

CHANGES:
samba-3.5.6-w5.sfs (Upload: 13 Feb 2011) for all Puppy-5.x.

samba-3.5.6-1-lucid.sfs(Update: 16 Feb 2011)
  • Cofigfile moved to /etc/samba/smb.conf
  • Start up script(/etc/init.d/smb) makes sure essential directories are created
samba-3.5.6-lucid.sfs (Update 27Dec 2010)
  • New release of upstream.
  • PET packages also available.
samba-3.5.5-lucid-1.sfs (Update: 18 Nov 2010)
  • Add log and spool directories(/var/log/samba, /var/spool/samba)
  • Start up script(/etc/init.d/smb) auto mount shared drive.
  • Configuration sample(/etc/opt/samba/smb.conf,sample) shared printer for cups

NOTE: configure options for samba-3.5.6-w5

Code: Select all

./configure --prefix=/opt/samba --localstatedir=/var/samba --with-privatedir=/var/samba/private --with-logfilebase=/var/log/samba --with-configdir=/etc/samba --target=i486-pc-linux-gnu --disable-netapi --without-ldap
(OLD options)

Code: Select all

./configure --prefix=/opt/samba --localstatedir=/var/opt/samba --with-configdir=/etc/opt/samba --target=i486-pc-linux-gnu --disable-netapi --without-ldap
Last edited by shinobar on Mon 07 Oct 2013, 05:50, edited 13 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

TIPS: shared folders

#2 Post by shinobar »

TIPS
Quick start:
  1. Hostname: Edit /etc/hostname to identify your PC with a unique name in your LAN.
    Its default is 'puppypc'. After changing the hostname, say 'newname', restart PC or type: 'hostname newname'.
  2. Config file: The config file is /etc/opt/samba/smb.conf.
    Find /etc/opt/samba/smb.conf.example, copy it and edit as /etc/opt/samba/smb.conf.
    The examle is guest account = spot, and the directory /root/spot is sharable from the public.
  3. Startup: From the virtual terminal, type: /etc/init.d/smb restart
    The samba starts at every boot of Puppy thanks to the start up script /etc/init.d/smb.
  4. Scan by pnethood or lameSMBxplorer. You can find your PC with the name 'puppypc' or the newname, and the shared 'spot'
ADDING SHARED FOLDERS:
Edit the config file /etc/opt/samba/smb.conf and restart samba.
Config example
Make a directory /mnt/home/public. The /mnt/home should be linux partition. Make its permission '1777'.

Code: Select all

[public]
   # the path should be readable and writable by the guest account
   path = /mnt/home/public
   force group = spot
   public = yes
   guest ok = yes
   writable = yes
   printable = no
   create mask = 0765
You can make shared folders on another partition than /mnt/home.
The file system can be any of file systems, but for Windows's NTFS, usr 'force user = root'(thanks to kanehekili).

Code: Select all

[public]
   # user root for ntfs
   path = /mnt/home/public
   force user = root
   public = yes
   guest ok = yes
   writable = yes
You can share the whole partition, say '/mnt/sda2' or some directory, say '/mnt/sda2/video'.

Code: Select all

[video]
   # the path should be readable and writable by the guest account
   path = /mnt/sda2/video
   force group = spot
   public = yes
   guest ok = yes
   writable = yes
   printable = no
   create mask = 0765
The shared directory should be readable and writable with the user 'spot'.
In case the shared partition is of Windows FAT, reboot PC or do next step.
Stop samba... '/etc/init.d/smb stop'.
Unmount the partition.
Start samba... '/etc/init.d/smb start'.
The partition is automatically mounted with the owner is the user 'spot'.

See the tips as for the samba-TNG:
http://www.murga-linux.com/puppy/viewtopic.php?t=60204

Another document on samba:
http://www.murga-linux.com/puppy/viewtopic.php?t=60981
Last edited by shinobar on Sat 18 Dec 2010, 11:05, edited 5 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: Samba 3.5.5 for Lucid Puppy

#3 Post by rcrsn51 »

shinobar wrote:Concider to use rcrsn51's Samba-TNG if you like a small pet. Although I have not yet tested it on Lucid.
It works fine for me in Lucid, but additional feedback would be appreciated.

gcmartin

Teach your QuickSET Puppy to Share files, folders and more.

#4 Post by gcmartin »

For those coming from Windows or new to sharing stuff from Linux with your local LAN users, here's a document to get you started "Simply, Teaching Puppy to SAMBA".

The SAMBA 3.5.5 that are provided should help each one of us.

Enjoy this ability to share from Puppy to your LAN.
Last edited by gcmartin on Tue 14 Dec 2010, 09:22, edited 1 time in total.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Update: samba-3.5.5-lucid-1.sfs

#5 Post by shinobar »

CHANGES:
samba-3.5.5-lucid-1.sfs (Update: 18 Nov 2010)
  • Add log and spool directories(/var/log/samba, /var/spool/samba)
  • Start up script(/etc/init.d/smb) auto mount shared drive.
  • Configuration sample(/etc/opt/samba/smb.conf,sample) shared printer for cups
If your Puppy has printers, you can use it on another PC's on the net.
If the another PC runs Windows, you need samba print share.
You need to make new printer entry in the CUPS on the print server Puppy.
The new entry does not have any driver, works raw mode.
The Windows client PC needs to install the printer driver for Windows. The new version samba-3.5.5-lucid-1.sfs is shared printer ready.
Refer the settings on /etc/opt/samba/smb.cof.sample to setup the samba, the step 3 above.
Last edited by shinobar on Thu 18 Nov 2010, 10:53, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Step 1: Cofigure the CUPS

#6 Post by shinobar »

Step 1: Cofigure the CUPS of the print server Puppy to allow remote access.

Menu > Setup > Setup Wizard > CUPS Printer Wizard
Press Administration on the new launched browser.
Mark on all the checkbox regarding shered access.
Image
Last edited by shinobar on Thu 18 Nov 2010, 10:35, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Shered printer, STEP 2

#7 Post by shinobar »

Shared printer via samba
Step 2: Add raw mode printer on the print server

Puppy.Menu > Setup > Setup Wizard > CUPS Printer Wizard
Press 'Administration' on the new launched browser.
Press 'Add printer'
Select the local printer found, then 'Continue'.
Image

Input simple name, will be seen in the network, say 'rawprinter'.
Mark on the 'Sharing' checkbox, then 'Continue.
Image

Select 'Another Make/Manufacturer'.
Select 'Raw'.
Image
Model: 'Raw Queue (en)'
Set 'Defailt Options'

Made the 'rawprinter' as a Local Raw Printer
Last edited by shinobar on Thu 18 Nov 2010, 10:34, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Shared printer, Step 3

#8 Post by shinobar »

Shared printer via samba
Step 3: Configure the samba on the print server Puppy.

Copy /etc/opt/samba/smb.conf.example to /etc/opt/samba/smb.conf. Maybe nothing to modify.
Restart samba with typing: /etc/init.d/smb restart

Code: Select all

[global]
   security = share
   map to guest = Bad User
   null passwords = Yes
   guest account = spot

   load printers = yes
   printcap name = cups
   printing = cups

[printers]
   comment = All Printers
   user account = spot
   create mode = 0700
   # the permission of the path should be 1777
   path = /var/spool/samba
   browseable = yes
   public = yes
   guest ok = yes
   printable = yes
   # allow Windows to use its printer driver
   use client driver = yes
Last edited by shinobar on Thu 18 Nov 2010, 10:10, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Shared printer, Step 4

#9 Post by shinobar »

Shared printer via samba
Step 4: Configure the printer on the client Windows.

Make the Windows client as network share enabled.
Find the shared printer from the Windows client.
Install the printer driver for the Windows.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

gcmartin

CUPS - SAMBA printing

#10 Post by gcmartin »

The steps offered here allows ANY Microsoft PC to print thru to the Printer attached to this Puppy PC.

RAW mode explanation ==> RAW mode simply means that Puppy is ONLY going to pass the print job to the printer without ANY interference.

This means that ALL PCS are responsible for having the correct driver in order for their prints to show up correctly on the printer. (This is one method of sharing printers and this method has been used since the days of Windows95 (1995). It works for any printer(s) you want to share from your Puppies!)

Hope this helps...

User avatar
maxpro4u
Posts: 293
Joined: Sat 19 Jun 2010, 18:20
Location: Rittman,Ohio,USA, In dog years,I'm dead
Contact:

#11 Post by maxpro4u »

I just tried this on 515 and macpup511- works great 8)
Thank you shinobar for the clear instructions. Finding this post was the hard part :roll:
Dell D610 1.7M w/1024mb
Testing Slacko and a few others
I'm Max Wachtel and I approve this message.
Registered Linux User #393236

gcmartin

Latest PUP5.2 PPM

#12 Post by gcmartin »

Have you seen latest PUP5.2 PPM?

See you PM

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Samba PET

#13 Post by shinobar »

Yes, I see several samba PET in the 'official' Puppy repositories.
But I don't know what works and/or what doesn't. I have never made samba PET because it becomes so large.

I am providing and can support samba server only in SFS.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

gcmartin

SAMBA

#14 Post by gcmartin »

Shinobar. Something strange. See PM
After reading that, see my post

gcmartin

What haopened ???

#15 Post by gcmartin »

Edit 1:01PM EST. Give me 2 hours to download 517 and try again from scratch. I will deliver subsequent console logs demonstrating findings for you.

Shinobar, as you have seen from my post, there are issues with both your PET-SFS and with Mobeus's that surfaced in PUP5.2 development.

I don't know what changed, but something certainly did. But, moving on, the question is can we get a SAMBA that behaves in PUP5.2 the way it did in prior PUPs.

To start, I would like the sample smb.conf that delivers with every SAMBA version I have worked with over the past 10 years. Yes, its a very confusing file, but, the instructions that are crafted instructs all to save it as a reference before starting. (and certainly, it does provide a "base" samba startup file if you just wanted to do local testing)

Next, Mobeus's PET installation cleverly Put a screen up on the desktop to get anyone of us started with SAMBA when the PET completed.

Next, most of the people in the forum world for most distros (Fedora/Ubuntu/SUSE/Madriva/Knoppix) refer to the SAMBA daemons as "smbd" and "nmbd". These are what any user who post for help in any Linux forum will be guided in using. In your latest, you have dropped the "d" which is fine for "Personalizing", but a red-herring if anyone ask for help in the Linux forums. So you may want to change that.

Further, I noticed that you had done some work in breaking out pieces of SAMBA as if to modularize it. I noticed a post you made of SAMBA memory in a PET. It confused me because when I went back to look at the memory use I cannot corraborate your findings. In fact, even though SAMBA libraries take some memory, Mobeus's PET didn't seem to achieve what you saw. If we must, we need to indicate that SAMBA is recommended to run on Puppies of a certain size when users want to share information out over the LAN.

Lastly the libraries that the SAMBA.org refers to for SAMBA. What do you think should be done as we progress forward in Puppy. Should we stay with the standard?

If we stay as close to the Linux-SAMBA standard, our user community will be able to find very consistent documentation and forum help should thay have to use this. Staying close to the standard and not attempting to modularize on our own might insure we deliver a stable implementation for the users. Its got to be consistent, stable, and documented (I'll help with this)

I only offer this as some points of why I am saying SAMBA is not working in PUP5.2. Its not a problem that you created, but it IS a problem now that we has lost this functionality in the PUP5 system.

Now, tell me how I can help the cause. PM me or email me if you must.. Here to Help.

P.S. Remember, that this one product intends to some simple LAN sharing as well as save us 10s of thousands of doallars when its used. My 2011 objective is to document how to set Puppy up to run as a PDC which saves having to pay M$

gcmartin

Looks like path problems when SAMBA completes

#16 Post by gcmartin »

Hi I promised Shinobar to post this several hours ago. Sorry for the delay.

I posted the findings to the PUPPY Beta thread because there some items that may pertain to them as well.

Hope this helps

gcmartin

A SMB.CONF that I'd like you to consider adding

#17 Post by gcmartin »

@Shinobar. I am enclosing a SAMPLE (EXAMPLE) smb.conf that I'd like you to consider shipping in the 3.5.6 updates you have planned. If you do,
I will rebuild the Puppy User Instructions around this smb.conf to make it easy for newbies to get started.

Review it and determine if you like its approach.

And, during the PET installation, the last installation window that POPs after PET install indicates that the Menu has been updated under Network. You may want to take a look at that message because teh current PET is NOT putting entry in Menu > Network. (Kirk did put an entry in Network when installing his PET in FATDOG)

Lastly, looking over your download site, I see that you had done some work on modularizing SAMBA. But, to properly use the pieces, will need some sort of document instructing what and how to piece things back together if need. See my PM to you on this.

Sometime in late January I will take the time to test and write a Puppy Guide to setting up a Puppy FULL LAN server that works same as vendor servers costing 1000-20000s of dollars. The SAMBA that you produce lets Puppy do this with ease.

Hope this helps.
Attachments
EXAMPLE_smb.conf.bz2
(748 Bytes) Downloaded 948 times

User avatar
maxpro4u
Posts: 293
Joined: Sat 19 Jun 2010, 18:20
Location: Rittman,Ohio,USA, In dog years,I'm dead
Contact:

#18 Post by maxpro4u »

Does your samba for puppy 4 use opt also? Can I use the config from 3.5.6?
Dell D610 1.7M w/1024mb
Testing Slacko and a few others
I'm Max Wachtel and I approve this message.
Registered Linux User #393236

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

samba-3.5.6-lucid.sfs and samba-3.0.26-3.sfs

#19 Post by shinobar »

maxpro4u wrote:Does your samba for puppy 4 use opt also? Can I use the config from 3.5.6?
I am running LupQ-511 with samba-3.5.6-lucid.sfs
and Puppy-431JPqs3 using samba-3.0.26-3.sfs.
Both have the same configuration at /etc/opt/samba/smb.conf.
I don't know on Fluppy, but samba-3.0.26-3.sfs may work.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
maxpro4u
Posts: 293
Joined: Sat 19 Jun 2010, 18:20
Location: Rittman,Ohio,USA, In dog years,I'm dead
Contact:

Re: samba-3.5.6-lucid.sfs and samba-3.0.26-3.sfs

#20 Post by maxpro4u »

shinobar wrote:
maxpro4u wrote:Does your samba for puppy 4 use opt also? Can I use the config from 3.5.6?
I am running LupQ-511 with samba-3.5.6-lucid.sfs
and Puppy-431JPqs3 using samba-3.0.26-3.sfs.
Both have the same configuration at /etc/opt/samba/smb.conf.
I don't know on Fluppy, but samba-3.0.26-3.sfs may work.
3.0.26-3.sfs worked on Fluppy but now my drive icons are missing :roll:
edit- using a frugal install of fluppy everything works fine-drive icons also are fine. I am going to format and do a full install of fluppy and see if the icons go missing again.
Dell D610 1.7M w/1024mb
Testing Slacko and a few others
I'm Max Wachtel and I approve this message.
Registered Linux User #393236

Post Reply