Re: [osol-discuss] OT: Re: Oracle 10g on OpenSolaris (Solaris 5.11)
On Mon, Aug 17, 2009 at 12:51 AM, Peter Tribble wrote: > On Fri, Aug 14, 2009 at 6:26 PM, Glenn Lagasse wrote: >> * casper@sun.com (casper@sun.com) wrote: > And the pendulum has swung way too far. Ermm.. excuse my ignorance or gmail mangling up this thread but... what does this have to do with Oracle 10g? I have about 20 emails in this thread and i was kinda hoping someone would ask how to install Oracle 10g on Solaris 5.11 and someone else would answer but all I see mentioned is what should be possible on the OS install time and what should not be... Anyway, just my two cents about installing 100s of servers without interaction, isnt that why there are things like Jumpstart and other fancy tools, I don't see the fuzz really... Or I am just tired, that's also possible. Anyway, if a way to install Oracle was mentioned in this thread, feel free to copy/paste me that off-list cause I seriously can't find it and I'd be very interested in knowing how to get that working cause I don't think it's officialy supported by Oracle and I don't think it will be... Cheers, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] strange root zpool DEGRADED at boot
Hi Dennis, I had happening the same on my Ultra-2 last week and asked one of the coworkers. Apparently this can happen when the SCSI disks take too long to respond to certain syscalls done by the operating system. I am still trying to find out the whats and whys regarding this... -- Patrick On Wed, Nov 26, 2008 at 5:41 PM, Dennis Clarke <[EMAIL PROTECTED]> wrote: > > This happens every time and I need to check this out on SXCE and then > Solaris 10 10/08 again to see if the issue is really hardware in some way. > > Here is what happens at every boot of this Sparc machine : > > 1) given four SCSI disks on three SCSI ports ( two controllers ) > > lom>poweron > lom> > LOM event: power on > > Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard > OpenBoot 3.10.27 ME, 1024 MB memory installed, Serial #12731976. > Ethernet address 8:0:20:c2:46:48, Host ID: 80c24648. > > > > > ok probe-scsi-all > /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 > Target 2 > Unit 0 Disk SEAGATE ST373307LSUN72G 0507 > > /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] > Target 3 > Unit 0 Disk FUJITSU MAT3073N SUN72G 0602 > > /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED] > Target 0 > Unit 0 Disk SEAGATE ST373307LSUN72G 0507 > Target 1 > Unit 0 Disk SEAGATE ST373307LSUN72G 0507 > > So four more or less identical Sun OEM disks. > > ok boot > Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL > PROTECTED]/[EMAIL PROTECTED],0:a File and args: > SunOS Release 5.10 Version Generic_137137-09 64-bit > Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: add_spec: No major number for fp > Hostname: core > Reading ZFS config: done. > Mounting ZFS filesystems: (5/5) > > core console login: root > Password: > Nov 26 16:35:22 core login: ROOT LOGIN /dev/console > Last login: Wed Nov 26 03:52:36 on console > Sun Microsystems Inc. SunOS 5.10 Generic January 2005 > # zpool status -x > pool: s10s > state: DEGRADED > status: One or more devices could not be opened. Sufficient replicas > exist for >the pool to continue functioning in a degraded state. > action: Attach the missing device and online it using 'zpool online'. > see: http://www.sun.com/msg/ZFS-8000-2Q > scrub: none requested > config: > >NAME STATE READ WRITE CKSUM >s10s DEGRADED 0 0 0 > mirror DEGRADED 0 0 0 >c0t0d0s0 ONLINE 0 0 0 >c0t1d0s0 ONLINE 0 0 0 >c1t3d0s0 UNAVAIL 0 0 0 cannot open >c2t2d0s0 UNAVAIL 0 0 0 cannot open > > errors: No known data errors > > Weird .. is there a driver or kernel module not loaded ? > Let's see what happens when I bring that disk online : > > # modinfo > /tmp/modinfo.1 > # zpool online s10s c1t3d0s0 > # zpool status -x > all pools are healthy > # zpool status s10s > pool: s10s > state: ONLINE > scrub: resilver completed after 0h0m with 0 errors on Wed Nov 26 16:36:48 > 2008 > config: > >NAME STATE READ WRITE CKSUM >s10s ONLINE 0 0 0 > mirror ONLINE 0 0 0 >c0t0d0s0 ONLINE 0 0 0 >c0t1d0s0 ONLINE 0 0 0 >c1t3d0s0 ONLINE 0 0 0 >c2t2d0s0 ONLINE 0 0 0 > > errors: No known data errors > # modinfo > /tmp/modinfo.2 > > Did some device driver get loaded ? > > # diff /tmp/modinfo.1 /tmp/modinfo.2 > > No change there. > > Everything runs fine other than this. I should point out that this is a > minimal or networked reduced core install system with only 121 packages > reported by pkginfo. > > I have done this sort of thing with SXCE SNV_81 with great success and had > ZFS with zones and resource caps in place etc and it all works on a very > very small footprint. I am trying to do the same thing with Sol10u6 and > SXCE SNV_101 but got stopped in my tracks with this on S10u6 thus far. Is > this a well know bug or is something funky at play here ? > > -- > Dennis Clarke > > ps: before anyone tears a strip off me for posting about s10u6 I can > assure you that the next step after getting this config locked down was to > reproduce it with SXCE. > > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] vmware/prstat/mpstat question
Hi, Quick question for you all. When I run mpstat/prstat/vmstat in a zone, is it actually outputting the statistics in regards of running queue, CPU usage and all of that particular zone only? I ask this cause I am trying to find out why one of our applications is behaving poorly but the figures returned seem to be a bit off or at least worrying for us if the statistics are really just from this zone... -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] unix file encryption
On Thu, Oct 2, 2008 at 3:25 PM, Cj <[EMAIL PROTECTED]> wrote: > Is there a way to encrypt a flat file or a database file so it can be ftp or > sftp to a remote windows system? > > this is for solaris/AIX etc. > > or is there a 3 party sw that can be used? PGP? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Installation OpenSolaris and Windows vista
On Wed, Sep 24, 2008 at 6:53 PM, Mark R. Bowyer <[EMAIL PROTECTED]> wrote: > Santiago Builes Palacio wrote: >> Hi, I tried to install OpenSolaris in a machine which has windows vista, >> but after about 65% of the installation that laptop restarts automatically >> without finishing the installation >> >> Any one knows the reason and how to repair it? Are you using the graphical installer? It might be worth using the motif installer, open a terminal and make a 'while true' loop that calls dmesg and 'sleep 1'. I had a similar problem and it constantly rebooted after an X percentage and I found out it was a kernel panic thrown due to my media being corrupted. -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE95 extremely unstable on x64 laptop
> > Can I see a stacktrace of this please ? > > Thx, > FrankH. And here is the ::stack output. I did my very best to reproduce the panics with the 32 bit kernel but no go (which is good for me I guess :P) unix.0 and vmcore.0 page_ctr_add_internal+0x11c(0, 3, ff0003bfffc8, 1) page_ctr_add+0x78(0, 3, ff0003bfffc8, 1) page_demote+0x28b(0, 7c200, 1, 0, 31, 2) page_freelist_split+0x184(0, 31, 0, 1, 0, ff0008b0e478) page_get_mnode_freelist+0x1ce(0, 31, 3, 0, 202000b) page_get_freelist+0x187(ff01d6e32c40, ff018b128000, ff01dff5a620, feb5c000, 1000, b) page_create_va+0x240(ff01d6e32c40, ff018b128000, 1000, 3, ff01dff5a620, feb5c000) swap_getapage+0xc1(ff01d6e32c40, ff018b128000, 1000, 0, ff0008b0e940, 1000) swap_getpage+0x99(ff01d6e32c40, ff018b128000, 1000, 0, ff0008b0e940, 1000) fop_getpage+0x9f(ff01d6e32c40, ff018b128000, 1000, 0, ff0008b0e940, 1000) anon_private+0x168(ff0008b0e9f8, ff01dff5a620, feb5c000, f, ff0003c11908, 0) segvn_faultpage+0x637(ff01d63fe020, ff01dff5a620, feb5c000, c000, 0, ff0008b0eb40) segvn_fault+0xaeb(ff01d63fe020, ff01dff5a620, feb5c000, 1000, 1, 2) as_fault+0x5ae(ff01d63fe020, ff01df5b9d58, feb5cb00, 1, 1, 2) pagefault+0x95(feb5cb00, 1, 2, 0) trap+0xbd3(ff0008b0ef10, feb5cb00, 0) 0xfb8001d9() unix.1 and vmcore.1 page_ctr_add_internal+0x11c(0, 3, ff0003bfffc8, 1) page_ctr_add+0x78(0, 3, ff0003bfffc8, 1) page_demote+0x28b(0, 7c200, 1, 0, 1f, 2) page_freelist_split+0x184(0, 1f, 0, 1, 0, ff0009440088) page_get_mnode_freelist+0x1ce(0, 1f, 3, 0, 202000b) page_get_freelist+0x187(ff01de3cde40, 213000, fbc2c840, ff01cab1d000, 1000, b) page_create_va+0x240(ff01de3cde40, 213000, 1000, 3, fbc2c840, ff01cab1d000) pvn_read_kluster+0x158(ff01de3cde40, 213000, fbc2c840, ff01cab1d000, ff0009440408, ff0009440410) pcfs_getapage+0x1ee(ff01de3cde40, 213000, 1000, ff000944070c, ff00094406a8, 2000) pcfs_getpage+0x119(ff01de3cde40, 213000, 1000, ff000944070c, ff00094406a8, 2000) fop_getpage+0x9f(ff01de3cde40, 213000, 1000, ff000944070c, ff00094406a8, 2000) segmap_fault+0x1dc(ff01cb28be78, fbc2c840, ff01cab1d000, 1000, 0, 1) as_fault+0x5ae(ff01cb28be78, fbc2a420, ff01cab1d000, 1, 0, 1) pagefault+0x200(ff01cab1d000, 0, 1, 1) trap+0x1263(ff00094409f0, ff01cab1d000, 1) 0xfb8001d9() kcopy+0x2c() uiomove+0xe5(ff01cab1c000, 2000, 0, ff0009440e20) rwpcp+0x4bf(ff01dde531c0, ff0009440e20, 0, 0) pcfs_read+0x7a(ff01de3cde40, ff0009440e20, 0, ff01d97820e8, 0) fop_read+0x69(ff01de3cde40, ff0009440e20, 0, ff01d97820e8, 0) read+0x28b(23, f541cb10, 1) read32+0x1e(23, f541cb10, 1) _sys_sysenter_post_swapgs+0x14b() unix.2 and vmcore.2 page_ctr_add_internal+0x11c(0, 3, ff0003bfffc8, 1) page_ctr_add+0x78(0, 3, ff0003bfffc8, 1) page_demote+0x28b(0, 7c200, 1, 0, 17, 2) page_freelist_split+0x184(0, 17, 0, 1, 0, ff0008b832c8) page_get_mnode_freelist+0x1ce(0, 17, 3, 0, 202004b) page_get_freelist+0x187(fbc2a720, ff00d9f55000, ff0008b83530, ff00d9f55000, 1000, 4b) page_create_va+0x240(fbc2a720, ff00d9f4e000, 2, 53, ff0008b83530, ff00d9f4e000) segkmem_page_create+0x8b(ff00d9f4e000, 2, 4, fbc2a720) segkmem_xalloc+0xbc(ff01cb254000, 0, 2, 4, 0, fb85ff90) segkmem_alloc_vn+0xcd(ff01cb254000, 2, 4, fbc2a720) segkmem_zio_alloc+0x20(ff01cb254000, 2, 4) vmem_xalloc+0x4fc(ff01cb255000, 2, 1000, 0, 0, 0) vmem_alloc+0x159(ff01cb255000, 2, 4) kmem_slab_create+0x7d(ff01cd48e5a0, 4) kmem_slab_alloc+0x57(ff01cd48e5a0, 4) kmem_cache_alloc+0x136(ff01cd48e5a0, 4) zio_data_buf_alloc+0x28(2) arc_get_data_buf+0x175(ff01dd1f4f78) arc_buf_alloc+0x9a(ff01cd028540, 2, ff01dd1f6838, 0) dbuf_read_impl+0x1a2(ff01dd1f6838, ff01dd13a840, ff0008b83b20) dbuf_read+0x1be(ff01dd1f6838, ff01dd13a840, a) dmu_tx_check_ioerr+0x70(ff01dd13a840, ff01dd164568, 0, 1c) dmu_tx_count_write+0xb2(ff01dace7878, 38, 1) dmu_tx_hold_write+0x57(ff01dc23e300, 7d3, 38, 1) zfs_write+0x373(ff01dd15ec00, ff0008b83e20, 0, ff01db75d030, 0) fop_write+0x69(ff01dd15ec00, ff0008b83e20, 0, ff01db75d030, 0) write+0x2af(23, f959db10, 1) write32+0x1e(23, f959db10, 1) _sys_sysenter_post_swapgs+0x14b() ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE95 extremely unstable on x64 laptop
On Mon, Aug 18, 2008 at 9:32 PM, Frank Hofmann <[EMAIL PROTECTED]> > Can I see a stacktrace of this please ? I have plenty, here goes the output of ::msgbuf in mdb :) unix.0 and vmcore.0: panic[cpu0]/thread=ff01d72e1b00: BAD TRAP: type=e (#pf Page fault) rp=ff0008b0e0f0 addr=ff000b9beb22 gvfsd: #pf Page fault Bad kernel fault at addr=0xff000b9beb22 pid=13313, pc=0xfb86aeec, sp=0xff0008b0e1e0, eflags=0x10207 cr0: 8005003b cr4: 6f8 cr2: ff000b9beb22 cr3: 13fd48000 cr8: c rdi: ff00079bb0f8 rsi:1 rdx:1 rcx:9 r8: ff00079be360 r9: 20003e1 rax:2 rbx: fbc43c90 rbp: ff0008b0e260 r10: fbc2a6a4 r11: ff50 r12: ff0003bfffc8 r13: fbc2a6a0 r14: fbc2a6b8 r15: fbc27b48 fsb:0 gsb: fbc2a7f0 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: fb86aeec cs: 30 rfl:10207 rsp: ff0008b0e1e0 ss:0 ff0008b0dfd0 unix:die+ea () ff0008b0e0e0 unix:trap+13b9 () ff0008b0e0f0 unix:cmntrap+e9 () ff0008b0e260 unix:page_ctr_add_internal+11c () ff0008b0e2c0 unix:page_ctr_add+78 () ff0008b0e370 unix:page_demote+28b () ff0008b0e430 unix:page_freelist_split+184 () ff0008b0e530 unix:page_get_mnode_freelist+1ce () ff0008b0e5f0 unix:page_get_freelist+187 () ff0008b0e6d0 unix:page_create_va+240 () ff0008b0e780 genunix:swap_getapage+c1 () ff0008b0e800 genunix:swap_getpage+99 () ff0008b0e8b0 genunix:fop_getpage+9f () ff0008b0e9a0 genunix:anon_private+168 () ff0008b0eab0 genunix:segvn_faultpage+637 () ff0008b0ec60 genunix:segvn_fault+aeb () ff0008b0ed70 genunix:as_fault+5ae () ff0008b0edf0 unix:pagefault+95 () ff0008b0ef00 unix:trap+bd3 () ff0008b0ef10 unix:cmntrap+e9 () syncing file systems... done dumping to /dev/zvol/dsk/nemesis/dump, offset 65536, content: kernel NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port unix.1 and vmcore.1 panic[cpu1]/thread=ff01dde24040: BAD TRAP: type=e (#pf Page fault) rp=ff000943fd00 addr=ff000b9beb22 nautilus: #pf Page fault Bad kernel fault at addr=0xff000b9beb22 pid=16891, pc=0xfb86aeec, sp=0xff000943fdf0, eflags=0x10207 cr0: 8005003b cr4: 6f8 cr2: ff000b9beb22 cr3: 139237000 cr8: c rdi: ff00079bb0f8 rsi:1 rdx:1 rcx:9 r8: ff00079be360 r9: 20003e1 rax:2 rbx: fbc43c90 rbp: ff000943fe70 r10: fbc2a6a4 r11: ff50 r12: ff0003bfffc8 r13: fbc2a6a0 r14: fbc2a6b8 r15: fbc27b48 fsb:0 gsb: ff01cfc6dac0 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: fb86aeec cs: 30 rfl:10207 rsp: ff000943fdf0 ss: 38 ff000943fbe0 unix:die+ea () ff000943fcf0 unix:trap+13b9 () ff000943fd00 unix:cmntrap+e9 () ff000943fe70 unix:page_ctr_add_internal+11c () ff000943fed0 unix:page_ctr_add+78 () ff000943ff80 unix:page_demote+28b () ff0009440040 unix:page_freelist_split+184 () ff0009440140 unix:page_get_mnode_freelist+1ce () ff0009440200 unix:page_get_freelist+187 () ff00094402e0 unix:page_create_va+240 () ff00094403a0 genunix:pvn_read_kluster+158 () ff00094404d0 pcfs:pcfs_getapage+1ee () ff0009440580 pcfs:pcfs_getpage+119 () ff0009440630 genunix:fop_getpage+9f () ff0009440740 genunix:segmap_fault+1dc () ff0009440850 genunix:as_fault+5ae () ff00094408d0 unix:pagefault+200 () ff00094409e0 unix:trap+1263 () ff00094409f0 unix:cmntrap+e9 () ff0009440b00 unix:kcopy+2c () ff0009440b70 genunix:uiomove+e5 () ff0009440c60 pcfs:rwpcp+4bf () ff0009440cd0 pcfs:pcfs_read+7a () ff0009440d40 genunix:fop_read+69 () ff0009440e90 genunix:read+28b () ff0009440ec0 genunix:read32+1e () ff0009440f10 unix:brand_sys_sysenter+1e6 () syncing file systems... done dumping to /dev/zvol/dsk/nemesis/dump, offset 65536, content: kernel NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port unix.2 and vmcore.2 panic[cpu1]/thread=ff01cfedbae0: BAD TRAP: type=e (#pf Page fault) rp=ff0008b82f40 addr=ff000b9beb22 nautilus: #pf Page fault Bad kernel fault at addr=0xff000b9beb22 pid=1024, pc=0xfb86b15c, sp=0xff0008b83030, eflags=0x10207 cr0: 8005003b cr4: 6f8 cr2: ff000b9beb22 cr3: 13a9f2000 cr8: c rdi: ff00079bb0f8 rsi:1 rdx:1 rcx:9 r8: ff00079be360 r
Re: [osol-discuss] SXCE95 extremely unstable on x64 laptop
On Mon, Aug 18, 2008 at 10:54 AM, Ghee Teo <[EMAIL PROTECTED]> wrote: > Patrick Ale wrote: >> >> Hi, >> >> I get random kernel panics when running SXCE 95 with the 64 bit >> kernel. The panics seem to have to do with reads/writes to disk. >> I can reproduce the panics every time I try to copy things from/to my >> USB stick or when I insert my USB wifi stick which is driven by the >> SUNWrum driver (which writes lts to /var/adm/messages). >> > > What file system have you on the USB? I have seen a FAT32 share filesystem > causes > kernel crashing when copy data to it on an earlier version. I tried ext2fs and FAT32 on my USB stick. But also downloading from sun download center directly to my ZFS pool or UFS filesystem causes panics, again, only with the 64 bit kernel loaded. -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE95 extremely unstable on x64 laptop
On Sun, Aug 17, 2008 at 10:05 PM, Orvar Korvar <[EMAIL PROTECTED]> wrote: > I have several problems with b95. The internet dies and it stops responding > to my actions. etc. b93(?) was fine, and after that, everything gets worse > and worse. I just found out the problems I mentioned are also reproducable in b96. -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SXCE95 extremely unstable on x64 laptop
Hi, I get random kernel panics when running SXCE 95 with the 64 bit kernel. The panics seem to have to do with reads/writes to disk. I can reproduce the panics every time I try to copy things from/to my USB stick or when I insert my USB wifi stick which is driven by the SUNWrum driver (which writes lts to /var/adm/messages). When I boot the 32 bit kernel, the panics disappear. It's an Acer Aspire 8920 laptop with 4GB of memory. Anyone else who has similar problems? I already filed a bug report, I just didnt get the number back yet. -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
On Mon, Aug 11, 2008 at 1:38 AM, Mike Meyer <[EMAIL PROTECTED]> wrote: > On Sun, 10 Aug 2008 22:48:08 +0200 > > Ah, the solaris community is just *full* of flashbacks. Chasing down > and installing the dependencies for a package by hand? Something I > thought I'd seen the last of in 1998. I am not saying which is better, I am just saying the dependencies are there for giving full facts in the discussion's sake :) Both Sunfreeware and CSW have pros and cons, just use what you feel more comfortable with, I am really too busy for a sunfreeware vs CSW vs the world flame bate -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
On Sun, Aug 10, 2008 at 4:30 PM, UNIX admin <[EMAIL PROTECTED]> wrote: >> There were enough problems with how the stuff from >> blastwave/csw was packaged to make it distasteful to >> use, this simply puts the last nail in the coffin. >> For the most part I build everything from the source, >> for those that I don't really want to take the time >> to build I'll go to www.sunfreeware.com > > Heh! > > Anybody with an insane idea of still "packaging" stuff into /usr/local and > not declaring dependencies obviously doesn't fully understand what they are > doing. But of course you've read the text provided with the hyperlink that states the dependencies eh? ;-) To be honest with you I use both CSW and sunfreeware at times. CSW when I need something really really quick and dont care too much for the bloatware dependencies installed, sunfreeware when I have a bit more time to spend on what I need, and sources when I want to make myself unmissable at work ;-) -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] genunix.org Top Level Domain records
On Thu, Aug 7, 2008 at 6:37 PM, Al Hopper <[EMAIL PROTECTED]> wrote: > > I'll let whoever made those changes apologize to the user community > for the inconvenience and disruption these changes have caused the > OpenSolaris user communities. Doesn't it have to do with the message that's readable on the blastwave site? I saw it this morning actually when trying to install CSW. I quote All websites, documents and binary software packages that bear the mark Blastwave or Blastwave(tm) are no longer available until further notice. Websites or domains include but are not limited to : blastware.net blastware.org blastware.ca blastwave.org blastwave.net blastwave.ca blastwave.biz blastwave.com blastwave.info genunix.biz genunix.com genunix.info genunix.net genunix.org genunix.us genunix.ca old-sparc.com old-sparc.net old-sparc.org oldsparc.com oldsparc.net oldsparc.org openfor.info openfor.org opn4.biz opn4.com opn4.info opn4.net opn4.org end quote. -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Very poor performance BM5787
On Tue, May 6, 2008 at 11:35 AM, Patrick Ale <[EMAIL PROTECTED]> wrote: > Hi, > > I have a Compaq 6710b laptop with the BM5787 mobile gigabit network cad. > All nevada builds give very poor performance, network wise. SCP > sessions stall, sites take two minutes to open, etc. This seems solved in the 'current' BFU archives! :) Everything runs as I'd expect it to run ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Very poor performance BM5787
Hi, I have a Compaq 6710b laptop with the BM5787 mobile gigabit network cad. All nevada builds give very poor performance, network wise. SCP sessions stall, sites take two minutes to open, etc. Under Solaris 10u4 I had the same problem with the bge driver, which I fixed by installing the BCME driver from the broadcom site, but this driver doesn't seem to work under opensolaris (it gives softmac errors). In my syslog I see the following messages thrown every 1 second: May 6 11:30:19 laptop-upc syseventconfd[1037]: [ID 898775 daemon.error] process 1039 exited with status 5 May 6 11:30:19 laptop-upc rcm_daemon[1044]: [ID 988102 daemon.error] IP: Device consumers prohibit offline(bge0) As as I stop the network traffic, the errors disapear. Is anyone else having this problem and is there a work around? I am using b88 at the moment. -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] IP: Device consumers prohibit offline(bge0)
Hello all, Any of you an idea what the following message means and why I see it every couple of seconds in my syslog? Feb 6 13:42:24 nlws481093 rcm_daemon[823]: [ID 988102 daemon.error] IP: Device consumers prohibit offline(bge0). This is on my HP/Compaq 6710b with the following Broadcom ethernet card: pci bus 0x0018 cardnum 0x00 function 0x00: vendor 0x14e4 device 0x1693 Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express Cheers, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [ogb-discuss] STAR integration
On Dec 20, 2007 9:09 PM, Neal Pollack <[EMAIL PROTECTED]> wrote: > Joep Vesseur wrote: > > >> Could you please explain this to Casper Dik? There is nothing to explain to Casper. He grasped the picture from second one. He even explained what was going on. Someone else was first to use /usr/bin/compare and he didn't see why it should be renamed. (Thank you google webmail for threading my mails). > >> He did start this thread and if you like to filter someone, you would need > >> to filter Casper... Actually you started the thread with accusing Sun ignoring PSARC on which Casper merely responded but hey.. matter of perception probably. > > > > > hmm, all sounds a lot like politics rather than psarc business. > This is easily understood in over 9 languages, as > the root "poly" means many, and "tics" are voracious > blood sucking creatures. I totally agree with this guy. I already replied after the 44th mail or so that people should get over themselfs and should worry about real issues in life. I let in the middle who is wrong or did what. I guess most of things can be explained by language boundaries or misinterpretation of emails. One thing is for sure. These kind of emails don't help the community and may look this mailling list like a bunch of negative nancy's who should go out more. > > > Thanks for your cooperation. "Goodbye" (yes, I did watch Robocop 1 to much) > > Joep Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any info on what holds b78 and b79 ?
On Dec 20, 2007 2:27 PM, Robert <[EMAIL PROTECTED]> wrote: > Alan, > > An announcement should be updated accordingly if an change is made and not > become 'buried' in the discussion forum since this is indeed an announcement > of an delay. > > But that's my €0.09. We're all aware that there are no SLAs or platinum contracts involved with these builds right? Last time I checked this was all community driven work and all. Besides, you can have build 80 already if you care enough. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Nameclash on svn_77 because Sun is ignoring PSARC discussions
On Dec 14, 2007 7:44 PM, Nicolas Williams <[EMAIL PROTECTED]> wrote: > I'm not sure that we can come up with such a method that will: a) allow > OpenSolaris to evolve and grow, while b) preventing any conflicts with > Linux distros (and *BSDs) that are also growing and evolving at > different rates. But it may be worthwhile to try. What are you all discussing anyway? /usr/bin/compare is in use, big ffing deal. Call it scompare (s from shilling obviously) like we see with star and what not. Get over yourselfs, really. I am sure you all have more important things to do. Sorry for my bluntness but this is both silly and frustrating looking at the work that still has/should be done. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How do I update my bugreport?
On Dec 11, 2007 4:59 PM, Alan Coopersmith <[EMAIL PROTECTED]> wrote: > > Patrick Ale wrote: > > Hi guys, Hi Alan! Well I know who's working on the case, it's Brian. I have his email address and he is helping me a lot a already, James gave me some pointers as well. Thank you all :) Patrick / WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How do I update my bugreport?
On Dec 11, 2007 2:04 PM, James Carlson <[EMAIL PROTECTED]> wrote: > > > > > > I found four bugs that appear to be from you; none are in "incomplete" > state. > > 6594586 root slice not within 1024 cylinders (SATA) > 6628352 libexpat.so.1 is missing after BFU to nv_76 > 6628353 Make libraries reside in the same directory > 6639117 JDS only starts with xVM kernel > Hi James! It's CR 6639382. JDS Soundsystem not working properly. Even though I got the answer yesterday per this mailing list I'd like to update the bugreport per request of the engineer. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How do I update my bugreport?
On Dec 11, 2007 11:49 AM, Ché Kristo <[EMAIL PROTECTED]> wrote: > > Was the bug filed through http://bugs.opensolaris.org/ or Bugzilla? > Hi Ché , It was filed at bugs.opensolaris.org :) Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] How do I update my bugreport?
Hi guys, I filed a bug last week, I got an email yesterday saying the bug has changed status to incomplete and if I could please give more information acording to the filled in fields by the engineer working on the bug. I'd love to do that but... how do I do this? I can't even find my bug back in the database :s Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sound problems in SXCE77?
On 12/10/07, Patrick Ale <[EMAIL PROTECTED]> wrote: > > > > On 12/10/07, Brian Cameron <[EMAIL PROTECTED]> wrote: > > > > Patrick: > > > > > This is a regression then, in my opinion. Prior to SXCE77 I never had > > to > > > rebuild anything. > > > [snip] > > Hi Brian :) > > And again, hi :P So, checking out the repository again as we speak, and I can confirm something did go wrong yesterday. Right now I see spec files in the 'top' directory of my svn checkout, something I didn't see yesterday. Yesterday I only saw spec files inside directories residing in the 'top' directory. I'll let you know how things go when I am done building. Cheers, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sound problems in SXCE77?
On 12/10/07, Brian Cameron <[EMAIL PROTECTED]> wrote: > > Patrick: > > > This is a regression then, in my opinion. Prior to SXCE77 I never had to > > rebuild anything. [snip] Hi Brian :) As far as I can tell I am using the same OSS modules 4.00, but I am not sure about the minor release version so I'll assume this version is different then. Regarding building JDS, what you describe looks exactly like what I tried yesterday evening, with the addition that I did a pkgtool uninstall-pkgs *.spec in the base-spec directory after checking out the svn repository. I dunno, maybe something went horribly wrong during the checkout which rendered me with a local repository I shouldn't have, I am gonna retry it as we speak :) Thanks for your explanations and time, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sound problems in SXCE77?
On Dec 10, 2007 7:17 PM, Brian Cameron <[EMAIL PROTECTED]> wrote: > Patrick: > > Note that for GNOME/GStreamer to work best with OSS, you need to rebuild > the SUNWgnome-audio* and SUNWgnome-media* packages after installing the > OSS packages. To do this you should use the CBE, which you can get > from the OpenSolaris website: > This is a regression then, in my opinion. Prior to SXCE77 I never had to rebuild anything. Not to mention that jds doesn't build from source due to all kind of errors in the spec files (invalid boolean errors from the top of my head) and the documentation not being confirming the 'real world'. (During svn checkout you get spec files in directories like exta,base-specs,closed where the documentation tells you to do pkgtool build -v *.spec). Cheers, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Sound problems in SXCE77?
Hi guys and girls, Just wondering, is anyone experiencing sound problems under SXCE77 where they didn't before? I have an Intel HDAUDIO chipset in my laptop. I installed the oss drivers from opensound.com (as I always do), osstest spews out sound but things like Rhythmbox or the volume control tell me the correct gstreamer plugins or sounddevice arent installed. Does anyone here recognize this behaviour? Cheers, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
> > > > I didn't see it mentioned in this thread so I assume it wasn't done > already. I filed a bug five minutes ago regarding my current experience with > a clean SXCE76 build. Let's see what comes out ;-) > > Patrick > I just downloaded SXCE77 and did a fresh install on the same laptop mentioned in this thread. The problem is not reproducable under SXCE77. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
On Dec 7, 2007 2:44 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > Or please guide me a right mailing list to ask. > Let's make things even cooler and weirder shall we? Yesterday at NLOSUG we all got the SXCE 76 build on DVD (thanks for the cool evening by the way, I know for sure Casper is on this list). So, I installed the DVD on my laptop (HP Pavilion dv8000 series with Nvidia Go 5600. Installation went and directly after this the weirdness started. 1) When I choose option 1 (Solaris Express community edition build 76) the system boots, I see X being loaded, I see the nvidia logo and then the root window, as if I started Xorg by typing /usr/X11/bin/X. 2) When I choose the xVM option from grub, my system works like a charm, I can log in to JDS, the whole lot. In my opinion this means my hardware is fine and functional and that this is really something within this build that doesn't play nice. As always, if I can help debug, let me know, just give me a hint or two of what commands I should try. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
On Dec 7, 2007 8:15 PM, Patrick Ale <[EMAIL PROTECTED]> wrote: > > > On Dec 7, 2007 2:44 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > > > Or please guide me a right mailing list to ask. > > > > I didn't see it mentioned in this thread so I assume it wasn't done already. I filed a bug five minutes ago regarding my current experience with a clean SXCE76 build. Let's see what comes out ;-) Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] "Indiana" review
On Dec 3, 2007 4:11 PM, UNIX admin <[EMAIL PROTECTED]> wrote: > > Sorry, but most shops wouldn't even know where to begin with ACLs, not to > mention most shops don't even know they exist in UNIX. I happen to know > about them and how to use them, but I'm a rare and dying breed these days. This is why Sun offers kick ass courses where you can learn this stuff. ACLs are handy, might take some time to get a long with them but once you do, you love them. Basic ACLs were being discussed in.. dunno, Fundamentals for Solaris 8 if i recall correctly. > > > ZFS did break the traditional UNIX interfacing with UNIX utilities, as did > SMF, and don't you think for one nanosecond that it doesn't bother me! Why does it bother you exactly? > But would it kill you guys to just once, admit you overcomplicated it and > overengineered it? Just once? You screwed up with the RBAC implementation, > just come out clean and admit it, and life goes on. Nobody will kill you for > it, people make mistakes. > > In my opinion they didn't screw up anything. They added some stuff that can make your life possibly easier. If you don't know how to implement it or use it in an intended way then they didn't screw up.. you just have to do some research. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] "Indiana" review
On Dec 2, 2007 7:03 PM, Patrick Ale <[EMAIL PROTECTED]> wrote: Is Sun even sure it's self what will do what and what will replace what? I just get an email from somebody of this list saying Indiana will replace SXCE and will be the basis for Solaris 11. Which is ff-ing funny since people who work at Sun (and highly placed functions) assured me less than four weeks ago that SXCE would stay around, that they needed the community to do what they are doing now and how they cant do things with out them and that SXCE would be the basis for Solaris 11 and Indiana was merrely a product derived from SXCE. If Indiana is going to substitute SXCE, then I'd be very very bitter, so to say. Not only cause it'd mean heaps of people working on SXCE who worked their ass of to make a stable product with features we should all cheer about have been being used to make a Linux-like distro but also (from what I can read on fora and IRC0 what they stand for is totally voided by this decision. Again, if it's true that Indiana will replace SXCE. MEH. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] "Indiana" review
On Dec 2, 2007 6:30 PM, W. Wayne Liauh <[EMAIL PROTECTED]> wrote: > "Broken, Broken, Broken, Broken, . . . ." > > Now I know why I am so compellingly addicted to Solaris. Kudos Sun's > management for their willingness to take such bold actions, undoubtedly > accompanied by tons of well-oxidized midnight oil, that will finally take > Solaris to world dominance, or even world ubiquitance. > > Maybe I am a bit the devil's advocate here and I never bothered with Indiana to start with but... Indiana is not Solaris or THE SXCE binary outcome (hence the long lasting discussions that were around when people made more or less the statement that Indiana was "the" binary distribution outcome derived from the Opensolaris community work)..Therefor whatever you'd expect to work in SXCE or Solaris 10 or future 11 and isn't working in Indiana doesn't have to get the stamp 'broken'. It's only broken if the result is different from what you should expect of Indiana. In my opinion it has been made very loud and clear that the packaging system of Indiana is different from that of SXCE and Solaris. Or maybe I should do more about life and less about IRC and fora. As for scripts, it has been wildely established as well that PATHs and directories where binaries reside is a bit off from what you can expect from a Solaris binary distribution or SXCE. So yes, if you want everything to work as in your binary Solaris distribution and/or SXCE, stick with them. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 19, 2007 12:05 PM, Patrick Ale <[EMAIL PROTECTED]> wrote: > On Nov 19, 2007 11:56 AM, Patrick Ale <[EMAIL PROTECTED]> wrote: > > On Nov 19, 2007 11:50 AM, UNIX admin <[EMAIL PROTECTED]> wrote: > > > > > > > > I read it right there on the Solaris 10 manual page, the relevant > > > excerpts which I quoted in my posts for reference. It says that in the > > > man pages for both cfgadm_scsi(1M) and cfgadm_sata(1M) > > Dude... > > For starters, a Netra uses SCSI, not SATA. > Secondly, I'll quite the man page I didn't quite the manpage of course, that'd be cruel, mean and very unpolite. I quoted it :P Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 19, 2007 11:56 AM, Patrick Ale <[EMAIL PROTECTED]> wrote: > On Nov 19, 2007 11:50 AM, UNIX admin <[EMAIL PROTECTED]> wrote: > > > > > I read it right there on the Solaris 10 manual page, the relevant excerpts > > which I quoted in my posts for reference. It says that in the man pages for > > both cfgadm_scsi(1M) and cfgadm_sata(1M) Dude... For starters, a Netra uses SCSI, not SATA. Secondly, I'll quite the man page " The disconnect (quiesce) operation is not supported on con- trollers which control disks containing critical partitions such as root (/), /usr, swap, or /var. The disconnect opera- tion should not be attempted on such controllers. Incorrect usage can result in a system hang and require a reboot." Which is quite usefull, if you'd do a cfgadm -c disconnect, which if you read the emails, we dont. We do a cfgadm - c unconfigure. So, to dclarke: You can hotswap your Netra disks, just follow the disk removal procedures, people who I strongly believe about they know what they are talking about verify this. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 19, 2007 11:50 AM, UNIX admin <[EMAIL PROTECTED]> wrote: > > I read it right there on the Solaris 10 manual page, the relevant excerpts > which I quoted in my posts for reference. It says that in the man pages for > both cfgadm_scsi(1M) and cfgadm_sata(1M). > > Perhaps it's a documentation bug, however given that it shows up explicitily > and twice in two separare manual pages makes me doubt it's a bug or a > documentation > oversight. I dunno... it makes me wonder why they design a server where you can hotswap disks but you can't ever use it cause you'll have to shutdown the system anyway. Is there somebody from Sun who could shred a light on this? ;-) Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 19, 2007 11:20 AM, UNIX admin <[EMAIL PROTECTED]> wrote: > - if SVM is used, metadevices in question must be `metadetach`ed, and any > meta databases on these metadevices destroyed > - the metadevice(s) in question must not house /, /usr or swap on them > - the controller must be capable of hot remove/hot plug support > - the operating system must be notified which action will be taken, prior to > actually performing the action > - the port(s) must support hot remove/hot plug operations. Yes, so a Netra, as dclake pointed out he's using or what i was discussing doesn't have to be in a cluster and does not require failover to another node for disk replacement. There are advantages of using a cluster but they're not needed for disk replacement on a Netra.. for other non-hotswap systems your point of having a cluster is valid, but then again, one might argue that if they don't spend 5K euro on a Netra with hotswap capabilities they won't spend 3K on a Sun cluster validation and/or Sun Cluster support contract either. So basicly the comments about running 'cfgadm -c unconfigure' in one of the first emails plus the comments from nachox were already establishing what you say. About the "> - the metadevice(s) in question must not house /, /usr or swap on them", I don't know where you read that but this is again in contradiction with my experience and what Sun engineers tell me and how they handle our systems. A Netra v240 only has two internal bays. We slice c1t0d0 into /, swap, /var, /opt and /metadb (last one is used for metadb later) and we have no problems whatsoever with replacing one of the internal disks. Where did you read this statement exactly? A Sun authentic resource? Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 19, 2007 9:57 AM, UNIX admin <[EMAIL PROTECTED]> wrote: > That's the plan, at least. I will be working on completely automating such a > cluster deployment, which, once I'm finished, should only take two `pkgadd` > commands; after that, things will just automagically work, period. It was always my understanding that you buy a 5K euro Netra for the hotswap possibilities and the high availability of the server. I have never ever have heard of having to shutdow a Netra to remove one of internal disks from it's bays. Neither did any Sun engineer in the datacenter ever shut down a Netra for disk removal, and they are over the floor quite some times since we have platinum contracts for most of our important servers and aren't supposed to replace disks ourselfs on those servers. Even the PSUs at the back can be taken out while the system is live. About the cfgadm. I believe it only shows stuff for 'SCSI driven' hardware. It was always my understanding that an Ultra 5 had IDE disks but that they were addressed as SCSI, I am not sure on this one though. On my AMD 4400+ I see the same output as you see on your i86pc system. Which I find quite logical. All my drives are ATA/SATA and not even hotplugable. I only see my USB and Firewire hosts, which are hotplugable. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 18, 2007 11:07 PM, Ignacio Marambio Catán <[EMAIL PROTECTED]> wrote: > > > > sun's manuals actually say you must run cfgadm Which makes a very good point that 'habbits' vs reading manuals should be in favor of reading manuals. Something I admittedly don't do enough. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hot Plug sub-mirrors ?
On Nov 18, 2007 10:47 PM, Dennis Clarke <[EMAIL PROTECTED]> wrote: > > This is one of those "oh I never knew that but wish I did topics" so I > figured I would make it into a thread and then see what we can learn from > each other. > > I'll tell ya, I have had no fun with dealing with a machine that is Netra > class gear ( bullet proof ) which generally runs forever and ever but when I > yanked that disk ... boom. And well, what can I tell you, the look on my > face said it all and "oops" was not the word that sprang out of my mouth at > the moment the dreaded "ok" prompt appeared. At these times I am happy I know how to say a word or two in portuguese and croatian, and my coworkers do not :P > > I was always of the opinion that I could metadetach those failed sub-mirrors > and then clear out any metadatabase's that may be on the physical devices .. > then yank the disk because .. after all that there is no reason for there to > be any IO right ? Same here, I metadetached, cleared the state databases, and removed the disk. And never had any problems doing so. If it wasn't for the engineer telling me to do a cfgadm -c unconfigure I prolly wouldn't ever have done it, which might have lead to where you were now.. I am not trying to make it a fact you should use cfgadm, I am just parroting what I got told from a Sun engineer. I hope it will help people in the future anyway so they won't have to learn foreign languages to express them selfs when things go wrong. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave down?
On Nov 18, 2007 8:14 PM, UNIX admin <[EMAIL PROTECTED]> wrote: [ sni sna snappie ] > Depending on your storage HW, you have to still run some sort of SCSI quiesce > equivalent on the device you plan to hot remove and hot plug. > As a funny coincidence I talked about this 'hotplug' saga with a Sun engineer who was onside with us two weeks ago. I always used to just unlock the handle of the disk on a Netra v240/Fire V440, let it spin down, and then pull out the disk, and put the new one in. Apparently you should always and always use 'cfgadm -c unconfigure' or things might go bad. (wait till the disk status led on the front turns blue). His theory was that the hardware is hotpluggable but the OS sometimes doesn't play nice with hotplug. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where to report compiling issues
On 9/30/07, UNIX admin <[EMAIL PROTECTED]> wrote: > Did you compile with any optimization switches? Nope, I used the same environmental file I use since compiling onnv_69, the only addition was __SSNEXT=""; export __SSNEXT to get it compiling with Sun Studio 12. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where to report compiling issues
On 9/28/07, Shawn Walker <[EMAIL PROTECTED]> wrote: > The discuss list is valid for all OpenSolaris related topics. However, > opensolaris-code might be best... Thanks Shawn, Okay so, to keep it short, simple and interesting for everybody here: DO *NOT* use Sun Studio 12 to compile onnv_74 , it's gonna make you cry. I did it just to see what would happen for learning/knowledge purposes and the compile *will* work, you *will* be able to bfu, your machine *will* come up nicely and all. But when you try to start any service (like apache2, mysql) it'll segfault horribly. This is done on an AMD 4400+ (64 Bit) Consider yourself advised :) Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Where to report compiling issues
Hey all, Trying to avoid another "what to discuss here and not" thread a quick and simple question: Where can I report problems/experiences regarding ONNV gate compiles? Thankies, Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE 70's installer and laying out file systems
On 8/20/07, Dave Miner <[EMAIL PROTECTED]> wrote: > You can have the discussion here if that's what floats your boat, but > you can also be certain that most of the people you'd like to have the > discussion with will *not* be participating in it because they've got > better things to do than wade through the general morass of other > mis-directed or otherwise pointless discussions which occur here, so > you're just barely beyond talking to yourself in terms of effecting > change. If you want to have a discussion about installation, then > you'll do a lot better to have it on install-discuss (or caiman-discuss, > if it's specific to the behavior of the new installer). Ellows, Just my two cents in this whole "what to discuss where" thread which i see re-occuring 3 times every week (and it gets tiresome to be honest). Someone put a wonderfull metaphore last week "opensolaris-discuss is like a square where you can meet and have a talk", something like that. And i agree with this. This means, in my opinion, that anyone should be able to shout something which might interest someone else reading this list, with the restriction that it's opensolaris related. Then, when you want to discuss something in depth which might not interest everybody but a selective group, in real life (yes it exists) you'd go to a pub, to a club house, to someone's home, whatever. In this case you'd go to a specific mailing list handling the matter you want to discuss. In short: opensolaris-discuss should be used and accepted for any input regarding opensolaris, for specific or in depth discussions you may want to and should be able to redirect users NICELY and POLITELY to an appropiate list without making them feel unwanted. Seriously, this is getting silly. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE 70's installer and laying out file systems
> > > Sorry, I forgot to check my filters, that should have been > caiman-discuss only. I actually filed a bug yesterday :) Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE 70's installer and laying out file systems
On 8/20/07, Alan Coopersmith <[EMAIL PROTECTED]> wrote: > Did you try the new installer in build 70? It just changed > the default layout. Yes, to the point it breaks on any big disk when you use an x86 platform. I tried a 200GB ATA disk, and it told me the '/' slice extended beyond the first 1024 cylinders of my HBA. So I was forced to use the old installer, which funny enough happely created a 200GB '/' partition, created just to test if it'd work. Big (read 400GB) SATA disks seem to be a problem on its own, neither the old or the new installer allow me to install a '/' partition of any size. Even when I create a '/' partition of 5120MB (which is 660 cylinders acording to the old installer) it tells me the '/' partition extends beyond the first 1024 cylinders. These error messages are just stupid in my opinion. Cause lo and behold my 'format' output after installing SXCE70 on a 200GB ata disk with a 15GB Part TagFlag Cylinders SizeBlocks 0 rootwm2323 - 4235 14.65GB(1913/0/0) 30732345 1 swapwu 3 - 10478.01GB(1045/0/0) 16787925 2 backupwm 0 - 30511 233.73GB(30512/0/0) 490175280 3varwm1048 - 23229.77GB(1275/0/0) 20482875 4 unassignedwm4236 - 8060 29.30GB(3825/0/0) 61448625 5 unassignedwm8061 - 30511 171.98GB(22451/0/0) 360675315 6 unassignedwm 00 (0/0/0) 0 7 unassignedwm 00 (0/0/0) 0 8 bootwu 0 - 07.84MB(1/0/0) 16065 9 alternateswu 1 - 2 15.69MB(2/0/0) 32130 As you can see, the installer happely installs my root partition way beyond the 1024th cylinder.. Patrick / WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SXCE 70's installer and laying out file systems
Hey all, I just downloaded the DVD and CD version of SXCE70 and this is my experience so far: First of all, the new installer looks flashy and neat. I like the looks :D Then some things I bumped into during the installation. CD media: - Grub presents you the option to use the Developer's install or the "normal" installer. The Developers install is the default, but, Developer''s install is only available for DVD media, not CD media and it will give you an appropiate error message when trying to select the Developer's install anyway. During the install of Developer's install: I miss the opportunity to layout filesystems within my Solaris 2 partition. After I have chosen how I want to partition my harddisk I get some inqueries regarding Location, Timezone, root password etc. after which the installer just starts deploying the packages. I am pretty sure I was able to layout filesystems with SXDE 68 and 69. The installer for the "normal" installation is still the java/CDE installer, is this correct? This is what I actually use for the moment since it does allow me to lay out file systems.. I hope this info is usefull, Patrick / WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Compile errors during onnv-gate
On 8/6/07, Jürgen Keil <[EMAIL PROTECTED]> wrote: Hi all, doing an 'rm -rf usr' and 'bunzip2 -c on-src.tar.bz2 | tar xvf -' solved my problem. I'll install Sun Studio 11 to more or less increase my chances of not running into problems. Maybe an ignorant question but.. why ship SS12 with SXCE and SXDE when 11 is what you're recommending? Take care and thanks for the answers, Patrick Ale WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Compile errors during onnv-gate
Hi all, And now for something completely different. I pulled the ONNV source from the mercurial (spelling) repository. I get the following errors in the mail_msg: http://pastebin.com/m776bbbf0 The end result after 8 hour compilation is... SILK! ACK! I don't see any cpio archives in the archives directory, and I think it's cause of the error shown in the mail_msg. Can someone give me a guide line as of what I am doing wrong or how I can fix it? I am trying to compile on an Athlon 2400XP+ with Sun Studio Pro 12, which is shipped by default with Nevada 69. Thanks in advance! Patrick Ale WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
On 8/5/07, W. Wayne Liauh <[EMAIL PROTECTED]> wrote: > How do I specify my $yourIP when operating as a dhcp client? > Use the loopback IP address 127.0.0.1, simply add your hostname to the existing line in /etc/hosts, beginning with 127.0.0.1 (and ::1 for IPv6) Patrick Ale WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
