Linux-kernel mailing list archive 1999-20,: Re: host (multibus) failover

# Re: host (multibus) failover

Chris Smith (cd_smith@ou.edu)
Mon, 17 May 1999 17:01:34 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alexandre Hautequest: "make: *** [_mod_drivers] Error 2 in 2.3.3"
- Previous message: Chris Zwilling: "2.3.3 st.h fix"
- Next in thread: Pavel Machek: "Re: host (multibus) failover"
- Reply: Pavel Machek: "Re: host (multibus) failover"
- Reply: Pavel Machek: "Re: host (multibus) failover"

Pavel Machek wrote:
> PS: Almost no kernel hacking should be required. I believe everything
> is there and "only" userland scripts + configuration should be
> required. (Which does not mean task is easy.)

Huh? How so? I was expecting to do most of my work in kernel space, since
I'm essentially writing a block device driver (one that simply forwards to
other block drivers). Can you clarify how this is doable in user space?

Thanks,
Chris Smith

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Alexandre Hautequest: "make: *** [_mod_drivers] Error 2 in 2.3.3"
- Previous message: Chris Zwilling: "2.3.3 st.h fix"
- Next in thread: Pavel Machek: "Re: host (multibus) failover"
- Reply: Pavel Machek: "Re: host (multibus) failover"
- Reply: Pavel Machek: "Re: host (multibus) failover"