![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Hmm I don't think that was the right interview that had a more detailed description of what systemd is and how it works. I can't remember where I heard it now. But it basically opens up all the sockets first and then can start up everything really quickly. The kernel sockets will buffer any messages to the system sockets and play them back to the service once they are up and running. The interview that I heard that went into more detail also talked about the types of problems this solves when dealing with service dependencies and such and how it compares to Upstart and Initd. If I remember where that interview was I'll post it. -- David On Mon, Dec 20, 2010 at 10:53 AM, David Miller <david3d-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote: > I don't dislike Upstart but I'm not convinced that Upstart is the right > solution. systemd looks very interesting but is still pretty new. > > If you're not familiar with systemd then have a listen to Linux Outlaws > Episode 156. Which has an interview with Ade Bradshaw that explains a bit > about systemd around 1 hour and 22 minutes into it. > -- > David > > >
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |