[ Mar 5 23:16:15 Executing start method (/usr/sbin/smbd -D). ]
ld.so.1: smbd: fatal: libavahi-core.so.6: open failed: No such file or directory
You're running into a newly introduced issue
7023783 Samba goes to maintenance on 159 due to missing libavahi-core.so.6
I expect this will be
Does that mean that xvm is supported to use solaris 11 express as Dom0 ?
Yes, the xVM packages are still present in 2010.11 although there are
known issues with them. And though the packages are there and I can't
speak to the dom0 roadmap, I should point out the following approved
ARC case
It sounds like you may be running into 6914346 which is documented in
the release notes:
6914346 upgrade from OpenSolaris 2009.06 (111b2) to 130 fails with stale
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914346
After updating to build 130 or beyond, the system may
Your question is probably better asked on the mailing list dedicated to
IPS at least until the issue is root caused. I've cc'ed that list and
Bcc'ed opensolaris-discuss.
I have tried on both b133 and b134 to install Sun Studio 12u1,
Netbeans, Openoffice, and to do a system update. I am using a
You may be running into the following issue
6932552 early calls to cv_reltimedwait() are even less safe post 6919691
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6932552
The work-around is to boot with the GRUB splashimage, foreground and
background lines deleted and the
I've noticed that since b132 my laptop freezes under load. Just dies
without any message other than memory pressure, tcp defensive mode
on. Probably short of memory. I've _only_ 1GB which used to be quite
ok for a laptop.
Are you certain it's actually frozen or just being *very* slow? If you
129: Xen manager did not even start
130: could not even see the screen as it was all dark white
I hope that build 131 will come soon and run smoothly like 128a.
Although I believe both of these issues have been resolved, did you
examine http://defect.opensolaris.org and/or
OpenSolaris, at least according to David Comay Co., is going for
Linux / GNU crowd directly, hence the forced-at-all-and-any-cost
replacement of System V utilities to GNU userland
Actually, that's never been stated as a goal in any form. What has
been said is there is a large community
While running OpenSolaris snv_116 I did an upgrade which created a new
BE running OS snv_118. I restarted OS and chose OS snv_118 to boot.
What I see is the OS boot screen with the progress bar moving and it has
been doing that for about an hour. Has anyone had success with this?
A reminder
Other known issues in this repository update
6811922 PCIE init err info failed BDF 0x0 on snv_109 (Ultra 20 M2)
I asked about this before but never got a complete answer. Let's try again...
I have an Ultra 20, not an Ultra 20 M2, does that mean
[ I've moved opensolaris-discuss to the Bcc ]
The utilities in question do not support Linux specific features. Why do you
believe you will be able to feed back such enhancements for Solaris to the
upstream?
Is it your personal experience that this is the case or can you point
to mail
What is the strategy to fix the utilities? Will the GNU utilities be
modified to be supersets of their Solaris counterparts? What is the strategy
for the cases where the default behavior is different between the Solaris
version and the GNU version (and/or when the GNU version is non-POSIX by
It would be better to go with the ATT AST tools
(http://www.research.att.com/sw/download/). AST supports many of the
BSD and GNU command line options missing in the native Solaris
userland and conform to POSIX.
If those tools are truly compatible with the GNU variants and track
feature
i'm surprised that gnu chmod is installed, what are the advantages
comparing to solaris chmod?
It's very annoying when using ACLs.
The default environment at the moment is to prefer the GNU tools as
that is the more familiar environment for most developers and
end-users; over time, the plan is
I'm using the GUI guest OS installer in virt-manager. Here is my setup for
the VM:
I believe there are changes to virt-manager(1) and/or virt-install(1M)
that are required to support 2008.05 as a PV guest. I would suggest
sending your question to [EMAIL PROTECTED] as the xVM team
know what
Same for me after installing package SUNWtoo, and the fact that they have
removed the failsafe from the 05/08 version makes this one hell of a disaster.
Before trying to install SUNWtoo, did you follow the steps documented
at the front of the release notes (labeled Important Package Update
[ Removed opensolaris-discuss from the Cc and Bcc'ed advocacy-discuss
and opensolaris-discuss. Folks, can we try to exercise some basic
email etiquette here? ]
Sigh. We have made no statements about compatibility with anything,
either past or future, in the preview releases. It's an
It is when you consider that pcn does not work and the ae driver does.
As Alan mentioned, a number of folks have been looking into ae. One
issue that several folks identified (at least on the Indiana prototype)
is that ae seemed to lock up on bulk transfers while the pcn driver
did not:
[ Bcc'ing advocacy-discuss and opensolaris-discuss to reduce cross-posting ]
Peter,
It would help a lot if the aims of this project were clearly explained
and enunciated, because I for one haven't a clue what they are, and
the more I think about it and look at what has been announced and
Can you provide some details on why you think Indiana is or will be any
less standard's compliant than SXCE is? It may very well turn out that
it may be less compliant but that hasn't occurred yet and so I'm just
trying to understand where you're coming from.
If Indiana is/becomes a (too)
Not everyone agrees with you on this. It is my understanding that SXCE
releases will continue, and until such time as standards compliancy is
actually considered a goal of Indiana, it is of little interest.
Frankly, if forced to discontinue my reliance on SXCE, I will likely go
to ShilliX, as
The unthinkable has happened: SunOS backwards compatibility has been broken.
First of all, you're talking about a prototype and nothing more. Such
an artifact is similar to the BFU archives available from many projects
on opensolaris.org and the ISO represents the (initial) output of a
project.
So, I gave Solaris 10 (11/06) a shot. Solaris barfed all over me; like
a girlfriend you love but who just can't get it together, it wouldn't
get past the initial display probe and gave me an unintelligible (read
bank) GUI screen. So it was a text based install, which I don't mind,
as with
For example knowing that libreadline is under the GPL
rather than the
LGPL or CDDL would be good information, particularly
since libtecla is
available as an alternative set of functionality.
One idea some of us have thrown around is to provide a command to provide this
information given a
Stefan,
2. The currently proposed Apache 2.2.4 integration installs Apache in
/usr/apache2, thereby _overwriting_ the existing Apache 2.0.x. Valid
arguments have been made pro, and against this approach, with the suggestion
that Apache 2.2.4 installs in /usr/apache2.2, thereby preserving the
These ARC cases are for integration to Solaris, so /opt is inappropriate,
and /usr is correct.
Oh in that case, I agree. *Provided* that the CoolStack stuff will replace
the current stuff on the Solaris distribution media.
Just for clarification, the integration that Stefan is working on
+1
A nit however, there are no such things as local zones. :-) The proper name is
non-global zones.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
The issue was introduced during the development of Solaris 10 and not via
OpenSolaris. It's present in all Solaris 10 releases (although thanks to
Secure by Default in Solaris 10 11/06, the port in question is disabled by
default in the current version).
A reminder that official patches are
+1
dsc
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Ryan,
You might try asking directly on security-discuss as that's where the SSH
minded folks hang out.
dsc
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
The Atheros NIC is supported by Nevada's bundled ath driver but there are a
few chipsets that are affected by
a href=http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6472427;
6472427/a
which causes a hard hang when the driver attaches. It appears that the AR5005G
may be one of the
By the way, you might be able to boot up Belenix's LiveCD by including the
option -B disable-ath=true on the GRUB multiboot line.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Yes, it is. Both the ability to cap physical memory (memory sets) as
well as the ability to cap virtual memory (swap sets).
Will it be available in sol 10 next release as well ?
No, not in the upcoming Solaris 10 update release. These particular
features are not yet in Solaris Express,
Have you considered requesting such support via
http://www.opensolaris.org/bug/report.jspa
Having such requests for enhancements let the community know about the missing
functionality and provides a way to track its progress (at the moment, modulo
any issues with bugs.opensolaris.org!)
Please
I don't know the answer about redistributing libC* but have you brought up the
DLJ question to [EMAIL PROTECTED] or the appropriate forum
http://forums.java.net/jive/forum.jspa?forumID=94
I'll make some inqueries myself but the DLJ folks might know the answer and
certainly would want to know
Starting with Solaris Express 5/06 (as well as the upcoming Solaris 10 update),
you can
assign extra privileges to a zone using the limitpriv property. In your
particular example,
you would perform the following for a zone named myzone
# zonecfg -z myzone
zonecfg:myzone set
I believe the issue is resolved in snv_48.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
emm Solaris Exress 5/06?
That's the *next* release of Solaris currently under development which will
follow Solaris 10.
It's codenamed Nevada.
I remember the version of my solaris10 is 6/06 (it
should not be an Express,
just a formal release) just like following:
bash-3.00# uname -a
http://www.gnusolaris.org/gswiki/Download
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Sorry, that should be copy /usr/openwin/lib/X11/fonts/F3bitmaps/fonts.alias.all
over to
/usr/openwin/lib/X11/fonts/F3bitmaps/fonts.alias
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
This is a known issue and is being tracked as
6445132 CDE stopped using the correct system interface fonts
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
This issue is currently being tracked under
6419446 RFE: zoneadm should dlopen libzfs.so to avoid patch accumulation
problems
But note that you're not required to use ZFS with zones - you just need, at
this time,
the relevant ZFS packages installed.
This message posted from opensolaris.org
There isn't a way at this time to change a package's status after it's been
installed.
Please feel free to file a RFE at bugs.opensolaris.org as this ability might be
useful.
As a workaround, I believe you can pkgrm(1M) the existing package and then
pkgadd(1M)
it again, this time specifying the
One of the rare things I like in Linux, is how Linux
solved this: regardless of the networking HW, all
interfaces are named eth[0-N], for example eth0,
eth1, ... , ethN.
Perhaps this would be a solution to consider? There
can still be bge0, and iprb0, iprb1 or ce0 in the
system, but they
To be particular, if I have a Solaris kernel tunable
pertinent to Oracle on Solaris 8, what do I do with
this tunable on Solaris 10 when the tunable is marked
as obsolete?
You would set (if required) a corresponding resource control. For more
details, see the
following chapter from the
Could you make the complete install_log file available somewhere for us to
peruse?
I suspect the details there might shed light on what happened with the
installation.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
Unfortunately, I can't speak to a date but the work is well underway.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
No, this functionality is not yet available in Solaris Express.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
This is one place where he might have a half valid
point. There should be some better mechanism to
patch a zone without having to bring it up. There
Agreed which is why in Solaris 10 1/06 it doesn't actually
boot the zone if it's not running - instead, it mounts the zone's
file systems and
One more clarification, do we have a plan
to introduce a layer or a kernel module
in uts to leverage underline HW capabilities
for resource management and allocation
per processor usage. Specifically, due to
the maturity of the cores, and core afiliation
and evolution of CMT on Solaris
Many, if not all, of the presentations are available here
https://opensolaris.org/os/community/os_user_groups/os-presentations/
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
In addition to the Solaris Internals book, please also review the proposed
OpenSolaris
Development Process draft
http://www.opensolaris.org/os/community/onnv/os_dev_process/
which describes in some detail a set of high-level design principles for the
project.
This message posted from
The build infrastructure is fairly straighforward.
What's not straightforward,
is the development process. OpenSolaris process is
based on the Solaris process,
you can read about it here:
http://www.opensolaris.org/os/community/onnv/os_dev_process/
Just a minor clarification - although
As yet, Solaris is unable to cap the memory usage of a zone as an container,
only the individual projects/tasks/users from within the zone.
That's correct.
Is the above facility upcoming?
Yes, it is. Both the ability to cap physical memory (memory sets) as
well as the ability to cap
Here are a couple of resources which go into this
http://blogs.sun.com/roller/resources/comay/zones-opensolaris.pdf
(slides 30 through 32)
http://developers.sun.com/solaris/articles/application_in_zone.html
This message posted from opensolaris.org
___
So, this all begs the question, why isn't Sun making more of an
effort to define a workable OpenSolaris process for interface
review. There should be something on the http://www.opensolaris.org/
website addressing this topic, even if it just says We are
working on figuring it out. Here are the
56 matches
Mail list logo
