Re: reasons to ditch LILO before upgrading to jessie?

Stephen Powell wrote: > As far as LILO being unmaintained is concerned, I wouldn't be too concerned > about that. I've been thinking about offering to maintain it myself. I > haven't > heard from Joachim lately. Maybe I'll drop him another line. I think LILO is an important part of Linux

Re: reasons to ditch LILO before upgrading to jessie?

On Sat, Jul 9, 2016, at 18:25, Brian wrote: > On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote: >> >> Long live choice! > > For choice to exist it does not have to be presented as such in the > installer. > Your point is well taken. The installer does not offer choice in everything,

Re: reasons to ditch LILO before upgrading to jessie?

Brian composed on 2016-07-09 21:00 (UTC+0100): ...the installer inexplicably offers a choice between GRUB and LILO. The installer manual is unhelpful on which to choose. A newcomer wouldn't have a clue. We do them no service with this retrograde offering. Get rid of it. Probably a Bad idea.

Re: reasons to ditch LILO before upgrading to jessie?

On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote: > On Sat, Jul 9, 2016, at 16:00, Brian wrote: > > > > All well and good but the installer inexplicably offers a choice between > > GRUB and LILO. The installer manual is unhelpful on which to choose. A > > newcomer wouldn't have a clue.

Re: reasons to ditch LILO before upgrading to jessie?

On Sat 09 Jul 2016 at 22:05:45 +0200, Erwan David wrote: > Le 09/07/2016 à 22:00, Brian a écrit : > > > > What is the point of a choice? Just offer GRUB; it is the bootloader for > > Debian and has many advantages over LILO in todayss Linux ecosystem. > > People who have a great desire to use

Re: reasons to ditch LILO before upgrading to jessie?

On Sat, Jul 9, 2016, at 16:33, Felix Miata wrote: > > All that's well and good, but I see nothing there that equates to my > understanding of the meaning of "editing", which includes removal as well as > appending. Oh, I see what you're saying. Well, the Linux kernel generally does it's own

Re: reasons to ditch LILO before upgrading to jessie?

On Sat, Jul 9, 2016, at 16:00, Brian wrote: > > All well and good but the installer inexplicably offers a choice between > GRUB and LILO. The installer manual is unhelpful on which to choose. A > newcomer wouldn't have a clue. We do them no service with this retrograde > offering. Get rid of it.

Re: reasons to ditch LILO before upgrading to jessie?

Erwan David composed on 2016-07-09 22:05 (UTC+0200): Brian composed: What is the point of a choice? Just offer GRUB; it is the bootloader for Debian... What is the point of a choice, just use the windows provided with your PC... :-D Linux and debian is just about choice given to the

Re: reasons to ditch LILO before upgrading to jessie?

Stephen Powell composed on 2016-07-09 13:19 (UTC-0400): Felix Miata wrote: Stephen Powell composed on 2016-07-09 08:58 (UTC-0400): As for features, LILO has all the features that I need. One feature it never acquired AFAIK, which Grub shares with Syslinux, is the

Re: reasons to ditch LILO before upgrading to jessie?

Le 09/07/2016 à 22:00, Brian a écrit : > > What is the point of a choice? Just offer GRUB; it is the bootloader for > Debian and has many advantages over LILO in todayss Linux ecosystem. > People who have a great desire to use LILO can search it out. > > Unmaintained in Debian, The bit-rot starts

Re: reasons to ditch LILO before upgrading to jessie?

On Sat 09 Jul 2016 at 13:19:08 -0400, Stephen Powell wrote: > On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote: > > Stephen Powell composed on 2016-07-09 08:58 (UTC-0400): > > > >> As for features, LILO has all the features that I need. > > > > One feature it never acquired AFAIK, which Grub

Re: reasons to ditch LILO before upgrading to jessie?

