Re: [osol-discuss] OpenGrok useless?

2006-12-22 Thread Cyril Plisko
On 12/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: In the beginning the opensolaris source index with OpenGok was extremely useful; unfortunately, it has become useless, IMHO, because it also indexes all projects on opensolaris.org. Another thing is that opengrok used to show history go

[osol-discuss] Dual Booting Solaris and Windows XP from seperate hard disk

2006-12-22 Thread Andrew Pattison
I have a slightly unusual setup that allows me to dual boot between Windows XP and Solaris (currently SXCR build 53) by going into the BIOS setup and changing the boot device. My main disk, which is for Windows XP, is a RAID 0 array on a Silicon Image 3112A SATA controller on the motherboard. Un

[osol-discuss] OpenGrok useless?

2006-12-22 Thread Casper . Dik
In the beginning the opensolaris source index with OpenGok was extremely useful; unfortunately, it has become useless, IMHO, because it also indexes all projects on opensolaris.org. Typical projects duplicate most of the ON source base and OpenGrok makes no attempt in sorting hits; I see all hits

[osol-discuss] Re: [i18n-discuss] Solaris G11N source code open sourced!

2006-12-22 Thread Michal Nowak
Thanks for sharing, Young. Finally... I was waiting for this very moment. This a milestone, indeed. I have to say, this gives us a LOT of work for a new year. :) As far as I can see it's going keep us busy for a LONGER while. Best, Michal ___ openso

[osol-discuss] Solaris G11N source code open sourced!

2006-12-22 Thread Young Joo Pintaske
(Hi! I'm passing on this announcement from Ienup who's not available at the moment. Please read on the good news. :-) Happy holidays!) Hello, I'm delighted to have an honor to announce that we, Sun G11N, have open sourced Solaris G11N source code at OpenSolaris.org and the source code can be

[osol-discuss] Re: Re: Contributing to OpenSolaris

2006-12-22 Thread W. Wayne Liauh
> Rich Teer wrote: > > At the moment, yes. But I think it would be a > desirable long term > > goal to have OpenSolaris becoame a separate legal > entity, much like > > the Apache Foundation. > > This would make financial contributions from other > entities much easier. > It would additionally h

[osol-discuss] Re: B54 and marvell cards

2006-12-22 Thread Lida Horn
> We just put together a new system for ZFS use at a > company, and twice > in one week we've had the system wedge. You can log > on, but the zpools > are hosed, and a reboot never occurs if requested > since it can't > unmount the zfs volumes. So, only a power cycle > works. > I've tried to repro

[osol-discuss] Re: Dual-Head on Radeon with Xorg

2006-12-22 Thread W. Wayne Liauh
> I'm not sure where the problem lies exactly. I've > now got it somewhat working. Just as a datapoint, I > put 6.8 onto svn_38 and it worked great. > > > Any advice would be most welcome as I'm starting to > lose my mind here. ;) > > -brian > > ps: I don't seem to be able to attach the c

Re: [osol-discuss] Re: Re: Dual-Head on Radeon with Xorg

2006-12-22 Thread Eric Enright
On 12/22/06, Brian Hechinger <[EMAIL PROTECTED]> wrote: >> Option "MetaModes" "1024x768-1280x1024" >The above line is interpreted as the resolution for >"Display0-Display1", so what you would want here is >"1280x1024-1280x1024". I had mistaken that for the range of supported resolutions, not th

Re: [osol-discuss] Re: Re: Re: vfork issues

2006-12-22 Thread Peter Buckingham
Eric Enright wrote: > Linux overcommits / lazy loads on memory allocations, though this is > tunable. I believe the default setting is to overcommit, which can > lead to the random killing of processes in order to retrieve memory > should one run out. I forget the terminology used for that partic

[osol-discuss] sxce on Tyan S3992 MB?

2006-12-22 Thread Paul Richards
Has anyone tried/succeeded in fully installing S11/SXCE on a Tyan S3992 motherboard-based system? I bought one of their TA26(B3992) barebones server chassis to use as a fileserver because of it's convenient 8-bay hotswap SATA front panel, and figured that whatever bumps would appear in the road

[osol-discuss] Re: Re: Dual-Head on Radeon with Xorg

2006-12-22 Thread Brian Hechinger
>> Option "MetaModes" "1024x768-1280x1024" >The above line is interpreted as the resolution for >"Display0-Display1", so what you would want here is >"1280x1024-1280x1024". Ah Ha I had mistaken that for the range of supported resolutions, not the resolution of each screen. That did the tri

Re: [osol-discuss] sys/ccompile.h & __sun_attr__()

2006-12-22 Thread James Carlson
Cyril Plisko writes: > Following your logic - what is the reason the thing below is defined there ? > > 96 /* > 97 * structure packing like #pragma pack(1) > 98 */ > 99 #define __sun_attr___packed__ __attribute__((__packed__)) > > Since __PACKED presumably should be just a shorthand version >

Re: [osol-discuss] sys/ccompile.h & __sun_attr__()

2006-12-22 Thread Cyril Plisko
On 12/22/06, James Carlson <[EMAIL PROTECTED]> wrote: Cyril Plisko writes: > > Note that choice of consolidation has nothing at all to do with > > whether you can deliver to /usr/bin, to the root partition, or even > > new kernel modules; all of those are possible outside of ON. It has > > more

[osol-discuss] Re: dkio(7d) and polling for the state of removeable media

2006-12-22 Thread Jürgen Keil
> I'd like to create a mechanism by which a kernel driver can "poll" on media > changes on USB removeable media, such as: > > - floppy ejection > - memory stick unplugs Hmm, an USB memory stick has fixed media. It's the scsa2usb driver that pretends the usb storage device is a remov

Re: [osol-discuss] sys/ccompile.h & __sun_attr__()

2006-12-22 Thread James Carlson
Cyril Plisko writes: > > Note that choice of consolidation has nothing at all to do with > > whether you can deliver to /usr/bin, to the root partition, or even > > new kernel modules; all of those are possible outside of ON. It has > > more to do with where your fellow travelers are located. ;-}

Re: [osol-discuss] Re: Re: Re: vfork issues

2006-12-22 Thread Joerg Schilling
"Eric Enright" <[EMAIL PROTECTED]> wrote: > Linux overcommits / lazy loads on memory allocations, though this is > tunable. I believe the default setting is to overcommit, which can > lead to the random killing of processes in order to retrieve memory > should one run out. I forget the terminolo

Re: [osol-discuss] Re: Re: Re: vfork issues

2006-12-22 Thread Casper . Dik
>Peter Buckingham <[EMAIL PROTECTED]> wrote: > >> Think of a situation where the memory footprint of the parent is large >> and you want execute something with a small footprint, eg execing >> something from a java process. >> >> The fact that you are execing means you don't need to access the a

Re: [osol-discuss] Re: Re: Re: vfork issues

2006-12-22 Thread Casper . Dik
>huy vu wrote: >> Thank to you both, Nacho and Joerg. However I would love to hear why >> the call to exec would fail right after a call to fork(). From >> reading things about vfork() it sounds like its sole purpose is to >> allow people to call exec right after a fork. I just like to >> understa

Re: [osol-discuss] Re: Re: vfork issues

2006-12-22 Thread Casper . Dik
>On 12/21/06, huy vu <[EMAIL PROTECTED]> wrote: >> Could someone tell me why one must use vfork() if one is to call exec right >> after? I am seeing e xec fails right after doing a fork() and would like to under stand why before trying vfork() >> >> Thanks, >> Huy >vfork() is not thread safe and