When using UbinizeImage with ubifs rootfs, ubinize.cfg is no longer
needed. Yet, the absance of ubinize.cfg would make the build process
abort with an error.
Fix that by checking if ubinize.cfg is present and do no not call the
"classic" ubinize image generation if it isn't.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
[missing new-line before UbinizeImage added itentionally]
SVN-Revision: 43788
Removed unused ubi file file from template as ubinized images are
passed directly and not inside the tarball.
Also removed left-over white-space.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
SVN-Revision: 41237
Small journal size can lead to problems if nand flash is too big. By default
ubifs will use ~12% of volume size or a maximum of 8MiB.
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 38799
When creating an image it makes no sense to have files owned by
the uid and gid on the host (and even creates a bug when for
example dropbear authorized_keys is included via env/files).
Signed-off-by: Joris de Vries <joris@apptrician.nl>
SVN-Revision: 38442
The extra commas get output by the shell resulting in errors since
the commands that get called with those extra commas are then
malformed.
Signed-off-by: Joris de Vries <joris@apptrician.nl>
SVN-Revision: 38419
Now it is possible to build ubi/ubifs images for only selected boards inside
single target.
Signed-off-by: Luka Perkov <luka@openwrt.org>
SVN-Revision: 38375
The new root.jffs2-*-raw images can be used for firmware
images with custom padding requirements.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38196
Linux expects that the /dev/console node is present in
the rootfs image. Create the node in rootfs images, in
order to make std{in,out,err} usable even in early init
process.
Note: tar.gz and cpio.gz images are not handled yet.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37847
Due to a typo in the Makefile variable, mkfs.jffs2 is called
without the correct parameters.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37514
Preserve order of components in initramfs image filename
when doing copy from $(KDIR) to $(BIN_DIR).
Patchwork: http://patchwork.openwrt.org/patch/3811/
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37452
Make jffs2_nand a separate option so this can be triggered without forcing
jffs2 images for nor targets.
Adds a new NAND_BLOCKSIZE variable that allows setting the generated layout
in <page_size>:<block_size> pairs.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 36860
xz supports using an architecture specific BCJ filter, use that one to
save us a couple kB while producing squashfs filesystems (mimics the
Linux kernel).
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 35097
All Image/mkfs/... macros call the Image/Build except for
Image/mkfs/targz and Image/mkfs/cpiogz
This patch adds the Image/Build call for Image/mkfs/targz and
Image/mkfs/cpiogz.
Signed-off-by: Maarten Bezemer <m.m.bezemer@utwente.nl>
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 34473
The genext2fs tool will 'reserve' 5% of the image size by default,
apparently by creating a huge lost+found directory. In fact it seemed to
be much more than 5% in practice — I saw an image with 8MiB used, and
recovered about 2MiB of it by deleting the 'empty' lost+found directory:
/dev/loop0 48377 8482 37438 19% /mnt/spare
# rmdir lost+found/
/dev/loop0 48377 6014 39906 14% /mnt/spare
This makes it configurable, but leaves it at the genext2fs default
of 5% for now. It should probably be changed to default to zero, but
that can be a separate patch.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 34408
Currently we call mkfs.jffs2 --squash, which will change
both file permissions and owners.
If we have some file with suid bits, it will clear these bits.
Thus it's enough to just squash file owners, by replacing that
argument to --squash-uids.
Signed-off-by: Jonh Wendell <jonh.wendell@oiwifi.com.br>
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 34397
On the off chance that the root filesystem's /tmp is used directly as a
temporary directory instead of having a tmpfs mounted over it, it should have
the sticky bit set.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 32572