TP-Link 1043ND - its tme :)

[Nenhum_de_Nos]

On Fri, August 30, 2013 10:12, Luiz Otavio O Souza wrote:
> On 30 August 2013 06:30, Nenhum_de_Nos <matheus at eternamente.info> wrote:
>
>>
>> On Thu, August 29, 2013 20:20, Nenhum_de_Nos wrote:
>> >
>> Populating `/root/work/freebsd/head/src/../mfsroot-tl-wr1043nd_matheus.img'
>> Image `/root/work/freebsd/head/src/../mfsroot-tl-wr1043nd_matheus.img'
>> complete
>> *** Running mkuzip to create a compressed filesystem ..
>> *** Target Done.
>> *** Target              : tplink
>> 3831+2 records in
>> 3831+1 records out
>> 1961523 bytes transferred in 1.025448 secs (1912845 bytes/sec)
>> [mktplinkfw] *** error: rootfs image is too big
>> root at dev:~ #
>>
>> I commented out some AH_DEBUG_ALQ. I imagine it is about ALTQ new
>> implementation. Am I right ?
>>
>
> ALQ stands for asynchronous logging queue. It is used to log all the debug
> information from ath.
>
> See that it is the rootfs that is too big now. DIR825 is using
> geom_uncompress which supports lzma compressed images.
>
> I've two patches one with the changes to TP-WN1043ND kernel and the other
> to change the rootfs compression method.
>
> With these changes i can now create the 1043 image, but it is not tested,
> so be aware...
>
> http://pastebin.com/JY2J8Cen
>
> http://pastebin.com/hSZHYsb7
>
> Luiz

Luiz,

my unit is still using TP-Link software, as I never got to create an image small enough. What is
the worst that could happen ? Can I void it forever ?

any schedule to it being ok to test ? (if it won't ruin it forever, I can test)

can I apply this patch to any svn rev ?

thanks,

matheus

-- 
We will call you Cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style