On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote: > Stephen Powell composed on 2016-07-09 08:58 (UTC-0400): > >> As for features, LILO has all the features that I need. > > One feature it never acquired AFAIK, which Grub shares with Syslinux, is the > ability to edit the kernel cmdline at boot

Re: reasons to ditch LILO before upgrading to jessie?

Stephen Powell composed on 2016-07-09 08:58 (UTC-0400): As for features, LILO has all the features that I need. One feature it never acquired AFAIK, which Grub shares with Syslinux, is the ability to edit the kernel cmdline at boot time, before kernel load. With problematic hardware,

Re: reasons to ditch LILO before upgrading to jessie?

On Thu, Jul 7, 2016, at 20:53, Felix Miata wrote: > Stephen Powell composed on 2016-07-07 20:30 (UTC-0400): > > > If your system has a BIOS and a traditional DOS-style partition table, > > there's no reason not to use LILO, unless you just don't want to. > > Or, if you like to be able to boot

Re: reasons to ditch LILO before upgrading to jessie?

On 08/07/16 07:06 PM, Brian wrote: On Fri 08 Jul 2016 at 18:13:01 -0400, Gary Dale wrote: On 08/07/16 02:19 PM, Brian wrote: If you have some way of easily adjusting files in /etc/grub.d to the needs of a user I wish you would say. So that's the problem. You never took the time to RTFM. See

Re: reasons to ditch LILO before upgrading to jessie?

On Fri 08 Jul 2016 at 18:13:01 -0400, Gary Dale wrote: > >>On 08/07/16 02:19 PM, Brian wrote: > > > >If you have some way of easily adjusting files in /etc/grub.d to the > >needs of a user I wish you would say. > So that's the problem. You never took the time to RTFM. See >

Re: reasons to ditch LILO before upgrading to jessie?

On Fri 08 Jul 2016 at 16:57:30 -0500, David Wright wrote: > On Fri 08 Jul 2016 at 21:16:00 (+0100), Brian wrote: > > > Stop moaning. Do it or file file a bug, Then stop moaning and do it. > > I'm the person without a complaint about Grub2, not the one moaning. Apologies. I was intending to

Re: reasons to ditch LILO before upgrading to jessie?

On 08/07/16 03:51 PM, Brian wrote: On Fri 08 Jul 2016 at 15:08:21 -0400, Gary Dale wrote: On 08/07/16 02:19 PM, Brian wrote: On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: On 07/07/16 05:12 PM, Brian wrote: On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: On 07/07/16

Re: reasons to ditch LILO before upgrading to jessie?

On Fri 08 Jul 2016 at 21:16:00 (+0100), Brian wrote: > On Fri 08 Jul 2016 at 14:23:01 -0500, David Wright wrote: > > On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote: > > > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: > > > > On 07/07/16 05:12 PM, Brian wrote: > > > > >On Thu 07 Jul

Re: reasons to ditch LILO before upgrading to jessie?

On Fri 08 Jul 2016 at 14:23:01 -0500, David Wright wrote: > On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote: > > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: > > > On 07/07/16 05:12 PM, Brian wrote: > > > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: > > > >>On 07/07/16

Re: reasons to ditch LILO before upgrading to jessie?

On Fri 08 Jul 2016 at 15:08:21 -0400, Gary Dale wrote: > On 08/07/16 02:19 PM, Brian wrote: > >On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: > > > >>On 07/07/16 05:12 PM, Brian wrote: > >>>On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: > >>> > On 07/07/16 02:55 PM, David

Re: reasons to ditch LILO before upgrading to jessie?

On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote: > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: > > On 07/07/16 05:12 PM, Brian wrote: > > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: > > >>On 07/07/16 02:55 PM, David Wright wrote: > > >>>On Thu 07 Jul 2016 at 14:39:51

Re: reasons to ditch LILO before upgrading to jessie?

