Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Casper . Dik
>No they need to decommisioned, moved else where, they are doing work >that the community is allready doing. Every package that is part of >CCD has been ported and availible in either sunrfreeware.com or >blastwave. The community is also doing a better job with a more >packages and more up to date

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Ignacio Marambio Catán
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Dickens wrote: > perhaps project approval is just too easy for Sun's pet projects. This > project was okayed only by Sun employees, I didn't notice anyone > outside of Sun giving an okay on this project, and at least one of the > one of the two

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Bart Smaalders
I'm both a user of blastwave and another Sun engineer cycle-stealing on this project. From my point of view, what I'd like to see happen with a community software distribution for Solaris Nevada is: 1) large scale participation of OpenSolaris developers/users. 2) automatic installation of requir

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Rich Teer
On Wed, 12 Apr 2006, Al Hopper wrote: > Alert! Alert! Massive outbreak of sarcasm detected! Possibly a 9 on the > Reichter Scale. Seek immediate shelter. Alert! Alert! :) I though the Richteer Scale was the unit of sarcasm? :-) -- Rich Teer, SCNA, SCSA, OpenSolaris CAB member

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Dennis Clarke
> Dennis Clarke wrote: >> There must be a way in which we can work together. Compromises made >> and fences dropped. I am always trying to be a peace maker despite >> all my noise and passion. > > So that's a +1 from you in favor of Keith's proposal to set up a project I blatantly disag

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Eric Boutilier
Glynn Foster wrote: Hey, On Wed, 2006-04-12 at 20:03 -0400, Bill Rushmore wrote: I see no reason why the community needs yet another project. We have two good places to get what we need what could a new community here provide besides usurping what has been done already? Again, I am not s

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Al Hopper
On Wed, 12 Apr 2006 [EMAIL PROTECTED] wrote: > > Bill Rushmore writes: > > I see no reason why the community needs yet another project. > > I hope we're not heading down a path where project creation can be > vetoed. The Project support on opensolaris.org should be available > for all ideas -- go

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Al Hopper
On Wed, 12 Apr 2006, James Dickens wrote: > On 4/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Bill Rushmore writes: > > > I see no reason why the community needs yet another project. > > > > I hope we're not heading down a path where project creation can be > > vetoed. The Project

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Alan Coopersmith
James Dickens wrote: perhaps project approval is just too easy for Sun's pet projects. Why should it be hard for any project? Perhaps "Project Approval" is the wrong term - this process is not supposed to indicate any stamp of approval of a proposed solution or exclusivisity - just that there'

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread David J. Orman
> perhaps project approval is just too easy for Sun's pet projects. This > project was okayed only by Sun employees, I didn't notice anyone > outside of Sun giving an okay on this project, and at least one of the > one of the two people that okayed the project had a vested interest in > it, "(a vol

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread lianep
"James Dickens" writes: > perhaps project approval is just too easy for Sun's pet projects. Or any community member's pet project... The projects page says: The process for requesting a new project requires that a community member write a proposal to the opensolaris-discuss list and at leas

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Keith M. Wesolowski
On Wed, Apr 12, 2006 at 08:03:54PM -0400, Bill Rushmore wrote: > I see no reason why the community needs yet another project. We have two > good places to get what we need what could a new community here provide > besides usurping what has been done already? Again, I am not saying this > to b

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread James Dickens
On 4/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Bill Rushmore writes: > > I see no reason why the community needs yet another project. > > I hope we're not heading down a path where project creation can be > vetoed. The Project support on opensolaris.org should be available > for all

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread lianep
"Dennis Clarke" writes: > > All of that said, I'd still love to understand how it is that someone > > can grab the source for all of blastwave and rebuild it on their > > own machine. Is that possible? Planned? > >Have a look at : http://svn.blastwave.org/ > > Please read : http://s

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Alan Coopersmith
Dennis Clarke wrote: There must be a way in which we can work together. Compromises made and fences dropped. I am always trying to be a peace maker despite all my noise and passion. So that's a +1 from you in favor of Keith's proposal to set up a project area/mailing list on opensolaris

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Dennis Clarke
> On Wed, 2006-04-12 at 20:03 -0400, Bill Rushmore wrote: >> I see no reason why the community needs yet another project. We have two >> good places to get what we need what could a new community here provide >> besides usurping what has been done already? Again, I am not saying this >> to be ar

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Dennis Clarke
> Bill Rushmore writes: >> I see no reason why the community needs yet another project. > > All of that said, I'd still love to understand how it is that someone > can grab the source for all of blastwave and rebuild it on their > own machine. Is that possible? Planned? Have a look at : http

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread lianep
Bill Rushmore writes: > I see no reason why the community needs yet another project. I hope we're not heading down a path where project creation can be vetoed. The Project support on opensolaris.org should be available for all ideas -- good, bad, and even duplicate ones. The existence of a p

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Glynn Foster
Hey, On Wed, 2006-04-12 at 20:03 -0400, Bill Rushmore wrote: > I see no reason why the community needs yet another project. We have two > good places to get what we need what could a new community here provide > besides usurping what has been done already? Again, I am not saying this > to be

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Bill Rushmore
On Wed, 12 Apr 2006, James Dickens wrote: No they need to decommisioned, moved else where, they are doing work that the community is allready doing. Every package that is part of CCD has been ported and availible in either sunrfreeware.com or blastwave. The community is also doing a better job w

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread James Dickens
On 4/12/06, Alan Coopersmith <[EMAIL PROTECTED]> wrote: > James Dickens wrote: > > Sounds like it will be impossible to get rolling. /opt/sfw is allready > > owned by CCD group. That group is about as closed as it gets, > > It sounds like you are bringing preconceptions to the table - what you > sa

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Keith M. Wesolowski
On Wed, Apr 12, 2006 at 04:37:59PM -0500, James Dickens wrote: > see http://www.opensolaris.org/jive/thread.jspa?messageID=7545 the > community aspects of the community was just a facade. To appear > opensolaris friendly... I participated in that thread at that time and I'm familiar with the issu

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Al Hopper
On Wed, 12 Apr 2006, Dennis Clarke wrote: > > On 4/12/06, Keith M. Wesolowski <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 12, 2006 at 01:55:43PM -0500, Tao Chen wrote: > > > > > How's the proposed project or "CCD" related to this announcement back in > > > Aug > > > 2005 ? > > > http://www.opensol

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread James Dickens
On 4/12/06, Keith M. Wesolowski <[EMAIL PROTECTED]> wrote: > On Wed, Apr 12, 2006 at 01:30:17PM -0500, James Dickens wrote: > > > Sounds like it will be impossible to get rolling. /opt/sfw is allready > > owned by CCD group. That group is about as closed as it gets, just > > This is news to me. I

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Dennis Clarke
> Darren J Moffat wrote: > So I setup the share manually in /etc/dfs/dfstab thus : > > ZFS filesystems are designed to be plentiful as water. Use them liberally. > :) It takes awhile to get used to the new administrative model, which is > very different from the traditional disk-oriented

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Dennis Clarke
On 4/12/06, Keith M. Wesolowski <[EMAIL PROTECTED]> wrote: > On Wed, Apr 12, 2006 at 01:55:43PM -0500, Tao Chen wrote: > > > How's the proposed project or "CCD" related to this announcement back in Aug > > 2005 ? > > http://www.opensolaris.org/jive/thread.jspa?messageID=7545 > > This project will f

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Jim Grisanzio
Thanks, Keith. You have seconds. Eric will get you guys set up. Jim Keith M. Wesolowski wrote: I'd like to propose a project similar to SFW Nevada for the forthcoming opening of the collection previously known as the Solaris Software Companion. This body of software consists of Free and Open S

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Keith M. Wesolowski
On Wed, Apr 12, 2006 at 01:55:43PM -0500, Tao Chen wrote: > How's the proposed project or "CCD" related to this announcement back in Aug > 2005 ? > http://www.opensolaris.org/jive/thread.jspa?messageID=7545 This project will form a collaborative effort to implement the changes described by Marily

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Keith M. Wesolowski
On Wed, Apr 12, 2006 at 01:30:17PM -0500, James Dickens wrote: > Sounds like it will be impossible to get rolling. /opt/sfw is allready > owned by CCD group. That group is about as closed as it gets, just This is news to me. I wasn't aware that such a 'CCD group' exists at all. One possibility

