FESCO ticket#270 - preupgrade and F-12
Greetings folks, After careful review by Will Woods around recently discovered problems related to preupgrading to Fedora 12, I've filed ticket#270 (https://fedorahosted.org/fesco/ticket/270) for discussion at the next FESCO meeting. Please take a moment to read the details in the ticket. The high-level summary from Will ... preupgrade to F12 is basically not going to work for anyone without significant manual workarounds, due to insufficient disk space on /boot. I think we may need to talk to hughsie and/or the desktop team about removing the preupgrade integration in PackageKit for F10/F11 and how to do preupgrade right for F13 and higher. Most of the folks impacted by this proposal are already informed. However, as per the FESCO meeting guidelines [1], I'm sending this to fedora-devel-list for wider discussion. Thanks, James [1] https://fedoraproject.org/wiki/Development/Schedule/MeetingGuidelines#Meeting_shall_be_quick signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 2009-11-12 at 14:56 -0500, James Laska wrote: > Greetings folks, > > After careful review by Will Woods around recently discovered problems > related to preupgrading to Fedora 12, I've filed ticket#270 > (https://fedorahosted.org/fesco/ticket/270) for discussion at the next > FESCO meeting. Please take a moment to read the details in the ticket. > > The high-level summary from Will ... > > preupgrade to F12 is basically not going to work for anyone > without significant manual workarounds, due to insufficient disk > space on /boot. How much disk space will one require on /boot to perform the update without work arounds ? Can gparted resize /boot ? Thanks -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 12.11.2009 20:56, schrieb James Laska: > > preupgrade to F12 is basically not going to work for anyone without > significant manual workarounds, due to insufficient disk space on > /boot. I think we may need to talk to hughsie and/or the desktop > team about removing the preupgrade integration in PackageKit for > F10/F11 and how to do preupgrade right for F13 and higher. My last experience with preupgrade was, that I have go an error message because there was not enaugh space on the /boot partition to download a special image. But after rebooting I was able to download this image from a mirror server before my system starts the upgrade process. Best Regards: Jochen Schmitt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iJwEAQECAAYFAkr8aZEACgkQZLAIBz9lVu9edwQAlmTNnElmOCJDHBNxWu8uXuoi 7vuvyJxF+mGGHivNIiKJicpUn0P+aIIp+KglECHZEXW45HUG8Y6QC4L8Il7e1F8+ 4vYpG7FUSH7fCDqA56lXrb8fjv35lZ9ZB4nOo0zyurVR6F/LoZEEqKwTmdcYqOyc SL1KiYEZ1gAwAYMpECo= =Hszt -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
2009/11/12 James Laska : > preupgrade to F12 is basically not going to work for anyone > without significant manual workarounds, due to insufficient disk > space on /boot. I think we may need to talk to hughsie and/or > the desktop team about removing the preupgrade integration in > PackageKit for F10/F11 and how to do preupgrade right for F13 > and higher. Tomorrow I'll push a F11 update disabling the preupgrade functionality. This will give us enough time to fix things, and then we can "flip the switch" with another PK update in a few weeks that re-enables the upgrade functionality. Richard. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 2009-11-12 at 13:00 -0700, Linuxguy123 wrote: > On Thu, 2009-11-12 at 14:56 -0500, James Laska wrote: > > Greetings folks, > > > > After careful review by Will Woods around recently discovered problems > > related to preupgrading to Fedora 12, I've filed ticket#270 > > (https://fedorahosted.org/fesco/ticket/270) for discussion at the next > > FESCO meeting. Please take a moment to read the details in the ticket. > > > > The high-level summary from Will ... > > > > preupgrade to F12 is basically not going to work for anyone > > without significant manual workarounds, due to insufficient disk > > space on /boot. > > How much disk space will one require on /boot to perform the update > without work arounds ? From the ticket (see URL above). Here's the details. The default /boot partition is 200MB, but there's some overhead: Ext3/Ext4 overhead: 7MB Reserved space: 10MB F11 kernel: 8MB (at least - usually 3 kernels = 24MB) GRUB/EFI files: 1MB Total overhead: 26MB So there's 174MB of usable space maximum, and usually 158MB available. preupgrade now requires at least 167MB free space on /boot: F12 installer images: 143MB (8mb larger than F11!) F12 kernel: 18MB (10mb larger than F11!) RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) Total: 167MB (Was 149MB in F11 - no problem!) > Can gparted resize /boot ? There are definitely workarounds available, but none that meet the criteria for preupgrade as an effortless upgrade option. Thanks, James signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
James Laska wrote: > On Thu, 2009-11-12 at 13:00 -0700, Linuxguy123 wrote: >> On Thu, 2009-11-12 at 14:56 -0500, James Laska wrote: >> > Greetings folks, >> > >> > After careful review by Will Woods around recently discovered problems >> > related to preupgrading to Fedora 12, I've filed ticket#270 >> > (https://fedorahosted.org/fesco/ticket/270) for discussion at the next >> > FESCO meeting. Please take a moment to read the details in the ticket. >> > >> > The high-level summary from Will ... >> > >> > preupgrade to F12 is basically not going to work for anyone >> > without significant manual workarounds, due to insufficient >> > disk space on /boot. >> >> How much disk space will one require on /boot to perform the update >> without work arounds ? > > From the ticket (see URL above). > > Here's the details. > The default /boot partition is 200MB, but there's some overhead: > Ext3/Ext4 overhead: 7MB > Reserved space: 10MB > F11 kernel: 8MB (at least - usually 3 kernels = 24MB) > GRUB/EFI files: 1MB > Total overhead: 26MB > > So there's 174MB of usable space maximum, and usually 158MB > available. > > preupgrade now requires at least 167MB free space on /boot: > F12 installer images: 143MB (8mb larger than F11!) > F12 kernel: 18MB (10mb larger than F11!) > RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) > Total: 167MB (Was 149MB in F11 - no problem!) > >> Can gparted resize /boot ? > > There are definitely workarounds available, but none that meet the > criteria for preupgrade as an effortless upgrade option. > > Thanks, > James What if I have already a large /boot? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thursday 12 November 2009 12:10:13 pm James Laska wrote: > *snip* > > So there's 174MB of usable space maximum, and usually 158MB > available. > > preupgrade now requires at least 167MB free space on /boot: > F12 installer images: 143MB (8mb larger than F11!) > F12 kernel: 18MB (10mb larger than F11!) > RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) > Total: 167MB (Was 149MB in F11 - no problem!) Is part of the reason the F-12 kernel is so much larger that the debugging switch is still flipped on? Regards, -- Conrad Meyer -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 12 Nov 2009, Neal Becker wrote: James Laska wrote: On Thu, 2009-11-12 at 13:00 -0700, Linuxguy123 wrote: On Thu, 2009-11-12 at 14:56 -0500, James Laska wrote: Greetings folks, After careful review by Will Woods around recently discovered problems related to preupgrading to Fedora 12, I've filed ticket#270 (https://fedorahosted.org/fesco/ticket/270) for discussion at the next FESCO meeting. Please take a moment to read the details in the ticket. The high-level summary from Will ... preupgrade to F12 is basically not going to work for anyone without significant manual workarounds, due to insufficient disk space on /boot. How much disk space will one require on /boot to perform the update without work arounds ? From the ticket (see URL above). Here's the details. The default /boot partition is 200MB, but there's some overhead: Ext3/Ext4 overhead: 7MB Reserved space: 10MB F11 kernel: 8MB (at least - usually 3 kernels = 24MB) GRUB/EFI files: 1MB Total overhead: 26MB So there's 174MB of usable space maximum, and usually 158MB available. preupgrade now requires at least 167MB free space on /boot: F12 installer images: 143MB (8mb larger than F11!) F12 kernel: 18MB (10mb larger than F11!) RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) Total: 167MB (Was 149MB in F11 - no problem!) Can gparted resize /boot ? There are definitely workarounds available, but none that meet the criteria for preupgrade as an effortless upgrade option. Thanks, James What if I have already a large /boot? then just run preupgrade. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 2009-11-12 at 15:25 -0500, Neal Becker wrote: > James Laska wrote: > > > On Thu, 2009-11-12 at 13:00 -0700, Linuxguy123 wrote: > >> On Thu, 2009-11-12 at 14:56 -0500, James Laska wrote: > >> > Greetings folks, > >> > > >> > After careful review by Will Woods around recently discovered problems > >> > related to preupgrading to Fedora 12, I've filed ticket#270 > >> > (https://fedorahosted.org/fesco/ticket/270) for discussion at the next > >> > FESCO meeting. Please take a moment to read the details in the ticket. > >> > > >> > The high-level summary from Will ... > >> > > >> > preupgrade to F12 is basically not going to work for anyone > >> > without significant manual workarounds, due to insufficient > >> > disk space on /boot. > >> > >> How much disk space will one require on /boot to perform the update > >> without work arounds ? > > > > From the ticket (see URL above). > > > > Here's the details. > > The default /boot partition is 200MB, but there's some overhead: > > Ext3/Ext4 overhead: 7MB > > Reserved space: 10MB > > F11 kernel: 8MB (at least - usually 3 kernels = 24MB) > > GRUB/EFI files: 1MB > > Total overhead: 26MB > > > > So there's 174MB of usable space maximum, and usually 158MB > > available. > > > > preupgrade now requires at least 167MB free space on /boot: > > F12 installer images: 143MB (8mb larger than F11!) > > F12 kernel: 18MB (10mb larger than F11!) > > RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) > > Total: 167MB (Was 149MB in F11 - no problem!) > > > >> Can gparted resize /boot ? > > > > There are definitely workarounds available, but none that meet the > > criteria for preupgrade as an effortless upgrade option. > > > > Thanks, > > James > > What if I have already a large /boot? As Seth points out, you are likely okay in this scenario. The concern is for users who have installed using the default partition size for '/boot'. Thanks, James signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 2009-11-12 at 15:10 -0500, James Laska wrote: > On Thu, 2009-11-12 at 13:00 -0700, Linuxguy123 wrote: > > On Thu, 2009-11-12 at 14:56 -0500, James Laska wrote: > > > Greetings folks, > > > > > > After careful review by Will Woods around recently discovered problems > > > related to preupgrading to Fedora 12, I've filed ticket#270 > > > (https://fedorahosted.org/fesco/ticket/270) for discussion at the next > > > FESCO meeting. Please take a moment to read the details in the ticket. > > > > > > The high-level summary from Will ... > > > > > > preupgrade to F12 is basically not going to work for anyone > > > without significant manual workarounds, due to insufficient disk > > > space on /boot. > > > > How much disk space will one require on /boot to perform the update > > without work arounds ? > > From the ticket (see URL above). > > Here's the details. > The default /boot partition is 200MB, but there's some overhead: > Ext3/Ext4 overhead: 7MB > Reserved space: 10MB > F11 kernel: 8MB (at least - usually 3 kernels = 24MB) > GRUB/EFI files: 1MB > Total overhead: 26MB > > So there's 174MB of usable space maximum, and usually 158MB available. > > preupgrade now requires at least 167MB free space on /boot: > F12 installer images: 143MB (8mb larger than F11!) > F12 kernel: 18MB (10mb larger than F11!) > RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) > Total: 167MB (Was 149MB in F11 - no problem!) With all my kernels removed except the current one, I have this: # df -h FilesystemSize Used Avail Use% Mounted on /dev/sda2 143G 89G 47G 66% / /dev/sda1 190M 14M 167M 8% /boot tmpfs 2.0G 88K 2.0G 1% /dev/shm /dev/sdb1 294G 242G 37G 87% /data uname -a Linux localhost.localdomain 2.6.30.9-96.fc11.i686.PAE #1 SMP Tue Nov 3 23:41:33 EST 2009 i686 i686 i386 GNU/Linux -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 2009-11-12 at 12:26 -0800, Conrad Meyer wrote: > Is part of the reason the F-12 kernel is so much larger that the > debugging > switch is still flipped on? That's only true for the older F12 development kernels. The kernels since 2.6.31.5-94 have had debugging turned off. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thursday 12 November 2009 12:43:18 pm Jesse Keating wrote: > On Thu, 2009-11-12 at 12:26 -0800, Conrad Meyer wrote: > > Is part of the reason the F-12 kernel is so much larger that the > > debugging > > switch is still flipped on? > > That's only true for the older F12 development kernels. The kernels > since 2.6.31.5-94 have had debugging turned off. Ok, that's what I was curious about. Thanks for the clarification. -- Conrad Meyer -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
F12 kernel: 18MB (10mb larger than F11!) Is part of the reason the F-12 kernel is so much larger that the debugging switch is still flipped on? F12 initrd (initramfs) is about 15.5MB (x86_64) or 11.3MB (i686). F11 initrd (initramfs) is about 3.5MB (x86_64) or 3.0MB (i686). F12 initramfs has *all* the drivers; F11 has a subset. -- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thursday 12 November 2009, Jesse Keating wrote: > On Thu, 2009-11-12 at 12:26 -0800, Conrad Meyer wrote: > > Is part of the reason the F-12 kernel is so much larger that the > > debugging > > switch is still flipped on? > > That's only true for the older F12 development kernels. The kernels > since 2.6.31.5-94 have had debugging turned off. Are the newer non-debug ones still 10MB larger than the F-11 ones (more than twice the size)? If yes, why is that? Just wondering. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, 2009-11-12 at 23:30 +0200, Ville Skyttä wrote: > Are the newer non-debug ones still 10MB larger than the F-11 ones > (more than > twice the size)? If yes, why is that? Just wondering. > > They are larger, due to using dracut to make the initrds rather than mkinitrd. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
Once upon a time, Linuxguy123 said: > On Thu, 2009-11-12 at 15:10 -0500, James Laska wrote: > > preupgrade now requires at least 167MB free space on /boot: > > F12 installer images: 143MB (8mb larger than F11!) > > F12 kernel: 18MB (10mb larger than F11!) > > RPM/anaconda tmpfiles: >=8MB (measured in stupid tests) > > Total: 167MB (Was 149MB in F11 - no problem!) > > With all my kernels removed except the current one, I have this: > > # df -h > FilesystemSize Used Avail Use% Mounted on > /dev/sda1 190M 14M 167M 8% /boot I just removed all but the running kernel (on a system that was a fresh install of F11) and got a similar result: # rpm -e $(rpm -qf /boot/vmlinuz* | grep -v "kernel-$(uname -r)") # df -h /boot FilesystemSize Used Avail Use% Mounted on /dev/md0 194M 15M 169M 9% /boot That's right at the edge, and could push untested corner cases in anaconda with respect to temp files and such. I don't think increasing /boot just because of preupgrade is a viable solution, as the installer image continues to grow. Is it possible instead to put the installer image (the real problem) somewhere else, like /? Why does it need to be in /boot? -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
- "Chris Adams" wrote: > I don't think increasing /boot just because of preupgrade is a viable > solution, as the installer image continues to grow. Is it possible > instead to put the installer image (the real problem) somewhere else, > like /? Why does it need to be in /boot? Because anaconda's stage1 (initrd) doesn't know how to assemble LVM/mdraid/dmraid/whatever crazy thing your root partition is on. So install.img needs to be on something that stage1 can read. Conveniently, GRUB also requires a non-LVM partition - /boot! So that's the only place we can reliably put it. -w -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
Once upon a time, Will Woods said: > - "Chris Adams" wrote: > > I don't think increasing /boot just because of preupgrade is a viable > > solution, as the installer image continues to grow. Is it possible > > instead to put the installer image (the real problem) somewhere else, > > like /? Why does it need to be in /boot? > > Because anaconda's stage1 (initrd) doesn't know how to assemble > LVM/mdraid/dmraid/whatever crazy thing your root partition is on. > So install.img needs to be on something that stage1 can read. How about using dracut for anaconda's initrd as well? Obviously, not for F12, but maybe for F13? -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On 11/12/2009 10:45 PM, Jesse Keating wrote: > On Thu, 2009-11-12 at 23:30 +0200, Ville Skyttä wrote: >> Are the newer non-debug ones still 10MB larger than the F-11 ones >> (more than >> twice the size)? If yes, why is that? Just wondering. >> >> > > They are larger, due to using dracut to make the initrds rather than > mkinitrd. and do you still think it was worth to switch to dracut from mkinitrd? it's 4-5 times larger! this kind of reason smells comes from microsoft:-( -- Levente "Si vis pacem para bellum!" -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, Nov 12, 2009 at 02:56:42PM -0500, James Laska wrote: > Greetings folks, > > After careful review by Will Woods around recently discovered problems > related to preupgrading to Fedora 12, I've filed ticket#270 > (https://fedorahosted.org/fesco/ticket/270) for discussion at the next > FESCO meeting. Please take a moment to read the details in the ticket. > > The high-level summary from Will ... > > preupgrade to F12 is basically not going to work for anyone > without significant manual workarounds, due to insufficient disk > space on /boot. I think we may need to talk to hughsie and/or > the desktop team about removing the preupgrade integration in > PackageKit for F10/F11 and how to do preupgrade right for F13 > and higher. > > Most of the folks impacted by this proposal are already informed. > However, as per the FESCO meeting guidelines [1], I'm sending this to > fedora-devel-list for wider discussion. > From the ticket and my experiences (I preupgraded a machine with a 100MB /boot last night with no problems) this seems like an exageration. Could you please explain "not going to work for anyone without significant manual workarounds"? -Toshio pgpEkjcEiNL4L.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On 11/13/2009 05:05 AM, Farkas Levente wrote: > On 11/12/2009 10:45 PM, Jesse Keating wrote: >> On Thu, 2009-11-12 at 23:30 +0200, Ville Skyttä wrote: >>> Are the newer non-debug ones still 10MB larger than the F-11 ones >>> (more than >>> twice the size)? If yes, why is that? Just wondering. >>> >>> >> >> They are larger, due to using dracut to make the initrds rather than >> mkinitrd. > > and do you still think it was worth to switch to dracut from mkinitrd? > it's 4-5 times larger! this kind of reason smells comes from microsoft:-( Dracut produces a generic initrd by default instead of something system specific. If you want to reduce that, go to /etc/dracut.conf and enable the hostonly option. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
Sorry for breaking thread: > There are definitely workarounds available, but none that meet the > criteria for preupgrade as an effortless upgrade option. So I'm a bit confused by what is so hard here. preupgrade starts up, finds it can't store stage2, and then tells you that you'll need to have a wired connection to the internet if you want to use it. So you have to download stage2 when you reboot and you have to cart your laptop over to the router to plug it in while it does so... it's not like I'm going to be using it for work while anaconda is running I mean, in order to achieve the same thing without preupgrade, I'd have to get on IRC, ask skvidal for a script to dep solve against F12 and download the packages. Then I'd need to remember where the stage1 initird and kernel live in the download tree, grab them, and drop them in /boot. Then I'd need to modify grub.conf to add an entry for them. And I either have to figure out the magic kernel commandline options to specify where everything lives at or I have to figure out where everything belongs in a repository I build somewhere locally. Ugh. That's a lot of steps and a lot of memorizing that preupgrade encodes for me. The fact that stage2 needs to be (automatically) downloaded after I reboot is a truly trivial thing here. -Toshio pgpDZmYGxH0nw.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
Toshio Kuratomi (a.bad...@gmail.com) said: > > There are definitely workarounds available, but none that meet the > > criteria for preupgrade as an effortless upgrade option. > > So I'm a bit confused by what is so hard here. preupgrade starts up, > finds it can't store stage2, and then tells you that you'll need to have a > wired connection to the internet if you want to use it. So you have to > download stage2 when you reboot and you have to cart your laptop over to the > router to plug it in while it does so... it's not like I'm going to be using > it for work while anaconda is running Basically, the case where it fails is when there's enough space to download stage2, but not enough space left after downloading stage2 to do the upgrade. Bill -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, Nov 12, 2009 at 11:27:28PM -0500, Bill Nottingham wrote: > Toshio Kuratomi (a.bad...@gmail.com) said: > > > There are definitely workarounds available, but none that meet the > > > criteria for preupgrade as an effortless upgrade option. > > > > So I'm a bit confused by what is so hard here. preupgrade starts up, > > finds it can't store stage2, and then tells you that you'll need to have a > > wired connection to the internet if you want to use it. So you have to > > download stage2 when you reboot and you have to cart your laptop over to the > > router to plug it in while it does so... it's not like I'm going to be using > > it for work while anaconda is running > > Basically, the case where it fails is when there's enough space to download > stage2, but not enough space left after downloading stage2 to do the > upgrade. > What happens then? Grub can't copy files over to the /boot partition? Doesn't this just mean that preupgrade's estmate of how much space it needs is too small? -Toshio pgpSkdX4FzrJH.pgp Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
Hi. On Fri, 13 Nov 2009 08:33:32 +0530, Rahul Sundaram wrote: > Dracut produces a generic initrd by default instead of something > system specific. If you want to reduce that, go to /etc/dracut.conf > and enable the hostonly option. Can preupgrade generate an initrd? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Thu, Nov 12, 2009 at 11:27:28PM -0500, Bill Nottingham wrote: > Toshio Kuratomi (a.bad...@gmail.com) said: > > > There are definitely workarounds available, but none that meet the > > > criteria for preupgrade as an effortless upgrade option. > > > > So I'm a bit confused by what is so hard here. preupgrade starts up, > > finds it can't store stage2, and then tells you that you'll need to have a > > wired connection to the internet if you want to use it. So you have to > > download stage2 when you reboot and you have to cart your laptop over to the > > router to plug it in while it does so... it's not like I'm going to be using > > it for work while anaconda is running > > Basically, the case where it fails is when there's enough space to download > stage2, but not enough space left after downloading stage2 to do the > upgrade. > Could we add some support to use a USB key as scratch space for any part of this process? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Fri, 2009-11-13 at 09:35 -0500, Andy Gospodarek wrote: > On Thu, Nov 12, 2009 at 11:27:28PM -0500, Bill Nottingham wrote: > > Toshio Kuratomi (a.bad...@gmail.com) said: > > > > There are definitely workarounds available, but none that meet the > > > > criteria for preupgrade as an effortless upgrade option. > > > > > > So I'm a bit confused by what is so hard here. preupgrade starts up, > > > finds it can't store stage2, and then tells you that you'll need to have a > > > wired connection to the internet if you want to use it. So you have to > > > download stage2 when you reboot and you have to cart your laptop over to > > > the > > > router to plug it in while it does so... it's not like I'm going to be > > > using > > > it for work while anaconda is running > > > > Basically, the case where it fails is when there's enough space to download > > stage2, but not enough space left after downloading stage2 to do the > > upgrade. > > > > Could we add some support to use a USB key as scratch space for any part > of this process? Not a bad idea. Not sure who would add this support and test it before Tuesday. Definitely something to consider as a future enhancement to preupgrade. signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
> On Fri, 2009-11-13 at 09:35 -0500, Andy Gospodarek wrote: > > On Thu, Nov 12, 2009 at 11:27:28PM -0500, Bill Nottingham wrote: > > > Toshio Kuratomi (a badger gmail com) said: > > > > > There are definitely workarounds available, but none that meet the > > > > > criteria for preupgrade as an effortless upgrade option. > > > > > > > > So I'm a bit confused by what is so hard here. preupgrade starts up, > > > > finds it can't store stage2, and then tells you that you'll need to > > > > have a > > > > wired connection to the internet if you want to use it. So you have to > > > > download stage2 when you reboot and you have to cart your laptop over > > > > to the > > > > router to plug it in while it does so... it's not like I'm going to be > > > > using > > > > it for work while anaconda is running > > > > > > Basically, the case where it fails is when there's enough space to > > > download > > > stage2, but not enough space left after downloading stage2 to do the > > > upgrade. > > > > > > > Could we add some support to use a USB key as scratch space for any part > > of this process? > > Not a bad idea. Not sure who would add this support and test it before > Tuesday. Definitely something to consider as a future enhancement to > preupgrade. You could hand edit the stage2= line and point is to any non-lvm partition including a temporary usbkey. You would need to have a filesystem label on the usbkey, and change "Fedora" to be the name of your usbkey in the grub.conf file entry for preupgrade. Just make sure that the install.img resides in /images on the usbkey. You could boot off the boot.iso and pass the needed options to anaconda, appending to the boot line does work with: append initrd=initrd.img stage2=hd:LABEL="Fedora" preupgrade \ repo=hd::/var/cache/yum/preupgrade ks=hd:sda1:/upgrade/ks.cfg Yea, I know ks=hd:sda1 is less that ideal, but if that is the /boot partition unless your playing bios games with the boot order, where else can it be but sda1? This could be added to the boot.iso in a stanza as an option much like rescue. Just some thoughts, Jerry -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCO ticket#270 - preupgrade and F-12
On Mon, 2009-11-16 at 01:33 -0600, Jerry Vonau wrote: > > On Fri, 2009-11-13 at 09:35 -0500, Andy Gospodarek wrote: > > > On Thu, Nov 12, 2009 at 11:27:28PM -0500, Bill Nottingham wrote: > > > > Toshio Kuratomi (a badger gmail com) said: > > > > > > There are definitely workarounds available, but none that meet the > > > > > > criteria for preupgrade as an effortless upgrade option. > > > > > > > > > > So I'm a bit confused by what is so hard here. preupgrade starts up, > > > > > finds it can't store stage2, and then tells you that you'll need to > > > > > have a > > > > > wired connection to the internet if you want to use it. So you have > > > > > to > > > > > download stage2 when you reboot and you have to cart your laptop over > > > > > to the > > > > > router to plug it in while it does so... it's not like I'm going to > > > > > be using > > > > > it for work while anaconda is running > > > > > > > > Basically, the case where it fails is when there's enough space to > > > > download > > > > stage2, but not enough space left after downloading stage2 to do the > > > > upgrade. > > > > > > > > > > Could we add some support to use a USB key as scratch space for any part > > > of this process? > > > > Not a bad idea. Not sure who would add this support and test it before > > Tuesday. Definitely something to consider as a future enhancement to > > preupgrade. > > You could hand edit the stage2= line and point is to any non-lvm partition > including > a temporary usbkey. You would need to have a filesystem label on the usbkey, > and > change "Fedora" to be the name of your usbkey in the grub.conf file entry for > preupgrade. Just make sure that the install.img resides in /images on the > usbkey. > > You could boot off the boot.iso and pass the needed options to anaconda, > appending to the boot line does work with: > > append initrd=initrd.img stage2=hd:LABEL="Fedora" preupgrade \ > repo=hd::/var/cache/yum/preupgrade ks=hd:sda1:/upgrade/ks.cfg > > Yea, I know ks=hd:sda1 is less that ideal, but if that is the /boot > partition unless your playing bios games with the boot order, where else > can it be but sda1? This could be added to the boot.iso in a stanza as an > option much like rescue. > > Just some thoughts, Thanks for the input Jerry. Lot's of good ideas on how to manually work around the issue. The preupgrade target user is typically one who might not be fully comfortable with some of the manual workarounds on the table. Ideally, a preupgrade maintainer will be addressing a method to make this process more smooth for Fedora 13, but for now we're looking to avoid leaving the average user high-and-dry, and documenting suggested workarounds (as you've noted above) in the Common_F12_Bugs page. Thanks, James signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
