Announcement

Collapse
No announcement yet.

Using Udev Without Systemd Is Going To Become Harder

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • liam
    replied
    Originally posted by pgoetz View Post
    The argument was that they share a lot of code which then had be be maintained in two different places.
    Don't get your hopes up as there's many ways this could turn out but:

    https://lists.fedoraproject.org/pipe...st/201954.html

    Read the whole thread for context, but, in brief, there's a problem with systemd requiring certain services to be run that aren't needed in a containerized runtime.

    Leave a comment:


  • pgoetz
    replied
    Originally posted by tpruzina View Post
    I have always hated the fact that udev was merged with systemd (there never really was any rational reason apart from systemd being dependant on it).

    The argument was that they share a lot of code which then had be be maintained in two different places.

    Leave a comment:


  • tomegun
    replied
    Originally posted by mike4 View Post
    My pedals are still dead since yesterday. Now I don't think that it's even possible to create such a bug. Probably the autor got money from M$, Apple or alike to
    keep input devices buggy for the next 10 years.-
    Yeah, that's most likely what happened.

    I suggest you take your complaints to the appropriate venue though, as it is getting really annoying to read about your pedals all the time in tese unrelated threads.

    That said, you would probably be better off moving back to windows, as these people are clearly in the pockets of M$ and Apple, so I'm sure they would not fix your bug.

    Leave a comment:


  • mike4
    replied
    My pedals are still dead since yesterday. Now I don't think that it's even possible to create such a bug. Probably the autor got money from M$, Apple or alike to
    keep input devices buggy for the next 10 years.-

    Leave a comment:


  • Luke
    replied
    Bug reports are needed, but so is bug discussion.

    Originally posted by Vim_User View Post
    You can not claim to have no time to properly report a bug to the appropriate projects, when a) the bug is about a gaming device, play a bit less, report a bit more, and b) it seems that you have plenty of time to sput about that bug on Phoronix.

    It will not happen for me because:
    - I know that Phoronix is not the appropriate place to report bugs.
    - I know that bugs that don't get reported usually won't get fixed.
    - I know that proposals like "When this isn't be fixed I am going back to Windows" are nothing more than poor attempts to force someone to work on the issue, providing evidence of too much self importance.
    Phoronix is not the place to REPORT bugs, but it is a good place in my experience to DISCUSS bugs that have also been reported.

    Last spring I had to deal with the DRI3/SDL issue, when SDL based games slowed down at the X server switch to a DRI3 version. It was discussed both in these forums and the appropriate bug report originally filed against Xorg. A git bisect was beyond me as I am using PPA packages and not compiling X, so I rolled back packages, tested updates as they came out, and waited, still able to use the known good version. Performance of new versions improved little by little until a new version of libsdl appeared at the Trusty-Utopic transition time. A week later the slowdown returned, so I rolled back all packages and reinstalled one at a time until I found the offender, which was libsdl. I call that a "dpkg bisect" and it identified libsdl as the offender. The existing bug report was copied as a bug report against libsdl. It's closed now as the next update reverted an accidently left out change and fixed the bug for good.

    If I had only discussed it here, libsdl's devs would not have heard about it unless they observed it themselves. If I had not discussed it here, I would not have found out about the hyper-Z issue also affecting performance and would still be down 20% or so. That was something I was easily able to fix myself, but would have had no idea was a problem without these forums.

    If you want to be able to "bisect" a day's updates, keep all your old packages, and keep snapshots of your OS. When you get an unknown clunker, roll back, then reupdate one package at a time (or sets of packages known to be unrelated) until you find the problem. My experience is that this is essential to running a rolling release or Ubuntu alphas in working machines.

    Leave a comment:


  • Vim_User
    replied
    Originally posted by Mat2 View Post
    Please don't be too eager to condemn Him. Otherwise in a similar situation, when something is annoying to You but have no time to fix it the same will happen.
    You can not claim to have no time to properly report a bug to the appropriate projects, when a) the bug is about a gaming device, play a bit less, report a bit more, and b) it seems that you have plenty of time to sput about that bug on Phoronix.

    It will not happen for me because:
    - I know that Phoronix is not the appropriate place to report bugs.
    - I know that bugs that don't get reported usually won't get fixed.
    - I know that proposals like "When this isn't be fixed I am going back to Windows" are nothing more than poor attempts to force someone to work on the issue, providing evidence of too much self importance.

    Leave a comment:


  • mike4
    replied
    Just tried with my script but my pedals are dead again. They worked before lunch. Need to boot windows....baahh

    [email protected]:~$ uname -a
    Linux michael-ubuntu 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
    [email protected]:~$

    Leave a comment:


  • Mat2
    replied
    Originally posted by mike4 View Post
    Looks like a fix apart the "not always working part":

    http://cgit.freedesktop.org/systemd/...?id=2658624399

    Now how to easily update without breaking Ubuntu 14.04? I guess I have to wait..hopefully not like:
    http://forum.winehq.org/viewtopic.php?f=8&t=23007
    You are setting the permissions manually and so this does not affect You.
    If that would be the case, the Pedals would not work all the time.

    For the second time I ask You: did You try with Linux 3.2 (or whatever kernel version worked last)?

    Leave a comment:


  • mike4
    replied
    Looks like a fix apart the "not always working part":

    http://cgit.freedesktop.org/systemd/...?id=2658624399

    Now how to easily update without breaking Ubuntu 14.04? I guess I have to wait..hopefully not like:
    http://forum.winehq.org/viewtopic.php?f=8&t=23007

    Leave a comment:


  • Mat2
    replied
    Originally posted by Vim_User View Post
    Come on, guys, don't feed the troll. It should be pretty clear now that mike4 is not actually interested in fixing that, just because it would take that one reason from him that he has to complain about systemd (though it is not even clear that this is a systemd issue).
    Please don't be too eager to condemn Him. Otherwise in a similar situation, when something is annoying to You but have no time to fix it the same will happen.

    Leave a comment:

Working...
X