AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070403104641.55b2ff8c@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>,<dl-Cougar@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E031DEA1D@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 3 Apr 2007 10:47:05 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>
Subject: Re: ssc on linux
Message-ID: <20070403104705.7edc7520@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E031DEA1D@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E031DEA1D@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 2 Apr 2007 17:53:58 -0700 "Maxim Kozlovsky"
<maxim.kozlovsky@onstor.com> wrote:

> I've made a pass through the code so most of it compiles without
> errors with the changes Andy is reviewing.
> 
> The following modules I did not try to build - we need to run config
> for linux and fix to include appropriate config file:
> 
> nfxsh
> ssc-sshd-kb5

Linux will have a new sshd and ssh.  We will need to design a solution
to the sshd question. [Can it be done with pam configuration rather than
sshd modifications?  With kernel virtual server capabilities?]

> samba-3.21a
> socat

Do we have a special socat or can we just use the Linux package?

> sendmail

we will be using exim-tiny on Linux, so sendmail is out

> snmpd

I don't know what to do here.  I discussed with Rendell, there are lots
of ugly issues.  Ideally, we would forward port our changes to a modern
version of snmpd, but Rendell thinks thats too much work, so we might
have to port the version we have to Linux/GNU libc.  Yuck.

> Here is the list of modifications required, along with some estimates:
> 
> afs - I've hacked the config file so I could make some progress, we
> should run the config and fix to include appropriate config file. -1d
> 
> ssc-vsd/vs-ipm.c 
> ipmd - did not try to build, very platform dependent code dealing with
> network interfaces, need to be changed / rewritten for linux kernel.
> -1-2w
> 
> pm - need to rewrite the part that deals with kvm -3d
> 
> nfxdns - lots of platform dependant code with uses the internal bsd
> library structures  -1-2w 
> 
> ssc-cluster/cluster-contrl-cfg.c - minor platform dependant, has to do
> with determining if a filesystem is readonly and remounting it
> readwrite -1d

Should be modified to use library routine to do this, we have 2 or
three functions to do this laying around in our code.  The library
routine will then be made portable, and then so will everything that
uses it.

> Chassisd -  fix hardcoded syscall numbers once we have kernel support
> for the watchdog - 0d.
> 
> sm-event/emrs-api.h, sm-opt/fs.c - few little pieces of platform
> dependant code -1d
> 
> Crashsave - will need to be modified to integrate with Linux crashdump
> facility, whatever it is. -2d
> 
> Ssc-promupgrade - may need to be modified once we have kernel support
> for prom upgrade -2d
> 
> Nfxsh - once we have the right config file, there probably will be
> several days worth of additional random changes

Lots of platform dependent code in places, especially places like
'system ...' -- 'system copy all -i' for example has many platform
dependent sections.


Thanks Max, this is very helpful.

Cheers,

a
