[EMAIL PROTECTED] wrote:
[...]
Strictly conformant to the above would therefore be:
#define dirfd(dp) ((dp) ? (dp)-dd_fd : -1)
No. Nothing to do with strictly conformant; while it is possible
to have a DIR * which is NULL, using it immediately gets you undefined
behaviour.
IMHO,
And to try to answer my own question, Draft 2 says
(about dirfd() among others):
...shall be declared as functions and may also be defined as macros. Function
prototypes shall be provided.
and specifically about dirfd():
The dirfd( ) function may fail if:
[EINVAL] The dirp argument does not
Moinak Ghosh wrote:
[EMAIL PROTECTED] wrote:
[...]
Strictly conformant to the above would therefore be:
#definedirfd(dp)((dp) ? (dp)-dd_fd : -1)
No. Nothing to do with strictly conformant; while it is possible
to have a DIR * which is NULL, using it immediately gets you
On 3/22/07, James Carlson [EMAIL PROTECTED] wrote:
I don't think, though, that decent package management is entirely or
even primarily a feature of the packaging software itself. A huge
amount of the effort rests on the project teams who package and
deliver the software -- if they don't think
Thanks Rod !
Does the GNU Toolchain also generates this dynamic entry (or a similar kind) in
its executable's elf files?
If not, Would the rtld still work fine without this Libc interface information ?
Regards,
Rajesh
This message posted from opensolaris.org
As a related note glibc has some questionable protections, like
free(NULL)
which it simply ignores resulting in bugs remaining hidden. GNU ls
does a
free(NULL) somewhere which we discovered while demoing truss on linux
processes in BrandZ. It is also visible when you use ltrace in
[EMAIL PROTECTED] wrote:
As a related note glibc has some questionable protections, like
free(NULL)
which it simply ignores resulting in bugs remaining hidden. GNU ls
does a
free(NULL) somewhere which we discovered while demoing truss on linux
processes in BrandZ. It is also visible
[EMAIL PROTECTED] wrote:
As a related note glibc has some questionable protections, like
free(NULL)
which it simply ignores resulting in bugs remaining hidden. GNU ls
does a
free(NULL) somewhere which we discovered while demoing truss on linux
processes in BrandZ. It is also
Ian Collins [EMAIL PROTECTED] wrote:
Solaris libc, unfortunately, also allows free(foo); free(foo);
Legal undefined behaviour :)
Calling free(foo); free(foo); is not legal and may result in anything, including
pink smoke on top of your screen.
free(foo); free(foo); however is no
On 22/03/07, Darren J Moffat [EMAIL PROTECTED] wrote:
Dick Davies wrote:
On 22/03/07, Thomas De Schampheleire [EMAIL PROTECTED] wrote:
pkginfo SUNWman does show:
system SUNWman On-Line Manual Pages
doesn't this mean it is installed?
That's the man command, not the man pages.
The
Joerg Schilling wrote:
Ian Collins [EMAIL PROTECTED] wrote:
Solaris libc, unfortunately, also allows free(foo); free(foo);
Legal undefined behaviour :)
Calling free(foo); free(foo); is not legal and may result in anything,
including
pink smoke on top of your screen.
Hi.
The ARC Cases for the WebStack NG Project have been
submitted for review (and
hopefully approval), and i would like to ask our
community's input regarding two
important questions which have come up during our
discussions:
1. Should the initial components released for this
Overwriting the /usr/apache2 that comes on the
Solaris media is a no-no,
in my opinion, and /usr/apache2.2 just pollutes the
/usr namespace even
more than it is already. IMHO, the correct place for
this is under /opt.
Agreed.
I have no strong feelings either way, but I would
prefer
On Thu, 22 Mar 2007, Richard L. Hamilton wrote:
And to try to answer my own question, Draft 2 says
(about dirfd() among others):
...shall be declared as functions and may also be defined as macros. Function
prototypes shall be provided.
and specifically about dirfd():
The dirfd( ) function
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
Moinak Ghosh [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
[...]
Strictly conformant to the above would therefore be:
#definedirfd(dp) ((dp) ? (dp)-dd_fd : -1)
No. Nothing to do with strictly conformant; while it is possible
to have a DIR * which is NULL,
Whatever proposal wins it should preserve _choice_
for admins/developers.
Let _them_ decide which version they are going to
use.
If we are going to compete with linux we should give
choice because
one of linux strength is giving choice (one may
disagree with me but I
have written one of).
The user could easily change the apache2 symlink if
it bothers them, and that
would point to the new version, but would allow your
entire stack to use the
runpath you compiler for.
That won't work. It's ad-hoc, and ad-hoc doesn't work if you have several tens
of thousands (yes, you read
[EMAIL PROTECTED] wrote:
As a related note glibc has some questionable protections, like
free(NULL)
which it simply ignores resulting in bugs remaining hidden. GNU ls
does a
free(NULL) somewhere which we discovered while demoing truss on linux
processes in BrandZ. It is also visible
These ARC cases are for integration to Solaris, so
/opt is inappropriate,
and /usr is correct.
I missed that, ouch. In that case, apologies for the /opt questions. I was
under the *wrong* impression that CoolStack (NG) was delivered separately of
Solaris. Live and learn...
This message
I never liked the /etc/opt/apache2, and so on that
some distributions
did as sometimes it wasn't clear which apache2 read
what configuration
from where, it also made greps by lazy admins (like
me) painful ;)
/etc/opt/vendor or stock symbol/apache2/ is the clean and correct way to
deliver
Agreed, which is why the docs actually suggest
/{etc,var}/opt/packagename,
for example, /etc/opt/RICHTapache2 and
/var/opt/RICHTapache2. Although
the pathname is a bit longer, there can be no
confusion as to what package
it's associated with!
That works too, although over time, you'll
Hi,
before it is too late and children will be infiltrated by MS
software anywhere on the world, we need Solaris in the
Intel competitive HW made against the One Laptop per Child
initative.
http://www.classmatepc.com/classmatepc-system-hardware.html
Jörg
--
EMail:[EMAIL PROTECTED] (home)
Horvath writes:
How to update to Nevada b60 ?
Assuming you have build 60 available, there are several ways to go
about it. Here are three:
- Boot from an snv_60 DVD. This is very slow and requires your
system to be down while the upgrade is happening, but it works.
- Use lofiadm to
Frank Hofmann writes:
On Thu, 22 Mar 2007, Richard L. Hamilton wrote:
The dirfd( ) function may fail if:
[EINVAL] The dirp argument does not refer to a valid directory stream.
Will they really go for that ?
I mean, the explicit NULL exception is one thing, but claiming that the
Please do NOT reply to this address. If you have any problems, feel free
to send email to desktop dash discuss at opensolaris dot org
Firefox 2.0.0.3 contrib. builds on Solaris10, Solaris8/9 are now
available on www.mozilla.com
What's New
===
UNIX admin writes:
I never liked the /etc/opt/apache2, and so on that
some distributions
did as sometimes it wasn't clear which apache2 read
what configuration
from where, it also made greps by lazy admins (like
me) painful ;)
/etc/opt/vendor or stock symbol/apache2/ is the clean
UNIX admin wrote:
These ARC cases are for integration to Solaris, so
/opt is inappropriate,
and /usr is correct.
I missed that, ouch. In that case, apologies for the /opt questions. I was
under the *wrong* impression that CoolStack (NG) was delivered separately of
Solaris. Live and
I can ask around and see if there is an opportunity here for Solaris as well.
Believe the classmate PC has been going on long before the Sun-Intel alliance.
One thing I noticed is that the HW platform described only has 256MB of memory.
When I tried to install an OpenSolaris build the other
Is this just a packaging issue? Can Solaris run on small machines?=
Are there implementations which run on really tiny things like cell=
phones and the like?
GUI installer issue.
Casper
___
opensolaris-discuss mailing list
On 3/23/07, Stewart, David C [EMAIL PROTECTED] wrote:
I can ask around and see if there is an opportunity here for Solaris as well.
Believe the classmate PC has been going on long before the Sun-Intel alliance.
One thing I noticed is that the HW platform described only has 256MB of memory.
Stewart, David C wrote:
I can ask around and see if there is an opportunity here for Solaris as well.
Believe the classmate PC has been going on long before the Sun-Intel alliance.
One thing I noticed is that the HW platform described only has 256MB of memory.
When I tried to install an
On Thu, 22 Mar 2007, eric wang wrote:
Thanks!!
More information:
Hi, All,
Here is the pstack information from dbx.
[EMAIL PROTECTED] ([EMAIL PROTECTED]) terminated by signal SEGV (access to
address exceeded protections)
0xfd90b258: _lock_try_adaptive : ldstub [%o0 + 12], %o1
(dbx)
Hello forum users,
I am finishing computer science studies this year and I need to create thesis.
I'm interested in Solaris containers and would like to describe this
technology. I want to create a project that uses containers to do “something
useful” and provides some functionality, not only
You can still show the value of containers with 512MB RAM (although you
may want to disable the desktop UI if RAM becomes too big an issue).
I've done 3 (sparse) zones in 512MB RAM with no issues.
One of the primary benefits of Containers is delegated administration.
Think of a company
Hello John,
Friday, March 23, 2007, 5:10:34 PM, you wrote:
JC You can still show the value of containers with 512MB RAM (although you
JC may want to disable the desktop UI if RAM becomes too big an issue).
JC I've done 3 (sparse) zones in 512MB RAM with no issues.
JC One of the primary
On Fri, 23 Mar 2007, UNIX admin wrote:
That works too, although over time, you'll have lots of config dirs in
/etc/opt/.
True...
I deliver all my config stuff in /etc/opt/my-stock-symbol/ and then,
if the app has more than two config files, in
/etc/opt/my-stock-symbol/app, for example:
I've been long interested in reducing Solaris's footprint. This wasn't
possible with the monolithic Solaris distribution, just as it isn't
possible to install RHEL4 onto a mobile phone. But Nexenta and Belenix
both have a smaller footprint than Sun's server focused distribution and
of you
The NWS project consists of drivers, libraries and utilities in support of
storage interconnect technologies including both Fibre Channel and iSCSI.
The NWS project source code has been available since 2/06, however, the project
does not have its own project page but rather exists as part of
Is there a mechanism to pass PCIe AER from PCI nexus driver to leaf driver ?
PCIe AER driver in Linux has a PCI error recovery callback to notify AER to
endpoint device driver. Does Solaris have similar infrastructure ?
Thanks.
This message posted from opensolaris.org
I'll try not to muddle things further, but the Review your contributor
grants section of the poll instructions and relevant sections of the
draft constitution could be made more specific to this election:
http://opensolaris.org/os/project/website/poll_instructions
In simple terms, if you
Shawn Walker wrote:
Your manpath probably isn't set correctly. The default manpath for
Solaris does *not* include all of the man directories for all
installed software; it is up to you set it appropriately.
Setting your manpath to include /usr/sfw/man, /opt/SUNWspro/man, etc.
would probably
You might want to look at the way the GNOME community handles
elections. I thought that was pretty straightforward.
Dennis Clarke wrote:
I'll try not to muddle things further, but the Review your contributor
grants section of the poll instructions and relevant sections of the
draft
John Forte wrote:
The NWS project consists of drivers, libraries and utilities in support of
storage interconnect technologies including both Fibre Channel and iSCSI.
The NWS project source code has been available since 2/06, however, the project
does not have its own project page but rather
On Friday 23 March 2007 01:00 am, Eric Enright wrote:
Indeed.
Several months ago a friend of mine running Debian did an `apt-get
dist-upgrade'. Among other things, it upgraded apache2 and squid to
newer versions, which took advantage of epoll().
epoll() is only available in Linux 2.6.
On Thursday 22 March 2007 10:15 pm, Horvath wrote:
How to update to Nevada b60 ?
I would start by having the media.
Then I would boot it on the machine, and select the upgrade option instead of
a new install.
--
Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
Advocate of insourcing at
Thanks Cindi.
I assume the to be released document will detail how a leaf driver can register
its callback to the nexus driver/framework. Is it correct ?
Or is there any current published document that talks about the callback
registration ?
Thanks.
This message posted from opensolaris.org
On 3/23/07, John Forte [EMAIL PROTECTED] wrote:
The NWS project consists of drivers, libraries and utilities in support of
storage interconnect technologies including both Fibre Channel and iSCSI.
The NWS project source code has been available since 2/06, however, the project
does not have
So, could we assume that NWS now will not be delivered as a separated
tarball and will be part of ON tarball?
Or this is just an effort to get dedicated web page on opensolaris.org?
On Fri, 2007-03-23 at 10:19 -0700, John Forte wrote:
The NWS project consists of drivers, libraries and utilities
Hi,
Alan DuBoff pÃÅ¡e v pá 23. 03. 2007 v 12:12 -0700:
On Friday 23 March 2007 01:00 am, Eric Enright wrote:
Indeed.
Several months ago a friend of mine running Debian did an `apt-get
dist-upgrade'. Among other things, it upgraded apache2 and squid to
newer versions, which took
Erast Benson wrote:
So, could we assume that NWS now will not be delivered as a separated
tarball and will be part of ON tarball?
Or this is just an effort to get dedicated web page on opensolaris.org?
Erast,
You ask a good question. It isn't aimed as much to get a new project
page in
One thing I noticed is that the HW platform described
only has 256MB of memory. When I tried to install an
OpenSolaris build the other day on a machine with
512MB, the install failed due to my machine not
having enough memory - wanted 796MB or some such.
I always install Solaris in text
Will they really go for that ?
I mean, the explicit NULL exception is one thing,
but claiming that the
function may not crash for any random pointer passed
in, but return EINVAL
instead, forces either a system call (to error out on
copyin() failure) or
a horrid check against all
int fd;
DIR *dp;
if ((fd=dirfd(dp=opendir(/my/dir))) == -1) {
/*fail*/
}
Well, this code cannot tell the difference between this implementation
does not use file descriptors for directory streams and directory
stream open failed.
Casper
___
Strictly conformant to the above would therefore be:
#define dirfd(dp) ((dp) ? (dp)-dd_fd : -1)
You'd still crash if you pass an invalid pointer,
though.
Regardless of one's opinion on checks for NULL args, as a macro,
that's bad, with multiple references to the arg on the
On 23/03/07, Brian Nitz [EMAIL PROTECTED] wrote:
Shawn Walker wrote:
Your manpath probably isn't set correctly. The default manpath for
Solaris does *not* include all of the man directories for all
installed software; it is up to you set it appropriately.
Setting your manpath to include
I should correct myself. Where can I get the dvd iso images of b60 or b61? I
thought the iso's would be updated every other friday but when I checked the
web site I saw only b59 there.
This message posted from opensolaris.org
___
On 23/03/07, Horvath [EMAIL PROTECTED] wrote:
I should correct myself. Where can I get the dvd iso images of b60 or b61? I
thought the iso's would be updated every other friday but when I checked the
web site I saw only b59 there.
They are not necessarily updated every other Friday. It
UNIX admin wrote:
One thing I noticed is that the HW platform described
only has 256MB of memory. When I tried to install an
OpenSolaris build the other day on a machine with
512MB, the install failed due to my machine not
having enough memory - wanted 796MB or some such.
I always
On 3/24/07, Shawn Walker [EMAIL PROTECTED] wrote:
On 23/03/07, Horvath [EMAIL PROTECTED] wrote:
I should correct myself. Where can I get the dvd iso images of b60 or b61? I
thought the iso's would be updated every other friday but when I checked the web
site I saw only b59 there.
They are
On 24/03/07, Cyril Plisko [EMAIL PROTECTED] wrote:
On 3/24/07, Shawn Walker [EMAIL PROTECTED] wrote:
On 23/03/07, Horvath [EMAIL PROTECTED] wrote:
I should correct myself. Where can I get the dvd iso images of b60 or b61?
I thought the iso's would be updated every other friday but when I
On 24/03/07, Moinak Ghosh [EMAIL PROTECTED] wrote:
UNIX admin wrote:
One thing I noticed is that the HW platform described
only has 256MB of memory. When I tried to install an
OpenSolaris build the other day on a machine with
512MB, the install failed due to my machine not
having enough
62 matches
Mail list logo
