MD5 Checksum: 76705b8eff53bace85a0b79d6e1b44dcĠ 0x0 DLOB firmware header, boot partition: "dev=/dev/mtdblock/2"ġ12 0x70 LZMA compressed data, properties: 0x5D, dictionary size: 33554432 bytes, uncompressed size: 4237652 bytesġ441904 0x160070 PackImg section delimiter tag, little endian size: 2121216 bytes big endian size: 6168576 bytesġ441936 0x160090 Squashfs filesystem, little endian, version 4.0, compression:lzma, size: 6164554 bytes, 2205 inodes, blocksize: 262144 bytes, created: 07:05:15 When I use binwalk to extract the firmware directly: $ binwalk -Me DIR-645_FIRMWARE_1.04.B11.ZIP These are all things that a package management tool does (as well as making sure dependencies are met etc.I download firmware of D’link DIR-645 from here ![]() To not use a binary package means that you will have to keep track of where all the files are installed yourself, tar them up somehow and then hope that untarring that tar file won't overwrite things at the destination. Here's a HOWTO for dpkg, and here's another that the Rasbian people link to from their own pages. If it isn't available, or you just don't want to contact the maintainer, you could consider building a package with whatever package managing system Rasbian uses (seems to be Debian packages).If it is available, but the version is too old, then I would contact the package maintainer about an update.If it is available, that would be your first port of call.I'm not a Rasbian user and I don't know if netatalk is available as a package for the system (checking. This is why packaging tools like yum, dpkg and rpm exists. make a note of the libraries you need to install separately to get everything working.on each Raspberry Pi, run make install.copy the tarball to the other Raspberry Pis.If checkinstall doesn't work, there's always the pre-built tarball approach: deb should have the appropriate dependencies. That way you know that the required libraries are already installed, and the resulting. Install it again using checkinstall: checkinstall -D make install There's a simpler variant if the netatalk Makefile has a working uninstall target: in that case, on the first Raspberry Pi, packages (not -dev!) are installed on the second one. ![]() I'm not sure how well this will work if any of the required libraries are missing, so you may want to run ldd on the binaries on your first Raspberry Pi beforehand, and make sure that the corresponding lib. deb package to other Raspberry Pi systems. This last step will install the binaries copied across in the pre-built source from your first Raspberry Pi (which shouldn't require any -dev package), and build a. Install the binaries using checkinstall checkinstall -D make install on that other Raspberry Pi, install checkinstall and extract the tarball.copy the tarball to another Raspberry Pi.tar up the source (and binaries built in the source tree).Now that you've installed your locally-built version of netatalk, I would recommend the following approach (I'm assuming you extracted netatalk to a directory called netatalk-3.1.8, and built and installed it from there): ![]() Kusalananda's answer is the better approach generally but in netatalk's case, upgrading the package to a newer version seems rather complex (at least, in the context of a distribution).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |