Posts by lattera@bsd.network
 (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.
       
 (DIR) Post #A2RGnT4A1q9ZWHmWuW by lattera@bsd.network
       2020-12-21T21:33:47Z
       
       1 likes, 0 repeats
       
       This great video by Andreas Kling shows how exploitation on systems without ASLR (or an improper implementation) makes exploitation of user-land programs easy. Exploit code can re-use hardcoded addresses. Later exploits can copy/paste addresses en masse.https://www.youtube.com/watch?v=LORxdO1XUjY
       
 (DIR) Post #A2dDGKkO5Rn06N7Br6 by lattera@bsd.network
       2020-12-27T15:56:20Z
       
       0 likes, 1 repeats
       
       What's the best bang-for-the-buck server-class AMD CPU these days?
       
 (DIR) Post #A2f3zswvA045z2ym5g by lattera@bsd.network
       2020-12-28T12:51:04Z
       
       0 likes, 2 repeats
       
       Inside the massive (and unregulated) world of surveillance tech:https://www.youtube.com/watch?v=ZcrnN-A2c60#Surveillance #SurveillanceTech #privacy
       
 (DIR) Post #A2ftjAESqQsmHNX6NE by lattera@bsd.network
       2020-12-28T21:46:33Z
       
       1 likes, 0 repeats
       
       I had an APU2 lying around and gathering dust with two WNICs installed. I ended up installing #HardenedBSD on it and setting it up as the new WAP.#wireless #networking
       
 (DIR) Post #A2iVMhYfBYj11SSPPE by lattera@bsd.network
       2020-12-29T23:05:00Z
       
       1 likes, 0 repeats
       
       Today, I converted a coworker from running #Win10 on bare metal to #HardenedBSD on bare metal with Win10 running in a #bhyve VM.Needless to say, it was a good day. :)
       
 (DIR) Post #A2yRFH6wF5PYTEd8WO by lattera@bsd.network
       2021-01-06T21:50:51Z
       
       0 likes, 1 repeats
       
       I wonder how this would play out if it was a group of people of color protesting against racial injustice.What would Trump's response be?Would it still be "you were defrauded"?
       
 (DIR) Post #A2zSSgfSO9HrsgLzGq by lattera@bsd.network
       2021-01-06T19:45:22Z
       
       0 likes, 1 repeats
       
       It pains me to see how divided our United States is.