Hi all!
I am following devuan since it has started (also with a little contribution)
talking about it the distributions based on devuan to my friends and at work.
So, first of all: thanks!
Now, it is the time for me to migrate my system from wheezy to devuan,
so I need some info and advices...
Just for the record...
I did a standard system install of wheezy on encrypted lvm, then added
xorg and xfce4 (full metapackages) and not much else.
Changed sources to devuan jessie and added the avoid-systemd pin, ran
'apt-get update' and added the devuan keyring, then ran 'apt-get
dist-upgrade'
On my wheezy pulseaudio wants:
libsystemd-daemon0 (= 31), libsystemd-login0 (= 31)
If i had some time i would change to jack...
Possibly it would be a boost for the jack development if we make it
standard in Devuan?
Well, before we overreact- if the package has been depreciated, we
On Tue, Jan 06, 2015 at 03:32:34PM +, t.j.duch...@gmail.com wrote:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773924
Wow! Thanks, Oli.
That’s very informative and much appreciated. It looks like we could simply
rebuild the package without the dependency, if I am reading
Then I have no idea about default installation (you can probably look at
package dependencies to figure it out). But from Debian's current POV, it is
probably considered an improvement to add systemd components and more
recent versios of __ that use them, even if PID1 is still sysvinit. After
I recently unintentionally installed systemd and a bunch of the related
tentacles.
It was a new Wheezy install w/XFCE from a DVD I figured I'd be safe from
systemd with wheezy, but for some hardware (AMD A10-7850K Kaveri) I
needed a newer kernel and so I enabled backports.
I obviously was
Hi, Clarke!
It was a bit of a wake up call for me as it made me realize that for
more recent hardware continued use of Wheezy to avoid systemd may not be
as simple as it first seems.
You can get around that. Systemd is not a kernel requirement. You can easily
get around said problems by
Thank you, Hendrik.
That is what I assumed you would find. I’m not overreacting per se. I freely
admit, I’ve not looked at the code to see how well it functions independently.
I also do not know for certain that it is a recent addition. I do not recall
seeing it in previous Wheezy releases
On 2015-01-05
T.J. Duchene t.j.duch...@gmail.com wrote:
I was installing wheezy this morning on a second hard drive and I noted
that systemd named packages have crept their way into the wheezy default
installs. I'm presuming that they are compatibly named or part of a
systemd/system 5 shim
https://packages.debian.org/wheezy/systemd
---
fr33domlover http://www.rel4tion.org/people/fr33domlover
GPG key ID: 63E5E57D (size: 4096)
GPG key fingerprint: 6FEE C222 7323 EF85 A49D 5487 5252 C5C8 63E5 E57D
signature.asc
Description: PGP signature
I was installing wheezy this morning on a second hard drive and I noted
that systemd named packages have crept their way into the wheezy default
installs. I'm presuming that they are compatibly named or part of a
systemd/system 5 shim since systemd is not actually running. I'm guessing
they did
IIRC, Wheezy is known to have systemd packages but they aren't (or shouldn't
be?) installed by default, probably as an early preparation for full systemd in
Jessie.
Yes, I know.
As I’ve said before I have no problem with systemd, except on mission critical
servers. My concern is that
My concern is that Debian is backporting code to the Wheezy release that
they shouldn’t be installing by default
I should say “might be” as I am not sure and have not looked at the code
personally. I am merely concerned.
From: t.j.duch...@gmail.com
Sent: Monday, January 5,
13 matches
Mail list logo
