[osol-discuss] PDU error in solaris
Hi, I am getting the following error in my messages file. Could you please provide any workaround for the same. Apr 12 00:46:33 sr1-ebiz1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] error while receiving a pdu from localhost.32809: Decode the header of the variables failed: asn length too long Thanks in advance Regards, Satya This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Marc Hamilton, Introduction
Marc Hamilton wrote On 04/10/07 06:16,: Hi, I wanted to introduce myself to the OpenSolaris community. Some of you might know me from my previous roles at Sun, or from my blog, but starting today I'll be leading up Sun's Solaris marketing efforts, including OpenSolaris marketing. The first thing I want to do is listen to the OpenSolaris community and understand what you want Sun to be doing better to support you. I've already had some good advice from my blog posting over the weekend including: - make sure you are telling non-Sun users about OpenSolaris - get more Sun engineers to speak on OpenSolaris at conferences, especially non-Sun oriented conferences like USENIX, LISA, etc. - clean up the branding, i.e. Solaris Express Community Edition, Solaris Express Developer Edition, OpenSolaris, Solaris 10, etc. While it is only my first day in the new job, I can already tell you there is a tremendous amount of executive attention at Sun focused on ensuring the OpenSolaris community is successful. Among many other things, one of my priorities is to ensure we bring our own Solaris 10 distribution closer to the OpenSolaris source base (there is a pretty big time lag right now). I'm really excited about my new job, hope to meet many more OpenSolaris community members, either virtually or in person, and look forward to the growing success of the community. BTW, here is my blog entry from June 14, 2005, the day we launched OpenSolaris. I guess I better get my team to start planning our two year anniversary. http://blogs.sun.com/marchamilton/entry/opensolaris_launch Welcome, Marc. Are we up for a big "Year 2" celebration? What do people think? Jim -- Jim Grisanzio http://blogs.sun.com/jimgris ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: [opensolaris-discuss] Upnp server to solaris
Hi i have try to build both too but i have faced problems meet requirements i have used only Sun Studio 11 compilers so far. i try to build again using gcc and other tools from /usr/sfw near days. This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: Driver for Marvel Youkon Gigabit Ethernet Adapter under SNV_59(64bit)
Sorry, something is wrong with URL. Google also found entry,but couldn't bring me to posting Please, check it one more time. Boris. This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Xorg blows up on SXCE B61
On Thu, 12 Apr 2007, Tom Haynes wrote: > I've seen the same problem with Firefox - just on one of my machines. The > other one is fine. I too have seen this problem, on my Ultra 20, with Firefox and acroread. Hopefully it'll be fixed soon! -- Rich Teer, SCSA, SCNA, SCSECA, OGB member CEO, My Online Home Inventory Voice: +1 (250) 979-1638 URLs: http://www.rite-group.com/rich http://www.myonlinehomeinventory.com ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Xorg blows up on SXCE B61
John Weekley wrote: I've run across what appears to be a bug with Xorg on SXCE B61. While installing Sun's web proxy 4.0.4, Xorg blew up, and kicked me out, requiring me to login again. I'd seen similar behavior with the bundled Firefox, but I was unable to reliably repeat it. I downloaded Mozilla.org's latest firefox build and the problem did not reappear with firefox. With the proxy server's java installer splash screen the failure is repeatable. B61 is installed on a Ferarri 3400, 768 MB RAM. Thanks, John ___ opensolaris-discuss mailing list [EMAIL PROTECTED] I've seen the same problem with Firefox - just on one of my machines. The other one is fine. ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Xorg blows up on SXCE B61
I've run across what appears to be a bug with Xorg on SXCE B61. While installing Sun's web proxy 4.0.4, Xorg blew up, and kicked me out, requiring me to login again. I'd seen similar behavior with the bundled Firefox, but I was unable to reliably repeat it. I downloaded Mozilla.org's latest firefox build and the problem did not reappear with firefox. With the proxy server's java installer splash screen the failure is repeatable. B61 is installed on a Ferarri 3400, 768 MB RAM. Thanks, John ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: Need help getting audio driver to work
Before you ( soi.e1 ) install the OSS audio drivers. if you have Solaris or OpenSolaris boot unix with the grub option of -rv behind it and then the /var/adm/messages file has a lot more detail of that the kernel.warnings it sees and attempt to use, this is also very good info to provide in the bug id/RFE along with running "prtconf -pv" and Also Linux run and save "lspci -vv -n nd" provide that as well. Here is my output from Solaris driver detection from the java 1.1 tool the page is located at URL of : http://www.sun.com/bigadmin/hcl/hcts/device_detect.html#use Solaris Driver 32-bit Solaris Driver 64-bit Device Type Vendor Device Name Driver Name No Solaris Driver No Solaris Driver Multimedia nVidia Corporation MCP51 High Definition Audio No Solaris Driver No Solaris Driver Multimedia Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder Solaris Express, Developer Edition 2/07 Solaris Express, Developer Edition 2/07 Firewire Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) hci1394 Solaris Express, Developer Edition 2/07 Solaris Express, Developer Edition 2/07 Video nVidia Corporation C51G [GeForce 6100] vgatext . . . One work of caution there are two variations of the device reports one for version of Developer Edition 2/07 and one for regular Solaris 10 11/06, so save both reports and include the differences and make a note if need be in your Bug-id/RFE report. if you still have your Windows partition intact try running, one thing nice about windows registry is gives a independent verification for the BUGID/RFE that is running on your PC to show HW device registers that are in use and known to windows. detail run and a start / run / cmd reg query hklm\system\currentcontrolset\enum\pci /s > c:\wreg.txt which is part of the Solaris driver detection page and include in the report bug id/RFE as well. One last thing, if you end up installing the oss audio drivers, liek I had indicated then run the above commands first as to keep the data imperical on your root image make a backup copy of your your /etc/path_to_inst and the /etc/devices_aliases file and then run a script command to save the pkgadd -d oss-verion.pkg output to get back to where you were, the pkgrm oss leaves drivers and entries behind when i have ran it in the past, so I had to reinstall everything to dupicate the issues when bug id do come around, to be fair it takes several months if there is demand fora fix, but it is well worth the wait, that is what make this OpenSolaris/Solaris so great! This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Need help getting audio driver to work
On 12/04/07, N. L. Barna <[EMAIL PROTECTED]> wrote: Hi friends, I just received and installed Solaris Express, Developer Edition, and I don't know what I'm doing. I'm on an x86 system and converted from XP. Everything seems fine except now I don't have sound. The sound card is a Sound Blaster Audigy 2. I found this site http://www.tools.de/opensource/solaris/audio/beta/ for a possible driver (likely audioemu in my case). It says I need to unpack and download the file with bunzip2, which I didn't think I had so I went to this site http://www.bzip.org/downloads.html and downloaded the source tarball. The problem is I don't know what I'm doing when I'm "extracting" these things. When I think I've extracted something, then there are all these files from which I don't comprehend and so don't know how to execute or install [i]the[/i] program. I'm probably lost due to my poor conditioning with automated installers. I deeply appreciate any help. I suggest using the OpenSound driver instead, not because the one you have won't work, but because the OpenSound driver has a better mixer, etc.: http://www.opensound.com/ Plus, the install is dead easy. It's free for personal use. As far as decompressing that file, you should be able to do something like: bzcat filename.tar.bz2 | tar -xf - -- "Less is only more where more is no good." --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Need help getting audio driver to work
Hi friends, I just received and installed Solaris Express, Developer Edition, and I don't know what I'm doing. I'm on an x86 system and converted from XP. Everything seems fine except now I don't have sound. The sound card is a Sound Blaster Audigy 2. I found this site http://www.tools.de/opensource/solaris/audio/beta/ for a possible driver (likely audioemu in my case). It says I need to unpack and download the file with bunzip2, which I didn't think I had so I went to this site http://www.bzip.org/downloads.html and downloaded the source tarball. The problem is I don't know what I'm doing when I'm "extracting" these things. When I think I've extracted something, then there are all these files from which I don't comprehend and so don't know how to execute or install [i]the[/i] program. I'm probably lost due to my poor conditioning with automated installers. I deeply appreciate any help. This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: Project Proposal: Tesla, Solaris Enhanced Power Management
Hi Richard, Sorry for the delay (vacation). Implementation of a suspend / resume mechanism wouldn't likely be a direct goal of this project, but when a suspend / resume becomes available, that mechanism could certainly be leveraged as part of this project's policy implementation. I do know that suspend / resume core support in Solaris is already being worked by a separate project. Thanks, -Eric This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: [opensolaris-discuss] Upnp server to solaris
On Wed, 11 Apr 2007, homerun wrote: Hi zfs makes solaris now good choise to store media content. could it be possible to get as part of "freeware" and integrated to /usr/sfw - tree some Upnp mediaserver. i have found two media servers that runs on linux - MediaTomb http://mediatomb.cc - GMediaServer http://www.gnu.org/software/gmediaserver From what I can see, there aren't any Solaris versions of MediaTomb or GMediaServer on any of the various Solaris freeware projects, so to maybe get the ball rolling I just did a cursory attempt. Unfortunately neither of them, nor libupnp-1.4.3 on which GMediaServer depends, compiled for me "out of the box". And I used gcc/g++ and a fairly GNU-friendly build environment too... Petri, anyone else -- want to help troubleshoot? Following is the build environment I use: http://www.genunix.org/wiki/index.php/Environment Eric ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: rbac
Any resolution on adding auth names that don't start with Solaris? I tried this Solaris 10 u 3 and it also won't recognize anything that doesn't start with Solaris. The man page explicitly says that you should use reverse DNS info to avoid naming collisions but that doesn't seem to work. This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] vncviewer snv60 x86
Not sure if it's related, but I was getting a similar-sounding error message trying to launch sunstudio on a fresh b59 install. I was able to get around it by starting up the X font server on the box, e.g.: svcadm enable x11/xfs xset +fp tcp/localhost:7100 -Matthew On 4/12/07, James Carlson <[EMAIL PROTECTED]> wrote: Marcin Woœô¡ºniak writes: > i have problem running this tool, i get warning > > Warning: Unable to load any usable ISO8859-1 font > Segmentation Fault (core dumped) > > vncviewer from blastwave.org and companion cd for solaris 10 u3 problem the same. > i guess maybe problem with xserver ? Yes. This is CR 6534687. It's pretty brutal, and seems to be a problem with the way fonts are searched. (Wildcards that are "too wild" find nothing, while restricted subsets find usable fonts.) It seems to be somewhat better in b61 and above; not sure what the real fix or bug is, though. -- James Carlson, Solaris Networking <[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 [EMAIL PROTECTED] -- Matthew R. Wilson http://www.mattwilson.org/ ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
I like it the way it is. I routinely deliberately install SUNWxcu4. I routinely deliberately use some of the xpg4 binaries. I share James Carlson's lack of understanding into the problem. But then I'm a native US English speaker and basically never have to deal with i18n except for message catalog coding. And I may not even be a typical Solaris/OpenSolaris "customer". How many people are having a problem with it as is? Please speak up. That is, whether you insist upon /usr/xpg4/bin ahead of /usr/bin in PATH by default. Let's not clutter up that point with the packaging or any other tangential matters. James Carlson wrote: I. Szczesniak writes: On 4/11/07, James Carlson <[EMAIL PROTECTED]> wrote: I'm confused. They *do* have the same level of support. Can you explain why you think they're supported differently? SUNWxcu4 is a separate package which is IMO wrong. The package should be merged into SUNWcsu In my opinion, it's right as it is. Not everyone requires XPG4. and system scripts should use /usr/xpg4/bin:/usr/bin as PATH, not /usr/bin. Why? They work fine without it. It would help if system scripts use /usr/xpg4/bin:/usr/bin as their default path. This would at least ensure that such scripts will work with multibyte locales. You can do that today. No, I cannot do that without modifying all script myself. You can do it with your own scripts. You have no reason (that I can see) to demand that others write their code to your restrictions. If you do have a reason, then please be specific about where the problem exists. Either file a bug, or run an ARC case to set a new policy. Now, what those scripts are doing with multibyte locales is a bit of a mystery to me. I had thought that was an issue for user processes, not system scripts. Ask yourself: What will happen if a system script encounters a file name with multibyte characters. Please be specific, and file a bug. What system script has that problem? If not, then just what are you asking for? To have /usr/bin change incompatibly? I don't think this will happen without a major shift to a more customer-friendly policy at Sun. We obviously have different notions of what "friendliness" entails. The inability to handle multibyte characters is very customer-unfriendly. In some countries like Taiwan it is considered a serious offense. The system is certainly able to handle multi-byte extensions without the changes you seem to be suggesting. It has been able to do so for quite some time. If not, please do file specific bugs outlining where the system fails to work properly. Claiming that it's offensive to Taiwan without providing specifics is just FUD -- totally unnecessary and unwelcome here. In other words, I just don't understand what you're asking for, or why. -- Jerry Sutton[EMAIL PROTECTED] ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
I. Szczesniak wrote: Ask yourself: What will happen if a system script encounters a file name with multibyte characters. Well, mostly they just work. Sometimes there are bugs, just as there are bugs when filenames have spaces in them. Do you have a specific example of a problem? - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
I. Szczesniak writes: > On 4/11/07, James Carlson <[EMAIL PROTECTED]> wrote: > > I'm confused. They *do* have the same level of support. Can you > > explain why you think they're supported differently? > > SUNWxcu4 is a separate package which is IMO wrong. The package should > be merged into SUNWcsu In my opinion, it's right as it is. Not everyone requires XPG4. > and system scripts should use > /usr/xpg4/bin:/usr/bin as PATH, not /usr/bin. Why? They work fine without it. > > > It would help if system scripts use /usr/xpg4/bin:/usr/bin as their > > > default path. This would at least ensure that such scripts will work > > > with multibyte locales. > > > > You can do that today. > > No, I cannot do that without modifying all script myself. You can do it with your own scripts. You have no reason (that I can see) to demand that others write their code to your restrictions. If you do have a reason, then please be specific about where the problem exists. Either file a bug, or run an ARC case to set a new policy. > > Now, what those scripts are doing with multibyte locales is a bit of a > > mystery to me. I had thought that was an issue for user processes, > > not system scripts. > > Ask yourself: What will happen if a system script encounters a file > name with multibyte characters. Please be specific, and file a bug. What system script has that problem? > > > > If not, then just what are you asking for? To have /usr/bin change > > > > incompatibly? > > > > > > I don't think this will happen without a major shift to a more > > > customer-friendly policy at Sun. > > > > We obviously have different notions of what "friendliness" entails. > > The inability to handle multibyte characters is very > customer-unfriendly. In some countries like Taiwan it is considered a > serious offense. The system is certainly able to handle multi-byte extensions without the changes you seem to be suggesting. It has been able to do so for quite some time. If not, please do file specific bugs outlining where the system fails to work properly. Claiming that it's offensive to Taiwan without providing specifics is just FUD -- totally unnecessary and unwelcome here. In other words, I just don't understand what you're asking for, or why. -- James Carlson, Solaris Networking <[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 [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
On 4/11/07, James Carlson <[EMAIL PROTECTED]> wrote: I. Szczesniak writes: > On 4/11/07, James Carlson <[EMAIL PROTECTED]> wrote: > > I. Szczesniak writes: > > > I explained this in another mail. Our statistics show that lots of > > > customers do not have SUNWxcu4 installed. The system scripts do not > > > require this package and customers tend to remove unused packages from > > > their systems. > > > > What would satisfy your complaint? > > Make sure that the tools in /usr/xpg4/bin are treated with the same > level of support as the tools in /usr/bin and merge the SUNWxcu4 > package into SUNWcsu. I'm confused. They *do* have the same level of support. Can you explain why you think they're supported differently? SUNWxcu4 is a separate package which is IMO wrong. The package should be merged into SUNWcsu and system scripts should use /usr/xpg4/bin:/usr/bin as PATH, not /usr/bin. > > We could make the system less configurable by forcing SUNWxcu4 into > > SUNWCmreq or by just removing SUNWxcu4 and putting the binaries into > > SUNWcsu. Would that help? > > It would help if system scripts use /usr/xpg4/bin:/usr/bin as their > default path. This would at least ensure that such scripts will work > with multibyte locales. You can do that today. No, I cannot do that without modifying all script myself. Now, what those scripts are doing with multibyte locales is a bit of a mystery to me. I had thought that was an issue for user processes, not system scripts. Ask yourself: What will happen if a system script encounters a file name with multibyte characters. > > If not, then just what are you asking for? To have /usr/bin change > > incompatibly? > > I don't think this will happen without a major shift to a more > customer-friendly policy at Sun. We obviously have different notions of what "friendliness" entails. The inability to handle multibyte characters is very customer-unfriendly. In some countries like Taiwan it is considered a serious offense. Irek ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
>Peter C. Norton wrote: >> On Wed, Apr 11, 2007 at 01:36:59PM -0500, Shawn Walker wrote: >>> On 11/04/07, I. Szczesniak <[EMAIL PROTECTED]> wrote: I don't think this will happen without a major shift to a more customer-friendly policy at Sun. >>> When is "break my customer's stuff" seen as friendly? >> >> Can you quantify: >> >> 1) How many of your customers things are going to break >> 2) What change will do the breaking > >What changes are you proposing? How can we know what will break >without a list of what you want changed? This whole conversation is a >lot of hand waving without any specific proposals. > >A lot of brain damage in /usr/bin utilities can be fixed without >breaking them - adding new flags that were never used before is >usually completely compatible, and trivial to do. Indeed; and one of the issues with how we did xpg4/xpg6 initially was that new flags/features were added only to the standard compliant variants. That was wrong and we are trying to rectify that (if we haven't already for the most part) There are some arcania which will cause breakage because of different behaviour, e.g., between /bin/sh and /bin/ksh. Without knowning what people do or run that is a difficult problem to phatom; you cannot, e.g., check this using interviews with customers. They will not be able to tell you. Tooling is needed, but we certainly should fix utilities to include features which would otherwise provoke syntax or usage errors. Casper ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
Peter C. Norton wrote: On Wed, Apr 11, 2007 at 01:36:59PM -0500, Shawn Walker wrote: On 11/04/07, I. Szczesniak <[EMAIL PROTECTED]> wrote: I don't think this will happen without a major shift to a more customer-friendly policy at Sun. When is "break my customer's stuff" seen as friendly? Can you quantify: 1) How many of your customers things are going to break 2) What change will do the breaking What changes are you proposing? How can we know what will break without a list of what you want changed? This whole conversation is a lot of hand waving without any specific proposals. A lot of brain damage in /usr/bin utilities can be fixed without breaking them - adding new flags that were never used before is usually completely compatible, and trivial to do. -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
On Wed, Apr 11, 2007 at 01:36:59PM -0500, Shawn Walker wrote: > On 11/04/07, I. Szczesniak <[EMAIL PROTECTED]> wrote: > >I don't think this will happen without a major shift to a more > >customer-friendly policy at Sun. > > When is "break my customer's stuff" seen as friendly? Can you quantify: 1) How many of your customers things are going to break 2) What change will do the breaking 3) How long it takes to fix Every time thiss stupid conversation comes up, it's all about hand-waving to explain why Solaris has to break. Please, hire a grad student specializing in HCI or usability and give them access to sun's customers and give us a write-up in a year about what the real costs vs. benefits are for these changes instead of this bogosity. Or, perhaps as I suggested in my last email, a SUNWunFkdusr package with a /usr that doesn't actually need /usr/xpg?/ to work decently, and then you can (horror of horrors) let your customers make a decision. -Peter -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Trouble booting foo1/unix
Frank Van Der Linden wrote: Manoj Joseph wrote: Hi, I compiled the on consolidation but am having trouble installing the kernel. I followed Rich Teer's article 'Building and Installing OpenSolaris'. http://www.opensolaris.org/os/community/tools/building_opensolaris I built the source and created the install tar using the glomname 'foo1'. I did this on a 64bit AMD machine. I then copied the tar file over to a vmware instance on my laptop (which is 32 bit intel), extracted the files and rebooted. But read of foo1/unix fails. I believe /platform/i86pc/foo1/unix is present in the ramdisk. -bash-3.00# bootadm list-archive | tail -2 boot/acpi/tables platform/i86pc/foo1 -bash-3.00# ls /platform/i86pc/foo1/unix -bash-3.00# reboot -- foo1/unix [reboot] Elf32 read error. panic: no entry point in foo1/unix Press any key to reboot What is the distribution/version of your installed system? You are probably running into what is described here: http://www.opensolaris.org/os/community/on/flag-days/pages/2007011901/ Upgrading kernels is somewhat less straightforward because of that flag day, but workarounds are described in that link. Thanks Frank, this seems to be it. I am on Solaris express CE build 54 and was building the bleeding edge source. The workaround didn't help much cause the grub that I have doesn't care much for the new entries. But I am now compiling build 54 + my stuff and this should do for me. Thanks! -Manoj ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] vncviewer snv60 x86
Marcin Woniak writes: > i have problem running this tool, i get warning > > Warning: Unable to load any usable ISO8859-1 font > Segmentation Fault (core dumped) > > vncviewer from blastwave.org and companion cd for solaris 10 u3 problem the > same. > i guess maybe problem with xserver ? Yes. This is CR 6534687. It's pretty brutal, and seems to be a problem with the way fonts are searched. (Wildcards that are "too wild" find nothing, while restricted subsets find usable fonts.) It seems to be somewhat better in b61 and above; not sure what the real fix or bug is, though. -- James Carlson, Solaris Networking <[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 [EMAIL PROTECTED]
Re: [osol-discuss] Trouble booting foo1/unix
Manoj Joseph wrote: Hi, I compiled the on consolidation but am having trouble installing the kernel. I followed Rich Teer's article 'Building and Installing OpenSolaris'. http://www.opensolaris.org/os/community/tools/building_opensolaris I built the source and created the install tar using the glomname 'foo1'. I did this on a 64bit AMD machine. I then copied the tar file over to a vmware instance on my laptop (which is 32 bit intel), extracted the files and rebooted. But read of foo1/unix fails. I believe /platform/i86pc/foo1/unix is present in the ramdisk. -bash-3.00# bootadm list-archive | tail -2 boot/acpi/tables platform/i86pc/foo1 -bash-3.00# ls /platform/i86pc/foo1/unix -bash-3.00# reboot -- foo1/unix [reboot] Elf32 read error. panic: no entry point in foo1/unix Press any key to reboot What is the distribution/version of your installed system? You are probably running into what is described here: http://www.opensolaris.org/os/community/on/flag-days/pages/2007011901/ Upgrading kernels is somewhat less straightforward because of that flag day, but workarounds are described in that link. - Frank ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] vncviewer snv60 x86
i have problem running this tool, i get warning Warning: Unable to load any usable ISO8859-1 font Segmentation Fault (core dumped) vncviewer from blastwave.org and companion cd for solaris 10 u3 problem the same. i guess maybe problem with xserver ? (gnome desktop) opensolaris snv60 x86 ibm thnkpa r51e thanks for any help This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Trouble booting foo1/unix
Hi, I compiled the on consolidation but am having trouble installing the kernel. I followed Rich Teer's article 'Building and Installing OpenSolaris'. http://www.opensolaris.org/os/community/tools/building_opensolaris I built the source and created the install tar using the glomname 'foo1'. I did this on a 64bit AMD machine. I then copied the tar file over to a vmware instance on my laptop (which is 32 bit intel), extracted the files and rebooted. But read of foo1/unix fails. I believe /platform/i86pc/foo1/unix is present in the ramdisk. -bash-3.00# bootadm list-archive | tail -2 boot/acpi/tables platform/i86pc/foo1 -bash-3.00# ls /platform/i86pc/foo1/unix -bash-3.00# reboot -- foo1/unix [reboot] Elf32 read error. panic: no entry point in foo1/unix Press any key to reboot I don't think compiling on x64 is the problem... I am not sure what I am missing. Can someone help? Regards, Manoj ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: How to color vim in OS
I have fixed the syntax colors with vim under screen! In the ~/.screenrc term xterm Now both vim and screen with colors :-) Thank you to all!! This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: How to color vim in OS
Hi Jedy, The output is: bash-3.00$ echo $TERM vt100 (under screen) Without screen: bash-3.00$ echo $TERM xterm In ~/.screenrc: term screen-256color Thanks! This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Re: How to color vim in OS
Hi Halton, Thank you very much for the resources file. I have downloaded latest version of vim from blastwave (http://www.blastwave.org) and I use gnome-terminal and / or xterm under JDS too. Not yet colors with your vimrc, but wait I'm trying more things :-) Cheers This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] How to color vim in OS
On Thu, 2007-04-12 at 02:14 -0700, Iban Nieto wrote: > Hi, > > I use a lots of time the terminal, command line tools, editors etc. I'm using > screen with ansi colors that works perfect. But when I ran vim (with syntax > on in ~/.vimrc) cannot view any colors, only black and white with some bold > texts... > > How to colorify vim in OpenSolaris?? Is a question for the console xterm / > dtterm ... ??? > > I have probe with different terminals with no colors yet :( What's the output of "echo $TERM"? Regards, Jedy Wang > > Cheers > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > [EMAIL PROTECTED] ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] How to color vim in OS
On Thu, 2007-04-12 at 02:14 -0700, Iban Nieto wrote:
> Hi,
>
> I use a lots of time the terminal, command line tools, editors etc. I'm using
> screen with ansi colors that works perfect. But when I ran vim (with syntax
> on in ~/.vimrc) cannot view any colors, only black and white with some bold
> texts...
>
> How to colorify vim in OpenSolaris?? Is a question for the console xterm /
> dtterm ... ???
My vim works fine with gnome-terminal and xterm under JDS. Do not know
where your vim comes from, there is no vim by default.
Attach my .vimrc maybe helpful.
Halton.
>
> I have probe with different terminals with no colors yet :(
>
> Cheers
>
>
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> [EMAIL PROTECTED]
" An example for a gvimrc file.
" The commands in this are executed when the GUI is started.
"
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
" Last change: 2001 Sep 02
"
" To use it, copy it to
" for Unix and OS/2: ~/.gvimrc
" for Amiga: s:.gvimrc
" for MS-DOS and Win32: $VIM\_gvimrc
" for OpenVMS: sys$login:.gvimrc
" Make external commands work through a pipe instead of a pseudo-tty
"set noguipty
" set the X11 font to use
" set guifont=-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso8859-1
set ch=2" Make command line two lines high
set mousehide " Hide the mouse when typing text
" Make shift-insert work like in Xterm
map
map!
" Only do this for Vim version 5.0 and later.
if version >= 500
" I like highlighting strings inside C comments
let c_comment_strings=1
" Switch on syntax highlighting if it wasn't on yet.
if !exists("syntax_on")
syntax on
endif
" Switch on search pattern highlighting.
set hlsearch
" For Win32 version, have "K" lookup the keyword in a help file
"if has("win32")
" let winhelpfile='windows.hlp'
" map K :execute "!start winhlp32 -k " . winhelpfile
"endif
" Set nice colors
" background for normal text is light grey
" Text below the last line is darker grey
" Cursor is green, Cyan when ":lmap" mappings are active
" Constants are not underlined but have a slightly lighter background
highlight Normal guibg=grey90
highlight Cursor guibg=Green guifg=NONE
highlight lCursor guibg=Cyan guifg=NONE
highlight NonText guibg=grey80
highlight Constant gui=NONE guibg=grey95
highlight Special gui=NONE guibg=grey95
endif
" I got this 'if' statement from (:help xterm-color) and it works,
" so I'm not going to complain.
"
if has("terminfo")
let &t_Co=8
let &t_Sf="\e[3%p1%dm"
let &t_Sb="\e[4%p1%dm"
else
let &t_Co=8
let &t_Sf="\e[3%dm"
let &t_Sb="\e[4%dm"
endif
autocmd BufReadPost * if line("'\"") && line("'\"") <= line("$") | exe "normal
`\"" | endif
___
opensolaris-discuss mailing list
[EMAIL PROTECTED]
[osol-discuss] How to color vim in OS
Hi, I use a lots of time the terminal, command line tools, editors etc. I'm using screen with ansi colors that works perfect. But when I ran vim (with syntax on in ~/.vimrc) cannot view any colors, only black and white with some bold texts... How to colorify vim in OpenSolaris?? Is a question for the console xterm / dtterm ... ??? I have probe with different terminals with no colors yet :( Cheers This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Monitor mode for Wireless devices in OS
Hi! Anyone known if the wireless driver (ipw, iwi or ath) supports "monitor" mode / inyection /sniffing features in order to capture IVs and cracking WEP wlans? I'm trying to modify and compile both aircrack and weplab security tools with no sucess yet... Thank you This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
[osol-discuss] Dangling /dev/rdsk entries remaining. Cleanup issue
HI, The device special files (/dev/rdsk/*) files are not gettling cleaned up properly thru "devfsadm -C" command after a lun has been made unvisible to the host. Basically, open to such stale entries fail. Is there any other way to cleanup these other than using "rm" command. Following is the sequence followed: . 1. Presented a RAID-0 EVA disk array lun to aSolaris 10 host 2. Executed "devfsadm -C" command in the Solaris 10 host. 3. Executed "format" command in the Solaris 10 host and created partition on the presented replica. 4. "ls /dev/rdsk/*s2" lists the replica cxtydzs2 entry in the Solaris 10 host. 5. Un-presented replica to the Solaris 10 host. 6. Executed "devfsadm -C" command in the Solaris 10 host several times with some delay in between. 7. "ls /dev/rdsk/*s2" still lists the un-presented replica cxtydzs2 entry in the Solaris 10 host. Regards Kiran This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] xpg/bin/tr unexpect output on Sparc?
Hi, On st, 2007-04-11 at 22:38, Peter Tribble wrote: > On 4/11/07, Bart Smaalders <[EMAIL PROTECTED]> wrote: > > Peter Tribble wrote: > > > I like the second idea - remove the package entirely and make sure > > > the files are always available under any conditions. > > > > > > (One could also ask why SUNWesu is a separate package.) > > > > > > > I was under the impression that many people found our package > > breakdown already too coarse. Is this not the case? > > No, we have far too many packages. The resulting level of choice > and subsequent diversity of configuration lead to chaos. > > Ultimately, the split into packages is done along boundaries that > aren't useful for users. > > Two contrasting examples: > > SUNWsmapi shouldn't exist as a package - it supplies one library > which is used by the format command. (And presumably other things, > but splitting a single library used by the format command into a separate > package just can't be right.) > Are you sure that nobody needs just that library and not binaries which depend on that library? > In snv_61, we get svn. In order for the svn client to work you need > to install the apache2 server. > OK, so svn client should go to apache2 package? And if somebody doesn't need svn client, but wants to have apache2? > The second case argues for more granularity, for sure - we just need > to do the other half of the problem and consolidate packages that don't > need to be split. > OK, you have some "needs". But there are also others. It is much simpler to install two packages then delete some files, or not? Actually, I think we have too big packages. Best regards, Milan ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
