September 2012 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] Fwd: [systemd-devel] [ANNOUNCE] systemd 193 (jounal networking support)
by Frederic Crozat 28 Sep '12

28 Sep '12

Le vendredi 28 septembre 2012 à 11:09 +0200, Michael Schroeder a écrit : > On Fri, Sep 28, 2012 at 10:03:00AM +0100, Frederic Crozat wrote: > > Feel free to review my "work in progress" package in > > https://build.opensuse.org/package/show?package=systemd&project=home% > > 3Afcrozat%3Abranches%3ABase%3ASystem > > Ohhh, a %pretrans bash script. That can't work for initial installs, as > there is no bash. Basically all %pretrans scripts have to be written > … [View More]

2 1

[opensuse-factory] ARM Chip
by gm1mqe＠aol.com 27 Sep '12

27 Sep '12

I have noticed a number of messages talking about ARM chips. Is there an ARM version of linux and if so does it support the Raspberry Pi system. Thanks, Andy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Status: Distribution
by Stephan Kulow 26 Sep '12

26 Sep '12

Hi, I just commited kernel 3.6.0-rc7, so from now on I will only pick pieces to get a working Milestone0. Hopefully for next week. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Status: Factory
by Stephan Kulow 26 Sep '12

26 Sep '12

Hi, Please note that Mesa and XOrg were updated in factory and cause quite some fallout. Before that isn't sorted out, we can't take other packages. This was caused by some packages submitted by autosubmit and that didn't look that harmful. I talked with Stefan about it and we agreed that it's better to fix it in factory than to revert. Watch out. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

Re: /run/media/$USER (Re: [opensuse-factory] usb devices not showing in kde)
by "Stefan Brüns" 26 Sep '12

26 Sep '12

Am 09/21/12, schrieb Alin M Elena <alinm.elena(a)gmail.com>: > > I use Tumbleweed and lost auto-mounting although devices were recognized > > and announced sometime during 12.1, but it came back sometime between rc1 > > and rc2 and is still functioning as is expected (kde). > > just to be clear... the problem is not automount... I do not care and I do not > use it... the problem is that dolphin/device notifier do not present the usb > devices to be … [View More]mounted.... the system at lower level sees them: (the only > exotic thing on this machine is the fact I installed 12.2 with lxdm and them > duped to factory and then installed kde --all clean confings) > > [alin@abbaton:~]: udisksctl monitor > Monitoring the udisks daemon. Press Ctrl+C to exit. > 09:11:15.286: The udisks-daemon is running (name-owner :1.80). > 09:11:17.178: Removed /org/freedesktop/UDisks2/block_devices/sdc1 > 09:11:17.178: Removed /org/freedesktop/UDisks2/block_devices/sdc > 09:11:17.179: Removed > /org/freedesktop/UDisks2/drives/Kingmax_USB2_2e0_FlashDisk_4000000009261 > 09:11:23.517: Added > /org/freedesktop/UDisks2/drives/Kingmax_USB2_2e0_FlashDisk_4000000009261 > org.freedesktop.UDisks2.Drive: This is udisks *2*, but KDE might still be using udisk *1*. The lowest level on the KDE side where you can check easily is "solid-hardware list", it should list all kind of hardware, including devices found through solids backend for udisks, at least the backend itself should be listed, e.g.: $> solid-hardware list ... udi = '/org/freedesktop/UDisks' udi = '/org/freedesktop/UDisks/devices/sda' ... I do not know if the solid UDisks2 backend is already stable and which backend KDE in 12.2 is using. If it is still using UDisks1, it might just not be installed (UDisks1 and UDisks2 can be installed and running side by side, according to its author). Regards, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

10 13

[opensuse-factory] Xf86- packages give me a problem
by Constant Brouerius van Nidek 26 Sep '12

26 Sep '12

After today zypper dup I got a new xorg.x11-driver-video with 28 new Xf86- packages. My system did come to init 5 and only showed a blinking cursor. Did not seem to find the right X11 driver. System worked after reinstalling the old xorg.x11-driver-video. which got automatically rid of all 28 new drivers. I am using factory. -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.3 Milestone 0 (i586) Kernel: 3.5.0-1-desktop KDE Development Platform: 4.9.1 "release … [View More]

1 0

Re: /run/media/$USER (Re: [opensuse-factory] usb devices not showing in kde)
by "Stefan Brüns" 26 Sep '12

26 Sep '12