[osol-discuss] Re: Re: SUNWscpu ? Am I old fashioned and confused ?

2006-04-12 Thread UNIX admin
> which I rarely ever need as I rarely edit the > /etc/passwd file directly. You and me both. But what about others? > You are more likely to get a stream of other answers > also. Less expected. (:-D This one made me laugh! Honestly Dennis! Thanks for making my day! > I swear it was just a ex

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Alan Coopersmith
James Dickens wrote: Sounds like it will be impossible to get rolling. /opt/sfw is allready owned by CCD group. That group is about as closed as it gets, It sounds like you are bringing preconceptions to the table - what you say only holds true if you assume this is not the CCD team trying to o

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread Tao Chen
On 4/12/06, James Dickens <[EMAIL PROTECTED]> wrote: On 4/11/06, Keith M. Wesolowski <[EMAIL PROTECTED]> wrote:> I'd like to propose a project similar to SFW Nevada for> the forthcoming opening of the collection previously > known as the Solaris Software Companion.  [...]>> Sounds like it will be i

[osol-discuss] Re: First pass: updated General FAQ

2006-04-12 Thread Karyn Ritter
Below are the diffs in a more readable format. Apologies... - Karyn --- general_faq.txt --- 6c6 < [4] Why is Sun open sourcing the Solaris Operating System? --- > [4] Why has Sun open sourced the Solaris Operating System? 11,13c11 < [8] What release of the Solaris sourc

Re: [osol-discuss] Project proposal: Nevada Companion Software

2006-04-12 Thread James Dickens
On 4/11/06, Keith M. Wesolowski <[EMAIL PROTECTED]> wrote: > I'd like to propose a project similar to SFW Nevada for > the forthcoming opening of the collection previously > known as the Solaris Software Companion. This body > of software consists of Free and Open Source software > not supported b

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread James Carlson
Dan Price writes: > > Extremely irritating cron jobs and pointed sticks come to mind. :-/ > > The basic view in bugster is, effectively just a reflection of records > in a database. What it needs to be is a persistent workspace in which > you manage, query, view, edit, sort and sift single bugs

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread Dan Price
On Wed 12 Apr 2006 at 09:18AM, James Carlson wrote: > > > > I have no idea how you plan to encourage people to keep information > > in bugster accurate, but I wish you the best of luck :) > > Extremely irritating cron jobs and pointed sticks come to mind. :-/ The basic view in bugster is, effec

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Eric Lowe
Darren J Moffat wrote: So I setup the share manually in /etc/dfs/dfstab thus : # vi /etc/dfs/dfstab "/etc/dfs/dfstab" 1 lines, 97 characters share -F nfs -o ro=isis,root=isis -d "jumpstart" /export/zfs_0/jumpstart/s10/SXCRb35 So why did you do that rather than what it suggested you should do w

