Dave Marquardt wrote:
Roland == Roland Mainz [EMAIL PROTECTED] writes:
Roland Did anyone thought about creating a tuneable in /etc/system to set the
Roland (preferred) default page size for stackhead to something else than 8k
Roland (e.g. 64k) globally (instead of using libmpss.so - which
James Carlson wrote:
Roland Mainz writes:
Did anyone thought about creating a tuneable in /etc/system to set the
(preferred) default page size for stackhead to something else than 8k
(e.g. 64k) globally (instead of using libmpss.so - which does not work
for inital processes, deamons
Hi!
Is it currently somehow possible to assign processes running under one
projectid to one specific swap device and others to another set of swap
devices ?
The scenario would be a machine shared by two workgroups (all memory
slots full) and one of them bought a set of solid-state disks to
Jürgen Keil wrote:
What kind of cpu is used on the host OS? A dual core AMD cpu perhaps?
In this case, a wild guess is that it could be the AMD TSC drift issue with
dual core cpus:
http://groups.google.com/group/comp.unix.solaris/msg/ce39f46758e5e539?hl=en;
As a workaround, try to use
Gerard J. Cerchio wrote:
Hi Frankho,
Has there been any progress or discussion porting FUSE to Solaris?
Well, first I'd like to see FUSE revamped a little bit. Last time I
checked (note: My knowledge is almost a year old so I could be wrong) it
was very difficult to write FUSE
Frank Hofmann - Solaris Sustaining wrote:
Gerard J. Cerchio wrote:
Has there been any progress or discussion porting FUSE to Solaris?
Well, first I'd like to see FUSE revamped a little bit. Last time I
checked (note: My knowledge is almost a year old so I could be wrong) it
was very
Artem Kachitchkine wrote:
Name: The project has been known internally as Tamarack for quite some
time. Since we need a shorter alternative to removable media and
hotpluggable device enhancements and two codenames for one project
would be confusing, I suggest that we keep the name (unless it
If probe-scsi-all show your disks then maybe your disks don't have the right
label: Try a format -e on a prompt and check your labels and partitions;
Solaris install will not see your disks if the label is not SMI...
This message posted from opensolaris.org
Tamarack is a great name .I doubt that it is offensive in any other
language since there are several companies out there with that name,
including Tamarack Funds and Tamarack Scientific
Darren J Moffat wrote:
Artem Kachitchkine wrote:
Name: The project has been known internally as
SXCR 34 was released yesterday (3/6), as scheduled.
Steve will release another nightly sync with onnv_35 today (3/7) or tomorrow
(3/8).
Hopefully you all noticed that the source for the packaging tools was also
released yesterday. See http://www.opensolaris.org/os/downloads/ for all the
Wide open question here.
If I have a server based on build 35 and am running with a ZFS
filesystem shared out via NFS am I safe to assume that there will be
no substantial changes to ZFS for the next year or so? While there
may be the occasional patch or minor tweak I have this gut feeling
that
On 3/7/06, Karyn Ritter [EMAIL PROTECTED] wrote:
SXCR 34 was released yesterday (3/6), as scheduled.
Excellent .. thank you.
Steve will release another nightly sync with onnv_35 today (3/7) or tomorrow
(3/8).
Hopefully you all noticed that the source for the packaging tools
You mean the
Hello Dennis,
Tuesday, March 7, 2006, 3:33:08 PM, you wrote:
DC Wide open question here.
DC If I have a server based on build 35 and am running with a ZFS
DC filesystem shared out via NFS am I safe to assume that there will be
DC no substantial changes to ZFS for the next year or so? While
Would you mind dropping the subject? It's been a little beaten to death and
it's pointless to drag it on. You have a couple of solutions--actually a third,
if you don't mind putting a bit of effort, i.e., you have the source and Studio
11, make it work--and at some point Open Solaris will
I have noticed that on the SVOSUG page -
http://opensolaris.org/os/community/os_user_groups/svosug/
That the videos are sometimes hard to follow slide wise
with lighting issues, etc. While I appreciate the videos I
was wondering if PDF files of the slides sets could be posted
there as well?
Robert Milkowski wrote:
I belive that some new features like encryption, other
compression algorithms or hot spare support will be added relatively
soon.
Depends on your definition of soon when it comes to the crypto
support. There is no funded and agreed on roadmap yet even though
the
I would also hesitate to call it sophisticated. If
you are just talking
about ON (i.e., all the stuff in OpenSolaris), then
it's really pretty
simple. If you are talking about all of Solaris
(including Gnome, CDE, the
install tools, etc), then it is complicated but not
particularly
Joel Buckley wrote:
I manage a consolidation with a total of 2 developers. Even with this
size the gatekeeper role is intact. I would suggest the wording be
explicitly stated for the gatekeeper. Then describe the role the
gatekeeper conducts as part of the product release process.
Perhaps
I have noticed that on the SVOSUG page -
http://opensolaris.org/os/community/os_user_groups/svosug/
that the videos are sometimes hard to follow, slide wise,
with lighting issues, etc. While I appreciate the videos I
was wondering if PDF files of the slides sets could be posted
there as well?
Alan Coopersmith wrote:
James Carlson wrote:
Having engineers rather than gatekeepers marking bugs as
integrated, as Alan describes for non-ON gates, seems broken to
me.
Well, it is admittedly for gates with no gatekeepers. When you have
a fraction of the developers ON does, you get
Roland Mainz wrote:
The goal would to have _everything_ use 64k pages by default (instead of
8k pages) to squish the last bits of performace out of a system
(primarily HPC configurations with lots of memory[1]), including that
bits such as tmpfs, |getpagesize()|/|sysconf(_SC_PAGESIZE)| make use
On Tuesday 07 March 2006 07:39 am, John Kaitschuck wrote:
I have noticed that on the SVOSUG page -
http://opensolaris.org/os/community/os_user_groups/svosug/
that the videos are sometimes hard to follow, slide wise,
with lighting issues, etc. While I appreciate the videos I
was wondering if
Hi Roland,
What you're asking for is called Swap Sets (as an extension
for Resource Pools). This feature is not available in Solaris
today, but it is on the list of things to do after Memory Sets.
- Andrei
On 3/7/06, Roland Mainz [EMAIL PROTECTED] wrote:
Hi!
Is it currently somehow
* Roland Mainz [EMAIL PROTECTED] [2006-03-07 02:04]:
Is it currently somehow possible to assign processes running under one
projectid to one specific swap device and others to another set of swap
devices ?
The scenario would be a machine shared by two workgroups (all memory
slots full) and
Dennis Clarke wrote:
Wide open question here.
If I have a server based on build 35 and am running with a ZFS
filesystem shared out via NFS am I safe to assume that there will be
no substantial changes to ZFS for the next year or so? While there
may be the occasional patch or minor tweak I have
On 3/7/06, Joerg Schilling [EMAIL PROTECTED] wrote:
ken mays [EMAIL PROTECTED] wrote:
3. The DHCP process worked better than in other
OpenSolaris distros. No 'hangs' during ethernet
detection or initialization.
Thank you for this positive view. I will enhance the DHCP procedure
for the
On Tue, Mar 07, 2006 at 08:13:01AM -0800, UNIX admin wrote:
The reason I took up interest in the code gates is that some of the
kernel engineering folks' posts seem to imply there's 'gatekeeper'
logic of some sort sitting on a code gate, doing basic sanity checks
on the putback source code.
On Tue, Mar 07, 2006 at 01:21:52PM -0500, Dennis Clarke wrote:
What I am looking for here is a warm and fuzzy feeling in my gut that
I can perform my last BFU on this box and then run with it for the
next year. It will have power and cooling and love. Nothing else.
It will also have the
Thanks, Artem. You have some seconds. Eric will get you set up.
Jim
Artem Kachitchkine wrote:
Solaris lags considerably in terms of removable media and hotpluggable
device management on the desktop. A detailed problem statement and some
recommendations can be found in the Solaris Desktop
I neglected to add a section to this report yesterday for proposals that
didn't get consensus (or a second for projects), are over the 30 day
time limit, or lack a CAB vote. So, the following proposals are void and
will be removed from next week's report. If community members wish to
revisit
These are very helpful, Glynn. Thanks. I'll link to these in the monthly
newsletter.
Jim
Glynn Foster wrote:
Hi,
Here's OpenSolaris Weekly News #2. As always feedback, or content [from
the missing represented communities] welcome.
Glynn
==
Jim Grisanzio reported [1] that he has published
Andy Tucker wrote:
On 3/6/06, Roland Mainz [EMAIL PROTECTED] wrote:
I'm hitting some problems with Solaris guest installations in VMware
(e.g. Solaris being the guest in a VMware VM):
Sometimes the clock is going out-of-sync. I configured xntpd to
counteract these issues - but suddenly at
Dennis Clarke wrote:
On 3/7/06, Andy Tucker [EMAIL PROTECTED] wrote:
On 3/6/06, Roland Mainz [EMAIL PROTECTED] wrote:
I'm hitting some problems with Solaris guest installations in VMware
(e.g. Solaris being the guest in a VMware VM):
Sometimes the clock is going out-of-sync. I
Keith M Wesolowski writes:
On Tue, Mar 07, 2006 at 08:13:01AM -0800, UNIX admin wrote:
The reason I took up interest in the code gates is that some of the
kernel engineering folks' posts seem to imply there's 'gatekeeper'
logic of some sort sitting on a code gate, doing basic sanity
On 3/7/06, Keith M Wesolowski [EMAIL PROTECTED] wrote:
On Tue, Mar 07, 2006 at 01:21:52PM -0500, Dennis Clarke wrote:
What I am looking for here is a warm and fuzzy feeling in my gut that
I can perform my last BFU on this box and then run with it for the
next year. It will have power and
This is really excellent, Sam. Thanks for doing this. +1
- ahl
On Mon, Mar 06, 2006 at 04:17:15PM -0700, Sam Falkner wrote:
I have been doing some work on making a DTrace provider for NFSv4.
See this blog entry for more details:
Bart Smaalders wrote:
Roland Mainz wrote:
The goal would to have _everything_ use 64k pages by default (instead of
8k pages) to squish the last bits of performace out of a system
(primarily HPC configurations with lots of memory[1]), including that
bits such as tmpfs,
Was this project integrated into Solaris 10 ?
No, it failed at some of the last hurdles: not breaking software.
Which code breaks ? Userland or kernel code ? Was there a common cause
(or better: What was the most common cause...) which triggered problems
(for example stack overflow) ?
On Tue, 7 Mar 2006, Roland Mainz wrote:
It may be much better to think about getting VMware itself running on
top of Solaris x86 (e.g. Solaris x86 as host OS) - then I wouldn't have
to fight Linux on the laptop anymore... :-)
A big +1 from me on that!
Bill
rushmores.net
[EMAIL PROTECTED] wrote:
Was this project integrated into Solaris 10 ?
No,
;-((
it failed at some of the last hurdles: not breaking software.
Why wasn't it put into the kernel but disabled by default ?
Which code breaks ? Userland or kernel code ? Was there a common cause
(or better:
Roland == Roland Mainz [EMAIL PROTECTED] writes:
Roland Bart Smaalders wrote:
Roland Mainz wrote:
The goal would to have _everything_ use 64k pages by default (instead of
8k pages) to squish the last bits of performace out of a system
(primarily HPC configurations with lots of memory[1]),
Roland Mainz wrote:
[EMAIL PROTECTED] wrote:
Was this project integrated into Solaris 10 ?
No,
;-((
it failed at some of the last hurdles: not breaking software.
Why wasn't it put into the kernel but disabled by default ?
Because that just multiplies our test matrix, and having a
Bart Smaalders wrote:
Roland Mainz wrote:
[EMAIL PROTECTED] wrote:
Was this project integrated into Solaris 10 ?
No,
;-((
it failed at some of the last hurdles: not breaking software.
Why wasn't it put into the kernel but disabled by default ?
Because that just multiplies our
Artem Kachitchkine [EMAIL PROTECTED] wrote:
Solaris lags considerably in terms of removable media and hotpluggable
device management on the desktop. A detailed problem statement and some
recommendations can be found in the Solaris Desktop Gap Analysis:
Joerg,
Thanks for your feedback. That's a lot of stuff, it's probably better to
break it up into smaller pieces, around which discussions could focus -
some in desktop-discuss, some in approachability-discuss. It's hard to
think about many problems simultaneously.
I will only address this
Artem Kachitchkine [EMAIL PROTECTED] wrote:
Joerg,
Thanks for your feedback. That's a lot of stuff, it's probably better to
break it up into smaller pieces, around which discussions could focus -
some in desktop-discuss, some in approachability-discuss. It's hard to
think about many
http://groups.google.com/group/linux.kernel/browse_thread/thread/d463747ed8a5291c/28cd281aa2c8408c?lnk=stq=%22If+you+cannot+maintain+a+stable+kernel+interface%22rnum=1#28cd281aa2c8408c
No-no, that's just Linus performing his Tyranosaurus Rex impression.
Dammit, if this is the logic and mode
Thanks, Sam. You have a couple of seconds. Eric will get you guys set up.
Jim
Sam Falkner wrote:
I have been doing some work on making a DTrace provider for NFSv4. See
this blog entry for more details:
http://blogs.sun.com/roller/page/samf?entry=a_dtrace_provider_for_nfs
I would like to
Eric Lowe wrote:
but there's too much code out there that just breaks. The
programmers made implicit assumptions about the approximate
size of a page, and that was that.
Which code breaks ? Userland or kernel code ? Was
Userland. The problem is that mmap() exposed too much detail
Roland Mainz wrote:
Userland. The problem is that mmap() exposed too much detail
and as a result assumptions about sysconf(_SC_PAGESIZE) or
even the range of possible values resulted in programs dying
when sysconf returns 64K for the pagesize. In other words,
the value of sysconf(_SC_PAGESIZE)
Roland Mainz wrote:
Eric Lowe wrote:
but there's too much code out there that just breaks. The
programmers made implicit assumptions about the approximate
size of a page, and that was that.
Which code breaks ? Userland or kernel code ? Was
Userland. The problem is that mmap() exposed too
Eric Lowe wrote:
Roland Mainz wrote:
Userland. The problem is that mmap() exposed too much detail
and as a result assumptions about sysconf(_SC_PAGESIZE) or
even the range of possible values resulted in programs dying
when sysconf returns 64K for the pagesize. In other words,
the value
From: Roland Mainz [EMAIL PROTECTED]
Date: Wed, 08 Mar 2006 02:14:25 +0100
This could be very unfortunate since it limits future development (at
least for Solaris... other operating systems like Linux are likely not
affected, right ?). The decision may be acceptable today - but in twenty
On Wed, Mar 08, 2006 at 02:14:25AM +0100, Roland Mainz wrote:
BTW: The discussion was about a _tuneable_ which could be set to a value
used as default page size (used by kernel and returned by
|getpagesize()|co.) - the default for this tuneable should remain 8k.
It would allow people to switch
Linda Bernal wrote:
Here is an update on OpenSolaris for the month of February:
http://opensolaris.org/os/project/content/newsletter/feb06/
We are accepting contributions for the March newsletter, please send
them to [EMAIL PROTECTED]
I'd like to include some new sections in the March issue
David S. Miller wrote:
From: Roland Mainz [EMAIL PROTECTED]
Date: Wed, 08 Mar 2006 02:14:25 +0100
This could be very unfortunate since it limits future development (at
least for Solaris... other operating systems like Linux are likely not
affected, right ?). The decision may be
Roland Mainz wrote:
This could be very unfortunate since it limits future development (at
least for Solaris... other operating systems like Linux are likely not
affected, right ?). The decision may be acceptable today - but in twenty
years it _may_ become a real problem - assuming the optimum
David S. Miller wrote:
The only thing that breaks is if apps don't call sysconf(_SC_PAGESIZE)
or some similar function such as getpagesize() to obtain that
information portably.
.. or they make assumptions about the possible range of values. ;)
Or did Solaris accidently return 8K always in
Yes, exactly. Once enough applications make assumptions about pagesize the
platform pagesize might as well have been part of the ABI.. as I recall it
was more than one application that broke, so we can't reasonable change it
now and claim to remain binary compatible.
And even between 4K
59 matches
Mail list logo
