(old)Puppy Linux Discussion Forum

Discontinued. See the Samba4 Basic app in the Stretch Live Starter Kit project.

rcrsn51 wrote:I am not personally interested in Samba - there are simpler ways to have Puppy serve up some files.

OK, I'll bite! How would you serve up files? (I'm currently looking at FreeNAS, but haven't tried it yet).

I'd like to plug my (new, soon to be created) file server into my wireless DSL router, with the ability to deny outside users access to these files (I have not decided if I wish to allow non-local users access to any files on the machine -- that may depend on how hard it is to secure, etc.).

So I'm looking for good, secure method (either passworded, or simply denial of outside users).

What would you recommend?

Samba4 Basic moved here.

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

rcrsn51 wrote:A really simple method for setting up a Puppy fileserver is here.

If you are interested in FreeNAS, there are instructions here.

Thanks rcrsn51, I'll look into these further.

Thanks rcrsn51

Great timing! I was just looking in to setting up a print and file server on an old laptop I was looking for a use for.

Using the posted pet and start up file I was up and running in less than 10 mins and everybody here is really pleased to have somewhere on the network to share and backup their files and printing is now so much simpler rather than transferring the files to the computer with the printer installed.

I have had this old lifebook 700mhz lappy for a couple of years and it cost me £10 on ebay, its not much use for anything else but is now doing a really useful job.

Thanks again

Gary

gary101 wrote:..printing is now so much simpler rather than transferring the files to the computer with the printer installed.

Do you mean "Windows machines can now print to the server"? I thought that when configured, CUPS already enables Linux machines to print through the network.

raffy wrote: I thought that when configured, CUPS already enables Linux machines to print through the network.

In a Samba setup, the CUPS printers hosted by the server are advertised by their assigned names. This is a good thing, because a client does not need to reinstall its printer if the server's IP address changes.

However, I could not get this to work with Samba-TNG, so I removed all the printing components.

A client, either Linux or Windows, can still see the Puppy server's printers as described here.

Update The 2010-10-04 release of samba-tng-rcrsn now has full print sharing capability.

The Samba server was in the standard Puppy release many years ago.
I don`t know why it`s not included, it doesn`t take up much space really.

sunburnt wrote:The Samba server was in the standard Puppy release many years ago.

I think that you are mis-remembering. Puppy has contained Samba CLIENT functionality for a long time.

I don`t know why it`s not included, it doesn`t take up much space really.

MU once hosted a Samba server PET that was 20MB. And the current Wary repo has the samba-3.4.2-w5.pet at 28MB.

rcrsn51; No... In fact it was included in a release or two back in Puppy2xx.
The 2 library files "smbd" and "nmbd" which make the Samba server work,
are less than 2 mb. ( I think, it`s been awhile and they may be bigger now. )

[Update] The version of samba-tng-rcrsn dated 2010-10-04 can now handle network print sharing.

There are also instructions for setting up a headless, dedicated server.

.

rcrsn51 wrote:How to Use Samba-TNG in Puppy - Part B

Thanks for all the hard work, rcrsn51!...

I haven't gotten a chance to try it, but it looks like every day I dawdle, it improves!

I have an old "toaster" that I plan to turn into a fileserver, but based on what I'm seeing here, I think I'll also try to make it a print-server at the same time...

.

[Update] You can password protect your Samba printers by removing the "guest OK" entry. However, you will then need a different CUPS smb backend that allows authentication. Read here about smbw.

[Update] There is a new Samba client package attached to Part A above that contains an updated samba-login tool. This version lets you more easily change the default login settings and keep them from one session to the next.

Note that the files are no longer in /root/my-applications/bin.

The samba-adduser script in samba-tng-rcrsn-admin-1.0 has moved to a new location.

Here are snapshots of the two samba-tng-rcrsn client tools:

samba-login


samba-shares

rcrsn51 wrote:Here are snapshots of the two samba-tng-rcrsn client tools:

samba-login


samba-shares

rcrsn51

can you advise on making Samba-TNG work for FatDog64?

I was looking at compiling the full version from source (samba-3.5.6), but the setup and config is daunting.

Looking at the posts here makes me think that this is just the ticket for home networks!

As you've done all this amazing work I'd love to use it.

moB

"Think not, is my eleventh commandment;
and sleep when you can, is my twelfth. "
{Stubb, to himself}
- Herman Melville, The Whale (Moby-Dick)

I built it using the absolute defaults: This puts everything into /usr/local/samba.

You could then take the samba-start and samba-stop scripts out of the 32 bit version and use them to run the server.

BTW, I downloaded fatdog and the devx file. But I couldn't get the devx to load at bootup. What am I missing?

rcrsn51 wrote: BTW, I downloaded fatdog and the devx file. But I couldn't get the devx to load at bootup. What am I missing?

I had a similar event. Perhaps you put the devx in the fd64 psubdir as we did here?

When a symlink to the file was placed on the root (ie "C") drive the bootmanager was able to load devx. (I like to keep the puppy stuff out of ms-Win's stuff in one easy to find place.)

Hope this helps.

Thanks for the tips on using your samba tools. I will look into it and try to get my tiny brain around it

moB

"Elves and Dragons!" I says to him.
"Cabbages and potatoes are better for
you and me."

-- J. R. R. Tolkien