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 headless
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 e
-Original Message-
From: Gary Driggs [mailto:gdri...@gmail.com]
Sent: Sunday, April 10, 2011 1:59 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Question about restricting
visibilityofcomstar targets
On Apr 10, 2011, at 10:35 AM, "Dan Swartzendruber" wrote:
>
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, dy
-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 ever
"LUN 0: There is one LUN which is required to exist in every target: zero. The
logical unit with LUN zero is special in that it must implement a few specific
commands, most notably Report LUNs, which is how an initiator can find out all
the other LUNs in the target. But LUN zero need not provide
-Original Message-
From: Svein Skogen (Listmail account) [mailto:svein-listm...@stillbilde.net]
Sent: Sunday, April 10, 2011 11:38 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Question about restricting visibility of
comstar targets
*snip*
I'll keep this of
> "I also noticed that as soon as I insert the keyboard to the PS/2 port the
> orange sausage starts to roll and the system boots up, so it is as if the
> system is just sitting there waiting for a keyboard to say "Hello"."
>
> Does PS/2 support 'hotswap' as usb does?
>
> __
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
*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 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 headless file server but
> I had to at
-Original Message-
From: Svein Skogen (Listmail account) [mailto:svein-listm...@stillbilde.net]
Sent: Sunday, April 10, 2011 5:42 AM
To: openindiana-discuss@openindiana.org
Subject: Re: [OpenIndiana-discuss] Question about restricting visibility of
comstar targets
On 10.04.2011 03:44, Da
On 10.04.2011 03:44, Dan Swartzendruber wrote:
>
>
> Please forgive the imprecision here, as I don't have access to the machine
> in question at this point. I have a number of iSCSI targets I want to make
> visible to various client systems. I don't want any client to see any
> targets not int
13 matches
Mail list logo
