write.sh only manage /dev/sdX but not /dev/mmcblk0 about kubernetes-on-arm

[luxas]

Yeah, when you say it, that's how it is.
The script takes the input /dev/sda and appends 1 and 2 for the partitions.
Thanks for observing this.
Which way is best to do it? Ask the user and provide options PART1=p1 PART2=p2 sudo sdcard/... for automating the process. What do you think?

But, how couldn't write.sh be executable by default?
I have to investigate it.

[nsteinmetz]

I was thinking about write.sh being able to manage something like:

In pseudo code:

if $1 starts with "/dev/sdX": then :
    part1= /dev/sdX1
    part2= /dev/sdX2
elif $1 starts with "/dev/mmcblkX"; then :
    part1= /dev/mmcblkXp1
    part2= /dev/mmcblkXp2
else:
    exit()

... do some stuff with part1 and part2.

I don't know if there could be something else than these 2 cases.

[luxas]

It's fully possible.
One could set it like this to handle every case (I don't either know if there are more cases than this):

# Special case
if $1 starts with "/dev/mmcblkX"; then :
    part1= ${1}p1
    part2= ${1}p2
else:
    # General case, /dev/sda, (/dev/hda?)
    part1= ${1}1
    part2= ${1}2

# Question the user about continuing
if $continue is some of (n|N); then
   exit
else: 
   # do stuff

[luxas]

Oh, I didn't know that commits could automatically close issues.
Feel free to comment more if it isn't working in future releases.