Am 09/26/12, schrieb Karl Eichwalder <ke(a)suse.de>: > Someone out there who know how you can use these tools without too much > pain from the command line? Hm, depends on what you want to achieve: 1. mount all SD cards 2. mount any USB storage when it becomes available 3. mount some storage with a known name/label For the last point, you can use one of the symlinks in /dev/disk/by-*. For the other ones, I think you have to write some script which either parses the output of --… [View More]

1 0

[opensuse-factory] Better support for third-party JREs
by Michal Vyskocil 25 Sep '12

25 Sep '12

Hallo all, from time to time I got the complaints from the users want to use our Java packages, but not the JVM itself. As Oracle retired the permission to distribute their own JVM, most of the users want to manually install the Oracle JVM instead of openjdk we distribute. In a past, we have changed a logic of alljava.sh, so it search for jvm in /usr/java/latest and /usr/java as well, so can setup the proper JAVA_HOME for third-party JVM. The next unsolved problem are dependencies. In a bug#… [View More]

14 68

[opensuse-factory] GStreamer dependencies change in Factory
by Dimstar / Dominique Leuenberger 25 Sep '12

25 Sep '12

Hi all, as announced earlier and as a dependency to GNOME 3.6, we submitted GStreamer 1.0 to Factory, as package name gstreamer. In the past, gstreamer-0_10 provided a virtual symbol gstreamer and gstreamer-0_10-devel provided gstreamer-devel. They were conveniance provides, which had to be removed, as they would; for obvious reasons clash with the actual package called gstreamer and gstreamer-devel. So, if you get a "Nothing provides gstreamer-devel" (which is currently possible, as … [View More]

1 0

[opensuse-factory] Why does OpenSuSE disabled the default of allowing multi-core use in Coreutils 'sort'??
by Linda Walsh 25 Sep '12

25 Sep '12

I wondered why I wasn't getting multi-cpu support in my sorts of >128k line files, even when I specified that it should use multiple threads. It seems SuSE adds a patch to set the max CPU's my machine has to 1, so no matter what I set in --parallel, it uses the smaller of (1, number I ask for). The default is to use min(available CPU's, number I ask for)... Yet the OSuSE version is hard-coded to disallow parallel usage. Could someone point me at the discussion in the archives as to why … [View More]

13 33

Re: [opensuse-factory] Re: What is the purpose of the systemd journal service?
by Frederic Crozat 25 Sep '12

25 Sep '12

Le mardi 25 septembre 2012 à 12:46 +0200, Andreas Jaeger a écrit : > On Tuesday, September 25, 2012 12:39:59 Stephan Kulow wrote: > > On 25.09.2012 11:42, Andreas Jaeger wrote: > > > On Thursday, September 20, 2012 21:51:35 Peter Czanik wrote: > > >> Hello, > > >> > > >> Before we all end up in flames, a hopefully not too biased view > > >> from > > >> syslog-ng upstream :-) > > >> > > >> … [View More]

1 0

[opensuse-factory] Releasing Milestone 0
by Stephan Kulow 25 Sep '12

25 Sep '12

Hi, I would like to start the 12.3 game for real. We have a new KDE a new Xorg stack - at least. I would like to add kernel 3.6 into the mix and then release Milestone 0 "last change to use sysvinit" :) After that we can go into OSC12 and discuss how to continue. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Access denied to bugzilla and running Factory day to day
by Catalin Iacob 24 Sep '12

24 Sep '12

Hello everybody, First a bit on my background: I've been running openSUSE for a year, and switched almost exclusively (have a 12.2 chroot that I only had to use once) to Factory on my home system for about 2 months now (too brave? until now it worked great). The plan was to run the lastest software, help by reporting bugs, learn more about packaging and OBS and maybe try to help with some SRs. So far this has worked great, I did all of the above except reporting bugs (I'm only affected by one … [View More]that I'll report soon). I do zypper dup every day, sometimes it complains about problems. If that happens I cancel the update and try again the next day, usually in at most a few days it gets into an upgradable state again. However, it's been a while since I get: Problem: marble-4.8.5-1.7.x86_64 requires marble-data = 4.8.5, but this requirement cannot be provided Looking at this, it seems plasma-addons stayed at 4.8.5 and it requires marble-4.8.5 which is gone. Why did plasma-addons stay at 4.8.5? Because SR [1] was declined by somebody in the legal team. The decline reason points to [2] where I get: You are not authorized to access bug #779736. That's not very nice, I'm now completely in the dark as to why plasma-addons wasn't upgraded and how long will it keep blocking the rest of my upgrade. I understand that the legal issues might be sensitive but I have a feeling this time they're not and I think it's bad to split the community into SUSE employees that can see everything and "the rest". Exactly at this point I want to postpone the upgrade anyway until the Xorg and Mesa issues Coolo pointed out get fixed (thanks for that by the way! very important for people testing day to day to avoid major breakage if it's already known) but the principle remains: everybody should be able to see why a SR got rejected to know what can be done about it to move forward. To summarize: * having some bugs available just to SUSE employees is in my opinion bad * what should happen to plasma-addons so that it gets upgraded to 4.9.1? * am I doing things correctly to stay on top of Factory? are others doing the same? is Factory meant to be used day to day if you have some troubleshooting and system recovery skills? * thanks for a great distribution, and a very stable development version of it, keep up the good work! [1] https://build.opensuse.org/request/show/133585 [2] https://bugzilla.novell.com/show_bug.cgi?id=779736 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

