Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: initng https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173459 ------- Additional Comments From daner964@xxxxxxxxxxxxxx 2006-01-27 07:21 EST ------- (In reply to comment #181) > >> - some bugs (e.g. sometimes stopping a daemon does not seem to work if it > >> dependent on a service in the same file); > > > >Could you post a bug about this (with all relevant information) in initng bz? It > >doesn't sound like a hard fix to me... > > I will try but first I need to install 0.5.3. Or would svn be better? I think 0.5.3 is good. I haven't seen any big changes in that area since 0.5.3... > >> - sometimes sound devices are not created, this is clearly a udevd issue; > > >Udev scripts are being heavily worked on. Let's hope this gets fixed. Filing a > >bug might help too. > > The problem that it only happens occasionally so it seems like a timing issue. > Calling udevstart at the end of system/alsasound/loadmodules forces the devices > to be created but adds 2 seconds to the boottime (as it also checks all other > devices). Again I will need to install 0.5.3 before filing a proper bug report. I've also experienced strange timing problems involving udev. Someone promised me they were gone, but obviously not. Does it make any difference simply inserting a "sleep 10" at the beginning of system/alsasound/loadmodules? > >> - booting hung while starting the daemon udev/udevd hung because udevd does not > >> recognize the --daemon argument (easily fixable); > > > >Are you sure about this? According to udevd manpage udevd _has_ a daemon >argument. > > Not on my system! Perhaps you are running rawhide? I am running FC4 with the > latest updates but little else. Hmmm... After a closer look that particular argument doesn't exist anymore in 0.5.3. Just upgrade and be happy... > >> - console flashes (ugly); > > > >Flashes? Could you elaborate? > > The console turns black and then it comes back up. Strangeness. Haven't ever seen this one. Sounds like it tried to switch to another tty or something? > >> - no integration yet with rhgb (easily fixable I presume). > > > >Blah. Do we really need rhgb when running initng? > > I think we do (but it is of course not a show stopper). Many people do like the > cleanliness of a WinXP or Mac/OSX boot. On a desktop system users should not > see *any* bootmessages (even rhgb is too noisy for my taste). Ok. I guess the best way to do this would be a plugin. All output on the screen comes from a plugin named cpout (colorprintout). I don't think it would be a really big deal (for someone custom with rhgb) to make a rhgb output plugin which instead sends information to rhgb. I guess big question is what would be showed. Since multiple services/daemons are starting at the same time I guess rhgb would have to be extended? -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
