Re: mach's eatadma driver hangs on my box
On Sat, Oct 14, 2000 at 10:37:54PM +0200, Robert Bihlmeyer wrote:
> Steve Bowman <firstname.lastname@example.org> writes:
> > There seem to be a few driver conflicts in the default build. IMHO,
> > the best thing is to build your own rather than start disabling things
> > since someone else may need it to get started.
> Sure - I already built a minimal kernel. But IMHO there should be
> pre-built kernels for (almost) all configurations. Its clear that one
> kernel won't cut it (there are no modules, are there?). The current
> deb already has a couple of ncr drivers disabled. I just wanted to
> provide a datapoint - if more people reported that eatadma was a
> problem for them, it should also be disabled per default, with
> alternative kernels providing bootstrap support for those needing the
> dangerous drivers.
Not a bad idea actually if we don't have to provide too many options
to choose from. If I can ever get around to tracking down the conflict
with viarhine, I can provide another datapoint.
> The most obvious first cut is probably to have a ide version without
> any scsi drivers.
> > I'm a relative newcomer to hurd, but there was a lot of list traffic
> > on this topic a month ago or so. from what I gathered, most ppl are
> > building gnumach on linux.
> Thanks, I just thought it was no longer supported, because
> "debian/rules build" did not work out-of-the-box.
You're welcome :-).
Steve Bowman <email@example.com> (preferred)
Buckeye, AZ <firstname.lastname@example.org> <email@example.com>
Powered by Debian GNU/Linux and GNU/Hurd <http://www.debian.org>