Hello AIX folks,
I am changing the packaging of Samba for AIX. Presently Samba is built with
a truckload of static libs and bound up in a package that has no other
support for the supporting infrastructure.
What I'd like to do instead is make as much of the package dependant upon
shared libs and to allow for completeness of the package. In other words,
BDB, SSL, LDAP, SASL, KRB5, libiconv and gcc shared libs are all
included as *complete* packages; you'll have an LDAP server, Kerberos
support, SSL and Berkeley tools for hot backups and recovery.
You (should) need nothing else to make this work. The packages are
unconfigured; that's where you come in. Use the included example configs and
the mass of online documentation to setup your environment to your needs.
These packages are in BFF format and as such are installed using installp.
This will allow me to upgrade certain libraries along the way as the
technology and requirements change. The binary release notes will indicate
what is changing. My plans are to only change the shared libs about every 6
months or so and only when they are truly needed.
(This is actually part of a larger project to BFF many packages, which
include PHP, Apache, FreeRADIUS, the list grows a little each day, but is
about 43 a the moment. I've called the project "PWare" for "pSeries". I know
there are other sites doing this with Source Software, but this is
dependency responsive, driven by installp, more cohesive and is designed to
not interfere with, but also offer a replacement to, sites that already have
a /usr/local software repository.)
Anyway, a preliminary package is available at:
ftp://ftp.hvcc.edu/pub/pware
This includes Samba-3.0.23c with a temporary fix for an AIX panic confirmed
late last week with strptime (originally reported in Samba4) that is still
being worked on.
All software will install in /opt/pware. Be sure to examine the tree for an
understanding of where things are placed. path in particular
"/opt/pware/samba" is special. This is designed to allow several versions of
Samba to be installed simultaneously for version testing and debugging.
The installp command will automatically increase the size of the filesystems
as needed. You should look to have at leat 100MB free on /opt after install
to make room for logs if you need to collect debug information. This may
require an adjustment by you.
Another thing to note is all packages were built with gcc on AIX 5.2 and
should work fine on AIX 5.3. (I'm already working on an AIX 5.3 only version
to take advantage of compiling on the native S.)
You should, wherever possible and appropriate, upgrade AIX to recent levels:
You must agree to a license agreement that basically is a disclaimer that I
and my institution will not be held responsible, that they may adhere to
GPL, LGPL and other appropriate licensing agreements (where applicable) and
that copyrights are held by their respective owners.
When the package is extracted use the following commands that assume you are
cd'd to the extraction directory.
To view the license agreement:
installp -lE -d.
To preview the install:
installp -agpYX -d. all
To install all packages:
installp -agYX -d. all
To remove all packages:
installp -u pware.*
To create a new table of contents:
inutoc .
You can also use "smitty install" to manage installp packages.
It is recommended that this software not be used immediately in production
and be tested first in your environment with non-production data. We *are*
using this style (in AIX 5.3 compiled form) in a production environment and
it is working wonderfully. Please provide any feedback regarding operation,
packaging or basic AIX support to me off-list unless it will benefit many.
Be sure to look at the README for some basic known AIX issues.
Cheers,
Bill

Hi,

9/12/06, William Jojo <jojowil (AT) hvcc (DOT) eduwrote:
--
Hello AIX folks,
--
I am changing the packaging of Samba for AIX. Presently Samba is built with
a truckload of static libs and bound up in a package that has no other
support for the supporting infrastructure.

That's good news!

What I'd like to do instead is make as much of the package dependant upon
shared libs and to allow for completeness of the package. In other words,
BDB, SSL, LDAP, SASL, KRB5, libiconv and gcc shared libs are all
included as *complete* packages; you'll have an LDAP server, Kerberos
support, SSL and Berkeley tools for hot backups and recovery.

Great, i'll test here in a 5.3 server and give some feedback about its
behavior. Have you tried using it with Symas CDS?

Hi,

9/12/06, William Jojo <jojowil (AT) hvcc (DOT) eduwrote:
--
Hello AIX folks,
--
I am changing the packaging of Samba for AIX. Presently Samba is built with
a truckload of static libs and bound up in a package that has no other
support for the supporting infrastructure.

That's good news!

What I'd like to do instead is make as much of the package dependant upon
shared libs and to allow for completeness of the package. In other words,
BDB, SSL, LDAP, SASL, KRB5, libiconv and gcc shared libs are all
included as *complete* packages; you'll have an LDAP server, Kerberos
support, SSL and Berkeley tools for hot backups and recovery.

Great, i'll test here in a 5.3 server and give some feedback about its
behavior. Have you tried using it with Symas CDS?

