Hi Paul, >>> I was suspicious that it was smaller, and there were so many new >>> > modules. > > On second look, it wasn't so much smaller. Why were some modules > selected for the tarball and others left out? > All modules which are defined in the kernel config are included in the tarball. But I took a second look at the EISA/VL option for the AIC7XXX in the kernel Configure help:
" Probe for EISA and VL AIC7XXX Adapters CONFIG_AIC7XXX_PROBE_EISA_VL Probe for EISA and VLB Aic7xxx controllers. In many newer systems, the invasive probes necessary to detect these controllers can cause other devices to fail. For this reason, the non-PCI probe code is disabled by default. The current value of this option can be "toggled" via the no_probe kernel command line option. " This is the reason why it wasn't enabled in our kernel config. You can "toggle" the option on the standard (bering-uClibc) module by loading the module it like this: aic7xx no_probe This will _enable_ EISA/VL probing even without AIC7XXX_PROBE_EISA_VL enabled in the kernel config, so you could use the standard provided modules without recompiling the kernel. >>> VFS: Can't find a Minix or Minix V2 filesystem on device 08:01. >>> >>> >> The last line looks a bit suspicious, it has nothing todo with the scsi >> driver but something is not working properly. > > No, it's right. The drives aren't Minix filesystems. > > >> I wonder where you found that stuff, the only place I know of with some >> old cruft is the >> "http://leaf.cvs.sourceforge.net/leaf/src/bering-uclibc/configs/"; >> directory. But this directory can only be removed by the sourceforge > staff. >> All sources (up to date) are in the >> "http://leaf.cvs.sourceforge.net/leaf/src/bering-uclibc/apps/"; >> directory. > > I was just looking under every rock that looked like it might hide > something interesting. My suggestion would be README files in the first > few levels of directories identifying contents and pointers to alternative > locations for similar or updated content. > A better option is to remove the obsolete content.... >> Yup, I was about to remove that option from the kernel config ;-) >> > > No, I think that would be a mistake. (Now I need to edit root.blk to add > SCSI CDROMs.) The thing is, many of us don't buy into the "Detroit > Paradigm" of upgrading HW/SW vendors try to sell users on. Faster isn't > necessarily better, especially when it comes bundled with the expensive > latest version of, umm, "bloatware". ;-) When one has older hardware, it > may be necessary or desireable to use contemporaneous software. It can be > very frustrating when it's all been dumped into the bit-bucket. I'm still > using Bering-1.2 on my firewall. It doesn't seem to be broke, and I don't > really want to suffer the outage for doing the upgrade. Something could > happen. > I won't remove it ;-)) >>> to miss clues. But ya' know, in my entire career, error messages > have >>> NEVER been as helpful as they need to be and they've never gotten any >>> better. > > And that's been a while. You might be amazed about the first computer I > programmed: > http://www.xprt.net/~pgrogers/Ibm1620.html > Time goes fast.... > > > Paul Rogers ([EMAIL PROTECTED]) > http://www.xprt.net/~pgrogers/ > http://www.geocities.com/paulgrogers/ > Rogers' Second Law: "Everything you do communicates." > (I do not personally endorse any additions after this line. TANSTAAFL > :-) > > Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
