Create ISO using running ubuntu

abhishek jain ashujain9727 at gmail.com
Wed Dec 14 17:12:36 UTC 2016


Thanks folks for the reply.

Let me add bit more details to my requirement.

I'm configuring ubuntu 14.04.02 as a controller after installing multiple
packages,generating ko's and running multiple scripts which runs some
API's/services onto that system.This all stuff can be performed on ubuntu
14.04.02 only,cannot upgrade to the other version of ubuntu.

I want that the third person (which can anywhere in the world) should not
install the packages I installed above,should not generate ko's I generated
above and use my same ubuntu 14.04.02 above.

Please let me know regarding this.

Thanks
Abhishek Jain



On Dec 14, 2016 19:31, "Ralf Mardorf" <silver.bullet at zoho.com> wrote:

> On Wed, 14 Dec 2016 14:00:16 +0100, Liam Proven wrote:
> >On 14 December 2016 at 13:55, abhishek jain wrote:
> >> Filesystem      Size  Used Avail Use% Mounted on
> >> /dev/sda1       906G   29G  832G   4% /
> >> none            4.0K     0  4.0K   0% /sys/fs/cgroup
> >> udev            5.7G  4.0K  5.7G   1% /dev
> >> tmpfs           1.2G  1.3M  1.2G   1% /run
> >> none            5.0M     0  5.0M   0% /run/lock
> >> none            5.7G   76K  5.7G   1% /run/shm
> >> none            100M   40K  100M   1% /run/user
>
> >Before you copy it, avoid installing any special device drivers for
> >the graphics controller.
>
> Simply keep the original install as is and after copying to another
> machine write a xorg.conf with the vesa driver as a starting point. We
> could help you to do this.
>
> >Keep the partitioning simple and duplicate that on the other machine.
>
> It's impossible to keep it simpler than it already is ;).
>
> >Update /etc/fstab with the new device names.
>
> This is easy to do, we could help you assuming the information usually
> included to fstab shouldn't be al you need to know.
>
> # lsb_release -d; head -4 /etc/fstab
> Description:    Ubuntu 16.04.1 LTS
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
>
>
> >Reinstall GRUB on the new machine and that's it, you should be up and
> >running.
>
> This is also not hard to do, we could help you with this, too.
>
> >But if things like "adjust fstab" and "reinstall grub" sound complex
> >and are not things that you know how to do or how to quickly find out,
> >then this is probably not a task for you, I'm afraid.
>
> IMO it's easy to explain. I just like to recommend to download an Ubuntu
> (flavour) live media release 16.10 for systemd-nspawn usage, to adjust
> the copied install to the new machine. A short explanation for the OP,
> systemd-nspawn allows to run the copied install by the live media and
> to fix things, if needed.
>
> Regards,
> Ralf
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/ubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20161214/7b067fb2/attachment.html>


More information about the ubuntu-users mailing list