On Nov 30, 2007 12:32 PM, Rudolf Kastl <che666@xxxxxxxxx> wrote:
> On Nov 30, 2007 12:09 PM, Jonathan Dieter <jdieter@xxxxxxxxx> wrote:
> > On Fri, 2007-11-30 at 09:30 +0000, Rudolf Kastl wrote:
> > > Personally i am working on straightening out initng which is part of
> > > the repos and with selinux disabled (there is a bug in current initng
> > > regarding selinux so dont use it if you want selinux enabled until the
> > > next fix shows up) from start if init to gdm in 15 seconds with
> > > NetworkManager and all that stuff enabled.
> > > I guess with a bit more hacking and optimising you could go close to 10 seconds.
> > >
> > I just gave initng a shot, and, while it started up my system extremely
> > fast, I noticed a number of failure messages on the screen and when I
> > logged in, I noticed that my CPU Frequency applet said that my CPU
> > wasn't capable of scaling (it's a laptop with a Core Duo processor and
> > three different levels of scaling).
>
> the cpuspeed script has to be fixed. actually as a workaround you can
> just use the following wrapper:
>
> #!/sbin/itype
> # This is a i file, used by initng parsed by install_service
>
> # NAME:
> # DESCRIPTION:
> # WWW:
>
> service service/cpuspeed {
> need = system/bootmisc;
> use = system/modules system/coldplug;
> exec start = /etc/init.d/cpuspeed start;
> exec stop = /etc/init.d/cpuspeed stop;
> }
>
> put the above script into:
>
> /etc/initng/service/cpuspeed.i
>
> of course that is just a workaround :D
>
> >
> > Do you want bug reports or does it need a bit more work before it can
> > replace normal init?
>
> That is a pretty much known problem and if i am not too wrong i even
> filed it into fedora bugzilla. If you encounter something and dont
> find a report for it yet please report it as many people have the
> chance then to attach a fix for it.
>
> Of course there is still alot of work to do to smooth things out. What
> should work now is getting the system to boot in any case. There is
> also lots of things to improve in the base system to make things go
> smoother. e.g. you will see that NetworkManager will fail upon bootup.
> That is because dbus daemon needs 5 seconds when it has been started
> until the service is available. The above numbers i gave for boottime
> include having a sleep 5 in the NetworkManager startup script (hacky
> workaround that needs a fix with dbus).
>
> It is definitely not ready for real end user consumption because
> things have to be checked and improved all over the place but with
> more people contributing actually that could get done rather fast in
> my eyes. It is just alot work if only a few people with not much spare
> time fix things here and there as time permits, so every small bit of
> help and patch is a nice thing to have.
>
> Yes the bootup time is very fast but i think to get broader acceptance
> more stuff has to be fixed. Actually the new version of it in the pipe
> is supposed to be able to take dbus events to get things started up
> and uses posix compliant startup scripts (note that the upcoming
> scripts are automatically generated from the ifiles it uses now so it
> makes sense to just fix the current stable release). The svn scripts
> also allow the addition of new events like beeing able to add status
> scripts/routines and configcheck etc.
>
> kind regards,
> Rudolf Kastl
>
>
> >
> > Jonathan
>
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
>
as for the cpuspeed workaround... you also have to exchange the
service used for it in the runlevel file.
/etc/initng/runlevel/default.runlevel
kind regards,
Rudolf Kastl
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
