Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: association between device and module name
- To: <tlug@example.com>
- Subject: Re: association between device and module name
- From: "roylo" <roylo@example.com>
- Date: Sun, 2 Sep 2001 17:20:26 -0700
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain;charset="iso-8859-1"
- Delivered-To: tlug@example.com
- List-Help: <mailto:tlug-request@example.comsubject=help>
- List-Post: <mailto:tlug@example.com>
- List-Subscribe: <mailto:tlug-request@example.comsubject=subscribe>
- List-Unsubscribe: <mailto:tlug-request@example.comsubject=unsubscribe>
- Old-Return-Path: <roylo@example.com>
- References: <Pine.GSO.4.05.10109021617510.18641-100000@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <LU2S_C.A.BUG.Hzsk7@example.com>
- Resent-Sender: tlug-request@example.com
I was thinking about the same thing when I answered his question. so I wrote a shell script for it afterwards. :P Anyway, I guess most of the *nix SA will do the same (ie either write a perl or shell script for anything we need) after all, *nix SA are smarter and can do things like that ourself. So I guess that is why no one asked for it. {I'm not saying M$ windoz SA are dumber; however, I do look down on them from time to time :P } ----- Original Message ----- From: "Scott M. Stone" <sstone@example.com> To: "Tokyo Linux Users' Group" <tlug@example.com> Sent: Sunday, September 02, 2001 4:19 PM Subject: association between device and module name > > Well in my quest to find an association between "eth0" and "3c59x", for > example, I found that: > > struct netdevice {} > > contains an "owner" field which contains the name of the module. problem > is, this sturcture and associated functions are local to kernel space. > > So i guess I'll have to write a kernel module which goes through each > netdevice with a get_dev_by_index or what have you, and creates a /proc > file with entries like: > > 1:eth0:3c59x > > ie, ifIndex:ifDevName:ifModName > > looks do-able. I'm just surprised nobody's ever seen the need for this > before. > > -------------------------- > Scott M. Stone <sstone@example.com> > Director of Information Technology, Director of Research and Development > ITIsOpen, Inc. - http://www.itisopen.com > Cisco Certified Network Associate, Sun Solaris Certified Systems Administrator > > ----------------------------------------------------------------------- > Next Technical Meeting: Sat, Sep 15 13:30- Leading Edge Co., Place Canada > Next Nomikai Meeting: Fri, Oct 19 19:30- Tengu Tokyo Eki-Mae > ----------------------------------------------------------------------- > more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- Follow-Ups:
- Re: association between device and module name
- From: "Scott M. Stone" <sstone@example.com>
- References:
- association between device and module name
- From: "Scott M. Stone" <sstone@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: pump failing to obtain IP
- Next by Date: Re: association between device and module name
- Prev by thread: association between device and module name
- Next by thread: Re: association between device and module name
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links