[osol-discuss] Re: Re: Solaris on Intel Macs??

2006-04-12 Thread Jürgen Keil
I wrote: > [While I'm in GRUB] I can type exactly *one* character on the usb keyboard. > When trying to > read a second character from the keyboard, the system hangs. I'd say this is an Apple BIOS bug. The following INT 16, Function 0 BIOS call (GET KEYSTROKE) hangs: (tested from DEBUG.EXE, u

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Darren J Moffat
Dennis Clarke wrote: On 4/12/06, Darren J Moffat <[EMAIL PROTECTED]> wrote: Dennis Clarke wrote: What the heck is that "/export/zfs_0 is already shared." ?? No its not. So I setup the share manually in /etc/dfs/dfstab thus : # vi /etc/dfs/dfstab "/etc/dfs/dfstab" 1 lines, 97 characters share

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Dennis Clarke
On 4/12/06, Peter Tribble <[EMAIL PROTECTED]> wrote: > On Wed, 2006-04-12 at 14:01, Dennis Clarke wrote: > > I like to perform little experiments. Its my nature. > ... > > So I wondered to myself .. just how small a footprint can SXCR have? > > > > I know that Eric Bootilier did some interesting w

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Dennis Clarke
On 4/12/06, Darren J Moffat <[EMAIL PROTECTED]> wrote: > Dennis Clarke wrote: > > What the heck is that "/export/zfs_0 is already shared." ?? > > No its not. > > > > So I setup the share manually in /etc/dfs/dfstab thus : > > > > # vi /etc/dfs/dfstab > > "/etc/dfs/dfstab" 1 lines, 97 characters > >

Re: [osol-discuss] W/ATTACHMENT-- OpenSolaris Featured in Linux Format Magazine--with BeliniX DVD!

2006-04-12 Thread Dennis Clarke
On 4/12/06, Laura Ramsey <[EMAIL PROTECTED]> wrote: > > They don't have it online yet. (strange, tho it is...) and so I'm looking > at the online publishing rights. > I'll negotiate Blastwave as one of the sites in the bid. > I was not going to republish. Just put a big fat link on the homepage

Re: [osol-discuss] Re: Project proposal: Nevada Companion Software

2006-04-12 Thread Dennis Clarke
> On 4/12/06, Dennis Clarke <[EMAIL PROTECTED]> wrote: >> >> > On Tue, 11 Apr 2006, Michael Lee wrote: >> > >> >> I think a better idea might be to create something like Blastwave but >> for >> >> Solaris 10 Sparc and x86, where we can just install software into >> /opt/sfw >> >> using pkg-get or s

Re: [osol-discuss] W/ATTACHMENT-- OpenSolaris Featured in Linux Format Magazine--with BeliniX DVD!

2006-04-12 Thread Laura Ramsey
They don't have it online yet. (strange, tho it is...) and so I'm looking at the online publishing rights. I'll negotiate Blastwave as one of the sites in the bid. BRB, LKR Dennis Clarke wrote: Laura Ramsey wrote: This just in from Chhandomay--the OpenSolaris fea

Re: [osol-discuss] W/ATTACHMENT-- OpenSolaris Featured in Linux Format Magazine--with BeliniX DVD!

2006-04-12 Thread Dennis Clarke
> Laura Ramsey wrote: > >> >> This just in from Chhandomay--the OpenSolaris feature and BeliniX DVD >> is out.. in the April edition of Linux Format. >> Congrats Moinak! thanks Dennis! Thanks ERIC! Great visibility for >> the OpenSolaris community! >> >> Cheers! >> LKR >> The is a beautiful lo

Re: [osol-discuss] Re: Project proposal: Nevada Companion Software

2006-04-12 Thread Ignacio Marambio Catán
On 4/12/06, Dennis Clarke <[EMAIL PROTECTED]> wrote: > > > On Tue, 11 Apr 2006, Michael Lee wrote: > > > >> I think a better idea might be to create something like Blastwave but for > >> Solaris 10 Sparc and x86, where we can just install software into /opt/sfw > >> using pkg-get or something simil

Re: [osol-discuss] Re: Project proposal: Nevada Companion Software

2006-04-12 Thread Dennis Clarke
> On Tue, 11 Apr 2006, Michael Lee wrote: > >> I think a better idea might be to create something like Blastwave but for >> Solaris 10 Sparc and x86, where we can just install software into /opt/sfw >> using pkg-get or something similar. It'll be far more useful than a >> co-bundled product, which

Re: [osol-discuss] Re: Project proposal: Nevada Companion Software

2006-04-12 Thread Michael Lee
You're right that's a much better idea. It'll be great if Sun could just get behind Blastwave.On 4/12/06, Bill Rushmore < [EMAIL PROTECTED]> wrote:On Tue, 11 Apr 2006, Michael Lee wrote:> I think a better idea might be to create something like Blastwave but for Solaris 10 Sparc and x86, where we ca

[osol-discuss] OpenSolaris Featured in Linux Format Magazine--with BeliniX DVD!

2006-04-12 Thread Laura Ramsey
This just in from Chhandomay--the  OpenSolaris feature and BeliniX DVD is out.. in the April edition of Linux Format. Congrats Moinak!  thanks Dennis! Thanks ERIC!  Great visibility for the OpenSolaris community! Cheers! LKR --- All: Mike Saunders published a very positive, in-depth 'h

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Peter Tribble
On Wed, 2006-04-12 at 14:01, Dennis Clarke wrote: > I like to perform little experiments. Its my nature. ... > So I wondered to myself .. just how small a footprint can SXCR have? > > I know that Eric Bootilier did some interesting work with the reduced core > install cluster and I was thinking o

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread James Carlson
John Levon writes: > I really wish people would just remove themselves as RE when they're not doing > anything, I find it really annoying. I bet there's a number of bugs that > actually aren't getting fixed due to old RE entries. There's no way to tell. The standing rule I've heard is that if you

Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Darren J Moffat
Dennis Clarke wrote: What the heck is that "/export/zfs_0 is already shared." ?? No its not. So I setup the share manually in /etc/dfs/dfstab thus : # vi /etc/dfs/dfstab "/etc/dfs/dfstab" 1 lines, 97 characters share -F nfs -o ro=isis,root=isis -d "jumpstart" /export/zfs_0/jumpstart/s10/SXCRb35

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread John Levon
On Wed, Apr 12, 2006 at 09:06:39AM -0400, James Carlson wrote: > However, I think that a similar argument can be made for why RE != > NULL is a useless test. Of course. The question is whether it's more or less useless. I really wish people would just remove themselves as RE when they're not doi

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread James Carlson
John Levon writes: > I'm not suggesting that we hide the bug status, just that if we're going to > have a background colour for anything, then RE != NULL is more useful than > Accepted vs. Dispatched. Maybe ... but if we do that, we should include "escalation exists" in the RE != NULL test because

[osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

2006-04-12 Thread Dennis Clarke
I like to perform little experiments. Its my nature. Maybe I always wanted to be a scientist and dropped out of the masters program level to go get a real job with Pratt & Whitney and played with interesting materials in turbo fan jet engine blades. And I like to perform little experiments but

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread John Levon
On Wed, Apr 12, 2006 at 08:54:22AM -0400, James Carlson wrote: > John Levon writes: > > But this is a big list of bugs with a "come fix this" keyword already added. > > That is, they've clearly been triaged at least to the point where it's > > considered a relatively easy fix. > > What it seems t

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread James Carlson
John Levon writes: > But this is a big list of bugs with a "come fix this" keyword already added. > That is, they've clearly been triaged at least to the point where it's > considered a relatively easy fix. What it seems to me that you're suggesting is that instead of trying to make sure that peop

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread John Levon
On Wed, Apr 12, 2006 at 08:41:40AM -0400, James Carlson wrote: > "Accepted" should mean that someone thinks there's enough data > provided to evaluate it, and that it's at about the right priority and > in the right cat/subcat. Not much else. Sad to say but I've seen that not be the case several

Re: [request-sponsor] Re: [osol-discuss] Contributing Code

2006-04-12 Thread James Carlson
John Levon writes: > It doesn't seem useful to me to split out "Accepted" bugs. The "accepted" > state > doesn't really mean very much at all (I've even seen it on bugs that haven't > even been triaged). Not all groups actually have some sort of formal triage process. "Accepted" should mean that

Re: [osol-discuss] Re: Project proposal: Nevada Companion Software

2006-04-12 Thread Bill Rushmore
On Tue, 11 Apr 2006, Michael Lee wrote: I think a better idea might be to create something like Blastwave but for Solaris 10 Sparc and x86, where we can just install software into /opt/sfw using pkg-get or something similar. It'll be far more useful than a co-bundled product, which gets too s

Re: [osol-discuss] Re: SUNWscpu ? Am I old fashioned and confused ?

2006-04-12 Thread Dennis Clarke
>> Do we need vipw to safely edit the /etc/passwd >> file ? > > Yes, if you want sanity checks performed on the edit. which I rarely ever need as I rarely edit the /etc/passwd file directly. > > What did it say up there on the top of the man page? It says old .. really really old. In a world

Re: [osol-discuss] Re: SUNWscpu ? Am I old fashioned and confused ?

2006-04-12 Thread Dennis Clarke
On 4/12/06, UNIX admin <[EMAIL PROTECTED]> wrote: > > Do you realize what this could mean ? > > > > What the... > > I haven't used separate FileSystems since PROM 1.x, where the / FS couldn't > be booted by the PROM if it had been greater than 1GB. > gee .. someone rolled out of the sarcasm bed t

Re: [osol-discuss] Re: Re: Slowaris vs. Solaris

2006-04-12 Thread Peter Tribble
On Fri, 2006-03-31 at 11:52, UNIX admin wrote: > > That's not how I understood it. I thought the idea > > was that the package > > would be stored as a single file in datastream format > > rather than unpacked > > in filesystem format. Which would cut down a lot of > > the small I/O operations that

[osol-discuss] Re: SUNWscpu ? Am I old fashioned and confused ?

2006-04-12 Thread UNIX admin
> Do you realize what this could mean ? > > It could mean that separate filesystems could be > abolished. At least once > upon a time, way way back in the Solaris 2.5.1 days I > would regularly create > a separate / and /var and /usr and certainly a > separate /opt on any server > or workstation.

[osol-discuss] Re: SUNWscpu ? Am I old fashioned and confused ?

2006-04-12 Thread UNIX admin
> Do we need vipw to safely edit the /etc/passwd > file ? Yes, if you want sanity checks performed on the edit. > SunOS/BSD Compatibility Package Commands > vipw(1B) > - edit the password file > Well, perhaps this manpage has not be touched in 14 > years because "if its > not br

[osol-discuss] Re: Solaris on Intel Macs??

2006-04-12 Thread UNIX admin
> By adding "debug printfs" to the grub source code; I > used > console_putchar(char) calls. And building a custom > bootable Solaris x86 CD > with the modified boot/grub/stage2_eltorito file. > > The character printed before the gateA20(1) call in > init_bios_info() > appeared on the console, th

[osol-discuss] Re: Re: Re: Re: C shells

2006-04-12 Thread UNIX admin
> I'm sure you're absolutely correct! The question is, > *when* will they > be satisfied? Now that's the tricky part. You see, someone (incidentally from Sun) once wrote that "your product is only as good as your test suite". So when one thinks about it, how does one design an effective test

Re: [osol-discuss] Re: Re: Re: C shells

2006-04-12 Thread David J. Orman
On Apr 11, 2006, at 8:59 PM, UNIX admin wrote: Your point is very well taken. I am not a proponent of stasis, however I am a strong proponent of balance when it comes to these issues; I strongly believe that *moderation* between new features and forward/backward compatibility is the opt

[osol-discuss] Re: Re: Re: C shells

2006-04-12 Thread UNIX admin
> This, however, does not mean this is the best, or > even a *good* solution. > It's terrible. For every little change it takes me > 20x the amount of time > it would if this were running on a modern system. The > mainframes draw > enough power to light up NYC. You could re-write the > whole financ