Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

Open Source and Free Software

defacto7

(13,838 posts)

2. Although I see Andrea's point in principle

Reply to bananas (Reply #1)

Thu May 8, 2014, 11:21 PM

May 2014

I don't see the necessity of having "debug" visible in /proc/cmdline just to save some debug time. Seems more important to keep wandering init proc at bay for stability. So I guess this means I'm not quite up to their level and probably don't get the point.

I vote Linus.

Edit history

Please sign in to view edit histories.

Recommendations

0 members have recommended this reply (displayed in chronological order):

8 replies

= new reply since forum marked as read

Highlight:

Linus Torvalds suspends key Linux developer [View all] Recursion May 2014 OP

wtf bananas May 2014 #1

Although I see Andrea's point in principle defacto7 May 2014 #2

The real problem is there should not be a "wandering init proc" Recursion May 2014 #4

"PID 1 shouldn't be doing anything else" defacto7 May 2014 #6

Oh, now I see what you're talking about. Andrea's thing is a different thread Recursion May 2014 #8

There was an assertion failure in systemd Recursion May 2014 #3

On what kernels are these problems centering now? defacto7 May 2014 #5

That will hit any kernel whatsoever; it's a bug in systemd Recursion May 2014 #7