Thanks a lot Rao. I'll do that

Regards
Ramakrishnan 

-----Original Message-----
From: Rao Shoaib [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 17, 2007 12:52 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: [networking-discuss] File I/O from STREAMS module

In this case your only option seems to be to use vn_open() and read the
file. See ncaportconf_read() in common/fs/sockfs/nl7c.c for an example.

Rao.

Ramakrishnan Meenakshi Sundaram wrote:
> I'm writing a stream module that sits below the IP layer and does 
> packet interception.
>
> Can driver.conf be used for STREAMS modules to read the configuration 
> parameters?
>
> Regards
> Ramakrishnan
>
> -----Original Message-----
> From: Rao Shoaib [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 17, 2007 11:55 AM
> To: [EMAIL PROTECTED]
> Cc: [email protected]
> Subject: Re: [networking-discuss] File I/O from STREAMS module
>
> I am assuming that you want to read in some configuration parameters, 
> if so, do a man on driver.conf(4) and on ddi_prop_get_int(9F).
>
> Rao.
>
> Ramakrishnan Meenakshi Sundaram wrote:
>   
>> Hi all,
>>  
>> I'm a newbie writing a STREAMS module, that will be part of the 
>> network stack. It needs to read a configuration file to do its work.
>>  
>> I'm not sure how to open and read a file from inside a STREAMS module.
>>  
>> Since the online docs suggested uarea will be accessible from 
>> module's open method, i tried file i/o from that method, it fails 
>> reporting Bad Address
>>  
>> I'm not sure how to use the M_COPYIN and M_COPYOUT, IOCTL messages to 
>> read a file, as it is mentioned that these will be used to access the 
>> user space.
>>  
>> Kindly guide me.
>>  
>> FYI : Sorry if you receive a couple of mails with same contents. 
>> After i received an instruction saying this is a members only mailing 
>> list.I subscribed to it. So, I'm forwarding this mail again.
>>  
>> regards
>> Ramakrishnan
>> ---------------------------------------------------------------------
>> -
>> --
>>
>> _______________________________________________
>> networking-discuss mailing list
>> [email protected]
>>   
>>     
> _______________________________________________
> networking-discuss mailing list
> [email protected]
>   
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to