On 08/07/16 02:19 PM, Brian wrote: On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: On 07/07/16 05:12 PM, Brian wrote: On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: On 07/07/16 02:55 PM, David Wright wrote: On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: The big

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote: > On 07/07/16 05:12 PM, Brian wrote: > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: > > > >>On 07/07/16 02:55 PM, David Wright wrote: > >>>On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: > The big selling feature of

Re: reasons to ditch LILO before upgrading to jessie?

Gary Dale composed on 2016-07-07 14:39 (UTC-0400): It also has a "rescue shell" that I've never been able to do anything useful with. When grub fails, I boot from a rescue cd instead. That way I get a real working environment. The Grub shell works the same whether in boot rescue mode or run

Re: reasons to ditch LILO before upgrading to jessie?

On 07/07/16 05:12 PM, Brian wrote: On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: On 07/07/16 02:55 PM, David Wright wrote: On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: The big selling feature of Grub over Lilo was that it didn't need to updated each time you changed

Re: reasons to ditch LILO before upgrading to jessie?

Stephen Powell composed on 2016-07-07 20:30 (UTC-0400): If your system has a BIOS and a traditional DOS-style partition table, there's no reason not to use LILO, unless you just don't want to. Or, if you like to be able to boot without hunting down rescue media even though you forgot to

Re: reasons to ditch LILO before upgrading to jessie?

On Thu, Jul 7, 2016, at 10:57, Giovanni Gigante wrote: > > At the end, I decided to try the upgrade to jessie with LiLo (24.1) in > place. I thought that the probability of hitting some bug caused by the > interaction between LiLo and the upgraded distribution was less than the > probabily of

Re: reasons to ditch LILO before upgrading to jessie?

On 07/07/2016 05:47 PM, rhkra...@gmail.com wrote: I'll take advantage of this thread to ask a question / express my frustration with grub: The thing that always frustrated me about grub is that, iirc, they counted disks / partitions different than lilo and the rest of Linux--they start

Re: reasons to ditch LILO before upgrading to jessie?

On 07/07/2016 05:47 PM, rhkra...@gmail.com wrote: I'll take advantage of this thread to ask a question / express my frustration with grub: The thing that always frustrated me about grub is that, iirc, they counted disks / partitions different than lilo and the rest of Linux--they start

Re: reasons to ditch LILO before upgrading to jessie?

I'll take advantage of this thread to ask a question / express my frustration with grub: The thing that always frustrated me about grub is that, iirc, they counted disks / partitions different than lilo and the rest of Linux--they start counting at 1 (like Windows, iirc), and lilo and Linux

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote: > On 07/07/16 02:55 PM, David Wright wrote: > >On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: > >>The big selling feature of Grub over Lilo was that it didn't need to > >>updated each time you changed something. That fell by the

Re: reasons to ditch LILO before upgrading to jessie?

On 07/07/2016 01:55 PM, David Wright wrote: On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: The big selling feature of Grub over Lilo was that it didn't need to updated each time you changed something. That fell by the wayside with Grub 2. Now the big selling feature is that it works

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 15:18:05 (-0400), Gary Dale wrote: > On 07/07/16 02:55 PM, David Wright wrote: > >On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: > >>The big selling feature of Grub over Lilo was that it didn't need to > >>updated each time you changed something. That fell by the

Re: reasons to ditch LILO before upgrading to jessie?

On 07/07/16 02:55 PM, David Wright wrote: On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: The big selling feature of Grub over Lilo was that it didn't need to updated each time you changed something. That fell by the wayside with Grub 2. Now the big selling feature is that it works

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote: > The big selling feature of Grub over Lilo was that it didn't need to > updated each time you changed something. That fell by the wayside > with Grub 2. Now the big selling feature is that it works with more > than just Linux. I guess I

Re: reasons to ditch LILO before upgrading to jessie?

