Re: [osol-discuss] [ogb-discuss] Scheduled Tasks
This doesn't sound like a governance issue; redirecting to opensolaris-discuss. Marco Reyes Rasse wrote: Hello, my name is Marco Reyes from Chile, i new in this mailing list, i need help with one Scheduled Tasks for OpenSolaris and SunSolaris, and i have make one script to check if one folder of server is empty or not, this task should be executed at certain times of day. You can run scheduled tasks using cron. See the crontab(1M) man page. For example, this entry will make the /export/myscript program run once a day at 8AM local time: 0 8 * * * /export/myscript As for checking whether a directory is empty, it depends on the shell you're using, but one way to check emptiness is with Perl: perl -e 'opendir D, $ARGV[0]; $i++ while (readdir D); print $i\n;' \ directoryname That'll print 2 or less if the directory is empty. -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] failure upgrading from snv_131 to snv_134
On 3/14/2010 3:56 AM, Alan Coopersmith wrote: James Carlson wrote: How is it that a bug fixed back in build 127 didn't affect me in build 131 but started affecting me in build 134 ... ? The great renaming brought it back to life in 133: http://defect.opensolaris.org/bz/show_bug.cgi?id=14906 OK; that explains it. Thanks! Even with poring over the release announcements, it seems to be hard to keep up with the bumps. I hope it gets smoother soon. -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] failure upgrading from snv_131 to snv_134
I just attempted to upgrade my OpenSolaris build 131 AMD64 system to build 134, and failed miserably. Here's what happened: First, since this step is normally required, I tried to do pkg install SUNWipkg. That didn't work. It failed (after downloading well over 1GB) telling me that I had to use an alternate boot environment due to the nature of the update. I tried doing pkg image-update, and that failed, telling me that I had to install a new SUNWipkg first. That was a bit expected, though obviously not possible. I next did (as root; I'm still old school in some respects): beadm create opensolaris-8 beadm mount opensolaris-8 /mnt/tmp pkg -R /mnt/tmp install SUNWipkg That more or less worked, with a lot of errors about trouble installing (clone) drivers -- something that's apparently a known problem and can be safely ignored. No other errors were seen. I next did: beadm unmount opensolaris-8 beadm activate opensolaris-8 reboot That was a bad idea. This is a picture of the screen that greeted me after a fast reboot: http://www.workingcode.com/p1030100.jpg I rebooted a couple more times, hoping that a slow reboot would get it. No dice. It wouldn't boot. And OpenSolaris has no failsafe option, so I didn't know what to do. I ended up going back to the previous (build 131) BE. That's where I'm stuck now. I googled the messages, and come up with a few postings by other folks who'd seen this problem, but all were old (build 128 or older) and didn't seem to address this scenario. Is this a known problem? Did I do something wrong during the upgrade? What should I have done to recover? Should I file a bug? If so, what sort of information would be helpful in diagnosing the failure? -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] failure upgrading from snv_131 to snv_134
On 03/13/10 18:44, Shawn Walker wrote: On 03/13/10 03:10 PM, James Carlson wrote: I just attempted to upgrade my OpenSolaris build 131 AMD64 system to build 134, and failed miserably. Here's what happened: First, since this step is normally required, I tried to do pkg install SUNWipkg. That didn't work. It failed (after downloading well over 1GB) telling me that I had to use an alternate boot environment due to the nature of the update. Do you have packages from /contrib installed? If so, they have incorrect dependencies which caused the solver to incorrectly attempt to upgrade you to a new build. The solver in b134+ doesn't allow that. The solution is to remove /contrib (or /pending) packages and try again. Hmm. I'd removed those once before. I thought the problem was fixed. Thanks; I'll have to remember that one for next time. It's a bit of a hurdle. I tried doing pkg image-update, and that failed, telling me that I had to install a new SUNWipkg first. That was a bit expected, though obviously not possible. Use the -f option to ignore the SUNWipkg version check (which is probably wrong anyway due to the packages above). OK. I next did (as root; I'm still old school in some respects): beadm create opensolaris-8 beadm mount opensolaris-8 /mnt/tmp pkg -R /mnt/tmp install SUNWipkg Err...not quite right. See FAQ B1: http://hub.opensolaris.org/bin/view/Project+pkg/FAQ That link just hangs. I guess I'll read it another day. I was able to get to 134 by using bootadm update-archive but it looks like I'm going back to 131, because there's a lot that just plain doesn't work right in 134. In particular, less and telnet seem to be terribly broken -- both just appear to hang unless I press ^J. I expect it's some sort of problem in the GNOME terminal emulator. Too bad. I liked the new log-in screen, and GNOME itself seemed *much* snappier once I was logged in. But I can't stand having the system be unusable for long periods of time or having basic things not work at all. -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] failure upgrading from snv_131 to snv_134
On 03/13/10 22:44, Alan Coopersmith wrote: James Carlson wrote: I was able to get to 134 by using bootadm update-archive but it looks like I'm going back to 131, because there's a lot that just plain doesn't work right in 134. In particular, less and telnet seem to be terribly broken -- both just appear to hang unless I press ^J. I expect it's some sort of problem in the GNOME terminal emulator. Sounds a lot like the ptmx permissions bug in the release notes actually, which is fixable with a simple chmod. Really? The comments in that bug (particularly #26) seem to state that this was fixed in build 127. That was long ago. I was running build 131 and I tried to upgrade to build 134. How is it that a bug fixed back in build 127 didn't affect me in build 131 but started affecting me in build 134 ... ? I'll give it another try, but I'm skeptical, to say the least. Is it really fixed as the many comments in that bug seem to say? -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [networking-discuss] link aggregating
Arun Tomar wrote: I've a zfs box for storage and gigabit network. the max data transfer speed that i could get is may be between 100-125 mbps need to check that. Is that MBps (megabytes per second) or Mbps (megabits per second)? The former sounds about right. I wanted to achieve close to 300mbps of data transfer speed. I remembered that if i could use link aggregation, it improves reliability and performance. In general, true. so my question is if supposed with 1 lan card if my transfer speed is 100 mbps, then if i aggregate the links (2 gigabit lan cards aggregated) then would it double to 200 mbps? Not necessarily. If you don't have a bottleneck elsewhere (meaning that your CPU, disks, and other parts of your system can deliver that kind of performance), and if you have enough distinct flows to hash out over the available interfaces, then, yes, it'll scale in that way. -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Permission/Misc Questions
The Big T writes: 1) I installed the latest build off the site, yet did not notice a x64 build... Was just curiouse if there is a 64bit build available. It's all the same. If you have 64-bit system, then it runs 64-bit by default. If you don't, then it runs 32-bit. There's no separate build necessary. Now the biggest question that I have is about the permissions on the CIFS share I dont have much experiance with the Solaris/Unix permission types and havent been able to get the information that i need from google or the zfs/acl docs on the site over the past two days. SO hopefully someone here can help me out. You might get help here, but zfs-disc...@opensolaris.org or cifs-disc...@opensolaris.org might be better paths to the experts. 3) My last question is whats the best way to remote (i'm looking for something like Remote Desktop) into my OpenSolaris box from a windows/linux machine? Right now im using VPN through the gnome daemon though I would like something that does not require the user to be logged in locally on the server. I'd use ssh with the automatic X11 redirection, but there's also VNC for those who like such things. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Have read-only mount option for /usr
Ian Collins writes: Should work fine. Actually you can even do it via jumpstart profile (no finish script required): pool rpool auto 8192 8192 mirror c0t0d0s0 c0t1d0s0 bootenv installbe bename sol10_u7 dataset /var There has always been an option to split /var. /usr is a different story. lucreate(1M) includes this example: The following command, like the preceding, creates a new boot environment on a machine on which a BE has never been created. However, the following command differs in two respects: the -c option is omitted and the /usr file system is mounted on its own disk slice, separate from /. # lucreate -m /:/dev/dsk/c0t4d0s0:ufs -m /usr:/dev/dsk/c0t4d0s1:ufs \ -n second_disk lucreate: Please wait while your system configuration is determined. many lines of output lucreate: Creation of Boot Environment c0t4d0s0 successful. And filesystem(5) says this: /usr Mount point for the /usr file system. See description of /usr file system, below. And the jumpstart guide has this: http://docs.sun.com/app/docs/doc/820-0179/6nbugkoo4?a=view#frcfq I'm pretty sure that (at least apart from OpenSolaris IPS), using a split root/usr layout has been supported. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Have read-only mount option for /usr
Ian Collins writes: # lucreate -m /:/dev/dsk/c0t4d0s0:ufs -m /usr:/dev/dsk/c0t4d0s1:ufs \ -n second_disk That's with UFS root (I've used this a few times), how about ZFS root? Ah; I knew I had to be missing something there, because the answer was too easy. No, not with ZFS root. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Huawei E220 hot plugging and USB serial freesing problem drivers for snv111
Lei Chen writes: Yes, I have some discussion with Chototsu. And I will contact submitter of CR6840063 for further help. This CR is the first one with a coredump. And thank you for the hint of STREAM analysis. Once the root cause is known, I will putback my fix. OK; not trying to rush it. I'm just making sure all of you folks are talking. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Possible ZFS corruption?
Joel Robison writes: ::stack mutex_enter+0xb() metaslab_free+0x68() zio_dva_free+0x1f() zio_execute+0x60() zio_nowait+9() Looks a lot like CR 6794136, which was fixed in build 115. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] random OpenSolaris complaints [was Re: StudioExpress-sol-x86-2009-03-pkg.sh installer woes]
Anon Y Mous writes: When are we going to get an OpenSolaris server core that is command line and text only with no X-windows dependencies? The answer depends on when people decide to stop complaining about missing features in the work-in-progress that is the OpenSolaris distribution, and instead start working on providing those features. Seriously: I'm not on the Indiana team, but, as someone who has talked with those folks, I know that they're keenly aware of these shortcomings. The work is not done. It's not finished yet. You're looking at a work in progress. There are known feature gaps -- among them are many enterprise-class features. They're not being forgotten. The issues won't be ignored. The people doing this work just aren't that foolish. It takes time to do work. It takes more time if you have to run through a gauntlet of people throwing stones. I'm almost hoping we can get back to arguing about GPLv3 or Sun's buy-out. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] SUNWglrt prerequisite
John DeHart writes: forgive my ignorance but, what does 'encumbered' mean relative to the OpenGL package? Nobody who knows can give you the specifics, but encumbered generally means that there are legal restrictions on how the code must be handled. Some aspect of it (or of the documentation used to produce it) are controlled by an entity outside of Sun. There are a few things we have that are encumbered in one way or another. In some cases, we can freely share the binaries, but not the source. In others, the binaries must be individually licensed. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Huawei E220 hot plugging and USB serial freesing problem drivers for snv111
Georg-W. Koltermann writes: From Kazuhiko Kobayashi chototsu_moush...@yahoo.co.jp: USB serial freesing problem(Bug ID 6719062) patch and binary for snv111 http://chototsumoushinp.dip.jp/solaris/usbser.snv111.t ar.bz2 [...] chototsu you rock!! I'm online from OpenSolaris 2009.6 (snv111b) with your binary patch, using a Nokia N95 mobile phone! How long have I waited for this day! Hello Sun, if you are listening, could you _please_ consider this patch? It makes it possible for me to use OpenSolaris at home, without it I'm stuck with Linux :-((( Can you really be answerable to that ;-) ? It's wonderful to see this ... folks have been mis-attributing the problem to PPP for a while now, and it's good news that the root cause in USB has been found. The RE on that bug is Raymond Chen. I've copied him on this reply, and I'd hope that he'd follow up with the original poster. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Few questions w.r.t. OS 2009.06 ZFS mirroring and installation.
Karel Gardas writes: Hello, I do have few questions w.r.t. OS 2009.06 ZFS mirroring and installation: 1) if I install OS2009.06 on one drive and then just attach another drive to the installation to form the mirror, will it also mirror all needed information from the boot block and partition table? i.e. will second drive be bootable (if I for example need to change the first one)? You'll need to run installgrub. The zpool attach command will remind you to do that when you create the mirror. 2) what's the recommended practice? Partition the drive or let OS install to whole drive? How it'll affect (1)? (I'm talking here about options provided by the livecd installer) If you don't have anything special on the drive and don't plan to have GRUB entries for different OSes, it's simpler to say whole drive. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] open solaris on lenovo
khaldoun writes: hello alfred, thank you very much for your kind support. i had realized that to work on open office installed on regular laptop, is not the same as working on a macintosh apple laptop. i am very beginner in that, for example, you've told me 3. Install with pkg Command line:% pfexec pkg install openoffice but i don't know where i can write this command to execute it. i tried to do it from the terminal but it is saying bad command. What exactly did you type into that terminal window? Did you type the % at the beginning? If so, don't. That's just a prompt. The command you enter should begin with pfexec. i am sorry that i am giving you a lot of pressure, but i need your help badly, since i have notice that even i don't have the concept how to deal with the opensolaris OS It might be worthwhile to look for a book or two about OpenSolaris and/or Solaris and/or UNIX in general. There happens to be a pretty good book specifically about OpenSolaris available now. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] OpenSolaris 2009.06 missing SXCE b114 desktop applications
Andrew Watkins writes: With that in mind how would a user find out which package has the given program in it. So, I want gimp how do I know which package it is in?? This will work: % pkg search -r /usr/bin/gimp ... but, yeah, it'd be nice if the package names reflected the actual contents. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Live Upgrade question
Ivan Ordonez writes: I want to know if there is a good howto on Live Upgrade for opensolaris, or is it possible to do live upgrade on opensolaris? . Assuming you mean the OpenSolaris distribution (as opposed to the Solaris Express bits), Live Upgrade isn't possible on OpenSolaris, because Live Upgrade depends on System V packaging, which isn't used there for the base system itself. Instead, OpenSolaris uses the pkg and beadm commands. They have the same basic feature set, but work differently. There is no manual entry for lustatus, luugrade, etc... on my machine. Can someone please give me a hint? SunOS hostname 5.11 snv_110 i86pc i386 i86pc Solaris That could be either Solaris Express or OpenSolaris. What does pkg say? -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Live Upgrade question
Ivan Ordonez writes: I did get the manual entry for pkg and beadm command. I will look into it and see if these packages can help me. I have 3 harddrive on the machine and I want to make a clone of my boot environment, put it on the second disk. Sort of like making an image of one drive to another. It's not quite the same. The old (and encumbered) LU code was built around disk slices, so the underlying implementation just did a mkfs followed by a massive find|cpio to copy bits around. The new beadm is built around ZFS, so it's *MUCH* faster (it just snapshots the file system), but it doesn't work the way you're expecting. Your best bet is probably to do what most of the rest of us do: set up a ZFS mirror for the bootable dataset (usually named rpool), and then use 'installgrub' to make sure you've got both disks made bootable. (Incidentally, the newest LU on SXCE and S10 also supports ZFS, and also does the snapshot trick. So it's much faster and more usable there, but doesn't quite have the same conceptual simplicity as you're describing.) -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Live Upgrade question
Ivan Ordonez writes: uname -v shows snv_110. Is that Nevada? Sorry I'm a total noob. The 110 part is the build number (one new build every two weeks), and snv means Solaris Nevada, which is the code name for that thing after Solaris 10 that marketing isn't allowing us to call 11. None of it tells you whether you have the OpenSolaris distribution or you have SX:CE. (Other distributions may also have indistiguishable uname output.) -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] NEW desktop
Shamun Mahmud writes: i am building a new desktop. been using the hcl as guidance. have a tyan m/b and two amd opterons, along with 2 gbs of ram. which dvd+-rw drive would the folks on this distribution recommend? what about hard drives and controllers? I haven't been able to locate ones that _don't_ work. As for brands, I like the Lite-On and Plextor DVD drives, Seagate and WD for hard disk drives, and Adaptec for controllers ... but I doubt this is significant. SCSI and SAS seem to be faster than ATA and SATA. As I said, though, I haven't been able to find ones that don't work. (Things that may or may not to work, and might require more caution, are exotics like hardware RAID. There are supported hardware RAID devices from Areca, DPT, and LSI. Others may need to be put in a compatibility mode to work. I prefer software RAID anyway for flexibility reasons.) It shouldn't be this hard ... -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] packet forwarding, one port in, another port out
Tom Chen writes: There are two network ports on the tested network adapter also and they are connected to the two ports on the equipment. Testing packets sent from the external equipment come to one port of our card, qlge0, but the packets must be forwarded to another port, qlge1, then forwarded again back to the second port of the external equipment. So, the equipment can know when the packets it sends and when packets come back. Thus, it can calculate the performance. I am wondering how do I set up the test client machine so that the packets received by one port can exit from another port? I know in Linux, I can use iptables, but iptables isn't available in OpenSolaris. So, how do I set up? Why not just configure the two ports on separate subnets and enable IP forwarding? # routeadm -e ipv4-forwarding -u That seems like the simplest possible answer. If you really want iptables-like difficulty in this test, you could use the equivalent functionality in IP Filter -- the to keyword should do what you're asking. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] NAT router.
Gary Gendel writes: My hardware ethernet router is showing some signs of age and it occurred to me that this is a great opportunity to chuck it and use my SOHO OpenSolaris (SXCE) server to perform this function along with all the other services (mail-server, file-server, etc.). Internet [nic 1] - OpenSolaris (router services) - Intranet [nic 2] | v network services (web, mail, etc.) Yep; that's what I do. However, this encompasses a number of areas that are unfamiliar to me. Specifically: * dhcp server - How do I properly set this up and automatically add dhcp clients to the hosts and/or DNS tables for intranet lookup? How do I pass the appropriate gateway/dns server information to the clients? Run /usr/sadm/admin/bin/dhcpmgr and follow the instructions. It's not too hard to puzzle through (and it's been many years since I set it up), but if you need help, there's always docs.sun.com. * crossbow - Is it better to set up this router in a zone or not? It's probably simpler to get things working first, and then figure out how to move it to a zone if that's what you want. * port forwarding/NAT - General how to (ipf, etc.) On my system, I have this in my /etc/ipf/ipf.conf: pass in quick proto tcp from any to thishost port 3 31000 flags S keep state and this in /etc/ipf/ipnat.conf: map e1000g1 192.168.254.0/24 - myhostname/32 portmap tcp/udp 1:3 map e1000g1 192.168.254.0/24 - myhostname/32 ... but configuring packet filters is a much deeper topic. You'll probably want to spend some time working on that, and using 'xnmap' (or similar) to check your work. Has anyone actually done this? I've found snippets of information on the internet that is useful, but I don't want to put my server out of commission for too long. I really need to put all my ducks in a row before I attempt it. I would use another machine, but none of the ones with multiple nics are available. I suggest doing one thing at a time. Set up DHCP and get that working. Retire your old DHCP server and make sure you can serve all the clients properly. Then figure out how to filter away the packets you don't want. Spend some time testing that and making sure that you're not accidentally dropping necessary traffic. Then, finally, enable NAT and switch the link over. Barring that, would someone act as mentor? I could keep notes and put together a document for anyone wanting to do something similar in the future. I'm probably making too much out of this and it's probably much easier than I imagined, but there are a lot of places for silly mistakes. Based on my experience, the part that's easiest to get wrong is the packet filtering. Once you cross that hurdle, all else is easy. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Q: possible to turn OpenSolaris into a Wifi access point?
Martin Bochnig writes: For normal chipsets found in PCI 2.2 based cards (Desktop systems) there isn't much WLAN driver support yet. For Laptops it looks better. The big missing piece, though, is the lack of AP functionality. I don't think there's even an RFE filed for it yet. (And many of the interfaces I've used don't seem to support ad-hoc mode, either.) laptop-discuss would be the right place to ask about AP functionality. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Some trouble with Samba Snapshots
Edward Ned Harvey writes: The solution was pretty easy. Autosnapshot is just a bunch of cron jobs, /lib/svc/method/zfs-auto-snapshot When I edit that file, there’s a variable, SEP=: and the comment says it’s explicitly editable due to “:” being invalid CIFS character. YUCK! Please file a bug. The scripts under /lib/svc/method/* aren't intended to be configuration interfaces (so changing this is _not_ supported and _will_ fail on upgrade), and, at least in my opinion, there's no good reason at all to have two features that are so obviously in conflict by default. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Question about ZFS Send
Edward Ned Harvey writes: Note also that the data format for the ZFS send/receive mechanism isn't stable. Unless these two systems are running exactly the same OS build and are upgraded in lock-step fashion, you may run into problems. Understood. I've always been paranoid and obsessive about even dump and restore for ext3 etc. Always the same precise exact version. So I appreciate that caution. No idea about ext3, but for UFS, dump and restore are safer, because the UFS on-disk format is a Committed Private interface, and the utilities generate streamed versions of that same interface. The same sort of locking-down just hasn't been done with ZFS yet. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] How do I set up a DSL or (TCP / I.Pv4) connection for OpenSolaris 2008.11?
Dora Henaire writes: Can anyone tell me how to set up a DSL connection or better known as (TCP / I.Pv4)? I have tried everything and nothing has worked! In general, you shouldn't have to do anything special. It should just work. Since it doesn't, you'll need to provide some details: - Do you have an external router / NAT device? If so, is it configured to supply addresses by way of DHCP? - When you run Windows, do you need to configure PPPoE? - When you installed OpenSolaris, did you run the device driver detection tool available in the live CD? What did it report? - Bring up a terminal window, try running these commands, and report the results: pfexec dladm show-link pfexec ifconfig -a Some other pointers: - Try visiting this site for troubleshooting ideas: http://www.opensolaris.org/os/project/nwam/picea/troubleshooting/ - If you're having networking problems, I recommend posting to networking-disc...@opensolaris.org, rather than to this list. The opensolaris-discuss list is a rather noisy one, and not everyone involved with networking is on it. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] files stored
vattini giacomo writes: Hi there how can i know where are stored some files broadcasting in streaming? in which temporary directory? There's no clear answer for that question. You'll need to figure out first what application you're using for streaming. Then consult the documentation for that application or perhaps use a debugger or tracing tool (such as mdb, dtrace, or truss) to find out what the application is doing. It's possible that the file in question is kept only in memory, and never stored on disk anywhere. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Question about ZFS Send
Edward Ned Harvey writes: . Will my data stream going across the network require 1Tb every night? Or will the system somehow generate a delta from the last zfs send until the present time? You have to set it up to do what you want. If you take a snapshot, and then send deltas with the zfs send -i option, then you'll just send the deltas over. If you don't, then you'll end up sending everything. It's not automatic; you have to choose what you want to send. See the zfs(1M) man page for details. Note also that the data format for the ZFS send/receive mechanism isn't stable. Unless these two systems are running exactly the same OS build and are upgraded in lock-step fashion, you may run into problems. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Regular panics: BAD TRAP: type=e
Marco Stadler writes: I did some days ago, but nobody seems to care about. What can I do now? File a bug. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] root changes to xorg.conf?
Cooky Hex writes: On Sun, May 10, 2009 at 12:16 AM, Calum Benson calum.ben...@sun.com wrote: You might find this useful: http://developers.sun.com/jsp_utils/PrintPage.jsp?url=http%3A%2F%2Fdevelopers.sun.com%2Fdeveloper%2FtechnicalArticles%2Fopensolaris%2Fpfexec.html That's very very helpful for newbie like me :) Lots of thanks to you for your time of providing the materials! You can also do this: pfexec pkg install SUNWsudo ... then you'll have sudo on OpenSolaris, just like on other systems. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] process state varies from linux to solaris
barun parichha writes: I don't know, why both of them deviate from the basic open source format, which creates extra confusion. If you're reporting a problem, I suggest filing a bug instead. As for the variations on process state in 'ps' between OSes, I don't see a problem. There's a lot of alignment between them (in particular, at least [STZ] are identical, and [R] is quite similar), and in the places where they're not exactly the same, they're reflecting differences in the underlying system implementation. Solaris isn't Linux, so process status on Solaris shouldn't necessarily be the same as on Linux, should it? -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Dual Boot issue.
Kamin Horvath writes: All the Grubs are the same. It's simply a matter of transferring the contents of the osol menu.lst to the Ubuntu one (or vice versa) If you can access the osol partition (such as via livecd), just copy the boot entries from your osol menu.lst and paste them into the new Ubuntu one. I don't believe that's true. The OpenSolaris GRUB can read and boot from ZFS, but I don't think the Ubuntu one can do that. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Regular panics: BAD TRAP: type=e
Marco Stadler writes: May 6 09:30:38 tank genunix: [ID 655072 kern.notice] ff00043c1b30 zfs:dbuf_ write_ready+1e7 () May 6 09:30:38 tank genunix: [ID 655072 kern.notice] ff00043c1b60 zfs:arc_w rite_ready+2c () There seem to be several bugs filed with somewhat similar symptoms. Have you tried contacting zfs-disc...@opensolaris.org? -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] How to track SSH bad log in attempts / brute force attacks in Solaris?
Anon Y Mous writes: May 6 01:41:43 zone1 sshd[8833]: Failed keyboard-interactive for root from 64.27.1.36 port 37553 ssh2 But what log file are these console messages written to in OpenSolaris 2008.11? Does anybody know? They're logged via the auth_log() function in sshd, which, unless you've specified the -e or -d (debugging) options when invoking, calls syslog(). You should see the messages showing up as auth.notice in the default case, which you can redirect to any file you want via /etc/syslog.conf. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] opensolaris boot process
Nischal writes: can anyone please explain me the boot process in opensolaris? I would like somebody to explain the boot process at the process level like what forks and what execs and so on ( our textbooks say that init forks and execs getty, login blah blah... which is so outdated :) . ) The svc.startd(1M) and smf(5) man pages are probably a good introduction to the way services are started on OpenSolaris. Like traditional UNIX, OpenSolaris does start 'initd' at boot time, but if you look at /etc/inittab, you'll see very few things actually started by init -- only autopush, soconfig, and svc.startd. It's that last one that effectively behaves as the global 'initd' process on OpenSolaris, and forks/execs all the processes you see. (And, since this is System V, there's no getty, but instead ttymon. It'd be nice, though, if someone put ttymon out of our misery and installed mgetty instead ...) -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Solaris 10 10/08 install Crossbow
Gian Paolo Buono writes: Thanks for your reply, Now I have installed Solaris Express Community Edition and Crossbow work fine ... Can I create a zone with solaris10 on nevada ? I don't believe that's supported yet, but you'd need to contact the Zones community (zones-disc...@opensolaris.org) to get more accurate information. For Solaris 8 i have read that there is Solaris 8 Migration Assistant work on nevada ? Yes, I think that does exist. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Solaris 10 10/08 install Crossbow
Gian Paolo writes: is possible to install Crossbow on Solaris 10 10/08 sparc ? No. You could reinstall your system with OpenSolaris, and thus get Crossbow (plus a lot of other new features), but there's no way to install Crossbow on Solaris 10. If you have a support contract, then I would recommend contacting your Sun support representative and asking about CR 6790102. If you don't have a support contract, then I'd recommend sticking with OpenSolaris instead. You could upgrade your system to SX:CE in a relatively simple manner. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] b111a: Power Management and nwam-issue ?
Paul Griffith writes: I am still seeing issues with VirtualBox 2.2.2 and nwam. If you're seeing the 'dhcpagent' process spinning and consuming CPU time, then it's very likely to be the same CR that I cited. The fix for that problem was just integrated yesterday. Running OS 2008.11, waiting for 2009.06 to hit release! 2008.11 is now ancient. Unless you really have a need to stick with that (a paid support contract would be a good reason), I'd suggest moving over to the 'http://pkg.opensolaris.org/dev' package authority. It won't help right away with this problem -- unless you're willing to build your own binaries, you'll need to wait for the fix to percolate through the system; probably around 4 weeks -- but it'll certainly allow you to pick up the fix as soon as it's available rather than waiting many months between the 'stable' releases. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Solaris 10 Startup
Mike Magie writes: What replaced the /etc/rc2.d/s89 startup scripts in Solaris 10? There's no simple answer to that, because the numbers on the scripts reflected only relative ordering, not any sort of identity. (In other words, administrators and third party vendors were free to use S89 as a prefix for their own scripts.) Are you referring to S89PRESERVE or maybe the obscure S89bdconfig? If it's S89PRESERVE, then that's still present, and it still runs at boot time. If it's S89bdconfig, then that's also still there in S10, but it's gone from OpenSolaris. Everything relating to buttons and dials is long since obsolete. If it's something else, then please specify. (And you may want to use smf-inter...@opensolaris.org instead of this list; your question seems to be about SMF in particular, not about OpenSolaris in general.) -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] b111a: Power Management and nwam-issue ?
Detlef drew...@sun.com writes: 3. Also: After the boot I see dhcpagent/1 consuming 50 % CPU (looks like 1 core) and the nwam applet will not show up in the gnome panel. I first have to kill -9 the dhcpagent, then the nwam applet comes up and the cpu consuming goes away. This part sounds like CR 6743929. A fix for it has been code reviewed and should be integrated some time soon now. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] uname -a ... 32bit vs 64bit
Octave Orgeron writes: Now putting all that info into uname would just complicate life for everyone and break all sorts of stuff. As such, uname is for very high-level info and isainfo is for detailed. Exactly. Putting detailed processor information into uname is not only unnecessary, but it breaks backward compatibility by forcing people who are depending on uname output (often inside of 'configure' scripts) to deal with new and unexpected responses from the system. When we've done this in the past, it's been to add support for a new processor or system family, and not when we've just added support for yet another variant of an existing processor. Breaking existing code can sometimes be the only answer, but it'd better be for a really good reason. I'm not sure that merely disliking i386 as shorthand for all Intel and AMD x86 compatible CPUs is enough of a reason to make ./configure fall over and die. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] how to check the time stamp on Solaris?
Amy writes: To change the date on my Solaris computer, I log in as superuser, and I use the date command to change the date. But how do I know if the date was later changed by someone else, and then, changed back again? The simplest answer is to make sure you have good control over who has privileged access to your system: use good passwords and hand them out. A more complicated answer is to set up the auditing subsystem. Start by reading bsmconv(1M) and audit(1M), and look into the documentation on docs.sun.com. Perhaps a more useful answer is that you likely shouldn't have to set the date by using the date command at all. If you're connected to any half-way reasonable network, you should have access to an NTP server somewhere. Set up /etc/inet/ntp.conf (see /etc/inet/ntp.client for an example), and then svcadm enable ntp. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] how to check the time stamp on Solaris?
James Carlson writes: Amy writes: To change the date on my Solaris computer, I log in as superuser, and I use the date command to change the date. But how do I know if the date was later changed by someone else, and then, changed back again? The simplest answer is to make sure you have good control over who has privileged access to your system: use good passwords and hand them out. ... and don't hand them out. What a difference a word can make. ;-} -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] gettext
Hanma writes: checking for library containing acl_trivial... -lsec That part looks right. /bin/sh ../libtool --tag=CC--mode=link gcc -std=gnu99 -g -O2-o msgcmp msgcmp-msgcmp.o libgettextsrc.la gcc -std=gnu99 -g -O2 -o .libs/msgcmp msgcmp-msgcmp.o ./.libs/libgettextsrc.so /export/home/Pein/___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] gettext
Hanma writes: Carlsonj, can you tell me, how can I install Epiphany browser? Many .tar.gz open source packages don't installes. So how can I install packages? If it's .tar.gz, then you need to do this to unpack it first: gunzip -c filename.tar.gz | tar xf - where filename is the name of the file on your system. That will extract (decompress and unarchive) the contents of the file. What you do next depends on what was _inside_ that .tar.gz file. Some software is shipped as source, in which case you'll need to configure and compile it. Other software is shipped as binaries with an installer script, and you'll need to run that. Still other software is shipped as System V packages, and you'll need to run pkgadd with -d to pick up that directory. Most .tar.gz files have a README or INSTALL file with detailed instructions located somewhere in the archive. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Can mysql be slower in a zone?
Mike Gerdts writes: On Fri, Apr 10, 2009 at 9:19 AM, Mike DeMarco mikej...@yahoo.com wrote: You should only see a very little performace hit when using zones. Maybe 1 or 2 %. Are you using exclusive NIC to move the TCP stack down into the zone? What evidence do you have for that? There should be no overhead for a zone. If you have workloads that show a performance hit in zones, please bring it up at zones-discuss. Indeed. It's not as though they go through any sort of layer. The zone ID in the kernel is just a number and it's used in much the same way that a UID or GID is used. We're always comparing based on it, and the default (when there are no zones present) is just zero (also known as the global zone). If you see a performance difference, then I'd class that as a defect. It shouldn't be a measurable change, just as running with either UID 0 or UID 302 shouldn't be noticably different in performance. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] network autocomfiguration daemon question
Alex writes: I have an acer aspire one laptop running OpenSolaris 111 that I connect to the internet via ethernet at work. Is there anyway to re-request a DHCP lease via the network autoconf daemon? The system does that all on its own. The DHCP client will attempt to get a lease continuously. There's no failed state where we just give up. For example, i have an ip of 0.0.0.0 without a cable plugged in, I plug an Ethernet cable and it remains at 0.0.0.0. I've tried switching between auto and wired networks without success. I know how to configure things manually, but I would prefer to do it automatically. It sounds like the interface itself isn't working. Some of the troubleshooting techniques on the NWAM web page might be helpful, but I'd say that the first things to check are the output of ifconfig (does it say DHCP is running?) and either snoop or wireshark. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] disconnecting hdd from zfs mirror hangs whole
UNIX admin writes: Or volume management, which to this day doesn't work correctly (one can't create a zpool on a removable device, then eject (zpool export) and plug that device somewhere else and have it instantly imported by vold(1M). And if you're interested, the RFE for this was closed as will not fix. When saying something like that, it helps quite a lot of you can cite the actual CR number so that others can help either rescue the CR (if it's in need of rescue) or provide a more comprehensive explanation. In this case, though, I'll hazard a guess: everything related to the old 'vold' is gone. Just plain gone. Removed by PSARC/2005/672. It is no more. It is an ex-daemon. ;-} RFEs to it are moot. The Tamarack project is the replacement for it. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] disconnecting hdd from zfs mirror hangs whole
a b writes: When saying something like that, it helps quite a lot of you can cite the actual CR number so that others can help either rescue the CR (if it's in need of rescue) or provide a more comprehensive explanation. The CR is 681661 http://bugs.opensolaris.org/view_bug.do?bug_id=6811661 That's all you needed to supply. The CR was closed by renaud.ma...@sun.com, who noted in the evaluation that vold is gone, Tamarack replaced it, and that Tamarack *does* handle ZFS storage pools. The CR was then updated by artem.kachitch...@sun.com, who noted that Tamarack did do this, but that the methods it added are not invoked by USB hot plug, so that's still a problem. I'll leave it up to Artem (whom I've copied) to explain why he just updated the Evaluation field and didn't either reopen it or change the status, but my guess would have to be that this CR (given as a see also to the CR you cite) is the reason: 6786446 hald doesn't handle zfs formatted hotplug media and raises an error dialog. Fixing that problem would fix the problem you later reported in 6811661, making your CR effectively a duplicate. Is my time completely worthless? Should I have to worry about such details, or should I be able to use Solaris to get work done, and get it done fast and efficiently? You probably shouldn't assume that developers are either (a) trying to thwart you deliberately or (b) actually paying attention to your individual needs. Software development is just not the same thing as paid support. If you need paid support, there are solutions for that, but arguments on opensolaris-discuss probably won't get there. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Possible IBM aquisition of Sun
Alexander Vlasov writes: Have you tried aptitude? I sure have. Having suffered long enough with apt and aptitude on Debian is what eventually drove me to convert my home system from Linux to Solaris. :-/ -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] disconnecting hdd from zfs mirror hangs whole system
[corrected top-post] Alexander Vlasov writes: roland wrote: i added a bugreport to bugster for this yesterday. unfortunately, i dumped the response mail with the bug-id and now i cannot find my own bugreport anymore. (did somebody delete that?) as this thread is linked from the bugster bugreport, whoever is reading this thread please post the bug id here. Knowing your SunID it would take 5 minutes. Bugster supports reported email as search criterion. It's CR 6826247. I don't see where anything was deleted. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] fun with aptitude [was Re: Possible IBM aquisition of Sun]
Alexander Vlasov writes: That's really strange. Have you read /usr/share/doc/aptitude/README? I didn't specify what problems I had, so I guess I don't see why it's necessarily strange. And, yes, for the record, I did read the documentation. I'd been running Linux for years before I gave up. currently pkg has very rudimentary search ability, like you can't ask `which packages were installed only to satifsy other packages' dependencies', `show me all games' or `which packages has arrived into repository since last update'. Some search abilities of aptitude aren't even applicable in pkg since pkg doesn't have appropriate concepts (like priorities; pkg only supports `preferred' and `other' repos, no arrangement by-priority) The nasty problem I had with aptitude was (with Debian 'unstable'; 'stable' had too few features) wandering into dark corners with certain desired upgrades being prohibited because of a lack of version compatibility in other packages, and other upgrades causing still other bits to begin failing. The real issue, I suspect, is a lack of stability and basic architecture in the underlying system, but it shows through the packaging system as the most annoying sort of chaos. I had no problems searching for packages. I did have problems with random packages breaking over time. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Clean Install ZFS root SNV_110 Panics at Boot
aric writes: The failsafe does not appear to understand the 'boot' command. I tried setting the svcadm milestone -d none: svcadm Repository is read-only. Exiting. Init 6 and rebooting puts me back to the same problem. Can I edit grub to do this? Yes. At boot time, edit the grub entry (with 'e'), select the kernel entry, and edit (again, 'e') to add -m milestone=none (for instance). -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] libumem.so problem in Solaris 8
Jason King writes: On Thu, Apr 2, 2009 at 2:19 PM, Anandram anandra...@huawei.com wrote: Also, please let me know whether the library /usr/lib/libumem.so is present in solaris 8? or it is present only in solaris 9 and above versions? This isn't really the place for Solaris 8 or 9 support. But to answer the question, I wasn't aware of an official libumem backport. Either way the error is saying your're trying to use a 32bit lib with a 64bit binary. Try /usr/lib/sparcv9/libumem.so instead. Or just leave out the path. LD_PRELOAD=libumem.so.1 should work. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] useradd
Hanma writes: I can't understand what to do to authorise the user. I can't understand this -A authorization One or more comma separated authorizations defined in auth_attr(4). Only a user or role who has grant rights to the authorization can assign it to an account. what I must to write after -A? Please give me an example. I searched everywhere, but i can't find what to write. Did you try looking at the auth_attr(4) man page? An example might be: useradd -A solaris.admin.usermgr.pswd passfixer -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] DHCP obtained address random released
zhang yi writes: This issue annoy me so much. I am now using opensolaris 101a version. The NIC card release its DHCP obtained IP address automatically without renew its address after maybe 24 hrs of work. The address disappears without notice. wow... So fancy features... This seems also exist in 106 based opensolaris. Better mailing lists for this might be networking-discuss and/or nwam-discuss. It's hard to tell from that description what problem you might be having. It could be a driver problem, something wrong with the DHCP server, or even a bad IP filter configuration. I suggest starting here to gather some useful information about the problem: http://www.opensolaris.org/os/project/nwam/picea/troubleshooting/ and (after gathering debug logs) try posting on one of the lists described above, or (if you're certain you've found a problem in the system) use defect.opensolaris.org to file a bug. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Does wvdial work for OpenSolaris?
Martin Bochnig writes: On Mon, Mar 30, 2009 at 3:00 AM, Paul Harper pjhar...@yahoo.com wrote: I use wvdial to connect to my gprs phone with Linux. I have tried to find a ready made wvdial package for OpenSolaris but apparently one does not exist. Would wvdial work for OpenSolaris if compiled or is OpenSolaris's version of pppd so different from Linux that it would not work? Mmh, the ppp implementation should not be the blocker. Circa since Solaris 8 June 2000 (Update 1) Solaris uses exactly the same pppd, as LinUX does. Namely exactly pppd, rather than the UUCP based aspppd. Yes. And in fact, that version of PPP (originally written at CMU, then maintained at ANU, and now by samba.org) was originally written well before there was such a thing as Linux, and it ran on SunOS and Solaris systems before Linux itself was written. That people confuse pppd with Linux is unfortunate but expected. :-/ In any event, I don't know of anyone who has tried to run wvDial on Solaris. I would expect that it could be ported with some effort, as it's just a user-level application. (Scanning the web, it seems it relies on something called WvStreams, which others have tried and failed to port to other systems.) I haven't tried myself, mostly because my experience with ease of use tools like this is poor: they don't always work, and when they fail, you're usually worse off than you were before. I find it easier just to configure pppd properly. But if someone wanted a project, porting that stuff over and contributing it would probably be a good one. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] useradd
Hanma writes: how to use useradd comand in terminal? i can't understand how in manual. can you give me example? # useradd newuser -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] package naming [was RE: Which Samba packages to use and, what do Usr, Kernel, Root packages me]
a b writes: and there are some obscure ones (such as the .u and .v architecture-specific packages). Aaahhh! Now things are getting to be really interesting! I love such arcane knowledge, if you don't mind, please share insight on what these meant, if you have any. They're still around. The .u is for sun4u and .v is for sun4v. For example, if you look a the SPARC Solaris install media, you'll see two packages, one named SUNWcar.u and the other named SUNWcar.v. One has ARCH=sparc.sun4u and the other has ARCH=sparc.sun4v. The installer has some magic to make sure that the right ones are installed. IPS is long ways away from being useful, and it's slow; on top of that, they really shot themselves in the foot with setting GNU to be the default. IPS is a work in progress. They're nowhere near done, so I think it's pretty unfair to judge them. It would be better at this point to contribute constructively (e.g., if you find a performance problem, analyze it, and fix it). For what it's worth, I'm slowly converting my systems over from SX:CE to the OpenSolaris distribution. It's tough work, but given the direction things are going, I think it'll eventually be worthwhile. And since I have simple control over my own path by setting $PATH, the GNU by default thing never really bugged me. I was more harmed by ancient (and awful) scripts of mine finally going kablooie and forcing me to fix the old bugs they had. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] [ogb-discuss] General THANKLESS- and RESPECTLESSness towards Joerg Schilling (and others, which I leave out of this msg.) __/__ Was: Emergency project to rescue Opensolaris from IBM
Garrett D'Amore writes: I don't know who Jennifer is, but I think everyone who's had more than passing experience with either Solaris or OpenSolaris knows that Joerg has made some real contributions. While Jennifer's comments are unfortunate, I don't think they are representative of any community, and I think all the parties concerned (excepting perhaps Jennifer herself) already know that. Its not worth getting too upset over, I think. Indeed. procmail works great for solving problems like this. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Which Samba packages to use and, what do Usr, Kernel, Root packages me
UNIX admin writes: The r is the root portion of this component, payload which goes into / (usually /etc/, which is in the / filesystem). Then there is the u portion of the component, which goes into the /usr filesystem. Finally there is the kr portion of the component, which usually delivers (kernel) drivers. For what it's worth, those are just naming conventions, and not everything follows that naming. The actual package type is set by the SUNW_PKGTYPE variable, described in the pkginfo(4) man page. The reason that there's a distinction between root and usr bits is that Solaris (at least at one point) supported booting off of a small local disk (containing just /), and remote mounting /usr. More generally, it's because /usr is noted as a supported mount point in filesystem(5). The kernel distinction has to do at least in part with Zones. A zone has both root and usr packages, but there's no point at all in putting kernel drivers into a zone. We've had other packaging and naming distinctions in the past, such as the regular and x (64 bit) packages [removed in S10], and there are some obscure ones (such as the .u and .v architecture-specific packages). Most of this arcana, though, is probably fading in meaning. Sun's OpenSolaris distribution no longer bases the system on System V packaging. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] IBM and Auschwitz __/__ Re: Possible IBM aquisition of Sun
Martin Bochnig writes: Be also aware, that IBM supported Nazi-Germany's dead-camps, by selling the needed information technology to them: Many thanks from all of us for Godwinning this pointless thread. It needed to be done. http://en.wikipedia.org/wiki/Godwin%27s_law -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] IBM and Auschwitz __/__ Re: Possible IBM aquisition of Sun
ольга крыжановская writes: On 3/23/09, James Carlson james.d.carl...@sun.com wrote: Martin Bochnig writes: Be also aware, that IBM supported Nazi-Germany's dead-camps, by selling the needed information technology to them: Many thanks from all of us for Godwinning this pointless thread. It needed to be done. http://en.wikipedia.org/wiki/Godwin%27s_law James, this is not very funny. Do you wish to hear what the Nazis did in the Ukraine? I don't wish to hear about it on opensolaris-discuss@opensolaris.org, where it is entirely off-topic. I also don't wish to hear more about the business deal that may or may not occur between Sun and some other corporation on this list. Besides being essentially just rumor-mongering, the discussion is being had by folks who *by definition* have no useful information about the topic -- none of them could have special information on the deal, if there indeed is one -- rendering the whole thing just plain pointless. In any event, many thanks again for killing off the thread. It's quite welcome. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] IBM and Auschwitz __/__ Re: Possible IBM aquisition of Sun
Alan Coopersmith writes: Martin Bochnig wrote: Be also aware, that IBM supported Nazi-Germany's dead-camps, by selling the needed information technology to them: It's highly unlikely anyone working at IBM in the late 1930's/early 1940's is still working there. Blaming the current IBM employees for the actions of some of their predecessors makes no more sense than blaming everyone in Germany today for the horrific actions taken by some of the people who were there 70 years ago.So like Jim, I don't see any real relevance to current events there. Actually, that's not quite what Jim was saying. He was saying that he sees no relevance whatsoever to this list, at least at this point in time. I'll leave questions of collective guilt and the historical record for those better equipped to answer them. Fortunately, we needn't resolve them here ... as they're still quite glaringly off-topic. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] wireless browsing is slow
W. Wayne Liauh writes: have you tested whether it is slow with another OS? can you provide a comparison in performance on the same wlan between windows and opensolaris. As I have been told, many of the wireless-related problems will be solved in build 110. Fingers crossed. The fix for CR 6805726 went into build 110. It seems to have updated the 'iwh', 'iwk', and 'wpi' drivers. Users of 'iwk' have reported that the new driver is *much* more stable. That seems to be the only wireless fix in build 110, but for those affected by stability problems on those drivers, it seems to be a biggie. There are fixes for problems in many of the wired drivers as well, but none looks as interesting. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] files newer than a certain hours/minutes
Omer Faruk Sen writes: I have just realised that even Solaris 10's find command has not cmin option (which is valid for Linux) there is only ctime is used for Days. How can I check files which are created for example 1 hour ago? In addition to the common touch-based work-around, you can also just invoke GNU find as gfind on OpenSolaris, and, just as on Linux, it has the -cmin option. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Opensolaris Bible: Buy it!
Harry Putnam writes: I wanted to partition and slice up my disk to be able to work with raidz. Maybe that isn't really important and all the same stuff applies to any zpool. I don't know yet... I'm just getting started. I'm not sure that's a wise idea in the first place. A RAID volume tries to spread the I/O load across the members. If you do that with multiple partitions, you're naturally going to get the lowest possible performance -- causing the disk head to bounce back and forth between partitions on each access. It's redundant array of inexpensive *disks*, not partitions. As Dave said, your best bet is to feed ZFS a whole disk, and let it do as it will with it. I had some trouble getting advice about making raidz on partitions, probably because it isn't the best usage of raidz or even of zfs. Indeed. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Regarding Pstack
Akhil Jain writes: Can you please tell me some good doc links about understanding the output of Pstack. Like when I do a pstack on my process it shows like: 0009a890 main (1c, ffbff45c, ffbff4d0, 24d000, fd0a0380, fd0a03c0) + 2018 00098448 _start (0, 0, 0, 0, 0, 0) + 108 So I want to know what exactly is +2018 or +108 . I want to know about the contents of the stack of a process. Those numbers are the actual offset (in hex) of the program counter from the symbol given. In other words, the stack shows that a call was made from _start+108 to the function main(), and the program counter is currently at the instruction main+2018. The numbers on the left-hand side are the stack frame pointers. The numbers in parenthesis are the values of the registers usually used for argument passing. (There's no guarantee that they represent the actual passed values, as the compiler tends to reuse registers. You need to look at the actual assembly code to tease this information apart.) This probably isn't terribly interesting information unless you're looking at the code in a debugger, such as mdb. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Copying files and folders
Hanma writes:
What means ''grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
it don't works. There is message ./install.sh[1756]: cd:
usr/share/icons/hicolor: [No such file or directory]
cp: cannot access usr/share/icons/hicolor/48x48/apps/opera.png
cp: cannot access usr/share/icons/hicolor/32x32/apps/opera.png
cp: cannot access usr/share/icons/hicolor/22x22/apps/opera.png
It means that the person who wrote the script assumed that 'grep'
would take a -q option. That's true for the POSIX standards-
conforming grep (/usr/xpg4/bin/grep) and for GNU grep
(/usr/gnu/bin/grep), but unfortunately not true for /usr/bin/grep on
Solaris.
The problem is in this part of the 'install.sh' script (lines
1194-1197):
manifest_contains ()
{
grep -q $1'$' Manifest.md5
}
Changing that grep to ggrep should fix the problem.
(For what it's worth, lack of support of -q in the default
/usr/bin/grep is just a bug, not an intentional feature.)
--
James Carlson, Solaris Networking james.d.carl...@sun.com
Sun Microsystems / 35 Network Drive71.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] Any groups working on consol developement
Harry Putnam writes: Lingbo Tang lingbo.t...@sun.com writes: There have been virtual console functionality in solaris kernel. It's easy to extend the console environment, like scrollable screen in future. You can refer to project page on opensolaris.org for the latest status. If anyone from community can offer help, that will be great. Thank you. I'm not sure which project you mean... something here? http://opensolaris.org/os/projects/#portal http://www.opensolaris.org/os/project/vconsole/ -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Link to phoronix benchmark on opensolaris.com
Lurie writes: Seriously guys, What on earth is the link to AMD Shanghai Opteron: Linux vs. OpenSolaris Benchmarks doing on main page of opensolaris.com ? That article is seriously biased towards Linux as has been discussed many times already. Way to put potential users off... :) It looks like something that's auto-generated to me, not something that was put there intentionally. In any event, aren't we opensolaris.org here and not opensolaris.com? -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] opensolaris.org not responding
m...@bruningsystems.com writes: I would post this to website-discuss, except that I am not on that mailing list. To get on that mailing list, I need to get to opensolaris.org. www.opensolaris.org has timed out every time I have tried it today. I am having no problems with any other sites. You can also subscribe to mailing lists by using the -request address. Just send a subscription request to: website-discuss-requ...@opensolaris.org -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] EADDRINUSE error even after setting SO_REUSEADDR
neelesh writes: I am running a TCP client and TCP server in the same machine(64 bit x86 machine with Solaris 10). The Server and Client establish a connection and exchange messages. The port used by them is in TIME_WAIT state, after the completion. If I run the Server and Client programs again immediately within the TIME_WAIT state, in the Client program I get the errno 125 when it tries to connect(). I am using IPv6 addresses. I ensured to set the socket option SO_REUSEADDR. Can some one help me if there is any way to overcome this error. Can you post your code? At a guess, you might not have set the socket option before doing the bind() call, as is generally required for TCP-speaking servers. But that's just a guess. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Basic questions about pkg
Harry Putnam writes: James Carlson james.d.carl...@sun.com writes: There aren't any. Should there be? I'm not telling pkg where to connect to on the command line. Yet it knows. Its getting information somewhere... in some sense that is a configuration. There are no files that are documented for you to tweak. Yes, of course, the information is stored in a file. It's not documented, because it may change. I guess I'm asksing how to control that. pkg set-authority http://pkg.opensolaris.org/dev/ [...] OK, thanks. So will that be integrated into my `image' or will I need to upgrade everything to dev for a new `image'? It switches you from the stable branch to the development branch. When you do an upgrade, you'll be pulling the newer development bits. I now have several on the grub menu when I boot, but looking in /boot/grub I don't find anything that resembles what I see at boot time. You shouldn't need to do that. What are you trying to do? I guess this is another case of there being no configuration. So If I wanted to remove some of those BE... how would I do that? Just by the `e' edit key at boot time? See beadm(1M). -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Basic questions about pkg
Harry Putnam writes: what does an `authority' designation look like (the URL). Here are two: http://pkg.opensolaris.org/ http://pkg.opensolaris.org/dev/ Where is that set if not command line (pkg -a AUTH)? One comes with the system as normally installed. I did not find info about where to find any configuration files for pkg. There aren't any. Should there be? Also was not at all clear (to me) how to add a new addon authority. I mean in a configuration... not from command line. I did see the `-a' flag but no real description of what the URL would consist of. You do it from the command line. I assume by in a configuration, you mean that you _want_ to edit a file. It doesn't work that way. For example, I'm running opensol-11 installed from the official CD. Whatever authority it sets up, doesn't know anything about the pkg `lynx'. Although I saw on google that it is available in a SUN pkg somewhere. How would I tell pkg how to find that and install it. `pkg search -r lynx' doesn't find it. I think lynx integrated as of build 106, which means that it's not yet on the stable branch. You can pick it up by moving to the dev branch -- by making your authority be this: http://pkg.opensolaris.org/dev/ -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] emacs under solaris suggested keybindings please
Dag H. Wanvik writes: Dieter Kluenter die...@dkluenter.de writes: and a ~/.xmodmaprc file keycode 64 = Meta_L Alt_L this allows Alt+x operations Personally, I chose to use this stanza in my .emacs file to avoid changing the meaning of Alt and Meta for other programs: (setq x-alt-keysym 'meta) I haven't found that the above works for the odd changes in the Xorg server that occurred between 106 and 107. After a bunch of trial and error (mostly error), I found that the following, though, does restore normal operation: xmodmap -e clear mod4 -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] what are all these versions anyway? [was Re: emacs under solaris suggested keybindings please]
Harry Putnam writes: (If this question seems to off topic, please feel free to reply privately if you have time) No problem. I've changed the subject line to match the new topic. Fisrt, thanks for the additional tip. I'm very new here (on osol) and somewhat lost about mentions of version I see in the various news groups. Names like Nevada and Indiana also apparently versions. Not exactly. Nevada is the code name for the next Minor release of Solaris after Solaris 10. It was given a code name rather than a number (essentially) because marketing reserves the right to compute N+1 at a later time. ;-} OpenSolaris (the source code) and Nevada are effectively the same thing right now. Indiana is the name of a project. That project is producing something called the OpenSolaris distribution, which is based on a new installer and software packaging system. A distribution is a packaged form of the code that you can run on a system. There are many distributions using (or based on) OpenSolaris; see the web site for more information. Yes, it's a little confusing to have two distinct things both called OpenSolaris -- a source base and a distribution -- but that's how it is. There's also the Solaris Express distribution, which is the old installer and uses SysV packaging. This is slowly being replaced, and still exists because it's required for those who build from source. Finally, there are build numbers. These are incremented every two weeks. Because they're tracked at the source level, most distributions number their releases based on the build number. At a uname -a prompt I see `5.11 snv_101b'. I wondered if you might be able to steer me to documentation that explains how versioning and the various names work under Solaris? You mention 106 and 107.. where do those come from? If you're using the OpenSolaris distribution (and it sounds like you are), then you need to switch to the dev branch to see the newer builds -- change your authority to http://pkg.opensolaris.org/dev/;. If you do that, you should be able to upgrade to each of the weekly builds. The 101b build was the one released as OpenSolaris 2008.11. There'll likely be another such stable release in a few months for those who aren't on the dev train. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] OpenSolaris install on x4150?
Rich Reynolds writes: I had a similar problem on different hardware, and found that hand plumbing the interface and re-enable nwam served as a sufficient work around... svcadm clear nwam is the simpler work-around. The real problem here isn't nwam, but the device subsystem, which (inconsistently) requires all privileges in order to open the DLD control node early in boot. The fix (integrated into build 109) is to make nwamd open the device using all privileges (sigh). -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] Build error (dmake: Warning: Target `all.targ' not remade because of errors)
Henry Lau writes: Hi, While trying to build the latest src of opensolaris with Studio 12, I hit following errors. Any idea what I did wrong. Thanks! /export/home/bl/Desktop/usr/src/tools/proto/opt/onbld/bin/i386/ctfconvert -i -L VERSION debug32/modhash.o dmake: Warning: Target `all.targ' not remade because of errors Current working directory /export/home/bl/Desktop/usr/src/uts/intel/genunix The crucial information that would identify the problem is _above_ this point in your 'nightly.log' file. The above text shows that dmake has detected an error while building all.targ in genunix, but doesn't show what actual build rule failed or how it failed. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] opensolaris + pppoe
Ulrich Hiller writes: My files look like this: /etc/ppp/peers/myisp: [...] user [my account name at my ISP] password [my password at my ISP] Use either the (old) password option, or the more modern /etc/ppp/*-secrets files, but not both. It's not necessary to specify the password both ways. /etc/ppp/options.iprb0: 38400 asyncmap 0xa Those two options don't make sense here, and should be removed. /etc/ppp/myisp-chat: That file isn't involved -- there's no text mode chatting on a PPPoE link -- ignore it. When I now run `pppd call myisp' I get a short LED blink at the dsl modem but a connection is not established. There cannot be a hardware or modem problem, because under several linux distributions it works. /var/adm/messages does not give a message about it. /etc/ppp/connect-errors says 2008/12/14 18:57:13CET: /usr/lib/inet/pppoec: PPPoE operation requires the use of a tunneling device What does that mean? Can somebody give me a hint what I have to do? It means that you haven't run /usr/sbin/sppptun to configure iprb0 for use with PPPoE. Setting up the /etc/ppp/pppoe.if file makes sure that this happens at system boot time, but changes to that file don't affect the running system. You can simulate the same thing that happens at boot (and thus configure iprb0 for use with PPPoE tunneling) by doing this: pfexec /etc/init.d/pppd See the sppptun(1M) man page for more information. If you have other problems with PPP, please do run it with the debug option, and post any issues to networking-disc...@opensolaris.org. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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] [on-discuss] New community based development list
Ghee Teo writes: C. Bergström wrote: Thanks for the support Alexander.. I think the reception from those outside Sun is quite positive so far. +1 from me. Another one from inside Sun :) He's gotten several +1s from inside Sun (including one from me), and, as far as I can tell, nobody posting from a sun.com account has said otherwise, at least publicly. That he's still qualifying that statement seems quite strange to me. In any event, I think he's fixing a problem that doesn't actually exist, removing barriers that are purely imaginary. If you want to make changes in the code -- go ahead. Knock yourself out. Compile and distribute (or not) that code as you see fit. You can also share your changes on hg.opensolaris.org with fairly minimal overhead; there's just enough of a fog-a-mirror test there to make sure we don't have a pile of p0rn and ripped software repositories set up by bad guys. The part of the process that has overhead occurs only _IF_ you choose to integrate into the common gate. That requires review (sometimes multiple kinds of review, depending on the kind of change) and testing, so that the common gate doesn't just become a cesspool. If the request is to create a random project to do something possibly interesting to zero or more people, then +1. Go for it, even if the result is a long-lived fork. If the request here really is for the common ON gate to become a cesspool, though, I'd have to give a -1 to that. I don't think anyone could possibly benefit from such a result, even the original requester. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] SUNWgnome-im-client breaks beadm
paul writes: robs schrieb: # pkg install SUNWgnome-im-client DOWNLOADPKGS FILES XFER (MB) Completed 67/67 11346/11346 143.05/143.05 [snip] pathetic isn't it? The bottom line is: you can't install software with pkg as you will end up with an inconsistent system image. The only halfway safe command is pkg image-update. You *can* end up inconsistent that way because it pulls in the dependencies, but doesn't chase back up the chain to find what was dependent on those things. I believe it's a known problem, and the simple solution (until the problem is fixed) is to do image-update before adding any packages. It totally escapes me how opensolaris managed to mess up the distinction between OS and applications even more than all those stupid linux package managers. I don't believe it has anything to do with any such distinction. Get a life, use windows ;) I think you're missing at least the word or in that statement ... -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] [on-discuss] New community based development list
Shawn Walker writes: If have no idea why you think you can't do all of that using opensolaris.org, but good luck. I think the original complaint is the need for code review before ON integration. It's too slow. But +1 to both of your comments. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] where to file bugs for s10 u6?
[EMAIL PROTECTED] writes: I get an error using ::whatis in mdb with solaris 10 update 6. 30001d69f00::whatis mdb: couldn't find modctl walker: unknown walk name Do I need a support contract to file a bug? If not, where is the right place? (I tried google, but I guess I am not searching for the right thing). You'll likely need a support contract to get a fix, and filing a bug through support is probably the best approach. Filing a bug at bugs.opensolaris.org for an S10 problem, though, will eventually get to the right place, at least for evaluation. The system isn't very automated, and we have to triage the bugs arriving through there by hand. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] Using NWAM to connect to secured wifi networks
Roman Strobl writes: is there a way to connect using NWAM to a secured wifi network that doesn't broadcast it's SSID? See: http://defect.opensolaris.org/bz/show_bug.cgi?id=5048 It's a bug we're currently fixing. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] Using NWAM to connect to secured wifi networks
Roman Strobl writes: It's a bug we're currently fixing. Thanks! I assume that this will not get fixed for 2008.11, right? 2008.11 is already out the door. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] Any xemacs users out there? I could use some advice wrt packaging xemacs for OpenSolaris
Gordon Prieur writes: I tried contacting an xemacs user who used to work at Sun, but it looks like he no longer works at Sun. There are some around. I think Sebastien Roy is one. The excess of GUI grot annoys me, so I stick with GNU emacs with X. A few others around here use one of the emacs flavors inside a terminal window (for no reason I can see). I looked at the mailing lists at xemacs.org and it looks like a usenet newsgroup is their primary mailing list. NNTP -- try news1nwk.sfbay for a SWAN-based server, or just use google's news access. As soon as I figure out what tools Sun has for reading from and sending to newsgroups, I'll post there (I haven't read news groups sine the late 80's:-) Too bad. :-/ -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] [Fwd: [accessibility-discuss] I have some questions]
Li Yuan writes: Hi, I am going to try open solaris, but I have to get more memory first. My questions are as follows. How forgiving is open solaris to times when the computer looses power. I know this can be a serious problem in windows, but I have had no problem when this happened with my ubuntu machine. Very forgiving. ZFS is designed to maintain coherent data on the disk at all times; all writes are scheduled so that the disk data structures move from one known-correct state to another, so there's no need for fsck or Windows chkdsk. UFS (not used by default anymore) includes a transaction logging feature that's enabled by default. This also protects against corruption in case of failure. Right now you need 750 Mb to run the live CD. Is this going to be corrected so 512 Mb will work? I doubt it. We're generally moving forward in time rather than backwards, and new machines aren't getting less memory. But do check with the [EMAIL PROTECTED] list about the installer technology. Perhaps it'd even be possible for you (or someone else who cares about old systems) to start a project to support that. I would also like to know if there is a add remove programs feature for picking software? Sure. On the OpenSolaris distribution, that's the pkg(1) command, and in the GNOME desktop, there are GUI tools under System-Administration for package management and upgrades. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] [Fwd: [accessibility-discuss] I have some questions]
Glenn Lagasse writes: Several of us have been working on fixing this for a few weeks now. We're mostly 'there', just a few loose ends to tie up as it were. The formal release of 2008.11 should install on systems with only 512M of ram. Cool! -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] Seeking OpenSolaris help for Fluendo
Brian Cameron writes: Perhaps you misunderstand how codeina works, or I misunderstand something. The codeina application autodetects when a user tries to play a file that can't be played due to a lack of a codec. If Fluendo offers a codec for sale that enables playing that format, it pops up a window. The window steps the user through purchasing the plugin (via a mozembed plugin accessing their webstore), then after purchase it downloads the package and installs the plugins for you. I think there might be some simple ways to do this. One would be to have the codeina install process itself save a file somewhere on the system (under /var might be good) indicating exactly what kind of package was used to install codeina itself, and where it was installed from. Each distribution format of codeina can install a different file indicating how and where to get more. You then use this at run time to determine how to get more packages. The assumption is that the mechanism used to install codeina is the same as the common one that the user wants for all packages, and that you can have slightly different data in each package format you distribute, generated as part of the packaging process. I think the worst way to solve this problem would be to condition the logic based on the platform. There's no obvious or reliable technical definition of platform (it's more of a marketing issue), nor does there appear to be a way to tie platform into anything about preferred installation method. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] /etc/release on Solaris Express
Andrew Wasilczuk writes: Thanks James, this makes sense. The software I'd like to patch is called facter[1], which I use with puppet[2] to automate the management of our freebsd servers. Now I'd like to use it with opensolaris. Facter basically returns facts about the operating system, such as the hostname, kernel version etc. The previous release worked fine, but since the new version they've added the operatingsystemrelease fact to solaris 10 (which uses /etc/release) and it broke on opensolaris because the formating is different. That sounds like a bug to file against 'facter' ... though there are complications here. One of the complications is that it's unclear what naming is being used for OpenSolaris. OpenSolaris (the source base) is still using the code-name Nevada bi-weekly build numbering system, which is a system that we use for marketing releases under development. It's the way we've developed Solaris effectively forever. That makes those builds unreleased or work in progress artifacts. That includes the Solaris Express builds. OpenSolaris (the distribution) has its own numbering system, but it's not yet an integrated project, so the state of it as a release is quite unclear to me. I suppose the 'facter' folks could discuss the issue with the OpenSolaris Indiana project team if they were interested in supporting it. There probably should be something available that can be tested. On my solaris 10 box the operatingsystemrelease fact returns 10_u5. I guess on opensolaris this should be set to snv_XX (which, I can take from uname so no problem). On Solaris 10 what's the best place to get the exact release from (including the update number) other than from /etc/release? The release is `uname -r`. Updates are *not* distinct releases in that sense, because they are all part of one patch train. In particular, it's possible to install some of the patches that are part of one Update without upgrading everything to the entire Update. What should the tool report in those cases? 10_u4.5? It might be possible to get the KJP information from `uname -v` ... but I suspect that whatever is depending on seeing the string 10_u5 is itself broken, and the right string should be 10 or (more properly) 5.10. In other words, I disagree with what they're doing. I don't have enough context to figure out a better solution, but I what you're reporting doesn't make sense to me. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] snv_99 jumpstart issue
Tom Albers writes: My jumpstart no longer works as of build snv_99. Build snv_98 works fine. Problem occurs on both SPARC and x64 architectures. Is there an existing CR and a workaround? It might be CR 6760873 ... but the bug system seems to be down. :- -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] /etc/release on Solaris Express
Andrew Wasilczuk writes: I'm patching a bit of software to work on opensolaris which uses /etc/release to get system information from. I've only got indiana installed here and I'm not sure how different /etc/release is on sxde. It would be nice to make it work on both. Could someone with sxde around please paste the contents of their /etc/release so that I can have a look at the formating? Or is it exactly the same as on indiana? Here's /etc/release from an OpenSolaris system: OpenSolaris 2008.11 snv_99 X86 Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 08 October 2008 and one from Solaris Express: Solaris Express Community Edition snv_101 X86 Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 20 October 2008 However, I'd say that if you're using the contents of /etc/release to make any automated decisions, then you're pretty much on your own. Those aren't in any way stable interfaces -- we don't commit to any sort of stability in the text contained in that file, or the even the formatting of the text, other than to say that it should be readable by a human who understands English. If we wanted to change these four lines to read: Sorry We Broke You ... there'd be no real impediment to doing it. ;-} I recommend using something else to perform whatever test it is that you're performing -- or find a way to avoid the test entirely. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] /etc/release on Solaris Express
Ian Collins writes: James Carlson wrote: If we wanted to change these four lines to read: Sorry We Broke You ... there'd be no real impediment to doing it. ;-} Is Sun relocating to Redmond? :) No. I'm just trying to make it really clear that this file was intended for human eyes. If you're scripting around it, you've wandered off the reservation. You may get hurt, and it's not necessarily the case that anyone will notice ... or come to your rescue. It's like parsing the contents of man pages. It might work ... but probably not for long. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] [OT] was Re: The future of the IPS system
Martin Bochnig writes: Also: I'm not talking about getting famous like Madonna. It would be very nice already, if _certain_ folks would stop throwing fish at me. Or better: If the community would protect me from experiences like that. I doubt that having others choose a different packaging system (whether that's RPM in Nexenta, SysV in SX, IPS in OpenSolaris) necessarily hinders someone else from choosing yet another packaging system. Except for a user fan base, I see no obvious competition between these systems. If it's good and people want it, it'll stand on its own merits. If it's not, it won't. That goes for IPS as well as it does for Conary or anything else. A more interesting question for this group, I think, is what requirements need to put onto the projects delivering into OpenSolaris consolidations so that those systems can work. Right now, I think we have a possibly unstable situation: the source isn't just 'source,' it also (naturally) includes packaging information. That information is in SysV format, which (through scripting) has flexibility that other systems (such as IPS) don't have, so accomodating those downstream consumers (distribution constructors) is an issue. Do we restrict projects to the least common denominator? Somehow abstract packaging away? Select one mechanism as reference and convert everything over? We probably need something like an OpenSolaris-wide policy here. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] sun qfe card
Steve Szabo writes: I recently built a new peecee with the intention of running Solaris 10. It seems that Solaris 10 x86 does not include support for the Sun Quad Fast ethernet card. Is this card supported under OpenSolaris or any of the variants? Neither hme nor qfe (same hardware, different package) are supported on x86 yet. These two are CRs 6342827 and 6401215. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] crontab
Bill Shannon writes: I'm just asking about monitoring the messages file. I'm researching it by asking here. My budget is $0. I'm hoping there's an obvious solution that's part of OpenSolaris. I found System Log Viewer, although it gives lots of error messages when started up. I guess that's the right answer once it works. Unfortunately, the bulk of messages that show up in the system log files are not in any sense stable. There's little that those programs can rely on that we can't (or won't) change without notice, even in a patch. With rare exceptions, changes to those messages go through no review at all. The only standard is that the output is supposed to be legible to an English-speaking human (i18n doesn't apply for debug logs), or at least to a system administrator. That doesn't mean that people don't try to parse them automatically anyway. There are several log-scraping 'solutions' out there, both free and from commercial sources. A common one is called Sawmill. The right answer to this sort of problem is a structured, stable, and documented facility, such as FMA or SNMP. Getting the right answer though costs far more than getting an expedient and fragile one. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] crontab
Bill Shannon writes: In the olden days I could start up a console window that would display all the messages logged to the console. Now the messages just go into the log file. You can still do that. I usually crank up something like this to watch for log messages that would have gone to the system console: /usr/X11/bin/xterm -C -e /usr/bin/sleep 864000 -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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] ISC DHCPD problem (3.1.1 version).
Miguel Da Silva - URI writes: svc-cswdhcp: Executing: /opt/csw/sbin/dhcpd -d -cf /opt/csw/etc/dhcpd.conf I'm no ISC DHCP expert (I currently use the Solaris one), but the above looks like a mistake to me. The '-d' option enables debug *and* forces the daemon to run in the foreground. That's unlikely to be what you want. It'll block the SMF start method from completing, and when that times out, it'll go into maintenance state. Remove the '-d' (just use syslog for debugging) and you should be fine. -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.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
