Samba version 4.1.9 trimmed version for pup releases

Message

mikeb · #1 Post by **mikeb** » Sat 27 Jun 2015, 16:36

This is a revamp on request of a recent package of SAMBA with the aim of it potentially being include as a default package in puppy.

Unneeded for general use and items that require considerable extra resources eg python have been removed leaving a working core. Hopefully at 8.9MB compressed its an attractive proposition.
The simple management gui by micko has been played with to make it more generic across puppy versions and add the option of multiple shares.
It still works on the same basis and cannot work with an existing config but then for advanced users its not needed...its meant as a beginners click and share arrangement.

Been testing on Lucid so should be good for that and anything newer though lucid itself may need a symlink for libgnutls if not updated.

Some SAMBA info here for anone trying out these packages.
http://www.murga-linux.com/puppy/viewto ... 506#585506

One to try out and give suggestions and feedback.

Pet...
https://www.dropbox.com/s/er20oufv582fj ... 6.pet?dl=1

Sfs4...
https://www.dropbox.com/s/7d0zdrwv31ovo ... 4.sfs?dl=1

Thanks to those who made the original package and other related work.

Edit...64 bit versions for testing though most releases already seem to have this. Slightly larger as its 64 bit build but same structure as 32.

https://www.dropbox.com/s/57vf9nz3114ds ... 4.pet?dl=1
https://www.dropbox.com/s/4htlfeba0fe2s ... 4.sfs?dl=1

mike

gcmartin · #2 Post by **gcmartin** » Sat 27 Jun 2015, 17:48

Installed on a pristine TahrPUP602....Works!

+1 to the opening post's sentence
I agree that the ability for a user who has content they want to share across their LAN should be able to do so without need for installing anything. It should have been OOTB as @01Micko and @TaZoC had demonstrated to us, years ago, with their version 4 distros. Its cost has little to no impact in system operations.

Thanks muchly for this community offering. Looking forward to what you have planned.

01micko · #3 Post by **01micko** » Sat 27 Jun 2015, 20:24

Hi Mike

Thanks for this. I'm going to take a peek and will probably base a build script on what is in your package. ~9M is pretty good for gz compression.

For more info on the build scripts see https://github.com/puppylinux-woof-CE/petbuilds. Currently it supports up to ~140 packages producing over 300 *.pets (DOC, DEV, NLS etc without installwatch). Apologies for OT.

EDIT3:

After successful testing I added a build script to the petbuilds git repo.

EDIT2:

REVISED PATCH... needed to export vars so functions could see.

EDIT1:

Using the mikeb pet as a template, using xz compression in the pet...

Code: Select all

# for i in samba*;do echo $i;stat -c %s $i; file $i|cut -d ' ' -f2,3,4;done
samba-4.1.19-i686.pet
7858372
xz compressed data
samba_DEV-4.1.19-i686.pet
1512928
xz compressed data
samba_DOC-4.1.19-i686.pet
12440
xz compressed data

Note that all python and perl are mv'd to *_DEV

EDIT0:

Instead of clobbering the installed gxmessage can we have a test re this patch?

Code: Select all

--- samba.sh.orig	2015-06-24 09:28:48.000000000 +1000
+++ samba.sh	2015-06-28 09:52:05.949418760 +1000
@@ -7,6 +7,9 @@
 RUNNING=`ps |grep SMBGUI|grep -v grep`
 [ "$RUNNING" != "" ] && exit 0
 
+# sort out the message app
+type gxmessage 2>&1 >/dev/null && MSGAPP=gxmessage border='-borderless' || MSGAPP=xmessage border=
+export MSGAPP border
 #just in case
 chmod 755 /etc/init.d/rc.samba
 
