problem, you know, that can't be fixed, then oftentimes Patrick Vulkerting takes note of that and then fixes it. So it's, like I said, casual collaboration. It's kind of like this is how Slackware gets really iterated upon, which is by community involvement. Linuxquestions.org. You can see these scripts for yourself. I mean, like I say, it's rc.inet1 and rc.inet2 and then things like hosts.conf and hosts.allow and hosts.deny and even like a setup script, like the network setup script. So if you want to see how this stuff kind of like gets started and gets instantiated, like these are the scripts to look at. It's pretty interesting and I think, you know, kind of a testament in a way of just kind of that traditional Unix-like process of here's some scripts. We're going to launch them at a specific time. They're going to execute some specific actions and then we're done. Everything's set repeatably. It's automation at work. Definitely something to look at and something to keep in mind, I (16/55)
You are viewing a single comment's thread from: