From: Richard Hirst <rhirst@linuxcare.com>
To: "Neulinger, Nathan" <nneul@umr.edu>
Cc: "'parisc-linux@lists.parisc-linux.org'"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] HP-UX binary compatibility
Date: Fri, 5 Oct 2001 15:04:02 +0100 [thread overview]
Message-ID: <20011005150402.P11105@linuxcare.com> (raw)
In-Reply-To: <6CAC36C3427CEB45A4A6DF0FBDABA56D86D865@umr-mail03.cc.umr.edu>; from nneul@umr.edu on Thu, Oct 04, 2001 at 04:16:52PM -0500
On Thu, Oct 04, 2001 at 04:16:52PM -0500, Neulinger, Nathan wrote:
> Got a question of how best to do something - flexlm does the lanscan style
> open of /dev/lan, /dev/lan0...15 to try and figure out the local hardware
> address of the machine:
>
> 24240: open("/dev/lan", O_RDONLY) = -1 ENOENT (No such file or directory)
> 24240: open("/dev/lan", O_RDONLY) = -1 ENOENT (No such file or directory)
> 24240: open("/dev/lan0", O_RDONLY) = 9
> 24240: ioctl(9 [/dev/lan0], NETSTAT, 0x7b03bc28) = 0
> 24240: sigprocmask(2, 0x7b038a80, 0x7b03cf28) = 0
> 24240: sigprocmask(2, 0x7b03cf28, 0) = 0
> 24240: close(9 [/dev/lan0]) = 0
> 24240: time(0) = 0x3bbcd084
> 24240: write(1 [fluent.log], 0x7b028000, 66) = 66
>
> What do y'all think is the best way of dealing with this? I could add the
> wrapper that traps the open system call, and then special case handle an
> open of /dev/lan*, and somehow keep track of that file descriptor in a
> global var of some sort, and then test for that fd in a wrapped ioctl
> handler?
>
> Or would there be some nicer way of dealing with this?
>
> Then again, I suppose I could also just return legit info on any NETSTAT
> ioctl on any open fd and just have the open of /dev/lan really open
> /dev/null. That might be the simplest way to get it working.
One alternative approach might be to load a kernel module that provides
a driver for /dev/lan.
next prev parent reply other threads:[~2001-10-05 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 21:16 [parisc-linux] HP-UX binary compatibility Neulinger, Nathan
2001-10-05 14:04 ` Richard Hirst [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-05 15:14 Neulinger, Nathan
2001-10-06 7:58 ` Helge Deller
2001-10-04 20:56 Neulinger, Nathan
2001-10-04 17:58 Neulinger, Nathan
2001-10-04 20:10 ` Matthew Wilcox
2001-10-04 15:07 Neulinger, Nathan
2001-10-05 8:17 ` Helge Deller
2001-10-04 11:56 John Marvin
2001-10-04 12:43 ` Nathan Neulinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011005150402.P11105@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=nneul@umr.edu \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox