site  contact  subhomenews

Samba 3.0.37

July 07, 2010 — BarryK
Thanks to technosaurus, I was able to get the files to be fairly small.

# CFLAGS=" -pipe -combine -Os -momit-leaf-frame-pointer -fomit-frame-pointer -ffunction-sections -fdata-sections -fmerge-all-constants -march=i486 -mtune=i686 " LDFLAGS=" -Wl,-O4,-Os,-relax,--sort-common,--gc-sections,-s " CXXFLAGS=" -pipe -combine -Os -momit-leaf-frame-pointer -fomit-frame-pointer -fmerge-all-constants -ffunction-sections -fdata-sections -march=i486 -mtune=i686 " ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-pc-linux-gnu --enable-shared --with-configdir=/etc/samba --with-privatedir=/etc/samba/private --disable-fam --with-lockdir=/var/samba/locks --with-piddir=/var/samba/locks --with-logfilebase=/var/samba --without-ldap --with-cifsmount --without-pam --without-utmp --without-sendfile-support --without-python --disable-pie --with-libsmbclient

I have created a package '' which is only 398KB. It is very cut-down with only 'smbclient', 'nmblookup', 'mount.cifs' and 'umount.cifs', plus the 'smbc' script for CUPS printing.

I think that I will put this into the next Spup, as I am confused by Samba-tng -- it doesn't have smbmount, mount.cifs or umount.cifs.

The PET is here:


SAMBA in Quirky
Username: gcmartin
[u][b]There is a lot of confusion about SMB/CIFS and SAMBA.[/b][/u] [b]SMB/CIFS[/b] is an international standard for exchanging information on a LAN. [b]SAMBA[/b] is a linux facility that facilitates that. There are 2 sides to how a linux machine uses information on a LAN via SMB/CIFS. They are inbound and outbound. [b]INBOUND[/b] Use of LAN folders where Linux is reaching out to “pull” information from another LAN machine.This can be done via “[i]mount -t cifs //Lan-host/his_sharename /mnt/mount-point[/i]” for example. This lets me get/put information from another machine on my LAN for use into Puppy. Thus, it is inbound ONLY! [b]OUTBOUND[/b] SAMBA. [u]In its very simplest form[/u]; Allows Linux to “share one of its folders” with other machines on the LAN (Windows or LInux or OS2 or mainframes or HPUX or AIX or anyone...alike) ALL mature distros are baked with SAMBA. Puppy/Quirky, which is years in the making, is maturing at a very rapid rate. I can be very arrogant (like Microsoft) and ignore the fact that there is no one else in the world except me. But SADLY, my Puppy friends, by ignoring SAMBA and SMB/CIFS sharing outbound might be just the behavior we’ve come to despise. (This last comment is for those you fail to want to look at the need for CIFS and the ability for Puppy to insert itself, simply, into 99.9% or the world’s LANs, as a FULL participant) This is one of the many reason for SAMBA. [b]CUPS has been built around SAMBA[/b] and progresses in “lock-step” with SAMBA development. Its apparent to all that this umbilical relationship has existed for quite some time. Puppy’s/Quirky’s maturity means that at some point it will have to move its position from an inbound only distro (from a SMB/CIFS standpoint) to a full inbound-oubound distro as its appeal and its development participation continues to increase. [b]I want to make a bet with anyone who is interested. My bet[/b] is that once SAMBA is structured solidly in Quirky and it becomes apparent that it allows setting up of “shares” for use by Windows PCs, expansion of this distro is going to go the same way that RedHat-Fedora, Madriva, Suse, and Ubuntu went. Each of them saw a tremendous “increase” in its adoption and use when SAMBA was added. The reasoning is simple: It allows handling and sharing of information over SMB/CIFS to ALL Windows and other Linux machines; inbound and outbound sharing and use. I bet Puppy and Quirky will too. You may not have any way to measure, but, if I had access to the number of downloads, I bet you will see the trend that will occur. If you get the significant increase that I am projecting for you, pet yourselves on the back. P.S. #1 I still intend to build a simple instructional for setting up a share for other LAN users to use (without them having to install anything) as soon as I can find the simple features of SAMBA that allow this to occur. Up until the most recent work on SAMBA, this ability was NOT available in Quirky. P.S. #2 There is major concern about Puppy sizing. I understand and I am in support of the elders intentions. But SMB/CIFS sharing for Quirky folders is IMHO a requirement as it affords all of us some increases in how we use this distro for the productive purposes it will experience. Samba lets us do something as simple as sharing Puppy folders with our brethrens or some major functions of authenticating, managing and securing shared information across the LAN. My instructional is ONLY going to, simply, address sharing a folder with all users on the LAN. More complex uses will only follow as time permits."8 Jul 2010, 2:00"01705"'The PET Changed?"perthie"The original contained the smbc CUPS backend and the printing.auth file as described above. But they are missing from the current version in the repo. Username: 8 Jul 2010, 10:20
"01705"'Re smbc"BarryK"Yes, as I have created so many different samba PETs, I didn't want to have to maintain those scripts in all of them, so I moved them into Woof -- so there is only the one set. So, all future Woof-built puppies will have them. Username: 8 Jul 2010, 13:56
"01705"'SAMBA"gcmartin"ANYONE interested. Important information is here Might help as we go forward into future. Important to understand that [b]SAMBA (full) and CUPS are "lock-step"[/b] in progress."8 Jul 2010, 15:03"01705"'SAMBA"gcmartin"ANYONE interested. Important information is here Might help as we go forward into future. Important to understand that [b]SAMBA (full) and CUPS are "lock-step"[/b] in progress."8 Jul 2010, 15:03"01705"'Samba is from Oz"zygo"Struth! the original author of Samba was Andrew Tridgell of Oz."13 Jul 2010, 8:37"01705"'

Tags: puppy