I had a few minutes to poke around, and I found the problem (at last!).
The log never really showed anything, but it finally made me question
something.
The /etc/hosts file that I've used since 151a1 needed changing. It seems
rules have tightened up. Quite simply, you can no longer have the
h
On 11/26/2013 5:22 PM, Jim Klimov wrote:
On 2013-11-27 02:00, Rainer Heilke wrote:
This is what I would expect with NWAM disabled. But I explicitly do
*not* want to use NWAM.
As a side note, network/physical:default _does_ bring up my secondary
interface e1000g1, which will be used for my two S
On 2013-11-27 02:00, Rainer Heilke wrote:
This is what I would expect with NWAM disabled. But I explicitly do
*not* want to use NWAM.
As a side note, network/physical:default _does_ bring up my secondary
interface e1000g1, which will be used for my two SunRays. e1000g0 is
supposed to be 192.168.
On 11/22/2013 1:35 AM, Stefan Müller-Wilken wrote:
Hi Rainer,
Yep. Didn't work for me, as I need the system to boot right into a
networking state. Like all of the NWAM documentation I found, I had to
log in before the networking came up.
what do you mean by 'boot into a networking state'? Sim
On 2013-11-26 17:25, Jim Klimov wrote:
On 2013-11-17 03:50, Jim Klimov wrote:
For years I've mentioned "split-root" installations of Solaris-like
systems in such a way that the root filesystem (the BE) is represented
by several datasets, such as a split-off /usr dataset. Also there may
be som
On 2013-11-27 00:34, Lionel Cons wrote:
function nanosort { typeset -A a ; integer k=0; while read i ;
do key="$i$((k++))" a[$key]="$i" ; done ; printf "%s\n" "${a[@]}" ; }
Nifty, thanks! :)
//Jim
___
OpenIndiana-discuss mailing list
OpenIndiana-di
On 26 November 2013 19:23, Irek Szczesniak wrote:
> On Tue, Nov 26, 2013 at 7:07 PM, Jim Klimov wrote:
>> On 2013-11-26 17:25, Jim Klimov wrote:
>>>
>>> On 2013-11-17 03:50, Jim Klimov wrote:
For years I've mentioned "split-root" installations of Solaris-like
systems in such a w
On 2013-11-26 23:57, Rainer Heilke wrote:
Both usr:live-media *and* usr:default were enabled. Disabling
usr:live-media killed the bootup completely. Couldn't even use ESC to
get to the console. I'll have to start from scratch.
BTW, just for cases like this people use "beadm create" to make
some
Thanks for the reply, some answers/couter-arguments are below :)
On 2013-11-26 23:51, Peter Tribble wrote:
Here, you're solving the wrong problem. Just put the drivers in the right
place from the start. I've never understood why drivers were scattered.
This might be out of admin's control some
On 11/26/2013 2:44 PM, Jim Klimov wrote:
On 2013-11-26 23:30, Rainer Heilke wrote:
Yep. Told it to use the whole (650MB) disk, left the DVD in after the
reboot so it could finish it's stuff. Then I rebooted again, popped the
DVD out, and booted from the harddrive. Same as I used to always do.
I
On 11/26/2013 1:57 PM, Peter Tribble wrote:
On Tue, Nov 26, 2013 at 9:25 PM, Rainer Heilke wrote:
It looks like it did confuse at least one service:
rheilke@hastur:~$ svcs -xv
svc:/system/filesystem/root:media (root file system mount)
State: offline since November 25, 2013 07:59:32 PM PST
R
On Tue, Nov 26, 2013 at 10:19 PM, Jim Klimov wrote:
>
> I wonder how (un)acceptable would it be to enhance the fs-root script
> instead - when it makes sure that /usr/bin is available (the /usr is
> mounted), it could invoke "svcadm restart" of the active instance of
> the network/physical servic
On 2013-11-26 23:31, Stefan Müller-Wilken wrote:
Hi Jim,
first of all thanks for your efforts! Although I don't have a clear picture
here, my biggest concern would be breaking upstream compatibility for fairly
special case. Would we run that risk?
I wonder what those cases might be - brains
On 2013-11-26 23:30, Rainer Heilke wrote:
Yep. Told it to use the whole (650MB) disk, left the DVD in after the
reboot so it could finish it's stuff. Then I rebooted again, popped the
DVD out, and booted from the harddrive. Same as I used to always do.
I've done the live upgrades for the last few
On 11/26/2013 1:50 PM, Jim Klimov wrote:
On 2013-11-26 22:25, Rainer Heilke wrote:
It looks like it did confuse at least one service:
rheilke@hastur:~$ svcs -xv
svc:/system/filesystem/root:media (root file system mount)
State: offline since November 25, 2013 07:59:32 PM PST
Reason: Dependency
Hi Jim,
first of all thanks for your efforts! Although I don't have a clear picture
here, my biggest concern would be breaking upstream compatibility for fairly
special case. Would we run that risk?
Cheers
Stefan
Von: Jim Klimov [jimkli...@cos.ru]
Gese
On 2013-11-26 19:23, Irek Szczesniak wrote:
cut, cat and grep are ksh builtins. Use builtin (run builtin
--man to read details) to enable them by default and then remove the
absolute paths so the shell doesn't search PATH for them.
Most nawk usage can be replaced by ksh pattern matching, leaving
On Tue, Nov 26, 2013 at 9:25 PM, Rainer Heilke wrote:
> It looks like it did confuse at least one service:
>
> rheilke@hastur:~$ svcs -xv
> svc:/system/filesystem/root:media (root file system mount)
> State: offline since November 25, 2013 07:59:32 PM PST
> Reason: Dependency svc:/system/filesyst
On 2013-11-26 22:25, Rainer Heilke wrote:
It looks like it did confuse at least one service:
rheilke@hastur:~$ svcs -xv
svc:/system/filesystem/root:media (root file system mount)
State: offline since November 25, 2013 07:59:32 PM PST
Reason: Dependency svc:/system/filesystem/root-minimal:defaul
While I don't split-root install, the fact that the post-install script
didn't run correctly (at all?) and I had the root filesystem error would
undoubtedly have "lost" where /usr was as well. This is making sense now.
Rainer
On 11/26/2013 7:57 AM, Jim Klimov wrote:
On 2013-11-26 12:55, Jim K
It looks like it did confuse at least one service:
rheilke@hastur:~$ svcs -xv
svc:/system/filesystem/root:media (root file system mount)
State: offline since November 25, 2013 07:59:32 PM PST
Reason: Dependency svc:/system/filesystem/root-minimal:default is absent.
See: http://illumos.org/msg/
On Tue, Nov 26, 2013 at 7:07 PM, Jim Klimov wrote:
> On 2013-11-26 17:25, Jim Klimov wrote:
>>
>> On 2013-11-17 03:50, Jim Klimov wrote:
>>>
>>>For years I've mentioned "split-root" installations of Solaris-like
>>> systems in such a way that the root filesystem (the BE) is represented
>>> by
On 2013-11-26 17:25, Jim Klimov wrote:
On 2013-11-17 03:50, Jim Klimov wrote:
For years I've mentioned "split-root" installations of Solaris-like
systems in such a way that the root filesystem (the BE) is represented
by several datasets, such as a split-off /usr dataset. Also there may
be som
On Tue, Nov 26, 2013 at 4:25 PM, Jim Klimov wrote:
> On 2013-11-17 03:50, Jim Klimov wrote:
>
>>For years I've mentioned "split-root" installations of Solaris-like
>> systems in such a way that the root filesystem (the BE) is represented
>> by several datasets, such as a split-off /usr datase
On Tue, Nov 26, 2013 at 5:25 PM, Jim Klimov wrote:
> On 2013-11-17 03:50, Jim Klimov wrote:
>>
>>For years I've mentioned "split-root" installations of Solaris-like
>> systems in such a way that the root filesystem (the BE) is represented
>> by several datasets, such as a split-off /usr datase
On 2013-11-17 03:50, Jim Klimov wrote:
For years I've mentioned "split-root" installations of Solaris-like
systems in such a way that the root filesystem (the BE) is represented
by several datasets, such as a split-off /usr dataset. Also there may
be some datasets shared between boot environme
On 2013-11-26 12:55, Jim Klimov wrote:
I think I can somewhat confirm Rainer's problems with NWAM:
I've created an oi_151a8 installation in VirtualBox (for my
tests about split-root installation procedure), which is a
stock installation by the wizard with minimal "deviations"
(only the FS layout
On 2013-11-25 08:18, Stefan Müller-Wilken wrote:
Morning Rainer,
sorry to hear your understandable disappointment. But I'd still be willing to
help diagnosing the network problem if you'd share the output of nwamcfg, dladm
et cetera.
I think I can somewhat confirm Rainer's problems with NWA
On Tue, Nov 26, 2013 at 10:21 AM, Rainer Heilke wrote:
> I'm trying to clean up this error:
> rheilke@hastur:~$ svcs -xv
> svc:/system/filesystem/root:media (root file system mount)
> State: maintenance since November 25, 2013 03:10:44 PM PST
> Reason: Start method exited with $SMF_EXIT_ERR_FATAL
On 26 нояб. 2013 г., at 14:35, Rainer Heilke wrote:
>
> I'm going to bed right now, but what does this do, set my system to try to
> boot in minimal state? And then what? The OS is already installed.
Installed but still use boot services from LiveCD, where logic of mounting root
and usr filesy
I'm going to bed right now, but what does this do, set my system to try
to boot in minimal state? And then what? The OS is already installed.
Rainer
On 11/26/2013 2:30 AM, Alexander Eremin wrote:
svcadm disable root:media usr:media sysidcfg:live-media root-minimal
svcadm enable root:default us
The system remains in "Cylon Mode" with the white bar. The ESC button
doesn't even get me to the console. It never finishes booting.
Rainer
On 11/26/2013 2:22 AM, Alexander Eremin wrote:
As Peter said, you don't need this file on installed system. What exactly do you mean for "no
longer boot"
svcadm disable root:media usr:media sysidcfg:live-media root-minimal
svcadm enable root:default usr:default
svcadm enable sysidcfg:system sysidcfg:net
See
http://wiki.openindiana.org/oi/Advanced+-+Manual+installation+of+OpenIndiana+from+LiveCD+media
Alexander
> On 26 нояб. 2013 г., at 14:21, Ra
As Peter said, you don't need this file on installed system. What exactly do
you mean for "no longer boot"? Are you tried to boot with "-m milestone=none"
for example?
Alexander
> On 26 нояб. 2013 г., at 14:09, Rainer Heilke wrote:
>
> The LiveCD did have the file, but when I copied it to / o
I'm trying to clean up this error:
rheilke@hastur:~$ svcs -xv
svc:/system/filesystem/root:media (root file system mount)
State: maintenance since November 25, 2013 03:10:44 PM PST
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://illumos.org/msg/SMF-8000-KS
See: /var/svc/log
The LiveCD did have the file, but when I copied it to / on the server,
it would no longer boot.
Rainer
On 11/26/2013 1:10 AM, Stefan Müller-Wilken wrote:
Good to hear we're getting closer to the root cause. :-)
Can you mayberecheck your ISO image? I have a oi-dev-151a8-text-x86.iso
downloade
On Tue, Nov 26, 2013 at 9:03 AM, Rainer Heilke wrote:
> I've found the beginnings of my problems (thanks, Stefan). The 151a8
> LiveCD did not lay down a /.volsetid on my root filesystem (rpool). The one
> on the LiveCD doesn't work. So, how do I create one (with the right value)
> from scratch? I
Good to hear we're getting closer to the root cause. :-)
Can you mayberecheck your ISO image? I have a oi-dev-151a8-text-x86.iso
downloaded yesterday and unpacked a minute ago and it contains a .volsetid
file. Would be surprised if it was missing in the UI version of the ISO.
Cheers
Stefan
___
I've found the beginnings of my problems (thanks, Stefan). The 151a8
LiveCD did not lay down a /.volsetid on my root filesystem (rpool). The
one on the LiveCD doesn't work. So, how do I create one (with the right
value) from scratch? I don't think mkisofs will work.
TIA
Rainer
--
Mind the Gap
39 matches
Mail list logo
