Eric
I read some of the other posts, these are interesting times for the LEAF community.
Having a structured approach for new Bering (glibc or uClibc) releases sounds very
appealing.
It will be interesting to see how such a project will evolve from a management
position.
At 23:47 19.12.2003
PROTECTED]
Sent: Thursday, December 18, 2003 11:24 AM
Subject: Re: [leaf-devel] Bering Crew looks for expansion
Eric
At 23:31 17.12.2003 +0100, Eric Wolzak wrote:
Hello everybody,
As you might know , Jacques has stopped, and gave the rudder to me.
My plans with Bering are.
1. update kernel
On Fri, 2003-12-19 at 11:42, Etienne Charlier wrote:
Now a survey ???
What would be the advantage and drawbacks of merging the Bering
Bering-uclibc distributions ?
What would be the advantage and drawbacks of keeping the Bering
Bering-uclibc distributions separate ?
IMHO, I think
Hi Etienne
I don't consider myself a guru, but being a member of the Bering
uClibc team, I feel like I can voice my opinion nevertheless.
Now a survey ???
What would be the advantage and drawbacks of merging the Bering
Bering-uclibc distributions ?
Advantages would obviously be
Hi Mike,
Now a survey ???
What would be the advantage and drawbacks of merging the Bering
Bering-uclibc distributions ?
What would be the advantage and drawbacks of keeping the Bering
Bering-uclibc distributions separate ?
IMHO, I think that we don't need 2 separate variantes of bering.
Martin Hejl wrote:
What would be the advantage and drawbacks of keeping the Bering
Bering-uclibc distributions separate ?
The obvious, I guess - never touch a running system. People who have a
working Bering system would not have to worry about some new version. I
can surely understand that
Hi Charles,
What about the possability of moving forward with a mixed approach for
the next major version?
The core system (and most packages) could be compiled against uClibc,
while packages that require it are compiled against a newer glibc that
would optionally be installed by those with
On Fri, 2003-12-19 at 13:20, Martin Hejl wrote:
The main difference I see between the Bering branches is the target
audience. The uClibc team is targeting enterprise use, while the Bering
team is targeting SOHO/end users.
I'm curious - what makes you think so? My day work is targeting
Hi Mike,
I'm curious - what makes you think so? My day work is targeting
enterprise use (so, I think I know what they'd ask for, but then,
different customers ask for different things, so one can't be sure), and
with Bering uClibc, I don't see any of the buzz-words that would make
it in the
Hello All,
After my first mail, there were a few support offerings, that I am very
gratefull too.
in two of them the question came why not combine efforts.
Yesterday, I discussed this topic with Mike also ( chat).
I told him, i will think a few days about the future of bering.
interesting is
Hi Eric,
The conclusions I came up to so far are.
1. getting the route towards the bering-uclibc team, as I think that is where the
future lies. 2. Kernel development can be done together. (2.4.23 , and later 2.6.0)
3. The solution I think Charles also suggested. using uclibc for the core.
For
On Wed, 17 Dec 2003, Eric Wolzak wrote:
Date: Wed, 17 Dec 2003 23:31:40 +0100
From: Eric Wolzak [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: [leaf-devel] Bering Crew looks for expansion
Hello everybody,
As you might know , Jacques has stopped, and gave the rudder
Eric
At 23:31 17.12.2003 +0100, Eric Wolzak wrote:
Hello everybody,
As you might know , Jacques has stopped, and gave the rudder to me.
My plans with Bering are.
1. update kernel to 2.4.23.
2. update packages
3 revise the documentation and make some improvements.
4 create a basic webinterface.
13 matches
Mail list logo
