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

2005-07-07 Thread Shawn Walker
On 7/8/05, Danek Duvall <[EMAIL PROTECTED]> wrote: +1000 - a post put far more elegantly than I could given your internal knowledge and experience Thanks for the mini-insight into SUN's outlook on even "small" changes! -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://bi

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

2005-07-07 Thread Danek Duvall
On Thu, Jul 07, 2005 at 10:17:56PM -0500, Tao Chen wrote: > I vote for changing the default shell to a better one. Ah, but then the question is, which one. You might choose ksh over bash for various reasons, others might prefer tcsh, and some of us know that zsh is the One True Shell. If nothin

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

2005-07-07 Thread Dennis Clarke
On 7/7/05, Tao Chen <[EMAIL PROTECTED]> wrote: > On 7/7/05, Sunil <[EMAIL PROTECTED]> wrote: > > I remember there was a "library dependency" argument against changing the > default shell for root. > However at least in Solaris 10: > > # ldd /bin/sh > libgen.so.1 => /lib/libgen.so.

Re: [osol-discuss] London

2005-07-07 Thread Sean Sprague
It has been a very difficult day for us all, and we very much appreciate the solidarity that George W. Bush, yourself, and I am sure the entire American public has shown us today. And not forgetting the rest of the world, naturally ;-) ___ opensolaris

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

