<html> <head> <style></style> </head> <body class='hmmessage'> Ok ... so I worked out that some of the applications in my scripts were not the same as those from Sourcemage and hence did not<div>take the same options (this is partially fixed now)</div><div><br></div><div>Assuming someone actually is reading any of this (as have had no replies), but I was wondering if someone can tell me how the</div><div>"emits" lines in the Ubuntu scripts works??<br><br></div><div>For example, the mountall.conf upstart script lists some of the following lines:</div><div><br></div><div>emits virtual-filesystem</div><div>emits local-filesystems</div><div>emits mounted</div><div><br></div><div>To name a few. Yet there is no corresponding call to initctl emit <blah></div><div><br></div><div>So my question is, how do the events get 'emitted'?</div><div><br></div><div>Cheers</div><div>grail<br><hr id="stopSpelling">From: grail69@hotmail.com<br>To: upstart-devel@lists.ubuntu.com<br>Subject: RE: Using upstart on CLFS<br>Date: Wed, 11 Aug 2010 06:50:10 +0000<br><br> <meta http-equiv="Content-Type" content="text/html; charset=unicode"> <meta name="Generator" content="Microsoft SafeHTML"> <style> .ExternalClass .ecxhmmessage P {padding:0px;} .ExternalClass body.ecxhmmessage {font-size:10pt;font-family:Tahoma;} </style> Well I am hoping if I keep banging away here someone will assist or point me in the right direction :)<div><br></div><div>So I have taken the scripts below from an alternate install of a distro called Sourcemage, which boots just fine,</div><div>and supplanted the scripts to my CLFS system.</div><div><br></div><div>Good or bad my machine bombs on the first 2 scripts to be lanuched: hostname and mountall</div><div><br></div><div>The boot screen stop at the following errors(showing last several lines):</div><div><br></div><div>VFS: Mounted root (ext2 filesystem) readonly on device 8:1.</div><div>Freeing unused kernel memory: 400k freed</div><div>Freeing unused kernel memory: 1588k freed</div><div>hostname used greatest stack depth: 4440 bytes left</div><div>init: hostname main process (757) terminated with status 1</div><div>mount used greatest stack depth: 4248 bytes left</div><div>EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 213133</div><div>init: mountall main process (756) terminated with status 8</div><div><br></div><div>I have attached said scripts</div><div><br></div><div>Again any help would be greatly appreciated</div><div><br></div><div>Cheers</div><div>grail</div><div><br><br><hr id="ecxstopSpelling">From: grail69@hotmail.com<br>To: upstart-devel@lists.ubuntu.com<br>Subject: FW: Using upstart on LFS<br>Date: Tue, 10 Aug 2010 09:38:05 +0000<br><br> <style> .ExternalClass .ecxhmmessage P {padding:0px;} .ExternalClass body.ecxhmmessage {font-size:10pt;font-family:Tahoma;} </style> So I have been battling with this for the last couple of days and was wondering if anyone would tell me<div>what is the bare minimum of scripts required (to get to runlevel 3 equivalent on a base system) using Ubuntu </div><div>scripts to boot a system?</div><div><br></div><div>I have been trying to use a combination of the following scripts:</div><div><br></div><div>hostname</div><div>dbus</div><div>mountall</div><div>tty1</div><div>udev</div><div>udev-finish</div><div>udevtrigger</div><div>udevmontior</div><div><br></div><div>Would I require more than this to get to a console login screen?</div><div><br></div><div>I feel I must be missing something as I am getting an init error in the mountall script and never progressing any further :(</div><div>Unfortunately as I am unable to get very far in there also is not a great deal of logging for me to investigate to see where I am coming unstuck</div><div><br></div><div>Any suggestions would be greatly appreciated :)</div><div><br></div><div>I would also add, as per below, I have a fresh CLFS system with the exclusion of the System-V applications have not been installed.</div><div><br></div><div>Cheers</div><div>grail</div><div><br></div><div>PS. Let me know if I need to provide more detail for someone to assist me?<br><br><hr id="ecxstopSpelling">From: grail69@hotmail.com<br>To: upstart-devel@lists.ubuntu.com<br>Subject: RE: Using upstart on LFS<br>Date: Sun, 8 Aug 2010 23:11:21 +0000<br><br> <style> .ExternalClass .ecxhmmessage P {padding:0px;} .ExternalClass body.ecxhmmessage {font-size:10pt;font-family:Tahoma;} </style> 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> <br>-- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel</div> <br>-- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel</div> <br>-- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel</div> </body> </html>