4 4

[opensuse-factory] New develprj: X11:RemoteDesktop:x2go
by Jan Engelhardt 24 Sep '12

24 Sep '12

As per http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory#How_to_add_a_n… , I am to propose here a new develprj. Dear Build Service maintainers, please tell me what to do next :) X11:RemoteDesktop:x2go already existed when I started my involvements in 2012-Feb. Is X:R:x2go acceptable as new develprj or should the packages be migrated to some other DP? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] Moving forward with systemd
by Cristian Rodríguez 24 Sep '12

24 Sep '12

Hi: Above, there is a list of tasks, which are "up for the grabs" after we completely remove the old sysvinit system from the distribution. * We have to remove ConsoleKit, ASAP. its functionality has been replaced by systemd logind, apparently is enough to build polkit with systemd support to achieve this goal. * build the kernel with CONFIG_AUDIT_LOGINUID_IMMUTABLE=yes (From these point on sysvinit waves his old arse goodbye) * See if acpid can be replaced by logind features … [View More]

14 24

Re: [opensuse-factory] [RFC] sysvinit: plan B
by Frederic Crozat 24 Sep '12

24 Sep '12

Le dimanche 23 septembre 2012 à 06:23 +0200, Jan Engelhardt a écrit : > On Friday 2012-09-07 15:43, Michal Vyskocil wrote > [http://lists.opensuse.org/opensuse-factory/2012-09/msg00396.html] > > > >Name: vsftpd-sysv > >Description: Sysvinit script for vsftpd > >Supplements: packagageand(sysvinit:vsftpd) > >Requires: sysvinit > >Requires: vsftpd > >Source0: vsftpd.init > > It would seem more advantageous to change the systemd package, and … [View More]

2 1

[opensuse-factory] New package submitted : apache2-mod_pagespeed
by Robert Munteanu 23 Sep '12

23 Sep '12

Hi, I've submitted sr#134135 [1] to Apache:Modules . mod_pagespeed [2] identifies improvements that can be made to web-sites to improve their latency in an Apache server. HTML, CSS, JavaScript, and images are changed dynamically during the web serving process, so that the best practices recommended by Page Speed can be used without having to change the way the web site is maintained. This apache module shares a common codebase with multiple Google products which are related to web site … [View More]

1 0

[opensuse-factory] libotr
by Nelson Marques 23 Sep '12

23 Sep '12

I'm submitting an update to libotr; anyone has contrainsts with updating it to 4.0.0 ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] help! axe off contributions from one of my projects
by Nelson Marques 23 Sep '12

23 Sep '12

People, I'm being flooded with emails from one of my projects because of SR's; Is there a way to prevent this project from not taking SR's? It's not that I don't like, it's just that __AT__ the current time, I have other plans :) NM -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] python2 or python3
by Alin M Elena 22 Sep '12

22 Sep '12

Hi, I see that the factory has both python2 and python3. Are there any plans about switching to python3 as default? I will also appreciate if the python maintainers can push=20 home:HighwayStar:branches:devel:languages:python python3-matplotlib Alin PS can we also, cripple kmail by default, or update the settings of our mailing list to accept html emails... It is bloody annoying to get your messages bounced back because of the default settings of the mail client. -- … [View More]

5 4

[opensuse-factory] usb devices not showing in kde
by Alin M Elena 21 Sep '12

21 Sep '12

Hi, I have a strange problem, all my usk storage devices do not show in kde's device notifier. I can see them fine with lsusb and mount them manually as root... but somehow I lost the nicety of easy click. any idea on what may cause it? I am tempted to blame policy-kit... but I do not have the proof. regards, Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research … [View More]

6 8

Re: Re: [opensuse-factory] Proposal for 12.3: Drop sysinit V
by Frederic Crozat 21 Sep '12

21 Sep '12

