Should we fork Samba?

[Moose On The Loose]

Moose: The smb.conf for your working setup has this:

Code: Select all

preferred master = Yes
domain master = Yes

Many Puppy Samba packages have these set to No and there have been other reports of it not working that way.

So that would be the first change I would try with the non-working Sambas.

In the past, I have tried copying the smb.conf from the working to the non-working version. It made no difference, right down to the same error message on the XP machine.

[Moose On The Loose]

hI @Moose On The Loose

The following work is to be done on the PUP528 with your SAMBA 3.61 installed.
I'm going to assume you have a folder that is /mnt/home. Right? if so,
open a terminal and

1. type

   Code: Select all

   # ls /mnt/home

   to insure you have some files present.
2. next type

   Code: Select all

   # smbclient \\\\localhost\\puppyserver

   enter your bogas password. Assuming your password is correct, you will land at a "SMB>" prompt. Type

   Code: Select all

   ls

   at the prompt to insure you see the same files you saw in step 1, above.
3. At the SMB prompt, type

   Code: Select all

   exit

   to quit.

This insures that your server is working properly and "serving" your folder as you expect.

Your PUP528 is ready for any action your LAN PCs can throw at it. It is functioning and active.

Find out your IP address

Code: Select all

# ip address

and use it from Windows instead of the PUP528's hostname.

Let us know.

[/code]

Before following below, I checked that my version was working.
It functioned normally.
The XP Machine was rebooted sinc last tests



The following work is to be done on the PUP528 with your SAMBA 3.61 installed.
I'm going to assume you have a folder that is /mnt/home. Right? if so,
open a terminal and

Step 1:
type
Code:
# ls /mnt/home
Listed some files


to insure you have some files present.
next type
Code:

Step 2:
# smbclient \\\\localhost\\puppyserver
enter your bogas password. Assuming your password is correct, you will land at a "SMB>" prompt. Type
Code:
ls
Listed what appears to be the same files

at the prompt to insure you see the same files you saw in step 1, above.
At the SMB prompt, type
Code:
exit
to quit.

This insures that your server is working properly and "serving" your folder as you expect.

Your PUP528 is ready for any action your LAN PCs can throw at it. It is functioning and active.


Step 3:
Find out your IP address
Code:
# ip address
and use it from Windows instead of the PUP528's hostname.

XP Machine shows same error message.


Also:
The /var has
/var/log/ No samba stuff in there
/var/samba/log/ empty dir



/var/log.smbd **************
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2013/11/15 18:17:11.988335, 0] lib/util_sock.c:602(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2013/11/15 18:17:11.988462, 0] smbd/server.c:569(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address family not supported by protocol
[2013/11/15 18:17:11.993087, 0] lib/util_sock.c:602(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2013/11/15 18:17:11.993160, 0] smbd/server.c:569(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address family not supported by protocol
[2013/11/15 03:17:40, 0] smbd/server.c:1045(main)
*************************

/var/log.nmbd **************************
nmbd version 3.6.1 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2013/11/15 18:17:11, 0] nmbd/nmbd_subnetdb.c:250(create_subnets)
create_subnets: No local IPv4 non-loopback interfaces !
[2013/11/15 18:17:11, 0] nmbd/nmbd_subnetdb.c:251(create_subnets)
create_subnets: Waiting for an interface to appear ...
[2013/11/15 18:17:38, 0] nmbd/nmbd.c:66(terminate)
Got SIGTERM: going down...
[2013/11/15 03:17:40, 0] nmbd/nmbd.c:860(main)
nmbd version 3.6.1 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2013/11/15 03:18:03, 0] nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server PUPPYPC is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.2

*****
*******************************************


Reboot to working samba and all is well again

I think I'll just leave it. I have something that works

[technosaurus]

Both the samba and wine developers are clueless of how to properly share libraries. The build contains multiple static libs that are linked to several times by several different libraries. If they were smart, they would combine all the tiny static libs into one shared lib and link all the binaries against that (as the default for most distros) ...
... but samba goes a step further and defaults to larger position independent code across the board.

Fortunately we are Puppy and most people only need the client and a few others which can be built extremely small.
For workarounds see:
http://bkhome.org/blog/?viewDetailed=01705
http://bkhome.org/blog/?viewDetailed=01703

... however, if anyone is interested, I did fork samba at the last GPL2 commit here:
https://github.com/technosaurus/samba

[gcmartin]

Thanks @Technosaurus

I think 01Micko is or has already built SAMBA v4+ for 32bit Pups (at least for Slacko and Precise). I am not sure if his contribution is destined for WOOF-CE or not, but maybe. We may want to confer with him on current status. I have already tested one of his latest in his latest Slackos including 5.6s and upcoming 5.7s. In his SAMBA versions, he presents a "firstrun" which makes it simple and easy for any newbie to start sharing a folder to the LAN with some Simple understanding of what one is doing.

TaZoC has built 64bit SAMBA V4+

SAMBA allows any Linux PC to participate on a LAN such that your content, created/captured, can be extended for other users or LAN PCs....easily since all Windows and Macs have this sharing built-in. It will just show up in their Network resources Window.

We are just starting to see more and more PUP users adding SAMBA to allow the PC to share with their other PCs, NASs, and smart-devices(xPhones/xTablets/xTVs). Because of this addition to the base system, it allows the system to also be a NAS server, Backup and Restore server, media server, as well as a simple sharing operation without ever needing to change any other LAN PC or device.

Hope this helps

[technosaurus]

I split it into samba3 and samba4
https://github.com/technosaurus/samba3-GPL2
https://github.com/technosaurus/samba4-GPL2
v4 has the LDAP server stuff that is missing in v3 but is "unstable"
... I also forked gcc and binutils at their last GPL2 commit

[disciple]

You fork a surprising number of the projects that you don't seem to even like in the first place

[technosaurus]

You fork a surprising number of the projects that you don't seem to even like in the first place

I never liked GPL3, and I'm not the only one.

If anyone has a request that I fork other popular projects that have gone to the dark side of OSS, let me know (mupdf is on my TODO list already)

[amigo]

When did gcc and binutils go to GLPL3?

[technosaurus]

at versions 2.18 and 4.2.2 respectively

[amigo]

"2.18 and 4.2.2" Venerable versions there. I still build and use gcc-4.2 for some really old code. One of the main uses I have for gcc-4.2 is to compile gcc-3.4.6 which I use to compile really ancient code. Of course, by now I've gotten much better at patching old sources to compile with newer toolchains. The exception is for old C++ code. I pretty much refuse to learn anything about C++, so I still need the old tools sometimes!

I'm no fan of GPL3 either, but I don't let it get me off the track. I reject newer versions for more practical reasons. For instance, the source code for gcc is now written in C++, which means we now have a C compiler which is not able to reproduce itself, which is the gold standard by which compilers are judged. I'm currently using gcc-4.5.3 and don't really plan to update until I find that glibc will no longer compile with this old gcc version. And, when that happens, I'm hpoing that LLVM or clang will be far enough along to switch to them.

I also have never used the gold linker stuff -I have better things to do than trying to extract every gram of performance/size out of sources. Life is to short to get hung up on such things. Getting side-tracked on such details would make it impossible to build and maintain my own system at a usable level. I do enjoy being completely free of any dependence on other distros -I am always up-to-date because I am always running the latest version of my OS. LOL