, so it does not seem deprecated yet. So the question is: is there any serious reason to switch the system to GRUB before upgrading, or can I just keep my current setup and proceed to jessie? Thanks Giovanni The big selling feature of Grub over Lilo was that it didn't need to updated each time

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 08:33:57 (+0200), to...@tuxteam.de wrote: > On Wed, Jul 06, 2016 at 02:23:39PM -0500, Don Armstrong wrote: > > On Wed, 06 Jul 2016, Jonathan Dowland wrote: > > > YMMV, I find it impenetrable. > > > > I'm assuming you mean the generated configuration? It's literally just > >

Re: reasons to ditch LILO before upgrading to jessie?

Brian wrote: Giovanni Gigante seems happy enough with LiLo and there appears to be no definite indication that it would fail to boot an upgraded machine. He could consider leaving it in place, reading the bug reports and having a plan to install GRUB should something go wrong afterwards. At

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 12:44:40 +0200, to...@tuxteam.de wrote: > On Thu, Jul 07, 2016 at 11:32:42AM +0100, Brian wrote: > > On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote: > > > > > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote: > > > > Let's make it (GRUB2) impenetrable

Re: reasons to ditch LILO before upgrading to jessie?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jul 07, 2016 at 11:32:42AM +0100, Brian wrote: > On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote: > > > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote: > > > Let's make it (GRUB2) impenetrable boilerplate, then. > > > > :-)

Re: reasons to ditch LILO before upgrading to jessie?

On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote: > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote: > > Let's make it (GRUB2) impenetrable boilerplate, then. > > :-) +1! It doesn't need to be penetrable, does it? The generated grub.cfg just needs to boot the machine. In any

Re: reasons to ditch LILO before upgrading to jessie?

On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote: > Let's make it (GRUB2) impenetrable boilerplate, then. :-) +1! Lisi

Re: reasons to ditch LILO before upgrading to jessie?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Jul 06, 2016 at 02:23:39PM -0500, Don Armstrong wrote: > On Wed, 06 Jul 2016, Jonathan Dowland wrote: > > YMMV, I find it impenetrable. > > I'm assuming you mean the generated configuration? It's literally just > some boilerplate [...] Let's

Re: reasons to ditch LILO before upgrading to jessie?

On Wed, 06 Jul 2016, Jonathan Dowland wrote: > YMMV, I find it impenetrable. I'm assuming you mean the generated configuration? It's literally just some boilerplate for fancy splash screens, and then menu entries. Each entry containing appropriate module loading, root configuration, kernel and

Re: reasons to ditch LILO before upgrading to jessie?

On Tue, Jul 05, 2016 at 04:46:32PM -0500, Don Armstrong wrote: > On Tue, 05 Jul 2016, Marc Shapiro wrote: > > I finally switched to Jessie (but still using SysV Init) a few months > > ago. This box and its predecessors have uses lilo (and SysV Init) > > since Bo was a pup. I have yet to see any

Re: reasons to ditch LILO before upgrading to jessie?

On Tue, 05 Jul 2016, Marc Shapiro wrote: > I finally switched to Jessie (but still using SysV Init) a few months > ago. This box and its predecessors have uses lilo (and SysV Init) > since Bo was a pup. I have yet to see any real reason to switch from > lilo to grub. I have never had a problem

Re: reasons to ditch LILO before upgrading to jessie?

tion manual still mentions it, so it does not seem deprecated yet. So the question is: is there any serious reason to switch the system to GRUB before upgrading, or can I just keep my current setup and proceed to jessie? There's always the possibility that you'll discover a new bug with lilo and n

Re: reasons to ditch LILO before upgrading to jessie?

sie installation manual still > mentions it, so it does not seem deprecated yet. So the question is: > is there any serious reason to switch the system to GRUB before > upgrading, or can I just keep my current setup and proceed to jessie? There's always the possibility that you'll dis

reasons to ditch LILO before upgrading to jessie?

tion is: is there any serious reason to switch the system to GRUB before upgrading, or can I just keep my current setup and proceed to jessie? Thanks Giovanni

