-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvement #16
base: master
Are you sure you want to change the base?
Improvement #16
Conversation
The fdisk part of your modifications is failing
|
Hi,When did you check that?I have found a small typo error which has been fixed.I have checked several time and have used it an hour before.All are ok. Try again and you should be alright.This way is much easier and quicker.Let me know the result...
The fdisk part of your modifications is failingWelcome to fdisk (util-linux 2.25.2). Device does not contain a recognized partition table. Command (m for help): Partition type Command (m for help): Selected partition 1 Command (m for help): Partition type Command (m for help): Partition number (1,2, default 2): Command (m for help): The partition table has been altered. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8). |
However, the message is right as the size change will be effected in next reboot. just clone the git, make the image, boot with SD and all should be ok... (tested couple of times) |
Hi,
I have added few line of codes to improve the image creation process.
You do not need to fix the size of SD. Mine will calculate the rootfs size with minimum required free space (ext4 partition size) and add to bootsize (vfat partition size) and make the image size with combination of these two.
Also have control to change these values if required.
have used kpartx to use mapper instead of two losetup. Makes it easier...
cheers,
Saeid Ghazagh