Re: [osol-discuss] floppy driver problems, [was: b17 copying behaviour?]

2005-07-06 Thread Dragan Cvetkovic
On Tue, 5 Jul 2005, James Lick wrote: Dragan Cvetkovic wrote: dd: /dev/rdiskette: open: No such file or directory So, as far as Solaris is concerned, there is no floppy drive at all. It has worked fine before switching to new ACPI architecture. I see you've already fixed your problem,

Re: [osol-discuss] [New Community Proposal] - starting an OpenSolaris JDS Desktop Community

2005-07-06 Thread Joerg Schilling
Glynn Foster [EMAIL PROTECTED] wrote: Hey, I'd like to start the ball rolling in getting an OpenSolaris Desktop Community launched. Let's face it, there's an awful lot of FUD being spread around OpenSolaris not being ready for the desktop - it's time to prove them wrong ;) I'd

Re: [osol-discuss] [New Community Proposal] - starting an OpenSolaris JDS Desktop Community

2005-07-06 Thread Joerg Schilling
Stefan Teleman [EMAIL PROTECTED] wrote: how about a KDE community as well ? :-) lead-in: i am in the process of packaging and uploading KDE 3.4.1 for Solaris 10, both of x86 and SPARC, at KDE. finally. :-) i will post here when it's ready and sync'ed (very shortly). Solaris 10 is not

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

2005-07-06 Thread Joerg Schilling
Dana H. Myers [EMAIL PROTECTED] wrote: 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

[osol-discuss] Re: Feature request

2005-07-06 Thread Dana H. Myers
On my machine anyway, a single power button press induces shutdown. A triple press induces panic+crashdump. That's only if you've installed the experimental acpidrv (part of frkit) Dana This message posted from opensolaris.org ___

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

2005-07-06 Thread Dana H. Myers
Joerg Schilling wrote: Dana H. Myers [EMAIL PROTECTED] wrote: Jul 4 21:41:45 s11 acpica: [ID 972481 kern.warning] WARNING: AcpiOsWritePort: cf8 32 not permitted Jul 4 21:41:45 s11 acpica: [ID 815887 kern.notice] ACPI-0519: *** Error: Jul 4 21:41:45 s11 acpica: [ID 441208 kern.notice]

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

2005-07-06 Thread Joerg Schilling
Dana H. Myers [EMAIL PROTECTED] wrote: Have a look here: http://cvs.opensolaris.org/source/xref/usr/src/uts/i86pc/io/acpica/osl.c#570 What I'm contemplating is adding yet another acpi-user-options bit to disable access control for those willing to experiment with it. So you think of making

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

2005-07-06 Thread Dana H. Myers
Joerg Schilling wrote: Dana H. Myers [EMAIL PROTECTED] wrote: Have a look here: http://cvs.opensolaris.org/source/xref/usr/src/uts/i86pc/io/acpica/osl.c#570 What I'm contemplating is adding yet another acpi-user-options bit to disable access control for those willing to experiment with it.

Re: [osol-discuss] [New Community Proposal] - starting an OpenSolaris JDS Desktop Community

2005-07-06 Thread Alan Coopersmith
Joerg Schilling wrote: Stefan Teleman [EMAIL PROTECTED] wrote: how about a KDE community as well ? :-) lead-in: i am in the process of packaging and uploading KDE 3.4.1 for Solaris 10, both of x86 and SPARC, at KDE. finally. :-) i will post here when it's ready and sync'ed (very shortly).

Re: [osol-discuss] [New Community Proposal] - starting an OpenSolaris JDS Desktop Community

2005-07-06 Thread Alan Coopersmith
Joerg Schilling wrote: Glynn Foster [EMAIL PROTECTED] wrote: I'd like to lead a desktop community focused on JDS. There's absolutely no reason that others can't jump in with proposals to lead KDE, XFCE, or other variants - in fact, I'd totally encourage anyone to do so! I did see recently

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

2005-07-06 Thread Casper . Dik
Jul 2 11:10:09 s11 genunix: [ID 243001 kern.warning] WARNING: The binding file entry iprb 214 c onflicts with a previous entry on line 201 of /etc/name_to_major There's an issue here with corruption in the /etc/*_* files; /etc/name_to_major has duplicate entries and these are also not as they

