freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
p misc/151696  embedded   [nanobsd] [patch] nanobsd.sh doesn't run "make_conf_bu
o misc/151695  embedded   [nanobsd] [patch] Enhance tools/nanobsd/fill_pkg.sh
o misc/136889  embedded   [nanobsd] [patch] nanobsd error reporting and other re
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c

5 problems total.

alix1d video driver support

Hi people, first and foremost apologize me for my bad English.

I'm thinking in adquire an alix board, specifically this board:

http://www.pcengines.ch/alix1d.htm

that board has an LX Geode processor, and  I would like to know if
anyone has ever installed Xorg in it. and if the experience has had
succefully

Has anyone installed and used a graphical environment on the alix
board that I'm mentioning?

Thanks a lot.

freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
p misc/151696  embedded   [nanobsd] [patch] nanobsd.sh doesn't run "make_conf_bu
o misc/151695  embedded   [nanobsd] [patch] Enhance tools/nanobsd/fill_pkg.sh
o misc/136889  embedded   [nanobsd] [patch] nanobsd error reporting and other re
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c

5 problems total.

freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
p misc/151696  embedded   [nanobsd] [patch] nanobsd.sh doesn't run "make_conf_bu
o misc/151695  embedded   [nanobsd] [patch] Enhance tools/nanobsd/fill_pkg.sh
o misc/136889  embedded   [nanobsd] [patch] nanobsd error reporting and other re
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c

5 problems total.

GEOM_LZMA

Hi,

I`m happy to introduce GEOM_ULZMA module and utilitie to create an ulzma image.

Think now it in acceptable for testing/reviewing/committing state.

Wait for your questions. :)

Add xz-embedded to contrib:
http://my.ddteam.net/files/add_contrib_xz-embedded.patch
Add geom/ulzma/g_ulzma.c and usr.bin/mkulzma:
http://my.ddteam.net/files/geom_ulzma_and_mkulzma.patch

WBW
--

-- 
Alexandr Rybalko <ray@...> 
aka Alex RAY <ray@...>

Hi,

I`m happy to introduce GEOM_ULZMA module and utilitie to create an ulzma image.

Think now it in acceptable for testing/reviewing/committing state.

Wait for your questions. :)

Add xz-embedded to contrib:

Re: GEOM_LZMA

On 19 January 2011 18:54, Alexandr Rybalko <ray@...> wrote:
> Hi,
>
> I`m happy to introduce GEOM_ULZMA module and utilitie to create an ulzma image.
>
> Think now it in acceptable for testing/reviewing/committing state.
>
> Wait for your questions. :)

I like it. I'd like to see the ulzma and gz stuff unified in a later
pass of this code but personally I'm happy to have it committed as-is
so it immediately gets some wider exposure.

Adrian

Re: GEOM_LZMA

On Thu, 20 Jan 2011 09:49:55 +0100
Pawel Jakub Dawidek <pjd@...> wrote:

>> On Thu, Jan 20, 2011 at 12:31:03PM +0800, Adrian Chadd wrote:
>> > On 19 January 2011 18:54, Alexandr Rybalko <ray@...> wrote:
>> > > Hi,
>> > >
>> > > I`m happy to introduce GEOM_ULZMA module and utilitie to create an ulzma image.
>> > >
>> > > Think now it in acceptable for testing/reviewing/committing state.
>> > >
>> > > Wait for your questions. :)
>> > 
>> > I like it. I'd like to see the ulzma and gz stuff unified in a later
>> > pass of this code but personally I'm happy to have it committed as-is
>> > so it immediately gets some wider exposure.
>> 
>> IMHO it should first be unified, really. Once it is committed the
>> chances are much lower that it will be unified.
>> 
>> Alexandr, would you like to implement some more general geom_compress
>> class or something like that where it is easier to add new algorithms?
>> You can look at geom_label, which is more or less implemented that way.

It`s possible, but I think primary usage for it is a embedded, so we need smallest one and only one.
Now in my boxes I use only geom_ulzma.

Only one thing make Adrian idea as wished: gzip already in kernel for other things.
But if world produce new compressor fines than xz/lzma we must drop lzma and use new one.

Re: GEOM_LZMA

On Thu, Jan 20, 2011 at 12:26:44PM +0200, Alexandr Rybalko wrote:
> On Thu, 20 Jan 2011 09:49:55 +0100
> Pawel Jakub Dawidek <pjd@...> wrote:
> >> IMHO it should first be unified, really. Once it is committed the
> >> chances are much lower that it will be unified.
> >> 
> >> Alexandr, would you like to implement some more general geom_compress
> >> class or something like that where it is easier to add new algorithms?
> >> You can look at geom_label, which is more or less implemented that way.
> 
> It`s possible, but I think primary usage for it is a embedded, so we need smallest one and only one.
> Now in my boxes I use only geom_ulzma.
> 
> Only one thing make Adrian idea as wished: gzip already in kernel for other things.
> But if world produce new compressor fines than xz/lzma we must drop lzma and use new one.

Well, world is not that simple, I think:) Some algorithms are faster at
decompressing, some compress better, so use less resources to
decompress, etc. FreeBSD provides tools, not policies, right? Let's the
administrator choose which algorithm fits best his needs.

As for the code size, it should be trivial to decide which algorithms we
want to compile in.

--

-- 
Pawel Jakub Dawidek                       http://www.wheelsystems.com
pjd@...                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!

Re: GEOM_LZMA

Well, creating a generic geom_compress module shouldn't increase the
size by all that much. It's just a few function pointers that point at
the decompression class. The rest of the format is the same, right?
(ie, how it's broken into chunks, the chunks are separately
compressed, etc.)

This is great work by the way. :)

Adrian

Re: GEOM_LZMA

On Fri, 21 Jan 2011 15:09:16 +0100
Ivan Voras <ivoras@...> wrote:

>> On 21/01/2011 14:46, Alexandr Rybalko wrote:
>> 
>> > But really, gzip in most cases already compiled into kernel (my not) and anyway have small footprint.
>> >
>> > So I done join GEOM_UZIP + GEOM_ULZMA module, called GEOM_ULZMA yet.
>> >
>> > Module name open for discussion :)
>> 
>> Is "uzip" some kind of well-known or special name? Because since it 
>> doesn't reference the algorithm but only a generic term "zip", maybe 
>> it's better that the name remains geom_uzip? Except if it is 
>> incompatible with the old geom_uzip.

Yep, they are compatible with geom_uzip. But they have also ulzma and can include something else, so better
to have more generic
name.

>> 
>> 
>> _______________________________________________
>> freebsd-geom@... mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-geom
>> To unsubscribe, send any mail to "freebsd-geom-unsubscribe@..."

--

-- 
Alexandr Rybalko <ray@...> 
aka Alex RAY <ray@...>