Hey guys: OSCAR is coming up on another release (close to the end of the year) and we plan to include SystemImager 3.5.4. I am not sure when the udev work will stablize but if it is going to continue on beyond the new year, then perhaps we should tag (branch?) 3.5.4 so we can focus on weeding out some bugs and do another development release.
Anybody care to summarize the major changes between 3.5.3 and what is in the trunk? I know there is the virtual console, and probably some kernel updates... It would be _really_ nice if UYOK is fully working/integrated in 3.5.4, but that may be asking for too much... also, anybody knows if si_updateclient works now? I have reports from a few people saying that it breaks the installed nodes... Thanks, Bernard > -----Original Message----- > From: Brian Elliott Finley [mailto:[EMAIL PROTECTED] On > Behalf Of Brian Elliott Finley > Sent: Wednesday, November 23, 2005 12:56 > To: Andrea Righi > Cc: Bernard Li; sisuite-devel@lists.sourceforge.net > Subject: Re: [Sisuite-devel] UYOK and timestamps in initrd > > I've removed one, and we can remove other instances of the "touch" if > there are any. > > Andrea is correct in the current expected method for re-creating /dev. > However, I think we need to eliminate our need for devfs. To > do that, I > think we need to start using udev instead. > > We should use a hybrid that allows us to use whatever dev files are > brought over from a UYOK created initrd and supplement it > with whatever > udev sees. > > Or the other way 'round -- not sure which is more appropriate at this > point, or if it matters. I'm ready to start hacking this into trunk. > But if someone else (Andrea) starts working on it before I > do, just let > me know via this list. I'll also announce on the list when I start my > work on it. > > Cheers, -Brian > > > Thus spake Andrea Righi ([EMAIL PROTECTED]): > >I've done some little changes in the trunk in order to > support kernels > >without devfs (see SLES9 kernel for example). For now the > idea is not to > >put udev into the initrd, but, instead to use the content of > the /dev > >directory as seen from the golden client (without mounting devfs). > > > >So if the kernel support devfs, good... we go forward with > the classic > >installation steps, otherwise we try to use the static /dev/ files > >inside the initrd... > > > >I'm quite sure that something must be done also at the > autoinstallscript > >level, but with these changes an installation using the > standard BOEL > >kernel shouldn't have problems... > > > >Let me know if you find some problems... tonight I will re-try an > >installation using a suse kernel... > > > >Regards, > >-Andrea > > > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > >Register for a JBoss Training Course. Free Certification Exam > >for All Training Attendees Through End of 2005. For more info visit: > >http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click > >_______________________________________________ > >Sisuite-devel mailing list > >Sisuite-devel@lists.sourceforge.net > >https://lists.sourceforge.net/lists/listinfo/sisuite-devel > > -- > Brian Elliott Finley > Mobile: 630.631.6621 > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
