i tried the dtrace script, and i found that modunload is taking around 1 min. i
have attached the chart generated and the log file.
i tried disabling automount no success :(
--
This message posted from opensolaris.org___
indiana-discuss mailing
The answer is that your software is not correctly
packaged for
OpenSolaris 200x :)
Do you mind pointing out what exactly makes my software incorrectly packaged
for OpenSolaris?
Is there a formal specification document which details how and in what places
Indiana expects to have software
i tried the dtrace script, and i found that modunload
is taking around 1 min. i have attached the chart
generated and the log file.
Hmm, some of the hald commands show a strange delayed
start of about one minute...
Does your system have a ps/2 floppy drive, or is one
configured in the bios?
One solution is to create a little program that
utilizes the
isaexec API and accepts a pathname to an
executable.
See isaexec(3C).
Thanks Moinak.
I did exactly what you told me, and it worked, except that I replicated
/usr/lib/isaexec functionality.
As it turns out, a hard link is
I am trying to get OpenSolaris 2009.06 to run from my 32 GB Kingston
compact flash drive attached to a standard Sil 0680 IDE controller. The
installer detects the card and install successfully. Upon reboot, GRUB
drops to a grub prompt. Any attempts to read menu.lst fail with:
grub root
UNIX admin wrote:
The answer is that your software is not correctly
packaged for
OpenSolaris 200x :)
Do you mind pointing out what exactly makes my software incorrectly packaged
for OpenSolaris?
Is there a formal specification document which details how and in what places
Indiana expects to
James Lee wrote:
I am trying to get OpenSolaris 2009.06 to run from my 32 GB Kingston
compact flash drive attached to a standard Sil 0680 IDE controller. The
installer detects the card and install successfully. Upon reboot, GRUB
drops to a grub prompt. Any attempts to read menu.lst fail with:
Shawn Walker wrote:
UNIX admin wrote:
The answer is that your software is not correctly
packaged for OpenSolaris 200x :)
Do you mind pointing out what exactly makes my software incorrectly
packaged for OpenSolaris?
Is there a formal specification document which details how and in
what
Matt Ingenthron wrote:
Shawn Walker wrote:
UNIX admin wrote:
The answer is that your software is not correctly
packaged for OpenSolaris 200x :)
Do you mind pointing out what exactly makes my software incorrectly
packaged for OpenSolaris?
Is there a formal specification document which
Shawn Walker wrote:
Matt Ingenthron wrote:
Shawn Walker wrote:
UNIX admin wrote:
The answer is that your software is not correctly
packaged for OpenSolaris 200x :)
Do you mind pointing out what exactly makes my software
incorrectly packaged for OpenSolaris?
Is there a formal specification
Joseph J VLcek wrote:
With rpool imported/mounted can you cat the contents of the GRUB
menu.lst file? What does it contain?
e.g.: % cat /rpool/boot/grub/menu.lst
This question should probably be posted to install-disc...@opensolaris.org
Joe
Yes, I can cat the file just fine once
Hi James,
No answers from me, just some information.
The ability to boot from a disk greater than 1 TB integrated last fall
and this support is in the OpenSolaris 2009.06 release.
I see the same zio_read_data error (boot from install okay, but not
from the disk) in this CR:
6843138 can not
James Lee wrote:
Joseph J VLcek wrote:
With rpool imported/mounted can you cat the contents of the GRUB
menu.lst file? What does it contain?
e.g.: % cat /rpool/boot/grub/menu.lst
This question should probably be posted to install-disc...@opensolaris.org
Joe
Yes, I can cat the file just
On Thu, Jun 04, 2009 at 11:15:45AM -0700, Matt Ingenthron wrote:
Shawn Walker wrote:
Matt Ingenthron wrote:
Shawn Walker wrote:
As noted in:
PSARC/2005/185 Enabling serendipitous discovery
PSARC/2007/048 Include GNU coreutils 6.7
PSARC/1991/061 Packaging rules for system extensions
Matt Ingenthron wrote:
Shawn Walker wrote:
Matt Ingenthron wrote:
Shawn Walker wrote:
UNIX admin wrote:
The answer is that your software is not correctly
packaged for OpenSolaris 200x :)
Do you mind pointing out what exactly makes my software
incorrectly packaged for OpenSolaris?
Is there
Nicolas Williams wrote:
I myself am not sure where third-party pkgs should install into. FOSS
could always be integrated directly into OpenSolaris via the
consolidation process, or perhaps via /contrib, in which case it will
end up in /usr -- to me this argues for third parties packaging FOSS
a b wrote:
...many bits of software are moving to /usr :)
Deliver to /usr; your life will be simpler, many users will thank you,
and you won't have this issue.
Consider that if I deliver my software in /usr (as a 3rd party unbundled
applications vendor), I run an extremely high risk of:
...many bits of software are moving to /usr :)
Deliver to /usr; your life will be simpler, many users will thank you,
and you won't have this issue.
Consider that if I deliver my software in /usr (as a 3rd party unbundled
applications vendor), I run an extremely high risk of:
a) being
I disagree. For many of the same reasons stated in PSARC/2005/185, I
believe even third-party software belongs in /usr.
If you don't mind, would you please explain how software which enhances the OS
yet works in a different way (such as for example 3rd party clustering
software) would be
On Thu, Jun 04, 2009 at 04:34:52PM -0500, Shawn Walker wrote:
Nicolas Williams wrote:
I myself am not sure where third-party pkgs should install into. FOSS
could always be integrated directly into OpenSolaris via the
consolidation process, or perhaps via /contrib, in which case it will
end
On Thu, Jun 04, 2009 at 04:37:51PM -0500, Shawn Walker wrote:
a b wrote:
It appears that these architectural issue have not been thought throughly.
The OpenSolaris distribution, as you are aware, is experimenting with
changes that have not yet made it through ARC. Regardless, I don't see
James Lee wrote:
I am trying to get OpenSolaris 2009.06 to run from my 32 GB Kingston
compact flash drive attached to a standard Sil 0680 IDE controller. The
installer detects the card and install successfully. Upon reboot, GRUB
drops to a grub prompt. Any attempts to read menu.lst fail with:
Dave Miner wrote:
You didn't by chance turn on gzip-compression for the file systems on
this, did you?
Dave
No. I'm not using any compression.
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
On Thu, Jun 04, 2009 at 08:11:48PM +0200, a b wrote:
Consider that if I deliver my software in /usr (as a 3rd party
unbundled applications vendor), I run an extremely high risk of:
a) being overwritten by IPS, respectively your own updates
b) my software overwriting your software.
I
Nicolas Williams wrote:
On Thu, Jun 04, 2009 at 04:37:51PM -0500, Shawn Walker wrote:
a b wrote:
[snip]
I won't debate the merits, etc. of this with your nor comment on what
should or should not be done architecturally as that isn't my
responsibility. I'll just simply say that I
William Headrick wrote:
Anil Jangity wrote:
See attachments.
/var/adm/messages:
May 5 16:27:57 sjc gdm-binary[588]: [ID 702911 daemon.warning] WARNING:
Failed to start X server several times in a short time period; disabling
display :0
... oh, I forgot to plug the mouse in when I
opensola...@myspamfilter.fastmail.fm wrote:
On Thu, 04 Jun 2009 20:29 -0700, Alan Coopersmith
According to those logs, your X server started and is running on your
AST service processor/remote KVM.
Alan,
I believe that I am running into the same issue on a Sun Fire x2270. I've
got the
problem solved!
actually i had not disabled the floppy drive in the BIOS (i don't have a floppy
drive). The hal daemon was trying to access the floppy drive because it was
enabled in BIOS.
the same thing was probably happening in the older version of OpenSolaris. But
in this release, hal was
28 matches
Mail list logo