Message
From: "Stefan (metze) Metzmacher" <metze (AT) samba (DOT) org>
To: "Carlos Eduardo Pedroza Santiviago" <segfault (AT) core-dumped (DOT) org>
Cc: "William Jojo" <jojowil (AT) hvcc (DOT) edu>; <samba (AT) lists (DOT) samba.org>;
<samba-technical (AT) lists (DOT) samba.org>
Sent: Thursday, September 28, 2006 8:31 AM
Subject: Re: AIX Testers Needed.

PGP SIGNED MESSAGE
Hash: SHA1

Carlos Eduardo Pedroza Santiviago schrieb:
Hi,
>
>What I'd like to do instead is make as much of the package dependant
upon
>shared libs and to allow for completeness of the package. In other
words,
>BDB, SSL, LDAP, SASL, KRB5, libiconv and gcc shared libs are
all
>included as *complete* packages; you'll have an LDAP server, Kerberos
>support, SSL and Berkeley tools for hot backups and recovery.
>
It would be really nice to have some more AIX machines in our build-farm!

How many? I'm adding 8 more CPUs and 16GB to our 560 Saturday (which is one
of many reasons my AIX patches are way behind)

I can create you a .4 entitled VIC (presented as 2 VCPU with SMT, so 4
logical CPU) with 2 GB memory. How much disk does it need?

Btw: the SAMBA_3_0 branch currently fails to build on AIX,
--
;host=aix1;tree=samba_3_0;compiler=gcc
with:
ld: 0711-783 WARNING: TC overflow. TC size: 90328 Maximum size:
65536
Extra instructions are being generated for each reference to a TC
symbol if the symbol is in the TC overflow area.

I fixed this a couple of times. :-) You need "-bbigtoc" anywhere you do
linking (shared libs, execs, etc)

--
;host=oehmesrs6k;tree=samba_3_0;compiler=cc
the problem here is known, the pidl generated files are commited to the
svn tree without using and the cc compiler rejects to
compile enums with negative values

It would be nice to get this problems fixed

Which cc compiler? I'll look it up.

Cheers,

Bill

metze
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

DLmjC5PCKxvZ/s2zxfTvpH8=
=krXU
PGP SIGNATURE

Message
From: "Stefan (metze) Metzmacher" <metze (AT) samba (DOT) org>
To: "William Jojo" <jojowil (AT) hvcc (DOT) edu>
Cc: "Carlos Eduardo Pedroza Santiviago" <segfault (AT) core-dumped (DOT) org>;
<samba (AT) lists (DOT) samba.org>; <samba-technical (AT) lists (DOT) samba.org>
Sent: Thursday, September 28, 2006 10:30 AM
Subject: Re: AIX Testers Needed.


>>
;host=aix1;tree=samba_3_0;compiler=gcc
with:
ld: 0711-783 WARNING: TC overflow. TC size: 90328 Maximum size:
>65536
Extra instructions are being generated for each reference to a
TC
symbol if the symbol is in the TC overflow area.
>
>
>I fixed this a couple of times. :-) You need "-bbigtoc" anywhere you
do
>linking (shared libs, execs, etc)
>
In samba4 we use this:

CPP = ccache gcc -E
CPPFLAGS = -I./include -I. -I./lib -D_SAMBA_BUILD_=4 -DHAVE_CNFIG_H
CC = ccache gcc
CFLAGS = -Wall -I./include -I. -I./lib -D_SAMBA_BUILD_=4
- -DHAVE_CNFIG_H
PICFLAG =
LD = ccache gcc
LDFLAGS = -Wl,-brtl,-bexpall,-bbigtoc -L./bin
STLD = /usr/bin/ar
STLD_FLAGS = -rcs
SHLD = ccache gcc
SHLD_FLAGS = -Wl,-G,-bexpall -L./bin
SHLIBEXT = so

should I change SHLD_FLAGS to -Wl,-G,-bexpall,-bbigtoc -L./bin ?

Definitely. :-)

Cheers,

Bill

PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

f6SRDgmj5razPa7NZcw9F9E=
=FnjF
PGP SIGNATURE

Message
From: "Stefan (metze) Metzmacher" <metze (AT) samba (DOT) org>
To: "William Jojo" <jojowil (AT) hvcc (DOT) edu>
Cc: <samba (AT) lists (DOT) samba.org>; <samba-technical (AT) lists (DOT) samba.org>
Sent: Thursday, September 28, 2006 9:50 AM
Subject: Re: AIX Testers Needed.

PGP SIGNED MESSAGE
Hash: SHA1

Hi William,

It would be really nice to have some more AIX machines in our
build-farm!
>
>How many? I'm adding 8 more CPUs and 16GB to our 560 Saturday (which is
one
>of many reasons my AIX patches are way behind)
>
>I can create you a .4 entitled VIC (presented as 2 VCPU with SMT, so 4
>logical CPU) with 2 GB memory. How much disk does it need?
>
1GB free disk would be nice, but 2GB memory isn't needed 512MB would do
it really fine.

It would be nice to have each production release of AIX in the farm.

, so 512MB it is. How about a 5.2 and 5.3 system? Just need some specifics
on rootpw and any other specifics that are important. I can get those
systems rockin' next week for you. (Gotta find my later 5.2 CD's for virtual
support, but the 5.3 I can do immediately)

Btw: the SAMBA_3_0 branch currently fails to build on AIX,
>I fixed this a couple of times. :-) You need "-bbigtoc" anywhere you
do
>linking (shared libs, execs, etc)
>
Ah, thanks! I somehow gets lost somewhere in samba3's configure after
it's added to DYNEXP, I'm debugging this currently.
>
>>
;host=oehmesrs6k;tree=samba_3_0;compiler=cc
the problem here is known, the pidl generated files are commited to the
svn tree without using and the cc compiler rejects to
compile enums with negative values
>Which cc compiler? I'll look it up.
>
I don't know, it's AIX 5.2

but with the flags it build fine on samba4,
so we could workarround.

That's a gcc option, correct? and you're compiling with cc?

I'll have to svn the samba_3_0 tree and try it here to get the specifics.

Cheers,

Bill

--
metze
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

qePSlZ2uR+oVzfwSi8vXdZQ=
=9SNv
PGP SIGNATURE

PGP SIGNED MESSAGE
Hash: SHA1

Carlos Eduardo Pedroza Santiviago schrieb:
Hi,

>What I'd like to do instead is make as much of the package dependant upon
>shared libs and to allow for completeness of the package. In other words,
>BDB, SSL, LDAP, SASL, KRB5, libiconv and gcc shared libs are all
>included as *complete* packages; you'll have an LDAP server, Kerberos
>support, SSL and Berkeley tools for hot backups and recovery.

It would be really nice to have some more AIX machines in our build-farm!

Btw: the SAMBA_3_0 branch currently fails to build on AIX,

;host=aix1;tree=samba_3_0;compiler=gcc
with:
ld: 0711-783 WARNING: TC overflow. TC size: 90328 Maximum size: 65536
Extra instructions are being generated for each reference to a TC
symbol if the symbol is in the TC overflow area.

;host=oehmesrs6k;tree=samba_3_0;compiler=cc
the problem here is known, the pidl generated files are commited to the
svn tree without using and the cc compiler rejects to
compile enums with negative values

It would be nice to get this problems fixed

metze
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

DLmjC5PCKxvZ/s2zxfTvpH8=
=krXU
PGP SIGNATURE

PGP SIGNED MESSAGE
Hash: SHA1

Hi William,

It would be really nice to have some more AIX machines in our build-farm!

>How many? I'm adding 8 more CPUs and 16GB to our 560 Saturday (which is one
>of many reasons my AIX patches are way behind)

>I can create you a .4 entitled VIC (presented as 2 VCPU with SMT, so 4
>logical CPU) with 2 GB memory. How much disk does it need?

1GB free disk would be nice, but 2GB memory isn't needed 512MB would do
it really fine.

It would be nice to have each production release of AIX in the farm.

Btw: the SAMBA_3_0 branch currently fails to build on AIX,
>I fixed this a couple of times. :-) You need "-bbigtoc" anywhere you do
>linking (shared libs, execs, etc)

Ah, thanks! I somehow gets lost somewhere in samba3's configure after
it's added to DYNEXP, I'm debugging this currently.

>;host=oehmesrs6k;tree=samba_3_0;compiler=cc
the problem here is known, the pidl generated files are commited to the
svn tree without using and the cc compiler rejects to
compile enums with negative values
>Which cc compiler? I'll look it up.

I don't know, it's AIX 5.2

but with the flags it build fine on samba4,
so we could workarround.

metze
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

qePSlZ2uR+oVzfwSi8vXdZQ=
=9SNv
PGP SIGNATURE

PGP SIGNED MESSAGE
Hash: SHA1

William Jojo schrieb:
Message
From: "Stefan (metze) Metzmacher" <metze (AT) samba (DOT) org>
To: "Carlos Eduardo Pedroza Santiviago" <segfault (AT) core-dumped (DOT) org>
Cc: "William Jojo" <jojowil (AT) hvcc (DOT) edu>; <samba (AT) lists (DOT) samba.org>;
<samba-technical (AT) lists (DOT) samba.org>
Sent: Thursday, September 28, 2006 8:31 AM
Subject: Re: AIX Testers Needed.

Carlos Eduardo Pedroza Santiviago schrieb:
Hi,
What I'd like to do instead is make as much of the package dependant
>upon
shared libs and to allow for completeness of the package. In other
>words,
BDB, SSL, LDAP, SASL, KRB5, libiconv and gcc shared libs are
>all
included as *complete* packages; you'll have an LDAP server, Kerberos
support, SSL and Berkeley tools for hot backups and recovery.
It would be really nice to have some more AIX machines in our build-farm!

