Install from ISO file supported

[Sergio Belkin]

Hi Fedora community,

AFAIK fedup only works with DVD iso files not with LiveCD iso files:

I was reading the thread at
http://lists.fedoraproject.org/pipermail/users/2013-January/429113.htmlso...
interesting about it

ISO files are still useful, for example to test in a quicky way on a
Virtual machine, but I don't know you, but I'm sick of burning CDs....

I think that the best and more confortable method to upgrade the OS should
be:

1. Download a LiveCD Fedora.iso (it takes less time than download the DVD
iso file)
2. Launch  fedup --iso Fedora-LiveCD.iso, that make the job of adjusting
GRUB2 i.a.
3. Reboot the system
3. Choose LiveCD entry from GRUB2) Perform the installation as you wish

And forget about of burning optical discs....

Of course this does not cover all cases, for example, you should preserve
the partition where ISO image file is.


What do you think?

Greetings
-- 
--
Sergio Belkin  http://www.sergiobelkin.com
Watch More TV http://sebelk.blogspot.com
LPIC-2 Certified - http://www.lpi.org

[Ray Strode]

Hi,

>  1. Download a LiveCD Fedora.iso (it takes less time than download the
> DVD
>  iso file)
>  2. Launch  fedup --iso Fedora-LiveCD.iso, that make the job of adjusting
>  GRUB2 i.a.
>  3. Reboot the system
>  3. Choose LiveCD entry from GRUB2) Perform the installation as you wish
Unfortunately, the way the livecd's currently work, they can't be used
to do upgrades. They merely copy the live installation byte for byte
to the selected hardisk volumes, blowing away anything that's already
there.

--Ray

[Sergio Belkin]

2013/1/20 Ray Strode <halfline(a)gmail.com&gt;

>  Hi,
>
>  > 1. Download a LiveCD Fedora.iso (it takes less time than download the DVD
>  > iso file)
>  > 2. Launch  fedup --iso Fedora-LiveCD.iso, that make the job of adjusting
>  > GRUB2 i.a.
>  > 3. Reboot the system
>  > 3. Choose LiveCD entry from GRUB2) Perform the installation as you wish
>  Unfortunately, the way the livecd's currently work, they can't be used
>  to do upgrades. They merely copy the live installation byte for byte
>  to the selected hardisk volumes, blowing away anything that's already
>  there.
>
>  --Ray
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/devel 


Good point Ray, but even so I guess that in many of us have  a /home
directory so we can install the new version freshly...
-- 
--
Sergio Belkin  http://www.sergiobelkin.com
Watch More TV http://sebelk.blogspot.com
LPIC-2 Certified - http://www.lpi.org

[Bob Arendt]

On 01/20/2013 02:22 PM, Sergio Belkin wrote:
>  Hi Fedora community,
>
>  AFAIK fedup only works with DVD iso files not with LiveCD iso files:
>
>  I was reading the thread at
> http://lists.fedoraproject.org/pipermail/users/2013-January/429113.html something
> interesting about it
>
>  ISO files are still useful, for example to test in a quicky way on a Virtual machine, but
> I don't know you, but I'm sick of burning
>  CDs....
>
>  I think that the best and more confortable method to upgrade the OS should be:
>
>  1. Download a LiveCD Fedora.iso (it takes less time than download the DVD iso file)
>  2. Launch  fedup --iso Fedora-LiveCD.iso, that make the job of adjusting GRUB2 i.a.
>  3. Reboot the system
>  3. Choose LiveCD entry from GRUB2) Perform the installation as you wish
>
>  And forget about of burning optical discs....
>
>  Of course this does not cover all cases, for example, you should preserve the partition
> where ISO image file is.
>
>
>  What do you think?
>
>  Greetings
>  --
>  --
>  Sergio Belkin http://www.sergiobelkin.com
>  Watch More TV http://sebelk.blogspot.com
>  LPIC-2 Certified - http://www.lpi.org
>  
I find it easier (and smaller) to download the netinst.iso (like
Fedora-18-x86_64-netinst.iso)
Loop-back mount and pull the vmlinuz and initrd.img into /boot, and create a grub or
grub2
entry to start the install, adding additional options as desired (vnc display, kickstart
file).
Create a simple kickstart file and adding additional repo's (who doesn't use
rpmfusion or
some other add-on?) and mod the package list.  Then do a network install.  This has the
advantage of only downloading the most recent packages, and only the set desired.  Avoids
the  "initial install, then update most of the packages" syndrome that happens a
few months
after initial release.  The netinst.iso also doubles as a rescue install, and you can put
a couple images (e.g. 32 & 64 bit) on a single USB stick.  I'm not locked into a
"Spin"
and whether or not the packages I'm interested in made it onto the DVD.

I did several Xfce-only installs using this.  And a Gnome/KDE/Xfce/icewm joint setup using
this
same install image.  A small kickstart file provides recipe for what you want.  I also
avoid possible
confusion and manually format and label the partitions before I install.  This avoids
mistakes
with anaconda over-writing partitions you don't want disturbed.  It's better to
have have
anaconda fail to find your named partition (early) than to the have device ordering slip
and
wipe something you wanted to keep.

Cheers,
-Bob Arendt

[Ray Strode]

Hi,

>  I find it easier (and smaller) to download the netinst.iso (like
>  Fedora-18-x86_64-netinst.iso)
>  Loop-back mount and pull the vmlinuz and initrd.img into /boot 
The vmlinuz and
initrd are made available separately here:

http://mirrors.kernel.org/fedora//releases/18/Fedora/x86_64/os/images/pxe...

So you can avoid the loop-back mount.  It's a good tip, though.
Sometimes creating a grub entry is the most straightforward way to get
things rolling.

--Ray

[Rahul Sundaram]

Hi

On Sun, Jan 20, 2013 at 11:22 PM, Ray Strode wrote:

>  Hi,
>
>  > I find it easier (and smaller) to download the netinst.iso (like
>  > Fedora-18-x86_64-netinst.iso)
>  > Loop-back mount and pull the vmlinuz and initrd.img into /boot
>  The vmlinuz and initrd are made available separately here:
>
>
>  http://mirrors.kernel.org/fedora//releases/18/Fedora/x86_64/os/images/pxe...
>
>  So you can avoid the loop-back mount.  It's a good tip, though.
>  Sometimes creating a grub entry is the most straightforward way to get
>  things rolling. 

Ideally, fedup should do this as a option.  If someone wants it, file a RFE

Rahul

[Przemek Klosowski]

On 01/20/2013 11:43 PM, Rahul Sundaram wrote:
>  Hi
>
>  On Sun, Jan 20, 2013 at 11:22 PM, Ray Strodewrote:
>
>      Hi,
>
>       > I find it easier (and smaller) to download the netinst.iso (like
>       > Fedora-18-x86_64-netinst.iso)
>       > Loop-back mount and pull the vmlinuz and initrd.img into /boot
>      The vmlinuz and initrd are made available separately here:
>
>      http://mirrors.kernel.org/fedora//releases/18/Fedora/x86_64/os/images/pxe...
>
>      So you can avoid the loop-back mount.  It's a good tip, though.
>      Sometimes creating a grub entry is the most straightforward way to get
>      things rolling.
>
>
>  Ideally, fedup should do this as a option.  If someone wants it, file a RFE 
I thought fedup does this already? What am I missing here---I just ran 
fedup for the first time the other day and it created a new default 
'Update Fedora' entry during boot. How is it different from what you are 
discussing here?

[Sergio Belkin]

2013/1/22 Przemek Klosowski <przemek.klosowski(a)nist.gov&gt;

>  On 01/20/2013 11:43 PM, Rahul Sundaram wrote:
>
> > Hi
> >
> > On Sun, Jan 20, 2013 at 11:22 PM, Ray Strodewrote:
> >
> >     Hi,
> >
> >      > I find it easier (and smaller) to download the netinst.iso (like
> >      > Fedora-18-x86_64-netinst.iso)
> >      > Loop-back mount and pull the vmlinuz and initrd.img into /boot
> >     The vmlinuz and initrd are made available separately here:
> >
> >     http://mirrors.kernel.org/**fedora//releases/18/Fedora/**
> >
> x86_64/os/images/pxeboot/<http://mirrors.kernel.org/fedora//releases/1...
> >
> >     So you can avoid the loop-back mount.  It's a good tip, though.
> >     Sometimes creating a grub entry is the most straightforward way to get
> >     things rolling.
> >
> >
> > Ideally, fedup should do this as a option.  If someone wants it, file a
> > RFE
> >
>
>  I thought fedup does this already? What am I missing here---I just ran
>  fedup for the first time the other day and it created a new default 'Update
>  Fedora' entry during boot. How is it different from what you are discussing
>  here?
>
>  
We're talking about of using a LiveCD ISO file....