(Apr 05 2005 15:27) Mike Krieger wrote:
> 3.0 sounds promising due to:
>  Kernel 2.6
>  gcc 3.4
>  glibc 2.3.4
> However I asume this means no easy upgrade path- especially for those of us 
> with lots of self-compiled or contrib products.

It's impossible to change binary compatibility and still offer easy
upgrade paths for people with self-compiled binaries.
 
> Will this be as easy as a swup --upgrade / swup --list-alien or is this 
> going to require starting over... that's an awful lot of redevelopment.

We have not yet decided if we are going to develop an upgrade path with
swup, although I would be surprised if that would not be possible since
both 2.2 and 3.0 share swup version. However possible, it's not yet
decided if that will be officially supported.

On a production system I would not change distribution before I had to,
so moving from 2.2 to 3.0 is really not as interesting as moving from
2.2 to 3.1 (which will be the last in the 3.X series, much like 2.2 for
2.X).

Anyway, as I said this is not taken into consideration at this point.

> What's the plan for Trustix2.2- if I recall 3 years?  Is that right?

correct.



c

-- 
Christian Haugan Toldnes
Software Engineer
Trustix Secure Linux Development
Office Tel Europe: +44 (0) 161 8747070
Office Tel US: +1 888 COMODO 1  (1 888 266 6361)
Fax Europe: +44 (0) 161 8771767
Fax US: +1 201 963 9003
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
sender by replying to the e-mail containing this attachment. Replies to
this email may be monitored by Comodo for operational or business
reasons. Whilst every endeavour is taken to ensure that e-mails are free
from viruses, no liability can be accepted and the recipient is
requested to use their own virus checking software.
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to