samba - Mar 2016 - The sad state of samba 4 adaption for home/small business routers.

Jeremy Allison <jra <at> samba.org> writes:
> 
> On Sat, Mar 12, 2016 at 11:16:36AM +0000, Andy Walsh wrote:
> > 
> > Also keep in mind that samba3.6 was successfully adopted on any device
that
> > had a usb2.0 port in the past. So slapping a usbstick/sdcard/hdd on a
cheap
> > router is already a common scenario.
> 
> Yes, and I'd like to help you do the same for Samba4.x also.
> 
> Stop moaning about it, and start helping *do* it .
> 
Oki, i just noticed that i have missed the work openembedded did in the last
months, since they seem to have solved the problem in a general way in there
trunk.
https://goo.gl/jixOqE

Its still the most complicated setup any cross compile package uses, but
this looks good. So i guess we now need to convert this to a openWRT (based
on buildroot) compatible setup.

If i understand the waf-samba.bbclass correctly they build the qemu for the
host system and configure it to use the staging_dir environment to generate
the answer files.

So first i need to create a qemu package for openWRT, since currently only a
qemu-guest package is available. I will try to get this running in the next
days and see what problems pop up adapting the openembedded logic.

Btw can you take a look and the config and check if there is anything
missing to reduce the size?
https://goo.gl/fMDbIX

thx
Andy

On Sat, Mar 12, 2016 at 05:19:13PM +0000, Andy Walsh
wrote:
> Jeremy Allison <jra <at> samba.org> writes:
> 
> > 
> > On Sat, Mar 12, 2016 at 11:16:36AM +0000, Andy Walsh wrote:
> > > 
> > > Also keep in mind that samba3.6 was successfully adopted on any
device that
> > > had a usb2.0 port in the past. So slapping a usbstick/sdcard/hdd
on a cheap
> > > router is already a common scenario.
> > 
> > Yes, and I'd like to help you do the same for Samba4.x also.
> > 
> > Stop moaning about it, and start helping *do* it .
> > 
> 
> Oki, i just noticed that i have missed the work openembedded did in the
last
> months, since they seem to have solved the problem in a general way in
there
> trunk.
> https://goo.gl/jixOqE
> 
> Its still the most complicated setup any cross compile package uses, but
> this looks good. So i guess we now need to convert this to a openWRT (based
> on buildroot) compatible setup.
> 
> If i understand the waf-samba.bbclass correctly they build the qemu for the
> host system and configure it to use the staging_dir environment to generate
> the answer files.
> 
> So first i need to create a qemu package for openWRT, since currently only
a
> qemu-guest package is available. I will try to get this running in the next
> days and see what problems pop up adapting the openembedded logic.
> 
> Btw can you take a look and the config and check if there is anything
> missing to reduce the size?
> https://goo.gl/fMDbIX
I'll take a look next week (technically it's my weekend and
I should be enjoying it, daylight savings time-change notwithstanding :-).

I'm not sure qemu should be required. I've worked with systems
getting S4 x-compiled without it - just correct choices in the
answer files.

Jeremy Allison <jra <at> samba.org> writes:
> I'll take a look next week (technically it's my weekend and
> I should be enjoying it, daylight savings time-change notwithstanding .
> 
> I'm not sure qemu should be required. I've worked with systems
> getting S4 x-compiled without it - just correct choices in the
> answer files.
> 
The problem is that openWRT/buildroot needs to-be able to support as much
targets as possible in a single package/makefile.
https://git.openwrt.org/?p=openwrt.git;a=blob_plain;f=target/Config.in
https://git.openwrt.org/?p=openwrt.git;a=tree;f=target/linux

The way openWRT creates images for routers is to cross compile multiple
targets at once and than making the img + cross compiled optional packages
available for download.

New targets are also added frequently, so from a package maintainer point of
view we have no real clue what arch/kernel/basesystem combo we will get, so
preparing answer files seems problematic. Ofc atm we could manually create
files for the most used targets, but the point would be to make the whole S4
cross compile setup fool proof.

Atm you can grab the source from git, do a make menuconfig and all packages
should compile for all platforms/targets.


thx
Andy