Le vendredi 21 septembre 2012 à 13:42 +0200, Jos Poortvliet a écrit : > On Thursday, September 20, 2012 16:16:36 Frederic Crozat wrote: > > Le jeudi 20 septembre 2012 à 10:11 -0500, Larry Finger a écrit : > > > On 09/20/2012 07:20 AM, Frederic Crozat wrote: > > > > Le lundi 03 septembre 2012 à 19:13 -0500, Larry Finger a écrit : > > > >> On 09/03/2012 10:21 AM, Dominique Leuenberger a.k.a DimStar wrote: > > > >>> Hi all, > > &… [View More]gt; >>> > > > >>> I know, a radical proposal, BUT a bunch of reported issues in 12.2 are > > > >>> around systemd/sysinitV, both trying to do the same thing, > > > >>> differently. > > > >>> > > > >>> It would clearly help the distribution to commit clearly to ONE init > > > >>> system > > > >>> only, officially and formally ditching the other. > > > >>> > > > >>> This allows for proper testing of ONE Init System and fixing issues > > > >>> around it. Not having to worry for an alternative INIT System can > > > >>> only have it's advantages. > > > >>> > > > >>> (Not saying NOBODY can keep on working / integrating SysInitV, just > > > >>> saying: the openSUSE Project should focus on SystemD as the one > > > >>> supported Init System). > > > >>> > > > >>> There are a bunch of issues we could have saved ourselves from by not > > > >>> going the split way. > > > >> > > > >> One defect in the 12.1 and 12.2 implementations is that after.local is > > > >> ignored. There is an easy fix given by James McDaniel in his blog at > > > >> http://forums.opensuse.org/blogs/comments/comment549.html. This file > > > >> should be a part of any update of systemd. > > > > > > > > after.local wasn't implemented initially because I wasn't aware of this > > > > "suse-ism" when I ensured systemd was usable on openSUSE for 12.1. > > > > > > > > The other big issue with after.local is relying on $ALL virtual target > > > > which is was not possible to implement easily with a dynamic service > > > > manager, like systemd (unlike insserv which is computing static > > > > dependencies before booting). Fortunately, systemd 185 (ie not the one > > > > in 12.2 but for next openSUSE release) have a new service type, called > > > > "idle", which will be used for getty (so tty will be started only after > > > > all services had chances to write their status report) and probably for > > > > halt.local. > > > > > > > > For systemd in 12.1 or 12.2, we can't add support for after.local > > > > reliably (and I would advise people to try to write more .service files > > > > instead, adding After=... to ensure action is started at the right > > > > moment). > > > > > > Frederic, > > > > > > Welcome back. I hope that your inbox did not undo the therapeutic benefits > > > of your holiday. > > > > > > Your advice for writing more .service files is obviously correct; however, > > > that may be too steep a learning curve for many users. For most of them, > > > the file in the link I posted earlier does what they need, and we now > > > know that the next version of openSUSE will have a systemd that will > > > allow something that is akin to after.local on SystemV. > > > > Well, I re-read the after-local.service file from forum and chances are > > very high it won't do what people are expecting: it will indeed > > start /etc/init.d/after.local but it will be started at any time during > > the boot and not after all other services are started (which is what > > people are expected).. > > That's really something to find a solution for, then. Adding simple things to > this script is something 'normal' users can do and figure out (and they do). > Increasing the barrier to such things is imho bad - we've got quite a number > of users, I bet, who are on this level of proficiency with openSUSE: able to > add or remove a line to/from a shell script but not write stuff themselves. I > admittedly fall (mostly) in that category myself. As I explained in another reply in this huge thread, we should be able to handle after.local properly for 12.3 but for 12.2 (or to call after.local will probably not do what people are expecting.. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

1 0

Re: [opensuse-factory] Proposal for 12.3: Drop sysinit V
by Frederic Crozat 21 Sep '12

21 Sep '12