Re: Update: Last Linux kernel did not install correctly (was: Re: Problems with Apper / automatic upgrading of my Debian 7.11 system)

On Wednesday 29 June 2016 10:44:46 Selim T. Erdoğan wrote: > On Tue, Jun 28, 2016 at 09:32:43AM -0400, rhkra...@gmail.com wrote: > > Ok, I now believe that my problem is that the last Linux image > > (kernel) update did not install correctly / completely. That image > > was "linux-image-3.2.0-4-

Re: Update: Last Linux kernel did not install correctly (was: Re: Problems with Apper / automatic upgrading of my Debian 7.11 system)

On Tue, Jun 28, 2016 at 09:32:43AM -0400, rhkra...@gmail.com wrote: > Ok, I now believe that my problem is that the last Linux image (kernel) > update > did not install correctly / completely. That image was "linux-image-3.2.0-4- > amd64 Linux 3.2 for 64-bit PCs" > > I believe that what has

Update: Last Linux kernel did not install correctly (was: Re: Problems with Apper / automatic upgrading of my Debian 7.11 system)

Ok, I now believe that my problem is that the last Linux image (kernel) update did not install correctly / completely. That image was "linux-image-3.2.0-4- amd64 Linux 3.2 for 64-bit PCs" I believe that what has been happening since then is that, each time I've installed something else (either

Re: Problems with Apper / automatic upgrading of my Debian 7.11 system

That sounds like good advice, thanks! But, has anyone else had similar problems recently with "automatic" upgrades in apper (see my original post), or can anyone explain (or theorize) on what is going on? On Monday, June 27, 2016 01:48:41 PM Johann Klammer wrote: > Don't reboot until you know

Re: Problems with Apper / automatic upgrading of my Debian 7.11 system

Don't reboot until you know that the bootloader got installed correctly. Ideally have a boot CD ready in case it goes wrong.

Re: Problems with Apper / automatic upgrading of my Debian 7.11 system

. * Or, do you think my problems with upgrading / Apper are because I didn't activate the new kernel? * But, that wouldn't explain the problem with they first problematic upgrade, which was the kernel... Thanks for any clarification you can add... On Monday, June 27, 2016 10:27:24 AM

Problems with Apper / automatic upgrading of my Debian 7.11 system

Background: Since I upgraded to Debian 7.11 (wheezy) maybe 6 months to a year ago (maybe longer), I've made it a habit to upgrade any software for which Apper notifies me that an upgrade is available. Something like two weeks ago, I upgraded the Linux kernel when notified. Before the upgrade

Re: Upgrading iceweasel on Wheezy LTS

On 2016-06-10, Sven Joachim wrote: >> >> How would that work having both packages on my system at the same time; >> I mean, for example, if I typed 'firefox' in a terminal which flavor >> would I be likely to launch? > > The non-esr version if it is present on your system. I'm

Re: Upgrading iceweasel on Wheezy LTS

On Fri, 2016-06-10 at 18:07 +0200, Sven Joachim wrote: > That's because gnome-core in Wheezy depends on iceweasel.  Probably > the > dependencies of such metapackages won't be changed in Wheezy.  If you > really want to avoid having to install firefox-esr, you could build > your > own iceweasel

Re: Upgrading iceweasel on Wheezy LTS

On 2016-06-10 17:14 +, Curt wrote: > On 2016-06-10, Sven Joachim wrote: >> On 2016-06-10 08:13 +, Curt wrote: >> >>> In order to upgrade iceweasel, apt is asking to install an extra >>> package, notably firefox-esr, whereas (when) I am running firefox-release. >> >> Yes.

Re: Upgrading iceweasel on Wheezy LTS

On 2016-06-10, Sven Joachim wrote: > On 2016-06-10 08:13 +, Curt wrote: > >> In order to upgrade iceweasel, apt is asking to install an extra >> package, notably firefox-esr, whereas (when) I am running firefox-release. > > Yes. The switch from iceweasel to firefox-esr has

