Bug#761938: closed by m...@linux.it (Marco d'Itri) (Re: Bug#761938: please stop breaking my system with systemd)

2014-09-17 Thread Gianluigi Tiesi

On 09/17/14 16:39, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the systemd package:

#761938: please stop breaking my system with systemd

It has been closed by m...@linux.it (Marco d'Itri).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact m...@linux.it (Marco 
d'Itri) by
replying to this email.




currently it is a real bug report, udev does not wait enough for 
devices, I don't have more information because it scroll so fast and 
adding debug to commandline it's enough to make the bug not reproducible.


I will sure not be the only one with this problem.

Please do not close the bug report just because you don't agree with me

systemd is really broken in many place

--
Gianluigi Tiesi sher...@netfarm.it
EDP Project Leader
Netfarm S.r.l. - http://www.netfarm.it/
Free Software: http://oss.netfarm.it/

Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#761938: please stop breaking my system with systemd

2014-09-16 Thread Gianluigi Tiesi
Package: systemd
Severity: important

I've updated to systemd/udev 215-4, my system starts with a read-only
root, it has something to do with udev, mounting rw via kernel commandline,
or when a disk check occurs, workarounds the problem,
looks like a timing problem, but wait...
I'm unable to read the error because systemd is
SO BLAZING FAST!

really people, systemd and init scripts of many packages aren't just
ready for production.

I've rebuilt policykit removing systemd deps and my system magically
starts without any problems

and also:
- smartd daemon silently exits instead of starting
- transmission-daemon crashes
- I spin down my sdb disk, why hell it starts again at shutdown now?

If you want to play with systemd, just do it, but leave us an alternative,
please tell policykit maintainer to stop nazi mind and keep a non systemd
infected policykit.

Please stop this crazyness of forcing a non production-ready init system
or we'll just sit with pop-corn on jessie release wathing bug report storm.

Regards


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org