Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 21 Sep 2011 14:29:46 +0200
From: Igmar Palsenberg <igmar@...senberg.com>
To: owl-dev@...ts.openwall.com
Subject: Re: Owl 4.0 priorities



> Right.
> 
> This is needed for and allows for not only kernel update, but also glibc
> update, although we'll also need to update binutils first (but this
> should be easy).  So maybe the next steps after gcc update are: binutils
> update, glibc update.  I think having fresh glibc is highly desirable
> for work on and updates of other userland packages.  Updating/testing
> them on older glibc, which is to be updated before the release anyway,
> is a less productive use of our time.

Why is a glib update needed in the first place ? 

>> * Packetize new stuff / update existing.  ppp*, network sniffing tools,
>>  LAMP, parted, etc.
> 
> Yes.  Some of these might be a higher priority than some of the tasks
> above, so some of this work should proceed in parallel.

Can we specify those ? I'll be more then happy to assist in packaging / reviewing stuff.


>> * Repository setup (apt?).
> 
> As discussed, the choice of repository type in part depends on what
> libraries we end up packaging anyway, such as for LAMP components.
> At this time, all of zypper, apt, and yum are within consideration.
> 
>> These are likely to be mixed during the process.  However there are some
>> rather strong dependencies:
>> 
>> - Kernel update, IPv6, new tools, repository need MUCH space on CD.
> 
> I think IPv6 support doesn't need much extra CD space.  Other things you
> mentioned do.
> 
>> - Kernel update, new tools likely need new gcc as some new software
>>  doesn't compile by our gcc 3.4.5.
> 
> Yes, and also because our and our users' time spent testing stuff is
> made better use of if such testing is applied to builds that are more
> similar to those we'll have in the next release.  Updating gcc and glibc
> early will result in fewer bugs remaining in the release.

I've got working gcc 4.6.1 packages in OWL-3 stable.




	Igmar

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