*snip*
I'll keep this off the list, since my question is one of those
doh!-things.
You haven't by any chance assigned _ANY_ lun to the default (i.e.
not-named) view? Doing so will give exactly the behavior you described.
Don't ask if I discovered this the hard way...
//Svein
--
On 10.04.2011 17:37, Svein Skogen (Listmail account) wrote:
*snip*
I'll keep this off the list, since my question is one of those
doh!-things.
You haven't by any chance assigned _ANY_ lun to the default (i.e.
not-named) view? Doing so will give exactly the behavior you described.
Don't
-Original Message-
From: Gary Driggs [mailto:gdri...@gmail.com]
Sent: Sunday, April 10, 2011 1:29 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Question about restricting visibility
ofcomstar targets
LUN 0: There is one LUN which is required to exist in
On Apr 10, 2011, at 10:35 AM, Dan Swartzendruber wrote:
*** Okay, but this doesn't answer my question - e.g. the docs seem to say
that proper use of view, host groups, etc, will restrict which LUNs are
visible to which initiators, but I am not seeing that behavior.
Are you using static,
Thanks for the links.
I was looking more for something which does not require MS windows.
Tight home dir control is what I also used. But keeping up with all the
desktop settings and trying to find how to control things, feels like
working backwards.
If people are serious about opensource in the
On 2011-04-10 16:47, Nikola M. wrote:
On 04/ 9/11 01:24 PM, Robin Axelsson wrote:
Hi,
I just discovered that the system simply won't boot when there is no
keyboard present, all I see is a dead boot splash without the rolling
orange sausage.
The intention of the system is to run it as a
