Puppy Linux Discussion Forum

[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/

[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'.

[rcrsn51]

[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.

[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.

• Step 1: Cofigure the CUPS of the print server Puppy to allow remote access.
  
• Step 2: Add raw mode printer on the print server Puppy.
  
• Step 3: Configure the samba on the print server Puppy.
  
• Step 4: Configure the printer on the client 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.

[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.

[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'.


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


Select 'Another Make/Manufacturer'.
Select 'Raw'.

Model: 'Raw Queue (en)'
Set 'Defailt Options'

Made the 'rawprinter' as a Local Raw Printer

[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

[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.

[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...

[maxpro4u]

I just tried this on 515 and macpup511- works great
Thank you shinobar for the clear instructions. Finding this post was the hard part

[gcmartin]

Have you seen latest PUP5.2 PPM?

See you PM

[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.

[gcmartin]

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

[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$