Oliver Grawert [2015-08-17 15:24 +0200]:
> if you need to prevent an upstart service from starting on boot you need
> to create a .override files containing the word "manual", as described
> in your askubuntu links. i dont think there exists a tool to do that for
> you (and such a tool would be qui
On Mon, 17 Aug 2015 18:37:04 +0200, Oliver Grawert wrote:
>i havent called anything transparent, you have called "the boot process
>a mess" and pointed to pointless proof
I was speaking about transparency and I called the absence of
transparency a mess. Your claim is, that it isn't a mess, so the
Am Montag, den 17.08.2015, 18:13 +0200 schrieb Ralf Mardorf:
> On Mon, 17 Aug 2015 17:32:42 +0200, Oliver Grawert wrote:
> >unfounded FUD
>
> What next?
>
> Actually everything I pointed out is correct, it's not unfounded FUD.
> Even you mentioned that not all services are ported over.
neither t
hi,
Am Montag, den 17.08.2015, 12:05 -0400 schrieb Luis Mondesi:
> A chkconfig like tool is needed, even if it's overkill.
what is wrong with using upstreams systemctl to manage services ?
this is what systemd upstream proposes and what is used in ubuntu and
debian (and hopefully everywhere els
On Mon, 17 Aug 2015 17:32:42 +0200, Oliver Grawert wrote:
>unfounded FUD
What next?
Actually everything I pointed out is correct, it's not unfounded FUD.
Even you mentioned that not all services are ported over.
It's not that hard for me to make a profound comparison between an Arch
Linux instal
> Hi Luis,
>
> I strongly disagree.
>
> For my everyday production environment I run Arch Linux since February
> 2012 with a clean systemd.
>
> This year in July I installed Wily from the server ISO on this
> multi-boot machine. What I got wasn't a "Full Systemd Experience", but
> a mess with in
Am Montag, den 17.08.2015, 17:20 +0200 schrieb Ralf Mardorf:
> On Mon, 17 Aug 2015 17:03:02 +0200, Oliver Grawert wrote:
> >ubuntus upstream is debian in this case ...
>
> ... but systemd's upstream is _not_ Debian.
no, but you blame ubuntu for technical debian decisions here ...
martin pitt and
Thanks Oli, it works OK with:
$ cat /etc/init/modemmanager.override
start on starting dbus
stop on stopped dbus
I think network-manager is only needed if you want to establish an
Internet connection over the HSDPA modem or so.
In this case I only use it to send SMS, etc. so I don't need netwo
On Mon, 17 Aug 2015 17:03:02 +0200, Oliver Grawert wrote:
>ubuntus upstream is debian in this case ...
... but systemd's upstream is _not_ Debian.
I already wrote:
>>it's off topic and we don't need to discuss it.
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify
hi,
Am Montag, den 17.08.2015, 16:46 +0200 schrieb Ralf Mardorf:
> On Mon, 17 Aug 2015 15:56:34 +0200, Oliver Grawert wrote:
> >hi,
> >Am Montag, den 17.08.2015, 15:41 +0200 schrieb Ralf Mardorf:
> >
> >> Btw. I'm still not used to systemd after using it for around 3 years,
> >> but for my workfl
On Mon, 17 Aug 2015 15:56:34 +0200, Oliver Grawert wrote:
>hi,
>Am Montag, den 17.08.2015, 15:41 +0200 schrieb Ralf Mardorf:
>
>> Btw. I'm still not used to systemd after using it for around 3 years,
>> but for my workflow a clean systemd at least is easier to handle,
>> than the Wily hybrid.
>>
hi,
Am Montag, den 17.08.2015, 15:36 +0100 schrieb João M. S. Silva:
> Yes, it is:
>
> $ dpkg -l|grep network-manager
> $ dpkg -l|grep modemmanager
> ii modemmanager1.0.0-2ubuntu1
> amd64D-Bus service for managing modems
>
> Thanks Oli, that sounds reasonabl
Yes, it is:
$ dpkg -l|grep network-manager
$ dpkg -l|grep modemmanager
ii modemmanager1.0.0-2ubuntu1
amd64D-Bus service for managing modems
Thanks Oli, that sounds reasonable. I tried it but:
$ service modemmanager status
modemmanager stop/waiting
$ dmesg
On Mon, 17 Aug 2015 08:47:33 -0500, Jamie Strandboge wrote:
>On 08/14/2015 10:07 PM, Ralf Mardorf wrote:
>> On Sat, 15 Aug 2015 01:33:46 +0100, João M. S. Silva wrote:
>>> On 08/15/2015 01:12 AM, Ralf Mardorf wrote:
As already pointed out, the drive in question is _sdc_, not _sdb_
>>>
>>> Wha
Am Montag, den 17.08.2015, 14:56 +0100 schrieb João M. S. Silva:
> The specific problem here is that modemmanager depends on network-manager:
>
> $ cat /etc/init/modemmanager.conf
> (...)
> start on starting network-manager
> stop on stopped network-manager
> (...)
>
> But I don't need network-ma
Hello everyone,
Could someone offer help in the transition to libimobiledevice 1.2.0?
The SONAME changes during the sync.
https://bugs.launchpad.net/bugs/1485347
I can't help as I don't have any development or packaging knowledge.
libimobiledevice 1.2.0 has proper iOS 8 support that is p
The specific problem here is that modemmanager depends on network-manager:
$ cat /etc/init/modemmanager.conf
(...)
start on starting network-manager
stop on stopped network-manager
(...)
But I don't need network-manager and all of its dependencies on this server.
I'd just like to start modemman
hi,
Am Montag, den 17.08.2015, 15:41 +0200 schrieb Ralf Mardorf:
> Btw. I'm still not used to systemd after using it for around 3 years,
> but for my workflow a clean systemd at least is easier to handle, than
> the Wily hybrid.
>
> You might get used to the Wily hybrid systemd within 30 seconds,
On 08/14/2015 10:07 PM, Ralf Mardorf wrote:
> On Sat, 15 Aug 2015 01:33:46 +0100, João M. S. Silva wrote:
>> On 08/15/2015 01:12 AM, Ralf Mardorf wrote:
>>> As already pointed out, the drive in question is _sdc_, not _sdb_
>>
>> What about kworker?
>
> I wonder, if AppArmor or any of the other so
On Mon, 17 Aug 2015 08:43:50 -0400, Luis Mondesi wrote:
>When you do a clean install of 15.10 you get the Full Systemd
>Experience ™ It's very awkward for the first 30 seconds or so, but one
>gets used to its quirks very fast.
>
>Cannot really complaint about it. Just continue on...
Hi Luis,
I s
Am Montag, den 17.08.2015, 12:38 +0100 schrieb João M. S. Silva:
> does it mean I'm not using systemd? I don't seem to have systemd
> installed (Ubuntu 14.04.3 LTS).
update-rc.d and invoke-rc.d are tools for package maintainers only (to
be used from pre/postinst scripts) and only applies to sysv
> [root@moonstudio ~]# ls -l /bin/systemd /sbin/upstart
> ls: cannot access /sbin/upstart: No such file or directory
> lrwxrwxrwx 1 root root 20 Aug 12 16:58 /bin/systemd -> /lib/systemd/systemd
>
> FWIW even for 15.10 it's a hybrid, not a clean systemd.
When you do a clean install of 15.10 you
On Mon, 17 Aug 2015 12:38:35 +0100, João M. S. Silva wrote:
>does it mean I'm not using systemd? I don't seem to have systemd
>installed (Ubuntu 14.04.3 LTS).
AFAIK systemd is default for 15.04 and 15.10 only.
[root@moonstudio ~]# dpkg -s systemd | grep -A1 Installing
Installing the systemd pac
On 08/15/2015 09:02 AM, Tom H wrote:
If you're using systemd, you should be able to use
update-rc.d service enable
update-rc.d service disable
as in Debian
Since I get:
$ update-rc.d modemmanager enable
update-rc.d: /etc/init.d/modemmanager: file does not exist
does it mean I'm not using syst
24 matches
Mail list logo
