On 12/29/06, Alex Jones <[EMAIL PROTECTED]> wrote: > > On Sat, 2006-12-30 at 10:06 +1000, Peter Dolding wrote: > > Alex Jones wrote: > > > On Fri, 2006-12-29 at 13:02 +1000, Peter Dolding wrote: > > > > > >>> "initrd" is a RAM Disk used for initialising a bootup process. I have no > > >>> idea what relevance that has. > > >>> > > >>> If you mean SysVInit, well... /it's already gone in Ubuntu/. Upstart > > >>> replaced it ages ago. > > >>> > > >>> > > >>> > > >> PS the first SysVInit to run is inside the initrd. The mess starts at > > >> initrd and moves all the way threw the boot process. > > >> > > > > > > SysvInit isn't run at all. It is already replaced by Upstart. > > > > > The initilization min SysvInit last time I looked is still there. That > > just starts what drivers and setup is required from the initrd is still > > there before starting /sbin/init. > > Are you sure you're not confusing SysVInit for the Linux kernel starting > up? > > > Upstart has not replaced that as far > > as I know. > > No, and it never will replace the kernel :o) > > > Thinking the min SysvInit stops at the end of the intrd then > > the /sbin/init is started. So even if SysVInit is not installed its > > legacy can still be there. > > > > Basicly /bin/sh is in the initrd. The mess spread everywhere. I really > > have to have a look at it to see if they fixed in there as well. Ok time > > to look inside Ubuntu initrd to see if they got it all in the last release. > > > > Its only taken 5 years to start to get out of the /bin/sh problem. Even > > time I have looked most of the replacements have not got it all. > > > Peter Dolding >
...what? -- Travis Watkins http://www.realistanew.com _______________________________________________ gnome-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-devel-list
