d22cd3b...
by
Artem Bityutskiy <email address hidden>
liveusb: fix vfat UUID
Commit '3577b518715c29175c5f517c6f3cf7a70b0e3d39' fixed the UUID string for
raw images, but broke it for liveusb images. And this patch fixes the issue by
making the liveusb code stop adding a dash to the UUID, because now the dash is
there, just like in UUID of ext4.
This command will be used in the KS file and it will specify the list legacy
MIC features which have to be disabled. Instead of these feature, the general
installer framework infrastructure mechanisms will be used.
The first option will be "extlinux" which will disable the legacy extlinux
installation feature. At some point, installerfw=all will be supported,
it will disable all the legacy features (for keyboard, fstab, users, etc).
Along with the option, introduce a helper function which checks if a the
installer framework has to be used for a feature. Usage example:
if use_installerfw(ks, "extlinux"):
# do not execute MIC's built-in extlinux installation code
else:
# the compatibility legacy mode
original written by Artem
Artem: added the use_installerfw() function.
7bad061...
by
Artem Bityutskiy <email address hidden>
raw: support the 'fstab' installerfw attribute
Similarly to the 'extlinux' attribute of the 'installerfw' KS command, start
supporitng the 'fstab' attribute. This means, for example, if the KS file has
this command:
installerfw "extlinux,fstab"
then MIC will not install/configure extlinux, and it will not generate
/etc/fstab. Instead, installer framework scripts will do that.
I've added the support only to raw images, since installerfw "extlinux" is
allso supported only by raw images. The liveusb support can be added later. I
do not do this because I cannot test liveusb images at this point, so I am
afraid of breaking it.
4e9ae26...
by
Artem Bityutskiy <email address hidden>
baseimager: export partition device node
Also export the device node name for each partition. This will be helpful when
we start generating fstab entries in the installer framework scripts.
In MIC environment, the device node name is easily constructed from the disk
name. The disk name compes from the KS file from the --ondisk option of the
'part' command. And --ondisk is a mandatory argument.
In other installer environments, the disk names may be very different.
6b1b14e...
by
Artem Bityutskiy <email address hidden>
VfatDiskMount: fix vfat UUID string
The right format for the UUID string for vfat in Linux is 'XXXX-XXXX'. This is
how it can be used in fstab, for example (UUID='XXXX-XXXX'). Also, Linux udev
creates /dev/disk/by-uuid/XXXX-XXXX entries for vfat volumes.
The problem in VfatDiskMount is that it provides it in the 'XXXXXXXX' form
(without dash). However, mkfs.vfat does not like the dash, and this is why we
did not have it, I guess.
This patch fixes the situation and makes VfatDiskMount class expose UUID in a
fstab-friendly format. This makes --fstab-entry=uuid option also work for VFAT
volumes (I tested this).
