Thread: [Madwifi-users] Slackware rc.inet1/rc.wireless
Status: Beta
Brought to you by:
otaku
From: Richard C. <ric...@ho...> - 2005-03-25 10:16:31
|
I'm using slackware 10.1, and in the start up scripts for networks, it presumes that all Ethernet devices will begin with 'eth'. However, the device loaded with Madwifi was 'ath'. I'm using CVS from Wed 22nd March - and to solve this problem I made the following change: cvs diff: Diffing . Index: if_ath_pci.c =================================================================== RCS file: /cvsroot/madwifi/madwifi/ath/if_ath_pci.c,v retrieving revision 1.7 diff -u -r1.7 if_ath_pci.c --- if_ath_pci.c 16 Feb 2005 16:08:41 -0000 1.7 +++ if_ath_pci.c 25 Mar 2005 10:11:39 -0000 @@ -177,7 +177,7 @@ sc->aps_sc.sc_invalid = 1; dev = &sc->aps_sc.sc_dev; /* XXX blech, violate layering */ - memcpy(dev->name, "ath%d", sizeof("ath%d")); + memcpy(dev->name, "eth%d", sizeof("eth%d")); dev->irq = pdev->irq; dev->mem_start = mem; Is there an alternative way of solving this? Will this affect other behaviour? Cheers, Richard -- -- Richard Corden |
From: Alvin O. <alvin@Mail.Linux-Consulting.com> - 2005-04-04 22:37:07
|
hi ya On Fri, 25 Mar 2005, Richard Corden wrote: > I'm using slackware 10.1, and in the start up scripts for networks, it > presumes that all Ethernet devices will begin with 'eth'. However, the > device loaded with Madwifi was 'ath'. .. > Is there an alternative way of solving this? Will this affect other > behaviour? i normally startup slackware deamons/configs from /etc/rc.d/rc.* scripts rc.wireless ( aka wl.install.sh in my box ) http://www.Linux-Wireless.org/Install-HOWTO/WL/ http://www.Linux-Wireless.org/Wireless/Install-HOWTO/other-howto/ c ya alvin |
From: Mike D. <mik...@nr...> - 2005-04-05 13:27:16
|
On Fri, 25 Mar 2005 10:16:07 +0000 Richard Corden <ric...@ho...> wrote: > > I'm using slackware 10.1, and in the start up scripts for networks, it > > presumes that all Ethernet devices will begin with 'eth'. However, > the device loaded with Madwifi was 'ath'. > You could edit the startup scripts to use the new interface name. Eric has excelent modified versions at http://sox.homeip.net/slackware-10.1.IHWhqM/ Just use the modified versions of rc.inet1 and rc.inet1.conf in place of the the Slackware originals. Mike -- Mike Denhoff gpg public key: http://istop.com/~denhoff/gpg/mike.denhoff.gpg gpg signature info: http://www.gnupg.org |
From: Richard C. <ric...@pr...> - 2005-04-05 20:49:41
|
Mike Denhoff wrote: >On Fri, 25 Mar 2005 10:16:07 +0000 >Richard Corden <ric...@ho...> wrote: > > > >>I'm using slackware 10.1, and in the start up scripts for networks, it >> >>presumes that all Ethernet devices will begin with 'eth'. However, >>the device loaded with Madwifi was 'ath'. >> >> >> >You could edit the startup scripts to use the new interface name. Eric >has excelent modified versions at > >http://sox.homeip.net/slackware-10.1.IHWhqM/ > >Just use the modified versions of rc.inet1 and rc.inet1.conf in place of >the >the Slackware originals. > > I'm not sure that either of these suggestions are really great - since they are only viable against a particular version...and upgrading may be problematic. I think a module option would be the most useful, alternatively keep the name 'eth' as all other 'ethernet' devices uses. Why change it anyway? Richard -- Richard Corden Programming Research Ltd. ric...@pr... + 353 1 497 8012 |
From: Mike D. <mik...@nr...> - 2005-04-06 13:38:51
|
On Tue, 05 Apr 2005 20:47:22 +0000 Richard Corden <ric...@pr...> wrote: > Mike Denhoff wrote: > >> You could edit the startup scripts to use the new interface name. >Eric> has excelent modified versions at >> >> http://sox.homeip.net/slackware-10.1.IHWhqM/ >> <http://sox.homeip.net/slackware-10.1.IHWhqM/> >> That would be Eric Hameleers. >> >> Just use the modified versions of rc.inet1 and rc.inet1.conf in place >of> the Slackware originals. > > > I'm not sure that either of these suggestions are really great - since > they are only viable against a particular version...and upgrading may > be problematic. > > I think a module option would be the most useful, alternatively keep > the name 'eth' as all other 'ethernet' devices uses. Why change it > anyway? > > Richard > So the choice is whether to change the startup scripts or edit the madwifi code. I don't have a strong opinion here. I wonder what the madwifi developers think about changing ath to eth. I kind of like the wireless interface having a different name than the wired. I guess that a modified rc.inet1, similar to the one I linked to above, may turn up in Slackware soon, since the present rc.wireless was modified by Eric Hamleers. Mike -- Mike Denhoff gpg public key: http://istop.com/~denhoff/gpg/mike.denhoff.gpg gpg signature info: http://www.gnupg.org |
From: Michael R. <ma...@no...> - 2005-04-06 13:43:30
|
Hi. Mike Denhoff wrote: > I wonder what the madwifi developers think about changing ath to eth. Sebastian just committed my patch (the one that allows to change the interface name to something other than "ath") into the BSD branch. I'll also commit it to HEAD when I find the time. Bye, Mike |
From: Michael R. <ma...@no...> - 2005-04-06 06:56:15
|
Hi. Richard Corden wrote: > I'm using slackware 10.1, and in the start up scripts for networks, it > presumes that all Ethernet devices will begin with 'eth'. However, the > device loaded with Madwifi was 'ath'. http://article.gmane.org/gmane.linux.drivers.madwifi.devel/856 could be of help. The patch introduces a module parameter to define the name of the interface and lists several other possibilities to rename an interface after it becomes visible to the system. Bye, Mike |