@@ -104,30 +107,30 @@ echo "
 testconfig(){
 	testparm -s /tmp/smb.conf >/tmp/testparm.log 2>&1
 
-	[ $? -ne 0 ]&& gxmessage -center -bg "#e77" -timeout 5 "ERROR: your smb.conf is not correct, try again" && return
+	[ $? -ne 0 ]&& "$MSGAPP" -center -bg "#e77" -timeout 5 "ERROR: your smb.conf is not correct, try again" && return
 
 	echo ""  >> /tmp/testparm.log
 	SVPATH=`grep "path" /tmp/smb.conf|awk '{print $3}'|head -n1`
 	[ ! $SVPATH ] && echo "ERROR: SHARED PATH IS MISSING" >> /tmp/testparm.log || echo "Ok" >> /tmp/testparm.log
 	WORKGROUPSET=`grep "workgroup" /tmp/smb.conf|awk '{print $3}'`
 	[ ! $WORKGROUPSET ] && echo "ERROR: WORKGROUP IS MISSING" >> /tmp/testparm.log || echo "Ok" >> /tmp/testparm.log
-	gxmessage -file /tmp/testparm.log
+	"$MSGAPP" -file /tmp/testparm.log
 }
 
 #apply new settings if passes similar test to above... gui may have been altered after test to fresh config created anyway.
 _apply(){
-	[ ! $MYPATH ] && gxmessage -center -bg "#e77" -timeout 5 -borderless -buttons "" "ERROR: Aborting, you must enter a share path" && return
-	[ ! $WGROUP ] && gxmessage -center -bg "#e77" -timeout 5 -borderless -buttons "" "ERROR: Aborting, you must enter a workgroup" && return
+	[ ! $MYPATH ] && "$MSGAPP" -center -bg "#e77" -timeout 5 $border -buttons "" "ERROR: Aborting, you must enter a share path" && return
+	[ ! $WGROUP ] && "$MSGAPP" -center -bg "#e77" -timeout 5 $border -buttons "" "ERROR: Aborting, you must enter a workgroup" && return
 	
 	testparm -s /tmp/smb.conf >/tmp/testparm.log 2>&1
-	[ $? -ne 0 ]&& gxmessage -center -bg "#e77" -timeout 20  "ERROR: Aborting, Something went wrong with the Samba configuration.
+	[ $? -ne 0 ]&& "$MSGAPP" -center -bg "#e77" -timeout 20  "ERROR: Aborting, Something went wrong with the Samba configuration.
 	 Check the log at /tmp/testparm.log. 
 	 Please try again or consult the documentation in /usr/share/help
-	 You SAMBA config has NOT been changed" && return
+	 Your SAMBA config has NOT been changed" && return
 
 	cp -af /tmp/smb.conf /etc/samba/ #instate new smb.conf IF passes test
 	/etc/init.d/rc.samba restart &
-	gxmessage -center -bg "#4c4" -timeout 6 -borderless -buttons ""  "Samba is  starting/restarting. 
+	"$MSGAPP" -center -bg "#4c4" -timeout 6 $border -buttons ""  "Samba is  starting/restarting. 
 	You can check the log at /tmp/testparm.log"
 	 
 }

I'll attach it too coz the forum plays havoc with patches.

mikeb · #4 Post by **mikeb** » Sun 28 Jun 2015, 12:46

Ok dumb mistake time... had not updated the samba.conf to share /root as default to agree with the gui.... it also avoids any arsing around with /mnt/home and variants and puppy varients by using something more generic...
Reuploaded the pet and sfs with the correction

REVISED PATCH... needed to export vars so functions could see.

As far as i knew no variables were shared between functions (I did have a problem at one point) and therefore only came from gtkdialog function calls so did not need exporting...which one did I miss?

Well gxmessage... I refused to support the disgusting yaf splash mess and all the pups i saw symlinked gxmessage to xmessage to replace the real gxmessage so assumed this was still the case resulting in that awful display and lost functions.

I find it hard to support crap

...plus if its going to be merged then its up to the dev to decide what method is going to be used ultimately.

mike

mikeb · #5 Post by **mikeb** » Sun 28 Jun 2015, 12:49

Can you post messages as otherwise i get no notifications.

I don't speak diff...i find its a barrier to many who might otherwise contribute and restricts real progress...sling me a modified file instead.

Mike

mikeb · #6 Post by **mikeb** » Sun 28 Jun 2015, 12:52

diff...great tool for updating large sources... seems a bit silly for bash scripts.
Just my 5 cents

mike

01micko · #7 Post by **01micko** » Sun 28 Jun 2015, 13:03

mikeb wrote:Can you post messages as otherwise i get no notifications.

