<html> <head> <style></style> </head> <body class='hmmessage'> Hey Guys<div><br></div><div>Thanks for the feedback. I am just up to this now with my CLFS system. I have Ubuntu so have been using that as a guide</div><div>but still have a question regarding the replacement (or need for) the 3 rc*.conf scripts.</div><div><br></div><div>If I am never to use sysvinit or any of its files, do I a) still need them or b) have to replace them?</div><div><br></div><div>My main question here is about how each of these in the description say how they are for "System V ..."</div><div><br></div><div>Also, for example, the rcS.conf says:</div><div><br></div><div># This task handles the old System V-style single-user mode.</div><div><br></div><div>So my question here would be, what handles the new single-user mode? It appears there are no other *.conf</div><div>files that are launched on runlevel S (or does that mean it is no longer required if not using System V?)</div><div><br></div><div>Sorry if I have missed the point within your posts :( I am just keen to start with a clean slate (ie no System V anywhere).</div><div><br></div><div>Look forward to hearing from someone :)</div><div><br></div><div>cheers</div><div>grail<br><br>> Date: Fri, 23 Jul 2010 01:58:06 +0200<br>> From: stef@bononline.nl<br>> To: upstart-devel@lists.ubuntu.com<br>> Subject: Re: Using upstart on LFS<br>> <br>> On 07/19/2010 03:41 PM, Jeffrey Peckham wrote:<br>> > I tried doing something similar with an LFS build a few months ago. My <br>> > tactic was to just go through all the init scripts provided by LFS and <br>> > rewriting them as upstart jobs. Most of them can translate pretty <br>> > cleanly but I started running into trouble figuring out a clean and <br>> > flexible suite of networking jobs. I tried breaking out each layer of <br>> > the OSI model, that applied, as a different set of jobs. Probably too <br>> > esoteric and complex of a solution.<br>> ><br>> > This might just be a lack of good hard researching / understanding on <br>> > my part but I feel like early network setup (pre-NetworkManager) is <br>> > something ever distro does differently and there hasn't really been a <br>> > good clean solution to define, manage and monitor it.<br>> ><br>> > Let me know what you come up with in that area.<br>> ><br>> > ~Jeff<br>> Well, the idea with upstart is to define requirements per conf file, and <br>> let upstart do the rest.<br>> <br>> You do not have to find out yourself, on determine the requirements per <br>> service.<br>> <br>> Stef<br>> <br>> (LFS/CLFS since years)<br>> <br>> <br>> -- <br>> upstart-devel mailing list<br>> upstart-devel@lists.ubuntu.com<br>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel<br></div> </body> </html>