03-23-2017, 07:12 PM
The Help Manual provides instruction for using dd to 'burn' the Linux Lite ISO to a USB stick. I think, perhaps, that most folks reading this in the manual are already using Linux Lite. But, irregardless, I submit that using UNetbootin to accomplish this is better.
Why?
When UNetbootin is used to burn the ISO, it leaves the USB stick completely writable.
This is very advantageous.
For example, such a stick allows me to not only carry my installer wherever I go, but also carry a large media collection, a bunch of ISOs, VM appliances, and my encrypted personal files, email and bookmarks with me as well! With it, I can not only install an OS on a new computer but also conveniently restore onto it all of my 'baggage'. I use backup scripts to keep this content on the stick updated at regular intervals.
And whenever I want to update the stick with a new version of the OS, I don't have to re-format it. That is because I created on it a few folders into which I copied all of my baggage. So all I have to do is delete everything on the stick EXCEPT those folders. I can then use UNetbootin to burn a newer ISO onto the stick. I've been doing this now for quite some time without problem.
UNetbootin requires that the stick be prepared with standard FAT formatting. But this need be done only once.
The only thing that annoys me about the app is that the post-burn boot menu title is UNetbootin. However, due to the writability, this is easily rectified by editing the third line of syslinux.cfg on the stick to change 'UNetbootin' to something like 'Welcome to Linux Lite 3.2 64bit'. I have a item in my menu that does this for me, but it isn't much trouble to do it manually via leafpad in Thunar.
Consequently, it is not a waste of USB stick real estate to burn an ISO to a very large USB stick.
I have seen nothing about this use case on the Internet. I suggest that it might benefit some Help Manual readers to know about the advantages of UNetbootin used as an alternative to the dd method. And perhaps they should also know that this use case does not provide persistence for the installable OS.
Why?
When UNetbootin is used to burn the ISO, it leaves the USB stick completely writable.
This is very advantageous.
For example, such a stick allows me to not only carry my installer wherever I go, but also carry a large media collection, a bunch of ISOs, VM appliances, and my encrypted personal files, email and bookmarks with me as well! With it, I can not only install an OS on a new computer but also conveniently restore onto it all of my 'baggage'. I use backup scripts to keep this content on the stick updated at regular intervals.
And whenever I want to update the stick with a new version of the OS, I don't have to re-format it. That is because I created on it a few folders into which I copied all of my baggage. So all I have to do is delete everything on the stick EXCEPT those folders. I can then use UNetbootin to burn a newer ISO onto the stick. I've been doing this now for quite some time without problem.
UNetbootin requires that the stick be prepared with standard FAT formatting. But this need be done only once.
The only thing that annoys me about the app is that the post-burn boot menu title is UNetbootin. However, due to the writability, this is easily rectified by editing the third line of syslinux.cfg on the stick to change 'UNetbootin' to something like 'Welcome to Linux Lite 3.2 64bit'. I have a item in my menu that does this for me, but it isn't much trouble to do it manually via leafpad in Thunar.
Consequently, it is not a waste of USB stick real estate to burn an ISO to a very large USB stick.
I have seen nothing about this use case on the Internet. I suggest that it might benefit some Help Manual readers to know about the advantages of UNetbootin used as an alternative to the dd method. And perhaps they should also know that this use case does not provide persistence for the installable OS.
(1) LL5.2 on System76 Gazelle Pro L4P9 (2012) i7-3630QM 2.4 GHz - 8GB - Intel HD 4000 1920x1080
(2) LL5.2 on Dell Latitude E5540 (2015) i5-4310U 2.0 GHz - 8GB - Intel HD 4400 1920x1080
(3) Xubuntu 18.04 on 32bit Acer Aspire 5672 (2006) Core Duo T2300 1.66 GHz - 4GB - ATI Mobility Radeon X1400 1280x800
(4) LL4.6 on HP Compaq 8000 SFF (2009) Core 2 Duo E8400 3.0 GHz - 4GB - Intel 4 Integrated Graphics 1920x1080
(5) LL4.6 on Acer Aspire 5515 (2009) AMD Athlon 2650e 1.6 GHz - 3GB - ATI Radeon Xpress 1200 1280x800
(2) LL5.2 on Dell Latitude E5540 (2015) i5-4310U 2.0 GHz - 8GB - Intel HD 4400 1920x1080
(3) Xubuntu 18.04 on 32bit Acer Aspire 5672 (2006) Core Duo T2300 1.66 GHz - 4GB - ATI Mobility Radeon X1400 1280x800
(4) LL4.6 on HP Compaq 8000 SFF (2009) Core 2 Duo E8400 3.0 GHz - 4GB - Intel 4 Integrated Graphics 1920x1080
(5) LL4.6 on Acer Aspire 5515 (2009) AMD Athlon 2650e 1.6 GHz - 3GB - ATI Radeon Xpress 1200 1280x800