Hi all,<br><br>It's amazing that I've got lots of people helping me to hack the firmware. <br> Especially Stephen has shown me lots of examples and tools to apply to the firmware.<br>We've successfully found that the romfs partition inside the firmware is a zipped ext2 file system.
<br>One of my friend who is a software enginner also helped me to examine the codes in kernel.<br> <br>We've found the following section in physmap.c indicates the romfs part in firmware should not exceed 1,966,080 Bytes.
<br>name: "Initrd",<br> size: 0x1E0000,<br><br>However Stephen and I found that the Romfs (Initrd) which has been successfully extracted from firmware is about 2,939,222 bytes long. After uncompressing the Initrd, it becomes a more than 10M bytes long mountable file.
<br>The file size is too large to be stored in the flash partition as the configuration insides kernel codes. <br> According to the previous discussion in the list, I guess D-link might not release the kernel codes corresponds to DIR-450/451.
<br>I've told this situation to Dlink@US by their website 1 week ago, asking them to check if they've put wrong files on ftp site. But I haven't get any response until today.<br><br>However, I think technical disscussion in detail might not be appeared in legal-lists.
<br>But if people want to discussion about the concepts, events, or any possible action in legal-lists will need technical information as a evidence.<br>So I still reply this mail to both lists.<br> <br><br><div><span class="gmail_quote">
On 9/24/07, <b class="gmail_sendername">Stephen C. Fedder</b> <<a href="mailto:sfedder@hotmail.com">sfedder@hotmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
<div lang="EN-US" link="#0000ff" vlink="#0000ff"><div><p><font size="2" color="#000080" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: #000080">Hi,</span></font></p><p><font size="2" color="#000080" face="Arial">
<span style="font-size: 10pt; font-family: Arial; color: #000080"> </span></font></p><p><font size="2" color="#000080" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: #000080">I am glad to be of help. If you run into any problems let me know.
</span></font></p><p><font size="2" color="#000080" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: #000080"> </span></font></p><p><font size="2" color="#000080" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: #000080">
I'm not always sure that the gpl-violations mailing list is the place to be talking about tools/methods of reversing firmware, so I just sent my observations to you rather than to the list. I am not a regular contributor, but just thought I'd take a look and see if I could give you some direction.
</span></font></p></div></div></blockquote><div><br>[deleted....] </div><br></div><br>