Re: Upgrading iceweasel on Wheezy LTS

On 2016-06-10 08:13 +, Curt wrote: > In order to upgrade iceweasel, apt is asking to install an extra > package, notably firefox-esr, whereas (when) I am running firefox-release. Yes. The switch from iceweasel to firefox-esr has been mentioned in the recent DSA 3600-1 security

Upgrading iceweasel on Wheezy LTS

Hello, In order to upgrade iceweasel, apt is asking to install an extra package, notably firefox-esr, whereas (when) I am running firefox-release. Is this a dilemma? Can I run both firefox-esr and firefox-release? Unfortunately I'm in one of those situations in which if I wanted to take the

Re: Upgrading from Backports

On Wed, 08 Jun 2016, Alex Mestiashvili wrote: > On 06/07/2016 11:46 PM, Patrick Bartek wrote: > > Need to upgrade claws-mail installed from regular repo to a newer > > version in wheezy-backports. I don't want to end up with two > > installed versions. Have done research, but have found nothing

Re: Upgrading from Backports

backports? I did this > > with LibreOffice a few years ago. Worked fine. > > Doesn't really make a difference. The state of your system should be > the same after either 'remove && install' or a simple 'install'. I'll try "upgrading" without the version number. Yes, there's only one version of claws-mail in wheezy-backports, which is newer than the regular repo version. Thanks for clarifying. B

Re: Upgrading from Backports

Patrick Bartek: > Need to upgrade claws-mail installed from regular repo to a newer > version in wheezy-backports. I don't want to end up with two installed > versions. Have done research, but have found nothing specific about > this particular procedure. Would > >apt-get install -t

Re: Upgrading from Backports

On 06/07/2016 11:46 PM, Patrick Bartek wrote: > Need to upgrade claws-mail installed from regular repo to a newer > version in wheezy-backports. I don't want to end up with two installed > versions. Have done research, but have found nothing specific about > this particular procedure. Would >

Upgrading from Backports

Need to upgrade claws-mail installed from regular repo to a newer version in wheezy-backports. I don't want to end up with two installed versions. Have done research, but have found nothing specific about this particular procedure. Would apt-get install -t wheezy-backports claws-mail=

Re: Upgrading from 8.2 to 8.4

On Fri, 13 May 2016 10:13:59 -0400 Steve Matzura wrote: > Are 'apt-get update' and 'apt-get dist-upgrade' sufficient? > > Yes. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. There is a multi-legged creature crawling on

Upgrading from 8.2 to 8.4

Are 'apt-get update' and 'apt-get dist-upgrade' sufficient?

Re: Re: Problem upgrading libc6 on sid

> If you are working from remote machine, the problem might be restarting > services which kills your connection. The problem is that it did not behave this way on any of the other containers on either of my hosts. These are all via ssh connections, the same as I have been doing since 2002. --b

Re: Problem upgrading libc6 on sid

