On Sat, 2010-06-26 at 10:36 -0700, W. Wayne Liauh
wrote:
Hi Alex,
Sorry for forking the question, but have you
recently had any success in booting Milax 0.5 from
its vdi image? I keep getting the WARNING: init(1M)
exited on fatal signal 9, restarting automatically
message? Updating
On Sat, 2010-06-26 at 10:36 -0700, W. Wayne Liauh wrote:
Hi Alex,
Sorry for forking the question, but have you recently had any success in
booting Milax 0.5 from its vdi image? I keep getting the WARNING: init(1M)
exited on fatal signal 9, restarting automatically message? Updating
I haven't tried USB boot on that laptop -- it does have 1 USB 1.1 port, it's an
IBM thinkpad 600x. I don't own any usb / thumb drives and haven't taken the
time to figure out how to do a usb boot (if it's even possible). Sorry.
However, on the livecd the error message it gives after
module
Hi Alex,
Sorry for forking the question, but have you recently had any success in
booting Milax 0.5 from its vdi image? I keep getting the WARNING: init(1M)
exited on fatal signal 9, restarting automatically message? Updating Oracle
VirtualBox to the 3.2.6 did not help.
No problem booting
Anyone tried the latest Milax ISO on an old machine with 256M of memory? I
just tried that as an experiment and regardless if I choose text console
or regular boot it fails with can not start console login services and
then the usual blurb about check svcs -xv. Of course if I do login in
As a matter of fact (or coincidence?) I do have a laptop with 256mb of ram and
tried to boot Milax 0.5 just last weekend. It wouldn't boot due to some issue
with compression or uncompressing files. I think I tried it with the vesa
driver also, same error message.
It's currently running
As a matter of fact (or coincidence?) I do have a laptop with 256mb of ram
and tried to boot Milax 0.5 just last weekend. It wouldn't boot due to
some issue with compression or uncompressing files. I think I tried it
with the vesa driver also, same error message.
It's currently running
Could you please write what's the messages
on console before console-service error,
I'll try to investigate this (I haven't problems
with 0.5 in VBox with 256MB RAM).
Thanks for this,
Alex
--
This message posted from opensolaris.org
___
Also, if this old box has USB port,
could you test USB-boot?
Thanks,
Alex
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
As a matter of fact (or coincidence?) I do have a
laptop with 256mb of ram
and tried to boot Milax 0.5 just last weekend. It
wouldn't boot due to
some issue with compression or uncompressing files.
I think I tried it
with the vesa driver also, same error message.
It's currently
snip
This thread has only academic interest nowadays. Hardware is cheap
you time is not.
Well experimentation for the sake of testing small embedded solutions is
hardly a waste of my time.
Dennis
___
opensolaris-discuss mailing list
is under 256 MB. Still enough for today's
embedded Y2K purposes. I think the engineering quote was 384 MB RAM minimum
(512MB roughly).
~ Ken Mays
--- On Fri, 6/25/10, Dennis Clarke dcla...@blastwave.org wrote:
From: Dennis Clarke dcla...@blastwave.org
Subject: Re: [osol-discuss] Milax 0.5 boot
snip
This thread has only academic interest nowadays.
Hardware is cheap
you time is not.
Well experimentation for the sake of testing small
embedded solutions is
hardly a waste of my time.
I didn't mean to imply this; I haven't been there yet, no idea where Solaris
would be suitable
13 matches
Mail list logo
