I have built a USB stick with a Live Fedora 19 on it.
I gave it a large overlay to make room for updates.
I booted the stick and did a yum update. (Boy was that slow. I think that the Kingston DT101 G2 stick, combined with the USB 2.0 interface, was the cause.)
If I install from this stick, will the installed system be already updated?
Would I have to go through this process first? https://fedoraproject.org/wiki/LiveOS_image#Merge_overlay_into_new_image
On Mon, Jul 08, 2013 at 12:16:29 -0400, "D. Hugh Redelmeier" hugh@mimosa.com wrote:
I have built a USB stick with a Live Fedora 19 on it.
I gave it a large overlay to make room for updates.
I booted the stick and did a yum update. (Boy was that slow. I think that the Kingston DT101 G2 stick, combined with the USB 2.0 interface, was the cause.)
If I install from this stick, will the installed system be already updated?
The way things currently work the anwser is yes. The file system is essentially copied off the live image for live installs. (Note that updating a kernel on a live image doesn't change the kernel being booted when using the live image.)
| From: Bruno Wolff III bruno@wolff.to
| On Mon, Jul 08, 2013 at 12:16:29 -0400, | "D. Hugh Redelmeier" hugh@mimosa.com wrote:
| >If I install from this stick, will the installed system be already | >updated?
| The way things currently work the anwser is yes. The file system is | essentially copied off the live image for live installs. (Note that updating a | kernel on a live image doesn't change the kernel being booted when using the | live image.)
Great!
Now I've discovered a problem with my Live USB system: yum is now unhappy.
[liveuser@localhost ~]$ sudo yum update Loaded plugins: langpacks, refresh-packagekit fedora/19/x86_64/metalink | 25 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-19&arch=x86_64 error was No repomd file Error: File /var/cache/yum/x86_64/19/fedora/metalink.xml does not exist
I wonder how that happened. It isn't that the overlay is full:
[liveuser@localhost ~]$ sudo msetup status live-osimg-min: 0 16777216 snapshot 4576/4576 32 live-rw: 0 16777216 snapshot 4228920/8386560 16464
I did shut the live system down properly after the update.