Post A2Kmlupve2dhUni1eS by lattera@bsd.network
(DIR) More posts by lattera@bsd.network
(DIR) Post #9w5MQDWw0LYNccAlc0 by lattera@bsd.network
2018-06-08T13:00:56Z
0 likes, 0 repeats
#BSDCan day 1: I'll live toot the presentations I'm in. Prepare for the toot storm. We'll be starting the day with Benno Rice's talk "The Tragedy of #SystemD"
(DIR) Post #A2KmlixHorOWe93jSC by lattera@bsd.network
2018-06-08T13:06:30Z
0 likes, 0 repeats
#BSDCan (Opening remarks): Around 270 attendees.
(DIR) Post #A2KmljDaqERFSigks4 by lattera@bsd.network
2018-06-08T13:07:25Z
0 likes, 0 repeats
#BSDCan (Opening remarks): BSD is definitely dying. Don't come next year. ;)
(DIR) Post #A2KmljXReQJmSHyboW by lattera@bsd.network
2018-06-08T13:08:58Z
0 likes, 0 repeats
#BSDCan (Opening remarks): #HardenedBSD a sponsor of this year's BSDCan. :)
(DIR) Post #A2Kmlk1vp4hjyqExKi by lattera@bsd.network
2018-06-08T13:10:00Z
0 likes, 0 repeats
#BSDCan (Opening remarks): Hacker lounge tonight is at the HNN residence at 202 Henderson Ave.
(DIR) Post #A2KmlkbNhH3pkmpGaW by lattera@bsd.network
2018-06-08T13:11:17Z
0 likes, 0 repeats
#BSDCan (Opening remarks): The closing session is unlike any other closing session you've ever seen.[Personal note: definitely true. If there's one session you come to, make it the closing session.]
(DIR) Post #A2KmllQQdTtUJ6i29g by lattera@bsd.network
2018-06-08T13:11:58Z
0 likes, 0 repeats
#BSDCan (Opening remarks): We'll make Henning wear "inappropriate to Henning" clothing.Also, Henning does almost anything for cash.
(DIR) Post #A2Kmlm8jyjL6WXRQDw by lattera@bsd.network
2018-06-08T13:12:38Z
0 likes, 0 repeats
#BSDCan (Opening remarks): Closing social will be at The Red Lion after the charity auction.
(DIR) Post #A2KmlmXuT9TLmbDWSG by lattera@bsd.network
2018-06-08T13:13:34Z
0 likes, 0 repeats
#BSDCan (Opening remarks): Now turning the time over to Benno for his Tragedy of #SystemD talk.
(DIR) Post #A2Kmln98ElFLe2dFTM by lattera@bsd.network
2018-06-08T13:14:59Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): Definition of Tragedy: a form of drama based on human suffering that invokes an accompanying catharsis or pleasure in audiences.
(DIR) Post #A2KmlnqNdxqDoArmsq by lattera@bsd.network
2018-06-08T13:15:33Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): Aurynn Shaw's "Contempt Culture" article is an interesting one.
(DIR) Post #A2KmloVr9l1BsoGuX2 by lattera@bsd.network
2018-06-08T13:16:25Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): Familiarity feels really good to people, but it is good to have people reassess periodically.
(DIR) Post #A2Kmlp7Qu34llLqv6O by lattera@bsd.network
2018-06-08T13:17:45Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): In the beginning, there was UNIX. Well, there were other options back then, but UNIX is a good place to start off.init is the last step of the boot process.He's now reading the init manpage from seventh edition UNIX (1979).
(DIR) Post #A2KmlpWxN9Ub2VnIsy by lattera@bsd.network
2018-06-08T13:18:48Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): "Housekeeping funcitons like... mounting filesystems, and starting daemons."Back in Seventh Edition UNIX and 4.3 BSD, there weren't many processes at start.
(DIR) Post #A2Kmlq01d4kEUfOWC8 by lattera@bsd.network
2018-06-08T13:20:18Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): inetd has an interesting history. Services would usually use inetd. This turned out to be not-well-suited for applications that require a lot of persistent state.Then things changed. It seems glim to see the Internet happened. You see large applications that needed to keep lots of state. You start to see the notion of a stand-alone service, now called a daemon.
(DIR) Post #A2KmlqYPZEFaDJTynA by lattera@bsd.network
2018-06-08T13:21:46Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): Essentially, init could be viewed as system configuration. Especially with it responsible for mounting filesystems and bootstrapping/starting services.
(DIR) Post #A2Kmlr03uQMtb4Q3tI by lattera@bsd.network
2018-06-08T13:22:37Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): What the traditional rc system doesn't do is automated service management.
(DIR) Post #A2KmlrPwMD4ItKWjE8 by lattera@bsd.network
2018-06-08T13:23:45Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): We've gotten used to how the current rc system works.Other environments handle services well. Microsoft Windows NT does it really well. macOS/iOS launchd.Now we're getting into the idea of SystemD.
(DIR) Post #A2KmlrsIelkmJHnNQm by lattera@bsd.network
2018-06-08T13:24:54Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): The idea behind SystemD started with launchd from OSX. It's an events-based service management system. The idea is that when something in the environment changes (aka, an event), the services management solution should perform an action.
(DIR) Post #A2KmlsZu2edEUWCCOW by lattera@bsd.network
2018-06-08T13:26:43Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): Services aren't started until they're needed.In 2010, Lennart looked to enhance how Linux managed services. He looked at Upstart from Canonical, wasn't impressed. He liked how launchd worked.Take a look at Lennart's "Rethinking PID 1" article.
(DIR) Post #A2KmlszmURKdmmIrjM by lattera@bsd.network
2018-06-08T13:27:24Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): "An init system that is responsible for maintaining services needs to listen to hardware and software changes." -- Lennart, "Rethinking PID 1"Systems need to be reactive.
(DIR) Post #A2KmltUycSHlLWtmM4 by lattera@bsd.network
2018-06-08T13:29:12Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): SystemD is about system management. There's an understanding that is understood in other places. We tend to think of the universe as being just userspace and kernel.The dynamic stuff is better managed through userspace than the kernel.SystemD adds a layer in the middle: the system layer. Network management, time, things don't necessarily belong in the userspace or in the kernel.
(DIR) Post #A2Kmlu4mTKvR8ZeNA8 by lattera@bsd.network
2018-06-08T13:30:19Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): The reason why SystemD is so large is because it's building that system management layer between userspace and kernel. They have to bring in udev, ntp, etc. because those are tools typically used in userland. Building the system management layer means bringing those things in for a coherent experience.
(DIR) Post #A2KmluW4pqlAVEQAi0 by lattera@bsd.network
2018-06-08T13:33:52Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): We're gonna look at the complaints about SystemD.Complaint 1: "It violates UNIX philosophy!"Complaint 2: "It's bloated and monolithic!"Complaint 3: "It's buggy!" C'mon, it's software. We've all had fun bugs.A lot of people say "PID 1 cannot fail!" Essentially, that means people are saying PID 1 can never be replaced/rewritten. Plays into the "we've always done it this way" falacy.
(DIR) Post #A2Kmlupve2dhUni1eS by lattera@bsd.network
2018-06-08T13:36:44Z
1 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): Another complaint: "It's not portable!"That's a valid complaint. But, UNIX as a concept, is dead. This notion of portability and careful development is dead. Because Linux is in such a dominant position can do whatever they like.We in the BSDs get to be equally liberated. We can do whatever we want.
(DIR) Post #A2Kmlv94Urx4SAfJUO by lattera@bsd.network
2018-06-08T13:38:46Z
0 likes, 0 repeats
#BSDCan (Tragedy of #SystemD): SystemD represents change. This brings us to the tragedy of the piece. It's really scary when it threatens things you find familiar.We love change when we're the ones doing it. We dislike or fear it when someone else does it.