Largest DebConf Ever Will Hit Heidelberg In Mid-August
New submitter alfino writes: Less than two weeks away, DebConf15, the 16th Debian Conference, scheduled to take place 15–22 August in Heidelberg, Germany, has been officially announced. The organisers are expecting more than 550 participants from 53 countries (making it the largest DebConf so far, and the first in history that will be closing registrations early), and have presented a schedule packed with talks and events, including several prominent, invited speakers, and yet plenty of room for informal and ad-hoc collaboration. Most events will be streamed live to allow for remote participation, and archived for later consumption.
The celebrations of Debian's 22nd birthday on 16 August, the traditional "Cheese & Wine BoF", a screening of the Oscar-award-winning documentary Citizenfour (which mentions Debian in its end credits), and a day trip for all attendees top off the programme. Additionally, DebConf15 will be preceeded by DebCamp, a week of sprints, workshops and hacking sessions. It is expected that much progress will be made on Debian (gcc5 transition, planning of the next stable release "stretch", etc.), and of course Free Software in general. The conference itself begins with an Open Weekend geared to the public, and featuring a job fair.
Attendance is free of charge thanks to numerous sponsors, including Platinum Sponsor Hewlett-Packard. Registration is required nonetheless and only very few places are left.
The conference will be tracked on various social media sites using hashtag #DebConf15. Even though Debian does not endorse proprietary services, @DebConf will have the news.
The celebrations of Debian's 22nd birthday on 16 August, the traditional "Cheese & Wine BoF", a screening of the Oscar-award-winning documentary Citizenfour (which mentions Debian in its end credits), and a day trip for all attendees top off the programme. Additionally, DebConf15 will be preceeded by DebCamp, a week of sprints, workshops and hacking sessions. It is expected that much progress will be made on Debian (gcc5 transition, planning of the next stable release "stretch", etc.), and of course Free Software in general. The conference itself begins with an Open Weekend geared to the public, and featuring a job fair.
Attendance is free of charge thanks to numerous sponsors, including Platinum Sponsor Hewlett-Packard. Registration is required nonetheless and only very few places are left.
The conference will be tracked on various social media sites using hashtag #DebConf15. Even though Debian does not endorse proprietary services, @DebConf will have the news.
Who cares about debutantes?
I hope all 10 Debian users have a great time!
It burst into flames! It burst into flames, and it's falling, it's crashing! Watch it, watch it! Get out of the way! Get this, Charlie! Get this, Charlie! It's fire—and it's crashing! It's crashing terrible! Oh, my, get out of the way, please! It's burning and bursting into flames, and the—and it's falling on the mooring-mast and all the folks agree that this is terrible, this is one of the worst catastrophes in the world. [Indecipherable word(s)] It's–it's–it's the flames, [indecipherable, possibly the word "climbing"] oh, four- or five-hundred feet into the sky and it ... it's a terrific crash, ladies and gentlemen. It's smoke, and it's flames now ... and the frame is crashing to the ground, not quite to the mooring-mast. Oh, the humanity and all the passengers screaming around here. I told you, I can't even talk to people whose friends are on there. Ah! It's–it's–it's–it's ... o–ohhh! I–I can't talk, ladies and gentlemen. Honest, it's just laying there, a mass of smoking wreckage. Ah! And everybody can hardly breathe and talk, and the screaming. Lady, I–I'm sorry. Honest: I–I can hardly breathe. I–I'm going to step inside where I cannot see it. Charlie, that's terrible. Ah, ah—I can't. I, listen, folks, I–I'm gonna have to stop for a minute because I've lost my voice. This is the worst thing I've ever witnessed.
Even though Debian does not endorse proprietary services they been bought hook line and sinker.
'The developers outside looked from redhat to debian, and from debian to redhat, and from redhat to debian again; but already it was impossible to say which was which.'
Add systemd rants here, if you must.
Yes, systemd is there in the schedule:
https://summit.debconf.org/debconf15/meeting/304/systemd-how-we-survived-jessie-and-how-we-will-break-stretch/
https://summit.debconf.org/debconf15/meeting/305/your-systemd-tool-box-dissecting-and-debugging-boot-and-services/
I guess it will be a while before we see that kind of conference with devuan.
Otherwise: thanks a lot to Debian for an environment that has been a joy
to work with for a long time. My personal server is still running Debian, but
I for one most probably won't be joining the systemd bandwagon.
debian is irrelevant now that they use systemd.
When I upgraded to Jessie, it installed systemd, and the laptop started going into suspend all the time. I'd unsuspend it, and it would suspend again 30 seconds later.
In diagnosing it, I found that using journalctl is much nicer than grepping though the tangle of partial and redundant logs that syslogd generates -- how is it that that particular collective itch seems not to have provoked anyone to scratch it previously in the decades we've been suffering it?
I also discovered that the laptop's lid switch was stuck in, and needed a squirt of lubricant to get it working again -- for some reason sysvinit/acpi/etc. conspired to ignore that fact.
One gets the impression that the bulk of people still whining about systemd have either never used it, or have very little real experience of the tangle of string and duct tape that is sysvinit. If whining about Debian, they also seem to be incapable of basic reading comprehension -- One only uses the word "default" when other choices are available.
Debian: GNU/Linux done the Linux way
If there was a presentation at the conference about removing systemd. Its simple to do, but seeing both camps present at the conference would have been nice.
I keep seeing your type of fucking idiotic "If you don't like systemd, then you love sysvinit!" claims whenever this topic comes up.
That's utterly false.
Many of us have a deep dislike of both systemd and sysvinit!
But compared to one another, systemd tends to be far worse than sysvinit.
If we have to choose one or the other, we'll take sysvinit because it doesn't fuck us over nearly as badly as systemd constantly has.
Don't misunderstand me, I'm absolutely disgusted by systemd and what has happened to Debian. But I'm more disgusted by the farce that is Devuan.
First of all, Devuan shouldn't even exist. Yes, Debian should have been forked, but it is this fork that should have used systemd. Debian proper should have been left alone, so it could continue as it has for decades now. The existence of Devuan is equivalent to surrendering.
Second of all, Devuan was a knee-jerk reaction. Knee-jerk reactions rarely turn out well.
Third of all, because it was a knee-jerk reaction by individuals prone to knee-jerk reactions, its social and community structures were all fucked up from the very beginning. I remember following its discussion during its early days, and instead of talking about how to build a world-class Linux distro, so much of the discussion involved people accusing others of being "systemd trolls".
Finally, Devuan is totally unnecessary. Many Debian users have found that FreeBSD works much better than Debian ever did. After using FreeBSD, they end up wishing that they had switched years earlier! They get a system that's more capable than Debian, more stable than Debian, developed by better developers than Debian is, while still running pretty much all of the software that Debian can run.
Devuan is, in my opinion, a 100% lost cause. There is no hope for saving it. I don't think that it will ever be anything useful. That's why it's better that we, as former Debian users, ignore it. We should focus on the future, which is clearly FreeBSD.
Systemd hasn't caused me any trouble for a long time, as well. But that's because I switched from Debian to FreeBSD as soon as my Debian testing installation was first fucked up by systemd. After learning more about it, I came to the conclusion that systemd can't be fixed. It can only be thrown out. But the Debian project did not seem willing to do that. It was then clear to me that Debian, and Linux in general, was going to crash and burn, and that's pretty much what I think we've seen happen so far. I didn't want to be part of that disaster, so I moved my computers and data from Debian to FreeBSD right away. My computers now boot fine, my data is safe, and I can compute without the fear, uncertainty and doubt that systemd brought to Debian and Linux.
When I upgraded to Jessie, it installed systemd, and the laptop started going into suspend all the time. I'd unsuspend it, and it would suspend again 30 seconds later.
In diagnosing it, I found that using journalctl is much nicer than grepping though the tangle of partial and redundant logs that syslogd generates -- how is it that that particular collective itch seems not to have provoked anyone to scratch it previously in the decades we've been suffering it?
I also discovered that the laptop's lid switch was stuck in, and needed a squirt of lubricant to get it working again -- for some reason sysvinit/acpi/etc. conspired to ignore that fact.
One gets the impression that the bulk of people still whining about systemd have either never used it, or have very little real experience of the tangle of string and duct tape that is sysvinit. If whining about Debian, they also seem to be incapable of basic reading comprehension -- One only uses the word "default" when other choices are available.
Actually that is due to a particular annoying default in systemd, where it suspends if it detects the laptop is closed instead of reacting to the laptop-close event. It is quite frustrating. It default exists because Pottering has a laptop with an power button on the side that can turn it on in his bag, so systemd is configured to shut down on boot up if it detects the laptop is closed even though that makes no sense. He convinced me it just a default though, but I haven't yet figured out where to change it, so far I just open up the laptop before I can power off from the docking station.
In Debian, one rightfully expects the "default" to be rock-solid, and minimal-fuss. This implicit promise is broken by systemd. Also notice that systemd as default implies no full alternatives are possible long-term, as a lot has to be adjusted to whatever systemd needs. This means that over time, the "default" will be the only way to use the fill distro. Doubtlessly, that is what the systemd-mafia wants.
While I do not know how your reading comprehension is, you have at least failed to read any documents detailing the impact of making systemd the "default".
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
The point is that if sysvinit has problems, you can usually diagnose and fix them yourself. You can also work around it. So while not perfect and sometimes a pain, you can adapt it to be not broken for your particular needs and after that it usually stays non-broken, because it is stable and mature.
With systemd that is no longer possible. Even creating bug-reports for systemd seems to be a real challenge, and not only because the dev-team is mostly unresponsive.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
See subject & his "Run, Forrest: RUN!!!" vs. a fair challenge http://news.slashdot.org/comme...
APK
P.S.=> Keep on shooting your blowhard done nothing in computing mouth off gweihir - I'll be RIGHT THERE AGAIN to expose your crap yet again (have fun with the shame you'll have to publicly endure here & YOU STARTED IT WITH ME YOU USELESS TROLLING LOSER WITH NO SKILLS BUT LOTS OF MERE "TALK", lmao)... apk
See subject & his "Run, Forrest: RUN!!!" vs. a fair challenge http://news.slashdot.org/comme...
APK
P.S.=> Keep on shooting your blowhard done nothing in computing mouth off gweihir - I'll be RIGHT THERE AGAIN to expose your crap yet again (have fun with the shame you'll have to publicly endure here & YOU STARTED IT WITH ME YOU USELESS TROLLING LOSER WITH NO SKILLS BUT LOTS OF MERE "TALK", lmao)... apk
"Run, Forrest: RUN!!!" vs. a fair challenge http://news.slashdot.org/comme...
APK
P.S.=> Keep on shooting your blowhard done nothing in computing mouth off gweihir - I'll be RIGHT THERE AGAIN to expose your crap yet again (have fun with the shame you'll have to publicly endure here & YOU STARTED IT WITH ME YOU USELESS TROLLING LOSER WITH NO SKILLS BUT LOTS OF MERE "TALK", lmao)... apk
"Run, Forrest: RUN!!!" vs. a fair challenge http://news.slashdot.org/comme...
APK
P.S.=> Keep on shooting your blowhard done nothing in computing mouth off gweihir - I'll be RIGHT THERE AGAIN to expose your crap yet again (have fun with the shame you'll have to publicly endure here & YOU STARTED IT WITH ME YOU USELESS TROLLING LOSER WITH NO SKILLS BUT LOTS OF MERE "TALK", lmao)... apk
"Run, Forrest: RUN!!!" vs. a fair challenge http://news.slashdot.org/comme...
It's truly UTTERLY HILARIOUS seeing a bullshit artist mere talk TROLLING done zero loser like you has the NERVE to state what you did in the post parent to that & then you RAN after that link above, gweihir... lol!
FACT: You don't HAVE the ability to code & you have no evidence of any ware you've ever done, much less ones that have gone commercial or are highly esteemed as I have, e.g. MalwareBytes' folks HOSTING & RECOMMENDING my code even -> http://hosts-file.net/?s=Downl... (even GOOGLE & BING don't show a DAMN THING for you, loser) & the link above FURTHER evidences it!
FACT: You're a bullshit blowhard reduced to illogical ad hominem attacks when cornered & nothing more - Why? LOL, you're a MERE TECHIE MENIAL @ best/most!
FACT: Minus coders like myself, you TECHIE or NETWORK ADMIN MENIALS ARE HELPLESS - just as you've SHOWN yourself to be in that link above!)
FACT: You've been FROZEN as a NETWORK ADMIN/TECHIE ONLY FOR 15 FUCKING YEARS!
(You're not intelligent OR SKILLED ENOUGH to get higher in this field, & the HIGHEST LEVEL OF EVOLUTION, skills-wise IS CODING - after all/again - minus us coders, losers like you can't work @ all!)
* ABOVE ALL ELSE:
When the likes of MalwareBytes' people host & RECOMMEND YOUR WARE (especially for security as mine is)?
THEN, you can talk as a peer, you fucking pitiful hot-air windbag wannabe!
I see you TRY to effetely & vainly play "coder" here, when I KNOW, for a FACT, you're merely a network tech/admin FUCKING MENIAL that merely uses tools that actual coders like MYSELF create for you, USER WITH A BETTER PASSWORD ONLY IN REALITY, merely use!
APK
P.S.=> Shoot your blowhard mouth off gweihir & I'll be RIGHT THERE AGAIN to expose you again (shaming you publicly since YOU STARTED IT WITH ME YOU USELESS TROLLING LOSER WITH NO SKILLS BUT LOTS OF MERE "TALK", lmao)... apk