Re: [osol-discuss] Re: KDE 3.4.3 binary patch [CD/DVD authoring tools patch]
On 2/7/06, Arvinder <[EMAIL PROTECTED]> wrote: > Where are the patches uploaded. > I searched in sunfreeware and couldn't find them in the > /pub/sunfreeware/KDE/IA32AMD32/PATCHES.BINARIES folder. You can find them here: http://ftp.sayclub.com/pub/X/KDE/stable/3.4.3/SOLARIS/SUNSTUDIO10/IA32AMD32/PATCHES.BINARIES/ http://ftp.tiscali.nl/kde/stable/3.4.3/SOLARIS/SUNSTUDIO10/IA32AMD32/PATCHES.BINARIES/ --Stefan -- Stefan Teleman [EMAIL PROTECTED] ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: KDE 3.4.3 binary patch [CD/DVD authoring tools patch]
Where are the patches uploaded. I searched in sunfreeware and couldn't find them in the /pub/sunfreeware/KDE/IA32AMD32/PATCHES.BINARIES folder. -ad This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Proposal: ksh93 integration project
Hi! Here comes the requested (mini-) proposal to create a "ksh93 integration" project: The project should investigate and execute the integration of ksh93 and related features, including: - introduction of ksh93 (/usr/bin/nksh and /usr/bin/ksh93 were proposed in the private discussion) - introduction of libshell.so - investigate the migration of /usr/bin/ksh to ksh93 standard - discussion/bugfixing of Solaris-specific ksh93 bugs+fixes - enhancement of Solaris tools to use libshell instead of homegrown commandline parsers (like mdb, zfs, xauth etc.) - replacement of duplicate ksh versions in various Sun products with libshell.so (which is ksh93 as a shared library), including dbx and dtksh For now I only request a mailinglist for discussion and a project web page to track the status (nothing more!) since the current debate is done via private mail with a giant CC: list and much traffic - I think a mailinglist for such a discussion would be much much better (inclduing the detail that it would be archived) and would save us time, too. The proposed name for this mailinglist would be "[EMAIL PROTECTED]" and I volunteer to be the list admin. That's all for now. Comments/suggestion/etc. welcome... Bye, Roland P.S.: Please do not start a discussion/flamewar/etc. about the ksh93 integration here, please _wait_ until the matching mailinglist has been created (this is only the request to get the mailinglist) ... -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Community/Project Update: 2/6/06
In my report below, I forgot to list the "Packaging and Installation" community proposal. Apologies for that. Here it is: Packaging and Installation * Proposed 1/31 by Rob Anderson * Community consensus: yes * CAB vote: no ± vote yet * Opening date: currently not scheduled Also, there seems to be some confusion between the "Packaging and Installation" proposal and the "Packaged Software" proposal. Perhaps that could be clarified. Jim Jim Grisanzio wrote: Here's an update on community and project proposals. Jim --- Jim Grisanzio, Community Manager, OpenSolaris http://blogs.sun.com/jimgris/ *COMMUNITY PROPOSALS* Immigrants Community * Proposed 10/27/05 by Adam Leventhal * Community consensus: yes * CAB vote: approved * Opening date: TBD CIFS Community * Proposed 1/11/06 by Mark Sweeney * Community consensus: no consensus yet * CAB vote: no ± vote yet * Opening date: currently not scheduled Games community * Proposed 1/15/06 by Brendan Gregg * Community consensus: yes * CAB vote: approved * Opening date: proposed for this week Name Services Community * Proposed 1/20/06 by Anup Sekhar * Community consensus: yes * CAB vote: no ± vote yet * Opening date: currently not scheduled Packaged Software * Proposed 2/1/06 by Keith Wesolowski * Community consensus: no consensus yet * CAB vote: no ± vote yet * Opening date: currently not scheduled *PROJECT PROPOSALS* Network-SIP * Proposed 1/6/06 by Venugopal Iyer * Project motion seconded: yes * Opened 2/3/06 Visual Panels project * Proposed 1/18/06 by David Powell * Project motion seconded: yes * Opened 2/6/06 (/usr/)sfw Nevada * Proposed 2/1/06 by Keith Wesolowski * Project motion seconded: yes * Opening date: TBD ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Please update 4113420 (request for ksh93 integration)
On 1/10/06, Richard Lowe <[EMAIL PROTECTED]> wrote:
> Felix Schulte wrote:
>
> [snip]
>
> > And you do not have to "think through" - somewhere one or more of your
> > engineers have Roland Mainz's ksh88-to-ksh93 migration plan which is
> > pretty much straightforward and handled most of the issues.
>
> However, the rest of us on this alias don't. Perhaps you could post it
> here so we can all see it?
Here it is:
-- Forwarded message --
From: Roland Mainz <[EMAIL PROTECTED]>
Date: Feb 3, 2006 7:28 AM
Subject: Re: ksh88->ksh93 migration plan
To: Mike Kupfer <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], David Korn <[EMAIL PROTECTED]>,
[EMAIL PROTECTED], Joerg Schilling <[EMAIL PROTECTED]>,
"I. Szczesniak" <[EMAIL PROTECTED]>, Jim Grisanzio
<[EMAIL PROTECTED]>, Alan Coopersmith
<[EMAIL PROTECTED]>, Rich Teer <[EMAIL PROTECTED]>
Mike Kupfer wrote:
> Hi Roland, Felix Schulte mentioned recently that you had written up a
> plan for how Solaris could migrate from ksh88 to ksh93. I would like to
> take a look at it, as would the Sun engineer who is currently planning
> on doing ksh work, but we don't know where to get a copy of it.
Actually the migration itself is quite easy - but only if you see it
from the technical viewpoint... I did some reading through the
OpenSolaris mailing lists, talked to a couple of Sun people and Felix
this week and it seems that this issue is primarily a political (e.g.
Sun's policy of handling backwards compatibility) and "religions" one
(bourne shell vs. current Solaris ksh vs. ksh88 vs. ksh93 vs. bash vs.
"never touch a running system").
And I fear that nothing has changed in Sun's position about getting
/usr/bin/ksh updated to ksh93 status - it seems to be impossible like it
was impossible (to even think about (slaughtering the holy cow called
"backwards-compatibillty-must-never-ever-be-broken")) in the 2001/2002
time frame.
Anyway... I've cut the original plan (which was written for Solaris 8)
down to the main items (for two reasons: 1. the exact details need to be
reinvestigated for Solaris 10 and 2. I do not have much faith that Sun
will ever be willing to do the full migration (which means: Getting
/usr/bin/ksh updated to ksh93)):
* The plan now looks like this:
-- snip --
- Move current /usr/bin/ksh to /usr/bin/oksh (now called "old" korn
shell)
- Edit all existing scripts in the Solaris code base which use
/usr/bin/ksh to use /usr/bin/oksh instead until they have been tested
with ksh93.
A test in 2001 revealed that from 598 ksh scripts in a Solaris 8
installation 29 needed changes (unfortunately very prominent stuff like
"patchadd" / "patchrm" are on that list... ;-/ ) - that's AFAIK less
than 5%... :-)
And the changes required were usually minor AND made the scripts
"portable", e.g. they were able to run both with Solaris ksh and
ksh93...
- Put ksh93 into /usr/bin/nksh ("new" korn shell. ksh93 MUST NOT be
placed to /usr/bin/ksh93 - arguments can be listed here but that is
AFAIK outside the scope of this mail))
An alternative may be to just stuff ksh93 to /usr/xpg4/bin/sh (instead
of creating /usr/bin/nksh (on the other side the creation of
/usr/bin/nksh may be better... it indicates that there is a "new" korn
shell... :-) ))
- /usr/bin/ksh then gets a link (hard-/softlink - whatever you prefer)
to the following positions:
Solaris 9: /usr/bin/ksh --> /usr/bin/oksh
Solaris 10: /usr/bin/ksh --> /usr/bin/oksh
OpenSolaris: /usr/bin/ksh --> /usr/bin/nksh
Solaris 11: /usr/bin/ksh --> /usr/bin/nksh
- /etc/shells, the defaults for getusershell(3C) and the matching manual
pages needs to be adjusted
- libshell.so.1 needs to be introduced (both 32bit and 64bit versions)
- libc's wordexp(3) needs to be adjusted to use /usr/bin/oksh for now
(ignoring the fact that it is a horrible hack to abuse ksh (any version)
for such a purpose - but fixing that is IMO beyond the scope of this
project)
- /usr/xpg4/bin/sh can simply link to /usr/bin/nksh (except for the
wordexp(3) hack)
- Document /usr/bin/oksh as being depreciated, stop working on it and
let it silently die (and do not forget to move it into a seperate
package that people do not have to install it anymore unless it is
really required) ... :-)
* Note: I am listing Solaris 9/10 here too because products such as
"dbx" could be much simplified - instead of using their own
(unmaintained ?!) copy of ksh it would simply use libshell.so. Same
applies to "mdb" and the new **adm" tools which are very limited due
lack of expression&&error handling. Unfortunately this may require to
backport "nksh" and libshell.so to older releases to support the tools
depending on the new features (and that's the reason why I invented the
"oksh" and "nksh" naming scheme).
* Known problems/issues/questions:
- How should the old "rksh" and the old profile shells be named ?
Possible solution may be to stuff a "o" in front of the old ones and a
"n" in front of the new ones...
- Scripts need to be developed (u
[osol-discuss] share firewire storage between 2 sun blades
I am able to connect a Maxtor OneTouch 250gb firewire drive to a SunBlade 100 running Solaris 10. It is discovered and I can configure it with rmformat. The problem comes in when I want to attache it to a second sun blade at the same time. The drive is recognized but not configurable i.e. rmformat does not se it. I have seen that it is possible to do this in linux by downloading and installing oracle supplied packages. Is there any way to do this in solaris other that NFS mounts or iscsi. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Community Forum Proposal: Packaging, Patching, and Distribution Mgmt
Albert White wrote: Anyway, +1 from me, Me too. +1 Eric ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Multi-Homing...Is there any limitation on the number of Logical Units
Hello; Wouldn't the transverse of the routing and/or IP filter tables be a good cause not to do such things? Warmest Regards Steven Sim James Carlson wrote: Octave Orgeron writes: I've used ndd to increase the default to support 1000 vip's before and have not noticed any performance issues. And you shouldn't -- unless you have applications that are affected by high numbers of interfaces. So it won't hurt your server. "Maybe." The kernel and usual sorts of applications work just fine like this. It really just comes down to the application that will use the NIC. If it can co-exist with other apps on the same NIC and not cause any bottlenecks, you shouldn't have any issues. That's not the problem. There are some applications that use SIOCGLIFCONF and/or routing sockets to keep track of the interfaces on the system. These applications often build internal lists of interfaces for their own purposes. Unfortunately, some of those applications have O(N^2) or worse algorithms that iterate over those lists. If you have dozens or hundreds of interfaces, that's probably not a problem. If you have many thousands, you can shoot yourself in the foot. (I don't think this is really a _good_ reason for the hard-coded 8192 limit. It's the only reason I know, though.) Fujitsu Asia Pte. Ltd. _ This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Community Forum Proposal: Packaging, Patching, and Distribution Mgmt
> I imagine it's implicit in my being listed as a > community lead ;-), but > I do give this a +1. I dont see a post from Rob yet, does that imply that the other community lead doesnt give it a +1 ;-) Anyway, +1 from me, Cheers, ~Al -- Albert White, Patch System Test This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Multi-Homing...Is there any limitation on the number of Logical Units
Octave Orgeron writes: > I've used ndd to increase the default to support 1000 vip's before and > have not noticed any performance issues. And you shouldn't -- unless you have applications that are affected by high numbers of interfaces. > So it won't hurt your server. "Maybe." The kernel and usual sorts of applications work just fine like this. > It really just comes down to the application that will use the NIC. If > it can co-exist with other apps on the same NIC and not cause any > bottlenecks, you shouldn't have any issues. That's not the problem. There are some applications that use SIOCGLIFCONF and/or routing sockets to keep track of the interfaces on the system. These applications often build internal lists of interfaces for their own purposes. Unfortunately, some of those applications have O(N^2) or worse algorithms that iterate over those lists. If you have dozens or hundreds of interfaces, that's probably not a problem. If you have many thousands, you can shoot yourself in the foot. (I don't think this is really a _good_ reason for the hard-coded 8192 limit. It's the only reason I know, though.) -- James Carlson, KISS Network<[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Multi-Homing...Is there any limitation on the number of Logical Units
I've used ndd to increase the default to support 1000 vip's before and have not noticed any performance issues. So it won't hurt your server. It really just comes down to the application that will use the NIC. If it can co-exist with other apps on the same NIC and not cause any bottlenecks, you shouldn't have any issues. Octave --- James Carlson <[EMAIL PROTECTED]> wrote: > vijayanand writes: > > Can anyone let me know whether there is any limitaion on the number > > of Logical Units/Ip address that can be association with a single > > network physical interface. > > Yes. The limit is set by the ip_addrs_per_if ndd variable. The > default limit is 256, but can be increased to 8192: > > ndd -set /dev/ip ip_addrs_per_if 8192 > > This variable has a bit of an odd history. The kernel uses AVL trees > for interfaces, and so should scale fairly nicely with huge numbers > of > interfaces. I believe the limit is there mostly to protect > _application_ programs, many[1] of which will perform atrociously or > just fall over dead with an excessive number of interfaces. > > [1] No list here ... "you know who you are." ;-} > > -- > James Carlson, KISS Network > <[EMAIL PROTECTED]> > Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 > 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 > 1677 > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Systems Engineer http://www.opensolaris.org/os/community/sysadmin/ http://unixconsole.blogspot.com [EMAIL PROTECTED] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Spanish Translation Review: Teer2
Nacho, Here's a few more nits. Rick Usando BFU para instalar ON El parrafo que comienza con " Cuando el proceso de BFU termina (que ...) --> Añadale un "algo" delante de la "que" o comienza solo con "tarda." Segunda linea --> no entiendo esta parte: "no sean compatibles con que viejo kernel que esta en uso. " Tercera linea "(Los errores acerca del acceso a...)" --> deberia ser "(los errores)" Ultima linea: "No deberían usarse init o shutdown para rearrancar el sistema después de un proceso de BFU, debería usar el comando reboot." --> Podria ser: "No uses init o shutdown para rearrancar el sistema despues de un proceso de BFU; en ves, usa el comando reboot." Resolución de conflictos Segundo parrafo: "una copia del anterior de guarda en /bfu.child..." --> "se guarda" Ultima linea: "A los archivos dentro de este directorio se los conoce como hijo , padre " --> "se les conoce como hijo, padre..." ^^^ ^^^ El parrafo con la "bulleted list" --> Añadale un ":" a la palabra "reglas." --> Añadale un period a cada linea. Ignacio Marambio Catán wrote: On 2/6/06, Rick Ramsey <[EMAIL PROTECTED]> wrote: Jim, Nacho, The translation is excelente! :-) Coupla nits: Flag Days "Un Flag Day ocurre cuando uno o mas paquees del sistema." --> Deberia decir "paquetes del sistema" --> El parafo necessita un punto final. Introduccion a BFU El proceso con el cual instalamos ... --> falta la parentesis primera Segunda linea: "(y esa es lo que causa ...)" --> no deberia decir, "(y eso es lo que causa...)" Segunda linea: "estos archivos se crean como parte del proceso nightly de" --> puedes reemplazar "nightly" con "nocturno" o "que se repite cada noche." Ultimo parafo: "bfu es quiza lo mejor" --> deberia decir "bfu es quizas lo mejor." I have to prep for a meeting so I'll try to look over the rest later. Rick the proposed changes are mostly ok, except for the one about nightly, I explicitly used it because the actual script is called nightly, try to change that and you'll notice that the sentence would not make much sence unless you know that "nightly" is english for "nocturno"; in fact I thought about not translating for example the tags in the paragraph about the rules followed by BFU but I decided I would leave the translations and add the real tags in english between parenthesis; we could do the same if you think people will understand it. should I make the changes and resend it? (I'm guessing I don't have enough privileges to modify the draft in the page directly being an observer of the project) Thanks for the corrections nacho ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: solaris just stoped
no i dont have a USB cdrom but when it stoped i cant even restart it or do anything the only solution is to unplug the power i dont think this is the best solution This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Couldn't access /dev/ip with ndd -get /dev/ip \?
vijayanand writes: > I am able to see /dev/ip in my solaris box. But i'm having problem with the > following command, What version of Solaris? > $ ndd -get /dev/ip \? > open of /dev/ip failed: Permission denied That's normal. > When I was searching for a solution in internet, I found the following > workaround > > - replace the following line in /etc/security/device_policy : That file is new in Solaris 10. If you don't have it, then I'd suspect you aren't running Solaris 10. I also don't think that changing this entry (if you had it) would be wise. > But unfortunately I couldn't find the file 'device_policy' under > /etc/security. I'm a beginner and struggling to find a solution for this. You need to have sufficient privileges to open /dev/ip. One simple way to solve the problem is to become root -- su or sudo. A more robust but harder way to do it is to give 'ndd' the right privileges in /etc/security/exec_attr and then assign yourself to a profile that has the right authorization and use pfexec or one of the profile shells. You can read more about this in rbac(5). -- James Carlson, KISS Network<[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: solaris just stoped
I've been having a similar problem on my build 28 Tecra M2 laptop. However, I only have this problem when my external USB drive is plugged in and mostly occurs when it is getting hammered. Would that happen to be a USB CD drive you have? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: solaris just stoped
I had a similar problem with an Athlon no name computer running Solaris. When I upgraded to a newer Solaris version I was told by the install software that a firmware patch for the BIOS was needed. After installing the new BIOS version the problem vanished. -- Guenter This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: integrating star was: Incorporating open-source
Mike Kupfer <[EMAIL PROTECTED]> wrote: > But thanks for the ping. > > star/rmt is currently 7th on my To Do list. (Not a great answer, but > some of the things above it should be quick.) Mmm, then it depends on how long you spend on one topic of the todo list. Note that rmt integration also means deciding on what security policy /etc/default/rmt should use and to modify ufsdump/ufsrestore in order to make them work together with the librmt that uses an interface with minor differences to the one currently used. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] solaris just stoped
hi, i was copying a file from a CD and suddenly it stoped and i couldnt do anything not even to open a terminal or shutdown the system in a proper way so in this case what should i do..i mean do i have to unplug the power! Thanks This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: how much should be the space for root....
Solaris 10 and later on a 9G drive is going to be tight, especially if you want to put any additional software or your own data on the machine. It's best - by far - to keep things simple and just have a small swap area and large root. I would probably split it 7:2 or something like that. (You really do want to keep it simple. If you split it up any further then you're pretty much guaranteed to have one partition full and orphaned space somewhere else, especially on such a small drive.) -Peter Tribble L.I.S., University of Hertfordshire - http://www.herts.ac.uk/ http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
