Puppy Linux Discussion Forum

lcrimail · Joined: 30 Jun 2008 Posts: 25 Location: Italia

I have configured rc.samba succesfully but when I execute /etc/rc.d/rc.samba start ...(see the image below).

I don't succeed to execute the libdm command...(see the image)

lcrimail · Joined: 30 Jun 2008 Posts: 25 Location: Italia

Otherwise when I execute Testparm this is the message:

disciple · Posted: Sat 19 Jul 2008, 17:21 Post subject:

Oh, OK. So you're using the official samba package again (the dotpup doesn't need libdm).

You can get libdm from http://www.murga-linux.com/puppy/viewtopic.php?p=145728#145728

Make a link to it called libdm.so.0, and make sure it is executable.

Hopefully that will be the last problem to solve

lcrimail · Joined: 30 Jun 2008 Posts: 25 Location: Italia

the response is like the photo in attachment.

now how can i browse the windows network from puppy?

lcrimail · Joined: 30 Jun 2008 Posts: 25 Location: Italia

ip ip urrà!!!!

i can see puppy computer in windows network, i can share with windows.

Into my mac computer I don't see puppy, it's compatible samba with mac?

I have another problem, i would like to do the same thing in puppy 4.0 but samba 3.026 installs itself in another directory, the opt directory, and it doesn't install properly because rc.samba file doesn't exist.

If I digit this command into terminal:

/usr/sbin/smbd

puppy says: no such file or directory

What do I have to do?

disciple · Posted: Sun 20 Jul 2008, 19:05 Post subject:

smbd must be somewhere else. Try just running `smbd` in a terminal. If nothing happens, I guess you can search for it with pfind.
But I think even if it doesn't have rc.samba, that package must have some way of starting itself automatically when you boot puppy.

lcrimail · Joined: 30 Jun 2008 Posts: 25 Location: Italia

Puppy4
smbd is into /opt/samba/sbin directory.
rc.samba doesn't exist
I write this line "/opt/samba/sbin/smbd" into rc.local. Samba starts when i boot puppy4 but computer is invisible on the lan.
If I ping...puppy4 receives the package.

Pnethood do see all the network but none computer puppy4.

My mac do see other pc with windows on the lan but not puppy4

I should test with puppy3.1

disciple · Posted: Mon 21 Jul 2008, 05:22 Post subject:

I think you need to run nmbd for Puppy to show up on the network, and smbd to share things.

lcrimail · Joined: 30 Jun 2008 Posts: 25 Location: Italia

wow i resolved also with puppy 4 and it's more simple than 3.1

thank you!!!!

Ciaooooo

mawebb88 · Joined: 13 Jul 2008 Posts: 245 Location: France nr Lyon

Objective to share files on a Puppy Linux laptop to Windows XP machines and also to use the Puppy machine to as a printer server from Windows XP machines on a wired and wireless LAN.

Just spent some considerable time getting this working.

First tried to just used CUPS v1.1.23 as came with Puppy 4.00 to get CUPS lpd/lpr working. Added to the XP machines the extra printing protocol thats required “Other Network File and Print Services”. I use ZoneAlarm on the XP machines to made sure 192.168.1.* was on the trusted zone.

No joy so decided to install the CUPS 1.3.3 using PUPGet (which confusing opens PETGet which is not the same as the Puppy Package mager from the desktop install icon!!). No great progress so reversed back to v.1.1.23. (I copied my .2fs Puppy save file constantly from my frugal installed system on hda1 to a spare partition hda3 to ensure I could undo which I did many times. I used a Puppy 2.14R CD and mounting hda1 and my copy partition hda3 to do this).

Lots for Googleing and then decided to give Samba a shot. First decide to get the file server up and running. Use the PETGet version 3.026. Installed ok but seem to install in strange places and after wasting much time gave up. So un-did this and got the 3.0.25c DotPUP version (had seen on the forums that 3.0.12 had given some success also). Installed (need to install the dotpuphandler first)but lot of dependence libs missing as check using the PUPGet dependency checker. Tracked them all down on the web (some quite difficult to find) and put them in /lib and made relative symbolic links to make what PUPGet dependency checker reported as missing using ROX filer to create the links. Gradually got rid of all missing dependences.

On my EeePC901 using Puppy 4.1 there were a couple more libs missing so grabbed them off my Puppy 4.0 machine and put them in /lib and made the required symlinks again using the dependency checker to make sure everything was done

Copied the smb.conf from the forum earlier in this topic to /etc/samba. Did some changes (see latter). Run the firewall wizard to give 127.0.0. and 192.1.168. free access. Finally got some response from testparm in the console after Googleing and copying bits to my /etc/samba/smb.conf file. Had a lot of problem with browseable = yes in the printers section as testparm always reported “No” regardless. Gave up on this one in the end as it looks like testparm just ignores this.

smb.conf

disciple · Posted: Wed 13 Aug 2008, 18:51 Post subject:

Hmmm...
I think there must have been some small thing missing for your Samba sharing, and you are now sharing your printer in the other way (I can't remember what it is called, and I haven't tried it, as it would require extra software on my Win98 clients). I imagine if you stopped Samba, you could still print...

At least you can print now.