On Mon, 1 Feb 2016 07:41:47 -0500 Brad Alexander <stor...@gmail.com> wrote: > I have an openvz container that I am having a hard time upgrading libc6. > Whether I use dpkg -i, apt-get, or aptitude, I get the same result. > > (Reading database ... 56136 files and directories c

Problem upgrading libc6 on sid

I have an openvz container that I am having a hard time upgrading libc6. Whether I use dpkg -i, apt-get, or aptitude, I get the same result. (Reading database ... 56136 files and directories currently installed.) Preparing to unpack .../archives/libc6_2.21-7_i386.deb ... Checking for services

Re: Problem with udev upgrading from wheezy to jessie

On Sunday 31 January 2016 17:35:46 Chris Bannister wrote: > On Thu, Jan 28, 2016 at 10:53:55AM +, Lisi Reisz wrote: > > Not quite. It still does need the sentence: > > "Please upgrade your kernel before or while upgrading udev." > > Perhaps even better: > &g

Re: Problem with udev upgrading from wheezy to jessie

On Thu, Jan 28, 2016 at 10:53:55AM +, Lisi Reisz wrote: > > Not quite. It still does need the sentence: > "Please upgrade your kernel before or while upgrading udev." > Perhaps even better: > "Please upgrade your kernel before upgrading udev." > to

Re: Problem with udev upgrading from wheezy to jessie

; > >> Please upgrade your kernel before or while upgrading udev. > > >> > > >> AT YOUR OWN RISK, you can force the installation of this version of udev > > >> WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM > > >> AT THE

Re: Problem with udev upgrading from wheezy to jessie

n 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote: > > > >> Please upgrade your kernel before or while upgrading udev. > > > >> > > > >> AT YOUR OWN RISK, you can force the installation of this version of > > > >> udev WHICH DOE

Re: Problem with udev upgrading from wheezy to jessie

> > Alternatively: > > Please upgrade your kernel before or after upgrading udev. This > version of udev will not work with the kernel you are using at > present. If you do not upgrade the kernel before rebooting it can > lead to an unbootable system. > >

Re: Problem with udev upgrading from wheezy to jessie

On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote: > > Please upgrade your kernel before or while upgrading udev. > > AT YOUR OWN RISK, you can force the installation of this version of udev > WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTE

Re: Problem with udev upgrading from wheezy to jessie

Chris Bannister wrote: > I don't know what it means by 'creating the /etc/udev/kernel-upgrade > file.' I'd check to see it it exists prior then after. I'd remove it if > the latter, e.g. I haven't got one in my system. if we read the OPs original post we would note that he's upgra

Re: Problem with udev upgrading from wheezy to jessie

r then after. I'd remove it if >> the latter, e.g. I haven't got one in my system. > >if we read the OPs original post we would note that he's upgrading from >wheezy to jessie, which is not recommended. he must first upgrade to >squeeze and then jessie. RTFM :) > >regards > >

Re: Problem with udev upgrading from wheezy to jessie

On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote: > Am 26.01.2016 um 11:08 schrieb Chris Bannister: > > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote: > >> > >> Please upgrade your kernel before or while upgrading udev. > >>

Re: Problem with udev upgrading from wheezy to jessie

Ps original post we would note that he's upgrading from > wheezy to jessie, which is not recommended. he must first upgrade to > squeeze and then jessie. RTFM :) it was my mistake - jessie follows wheezy - I apologize regards

Re: Problem with udev upgrading from wheezy to jessie

Charlie Kravetz wrote: > > If I am reading this list correctly, release sequence was Squeeze, > Wheezy, Jessie. That would make the upgrade wheezy to jessie correct. > Yes apologies - this should be something with the arm related kernel and udev versions. regards

Re: Problem with udev upgrading from wheezy to jessie

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 26 Jan 2016 22:34:25 +0100 deloptes wrote: >Charlie Kravetz wrote: > >> >> If I am reading this list correctly, release sequence was Squeeze, >> Wheezy, Jessie. That would make the upgrade wheezy to jessie correct. >>

Re: Problem with udev upgrading from wheezy to jessie

OOT, by creating the /etc/udev/kernel-upgrade file. "force" and "creating" are still somewhat dissociated from each other. The two ideas would be better expressed in two sentences. Alternatively: Please upgrade your kernel before or after upgrading udev. This version of

Re: Problem with udev upgrading from wheezy to jessie

ystem. > > if we read the OPs original post we would note that he's upgrading from > wheezy to jessie, which is not recommended. he must first upgrade to > squeeze and then jessie. RTFM :) 7 -> 6 -> 8 I think it is you who have had a slight aberration, deloptes. ;-) Lisi Sorry for erroneous off-list post.

Re: Problem with udev upgrading from wheezy to jessie

Lisi Reisz wrote: > > I think it is you who have had a slight aberration, deloptes. ;-) > > Lisi > > Sorry for erroneous off-list post. at least gmail seem to work better than yahoo

