4:54 p.m.
Hello,
I'm a long term Debian and Ubuntu user and just tried to install Fedora
14. I want to share a couple of impressions:
I don't have a CD writer at hand, so I downloaded the netinstall image.
Following the instructions in the installation guide, I copied vmlinuz
and initrd.img from the .iso and bootet into it using my existing grub2
setup.
The first surprise came when the installer asked me where to install
from. I downloaded the network image, so I thought it'd be obvious that
I wanted to install from the network.
Lacking any URL or NFS server address, I figured that maybe the
installer is asking for the netinstall image itself? That'd be weird,
but seemed the most reasonable explanation.
Unfortunately, I am not able to use the downloaded disk image because
at this point the installer doesn't have LVM support. Brr.
Rebooted, copied the network image into NFS share, booted into the
installer again.
Now the installer reports that it can't mount the share. This is
obviously wrong, because if I try to specify the filename of the
netimage rather than just the directory, the installer complains that
this isn't the right file.
Grmbl. Reboot, read the documentation again. Ok, apparently I should be
able to manually enter the URL of a Fedora mirror. So I grab I piece of
paper and write down
http://mirror.cc.columbia.edu/pub/linux/fedora/releases/14/Fedora/x86_86/os/
Reboot, back into the installer. I am wondering why the hell I have to
enter this. The installer knows what I'm trying to install, and it should be
able to figure out where the closest mirror is.
Crash. I forgot that I downloaded the netboot image for i386. Why isn't
the installer warning me that install.img that it downloaded doesn't
work with the booted kernel?
Reboot, typed the correct address. Now I'm in a graphical mode that
knows LVM.
I'm warned about the installer not being able to update my existing
installation, but there is no existing Fedora installation. Well,
whatever.
Now the installer asks for the password of my LUKS encrypted swap
partition. Unfortunately the password is chosen at random on every boot.
It gives a really scary error message that it will not be able to use
this storage device which doesn't seem appropriate to me.
I chose manual partitioning. The installer asks me for the LUKS password
again and gives a scary error again. Now I'm trying to use the swap
partition for Fedora as well. I double click on it, and select "format
as swap", "encrypted". Doesn't seem to have any effect, there is no
indication that Fedora will actually use the device, and when I'm
reopening the dialog then my settings are gone.
Alright, so I'll do without swap for now. Next thing the installer
complains that I cannot put my root partition into LVM2. This works just
fine with Grub2, and isn't Fedora supposed to be cutting edge? Anyway,
so I try to create a primary /boot partition instead.
There is 128 MB of free space. I tell the installer to use all the space
that's available. It claims that there is not enough space left.
At this point I just got too annoyed. Am I just extremely unlucky or is
a Fedora installation always that painful?
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
10:19 a.m.
Honestly fedora is going to give you more trouble. I would install centos if
you want an rpm based install. It will save you headache when you get to the
pulse audio issues if you stay away from fedora.
You can also use Ubuntu 10.10 which I am currently using.
If you want to get fedora to install download the live USB Creator and
install from a stick. Then yum update to get current.
On 2011-02-05 11:13 AM, "Nikolaus Rath" <Nikolaus(a)rath.org> wrote:
Hello,
I'm a long term Debian and Ubuntu user and just tried to install Fedora
14. I want to share a couple of impressions:
I don't have a CD writer at hand, so I downloaded the netinstall image.
Following the instructions in the installation guide, I copied vmlinuz
and initrd.img from the .iso and bootet into it using my existing grub2
setup.
The first surprise came when the installer asked me where to install
from. I downloaded the network image, so I thought it'd be obvious that
I wanted to install from the network.
Lacking any URL or NFS server address, I figured that maybe the
installer is asking for the netinstall image itself? That'd be weird,
but seemed the most reasonable explanation.
Unfortunately, I am not able to use the downloaded disk image because
at this point the installer doesn't have LVM support. Brr.
Rebooted, copied the network image into NFS share, booted into the
installer again.
Now the installer reports that it can't mount the share. This is
obviously wrong, because if I try to specify the filename of the
netimage rather than just the directory, the installer complains that
this isn't the right file.
Grmbl. Reboot, read the documentation again. Ok, apparently I should be
able to manually enter the URL of a Fedora mirror. So I grab I piece of
paper and write down
http://mirror.cc.columbia.edu/pub/linux/fedora/releases/14/Fedora/x86_86/os/
Reboot, back into the installer. I am wondering why the hell I have to
enter this. The installer knows what I'm trying to install, and it should
be
able to figure out where the closest mirror is.
Crash. I forgot that I downloaded the netboot image for i386. Why isn't
the installer warning me that install.img that it downloaded doesn't
work with the booted kernel?
Reboot, typed the correct address. Now I'm in a graphical mode that
knows LVM.
I'm warned about the installer not being able to update my existing
installation, but there is no existing Fedora installation. Well,
whatever.
Now the installer asks for the password of my LUKS encrypted swap
partition. Unfortunately the password is chosen at random on every boot.
It gives a really scary error message that it will not be able to use
this storage device which doesn't seem appropriate to me.
I chose manual partitioning. The installer asks me for the LUKS password
again and gives a scary error again. Now I'm trying to use the swap
partition for Fedora as well. I double click on it, and select "format
as swap", "encrypted". Doesn't seem to have any effect, there is no
indication that Fedora will actually use the device, and when I'm
reopening the dialog then my settings are gone.
Alright, so I'll do without swap for now. Next thing the installer
complains that I cannot put my root partition into LVM2. This works just
fine with Grub2, and isn't Fedora supposed to be cutting edge? Anyway,
so I try to create a primary /boot partition instead.
There is 128 MB of free space. I tell the installer to use all the space
that's available. It claims that there is not enough space left.
At this point I just got too annoyed. Am I just extremely unlucky or is
a Fedora installation always that painful?
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
12:40 p.m.
On 02/04/2011 02:54 PM, Nikolaus Rath wrote:
I'm a long term Debian and Ubuntu user and just tried to install
Fedora
14. I want to share a couple of impressions:
I found this in my Junk folder on Thunderbird. Checking, it was sent to
"Undisclosed Recipients." Please don't do that, as I doubt I'm the only
one on this list who considers that a sign of spam.
1 p.m.
Nikolaus Rath <Nikolaus(a)rath.org> writes:
Hello,
I'm a long term Debian and Ubuntu user and just tried to install Fedora
14. I want to share a couple of impressions:
I don't have a CD writer at hand, so I downloaded the netinstall image.
Following the instructions in the installation guide, I copied vmlinuz
and initrd.img from the .iso and bootet into it using my existing grub2
setup.
The first surprise came when the installer asked me where to install
from. I downloaded the network image, so I thought it'd be obvious that
I wanted to install from the network.
[...]
Grmbl. Reboot, read the documentation again. Ok, apparently I should be
able to manually enter the URL of a Fedora mirror. So I grab I piece of
paper and write down
[...]
Kudos to the guys behind http://boot.fedoraproject.org, with the BFO
image the network installation is now just as pleasant as with Debian.
No need to memorize any URLs and image locations anymore.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
10:35 a.m.
New subject: Resizing PVs
On 6 February 2011 14:34, Nikolaus Rath <Nikolaus(a)rath.org> wrote:
Chris Adams <cmadams(a)hiwaay.net> writes:
> Once upon a time, Nikolaus Rath <Nikolaus(a)rath.org> said:
>> You can shrink a PV, but you will loose the extents that are stored in
>> the space that you have truncated. I don't consider that resizing.
>
> Changing the size of something is called resizing.
How would you distinguish between the resizing done by e.g. resize2fs
and the one done by fdisk?
fdisk will be resizing a partition or block device. resize2fs resizes
a filesystem.
Those are all you need to reduce the size of a fs on a physical
partition. But if you want to shrink that fs to less than the size of
the current data within it, then you also need to do some work first.
In LVM, you would first need to shrink your FS with resize2fs, then
you need to reduce the LV with lvreduce, then that gives you space in
your VG. You can then use pvresize to reduce the size of the PV and
finally fdisk to reduce the size of the PV's partition. Easy... :o(
>> Unfortunately, pvmove can only move extends to other PVs but
not to a
>> different location in the same PV.
>
> Not true. It isn't as straightforward; you have to know a map of the
> PEs and specify them to the pvmove command like (assuming the
> destination PEs are not in use):
>
> pvmove /dev/sda2:1000-1100 /dev/sda2:100-200
Oh, I didn't know about that. It seems that this thread finally produced
some useful information as well, thanks!
I didn't know this either. This definitely trumps my way of
temporarily extending the VG with another PV.
--
Sam
8:34 a.m.
New subject: Resizing PVs
Chris Adams <cmadams(a)hiwaay.net> writes:
Once upon a time, Nikolaus Rath <Nikolaus(a)rath.org> said:
> You can shrink a PV, but you will loose the extents that are stored in
> the space that you have truncated. I don't consider that resizing.
Changing the size of something is called resizing.
How would you distinguish between the resizing done by e.g. resize2fs
and the one done by fdisk?
> Unfortunately, pvmove can only move extends to other PVs but not
to a
> different location in the same PV.
Not true. It isn't as straightforward; you have to know a map of the
PEs and specify them to the pvmove command like (assuming the
destination PEs are not in use):
pvmove /dev/sda2:1000-1100 /dev/sda2:100-200
Oh, I didn't know about that. It seems that this thread finally produced
some useful information as well, thanks!
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
9:30 p.m.
New subject: Resizing PVs (was: Installation Impressions)
http://fedorasolved.org/Members/zcat/shrink-lvm-for-new-partition
Does that link have the information for handling the physical resizing?
I had used the LVM option in the past, but have gone to making regular
partitions on install, but do have some machines with old LVM setups.
+----------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
mailto:mikes@kuentos.guam.net
mailto:msetzerii@gmail.com
http://www.guam.net/home/mikes
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
SETI 10331255.834230 | EINSTEIN 5371421.810851
ROSETTA 2765286.340461 | ABC 4335306.527607
8:46 p.m.
On Sat, 2011-02-05 at 10:40 -0800, Joe Zeff wrote:
I found this in my Junk folder on Thunderbird. Checking, it was
sent
to "Undisclosed Recipients." Please don't do that, as I doubt I'm the
only one on this list who considers that a sign of spam.
Possibly due to them posting through the gmane usenet portal.
Much as I might like the idea, in principle, I find that gmane's actual
method of posting back to this list to be a nuisance. Something else
that it does is set a header so that replies go back to their
newsserver, *instead* of this list. i.e. Hijacking.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
8:46 p.m.
On Sat, 2011-02-05 at 09:39 -0800, suvayu ali wrote:
Fedora uses a patched version of GRUB Legacy. It can read /
partitions
on LVM but the /boot partition still needs to be ext* on disk.
Hmm, isn't it more the case that the *kernel* reads the LVM partitions?
GRUB starts loading the kernel, which is in the /boot partition. From
then on, it's the kernel doing the work, GRUB has passed the baton on.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
6:52 p.m.
On Sat, Feb 5, 2011 at 3:26 PM, Kevin J. Cummings
<cummings(a)kjchome.homeip.net> wrote:
On 02/05/2011 01:16 PM, Nikolaus Rath wrote:
>
> How come that Fedora sticks with GRUB Legacy? One of my reasons for
> wanting to try Fedora was to get quicker access to new features, so I'm
> really surprised to find that the first thing that I get in contact with
> is an outdated GRUB...
Grub-2.0 is available in the repos. If you want it, install and use it:
yum install grub2
"yum install grub2 gettext" otherwise grub.cfg won't be created.
6:10 p.m.
New subject: Resizing PVs (was: Installation Impressions)
Once upon a time, Nikolaus Rath <Nikolaus(a)rath.org> said:
You can shrink a PV, but you will loose the extents that are stored
in
the space that you have truncated. I don't consider that resizing.
Changing the size of something is called resizing.
Unfortunately, pvmove can only move extends to other PVs but not to
a
different location in the same PV.
Not true. It isn't as straightforward; you have to know a map of the
PEs and specify them to the pvmove command like (assuming the
destination PEs are not in use):
pvmove /dev/sda2:1000-1100 /dev/sda2:100-200
IIRC you get a warning, and it is slow (obviously, reading and writing a
bunch of data on the same drive is slow).
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
5:22 p.m.
New subject: Resizing PVs
Sam Sharpe <lists.redhat(a)samsharpe.net> writes:
On 5 February 2011 22:15, Nikolaus Rath <Nikolaus(a)rath.org>
wrote:
> You can shrink a PV, but you will loose the extents that are stored in
> the space that you have truncated. I don't consider that resizing.
That's interesting. I do consider it resizing... It's not the function
of the pvresize command to move the LVs around so that it is possible
to downsize the PV. That's something that the admin must do.
My definition of resizing is shrinking without the need for temporary
additional storage. A partition can be resized by resizing the file
system and then shrinking the partition with fdisk. A logical volume can
be resized the same way. A physical volume can not be resized, you first
need to put the data (extents) somewhere else.
Yes, so it won't do exactly what you want in one command, so you
have
to do it a different way. I have in the past added a second PV,
In my case that doesn't work. I just created one PV for every harddisk,
I never had the need for additional PVs or partitions until now. Well,
my bad luck I guess.
> Why so aggressive?
I wasn't being particularly aggressive, but I do actually dislike
people saying (or abbreviating) "just for the record" when they are
incorrect or the facts are disputed. The only thing that goes in the
official record are the facts.
My intention was just to avoid a reply of the form "Then use an USB
stick instead". It's not that I am not able to work around the problems,
I just wanted to clarify that it can be quite a hassle.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
4:28 p.m.
New subject: Resizing PVs (was: Installation Impressions)
On 5 February 2011 22:15, Nikolaus Rath <Nikolaus(a)rath.org> wrote:
You can shrink a PV, but you will loose the extents that are stored
in
the space that you have truncated. I don't consider that resizing.
That's interesting. I do consider it resizing... It's not the function
of the pvresize command to move the LVs around so that it is possible
to downsize the PV. That's something that the admin must do.
If I use fdisk to resize a partition, is it fdisk's job to resize the
filesystem?
From the same manpage that you looked up:
,----
| pvresize will refuse to shrink PhysicalVolume if it has allocated
| extents after where its new end would be. In the future, it should
| relocate these elsewhere in the volume group if there is sufficient free
| space, like pvmove does.
`----
Yup, that is true - so you need to free up those extents first. Often
this is done by adding a second temporary PV to the VG.
Unfortunately, pvmove can only move extends to other PVs but not to
a
different location in the same PV.
Yes, so it won't do exactly what you want in one command, so you have
to do it a different way. I have in the past added a second PV,
Extended the VG to this PV, then moved enough LVs to that second PV to
make reducing the original PV feasible. But the fact remains, that you
can shrink a Physical Volume.
Why so aggressive?
I wasn't being particularly aggressive, but I do actually dislike
people saying (or abbreviating) "just for the record" when they are
incorrect or the facts are disputed. The only thing that goes in the
official record are the facts.
--
Sam
4:15 p.m.
New subject: Resizing PVs (was: Installation Impressions)
Sam Sharpe <lists.redhat(a)samsharpe.net> writes:
On 5 February 2011 20:53, Nikolaus Rath <Nikolaus(a)rath.org>
wrote:
> JFTR, unfortunately PVs cannot be made smaller. The whole idea of LVM is
> to do all the resize operations *within* the containers.
JFTR, unfortunately, you'll need to raise a bug against the pvresize
manpage then...
http://linux.die.net/man/8/pvresize
---
Shrink the PV on /dev/sda1 prior to shrinking the partition with fdisk
(ensure that the PV size is appropriate for your intended new
partition size):
pvresize --setphysicalvolumesize 40G /dev/sda1
---
When filing the report, please state why your assertion "for the
record" is correct over the maintainer's.
You can shrink a PV, but you will loose the extents that are stored in
the space that you have truncated. I don't consider that resizing.
From the same manpage that you looked up:
,----
| pvresize will refuse to shrink PhysicalVolume if it has allocated
| extents after where its new end would be. In the future, it should
| relocate these elsewhere in the volume group if there is sufficient free
| space, like pvmove does.
`----
Unfortunately, pvmove can only move extends to other PVs but not to a
different location in the same PV.
Why so aggressive?
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
4 p.m.
On 5 February 2011 20:53, Nikolaus Rath <Nikolaus(a)rath.org> wrote:
suvayu ali <fatkasuvayu+linux(a)gmail.com> writes:
>> Ugh. So I have hundreds of free GBs in my LVM VGs, but I won't be able
>> to install Fedora? Is there no way around this?
>
> Well you have two options I think,
>
> 1. the obvious first, resize your LVMs to free 500 MB and use it as
> /boot
JFTR, unfortunately PVs cannot be made smaller. The whole idea of LVM is
to do all the resize operations *within* the containers.
JFTR, unfortunately, you'll need to raise a bug against the pvresize
manpage then...
http://linux.die.net/man/8/pvresize
---
Shrink the PV on /dev/sda1 prior to shrinking the partition with fdisk
(ensure that the PV size is appropriate for your intended new
partition size):
pvresize --setphysicalvolumesize 40G /dev/sda1
---
When filing the report, please state why your assertion "for the
record" is correct over the maintainer's.
--
Sam
2:53 p.m.
suvayu ali <fatkasuvayu+linux(a)gmail.com> writes:
> Ugh. So I have hundreds of free GBs in my LVM VGs, but I
won't be able
> to install Fedora? Is there no way around this?
Well you have two options I think,
1. the obvious first, resize your LVMs to free 500 MB and use it as
/boot
JFTR, unfortunately PVs cannot be made smaller. The whole idea of LVM is
to do all the resize operations *within* the containers.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
2:51 p.m.
Gilboa Davara <gilboad(a)gmail.com> writes:
On Fri, 2011-02-04 at 17:54 -0500, Nikolaus Rath wrote:
> Hello,
>
> I'm a long term Debian and Ubuntu user and just tried to install Fedora
> 14. I want to share a couple of impressions:
I wonder, what exactly were you trying to achieve?
Beyond a possible (?) bug report when dealing with your swap (and I
doubt it), your post is pure rent.
Not everything that's not praise or a bugreport is a rant. I think the
subject summarizes my intentions very well. Maybe I'm too naive, but I
honestly believed some people might be interested in feedback about the
installation process.
I do not think that everything that irritates me is necessarily a bug,
so I considered it more productive to raise these issues here on the
mailing list than to rush ahead and file several bugreports.
Let me help you:
1. Fedora uses grub1.
2. Fedora doesn't support /boot on LVM.
3. Fedora requires you to remember the URL of your network installation
image.
Well, thank you so much for this concise summary of my own mail.
4. All of the above is well documented.
Where? Pointers appreciated.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
2:26 p.m.
On 02/05/2011 01:16 PM, Nikolaus Rath wrote:
How come that Fedora sticks with GRUB Legacy? One of my reasons for
wanting to try Fedora was to get quicker access to new features, so I'm
really surprised to find that the first thing that I get in contact with
is an outdated GRUB...
Grub-2.0 is available in the repos. If you want it, install and use it:
yum install grub2
--
Kevin J. Cummings
kjchome(a)verizon.net
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
12:34 p.m.
On Sat, 2011-02-05 at 20:29 +0200, Gilboa Davara wrote:
On Fri, 2011-02-04 at 17:54 -0500, Nikolaus Rath wrote:
> Hello,
>
> I'm a long term Debian and Ubuntu user and just tried to install Fedora
> 14. I want to share a couple of impressions:
I wonder, what exactly were you trying to achieve?
Beyond a possible (?) bug report when dealing with your swap (and I
doubt it), your post is pure rent.
Forgot to add.
I case your post was a (very!) misguided plea for help.
Please post the your partition table and disk configuration - maybe
it'll be possible to work around the lack of boot space problem.
- Gilboa
12:29 p.m.
On Fri, 2011-02-04 at 17:54 -0500, Nikolaus Rath wrote:
Hello,
I'm a long term Debian and Ubuntu user and just tried to install Fedora
14. I want to share a couple of impressions:
I wonder, what exactly were you trying to achieve?
Beyond a possible (?) bug report when dealing with your swap (and I
doubt it), your post is pure rent.
Let me help you:
1. Fedora uses grub1.
2. Fedora doesn't support /boot on LVM.
3. Fedora requires you to remember the URL of your network installation
image.
4. All of the above is well documented.
Now, if 1-4 prevents you from using Fedora you could be civil (!!!) or
even, God forbids, constructive, and post an RFE in
http://bugzilla.redhat.com stating the problem and a possible solution,
hoping that your use-case will be enough to justify the effort.
On the other hand, you can rant @Fedora-users and feel good about
yourself.
Your choice.
- Gilboa
12:28 p.m.
On Sat, Feb 5, 2011 at 10:16 AM, Nikolaus Rath <Nikolaus(a)rath.org> wrote:
> Fedora uses a patched version of GRUB Legacy. It can read /
partitions
> on LVM but the /boot partition still needs to be ext* on disk.
How come that Fedora sticks with GRUB Legacy? One of my reasons for
wanting to try Fedora was to get quicker access to new features, so I'm
really surprised to find that the first thing that I get in contact with
is an outdated GRUB...
Not sure about the exact reasons for this.
>> There is 128 MB of free space. I tell the installer to use
all the space
>> that's available. It claims that there is not enough space left.
>>
>
> In Fedora we use an application called preupgrade for distro upgrades.
> During those upgrades the installer downloads the new kernel images to
> /boot before the upgrade is performed. On previous versions there has
> been problems where the /boot was not large enough and upgrades failed.
> So from F12 the recommended /boot size is 500MB to avoid such issues.
Ugh. So I have hundreds of free GBs in my LVM VGs, but I won't be able
to install Fedora? Is there no way around this?
Well you have two options I think,
1. the obvious first, resize your LVMs to free 500 MB and use it as
/boot
2. use an external drive (even small USB drives should work) as your
/boot. I haven't done this personally but there are many on this list
who do that. You should be able to find some discussions about this
in the archives.
However there is a more adventurous option, you can use option 2 above
to boot the netinstall iso but then actually install Fedora with grub2
from the repos. That way you get a Fedora install which uses grub2. I
think there are a few pages on the wiki about this. As far as I recall
there are some people on the list who use grub2. So maybe you can search
in the fedoraproject wiki and then start a new thread asking how others
do it.
Hope these help.
--
Suvayu
Open source is the future. It sets us free.
12:16 p.m.
suvayu ali <fatkasuvayu+linux(a)gmail.com> writes:
I don't know about your other issues, but I'll try to answer
the ones below.
On Fri, Feb 4, 2011 at 2:54 PM, Nikolaus Rath <Nikolaus(a)rath.org> wrote:
> Alright, so I'll do without swap for now. Next thing the installer
> complains that I cannot put my root partition into LVM2. This works just
> fine with Grub2, and isn't Fedora supposed to be cutting edge? Anyway,
> so I try to create a primary /boot partition instead.
Fedora uses a patched version of GRUB Legacy. It can read / partitions
on LVM but the /boot partition still needs to be ext* on disk.
How come that Fedora sticks with GRUB Legacy? One of my reasons for
wanting to try Fedora was to get quicker access to new features, so I'm
really surprised to find that the first thing that I get in contact with
is an outdated GRUB...
> There is 128 MB of free space. I tell the installer to use all
the space
> that's available. It claims that there is not enough space left.
>
In Fedora we use an application called preupgrade for distro upgrades.
During those upgrades the installer downloads the new kernel images to
/boot before the upgrade is performed. On previous versions there has
been problems where the /boot was not large enough and upgrades failed.
So from F12 the recommended /boot size is 500MB to avoid such issues.
Ugh. So I have hundreds of free GBs in my LVM VGs, but I won't be able
to install Fedora? Is there no way around this?
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
11:39 a.m.
I don't know about your other issues, but I'll try to answer the ones below.
On Fri, Feb 4, 2011 at 2:54 PM, Nikolaus Rath <Nikolaus(a)rath.org> wrote:
Alright, so I'll do without swap for now. Next thing the
installer
complains that I cannot put my root partition into LVM2. This works just
fine with Grub2, and isn't Fedora supposed to be cutting edge? Anyway,
so I try to create a primary /boot partition instead.
Fedora uses a patched version of GRUB Legacy. It can read / partitions
on LVM but the /boot partition still needs to be ext* on disk.
There is 128 MB of free space. I tell the installer to use all the
space
that's available. It claims that there is not enough space left.
In Fedora we use an application called preupgrade for distro upgrades.
During those upgrades the installer downloads the new kernel images to
/boot before the upgrade is performed. On previous versions there has
been problems where the /boot was not large enough and upgrades failed.
So from F12 the recommended /boot size is 500MB to avoid such issues.
At this point I just got too annoyed. Am I just extremely unlucky or
is
a Fedora installation always that painful?
I hope I answered a few of your issues.
--
Suvayu
Open source is the future. It sets us free.
11:07 a.m.
On Sat, 5 Feb 2011 10:19:03 -0600 Thomas Paine <painethom(a)gmail.com>
wrote:
Honestly fedora is going to give you more trouble. I would install
centos if you want an rpm based install. It will save you headache when you get to the
pulse audio issues if you stay away from fedora.
I don;t know about that. I have never had trouble with Fedora
installs from 1 to 14, except when my HW was very new (iwl4965)
about two years ago. I have had some minor trouble with ubuntu. Fedora
is a leading-edge distribution and you get what you bargain for.
You can also use Ubuntu 10.10 which I am currently using.
If you want to get fedora to install download the live USB Creator and install from a
stick. Then yum update to get current.
This (update to get current) is true even for a network install
(unfortunately), even though it does not need to be.
Really, with regard to distributions, to each his/her own. My wife
prefers and uses Ubuntu: I have stuck with Fedora.
Ranjan
On 2011-02-05 11:13 AM, "Nikolaus Rath"
<Nikolaus@rath.org<mailto:Nikolaus@rath.org>> wrote:
> Hello,
>
> I'm a long term Debian and Ubuntu user and just tried to install Fedora
> 14. I want to share a couple of impressions:
>
> I don't have a CD writer at hand, so I downloaded the netinstall image.
> Following the instructions in the installation guide, I copied vmlinuz
> and initrd.img from the .iso and bootet into it using my existing grub2
> setup.
>
> The first surprise came when the installer asked me where to install
> from. I downloaded the network image, so I thought it'd be obvious that
> I wanted to install from the network.
>
> Lacking any URL or NFS server address, I figured that maybe the
> installer is asking for the netinstall image itself? That'd be weird,
> but seemed the most reasonable explanation.
>
> Unfortunately, I am not able to use the downloaded disk image because
> at this point the installer doesn't have LVM support. Brr.
>
> Rebooted, copied the network image into NFS share, booted into the
> installer again.
>
> Now the installer reports that it can't mount the share. This is
> obviously wrong, because if I try to specify the filename of the
> netimage rather than just the directory, the installer complains that
> this isn't the right file.
>
> Grmbl. Reboot, read the documentation again. Ok, apparently I should be
> able to manually enter the URL of a Fedora mirror. So I grab I piece of
> paper and write down
>
> http://mirror.cc.columbia.edu/pub/linux/fedora/releases/14/Fedora/x86_86/os/
>
> Reboot, back into the installer. I am wondering why the hell I have to
> enter this. The installer knows what I'm trying to install, and it should be
> able to figure out where the closest mirror is.
>
> Crash. I forgot that I downloaded the netboot image for i386. Why isn't
> the installer warning me that install.img that it downloaded doesn't
> work with the booted kernel?
>
> Reboot, typed the correct address. Now I'm in a graphical mode that
> knows LVM.
>
> I'm warned about the installer not being able to update my existing
> installation, but there is no existing Fedora installation. Well,
> whatever.
>
> Now the installer asks for the password of my LUKS encrypted swap
> partition. Unfortunately the password is chosen at random on every boot.
> It gives a really scary error message that it will not be able to use
> this storage device which doesn't seem appropriate to me.
>
> I chose manual partitioning. The installer asks me for the LUKS password
> again and gives a scary error again. Now I'm trying to use the swap
> partition for Fedora as well. I double click on it, and select "format
> as swap", "encrypted". Doesn't seem to have any effect, there is
no
> indication that Fedora will actually use the device, and when I'm
> reopening the dialog then my settings are gone.
>
> Alright, so I'll do without swap for now. Next thing the installer
> complains that I cannot put my root partition into LVM2. This works just
> fine with Grub2, and isn't Fedora supposed to be cutting edge? Anyway,
> so I try to create a primary /boot partition instead.
>
> There is 128 MB of free space. I tell the installer to use all the space
> that's available. It claims that there is not enough space left.
>
> At this point I just got too annoyed. Am I just extremely unlucky or is
> a Fedora installation always that painful?
>
>
> Best,
>
>
> -Nikolaus
>
> --
> »Time flies like an arrow, fruit flies like a Banana.«
>
> PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
> --
> users mailing list
> users@lists.fedoraproject.org<mailto:users@lists.fedoraproject.org>
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
9:50 p.m.
i do believe you have had an unfortunate and rare occurrence while installing the most
advanced linux OS
i have been installing fedora since fedora 8 came out and up until the latest ubuntu came
out (10.10) Fedora has been much easier for me personally to install. Usually taking a max
of 3 hrs total to to install the os.
methods of installation i have tried:
USB Boot image of fedora 10 - 14 Gnome and kde
Live Image of fedora 8 - 14 Gnome, kde and lxde
Dvd image of Fedora 9 - 14 Gnome and Kde
Current system:
Phenom II X4 945 clock: 3.06Ghz
G.Skill 8gb ddr2 pc 8500 1066mhz (4 * 2gb)
ATI HD 4670 512mb ddr5 pci-e16x
HDD1 Sata3gb 320gb WD |Partitions: 4; Windows 7 ultimate 64; Fedora 14; JULinux8Stable
HDD2 Sata3gb 1tb WD |Partitions: 1;ntfs formatted storage
HDD3 Sata3gb 1tb WD |Partitions: 1;ntfs formatted storage
HDD4 Sata6gb 1tb WD |Partitions: 1;ntfs formatted storage
ASUS 21.5in HD LCD Monitor
ASUS 21.5in HD LCD Monitor
ASUS N Wifi pci-e1x
ASUS BT USB Doggle
ASUS CD/DVD Combo Burner
ASUS M4A78-EM Motherboard
Antec 650 Earthwatts PSU
Xigmatec Utgard mesh case
Next 5 fan controller
Next 5 fan controller
Logitech Trackman wired mouse
Microsoft/Razor Recluse keyboard
Planar 21.5in touchpanel monitor ( touch keyboard interface i designed) :P
the main drive hosting the operating systems hosts 3 different operating systems but each
operating system are optimized and tweaked to emulate the same full functionality and
compatability that the windows 7 ultimate offers.
Note: Julinux is based on Ubuntu
i'd advise getting a usb drive and visiting fedoras documentation pages to get the app
specifically for making fedora usb images to get through your difficulties with ease.
From: Nikolaus(a)rath.org
Subject: Installation Impressions
Date: Fri, 4 Feb 2011 17:54:34 -0500
To:
Hello,
I'm a long term Debian and Ubuntu user and just tried to install Fedora
14. I want to share a couple of impressions:
I don't have a CD writer at hand, so I downloaded the netinstall image.
Following the instructions in the installation guide, I copied vmlinuz
and initrd.img from the .iso and bootet into it using my existing grub2
setup.
The first surprise came when the installer asked me where to install
from. I downloaded the network image, so I thought it'd be obvious that
I wanted to install from the network.
Lacking any URL or NFS server address, I figured that maybe the
installer is asking for the netinstall image itself? That'd be weird,
but seemed the most reasonable explanation.
Unfortunately, I am not able to use the downloaded disk image because
at this point the installer doesn't have LVM support. Brr.
Rebooted, copied the network image into NFS share, booted into the
installer again.
Now the installer reports that it can't mount the share. This is
obviously wrong, because if I try to specify the filename of the
netimage rather than just the directory, the installer complains that
this isn't the right file.
Grmbl. Reboot, read the documentation again. Ok, apparently I should be
able to manually enter the URL of a Fedora mirror. So I grab I piece of
paper and write down
http://mirror.cc.columbia.edu/pub/linux/fedora/releases/14/Fedora/x86_86/os/
Reboot, back into the installer. I am wondering why the hell I have to
enter this. The installer knows what I'm trying to install, and it should be
able to figure out where the closest mirror is.
Crash. I forgot that I downloaded the netboot image for i386. Why isn't
the installer warning me that install.img that it downloaded doesn't
work with the booted kernel?
Reboot, typed the correct address. Now I'm in a graphical mode that
knows LVM.
I'm warned about the installer not being able to update my existing
installation, but there is no existing Fedora installation. Well,
whatever.
Now the installer asks for the password of my LUKS encrypted swap
partition. Unfortunately the password is chosen at random on every boot.
It gives a really scary error message that it will not be able to use
this storage device which doesn't seem appropriate to me.
I chose manual partitioning. The installer asks me for the LUKS password
again and gives a scary error again. Now I'm trying to use the swap
partition for Fedora as well. I double click on it, and select "format
as swap", "encrypted". Doesn't seem to have any effect, there is no
indication that Fedora will actually use the device, and when I'm
reopening the dialog then my settings are gone.
Alright, so I'll do without swap for now. Next thing the installer
complains that I cannot put my root partition into LVM2. This works just
fine with Grub2, and isn't Fedora supposed to be cutting edge? Anyway,
so I try to create a primary /boot partition instead.
There is 128 MB of free space. I tell the installer to use all the space
that's available. It claims that there is not enough space left.
At this point I just got too annoyed. Am I just extremely unlucky or is
a Fedora installation always that painful?
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
3:48 p.m.
From one that has used SuSE, OpenSuSE, Mandrake, Mandriva, Ubuntu,
Debian, Redhat before fedora, Fedora, RedHat, CentOS, Scientific
Linux, Knoppix,
DSL, Unbreakable Linux, EEEbuntu, and a dozen other distros over that last 12 years I:
For Home use CentOS for a server and Fedora for my desktop and netbook
At work I use
CentOS and Fedora for mostly dev and systems that don't require RedHat or SuSE to get
support on their software
Use Red Hat Enterprise Linux for critical production services
OpenSuse and Ubuntu for Student Lab machines
OpenSuse is currently on my desktop but I sorely miss Fedora and want to change soon.
Why do I mention this, because each installation comes with it's various quirks and I
choose distros based on their strengths and my
current need at the time.
I still shy away from LVM although I am starting to use it now that it installs (at least
with Fedora 14 with a more sensible naming
convention other than VolGroup00 ). The first time I had to take a LVM drive from one
system to another years ago it was painful
and I still feel the burn from that trying to get it working.
When Ubuntu came out and seemed to be the next best thing I tried it for some time and
found that a lot of what I considered to be
enterprise functionality (LDAP authentication, NFS server, Auto-mounting) either
didn't work well or required that I manually patch
it for things that where already in Fedora.
I just recently installed Debian 6.0 and was sorely disappointed in the look and way that
KDE was setup by default. I liked the gui
installer and I think Debian does a number of things right and some wrong. Just as with
any other distribution, there is some bad
but mostly good. I certainly like the way synaptic works and I like some of the
improvements that Ubuntu has made (I like the use
of sudo and gksu by default)
What we need to keep in mind is that there are may distributions out there and chances are
that you can find one that fits your
style and use case. Fedora is not for everyone as much as I would like it to be.
Certainly I have fought with what I consider to
be dumb defaults in many distributions ( preference of compiz over metacity comes to mind
in SLED and the general removal of
nautilus-open-terminal from most default Gnome installation, I really don't need
wobbly windows and burn effects). More often than
not the visual effects (while I applaud the community for developing and looking ahead and
really showcasing what linux and the
community can do), it does tend to interfere with some applications that I use such as
blender and seems to cause me more headaches
then it solves.
When I do an installation, I rarely do an upgrade. I like clean installs and either NFS
mount my home directory from a server or
keep a separate /home partition so that whatever system I install I can still keep my user
files. If for some reason I didn't put a
/home I use another hard drive to tar up my home directory and later restore it after an
installation.
This doesn't really help with the issue at hand but it's my use case.
regards,
-Tomas
3:06 p.m.
On 02/05/2011 12:53 PM, Nikolaus Rath wrote:
JFTR, unfortunately PVs cannot be made smaller. The whole idea of LVM
is
to do all the resize operations*within* the containers.
This, however, is a special case because /boot needs to be a regular
partition, not part of an LVM. Personally, for home computers, I
consider LVM to be a solution in search of a problem and would prefer
that it weren't the default configuration because most home users have
no need for it.
4803
days inactive
4836
days old
27 comments
14 participants
participants (14)
-
Chris Adams -
Gilboa Davara -
Joe Zeff -
Kevin Cummings -
Michael D. Setzer II -
Nikolaus Rath -
paul weston -
Ranjan Maitra -
Sam Sharpe -
Suvayu Ali -
Thomas Paine -
Tim -
Tom H -
Tomas Hajek