I don't speak diff...i find its a barrier to many who might otherwise contribute and restricts real progress...sling me a modified file instead.

Mike

mikeb wrote:diff...great tool for updating large sources... seems a bit silly for bash scripts.
Just my 5 cents

mike

Got it

mikeb · #8 Post by **mikeb** » Sun 28 Jun 2015, 13:54

Ok got that...seems to make sense for xmessage/gxmessage. (..the latter does sdo a sexy borderless

likewise I never found a decent alternative to gtklogfileviewer )

So export only related to that and not other variables after all.

Well the pet/sfs are not intended as add on packages as you are probably aware though others may take them as otherwise. I will however pop in this upsated samba.sh.

I have a 64 bit samba of 4.1.3 from ibiblio/puppy... a suitable base to work with or is there something newer?

mike

mikeb · #9 Post by **mikeb** » Sun 28 Jun 2015, 14:08

I noticed its calling gtkdialog rather than gtkdialog4 ... just wondered if in some cases gtkdialog may be a link to 3 which won't work...again may not be relevant as a built in package. (the original script called gtkdialog3 so must have expected that to be a symlink to 4...I know this stuff changes like the wind in puppy so I played safe)

mike

01micko · #10 Post by **01micko** » Sun 28 Jun 2015, 14:14

Oh, yes, that mess.. gtkdialog,1,2,3,4,5 .. nearly got to 6. Just add the 4 back on, as I strip it it off because any distro I build only has one gtkdialog exec and it has symlinks to cater for legacy stuffs.

-

That 4.1.3 64 bit version is about a year old; recent enough for most I would think. Compiled against 2 y.o. slackware libs so in the context of Puppy is reasonable for almost any 64 bit version available. YMMV.

mikeb · #11 Post by **mikeb** » Sun 28 Jun 2015, 14:18

Ok I will work with that build then...seems to have no noticeable effect on functionality.

At least gtkdialog4+ has backwards compatibility ...I usually symlink 3 to 4 or whatever now. Fun playing the 'one method fits all' game.

By the way sometimes when testing I get error = 13 permission denied... any clues?

packages updated with newer samba.sh

mike

slavvo67 · #12 Post by **slavvo67** » Fri 03 Jul 2015, 22:23

Hi MikeB:

She's not working in Barry's QU. My Samba Off button doesn't want to go green. On test it reads my smb.conf is not correct. I've never successfully used Samba yet, so it could surely be me. Any thoughts?

Best,

Slavvo67

gcmartin · #13 Post by **gcmartin** » Sat 04 Jul 2015, 06:35

I think that is a library issue on the 32bits Quirkys from @BarryK. The PET does NOT install correctly and is the root of the problem. Stay tuned.

BTW, are you using @BarryK's full install to USB/HDD? Or did you use one of the Live methods?

01micko · #14 Post by **01micko** » Sat 04 Jul 2015, 08:34

@slavvo67

Try running:

Code: Select all

/etc/init.d/rc.samba start

Tell us any messages you receive from that command. (if any or none).

mikeb · #15 Post by **mikeb** » Sat 04 Jul 2015, 09:43

hmm did get the effect that pidof was useless but that was on something much older...had to use a ps/grep hack instead. That's what detects which color button to show.

If you have a premade samba.conf the gui is useless...it can only work with configs written by itself. Though if the test shows an error then there is probably an error...could you post the contents here.

mike

slavvo67 · #16 Post by **slavvo67** » Sat 04 Jul 2015, 19:43

I'm going to try on a Fresh QU just to see. Mick0, thanks but that didn't work. GCMartin, I always use Barry's full USB installs. Still the most automated way to get Puppy on a USB, I think.

I'll get you all more facts soon.

Slavvo67

rcrsn51 · #17 Post by **rcrsn51** » Sun 05 Jul 2015, 10:08

@slavvo67: I tried some Samba4 packages in Quirky April 702 and it is missing many required components. But there are some older packages that work in Quirky. The forum's Samba gurus can recommend one.

gcmartin · #18 Post by **gcmartin** » Sun 05 Jul 2015, 18:36

Just had this report handed in:

Blue Pup V6 (Based on QT 6.0.5 k3-12-6)