Re: Problem with udev upgrading from wheezy to jessie

On Tuesday 26 January 2016 10:08:35 Chris Bannister wrote: > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote: > > Please upgrade your kernel before or while upgrading udev. > > > > AT YOUR OWN RISK, you can force the installation of this version of udev &g

Re: Problem with udev upgrading from wheezy to jessie

Am 26.01.2016 um 11:08 schrieb Chris Bannister: > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote: >> >> Please upgrade your kernel before or while upgrading udev. >> >> AT YOUR OWN RISK, you can force the installation of this version of udev >> WHIC

Re: Problem with udev upgrading from wheezy to jessie

> install both at the same time? Are you kidding me?!

Re: Problem with udev upgrading from wheezy to jessie

n >>  the running kernel: >> >>  - inotify(2) (CONFIG_INOTIFY_USER) >>  - signalfd(2) (CONFIG_SIGNALFD) >>  - accept4(2) >>  - open_by_handle_at(2) (CONFIG_FHANDLE) >>  - timerfd_create(2) (CONFIG_TIMERFD) >>  - epoll_create(2) (CONFIG_EPOLL) >>

Re: Problem with udev upgrading from wheezy to jessie

Martin Hanson wrote: > Please upgrade your kernel before or while upgrading udev. install both at the same time?

Problem with udev upgrading from wheezy to jessie

ept4(2) - open_by_handle_at(2) (CONFIG_FHANDLE) - timerfd_create(2) (CONFIG_TIMERFD) - epoll_create(2) (CONFIG_EPOLL) Please upgrade your kernel before or while upgrading udev. AT YOUR OWN RISK, you can force the installation of this version of udev WHICH DOES NOT WORK WITH YOUR RUNNING

Re: Problem with udev upgrading from wheezy to jessie

elease 198, udev requires support for the following features in > the running kernel: > > - inotify(2)(CONFIG_INOTIFY_USER) > - signalfd(2) (CONFIG_SIGNALFD) > - accept4(2) > - open_by_handle_at(2) (CONFIG_FHANDLE) > - timerfd_create(2) (CONFIG_TIMERFD

Re: Problem with udev upgrading from wheezy to jessie

On Sunday 24 January 2016 21:50:35 Martin Hanson wrote: > > install both at the same time? > > Are you kidding me?! No. # aptitude install linux-image-whatever udev Lisi

Re: Upgrading Debian

On 9/14/2015 2:33 AM, Lisi Reisz wrote: I know. It took me a while to work out what he actually wanted with all the drama. ;-) People who come from Ubuntu don't understand about point releases. Since I don't know Ubuntu, I don't know what it is that they are thinking of. Lisi I do run

Re: Upgrading Debian

On Sun, Sep 13, 2015 at 11:12:42AM +0300, Jarle Aase wrote: > On 09/13/2015 10:57 AM, Himanshu Shekhar wrote: > > I just want to make sure again. How can one upgrade from one > > version of Debian to other without losing data or without > > formatiing the partition, simply as Ubuntu does. An

Re: Upgrading Debian

On Monday 14 September 2015 14:01:48 Chris Bannister wrote: > On Sun, Sep 13, 2015 at 11:12:42AM +0300, Jarle Aase wrote: > > On 09/13/2015 10:57 AM, Himanshu Shekhar wrote: > > > I just want to make sure again. How can one upgrade from one > > > version of Debian to other without losing data or

Re: Upgrading Debian

Quoting Himanshu Shekhar (irm2015...@iiita.ac.in): > I just want to make sure again. How can one upgrade from one version of Debian > to other without losing data or without formatiing the partition, simply as > Ubuntu does. The more times you ask, the more different answers you will receive. At

<    1   2   3   4   5   6   7   8   9   10   >