Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment: Re:STOP FUCKING WITH X11 (Score 1) 189

by tck42 (#49063263) Attached to: Wayland 1.7.0 Marks an Important Release
I'm not sure how - note that Daniel Stone (the presenter) appears here http://www.x.org/wiki/BoardOfD... - so he's one of the current folks in charge of dealing with the current xorg code; who better to judge the current state of xorg than someone who works with it every day? Another good presentation on the current state of X and its problems: http://youtu.be/2l7ixRE3OCw

Comment: Re:Linux distros (Score 4, Informative) 189

by tck42 (#49058259) Attached to: Wayland 1.7.0 Marks an Important Release
FWIW the reddit you link to has some replies with very reasonable explanations for the behavior you mention. As they state, I think the deal is even if it fails, it failed _after_ it started, and thus the start itself was successful. I think this is reasonable. I also got all log entries when reproducing here (same result as everyone else in that thread).

I'm not saying deleting bugs is cool - at least a WONTFIX or link to a DUP is appropriate - but are you sure it was opened successfully? What was the bug #?

The above said - I do see your point from a usability, if not strict "proper functioning" standpoint; previously for forking services that did some sort of constant time initialization and checking (opening files, sockets, etc) if the initialization failed they could report back and the startup script could return that result - systemd doesn't seem to support that. However there are other problems with the old way too (as you're checking result code I assume you're scripting) - startup could hang and you never get a result.I suppose the solution is similar for both cases - pick a point of time in the future and check if the status is as expected.

Maybe this is a feature request? As stated in the reddit, it only makes sense for forking services. It's not something I'd ever want, but maybe you could give a use case?

Comment: Re:YAY! (Score 2) 135

by tck42 (#39863723) Attached to: Bug Busters! OpenBSD 5.1 Released
As a network appliance type device at least I'd say it's still very relevant. I still prefer configuring / maintaining pf over iptables (or any other competitor I've tried) for any non-trivial ruleset, the documentation is IMO much better than most of the other stuff out there, it's relatively secure and relatively stable, and the performance and compatibility with older hardware has been great (in my experience). I use it for my gateway device and have never had any problems. I briefly used Linux for the same task and found myself spending more time messing with it. I could easily see it replacing all sorts of expensive commercial solutions at my workplace but managers like commercial vendors. It's just well put together and does what it's built for quite well. I think there's room for all sorts of stuff in the "grand scheme", not just shiny and popular stuff.

I have yet to see any problem, however complicated, which, when you looked at it in the right way, did not become still more complicated. -- Poul Anderson

Working...