Re: [ug-jposug] ndis-1.2.2で カーネル パニック

2009-03-16 Thread Masayuki Murayama
 ?
 
 ?
 ???ndis?hp mini  
 1000?
 myk?
 hp mini 1000?myk
 
 ??

?grub?
??
??PC (FM V6800MG)??OScardbus?
cardbus?opensolaris?CD?
??

???
??? myk ?update?Sun?Darren Kenny???8040??
?system shutdown??panic??
resume??sony
vaio??marvel?nic?device Id?
???web?prtconf??
??

??
-- 
This message posted from opensolaris.org


Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]

2009-03-16 Thread Wyllys Ingersoll

I exchanged email with the lead engineer for the Tor project and he told me that
Tor will use whatever it considers reasonable defaults if it doesn't find a 
config file (/etc/torrc).  So, instead of delivering a sample config file, 
I think it is better to deliver a working config file in /etc/torrc with 2 
ports 
enabled by default - 9050 for socks, and 9001 for the standard Tor relay 
connections.  
I will not deliver the sample file.  

Also, Tor may be configured to listen on privileged ports such as 443 if it is 
set up 
as a bridge relay, so it will need the priv_net_privaddr privilege in addition 
to the 
basic set, I will add this to the /usr/lib/tor entry in 
/etc/security/exec_attr.

I have updated the spec and put a copy in the case directory.  I've also
attached it to this email for reference.

-Wyllys

-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: tor-ft-2.txt
URL: 
http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090316/9cf1d3f1/attachment.txt


PSARC 2008/769 - Multiple disk sector size support

2009-03-16 Thread Rick Matthews
Larry Liu wrote:
 Hi Rick,

 Thanks for your suggestion. We made the changes accordingly. That 
 said, by default, sd(7D) will do RMW to misaligned I/O with warning 
 message. Custormers can configure the behavior as do RMW without 
 warning message and do not do RMW with error returned. The 
 configuration will be per device based (PSARC 2008/465 
 [s]sd-config-list). We don't have a mechanism to configure the 
 behavior per partition based.

 I attached the modified rmw design doc.

 Thanks,
 Larry

I am happier with the proposed changes. Thank you

-- 
-
Rick Matthews   email: Rick.Matthews at sun.com
Sun Microsystems, Inc.  phone:+1(651) 554-1518
1270 Eagan Industrial Road  phone(internal): 54418
Suite 160   fax:  +1(651) 554-1540
Eagan, MN 55121-1231 USAmain: +1(651) 554-1500  
-




Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]

2009-03-16 Thread Scott Rotondo
Wyllys Ingersoll wrote:
 
 I exchanged email with the lead engineer for the Tor project and he told 
 me that
 Tor will use whatever it considers reasonable defaults if it doesn't 
 find a config file (/etc/torrc).  So, instead of delivering a sample 
 config file, I think it is better to deliver a working config file in 
 /etc/torrc with 2 ports enabled by default - 9050 for socks, and 9001 
 for the standard Tor relay connections.  I will not deliver the sample 
 file. 
 Also, Tor may be configured to listen on privileged ports such as 443 if 
 it is set up as a bridge relay, so it will need the priv_net_privaddr 
 privilege in addition to the basic set, I will add this to the 
 /usr/lib/tor entry in /etc/security/exec_attr.
 

I'm confused. Isn't /usr/lib/tor started by an SMF service? I would 
think you'd need to specify the privilege in the service manifest rather 
than exec_attr.

Scott


-- 
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)



Tor [PSARC/2009/175 FastTrack timeout 03/19/2009]

2009-03-16 Thread Wyllys Ingersoll
Scott Rotondo wrote:
 Wyllys Ingersoll wrote:

 I exchanged email with the lead engineer for the Tor project and he 
 told me that
 Tor will use whatever it considers reasonable defaults if it doesn't 
 find a config file (/etc/torrc).  So, instead of delivering a sample 
 config file, I think it is better to deliver a working config file in 
 /etc/torrc with 2 ports enabled by default - 9050 for socks, and 9001 
 for the standard Tor relay connections.  I will not deliver the sample 
 file. Also, Tor may be configured to listen on privileged ports such 
 as 443 if it is set up as a bridge relay, so it will need the 
 priv_net_privaddr privilege in addition to the basic set, I will add 
 this to the /usr/lib/tor entry in /etc/security/exec_attr.

 
 I'm confused. Isn't /usr/lib/tor started by an SMF service? I would 
 think you'd need to specify the privilege in the service manifest rather 
 than exec_attr.
 
 Scott

Yes, correct, it needs to be added there as well.

-Wyllys