>How many? I'm adding 8 more CPUs and 16GB to our 560 Saturday (which is one
>of many reasons my AIX patches are way behind)

>I can create you a .4 entitled VIC (presented as 2 VCPU with SMT, so 4
>logical CPU) with 2 GB memory. How much disk does it need?

Btw: the SAMBA_3_0 branch currently fails to build on AIX,


>;host=aix1;tree=samba_3_0;compiler=gcc
with:
ld: 0711-783 WARNING: TC overflow. TC size: 90328 Maximum size:
>65536
Extra instructions are being generated for each reference to a TC
symbol if the symbol is in the TC overflow area.


>I fixed this a couple of times. :-) You need "-bbigtoc" anywhere you do
>linking (shared libs, execs, etc)

In samba4 we use this:

CPP = ccache gcc -E
CPPFLAGS = -I./include -I. -I./lib -D_SAMBA_BUILD_=4 -DHAVE_CNFIG_H
CC = ccache gcc
CFLAGS = -Wall -I./include -I. -I./lib -D_SAMBA_BUILD_=4
- -DHAVE_CNFIG_H
PICFLAG =
LD = ccache gcc
LDFLAGS = -Wl,-brtl,-bexpall,-bbigtoc -L./bin
STLD = /usr/bin/ar
STLD_FLAGS = -rcs
SHLD = ccache gcc
SHLD_FLAGS = -Wl,-G,-bexpall -L./bin
SHLIBEXT = so

should I change SHLD_FLAGS to -Wl,-G,-bexpall,-bbigtoc -L./bin ?
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

f6SRDgmj5razPa7NZcw9F9E=
=FnjF
PGP SIGNATURE

PGP SIGNED MESSAGE
Hash: SHA1

William Jojo schrieb:
Definitely. :-)

ok, commited in rev 18975(samba4) and rev 18976(samba3)

metze
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

hecqF4EVYU+JEcMxIgZ9R4=
=QdnF
PGP SIGNATURE

PGP SIGNED MESSAGE
Hash: SHA1

Hi Bill,

of many reasons my AIX patches are way behind)
I can create you a .4 entitled VIC (presented as 2 VCPU with SMT, so 4
logical CPU) with 2 GB memory. How much disk does it need?
1GB free disk would be nice, but 2GB memory isn't needed 512MB would do
it really fine.

It would be nice to have each production release of AIX in the farm.

>, so 512MB it is. How about a 5.2 and 5.3 system? Just need some specifics
>on rootpw and any other specifics that are important. I can get those
>systems rockin' next week for you. (Gotta find my later 5.2 CD's for virtual
>support, but the 5.3 I can do immediately)

That's fine!

see for what we need.

having ssh access as user build would also be cool to track down
specific bugs, but it's not strictly needed.

>;host=oehmesrs6k;tree=samba_3_0;compiler=cc
the problem here is known, the pidl generated files are commited to the
svn tree without using and the cc compiler rejects to
compile enums with negative values
Which cc compiler? I'll look it up.
I don't know, it's AIX 5.2

but with the flags it build fine on samba4,
so we could workarround.

>That's a gcc option, correct? and you're compiling with cc?

no a pidl option. see the generated code in librpc/gen_ndr/

in samba3 it gets commited to svn as samba3 should not depend on pidl.

in samba4 we recreate this files with each build, because samba4 replies
on working perl and includes pidl.

So we know how a fix for samba3 could look like, just pass
to pidl when generating the files. But we need a bit of discussion
about this. But it will be fixed for the next official release!

metze
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

ttiN0c9J/NSW6z7qXfyizJM=
=bE5b
PGP SIGNATURE

Hi,

I've installed the pware package in our testbed AIX 5.3. However, i am
unable to change permissions on my own home directory, when trying to
add a domain user to it.

I have the following situation:
- 1 SLES9 Samba/PDC with LDAP (master)
- 1 AIX 5.3 updated (53-003 IIRC), using secldapclntd (AIX's native
LDAP client), and Samba 3.0.23c. This host was added as a domain
member.

I start nmbd, smbd and winbindd, but AFAICT, it cannot translate uid
<-sid mappings.

Any clue? I'll generate a loglevel10 of this ASAP.

Hi,

I've installed the pware package in our testbed AIX 5.3. However, i am
unable to change permissions on my own home directory, when trying to
add a domain user to it.

I have the following situation:
- 1 SLES9 Samba/PDC with LDAP (master)
- 1 AIX 5.3 updated (53-003 IIRC), using secldapclntd (AIX's native
LDAP client), and Samba 3.0.23c. This host was added as a domain
member.

I start nmbd, smbd and winbindd, but AFAICT, it cannot translate uid
<-sid mappings.

Any clue? I'll generate a loglevel10 of this ASAP.