Samba 3.0.22 Porting by Vidya Sagar

DISC SPACE: 11327520(SECTORS) PASSWORD: **

CPU TIME : 725144(SECONDS) LOC ATTR: $00000000

CONNECT TIME: 992678(MINUTES) SECURITY--READ : ANY

DISC LIMIT: UNLIMITED WRITE : AC

CPU LIMIT : UNLIMITED APPEND : AC

CONNECT LIMIT: UNLIMITED LOCK : ANY

MAX PRI : 150 EXECUTE : ANY

GRP UFID : $05670001 $0981A6C5 $000045CE $130028B8 $1B747DCB

USER UFID: $00000000 $00000000 $00000000 $00000000 $00000000

CAP: SM,AM,AL,GL,DI,OP,CV,UV,LG,PS,NA,NM,CS,ND,SF,BA,IA,PM,MR,DS,PH

The account structure for Samba can then be created as follows:

:NEWACCT SAMBA,MGR

:ALTACCT SAMBA;CAP=AM,AL,GL,ND,SF,BA,IA,PH,PM;ACCESS=(R,L,X:ANY;W,A:AC)

:ALTGROUP PUB.SAMBA;CAP=BA,IA;ACCESS=(R,L,X:ANY;W,A,S:AL)

:NEWUSER GUEST.SAMBA

:ALTUSER GUEST.SAMBA;CAP=ND,SF,BA,IA,PH;HOME=PUB

:ALTUSER MGR.SAMBA;CAP=AM,AL,ND,SF,BA,IA,PH;HOME=PUB

Next we should devise an MPE Group name unique to the version of Samba we are porting What should the Group name

be? For MPE/iX “group” names are restricted to 8 characters, upper case only [A-Z][0-9 | A-Z] For any new application

the names of account/group should be decided by the porter but should be meaningful and must be unique. Here version

is “SMB3022”, if Samba-3.0.22 is considered for port.

:NEWGROUP <version>.SAMBA

:ALTGROUP <version>.SAMBA;CAP=BA,IA,PH,PM;ACCESS=(R,L,X:ANY;W,A,S:AL)

:PURGELINK /SAMBA/CURRENT

:NEWLINK /SAMBA/CURRENT,<version>

:PURGELINK /usr/local/samba

:NEWLINK /usr/local/samba,/SAMBA/CURRENT

The reason behind adoption of such an accounting structure is to provide flexibility to switch among the various releases

of same product without actually purging the other revisions.For example, assuming this system previously had the

Samba-2.2.8a version installed; to revert back to Samba-2.2.8a, just we need to execute the following commands:

:purgelink /SAMBA/CURRENT

:purgelink /usr/local/samba

:newlink /SAMBA/CURRENT,SMB228A

:newlink /usr/local/samba,/SAMBA/CURRENT

At this point you’ve set-up the necessary MPE User and Directory structures for a successful Samba port.

Other application ports might need some additional packages like OpenSSL etc which requires to be installed apart from

the four basic packages described above. The first place to search for any additional package is

http://jazz.extenal.hp.com. The installation procedures for the packages on jazz are similar to what we have discussed for

the installation of basic four packages and are readily available along with the package. Prerequisite packages for a port

can be found from the application’s documentation.

2.A.5 Setting up the POSIX environment

It would be good idea to set up your POSIX environment during account setup. MPE provides a set of predefined

commands via the HPPXUDC.PUB.SYS file. Issue the following command on CI prompt while logged in as MGR.SAMBA:

:SETCATALOG HPPXUDC,APPEND;ACCOUNT