Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Jessie Minimum Kernel Requirement
19 views
Skip to first unread message
Florian Lindner
Oct 16, 2013, 6:00:02 AM10/16/13
to
Hello!
I plan to use Debian on a virtual server where I can't control the
kernel version, that is 2.6.32.
What is the minimum kernel version for the upcoming Jessie? Can I rely
on that this does no change after the freeze? (IIRC at Nov 5th)
Thanks,
Florian
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/c8bc612c3d420e2f...@centershock.net
I plan to use Debian on a virtual server where I can't control the
kernel version, that is 2.6.32.
What is the minimum kernel version for the upcoming Jessie? Can I rely
on that this does no change after the freeze? (IIRC at Nov 5th)
Thanks,
Florian
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/c8bc612c3d420e2f...@centershock.net
Brad Rogers
Oct 16, 2013, 7:00:01 AM10/16/13
to
On Wed, 16 Oct 2013 11:46:40 +0200
Florian Lindner <mailin...@xgm.de> wrote:
Hello Florian,
>on that this does no change after the freeze? (IIRC at Nov 5th)
Freeze is still over a year away, so probably a wee bit early to say
what kernel version will be used.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
You're only 29 got a lot to learn
Seventeen - Sex Pistols
Florian Lindner <mailin...@xgm.de> wrote:
Hello Florian,
>on that this does no change after the freeze? (IIRC at Nov 5th)
what kernel version will be used.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
You're only 29 got a lot to learn
Seventeen - Sex Pistols
recov...@gmail.com
Oct 16, 2013, 8:00:02 AM10/16/13
to
Hi.
wheezy to jessie (and that means using wheezy's kernel with jessie's
userland, at least temporary), it should be safe to assume that minimum
kernel requirement for jessie's userland is 2.6.32.
Since wheezy's kernel version is fixed for its lifetime, it's highly
unlikely that such requirement will change in the future.
Of course, wheezy's 2.6.32 and, say, CentOS's 2.6.32 are different
kernels, and in the second case you can expect all kinds of strange
behaviour.
Reco
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20131016155406.fad2...@gmail.com
> What is the minimum kernel version for the upcoming Jessie? Can I rely
> on that this does no change after the freeze? (IIRC at Nov 5th)
Considering one should be always able to do apt-get dist-upgrade from
> on that this does no change after the freeze? (IIRC at Nov 5th)
wheezy to jessie (and that means using wheezy's kernel with jessie's
userland, at least temporary), it should be safe to assume that minimum
kernel requirement for jessie's userland is 2.6.32.
Since wheezy's kernel version is fixed for its lifetime, it's highly
unlikely that such requirement will change in the future.
Of course, wheezy's 2.6.32 and, say, CentOS's 2.6.32 are different
kernels, and in the second case you can expect all kinds of strange
behaviour.
Reco
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Darac Marjal
Oct 16, 2013, 8:10:02 AM10/16/13
to
On Wed, Oct 16, 2013 at 03:54:06PM +0400, recov...@gmail.com wrote:
> Hi.
>
> On Wed, 16 Oct 2013 11:46:40 +0200
> Florian Lindner <mailin...@xgm.de> wrote:
>
> > What is the minimum kernel version for the upcoming Jessie? Can I rely
> > on that this does no change after the freeze? (IIRC at Nov 5th)
>
> Considering one should be always able to do apt-get dist-upgrade from
> wheezy to jessie (and that means using wheezy's kernel with jessie's
> userland, at least temporary), it should be safe to assume that minimum
> kernel requirement for jessie's userland is 2.6.32.
This isn't really a safe assumption. There have been transitions in the
> Hi.
>
> On Wed, 16 Oct 2013 11:46:40 +0200
> Florian Lindner <mailin...@xgm.de> wrote:
>
> > What is the minimum kernel version for the upcoming Jessie? Can I rely
> > on that this does no change after the freeze? (IIRC at Nov 5th)
>
> Considering one should be always able to do apt-get dist-upgrade from
> wheezy to jessie (and that means using wheezy's kernel with jessie's
> userland, at least temporary), it should be safe to assume that minimum
> kernel requirement for jessie's userland is 2.6.32.
past (such as udev) where the dist-upgrade should be performed as:
* Update sources.list
* Install new kernel and new udev
* Reboot
* Proceed with dist-upgrade
After the reboot, you're then running on the previous release's userland
with the current release's kernel. That situation SHOULD be more stable
than the other way around as kernels /rarely/ remove functionality. But
if you run new userland on an old kernel, and it tries to call
functionality that's not there, you can run into trouble.
Tom H
Oct 16, 2013, 8:30:02 AM10/16/13
to
On Wed, Oct 16, 2013 at 8:00 AM, Darac Marjal <maili...@darac.org.uk> wrote:
> On Wed, Oct 16, 2013 at 03:54:06PM +0400, recov...@gmail.com wrote:
>> On Wed, 16 Oct 2013 11:46:40 +0200
>> Florian Lindner <mailin...@xgm.de> wrote:
>>>
>>> What is the minimum kernel version for the upcoming Jessie? Can I rely
>>> on that this does no change after the freeze? (IIRC at Nov 5th)
>>
>> Considering one should be always able to do apt-get dist-upgrade from
>> wheezy to jessie (and that means using wheezy's kernel with jessie's
>> userland, at least temporary), it should be safe to assume that minimum
>> kernel requirement for jessie's userland is 2.6.32.
>
> This isn't really a safe assumption. There have been transitions in the
> past (such as udev) where the dist-upgrade should be performed as:
> * Update sources.list
> * Install new kernel and new udev
> * Reboot
> * Proceed with dist-upgrade
>
> After the reboot, you're then running on the previous release's userland
> with the current release's kernel. That situation SHOULD be more stable
> than the other way around as kernels /rarely/ remove functionality. But
> if you run new userland on an old kernel, and it tries to call
> functionality that's not there, you can run into trouble.
>
>> Since wheezy's kernel version is fixed for its lifetime, it's highly
>> unlikely that such requirement will change in the future.
Furthermore, Wheezy's kernel is 3.2 not 2.6.32.
> On Wed, Oct 16, 2013 at 03:54:06PM +0400, recov...@gmail.com wrote:
>> On Wed, 16 Oct 2013 11:46:40 +0200
>> Florian Lindner <mailin...@xgm.de> wrote:
>>>
>>> What is the minimum kernel version for the upcoming Jessie? Can I rely
>>> on that this does no change after the freeze? (IIRC at Nov 5th)
>>
>> Considering one should be always able to do apt-get dist-upgrade from
>> wheezy to jessie (and that means using wheezy's kernel with jessie's
>> userland, at least temporary), it should be safe to assume that minimum
>> kernel requirement for jessie's userland is 2.6.32.
>
> This isn't really a safe assumption. There have been transitions in the
> past (such as udev) where the dist-upgrade should be performed as:
> * Update sources.list
> * Install new kernel and new udev
> * Reboot
> * Proceed with dist-upgrade
>
> After the reboot, you're then running on the previous release's userland
> with the current release's kernel. That situation SHOULD be more stable
> than the other way around as kernels /rarely/ remove functionality. But
> if you run new userland on an old kernel, and it tries to call
> functionality that's not there, you can run into trouble.
>
>> Since wheezy's kernel version is fixed for its lifetime, it's highly
>> unlikely that such requirement will change in the future.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Osamu Aoki
Oct 16, 2013, 10:10:03 AM10/16/13
to
Soon, testing/jessie will only have 3.10.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Dmitrii Kashin
Oct 16, 2013, 12:40:01 PM10/16/13
to
Florian Lindner <mailin...@xgm.de> writes:
> I plan to use Debian on a virtual server where I can't control the
> kernel version, that is 2.6.32.
>
> What is the minimum kernel version for the upcoming Jessie?
I am using Jessie with the kernel from Wheezy. Don't worry, it's safe to
> I plan to use Debian on a virtual server where I can't control the
> kernel version, that is 2.6.32.
>
> What is the minimum kernel version for the upcoming Jessie?
upgrade.
Sven Joachim
Oct 16, 2013, 1:10:02 PM10/16/13
to
On 2013-10-16 11:46 +0200, Florian Lindner wrote:
> I plan to use Debian on a virtual server where I can't control the
> kernel version, that is 2.6.32.
>
> What is the minimum kernel version for the upcoming Jessie?
Currently 2.6.32, the version in Squeeze (oldstable).
> I plan to use Debian on a virtual server where I can't control the
> kernel version, that is 2.6.32.
>
> What is the minimum kernel version for the upcoming Jessie?
> Can I rely
> on that this does no change after the freeze? (IIRC at Nov 5th)
packages like udev might need a newer kernel then. However, you usually
do not need those on a vserver.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Florian Lindner
Oct 16, 2013, 4:00:03 PM10/16/13
to
Am Mittwoch, 16. Oktober 2013, 11:46:40 schrieb Florian Lindner:
> Hello!
>
> I plan to use Debian on a virtual server where I can't control the
> kernel version, that is 2.6.32.
>
> What is the minimum kernel version for the upcoming Jessie? Can I rely
> on that this does no change after the freeze? (IIRC at Nov 5th)
Basic false assumption was that I read Nov 5th 2013 instead of 2014. So I'll
> Hello!
>
> I plan to use Debian on a virtual server where I can't control the
> kernel version, that is 2.6.32.
>
> What is the minimum kernel version for the upcoming Jessie? Can I rely
> on that this does no change after the freeze? (IIRC at Nov 5th)
stick with wheezy.
FL
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Gregory Nowak
Oct 16, 2013, 4:50:03 PM10/16/13
to
On Wed, Oct 16, 2013 at 08:30:33PM +0400, Dmitrii Kashin wrote:
> I am using Jessie with the kernel from Wheezy. Don't worry, it's safe to
> upgrade.
As has already been pointed out, the kernel that comes with wheezy is
> I am using Jessie with the kernel from Wheezy. Don't worry, it's safe to
> upgrade.
3.2. The OP stated the kernel being used is 2.6.32, which came with
squeeze. So the fact that squeeze's kernel works with jessy isn't
relevant. Squeeze's kernel works with wheezy from what I've heard, but
I wouldn't expect it to keep working with jessy, even if it does so
now.
Greg
--
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
--
Free domains: http://www.eu.org/ or mail dns-m...@EU.org
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Oct 16, 2013, 5:30:02 PM10/16/13
to
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
recov...@gmail.com
Oct 17, 2013, 6:00:02 AM10/17/13
to
On Wed, 16 Oct 2013 08:21:35 -0400
Tom H <tomh...@gmail.com> wrote:
> Furthermore, Wheezy's kernel is 3.2 not 2.6.32.
OOPS, you've got me. I mistook squeeze for wheezy.
Tom H <tomh...@gmail.com> wrote:
> Furthermore, Wheezy's kernel is 3.2 not 2.6.32.
Reco.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
recov...@gmail.com
Oct 17, 2013, 6:10:01 AM10/17/13
to
On Wed, 16 Oct 2013 13:00:19 +0100
Darac Marjal <maili...@darac.org.uk> wrote:
> This isn't really a safe assumption. There have been transitions in the
> past (such as udev) where the dist-upgrade should be performed as:
> * Update sources.list
> * Install new kernel and new udev
> * Reboot
> * Proceed with dist-upgrade
Interesting. Don't remember running such procedure. Was it for testing
Darac Marjal <maili...@darac.org.uk> wrote:
> This isn't really a safe assumption. There have been transitions in the
> past (such as udev) where the dist-upgrade should be performed as:
> * Update sources.list
> * Install new kernel and new udev
> * Reboot
> * Proceed with dist-upgrade
or sid?
Reco
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bonno Bloksma
Oct 17, 2013, 6:30:02 AM10/17/13
to
Hi Reco,
>> This isn't really a safe assumption. There have been transitions in
>> the past (such as udev) where the dist-upgrade should be performed as:
>> * Update sources.list
>> * Install new kernel and new udev
>> * Reboot
>> * Proceed with dist-upgrade
>
> Interesting. Don't remember running such procedure. Was it for testing or sid?
If I remember correctly it was in the step from Lenny to Squeeze. I know for sure I had to do it on several machines.
Yup, just found it in my old notes, it was Lenny to Squeeze.
Bonno Bloksma
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/89D1798A7351D040B4E7...@HGLEXCH-01.tio.nl
>> This isn't really a safe assumption. There have been transitions in
>> the past (such as udev) where the dist-upgrade should be performed as:
>> * Update sources.list
>> * Install new kernel and new udev
>> * Reboot
>> * Proceed with dist-upgrade
>
> Interesting. Don't remember running such procedure. Was it for testing or sid?
Yup, just found it in my old notes, it was Lenny to Squeeze.
Bonno Bloksma
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
recov...@gmail.com
Oct 17, 2013, 7:00:02 AM10/17/13
to
On Thu, 17 Oct 2013 10:23:30 +0000
Bonno Bloksma <b.bl...@tio.nl> wrote:
> Hi Reco,
>
> >> This isn't really a safe assumption. There have been transitions in
> >> the past (such as udev) where the dist-upgrade should be performed as:
> >> * Update sources.list
> >> * Install new kernel and new udev
> >> * Reboot
> >> * Proceed with dist-upgrade
> >
> > Interesting. Don't remember running such procedure. Was it for testing or sid?
>
> If I remember correctly it was in the step from Lenny to Squeeze. I know for sure I had to do it on several machines.
> Yup, just found it in my old notes, it was Lenny to Squeeze.
Thanks, that explains why I don't remember it - I was running testing
Bonno Bloksma <b.bl...@tio.nl> wrote:
> Hi Reco,
>
> >> This isn't really a safe assumption. There have been transitions in
> >> the past (such as udev) where the dist-upgrade should be performed as:
> >> * Update sources.list
> >> * Install new kernel and new udev
> >> * Reboot
> >> * Proceed with dist-upgrade
> >
> > Interesting. Don't remember running such procedure. Was it for testing or sid?
>
> If I remember correctly it was in the step from Lenny to Squeeze. I know for sure I had to do it on several machines.
> Yup, just found it in my old notes, it was Lenny to Squeeze.
those days.
Back to the topic of discussion - I'm pretty sure that this wasn't
needed for squeeze → wheezy transition.
Reco
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Oct 17, 2013, 7:10:02 AM10/17/13
to
On Thu, Oct 17, 2013 at 6:00 AM, <recov...@gmail.com> wrote:
> On Wed, 16 Oct 2013 13:00:19 +0100
> Darac Marjal <maili...@darac.org.uk> wrote:
>
>> This isn't really a safe assumption. There have been transitions in the
>> past (such as udev) where the dist-upgrade should be performed as:
>> * Update sources.list
>> * Install new kernel and new udev
>> * Reboot
>> * Proceed with dist-upgrade
>
> Interesting. Don't remember running such procedure. Was it for testing
> or sid?
Lenny to Squeeze dist-upgrade
> On Wed, 16 Oct 2013 13:00:19 +0100
> Darac Marjal <maili...@darac.org.uk> wrote:
>
>> This isn't really a safe assumption. There have been transitions in the
>> past (such as udev) where the dist-upgrade should be performed as:
>> * Update sources.list
>> * Install new kernel and new udev
>> * Reboot
>> * Proceed with dist-upgrade
>
> Interesting. Don't remember running such procedure. Was it for testing
> or sid?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
James Cloos
Oct 17, 2013, 1:30:03 PM10/17/13
to
>>>>> "TH" == Tom H <tomh...@gmail.com> writes:
TH> The OP wants to use the Squeeze kernel and the Jessie userspace.
More likely openvz's kernel. Probably non-deb, too.
-JimC
--
James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/m338nz4...@carbon.jhcloos.org
TH> The OP wants to use the Squeeze kernel and the Jessie userspace.
More likely openvz's kernel. Probably non-deb, too.
-JimC
--
James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Beco
Oct 17, 2013, 10:40:01 PM10/17/13
to
On 17 October 2013 07:23, Bonno Bloksma <b.bl...@tio.nl> wrote:
> If I remember correctly it was in the step from Lenny to Squeeze. I know for sure I had to do it on several machines.
> Yup, just found it in my old notes, it was Lenny to Squeeze.
>
> Bonno Bloksma
>
Hi Bonno, hi Reco,
> If I remember correctly it was in the step from Lenny to Squeeze. I know for sure I had to do it on several machines.
> Yup, just found it in my old notes, it was Lenny to Squeeze.
>
> Bonno Bloksma
>
Yep, I confirm. I did this on my personal computers and two servers a
while back. Kind of confusing... I almost lost one of the servers. I
hope as time and Debian evolves, these procedures go safer and safer.
Best,
Beco.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Bannister
Oct 19, 2013, 11:10:02 PM10/19/13
to
On Thu, Oct 17, 2013 at 11:30:46PM -0300, Beco wrote:
> Yep, I confirm. I did this on my personal computers and two servers a
> while back. Kind of confusing... I almost lost one of the servers. I
> hope as time and Debian evolves, these procedures go safer and safer.
Several transitions may take place in sid/testing over the life of a
> Yep, I confirm. I did this on my personal computers and two servers a
> while back. Kind of confusing... I almost lost one of the servers. I
> hope as time and Debian evolves, these procedures go safer and safer.
stable release, hence when it comes time to upgrade to the next stable
there may be a couple of gotchas. But all this will be documented in the
releasenotes and must be read *BEFORE* doing the upgrade.
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages