Thanks for letting us know. We'll get that fixed.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> Thats a busybox vs util-linux based fdisk. The routines should have
> been set to force use of busybox fdisk. But, it seems there is still at
> least one floating around. Most resize things before doing anything
> else, which is why it has been missed all these years.
Ah!
The bridging kernel modules should have been installed when you
installed WAP mode. What version are you using?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Thats a busybox vs util-linux based fdisk. The routines should have
been set to force use of busybox fdisk. But, it seems there is still at
least one floating around.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Man in a van wrote:
> I think there is a max size of 2gb using this method (unless you go for
> the whole card :))
Oh, I just wanted to go to 100 or 200 MB. Turned out the issue is that
"fdisk -l /dev/mmcblk0" output is different from what "autoresize.sh"
expects. On my installation (RPi3B+,
34250
+---+
|Filename: pcp resize.png |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=34250|
+---+
pputzer wrote:
> Hi,
>
> I just noticed that I don't have any space available of on my SD card,
> despite having previously resized the partition. On following up, I
> noticed that while the "Resize partition" process appears to go through,
> it does not change the partition size for my
Hi,
I just noticed that I don't have any space available of on my SD card,
despite having previously resized the partition. On following up, I
noticed that while the "Resize partition" process appears to go through,
it does not change the partition size for my install (anymore - it has
worked
brctl is certainly not a requirement otherwise it would be part of the
kernel.
Perhaps you can try using "ip":
https://baturin.org/docs/iproute2/#ip-link-add-bridge
This being said I guess you'll have to bridge ethernet early enough so
that it'll get IP configured at boot, and not eth0. Hope
