On Wed 15 Jan 2020 at 08:08:30 -0800, Alan Savage wrote:
> I am trying to upgrade from stretch to buster using the nonfree
> installation DVD ISO "firmware-10.2.0-amd64-DVD-1.iso" that I downloaded
> using the torrent here:
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firm
Escaped from gnome. While working in gnome the visibility of my mouse
pointer became very erratic, often visible only at the margins of a
window. I would then have to move the mouse and guess where it pointed
in the window. The computer was all but unusable so I rebooted. Having
been schooled i
On Wed 18 Sep 2019 at 12:06:00 (-), Curt wrote:
> On 2019-09-17, Sven Joachim wrote:
> > On 2019-09-17 11:10 -0500, David Wright wrote:
> >>
> >> Well, the only link *needed* is init, hence its dependency on package
> >> init, whose sole function is to keep the number of init configurations
>
On 2019-09-17, Sven Joachim wrote:
> On 2019-09-17 11:10 -0500, David Wright wrote:
>
>>
>> Well, the only link *needed* is init, hence its dependency on package
>> init, whose sole function is to keep the number of init configurations
>> more than zero and less than two.
>>
>> The rest of those l
On Tue, Sep 17, 2019 at 05:06:52PM -0400, Greg Wooledge wrote:
[...]
> I can't believe people are still adding cruft to sysv-rc helpers in 2019.
Luckily, "real world" is much more colourful and diverse than your
(or my -- or anyone's!) beliefs ;-)
Cheers
-- tomás
signature.asc
Description: Di
On Tue, Sep 17, 2019 at 10:59:53PM +0200, Sven Joachim wrote:
> On 2019-09-17 09:13 -0400, Greg Wooledge wrote:
> > wooledg:~$ aptitude why systemd-sysv
> > i udev Depends dpkg (>= 1.19.3) | systemd-sysv
> >
> > OK... I'll admit, I do not quite understand that dependency.
>
> The udev init scrip
On 2019-09-17 09:13 -0400, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
>> What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite understand that dep
On 2019-09-17 11:10 -0500, David Wright wrote:
>
> Well, the only link *needed* is init, hence its dependency on package
> init, whose sole function is to keep the number of init configurations
> more than zero and less than two.
>
> The rest of those links just mean that I can read, say, a 60 lin
On Tue 17 Sep 2019 at 13:29:16 -0400, Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 06:25:05PM +0100, Brian wrote:
> > Upgrades from wheezy to jessie did not change the init system because
> > libpame-systemd had the dependency
> >
> > systemd-shim (>= 8-2) | systemd-sysv
>
> https://www.debi
On Tue, Sep 17, 2019 at 06:25:05PM +0100, Brian wrote:
> Upgrades from wheezy to jessie did not change the init system because
> libpame-systemd had the dependency
>
> systemd-shim (>= 8-2) | systemd-sysv
https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html#issues-sys
On Tue 17 Sep 2019 at 09:13:30 -0400, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
> > What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite under
On Tue 17 Sep 2019 at 10:37:15 +0100, Brian wrote:
> On Sun 15 Sep 2019 at 23:31:23 +0100, Roger Lynn wrote:
>
> > I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> > running KDE and a headless server. Is there any information available
> > anywhere to tell me what will ha
On Tue 17 Sep 2019 at 09:45:21 (-0400), Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
> > I believe its name was chosen with
> > insufficient consideration, and is not in fact derived from its
> > function.
>
> You're not looking closely enough.
>
> > $ apt-
On 2019-09-17, The Wanderer wrote:
>>> Yes, but unless I'm greatly misunderstanding matters, /sbin/init is
>>> not specific to sysvinit.
>> That's okay, as I never came close to claiming it was. But you focus
>> uniquely upon this "point," while ignoring the part about the "links
>> needed for s
On 2019-09-17 at 09:45, Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
>
>> I believe its name was chosen with
>> insufficient consideration, and is not in fact derived from its
>> function.
>
> You're not looking closely enough.
>
>> $ apt-file show systemd
On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
> I believe its name was chosen with
> insufficient consideration, and is not in fact derived from its
> function.
You're not looking closely enough.
> $ apt-file show systemd-sysv
> systemd-sysv: /sbin/halt
> systemd-sysv: /sbin/init
On 2019-09-17 at 09:28, Curt wrote:
> On 2019-09-17, The Wanderer wrote:
>
>>> Why he would say "despite its name" eludes this correspondent,
>>> because the package has *everything* to do with sysvinit,
>>> providing as it does the "links needed for systemd to replace
>>> sysvinit. Installing
On 2019-09-17, The Wanderer wrote:
>> Why he would say "despite its name" eludes this correspondent,
>> because the package has *everything* to do with sysvinit, providing
>> as it does the "links needed for systemd to replace sysvinit.
>> Installing systemd-sysv will overwrite /sbin/init with a
On 2019-09-17 at 09:13, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
>
>> What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite understand that de
On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
> What causes systemd-sysv to be installed?
wooledg:~$ aptitude why systemd-sysv
i udev Depends dpkg (>= 1.19.3) | systemd-sysv
OK... I'll admit, I do not quite understand that dependency. But
what I really need to do is check this on a je
On 2019-09-17 at 04:09, Curt wrote:
> On 2019-09-16, Brian wrote:
[that on some earlier date which has been clipped out, someone else -
who happens to be The Wanderer - wrote:]
>>> The dist-upgrade will have resulted in installing the
>>> systemd-sysv package, which (despite its name) has nothi
On Sun 15 Sep 2019 at 23:31:23 +0100, Roger Lynn wrote:
> I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> running KDE and a headless server. Is there any information available
> anywhere to tell me what will happen when I attempt to upgrade them to
> Buster? The release n
On 2019-09-16, Brian wrote:
>>
>> The dist-upgrade will have resulted in installing the systemd-sysv
>> package, which (despite its name) has nothing to do with sysvinit; it is
>> the package which sets systemd as the primary / active / default init
>> system.
>>
>> Installing sysvinit-core will
On Mon, Sep 16, 2019 at 3:17 PM The Wanderer wrote:
> >> If you want to keep sysvinit, here's the order of events:
> >>
> >> change sources from stretch to buster
> >
> > Fine.
> >
> >> apt update
> >
> > Splendid.
> >
> >> apt dist-upgrade
> >
> > Great.
> >
> >> apt install sysvinit-core
> >
Quoting Brian (2019-09-17 00:11:33)
> On Mon 16 Sep 2019 at 15:16:34 -0400, The Wanderer wrote:
>
> > On 2019-09-16 at 15:07, Brian wrote:
> >
> > > On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
> > >
> > >> Roger Lynn wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> I have three Stretch AM
On 2019-09-16 at 18:11, Brian wrote:
> On Mon 16 Sep 2019 at 15:16:34 -0400, The Wanderer wrote:
>
>> On 2019-09-16 at 15:07, Brian wrote:
>>
>>> On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
apt install sysvinit-core
>>>
>>> What happens if this is not done?
>>
>> Next time yo
On Mon 16 Sep 2019 at 15:16:34 -0400, The Wanderer wrote:
> On 2019-09-16 at 15:07, Brian wrote:
>
> > On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
> >
> >> Roger Lynn wrote:
> >>
> >>> Hi,
> >>>
> >>> I have three Stretch AMD64 systems with sysvinit - a desktop and
> >>> laptop run
On 2019-09-16 at 15:07, Brian wrote:
> On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
>
>> Roger Lynn wrote:
>>
>>> Hi,
>>>
>>> I have three Stretch AMD64 systems with sysvinit - a desktop and
>>> laptop running KDE and a headless server. Is there any
>>> information available anywhere
On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
> Roger Lynn wrote:
> > Hi,
> >
> > I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> > running KDE and a headless server. Is there any information available
> > anywhere to tell me what will happen when I attempt to
Quoting Dan Ritter (2019-09-16 03:52:50)
> Roger Lynn wrote:
> > The KDE systems have systemd-shim installed, which is not present in
> > Buster. Is this going to cause problems? Will the server be okay?
> > Should I just stay with Stretch until Bullseye is released or
> > consider moving to De
Roger Lynn wrote:
> Hi,
>
> I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> running KDE and a headless server. Is there any information available
> anywhere to tell me what will happen when I attempt to upgrade them to
> Buster? The release notes don't mention it and oth
Keith Bainbridge
keithr...@gmail.com
+61 (0)447 667 468
On 10/2/19 10:43 am, Richard Hector wrote:
On 10/02/19 12:01 PM, deloptes wrote:
Normally, I wouldn't bother since I usually only upgrade every other
release after LTS ceases on my primary install. But this time, Buster
includes supp
Hi Paul,
> Updated from Stretch to Buster (non-free) the other day all went fine, just
> undertaken
>
> apt update && apt upgrade
>
> today and all seem to go fine, The process seems to be pretty painless for
> the most part.
I do hope you did
apt dist-upgrade
too. ;-)
Bonno Bloksma
On Sun, 10 Feb 2019 00:01:47 +0100
deloptes wrote:
> Patrick Bartek wrote:
>
> > As for me, I'm the patient, very practical type. Debian is my distro
> > of choice after almost 20 years of using other Linuxes because of its
> > philosophy of stability and bug-freeness above all else. I'll wait
The freeze for buster will happen according to the following timeline:
* 2019-01-12 - Transition freeze
* 2019-02-12 - Soft-freeze
* 2019-03-12 - Full-freeze
via https://release.debian.org/buster/freeze_policy.html
On 2/9/19 3:01 PM, deloptes wrote:
Patrick Bartek wrote:
As for me, I'm
On 10/02/19 12:01 PM, deloptes wrote:
>> Normally, I wouldn't bother since I usually only upgrade every other
>> release after LTS ceases on my primary install. But this time, Buster
>> includes support for AMD's Ryzen APU series which a notebook I'm
>> considering purchasing around summertime use
Patrick Bartek wrote:
> As for me, I'm the patient, very practical type. Debian is my distro
> of choice after almost 20 years of using other Linuxes because of its
> philosophy of stability and bug-freeness above all else. I'll wait
> until Buster is in Release Candidate status before testing it
OP, are you on x86? amd64?
Cheers!
--
Boyan Penkov
www.boyanpenkov.com
> On Feb 9, 2019, at 16:29, Patrick Bartek wrote:
>
> On Sat, 9 Feb 2019 07:48:00 +
> Paul Sutton wrote:
>
>> On 09/02/2019 02:22, Peter Ehlert wrote:
>>>
>>> On 2/8/19 11:09 AM, Patrick Bartek wrote:
On Fri,
On Sat, 9 Feb 2019 07:48:00 +
Paul Sutton wrote:
> On 09/02/2019 02:22, Peter Ehlert wrote:
> >
> > On 2/8/19 11:09 AM, Patrick Bartek wrote:
> >> On Fri, 8 Feb 2019 15:06:34 +
> >> Paul Sutton wrote:
> >>
> >>> Updated from Stretch to Buster (non-free) the other day all went fine,
>
On 09/02/2019 02:22, Peter Ehlert wrote:
>
> On 2/8/19 11:09 AM, Patrick Bartek wrote:
>> On Fri, 8 Feb 2019 15:06:34 +
>> Paul Sutton wrote:
>>
>>> Updated from Stretch to Buster (non-free) the other day all went fine,
>>> just undertaken
>> Why? Buster is still alpha. A lot can still go
On 2/8/19 11:09 AM, Patrick Bartek wrote:
On Fri, 8 Feb 2019 15:06:34 +
Paul Sutton wrote:
Updated from Stretch to Buster (non-free) the other day all went fine,
just undertaken
Why? Buster is still alpha. A lot can still go wrong. Hope it's not
your primary use distro.
Why?: 1. mig
On Fri, 8 Feb 2019 15:06:34 +
Paul Sutton wrote:
> Updated from Stretch to Buster (non-free) the other day all went fine,
> just undertaken
Why? Buster is still alpha. A lot can still go wrong. Hope it's not
your primary use distro.
> apt update && apt upgrade
With testing, dist-upgrad
I did the same on a test install, a couple times. (mate desktop)
The first try failed, I forgot to also edit the
/etc/apt/sources.list.d/base.list
the second worked quite well.
I am a bit nervous about updating my daily drivers.
On 2/8/19 7:06 AM, Paul Sutton wrote:
Hi
Updated from Stretch t
On 2/8/19 8:06 AM, Paul Sutton wrote:
> Hi
>
> Updated from Stretch to Buster (non-free) the other day all went fine,
> just undertaken
>
> apt update && apt upgrade
>
> today and all seem to go fine, The process seems to be pretty painless
> for the most part.
>
> Paul
>
>
That's good to
44 matches
Mail list logo
