Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Best practices for updates?
07-19-2006, 10:33 PM, (This post was last modified: 07-19-2006, 10:38 PM by macker.)
Best practices for updates?
The StressLinux distro seems like a great platform for doing stress-testing and benchmarking of systems. That said, it's limited by the time of the developer(s), what they have access to, etc.

I'd like to do some customizing to support hardware platforms I'm dealing with, e.g. Supermicro motherboards and Adaptec 2130SLP RAID controllers. The Adaptec controller isn't currently being detected (doesn't show a driver loading in dmesg), and none of the Supermicro boards I'm working with are listed in sl-wizards. sensors-detect does a fair job of finding the hardware, so the lm_sensors package obviously supports the chips, though it sometimes misreads the values.

So my question is whether there's any practices or methods I should follow in customizing the distro for my needs (e.g. modifying sl-wizards to support more boards natively), without causing problems for any other scripts, and whether there's benefit in me contributing any changes I make. The documentation is sparse, and while most things are self-explanatory, development style and roadmap is not always so straight-forward.


EDIT: Just booted up one of the systems to test ... loading the aacraid module finds the controller, it's just not getting loaded automatically. The 7902's do get recognized automatically. Is this an issue of driver support statically compiled into the kernel, while others are dynamically loaded modules?

Messages In This Thread
Best practices for updates? - by macker - 07-19-2006, 10:33 PM
RE: Best practices for updates? - by stresslinux - 07-23-2006, 09:42 PM

Forum Jump:

Users browsing this thread: 1 Guest(s)