Code: Select all

# date
Sun Jul  5 17:08:45 BST 2015
# uname -a
Linux BluePupV6 3.12.6 #1 SMP Wed Dec 25 02:35:43 GMT 2013 i686 i686 i686 GNU/Linux
# /etc/init.d/rc.samba start
Starting Samba:  /usr/sbin/smbd -D
                 /usr/sbin/nmbd -D
# 
Then reboot:
# date
Sun Jul  5 17:14:54 BST 2015
# uname -a
Linux BluePupV6 3.12.6 #1 SMP Wed Dec 25 02:35:43 GMT 2013 i686 i686 i686 GNU/Linux
# /etc/init.d/rc.samba start
Starting Samba:  /usr/sbin/smbd -D
[2015/07/05 17:15:34,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.smbd': No such file or directory
[2015/07/05 17:15:34,  0] ../source3/lib/dumpcore.c:249(dump_core_setup)
  Unable to setup corepath for smbd: No such file or directory
[2015/07/05 17:15:34,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.smbd': No such file or directory
[2015/07/05 17:15:34,  0] ../source3/smbd/server.c:1205(main)
  smbd version 4.1.9 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2013
[2015/07/05 17:15:34.599710,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.smbd': No such file or directory
[2015/07/05 17:15:34.600444,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.smbd': No such file or directory
[2015/07/05 17:15:34.600658,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.smbd': No such file or directory
                 /usr/sbin/nmbd -D
Unable to setup corepath for nmbd: No such file or directory
[2015/07/05 17:15:34,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory
[2015/07/05 17:15:34,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory
[2015/07/05 17:15:34,  0] ../source3/nmbd/nmbd.c:904(main)
  nmbd version 4.1.9 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2013
[2015/07/05 17:15:34.639165,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory
[2015/07/05 17:15:34.639908,  0] ../lib/util/debug.c:595(reopen_logs_internal)
  Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory
#

UCF2FS Pup (Based on Unicorn-6.0 k3.14.20)

Code: Select all

# date
Sun Jul  5 17:49:44 BST 2015
# uname -a
Linux UCF2FS-Pup 3.14.20 #1 SMP Thu Oct 9 16:57:53 BST 2014 i686 i686 i686 GNU/Linux
# /etc/init.d/rc.samba start
Starting Samba:  /usr/sbin/smbd -D
/usr/sbin/smbd: error while loading shared libraries: libgnutls.so.28: cannot open shared object file: No such file or directory
                 /usr/sbin/nmbd -D
/usr/sbin/nmbd: error while loading shared libraries: libgnutls.so.28: cannot open shared object file: No such file or directory
#

This report sheds some light on what is happening in @ETP'S and @BarryK's 32bit distros.

My thinking is that this might need be added to default conf

Code: Select all

[global]
    log level = 2
    log file = /var/log/samba/log.%m
    max log size = 50
    debug timestamp = yes

And the log pathname should "match" as much as possible the existing available path in modern PUP distro's filesystem. At the very least, the majority of them. The one shown above is what would be found in the LightHouse/PhatSlacko distro. I think this is the SAMBA default, though.

Here's Lighthouse's lib

Any helpful Ideas on the lib issues shown in the report?

mikeb · #19 Post by **mikeb** » Mon 06 Jul 2015, 10:13

Blue Pup V6...thats suggests a broken save system or more likely /var/log is being erased at shutdown....

UCF2FS Pup...needs a symlink to whatever gnutls is included this week.

Neither will be fixed by playing with the samba config.

quirky missing components...well its pretty standard stuff but then we are dealing with quirky. gnutls will most likely be one of them...symlinking seems to work...it did in Lucid.

mike

rcrsn51 · #20 Post by **rcrsn51** » Mon 06 Jul 2015, 12:27

mikeb wrote:quirky missing components...well its pretty standard stuff but then we are dealing with quirky. gnutls will most likely be one of them...symlinking seems to work...it did in Lucid.mike

You can't symlink to files that aren't there. But for another 3MB of content, you can have Samba4 in Quirky April 702.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Samba version 4.1.9 trimmed version for pup releases

Samba version 4.1.9 trimmed version for pup releases