Le jeudi 20 septembre 2012 à 10:11 -0500, Larry Finger a écrit : > On 09/20/2012 07:20 AM, Frederic Crozat wrote: > > Le lundi 03 septembre 2012 à 19:13 -0500, Larry Finger a écrit : > >> On 09/03/2012 10:21 AM, Dominique Leuenberger a.k.a DimStar wrote: > >>> Hi all, > >>> > >>> I know, a radical proposal, BUT a bunch of reported issues in 12.2 are around > >>> systemd/sysinitV, both trying to do the same thing, differently. … [View More]> >>> > >>> It would clearly help the distribution to commit clearly to ONE init system > >>> only, officially and formally ditching the other. > >>> > >>> This allows for proper testing of ONE Init System and fixing issues around it. > >>> Not having to worry for an alternative INIT System can only have it's advantages. > >>> > >>> (Not saying NOBODY can keep on working / integrating SysInitV, just saying: the > >>> openSUSE Project should focus on SystemD as the one supported Init System). > >>> > >>> There are a bunch of issues we could have saved ourselves from by not going the > >>> split way. > >> > >> One defect in the 12.1 and 12.2 implementations is that after.local is ignored. > >> There is an easy fix given by James McDaniel in his blog at > >> http://forums.opensuse.org/blogs/comments/comment549.html. This file should be a > >> part of any update of systemd. > > > > after.local wasn't implemented initially because I wasn't aware of this > > "suse-ism" when I ensured systemd was usable on openSUSE for 12.1. > > > > The other big issue with after.local is relying on $ALL virtual target > > which is was not possible to implement easily with a dynamic service > > manager, like systemd (unlike insserv which is computing static > > dependencies before booting). Fortunately, systemd 185 (ie not the one > > in 12.2 but for next openSUSE release) have a new service type, called > > "idle", which will be used for getty (so tty will be started only after > > all services had chances to write their status report) and probably for > > halt.local. > > > > For systemd in 12.1 or 12.2, we can't add support for after.local > > reliably (and I would advise people to try to write more .service files > > instead, adding After=... to ensure action is started at the right > > moment). > > Frederic, > > Welcome back. I hope that your inbox did not undo the therapeutic benefits of > your holiday. > > Your advice for writing more .service files is obviously correct; however, that > may be too steep a learning curve for many users. For most of them, the file in > the link I posted earlier does what they need, and we now know that the next > version of openSUSE will have a systemd that will allow something that is akin > to after.local on SystemV. Well, I re-read the after-local.service file from forum and chances are very high it won't do what people are expecting: it will indeed start /etc/init.d/after.local but it will be started at any time during the boot and not after all other services are started (which is what people are expected).. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

2 1

[opensuse-factory] Fwd: [systemd-devel] [HEADS-UP] Early-boot SysV service support is going away
by Cristian Rodríguez 20 Sep '12

20 Sep '12

-------- Original Message -------- Subject: [systemd-devel] [HEADS-UP] Early-boot SysV service support is going away Date: Tue, 18 Sep 2012 00:59:26 +0200 From: Lennart Poettering <lennart(a)poettering.net> Organization: Red Hat, Inc. To: systemd Mailing List <systemd-devel(a)lists.freedesktop.org> Heya, In a month or two we'll make the SysV service logic in systemd generator-based. This helps us clean up our codebase a bit and makes SysV service support an optional plugin rather … [View More]than something that is built into PID1. Effectively, by doing this move very little will change in behaviour for SysV scripts, with one exception however: we will remove support for early-boot SysV scripts. Early-boot SysV scripts are those for the special "S", "boot", or "b" runlevel that exist on some distributions. These runlevels are highly distro specific, have never been really standardized and are really cumbersome to support right now with a lot of per-distribution hacks. Please do not misunderstand this: it's one thing supporting normal SysV scripts, it's another one supporting them in the early boot part of the things. The former is going to stay for a long time, the latter however is going to be removed in a couple of month. Anyway, this is basically just a heads-up about this, so that you folks who still need this can think about good solutions what to do instead. Here's what I can propose: a) port the early-boot init scripts to native systemd units. You probably should do that anyway, and in most cases there should be very little left that systemd doesn't do on its own anyway in the early-boot process. We recommend to go this way, of course. or b) Try to forward-port support for these magic runlvels to what's coming. Probably a lot of work, since due to the conversion to a generator this is a lot more work than it might appear right now. The code structure of the sysv logic will change quite substantially. or c) write an explicit generator for these services, in the specific syntax of your distro. Anyway, please think about it, we'd just like to make you aware of this in time. At least Debian, Suse, Ubuntu, Angstrom appear to be candidates where this lost functionality might be noticable. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel(a)lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

2 1

[opensuse-factory] Proposal for 12.3: Drop sysinit V
by Dominique Leuenberger a.k.a DimStar 20 Sep '12

20 Sep '12

Hi all, I know, a radical proposal, BUT a bunch of reported issues in 12.2 are around systemd/sysinitV, both trying to do the same thing, differently. It would clearly help the distribution to commit clearly to ONE init system only, officially and formally ditching the other. This allows for proper testing of ONE Init System and fixing issues around it. Not having to worry for an alternative INIT System can only have it's advantages. (Not saying NOBODY can keep on working / … [View More]

51 291