Comments (13)
Thanks for your contribution ;). This is what I hoped to see from the start. I
will apply them ASAP.
Original comment by [email protected]
on 24 Feb 2011 at 11:27
from firmware-mod-kit.
Ok, I admit to being a fiddler. I couldn't leave well enough alone.
I modified it to allow for a "rebuild number" that automatically increments.
This is both sets of patches against the distribution version.
Original comment by [email protected]
on 25 Feb 2011 at 12:51
Attachments:
from firmware-mod-kit.
I should say, there's a couple of shell'isms used which may be less than
perfectly portable but I think they're solid.
Original comment by [email protected]
on 25 Feb 2011 at 12:52
from firmware-mod-kit.
Booboo'd on doing the md5sums.
Single line fix.
Original comment by [email protected]
on 25 Feb 2011 at 1:02
Attachments:
from firmware-mod-kit.
Thanks again, I'll try to go ahead and commit these during today's work session.
Original comment by [email protected]
on 25 Feb 2011 at 1:37
from firmware-mod-kit.
It occurred to me, why not just give you commit access.. That is easier for
everyone. So, I've done so. Just check back out the project using the
credentials Google supplies and you can commit whatever changes you like. You
are clearly a trustworthy and competent developer.
Original comment by [email protected]
on 25 Feb 2011 at 1:57
from firmware-mod-kit.
And as the firmware mod kit version changes, perhaps we can host that
elsewhere, or I can be responsible for updating it on my server. If it can be
publicly exposed on Google Code, then we should use that route.
Original comment by [email protected]
on 25 Feb 2011 at 2:05
from firmware-mod-kit.
Ok, changes checked in.
I did it in two separate actions to allow them to be separated if needed.
Original comment by [email protected]
on 25 Feb 2011 at 2:59
- Changed state: Fixed
from firmware-mod-kit.
Re: #7, I don't think I understand. Isn't this (GoogleCode) a good place for it?
Original comment by [email protected]
on 25 Feb 2011 at 3:25
from firmware-mod-kit.
Yes, it is - and exactly what I was saying. I just made the change so that it
checks the browsed Google code site, using the 'raw file' link. As long as this
doesn't change, no more of me having to put the TXT file on my web server (and
messing it up half the time ;p).
Done as of r174. r173 was bad because I used the non-raw URL, which would have
required more parsing.
Thanks again for your contributions ;). If I can do anything, let me know. I am
normally busy with my business at Bitsum Technologies, but if you need elevated
rights or credits (please feel free to add credits for yourself) anywhere, just
let me know.
Thanks ;)
Original comment by [email protected]
on 25 Feb 2011 at 3:40
from firmware-mod-kit.
One quick question, do you remember if there's any conflicts between the
shared.inc file and the ipkg_* scripts? (I know that they don't use the
shared.inc file but I want them to.) (I'll also open a separate ticket for it
when I get ready to do it.)
Original comment by [email protected]
on 25 Feb 2011 at 3:45
from firmware-mod-kit.
No conflicts I know of. I do not remember the rationale for not including it in
those scripts. It may have been a simple lack of necessity at the time.
Original comment by [email protected]
on 25 Feb 2011 at 3:49
from firmware-mod-kit.
Original comment by [email protected]
on 28 Feb 2011 at 1:16
- Added labels: Usability
from firmware-mod-kit.
Related Issues (20)
- mkcramfs-lzma
- Checksums don't match after build
- Fails to compile on Arch x64
- can we extract this firmware file
- extract openwrt ERR No supported file system found!
- Autoconf not listed in prerequisites guide
- Tenda N300 firmware binary - no supported filesystem found.
- Python 2 dependencies HOT 1
- unable to build jffs2 filesystem ... HOT 3
- Add support for UBI filesystems? (Linksys WRT32X)
- Unable to build Zlib HOT 1
- extract-firmware.sh DVRF_v03.bin Tools build failed! Check pre-requisites. Quitting... HOT 2
- Release a new version?
- Extraction error also compliance HOT 3
- Unsupported file system 'mpfs'! Quitting...
- "No supported filesystem found" with Trendnet THA-101 firmware HOT 1
- squashfs-4.0-realtek
- add support for hg630v2
- Installation HOT 1
- Firmware version incorrect after modification
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from firmware-mod-kit.