2005-07-07 Thread Sittichai Palanisong
I always edit /etc/passwd manually to change root's shell to ksh and change home to /root. And add followings to /etc/profile: VISUAL=vi PS1=`uname -n`:'${PWD##*/}# ' export VISUAL PS1 This will enable vi commandline edit mode and also a nice prompt :-) This message posted from opensolaris.org _

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

2005-07-07 Thread Sunil
> I remember there was a "library dependency" > argument against changing the default shell for > root. /bin/bash and /bin/sh depend on exact same # libraries on solaris 10. And /bin/sh is a link to /sbin/sh. root's (static before 10) shell and normal bourne shell are no longer different. so root

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Glynn Foster
Heya, > Hope that makes some sense, even if you don't agree that it's the right way > to go. Glynn, or maybe Alan, might be able to offer further words on why > they're done that way -- maybe "The ARC made us do it". ;-) 'The ARC made us do it' ;) Seriously though, I think the current packagin

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

2005-07-07 Thread Tao Chen
On 7/7/05, Sunil <[EMAIL PROTECTED]> wrote: I don't think anybody is getting your point and I think they never will, and it is the same mentality that has cost sun bigtime in last 3 years Considering some of the illogical arguments against changing the default shell that we see in this dicussion, I

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

2005-07-07 Thread Shawn Walker
On 7/7/05, Sunil <[EMAIL PROTECTED]> wrote: > can you please list one such incompatibility? Shell wise? Not specifically. But I can list a few of *many* issues that I've had over the years when upgrading to newer Linux distributions: * glibc ABI changes breaking my binaries (I won't even talk abo

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

2005-07-07 Thread Sunil
> The operating system on your thousands of Linux boxes > have never had > to worry about satisfying the needs of millions of > customers while > retaining backwards compatibility. It is a certainty > that if SUN > decided to change the default shell that at least > some of their > customers (if no

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Joe Halpin
W. Wayne Liauh wrote: I am wondering if anyone would be interested in discussing Solaris_86 (10 and later) vis-a-vis Linux? I have been using Red Hat Linux since 4.2 and am very pleased, as far as desktops are concerned, with Fedora Core 4. However, because of several critical issues (e.g., ina

[osol-discuss] Re: Errors with mounting of boot archive

2005-07-07 Thread Sunil
just to document the problem here: when I rebooted the kernel with 'reboot -- 'kernel.mine/unix'' the file /platform/i86pc/boot_archive was updated to be 20bytes. All I did to recover from this failure was to boot in failsafe mode, mount my root partition and remove /a/platform/i86pc/boot_archiv

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

2005-07-07 Thread Joe Halpin
Rich Teer wrote: On Thu, 7 Jul 2005, Sunil wrote: /bin/bash is compatible. our shell scripts (with #!/bin/sh at top) Not completely so (or at least, that was the case historically). The points of incompatibility are very small, and I've never run into one. One thing that can be said in fav

[osol-discuss] gnome/jds packaging (Was: Insecure by default)

2005-07-07 Thread Laszlo Peter
Hey, On Thu, 2005-07-07 at 18:20, [EMAIL PROTECTED] wrote: > >On Thu, Jul 07, 2005 at 08:31:55PM +0100, Peter C. Tribble wrote: > > > >> Why on earth does gnome/jds come in 200 odd separate packages? Does the > >> split of files make any sense? > > > >It does, but it's reasonably arcane, and like

[osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Nikolay Molchanov
I think this discussion perfectly describes current situation :-) a) There is a large group of developers who use TW everyday, and don't want to use CVS or SVN because ... (see mails above for details). b) There is another group of developers who use CVS and don't want to use TW or SVN because ..

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

2005-07-07 Thread Rich Teer
On Thu, 7 Jul 2005, Sunil wrote: > /bin/bash is compatible. our shell scripts (with #!/bin/sh at top) Not completely so (or at least, that was the case historically). > it fixed sooner than you would make /bin/sh POSIX compliant. People > have put in lot of effort there. That's great to hear.

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

2005-07-07 Thread Rich Teer
On Thu, 7 Jul 2005, Gerhard S. wrote: > > POSIX compliance is a key feature of Solaris, I > > wouldn't expect SUN to > > change this. > > Can you please quote the part of POSIX that > forbids having working cursor keys in a shell? > Hint: You won't find it. There isn't any. Is there a section tha

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

2005-07-07 Thread Sunil
> Even if the Solaris bourne shell isn't POSIX > compliant (which I have > perhaps wrongly assumed it was), you still have the > issue of backwards > compatability, and that is a paramount feature in > enterprise level > systems. /bin/bash is compatible. our shell scripts (with #!/bin/sh at top) fr

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

2005-07-07 Thread Gerhard S.
> I don't think anybody is getting your point and I > think they never will, I start to get a similar feeling. > I have never understood why is sun still stuck with > bourne shell as the default shell when bash has been > a stable and compatible shell for years and is so > popular with developer

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

2005-07-07 Thread Shawn Walker
On 7/7/05, Gerhard S. <[EMAIL PROTECTED]> wrote: > Can you please quote the part of POSIX that > forbids having working cursor keys in a shell? > Hint: You won't find it. There isn't any. I never said that it did. But, it does require certain actions all the way down to how the cursor behaves when

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

2005-07-07 Thread Shawn Walker
On 7/7/05, Sunil <[EMAIL PROTECTED]> wrote: > I don't think anybody is getting your point and I think they never will, and > it is the same mentality that has cost sun bigtime in last 3 years (if only > sun had the vision of open sourcing solaris even during or close to dotcom > bust, it would h

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

2005-07-07 Thread Sunil
> http://www.opengroup.org/onlinepubs/009695399/utilitie > s/sh.html this doc says 'set -o vi' should set vi command line editing mode. As far as I remember, 'set -o vi' only works in ksh. So, how is /bin/sh compiliant to this standard? This message posted from opensolaris.org ___

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

2005-07-07 Thread Gerhard S.
> On 7/7/05, Gerhard S. <[EMAIL PROTECTED]> > wrote: > > But shouldn't be needed. In Linux it works all out > of > > the box without adding magic commands. > > POSIX compliance is a key feature of Solaris, I > wouldn't expect SUN to > change this. Can you please quote the part of POSIX that forbi

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

2005-07-07 Thread Sunil
I don't think anybody is getting your point and I think they never will, and it is the same mentality that has cost sun bigtime in last 3 years (if only sun had the vision of open sourcing solaris even during or close to dotcom bust, it would have been opensolaris all over not linux). Doing cool

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

2005-07-07 Thread Shawn Walker
On 7/7/05, Gerhard S. <[EMAIL PROTECTED]> wrote: > But shouldn't be needed. In Linux it works all out of > the box without adding magic commands. POSIX compliance is a key feature of Solaris, I wouldn't expect SUN to change this. > In what way is making broken cursor keys work > not backward comp

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

2005-07-07 Thread Rich Teer
On Thu, 7 Jul 2005, Gerhard S. wrote: > > > typing bash or ksh set -o emacs after every su. Not > > very friendly. > > So put it into root's .profile. Not exactly hard > > work. > > But shouldn't be needed. In Linux it works all out of > the box without adding magic commands. Solaris is not Linu

Re: [osol-discuss] London

2005-07-07 Thread Sean Sprague
All the best to our community members and their family and friends in London today. Our thoughts and prayers are with you. My wife arrived at work in the Liverpool Street area of London about 10 minutes before the explosions commenced. Much too close for my liking. The report that hurt me th

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

2005-07-07 Thread Gerhard S.
> On Thu, 7 Jul 2005, Gerhard S. wrote: > > > if I change the root default shell to bash. So now > I end up > > typing bash or ksh set -o emacs after every su. Not > very friendly. > So put it into root's .profile. Not exactly hard > work. But shouldn't be needed. In Linux it works all out of t

Re: [osol-discuss] great, now we can google the source!

2005-07-07 Thread Alan Hargreaves - Product Technical Support (APAC)
[EMAIL PROTECTED] wrote: Just noticed today. For example, googling for "environ_base" takes you straight to ... http://cvs.opensolaris.org/source/raw/usr/src/lib/libc/port/gen/getenv.c ... of course. But still, how cool is that?! It was indexed almost the first day, I think. Who needs csc

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Shawn Walker
On 7/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Is there really a good reason, though, to make GNOME more than five > packages? As long as we don't do RPM style patches, who would install > only M out of N GNOME packages (not to pick on GNOME, we all offend here). >From an end user stan

[osol-discuss] Errors with mounting of boot archive

2005-07-07 Thread Sunil
So, I cap-eye-installed the kernel as kernel.mine and did reboot -- 'kernel.mine/unix'. Panic with these errors: reading beyond end of ramdisk start=0x2000 size=0x2000 failed to read superblock panic : can't mount boot archive There are two filelist.ramdisk file

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Danek Duvall
On Fri, Jul 08, 2005 at 12:20:21AM +0200, [EMAIL PROTECTED] wrote: > Is there really a good reason, though, to make GNOME more than five > packages? As long as we don't do RPM style patches, who would install > only M out of N GNOME packages (not to pick on GNOME, we all offend here). > > What m

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Casper . Dik
>On Thu, Jul 07, 2005 at 08:31:55PM +0100, Peter C. Tribble wrote: > >> Why on earth does gnome/jds come in 200 odd separate packages? Does the >> split of files make any sense? > >It does, but it's reasonably arcane, and like Casper said, it suffers >greatly from the lack of good tools to manage

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Danek Duvall
On Thu, Jul 07, 2005 at 08:31:55PM +0100, Peter C. Tribble wrote: > Why on earth does gnome/jds come in 200 odd separate packages? Does the > split of files make any sense? It does, but it's reasonably arcane, and like Casper said, it suffers greatly from the lack of good tools to manage it. Eac

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Shawn Walker
On 7/7/05, Patrick Mauritz <[EMAIL PROTECTED]> wrote: > > Clarify, please? I don't understand this comment. > the use of libneon (is it finally stable, after 5 years?), apache2 with > their > own module - or alternatively ssh+svnserve (which needs full blown > accounts > on the machine for every de

Re: [osol-discuss] Re: RE: Re: Solaris vs. Linux

2005-07-07 Thread Rich Teer
On Thu, 7 Jul 2005, Gerhard S. wrote: > That's fine. But why does /bin/sh not just implement > command line editing? It's not that cursor key support Because then it wouldn't be the Bourne Shell! Solaris takes backwards compatibility more seriously than other OSes... > Also why are the cursor k

[osol-discuss] Re: RE: Re: Solaris vs. Linux

2005-07-07 Thread Gerhard S.
> Yes, in Solaris, Sun has stuck with good old Bourne good? > Shell for the default root shell. For users, the > shell is up to the administrator. The bells and > whistles you are talking about in Linux come from > them using BASH (Bourne Again Shell) by default. I know this. > of Solaris 10

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

2005-07-07 Thread Rich Teer
On Thu, 7 Jul 2005, Gerhard S. wrote: > if I change the root default shell to bash. So now I end up > typing bash or ksh set -o emacs after every su. Not very friendly. So put it into root's .profile. Not exactly hard work. > Why do this not work out of the box? Now it has all this eye candy Ba

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

2005-07-07 Thread Gerhard S.
> > >One technical difference is that cursor keys and > command line editing and completion generally wor > ks out of the box in Linux and it generally doesn't > in Solaris. I hope OpenSolaris will finally fix > that usability issue so that it can lose that "80ies > s feeling" > >and be more user

Re: [osol-discuss] great, now we can google the source!

2005-07-07 Thread Casper . Dik
>Just noticed today. For example, googling for "environ_base" takes you >straight to ... > > http://cvs.opensolaris.org/source/raw/usr/src/lib/libc/port/gen/getenv.c > >... of course. But still, how cool is that?! It was indexed almost the first day, I think. Who needs cscope now :-) Casper

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Patrick Mauritz
On Thu, 2005-07-07 at 18:19, Shawn Walker wrote: > I thought you were speaking of the fact that anonymous read access to > SVN using Apache requires write access to the repository whereas > svnserve + fsfs does not (if I remember correctly). That's what I was > referring to anyway... I don't even k

[osol-discuss] great, now we can google the source!

2005-07-07 Thread Phil Harman
Just noticed today. For example, googling for "environ_base" takes you straight to ... http://cvs.opensolaris.org/source/raw/usr/src/lib/libc/port/gen/getenv.c ... of course. But still, how cool is that?! Phil smime.p7s Description: S/MIME Cryptographic Signature

[osol-discuss] London

2005-07-07 Thread Jim Grisanzio
All the best to our community members and their family and friends in London today. Our thoughts and prayers are with you. Jim ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

[osol-discuss] Re: I hosed my install

2005-07-07 Thread Sunil
I will really appreciate some help here:( This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Casper . Dik
>Then surely the completely arbitrary way that Solaris is split into >packages needs to be fixed. Indeed. >Why on earth does gnome/jds come in 200 odd separate packages? Does the >split of files make any sense? No; especially not considering that there's no tool which allows you to visualize th

[osol-discuss] Re: Insecure by default

2005-07-07 Thread A K Saravanan
I think we should consider the security "capabilities" of the OS instead of the "security settings" that that are set by default. Solaris is very much stronger in its security features. This message posted from opensolaris.org ___ opensolaris-discuss ma

Re: [osol-discuss] Re: Re: Insecure by default

2005-07-07 Thread Peter C. Tribble
Richard Elling <[EMAIL PROTECTED]> said On Fri, 24 Jun 2005, Paul Walsh wrote: > I remember being told by the tutor on a Solaris SysAdmin course to > always choose "Entire distribution + OEM support" Nowadays I'm not so I think that's very poor advice. >>> >>>In gen

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Casper . Dik
Well, with the fixed AML the system now detects its floppy again; not that I can check that it works, remotely, but this is nice. @@ -1350,13 +1350,6 @@ FDCT, 8 } -OperationRegion (PCIC, SystemIO, 0x0CF8, 0x08) -Field (P

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Dana H. Myers
[EMAIL PROTECTED] wrote: I'm more inclined to add an additional acpi-user-options bit to permit users to relax the I/O permission checks. Legacy acpi_intp had no permission check and I don't recall any bugs filed, though any problem resulting from non-atomic access to PCI config space is likely

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Casper . Dik
>I'm more inclined to add an additional acpi-user-options bit >to permit users to relax the I/O permission checks. Legacy >acpi_intp had no permission check and I don't recall any >bugs filed, though any problem resulting from non-atomic access >to PCI config space is likely to be pretty mysterio

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Dana H. Myers
[EMAIL PROTECTED] wrote: The system ACPI BIOS is attempting to access PCI configuration space directly rather than using the correct PCI Config space operation regions. This is unsafe - directly accessing config space like this is non-atomic. The OSL implementation blocks these accesses. Perh

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Casper . Dik
>[EMAIL PROTECTED] writes: > >> PS: What is the status of iasl? Getting a standard Solaris iasl binary >> out would be very helpful. > >Dan Mick put one at > > ftp://playground.sun.com/pub/dmick/iasl > >some time ago. Excellent; with "iasl -g" you can extract the AML code from the system

[osol-discuss] Re: I hosed my install

2005-07-07 Thread Sunil
this is the setup I have as seen from grub.conf: hd0,0 -> XP hd0,1 -> OS hd1,0 -> Linux grub is installed from linux onto hd0. Now I can boot both linux and xp thru grub, but OS gives the "panic: can't mount boot archives". I can mount the partition in failsafe mode and access all data in it. B

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Rainer Orth
[EMAIL PROTECTED] writes: > PS: What is the status of iasl? Getting a standard Solaris iasl binary > out would be very helpful. Dan Mick put one at ftp://playground.sun.com/pub/dmick/iasl some time ago. Rainer -- --

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Casper . Dik
>The system ACPI BIOS is attempting to access PCI configuration space >directly rather than using the correct PCI Config space operation regions. >This is unsafe - directly accessing config space like this is non-atomic. >The OSL implementation blocks these accesses. Perhaps, Dana, you can give

[osol-discuss] Re: Re: vt's

2005-07-07 Thread Sunil
> I would think a simple solution to that would be that > when vt's are > enabled, to add the ability to have the system is the vt code still present? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opens

Re: [osol-discuss] Open Solaris on SPARC sans piggies

2005-07-07 Thread Shawn Walker
On 7/5/05, A G T <[EMAIL PROTECTED]> wrote: > It certainly is nowadays. > Old assembler language guys cringe at wasted bytes though ; > Perhaps, but even as someone that used to write assembly language, I'll take portable, easier to maintain code over something that's extremely efficient but diffi

Re: [osol-discuss] Re: Re: Re: Feature request

2005-07-07 Thread Dana H. Myers
Joerg Schilling wrote: If I plug in a PS/2 mouse (even after the system is booted successfully) the keyboard becomes non-functional until the system is rebooted. That's odd. I'll have to forward this to the keyboard/mouse team; it doesn't sound directly related to ACPI. Though... OK, here

Re: [osol-discuss] Open Solaris on SPARC sans piggies

2005-07-07 Thread A G T
On Tue, 5 Jul 2005, Rich Teer wrote: Date: Tue, 05 Jul 2005 18:58:44 -0700 (PDT) From: Rich Teer <[EMAIL PROTECTED]> To: AG Toon <[EMAIL PROTECTED]> Cc: opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] Open Solaris on SPARC sans piggies On Tue, 5 Jul 2005, AG Toon wrote: So wha

Re: [osol-discuss] Re: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread matty91
On Thu, 7 Jul 2005, [UTF-8] Jürgen Keil wrote: Issue 2: CPU type is not derived correctly -- hard code/`uname -p` -bash-3.00$ grep -n "^cpu" configure 29:cpu=`uname -m` Under Solaris, `uname -m` returns the hardware architecture: $ uname -m sun4u I'd say that's not a problem, because two li

Re: [osol-discuss] Thus far netboot of onv_16 is not working at all

2005-07-07 Thread Dennis Clarke
On 7/7/05, Robert Milkowski <[EMAIL PROTECTED]> wrote: > Hello Dennis, > > Monday, June 13, 2005, 12:56:26 AM, you wrote: > > > I'm just trying it - I actuall managed to boot kernel this way, can't > go any further 'coz ethernet driver is missing. Now I'm trying to > change miniroot :) > > Anyw

[osol-discuss] Re: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Jürgen Keil
> Issue 2: CPU type is not derived correctly -- hard code/`uname -p` > > -bash-3.00$ grep -n "^cpu" configure > 29:cpu=`uname -m` > > Under Solaris, `uname -m` returns the hardware > architecture: > > $ uname -m > sun4u I'd say that's not a problem, because two lines further down the configure

Re: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005 [EMAIL PROTECTED] wrote: On Thu, 7 Jul 2005, Dragan Cvetkovic wrote: On Thu, 7 Jul 2005, [UTF-8] Jürgen Keil wrote: Apropos qemu, does it work for you on b16 or b17, x86 platform? Which version are you using? Which hardware architecture are you attempting to build un

[osol-discuss] Creating Communities: Request for Enhancement

2005-07-07 Thread Jaime Cardoso
Hello People I see several people here talking about the creation of communities (good, good) but, I have a request for the web devs of Opensolaris. Each community discussion forum should have a Sticky thread (a thread always on top with no one but the community leader could edit) with the rule

Re: [osol-discuss] Re: vt's

2005-07-07 Thread Rich Teer
On Thu, 7 Jul 2005, Calum Benson wrote: > There's been some debate in the past about whether it's a potential > security risk or not (since it's quite easy to leave yourself logged > in as root on a VT and forget about it, for example-- and of course > it's not then protected by your screensaver/l

Re: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread matty91
On Thu, 7 Jul 2005, Dragan Cvetkovic wrote: On Thu, 7 Jul 2005, [UTF-8] J?rgen Keil wrote: Apropos qemu, does it work for you on b16 or b17, x86 platform? [snip] when compiled with /opt/csw/gcc3/bin/gcc it starts, but does nothing. No windows opens, and after some 10-15 minutes of frene

Re: [osol-discuss] Re: vt's

2005-07-07 Thread Shawn Walker
On 7/7/05, Calum Benson <[EMAIL PROTECTED]> wrote: > On 7 Jul 2005, at 16:41, Sunil wrote: > > why would anybody remove such a useful thing? how do we debug X > > hangs for example? > > There's been some debate in the past about whether it's a potential > security risk or not (since it's quite eas

Re: [osol-discuss] Re: vt's

2005-07-07 Thread Calum Benson
On 7 Jul 2005, at 16:41, Sunil wrote: why would anybody remove such a useful thing? how do we debug X hangs for example? There's been some debate in the past about whether it's a potential security risk or not (since it's quite easy to leave yourself logged in as root on a VT and forget

Re: [osol-discuss] Thus far netboot of onv_16 is not working at all

2005-07-07 Thread Robert Milkowski
Hello Dennis, Monday, June 13, 2005, 12:56:26 AM, you wrote: DC> I have created a jumpstart server on both x86 and Sparc servers and DC> both result in the same errors when I attempt to add a install client DC> : DC> # ./add_install_client -t /mnt/jumpstart/Solaris_11/Tools/Boot charon i86pc DC>

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Shawn Walker
On 7/7/05, Patrick Mauritz <[EMAIL PROTECTED]> wrote: > On Thu, Jul 07, 2005 at 11:00:30AM -0500, Shawn Walker wrote: > > That's not true of svn as far as the write access is concerned. At > > least if you're using svnserve + fsfs. > uh, how does the method with which writing to the server and stor

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Patrick Mauritz
On Thu, Jul 07, 2005 at 11:00:30AM -0500, Shawn Walker wrote: > That's not true of svn as far as the write access is concerned. At > least if you're using svnserve + fsfs. uh, how does the method with which writing to the server and storage is done affect the general necessity to allow writing to t

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Shawn Walker
On 7/7/05, Dennis Clarke <[EMAIL PROTECTED]> wrote: > Sorry, this has been a long winding post ( as is usual from me ) and I > am simply pouring out my thoughts here. +1 as usual -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005, Joerg Schilling wrote: You don't seem to understand that a "stable" kernel offers stable interfaces. Linux-2.6 does not and for this reason cannot be called stable. Can't we leave this kind of discussion to c.u.s /c.o.l.a crossposts? I don't think we need another list to d

Re: [osol-discuss] Re: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005, Shawn Walker wrote: On 7/7/05, Dragan Cvetkovic <[EMAIL PROTECTED]> wrote: Well, I probably didn't have SDL installed on my machine so it didn't detect it. Anyway, I downloaded qemu from blastvawe testing (why does it has CSWgcc3 as one dependency?) and am now booting the l

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Shawn Walker
On 7/7/05, Patrick Mauritz <[EMAIL PROTECTED]> wrote: > On Thu, 2005-07-07 at 09:44, Darren Kenny wrote: > > CVS and SVN were designed with globally spread out developers in mind - > > TW wasn't. I think > > this is what makes them stronger candidates as a code management system > > for OpenSolaris

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Joerg Schilling
Chris Ricker <[EMAIL PROTECTED]> wrote: > On Thu, 7 Jul 2005, Joerg Schilling wrote: > > > And BTW: it is definitely unfair to compare an instable devleopment kernel > > from > > Linux (2.6) with a stable Solaris-10. A fair comparison would compare > > Linux2.6 > > with Solaris-11 or Solaris-10

Re: [osol-discuss] Re: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Shawn Walker
On 7/7/05, Dragan Cvetkovic <[EMAIL PROTECTED]> wrote: > Well, I probably didn't have SDL installed on my machine so it didn't > detect it. Anyway, I downloaded qemu from blastvawe testing (why does it > has CSWgcc3 as one dependency?) and am now booting the latest knoppix. It > is rather slow, bu

Re: [osol-discuss] Re: A macsot for SchilliX

2005-07-07 Thread Joerg Schilling
Dennis Clarke <[EMAIL PROTECTED]> wrote: > On 7/7/05, Joerg Schilling <[EMAIL PROTECTED]> wrote: > > Dennis Clarke <[EMAIL PROTECTED]> wrote: > > > > > Whatever it is .. it looks good. And he is a happy looking fellow isn't > > > he? > > > > Should should have seen him at the time when there

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

2005-07-07 Thread Joerg Schilling
"Albertson, Brett" <[EMAIL PROTECTED]> wrote: > Yes, in Solaris, Sun has stuck with good old Bourne Shell for the default > root shell. For users, the shell is up to the administrator. The bells and > whistles you are talking about in Linux come from them using BASH (Bourne > Again Shell) by

[osol-discuss] Re: vt's

2005-07-07 Thread Sunil
why would anybody remove such a useful thing? how do we debug X hangs for example? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

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

2005-07-07 Thread Joerg Schilling
"Gerhard S." <[EMAIL PROTECTED]> wrote: > One technical difference is that cursor keys and command line editing and > completion generally works out of the box in Linux and it generally doesn't > in Solaris. I hope OpenSolaris will finally fix that usability issue so that > it can lose that "80

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Chris Ricker
On Thu, 7 Jul 2005, Joerg Schilling wrote: > And BTW: it is definitely unfair to compare an instable devleopment kernel > from > Linux (2.6) with a stable Solaris-10. A fair comparison would compare Linux2.6 > with Solaris-11 or Solaris-10 with Linux-2.4 (which is the latest stable > Linux). N

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Cyril Plisko
On Thu, 2005-07-07 at 18:28, Joerg Schilling wrote: > [EMAIL PROTECTED] wrote: > > > The fact that developers all write to the main repository for their > > branches even when nowehere near completion just doesn't make sense > > to me. Either way you have to continuously merge the main branch > >

Re: [osol-discuss] Re: Code Management System for OpenSolaris

2005-07-07 Thread Joerg Schilling
[EMAIL PROTECTED] wrote: > The fact that developers all write to the main repository for their > branches even when nowehere near completion just doesn't make sense > to me. Either way you have to continuously merge the main branch > with your own branch, so there's no gain to be had there. This

Re: [osol-discuss] Re: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005, [UTF-8] Jürgen Keil wrote: (bash) configure should detect SDL, like this: % bash configure --target-list=i386-softmmu --prefix=/tmp/qemu Install prefix/tmp/qemu BIOS directory/tmp/qemu/share/qemu binary directory /tmp/qemu/bin Manual directory /tmp/qemu/share/man E

[osol-discuss] Re: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Jürgen Keil
(bash) configure should detect SDL, like this: % bash configure --target-list=i386-softmmu --prefix=/tmp/qemu Install prefix/tmp/qemu BIOS directory/tmp/qemu/share/qemu binary directory /tmp/qemu/bin Manual directory /tmp/qemu/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Joerg Schilling
Shawn Walker <[EMAIL PROTECTED]> wrote: > > ftp://ftp.software.ibm.com/linux/pdfs/LinuxVersusSolarisAnalysis24Feb2005.pdf > > I think after making your rather flaming and wholly inaccurate comment > about the CDDL that hardly anyone can trust your assessment of "fair" > in regards to any compariso

Re: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005, Dennis Clarke wrote: martin on #blastwave on irc.freenode.net has patched a version of qemu so that it builds in /usr/sfw/bin/gcc i have built it my self.. works fine.. linux kernel 2.6.x use a 1000hz clock that expose defects in the qemu code on slower boxes, but haven't e

Re: [osol-discuss] Re: Fwd: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread James Dickens
On 7/7/05, Jürgen Keil <[EMAIL PROTECTED]> wrote: > martin  ... has patched a version of> qemu so that it builds in /usr/sfw/bin/gcc i have built it my self..Aren't you running qemu on Solaris SPARC?  On S10 SPARC there's no suchissue with a crashing qemu due to /usr/sfw/bin/gcc. This message poste

[osol-discuss] Re: Re: build always uses the gcc

2005-07-07 Thread Sunil
since I have a triple boot setup (XP,gentoo 2.6.9, opensolaris), I was very tempted to do performance comparisons. OS lagged behind gentoo by 7% in my encoding tests, but then my gentoo is super optimized and very light on services. I just wanted to build a non-debug OS to see how far OS can bea

Re: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005, [UTF-8] Jürgen Keil wrote: Apropos qemu, does it work for you on b16 or b17, x86 platform? [snip] when compiled with /opt/csw/gcc3/bin/gcc it starts, but does nothing. No windows opens, and after some 10-15 minutes of frenetic CPU usage (e.g. when booting Knoppix 3.9)

[osol-discuss] Re: Fwd: Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Jürgen Keil
> martin ... has patched a version of > qemu so that it builds in /usr/sfw/bin/gcc i have built it my self.. Aren't you running qemu on Solaris SPARC? On S10 SPARC there's no such issue with a crashing qemu due to /usr/sfw/bin/gcc. This message posted from opensolaris.org ___

Re: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Dennis Clarke
> martin on #blastwave on irc.freenode.net has patched a version of qemu so > that it builds in /usr/sfw/bin/gcc i have built it my self.. works fine.. > linux kernel 2.6.x use a 1000hz clock that expose defects in the qemu code > on slower boxes, but haven't experienced any crashes FYI : the p

Fwd: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread James Dickens
oops meant this to go to everyone -- Forwarded message --From: James Dickens <[EMAIL PROTECTED] >Date: Jul 7, 2005 9:35 AMSubject: Re: [osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)To: Jürgen Keil <[EMAIL PROTECTED]> On 7/7/05, Jürgen Keil <[EMAIL PROTECTED]> wrote: >> Apropos

[osol-discuss] Re: Qemu (was Re: Solaris vs. Linux)

2005-07-07 Thread Jürgen Keil
> > Apropos qemu, does it work for you on b16 or b17, x86 > platform? I have downloaded it, applied the patch as per > > http://blogs.sun.com/roller/page/thebentzone?entry=run_windows_or_linux_or > > (had to fix isgreater() macro in gnu-c99-math.h), but > have problems with it. If I compile it w

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

2005-07-07 Thread Casper . Dik
>Yes, in Solaris, Sun has stuck with good old Bourne Shell for the def= >ault root shell. For users, the shell is up to the administrator. T= >he bells and whistles you are talking about in Linux come from them u= >sing BASH (Bourne Again Shell) by default. As of Solaris 10 (or mayb= >e 9) BASH

Qemu (was Re: [osol-discuss] Solaris vs. Linux)

2005-07-07 Thread Dragan Cvetkovic
On Thu, 7 Jul 2005, Dennis Clarke wrote: [good stuff snipped] Personally I predict a "super-system" that is a bottom layer host for just about anything on top. Within 5 years. We currently see VMWare and Qemu and perhaps others that allow us to 'simulate' an x86 system on top of some other sy

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

2005-07-07 Thread Casper . Dik
>One technical difference is that cursor keys and command line editing and >completion generally wor ks out of the box in Linux and it generally doesn't in Solaris. I hope OpenSolaris will finally fix that usability issue so that it can lose that "80ies feeling" >and be more user friendly. > >C

Re: [osol-discuss] Re: A macsot for SchilliX

2005-07-07 Thread Dennis Clarke
On 7/7/05, Joerg Schilling <[EMAIL PROTECTED]> wrote: > Dennis Clarke <[EMAIL PROTECTED]> wrote: > > > Whatever it is .. it looks good. And he is a happy looking fellow isn't > > he? > > Should should have seen him at the time when there still was a dead penguin > behind him :-) > sigh .. wh

Re: [osol-discuss] Solaris vs. Linux

2005-07-07 Thread Dennis Clarke
On 7/7/05, Jim Grisanzio <[EMAIL PROTECTED]> wrote: > As this discussion gets going, I'd just like to chime in with this: many > of us here believe that both communities, both technologies, and both > licenses have great value and will thrive side by side well into the > future. Technical conversat

  1   2   >