From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Enable mount SquashFS
Date: Mon, 21 Jan 2019 21:45:44 +0100 [thread overview]
Message-ID: <20190121214544.5e615f30@gmx.net> (raw)
In-Reply-To: <CAOqJNTfN9Ux1x_q3hXd6utAqtVCasUyx5yA1d2MqvMFg2_bMKg@mail.gmail.com>
Hello ??????,
please keep buildroot at busybox.net in CC....
On Mon, 21 Jan 2019 12:21:55 +0200, ?????? ????? <sergei.sakhno@gmail.com> wrote:
> Thks. I missed this this parametr.
> Can you help me with mount squashfs image in minimal image of linux,
> created in buildroot?
> When i try mount squashfs image as root (mount -t squashfs -o
> ro,loop,sizelimit=14319616 /home/update-last.raucb /run/rauc/bundle), i get
> error:
>
> > mount: /run/rauc/bundle: mount failed: Operation not permitted.
> > Failed mounting bundle: failed to run mount: Child process exited with
> > code 1
> > installing /home/update-last.raucb: Failed mounting bundle: failed to run
> > mount: Child process exited with code 1
> >
> EXT4 partition on real storage device mounted successfully.
Not much info....why mount to /run/rauc/bundle and not just /mnt ? Why option sizelimit?
Where does the 'installing' error message come from? How is the squashfs image update-last.raucb
created (never worked with rauc (yet))? Loop mounting enabled in the kernel?
Do you run your commands as root user? Which are the file permissions of the squashfs image file?
Regards,
Peter
>
>
> ??, 18 ???. 2019 ?. ? 21:32, Peter Seiderer <ps.report@gmx.net>:
>
> > Hello ??????,
> >
> > On Fri, 18 Jan 2019 20:27:41 +0200, ?????? ????? <sergei.sakhno@gmail.com>
> > wrote:
> >
> > > Good evening everyone. How to enable the ability to mount SquashFS? In
> > the
> > > menuconfig of busybox downloaded from the busybox site there is an item
> > > [SquashFS filesystem] in the [Filesystem / Volume identification]
> > section,
> > > but in the menuconfig of busybox unpacked buildroot it is not.
> >
> > Busybox CONFIG_FEATURE_VOLUMEID_SQUASHFS depends on VOLUMEID &&
> > FEATURE_BLKID_TYPE,
> > VOLUMEID is already enabled, FEATURE_BLKID_TYPE is Linux System Utilities
> > -->
> > blkid --> Print Filesystem type
> >
> > More important is enabled squashfs support in the linux kernel...
> >
> > Regards,
> > Peter
> >
> >
next prev parent reply other threads:[~2019-01-21 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 18:27 [Buildroot] Enable mount SquashFS Сергей Сахно
2019-01-18 19:32 ` Peter Seiderer
[not found] ` <CAOqJNTfN9Ux1x_q3hXd6utAqtVCasUyx5yA1d2MqvMFg2_bMKg@mail.gmail.com>
2019-01-21 20:45 ` Peter Seiderer [this message]
[not found] ` <CAOqJNTd10twL7LOeVpJn2Q8XLLALxYT-zr7hoH_oC4uYP2enwQ@mail.gmail.com>
2019-01-22 18:19 ` Peter Seiderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190121214544.5e615f30@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox