Here are my two stock post-install scripts that I drop into the /var/lib/systemimager/scripts/post-install subdirectory. One updates the e1000 driver options (it can reduce latency by up to 70% on HPC systems), and the other adds the /dev/shm entry to modules/modprobe.conf.
For me, this works well enough for now. > -----Original Message----- > From: Erich Focht [mailto:[EMAIL PROTECTED] > Sent: Friday, January 13, 2006 6:46 AM > To: Siadal, Jeremy C > Cc: [email protected]; Paul Greidanus; oscar- > [EMAIL PROTECTED] > Subject: Re: [Oscar-devel] Re: [Sisuite-devel] Troubles with /dev/shm > > Hi Jeremy, > > On Thursday 12 January 2006 20:00, Siadal, Jeremy C wrote: > > I've added the option (just like you have it below) as the last line in > > the file, OSCAR nodes couldn't image any more. Checking the oscarmaster > > script shows that when the /dev/shm option is added to the .disk file, > > SIS tries to install to the second physical hard drive. I think that is > > the same problem Paul had. > > > > To me, that is a real bug. If I need to add devices to the .disk file, > > OSCAR needs to interpret them in the correct order. > > that is a bug, indeed. I found that systeminstaller creates an entry like > > <disk dev="/dev/none" label_type="msdos" unit_of_measurement="MB"> > </disk> > > in the etc/systemimager/autoinstallscript.conf file inside the image. > > As a workaround: delete that <disk ..> </disk> block and regenerate the > autoinstallscript with si_mkautoinstallscript. > > I'll have a look at systeminstaller, and will also consider adding > /dev/shm > by default. > > Regards, > Erich
81all.add_shm_device
Description: 81all.add_shm_device
80all.add_e1000_options
Description: 80all.add_e1000_options
