Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Feb 2010 15:01:01 -0800
From:      Tim Kientzle <kientzle@freebsd.org>
To:        Alex RAY <ray@ddteam.net>
Cc:        bf1783@gmail.com, freebsd-hackers@freebsd.org
Subject:   Re: GEOM_ULZMA
Message-ID:  <4B81BB2D.2090009@freebsd.org>
In-Reply-To: <20100222004656.3dd2acfe.ray@ddteam.net>
References:  <d873d5be1002202023w4dfcc8d9o56ec4fe53066f8ca@mail.gmail.com>	<4B80C7E7.1090303@freebsd.org> <20100222004656.3dd2acfe.ray@ddteam.net>

next in thread | previous in thread | raw e-mail | index | archive | help
>> I see no reason to not import the current
>> version [of liblzma and xz] into the FreeBSD base system.  I plan
>> to do so but may not get to it very soon; I
>> certainly would not complain if someone else
>> beat me to it.  ;-)
> 
> Thanks for that info.
> GEOM_ULZMA contain two parts mkulzma and GEOM module.
> libarchive can help for mkulzma utility, but how they can help for GEOM module?
> I need to know, where correct place for lzma code in kernel tree?

I think you mean "liblzma" can help.

I plan to import liblzma into FreeBSD base system as
/usr/lib/liblzma.a and /usr/lib/liblzma.so (that may
change to /lib/liblzma.so), with the headers in
/usr/include/.  I expect xz to end up as /usr/bin/xz.

I'm not familiar enough with kernel development processes
to understand the implications there.

Cheers,

Tim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B81BB2D.2090009>