OEM Install or Kickstart?

You mean the questions asked by the Ubiquity installer (such as user name, new password, time zone, etc)?

Yes, the things that kickstart would normally answer. Then perhaps a custom shell script at the end.

So you need to modify the boot parameters to tell Ubuntu to load the kickstart file from the customized ISO?

If you place a kickstart file on the customized iso, you could probably always press "ESC" and ~manually~ add the boot parameter pointing to the kickstart file.

However, I suspect what you are asking for is...
1. You boot from the customized ISO.
2. The boot parameter is already on the ISO, so you need not do any manual intervention.
3. The installer starts and automatically reads the kickstart file
4. The installer automatically installs your customized Ubuntu.

If it really does work this way, I'd hate to be the person who accidentally inserts your USB into their computer, turns it on, and walks away for a few minutes!! ;-)

Anyway, I ~think~ your ask is for Cubic to allow you to modify the boot parameters before you repackage your customized ISO. This way you can input the parameter to point to the kickstart file. <-- IS THIS WHAT YOU ARE ASKING FOR???

To accomplish this, we will need a new screen in Cubic, probably after the kernel/package manifest screen, but before the repackage iso page.

Another hurdle is that, since you can not run GUI applications from inside Cubic's chroot environment, you will need to generate and edit the kickstart config file using system-config-kickstart ~outside~ of Cubic, and then drag the ks.cfg file onto Cubic to place it in the correct location. This shouldn't be a show stopper, though.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

REFERENCE: https://help.ubuntu.com/lts/installation-guide/i386/ch04s06.html

"To generate a Kickstart file, install the system-config-kickstart package and run system-config-kickstart. This offers you a graphical user interface to the various options available.

Once you have a Kickstart file, you can edit it if necessary, and place it on a web, FTP, or NFS server, or copy it onto the installer's boot media. Wherever you place the file, you need to pass a parameter to the installer at boot time to tell it to use the file.

[...]

To place a Kickstart file on a CD, you would need to remaster the ISO image to include your Kickstart file, and add ks=cdrom:/path/to/ks.cfg to the kernel boot parameters. See the manual page for mkisofs for details."

Yes, you nailed it. That's exactly what I want to do.

I don't mind generating the kickstart file else-where.

Thanks

Steve,

Ubuntu based distributions seem to use a "preseed" directory on the ISO with multiple *.seed files inside.
Is this the directory you use?
Do you also use the extension *.seed?

It's possible, I have no experience with it. Thanks

The newest version of Cubic will support preseed files and the ability to edit boot configurations.

Currently a beta version is available in the *Development* branch...

    # Remove Cubic
    # Your Cubic project will not be deleted, so you will not lose your custmizations.
    $ sudo apt autoremove --purge cubic

    # Remove the *Release* repository
    $ sudo apt-add-repository --remove ppa:cubic-wizard/release

    # Add the *Development* repository
    $ sudo add-apt-repository ppa:cubic-wizard/development

    # Install the *Development* version of Cubic
    $ sudo apt update
    $ sudo apt install cubic

I followed the above instructions on Ubuntu 16.04.5 LTS. Cubic shows 2019.03-183

It opens the chroot window and when I click next if seems to error out, disappears.

I see this in the syslog:

Mar 4 08:13:21 spollock-virtual-machine kernel: [2990780.769140] traps: cubic.py[18684] trap int3 ip:7f610ceb0afb sp:7ffe1bce5f70 error:0 in libglib-2.0.so.0.4800.2[7f610ce60000+10f000]

Thanks for testing. I've fixed this issue (reference Bug #1818597).

Please retry with the newer development version 2019.03-184...

$ dpkg -l cubic
# 2019.03-183-development

$ sudo apt update

$ sudo apt install cubic

$ dpkg -l cubic
# 2019.03-184-development

This feature is now available in the Release branch:

    # Remove Cubic
    # Your Cubic project will not be deleted, so you will not lose your customizations.
    $ sudo apt autoremove --purge cubic

    # Remove the *Development* repository
    $ sudo apt-add-repository --remove ppa:cubic-wizard/development

    # Add the *Release* repository
    $ sudo add-apt-repository ppa:cubic-wizard/release

    # Install the *Release* version of Cubic
    $ sudo apt update
    $ sudo apt install cubic

    # Check your version
    $ dpkg -l cubic
    # cubic - 2019.03-47-release

Thank-you!

I'm a bit locked down atm, but will test this soon.

Regards,

-Steve

(415) 320-1102 <https://www.google.com/voice/#phones>

On Tue, Mar 12, 2019 at 5:57 PM Cubic PPA <
<email address hidden>> wrote:

> Your question #678392 on Cubic changed:
> https://answers.launchpad.net/cubic/+question/678392
>
> Cubic PPA posted a new comment:
> This feature is now available in the Release branch:
>
> # Remove Cubic
> # Your Cubic project will not be deleted, so you will not lose your
> customizations.
> $ sudo apt autoremove --purge cubic
>
> # Remove the *Development* repository
> $ sudo apt-add-repository --remove ppa:cubic-wizard/development
>
> # Add the *Release* repository
> $ sudo add-apt-repository ppa:cubic-wizard/release
>
> # Install the *Release* version of Cubic
> $ sudo apt update
> $ sudo apt install cubic
>
> # Check your version
> $ dpkg -l cubic
> # cubic - 2019.03-47-release
>
> --
> You received this question notification because you asked the question.
>

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Thanks! This looks like it will do the trick.