Re: [osol-discuss] [New Community Proposal] - starting an OpenSolaris JDS Desktop Community

2005-07-06 Thread Joerg Schilling
Alan Coopersmith [EMAIL PROTECTED] wrote: Joerg Schilling wrote: Glynn Foster [EMAIL PROTECTED] wrote: I'd like to lead a desktop community focused on JDS. There's absolutely no reason that others can't jump in with proposals to lead KDE, XFCE, or other variants - in fact, I'd totally

[osol-discuss] Solaris vs. Linux

2005-07-06 Thread W. Wayne Liauh
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., inability to include

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

2005-07-06 Thread Cyril Plisko
Nikolay Molchanov wrote: I'd like to ask if there is a recommended Code Management System for OpenSolaris. Solaris is shipped with sccs (/usr/ccs/bin/sccs), and inside Sun all Solaris sources are under SCCS. We use Sun's CodeManager (also known as TeamWare) as primary Code Management System

Re: [osol-discuss] Solaris vs. Linux

2005-07-06 Thread Michael K Dolan Jr
I've read a pretty fair comparison of Linux 2.6 vs Solaris 10. I think I originally got it off LinuxToday.com but just did a search and found a link to it on IBM's site... It actually looks at everything from technical differences, legal/licensing, and ecosystems support. In the end it comes

Re: [osol-discuss] vt's

2005-07-06 Thread Shawn Walker
On 7/6/05, Sunil [EMAIL PROTECTED] wrote: What I miss the most (from Gentoo system) is the ability to have access to multiple vt's from console without having to login onto X. I know I can use screen but its not quite as convenient as the vt's since I can't really switch from X to console.

Re: [osol-discuss] Solaris vs. Linux

2005-07-06 Thread Shawn Walker
On 7/6/05, Chris Ricker [EMAIL PROTECTED] wrote: On Wed, 6 Jul 2005, Michael K Dolan Jr wrote: ftp://ftp.software.ibm.com/linux/pdfs/LinuxVersusSolarisAnalysis24Feb2005.pdf You might note who paid for that analysis. Like most such studies, it ends up supporting its sugar daddy -- no real

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

2005-07-06 Thread Nikolay Molchanov
I don't know if JDS sources have ever been under TW, or if JDS developers used to use TW, but now decided to use CVS (which sounds strange to me :-). Anyway, this is not a problem. We have created a TeamWare client for CVS. This tool allows to use CVS repository as a parent workspace, so each

[osol-discuss] [Fwd: Re: [solarisx86] talk]

2005-07-06 Thread Alan Coopersmith
From a coding standpoint, this might almost qualify for oss-bite-size, but since it changes the protocol and could involve bringing in new code from BSD, it would also seem a good simple case for getting an introduction to Sun's ARC and legal review processes. -alan- Original

Re: [osol-discuss] Solaris vs. Linux

2005-07-06 Thread Al Hopper
On Wed, 6 Jul 2005, Michael K Dolan Jr wrote: I've read a pretty fair comparison of Linux 2.6 vs Solaris 10. I think I originally got it off LinuxToday.com but just did a search and found a link to it on IBM's site... It actually looks at everything from technical differences,

Re: [osol-discuss] Solaris vs. Linux

2005-07-06 Thread Michael K Dolan Jr
Ok, ok, poor form.. Someone else answer the original question then - I retract mine.. Al Hopper wrote: On Wed, 6 Jul 2005, Michael K Dolan Jr wrote: I've read a pretty fair comparison of Linux 2.6 vs Solaris 10. I think I originally got it off LinuxToday.com but just did a

[osol-discuss] build always uses the gcc

2005-07-06 Thread Sunil
Why is the default build trying to use gcc? I am following the directions given in the dev. reference document. The only variable that affects the gcc usage is __GNUC which I have set promptly to '#' but no go. If I set CC=cc then it spews some cc warnings: - cd usr/src/uts

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

2005-07-06 Thread Sherry Moore
Hi Sunil, By default we always build both i386 and amd64. If you would like to build i386 only, you can modify the following files this way: --- usr/src/uts/i86pc/Makefile.i86pc --- Index: usr/src/uts/i86pc/Makefile.i86pc 28c28 # ident @(#)Makefile.i86pc 1.124 05/06/08