Mick <michaelkintz...@gmail.com> [15-08-01 04:28]:
> On Friday 31 Jul 2015 19:19:06 meino.cra...@gmx.de wrote:
> > Hi,
> > 
> > on my tablet PC I used an Android App called "Linux deploy"
> > to install an chroot-environment for - guess - Gentoo. :)
> > 
> > The tablet has a SDcard slot and recognizes any FAT32 formatted
> > SDcard automatically. Anything else will silently be ignored.
> > 
> > Furthermore Linux deploy uses a single file when it is
> > pointed to an external SDcard (with FAT32) which is mounted
> > via a loop device, formatted ext4, and then populated with
> > the Gentoo Linux files.
> > 
> > So far so nice.
> > 
> > Unfortunately the file size is limited to 4GB, which is not
> > /that/ much in respect to what I want to install later (Linux
> > deploy goes as far as LXDE runs a terminal and only a few moe things).
> > 
> > I created a second file of 4GB and set it up as a "second partition".
> > This is now additional storage capacity of another 4GB.
> > 
> > BUT:
> > Linux deploy already installed a full rootfs and more on the first
> > file. And I need to increase the size of _the whole rootfs_ with this
> > extra file ... not only the storage capacity located behind a certain
> > mountpoint.
> > 
> > Is there any way to add the capacity of the second file in a way, that
> > the whole rootfs participates from/in/at/of (damn! sorry, I am not
> > good with/at/in/of/from propositions) this?
> > 
> > How can I deal with this?
> > 
> > Thank you very much in advance for any help!
> > Best regards,
> > Meino
> 
> Have you tried mounting it with '-o loop' from your chrooted system?  
> However, 
> this won't work unless the chrooted system can see the new partition.
> 
> -- 
> Regards,
> Mick

Hi Mick, 

yes...my question is a result from that. What I did is (the structure
is an example):

This is the root of the current image file, which contains the
chroot environment and is mounted via loop by the android OS:
drwxr-xr-x   2 root root  4096 2015-07-25 04:04 bin
drwxr-xr-x   5 root root  1024 2015-07-25 07:42 boot
drwxr-xr-x   3 root root     0 2015-08-01 04:26 config
drwxr-xr-x  18 root root 15640 2015-08-01 04:26 dev
drwxr-xr-x   2 root root  4096 2015-01-11 16:42 doc
drwxr-xr-x 150 root root 12288 2015-07-31 04:01 etc
drwxr-xr-x   5 root root  4096 2014-01-13 05:21 home
lrwxrwxrwx   1 root root     5 2015-03-24 03:10 lib 
drwx------   2 root root  4096 2014-10-08 17:04 lost+found
drwxr-xr-x   3 root root  4096 2014-05-12 03:56 media
drwxr-xr-x   5 root root  4096 2010-11-05 21:07 mnt
drwxr-xr-x  14 root root  4096 2015-07-24 19:34 opt
dr-xr-xr-x 179 root root     0 2015-08-01 04:26 proc
drwx------  96 root root 12288 2015-08-01 04:56 root
drwxr-xr-x  19 root root   860 2015-08-01 04:28 run
drwxr-xr-x   2 root root 12288 2015-07-28 21:07 sbin
dr-xr-xr-x  12 root root     0 2015-08-01 04:26 sys
drwxrwxrwt  39 root root  4096 2015-08-01 04:58 tmp
drwxr-xr-x  18 root root  4096 2014-09-07 19:09 usr
drwxr-xr-x  14 root root  4096 2015-01-08 08:27 var

This fs is nearly filled up...not much more space available.

So I created a second image file, which currently contains
nothing more than 4GB of free space (YEAH!:)

If I mount this (via loop) to for example to /mnt/
I will get:
drwxr-xr-x   2 root root  4096 2015-07-25 04:04 bin
drwxr-xr-x   5 root root  1024 2015-07-25 07:42 boot
drwxr-xr-x   3 root root     0 2015-08-01 04:26 config
drwxr-xr-x  18 root root 15640 2015-08-01 04:26 dev
drwxr-xr-x   2 root root  4096 2015-01-11 16:42 doc
drwxr-xr-x 150 root root 12288 2015-07-31 04:01 etc
drwxr-xr-x   5 root root  4096 2014-01-13 05:21 home
lrwxrwxrwx   1 root root     5 2015-03-24 03:10 lib 
drwx------   2 root root  4096 2014-10-08 17:04 lost+found
drwxr-xr-x   3 root root  4096 2014-05-12 03:56 media
drwxr-xr-x   5 root root  4096 2010-11-05 21:07 mnt  (behind this there is 4GB 
of additional space)
drwxr-xr-x  14 root root  4096 2015-07-24 19:34 opt
dr-xr-xr-x 179 root root     0 2015-08-01 04:26 proc
drwx------  96 root root 12288 2015-08-01 04:56 root
drwxr-xr-x  19 root root   860 2015-08-01 04:28 run
drwxr-xr-x   2 root root 12288 2015-07-28 21:07 sbin
dr-xr-xr-x  12 root root     0 2015-08-01 04:26 sys
drwxrwxrwt  39 root root  4096 2015-08-01 04:58 tmp
drwxr-xr-x  18 root root  4096 2014-09-07 19:09 usr
drwxr-xr-x  14 root root  4096 2015-01-08 08:27 var

BUT: The space of the filesystem to which for example updates and new programs
will be installed is not increased by a single byte.

I need a soultion which add the 4GB space in a way that 
the current nearly filled filesystem will get more space as a whole.

How can I do that?

Best regards,
Meino









Reply via email to