8:51 a.m.
Hey all,
for those of us who are a little reluctant about moving to Gnome3 just yet,
does anyone know if there are plans to release rpms of kernel versions later
than 2.6.35 for F14?
Best,
Chris
12:08 p.m.
On Thu, Aug 25, 2011 at 6:51 AM, Christopher Svanefalk
<christopher.svanefalk(a)gmail.com> wrote:
Hey all,
for those of us who are a little reluctant about moving to Gnome3 just yet,
does anyone know if there are plans to release rpms of kernel versions later
than 2.6.35 for F14?
Is there any chance that Fedora will extend security updates for F14
until F16 comes out to allow time for gnome3 to improve?
+1 if you agree
--
Robert Arkiletian
Eric Hamber Secondary, Vancouver, Canada
12:20 p.m.
On 09/01/2011 10:08 AM, Robert Arkiletian wrote:
Is there any chance that Fedora will extend security updates for F14
until F16 comes out to allow time for gnome3 to improve?
AIUI, it's standard for Fedora to provide security and other updates for
each version right up until it reaches End Of Life. For F14, that will
be shortly after F16 is released.
12:14 p.m.
On Thu, Sep 1, 2011 at 10:08 AM, Robert Arkiletian <robark(a)gmail.com> wrote:
On Thu, Aug 25, 2011 at 6:51 AM, Christopher Svanefalk
<christopher.svanefalk(a)gmail.com> wrote:
> Hey all,
>
> for those of us who are a little reluctant about moving to Gnome3 just yet,
> does anyone know if there are plans to release rpms of kernel versions later
> than 2.6.35 for F14?
>
Is there any chance that Fedora will extend security updates for F14
until F16 comes out to allow time for gnome3 to improve?
+1 if you agree
Sorry I meant until F17
--
Robert Arkiletian
Eric Hamber Secondary, Vancouver, Canada
2:21 p.m.
On 08/31/2011 12:08 PM, stan wrote:
Does this mean it is possible to update a non-running system by
using
releasever and installroot? e.g. update F14 from F15
yum -y update --releasever=14 --installdir=<path to F14 root>
It might, but I'd think that it'd be safer to use chroot to avoid any
chance of problems. If nothing else, you'd want the F14 database
updated, not the F15, even if you're doing this from a LiveCD.
9:08 p.m.
On Wed, 31 Aug 2011 14:21:12 -0500
Richard Shaw <hobbes1069(a)gmail.com> wrote:
On Wed, Aug 31, 2011 at 2:08 PM, stan <gryt2(a)q.com> wrote:
> Do you know if a yum clean meta would clean up the cache
> corruption after doing this?
It appears to store the information separately. I haven't had any
problems using this. I don't think you need to do anything afterwards.
> Does this mean it is possible to update a non-running system by
> using releasever and installroot? e.g. update F14 from F15
> yum -y update --releasever=14 --installdir=<path to F14 root>
I would think so but have never tried that. I usually do the 'chroot
/mtn/sysimage' method.After that I would think it would properly
detect the release of the chroot regardless of the rescue system you
booted.
Thank you Richard (and Joe) for your responses. It seems that the
chroot method is the way to go.
2:21 p.m.
On Wed, Aug 31, 2011 at 2:08 PM, stan <gryt2(a)q.com> wrote:
> >> $ yumdownloader --source <package>
> >>
> > That's true if you are getting the package for the currently running
> > system, and it is how I get src.rpm packages on F15. But doing
> > that on F14 will not get an F15 package. The OP is running F14 and
> > wants newer kernels. I didn't, however, check whether
> > yumdownloader has an option like yum to set other repositories
> > while dowloading. There could be, and in that case your suggestion
> > will work with a little tweaking.
>
> $ yumdownloader --releasever=15 --source <package>
>
Thanks for that. After your post I looked at the options for
yumdownloader, and it turns out it inherits options from yum, and this
is one of them. Here's what it says about that option:
--releasever=version
Pretend the current release version is the given string.
This is very useful when combined with --installroot. Note that with
...
Do you know if a yum clean meta would clean up the cache corruption
after doing this?
It appears to store the information separately. I haven't had any
problems using this. I don't think you need to do anything afterwards.
Does this mean it is possible to update a non-running system by
using
releasever and installroot? e.g. update F14 from F15
yum -y update --releasever=14 --installdir=<path to F14 root>
I would think so but have never tried that. I usually do the 'chroot
/mtn/sysimage' method.After that I would think it would properly
detect the release of the chroot regardless of the rescue system you
booted.
Richard
2:08 p.m.
On Wed, 31 Aug 2011 10:09:40 -0500
Richard Shaw <hobbes1069(a)gmail.com> wrote:
On Wed, Aug 31, 2011 at 9:57 AM, stan <gryt2(a)q.com> wrote:
> On Wed, 31 Aug 2011 12:31:36 +0200
> suvayu ali <fatkasuvayu+linux(a)gmail.com> wrote:
>
>> On Wed, Aug 31, 2011 at 5:01 AM, stan <gryt2(a)q.com> wrote:
>> > as user, rpm -ivh the src.rpm package (you will have to get this
>> > manually from a repository)
>> >
>>
>> $ yumdownloader --source <package>
>>
> That's true if you are getting the package for the currently running
> system, and it is how I get src.rpm packages on F15. But doing
> that on F14 will not get an F15 package. The OP is running F14 and
> wants newer kernels. I didn't, however, check whether
> yumdownloader has an option like yum to set other repositories
> while dowloading. There could be, and in that case your suggestion
> will work with a little tweaking.
$ yumdownloader --releasever=15 --source <package>
Thanks for that. After your post I looked at the options for
yumdownloader, and it turns out it inherits options from yum, and this
is one of them. Here's what it says about that option:
--releasever=version
Pretend the current release version is the given string.
This is very useful when combined with --installroot. Note that with
the default upstream cachedir, of /var/cache/yum, using this option
will corrupt your cache (and you can use $releasever in your
cachedir configuration to stop this).
Is it necessary to have the repo files for the desired repository
installed, or does it get them off the web in a one-off manner?
Do you know if a yum clean meta would clean up the cache corruption
after doing this?
Does this mean it is possible to update a non-running system by using
releasever and installroot? e.g. update F14 from F15
yum -y update --releasever=14 --installdir=<path to F14 root>
10:09 a.m.
On Wed, Aug 31, 2011 at 9:57 AM, stan <gryt2(a)q.com> wrote:
On Wed, 31 Aug 2011 12:31:36 +0200
suvayu ali <fatkasuvayu+linux(a)gmail.com> wrote:
> On Wed, Aug 31, 2011 at 5:01 AM, stan <gryt2(a)q.com> wrote:
> > as user, rpm -ivh the src.rpm package (you will have to get this
> > manually from a repository)
> >
>
> $ yumdownloader --source <package>
>
That's true if you are getting the package for the currently running
system, and it is how I get src.rpm packages on F15. But doing that on
F14 will not get an F15 package. The OP is running F14 and wants newer
kernels. I didn't, however, check whether yumdownloader has an option
like yum to set other repositories while dowloading. There could be,
and in that case your suggestion will work with a little tweaking.
$ yumdownloader --releasever=15 --source <package>
:)
Richard
9:59 a.m.
Am 31.08.2011 16:57, schrieb stan:
> $ yumdownloader --source <package>
>
That's true if you are getting the package for the currently running
system, and it is how I get src.rpm packages on F15. But doing that on
F14 will not get an F15 package. The OP is running F14 and wants newer
kernels. I didn't, however, check whether yumdownloader has an option
like yum to set other repositories while dowloading. There could be,
and in that case your suggestion will work with a little tweaking.
why not simply download the src.rpm from http://koji.fedoraproject.org/koji/builds
9:57 a.m.
On Wed, 31 Aug 2011 12:31:36 +0200
suvayu ali <fatkasuvayu+linux(a)gmail.com> wrote:
On Wed, Aug 31, 2011 at 5:01 AM, stan <gryt2(a)q.com> wrote:
> as user, rpm -ivh the src.rpm package (you will have to get this
> manually from a repository)
>
$ yumdownloader --source <package>
That's true if you are getting the package for the currently running
system, and it is how I get src.rpm packages on F15. But doing that on
F14 will not get an F15 package. The OP is running F14 and wants newer
kernels. I didn't, however, check whether yumdownloader has an option
like yum to set other repositories while dowloading. There could be,
and in that case your suggestion will work with a little tweaking.
8:56 p.m.
On 08/25/2011 07:21 PM, Christopher Svanefalk wrote:
Hey all,
for those of us who are a little reluctant about moving to Gnome3 just
yet, does anyone know if there are plans to release rpms of kernel
versions later than 2.6.35 for F14?
You can find the status at
https://fedoraproject.org/wiki/Kernel
Rahul
10:01 p.m.
On Thu, 25 Aug 2011 15:51:34 +0200
Christopher Svanefalk <christopher.svanefalk(a)gmail.com> wrote:
for those of us who are a little reluctant about moving to Gnome3
just yet, does anyone know if there are plans to release rpms of
kernel versions later than 2.6.35 for F14?
I can't answer your question about updates, but I can tell you that the
2.6.38 kernel src.rpm packages from F15 compile and run fine on F14.
The 2.6.40 packages (version 3 kernels) compile fine but have
dependency issues when installing. I didn't try resolving them.
https://fedoraproject.org/wiki/Building_a_custom_kernel
If you aren't making any changes to the configuration of the kernel, it
is very straightforward to compile the src.rpm package.
Pretty much
install the rpmbuild utilities
as user, rpm -ivh the src.rpm package (you will have to get this
manually from a repository)
cd to ~/rpmbuild/SPECS and run rpmbuild -bb kernel.spec
The output will be under ~/rpmbuild/RPMS/<arch> and you can just
install the RPMs with yum (as root).
I usually run dracut to create a custom initramfs tuned to my system,
replacing the one in the grub menu with my own.
HTH
4620
days inactive
4627
days old
13 comments
8 participants
participants (8)
-
Christopher Svanefalk -
Joe Zeff -
Rahul Sundaram -
Reindl Harald -
Richard Shaw -
Robert Arkiletian -
stan -
Suvayu Ali