Linux-kernel mailing list archive 2000-06,: Re: SCSI Makefile cleanup

# Re: SCSI Makefile cleanup

Jeff Garzik (jgarzik@mandrakesoft.com)
Tue, 08 Feb 2000 05:49:58 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Anton Ivanov: "Re: Gigabit Linux Server Bottlenecks"
- Previous message: Alan Cox: "Re: Source Code Release of NWFS 2.0 for 2.2/2.3/2.4"
- Maybe in reply to: willy@thepuffingroup.com: "SCSI Makefile cleanup"
- Next in thread: david parsons: "Re: SCSI Makefile cleanup"

david parsons wrote:
> I'd be tempted to just leave the modules they way they work now,
> because in most cases module loading lets you shoot yourself in the
> foot (except, for no apparent reason, ethernet modules, where a lot
> of 'em won't autoprobe because The Computer Knows What's Best.
> Sigh.) today, and someone may actually want to take advantage of
> one module stepping all over anothers address space.

modern ethernet hardware is PCI, and autoprobes. though I do agree --
typically one should specify ethXX assign with "alias ethXX my_driver"
in conf.modules.

Jeff

    --
    Jeff Garzik         | Old SysOps never die, they simply
    Building 1024       | forgot their own passwords.
    MandrakeSoft, Inc.  |

    -
    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: Anton Ivanov: "Re: Gigabit Linux Server Bottlenecks"
- Previous message: Alan Cox: "Re: Source Code Release of NWFS 2.0 for 2.2/2.3/2.4"
- Maybe in reply to: willy@thepuffingroup.com: "SCSI Makefile cleanup"
- Next in thread: david parsons: "Re: SCSI Makefile cleanup"