Deploying LL with customized install disk

[paul1149]

I have installed LL on three units in the past few weeks. Each time it gets a little easier as I learn the ropes.

But is it possible to compile a custom installation disk with the common programs, addons and settings that I want to place on each machine? For instance, I want WINE and a couple of Windows programs, I want the expanded gnome theme collection, a video editor, the slimjet browser, etc.

[torreydale]

Yes!

You can use Systemback.  It's been discussed in this feed:
https://www.freecinema2022.gq/forums/sugge...timeshift/

You can create your own Live Media using the tool.  I've had the same thoughts as you.  I've created 32bit and 64bit installs of Linux Lite in Virtualbox.  I've made the adjustments to the installs that I want to provide for people in my sphere of influence, and then I created Live System images of each install using the Systemback tool. 

The next user I convert to Linux Lite will be easier.  I just boot to the Live System image I created, open Systemback, follow the prompts, reboot, and then I'm done.  I can run updates at that point for added measure, but the customization has already been done in advance.

[paul1149]

Wow, I hadn't understood the installation capability of the SystemBack Live function. If that means an adaptive install to dissimilar hardware is possible, we are talking one powerful piece of software indeed. Has anyone used SB in this way?

Thanks, torreydale. This looks like the perfect solution.

[torreydale]

@paul1149,

I plan on using it on dissimilar hardware.  That's the beauty of Linux and Live CDs/Media.  We don't have to keep up with individual drivers or develop a golden image for each model of hardware.  I've made two images in VirtualBox.  One for 32bit Linux Lite, and one for 64bit Linux Lite. 

I had someone approach me today about a Libre Office concern.  They apparently saved a file in the default format *.odf.  When they shared it with their spouse, the spouse couldn't open that format on their cell phone.  I showed the guy who approached me how to use the Libre Office Save As option and choose the Microsoft Office format for his document.  Later tonight, I'll adjust my Systemback images to use the MS Office extensions as the default Save As options as for Libre Office.  I'll rerun the System Image option of Systemback, and then my two images (that I created in VirtualBox) will be updated with this new feature.  The next person I migrate to Linux Lite will get the benefit of this concern brought up by the guy who approached me today. 

I think the Libre Office settings I'm planning should hold in the System Image.  I like the smaller toolbar icons of Libre Office.  Those held over in the image, so this should, too.

[paul1149]

Using a VM to create the image is a great idea. Thanks again, torreydale!

[torreydale]

@paul1149,

By the way, if you're going to use VirtualBox, they had an update to version 5.0 this month.  According to the release, this update should make the drag and drop features work better.  I didn't notice that over the weekend.  But reading the documentation today, it appears I need to update the VirtualBox Guest Additions for drag and drop to work as planned with the new version 5.0 of VirtualBox.  I'll try that later tonight.

My time wasn't totally wasted, though.  In my difficulty trying to get drag and drop to work properly, I got really good at creating shared folders.


P.S.  Using a VM to create the images is a good idea.  But testing the Systemback image with a VM wasn't successful for me over the weekend.  I had to boot to the image using real hardware.  When I tried booting to the Systemback image in Virtualbox, I got to the Linux Lite splash screen and then the display just went black.  This happened on my 32bit and 64bit images.

I may try booting to them using VMware Player for Linux to make sure it wasn't just a VirtualBox fluke.  Then again, maybe after I update Virtualbox guest additions on my images, they'll boot up in Virtualbox.

Lastly, when creating the image using a VM, make sure to give your virtual hard disk enough space to hold the *.sblive and the *.iso files that Systemback creates.  I didn't do this, but again, I learned to get good at virtual hard disk expansion and partition resizing as a result.  To save you the trouble, I would say to give your virtual hard disk the capacity to dynamically grow to no less than 15-20GB.  The default in VirtualBox is only 8GB.

[paul1149]

Thanks for the tips. I have had poor results with Virtual Box and eventually gave up on it. VMWare Player has worked much better for me. I'll keep your other suggestions in mind.

[torreydale]

@paul1149,

I was able to get my Systemback VM images to boot into both Virtualbox and VMware Player.  The thing I had to do was turn off Hardware Virtualization in the settings of the VM in both Virtualbox and VMware Player.  I also turned off the USB Controller in VMware Player.  It seems Systemback doesn't want your VM to be able to create VMs, so you have to disable those features in each tool.

For the record, in Virtualbox, that would mean going into the System category and the Acceleration tab to disable Hardware Virtualization (uncheck "Enable Vt-x/AMD-V"). 

In VMware Player, that means going to the Processors category and unchecking those Virtualization Engine items, and then going into the USB Controller category and disabling USB input devices.


P.S.  You might also have to turn off any 3D Acceleration in Virtualbox and VMware Player if the above doesn't work.

[paul1149]

Ok, thanks. I took an image of the most recent install, so I can test this out when I get a chance. Thanks again.