Re: [osol-discuss] beadm rename fails

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I guess an even better outcome would be for the rename to simply succeed 
(either by avoiding whatever the root cause is, or by performing the 
"workaround" steps below). I realise I'm preempting the outcome of 
whether this works or not, but if I do the following, I get "unmount 
failed" too:


opensolaris:~> pfexec beadm create test
opensolaris:~> pfexec beadm activate test
opensolaris:~> beadm list
BE   Active Mountpoint Space   Policy Created
--   -- -- -   -- ---
snv-111b -  -  37.90M  static 2009-06-03 09:49
snv-129  -  -  189.89M static 2009-12-14 11:57
snv-130  -  -  16.68M  static 2010-01-04 11:11
snv-131  -  -  29.83M  static 2010-01-26 11:33
snv-132  N  /  186.5K  static 2010-02-03 08:40
test R  -  22.34G  static 2010-02-08 15:58
opensolaris:~> pfexec beadm rename test newtest
Rename of BE test failed.
unmount failed.

Sure enough, truss confirms it received EBUSY from umount2("/"). 
However, if I re-activate the currently running BE (snv-132), I can then 
rename and reactivate the new BE:


opensolaris:~> pfexec beadm activate snv-132
opensolaris:~> pfexec beadm rename test newtest
opensolaris:~> pfexec beadm activate newtest
opensolaris:~> beadm list
BE   Active Mountpoint Space   Policy Created
--   -- -- -   -- ---
newtest  R  -  22.34G  static 2010-02-08 15:58
snv-111b -  -  37.90M  static 2009-06-03 09:49
snv-129  -  -  189.89M static 2009-12-14 11:57
snv-130  -  -  16.68M  static 2010-01-04 11:11
snv-131  -  -  29.83M  static 2010-01-26 11:33
snv-132  N  /  4.27M   static 2010-02-03 08:40


Is there a technical reason that it cannot rename an activated BE?


Thanks,
Brian


On 02/ 8/10 03:52 PM, Shawn Walker wrote:
On 02/ 8/10 04:32 AM, Brian Ruthven - Solaris Network Sustaining - Sun 
UK wrote:


Is the BE that you are trying to rename the currently activated BE (that
is, active on next reboot)?

I ran into problems like this, and had to do a bit of a dance with
"beadm activate" to avoid renaming either the current BE or the
newly-created-and-activated BE:

beadm activate current
beadm rename new latest
beadm activate latest

Admittedly, this was all before the --be-name option came in, so it
could have changed since then. Does the above serve as a useful 
workaround?


If that works, then beadm could use some better error messaging for 
this case.




--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] beadm rename fails

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Is the BE that you are trying to rename the currently activated BE (that 
is, active on next reboot)?


I ran into problems like this, and had to do a bit of a dance with 
"beadm activate" to avoid renaming either the current BE or the 
newly-created-and-activated BE:


beadm activate current
beadm rename new latest
beadm activate latest

Admittedly, this was all before the --be-name option came in, so it 
could have changed since then. Does the above serve as a useful workaround?


HTH
Brian


On 02/ 5/10 08:39 PM, Bill Shannon wrote:

Trying to upgrade from b127 to b132.  After working around some other
bugs, pkg image-update succeeded, but left me with a BE with a stupid
name.  I tried to rename it (while still running in the old BE) but
it fails saying "unmount failed."  truss shows that it's trying to
unmount "/"!  Yow, that's never going to work!

Is it just broken, or am I doing something wrong?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] [laptop-discuss] Toshiba M10 - 111 to 131 upgrade issues - GDM fails, blank screen

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

On 01/29/10 04:19 PM, Bruce Porter wrote:


ff0007f7c420 vpanic()
ff0007f7c4d0 hat_devload+0x20f(ff01be68ae78, ff017b01b000, 1000,
3c000, 3, 1)
ff0007f7c530 rootnex_map_regspec+0x129(ff0007f7c540, c0059e48)
ff0007f7c5e0 rootnex_map+0x141(ff01bf82ecb0, ff01bf82e7a0,
ff0007f7c670, 0, 0, c0059e48)
ff0007f7c630 ddi_map+0x51(ff01bf82e7a0, ff0007f7c670, 0, 0,
c0059e48)
ff0007f7c730 npe_bus_map+0x481(ff01bf82e7a0, ff01bf82e518,
ff0007f7c7b0, 0, 1000, c0059e48)
ff0007f7c780 ddi_map+0x51(ff01bf82e518, ff0007f7c7b0, 0, 1000,
c0059e48)
ff0007f7c840 ddi_regs_map_setup+0xd5(ff01bf82e518, 1, c0059e48,
0, 1000, c0059e60, c0059e50)
ff0007f7c900 intel_chipset_flush_setup+0x425(ff01bf82e518,
ff01d4933d00, 15)
ff0007f7c9b0 agp_target_ioctl+0x30b(d9, 20004d26, 0, 8020,
ff01c0367e88, 0)
ff0007f7c9f0 cdev_ioctl+0x45(d9, 20004d26, 0, 8020,
ff01c0367e88, 0)
ff0007f7ca30 ldi_ioctl+0xb0(ff01db3f3020, 20004d26, 0, 8000,
ff01c0367e88, 0)
ff0007f7ca80 agpgart_open+0x2d5(ff0007f7cb08, 2003, 2, ff01d352b698
)
ff0007f7cab0 dev_open+0x3c(ff0007f7cb08, 2003, 2, ff01d352b698)
ff0007f7cb60 spec_open+0x5dc(ff0007f7cc40, 2003, ff01d352b698, 0)
ff0007f7cbd0 fop_open+0xbf(ff0007f7cc40, 2003, ff01d352b698, 0)
ff0007f7cd70 vn_openat+0x65d(5fcde8, 0, 2003, ae0, ff0007f7cdb8, 0, 12,
0, d)
ff0007f7ced0 copen+0x435(ffd19553, 5fcde8, 2003, 865ae0)
ff0007f7cf00 open+0x34(5fcde8, 2, 865ae0)
ff0007f7cf10 sys_syscall+0x17a()

---8<

Anymore info needed ?
   


The stack matches that in 6914386 which is possibly a duplicate of 
6911372 which is fixed in snv_131. This was introduced in b130, so it 
fits your problem.


My suggestion would be to jump back to b129 (or whatever was your last 
stable one) and upgrade to b131 which is currently available. Let us 
know if you still get the above panic.


Regards,
Brian

--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Need to find files with in name. How?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

On 02/ 2/10 09:38 PM, Orvar Korvar wrote:

ls -b
shows My\344Document\366.doc¨which seems better. I tried to find "*\344*" but 
that didnt work.
   



Some ways I've used in the past:

1) Shell completion (personally, I use tcsh) has helped me out 
here. If the name starts with a unique letter or phrase, then start 
tying "rm My" and press . tcsh will complete, usually including the 
necessary escapes along the way.


2) Locate some unique part of the filename, and use "rm *uniq*" to 
delete it.


3) Locate some partially-unique part of the filename, and use "rm 
-i *uniq*" to interactively delete the one you want;


opensolaris:~/test> rm -i file*
rm: remove file1 (yes/no)? n
rm: remove file2 (yes/no)? n
rm: remove file3 (yes/no)? y
rm: remove file4 (yes/no)? n
opensolaris:~/test> ls
file1  file2  file4  hello

4) Use a file manager and delete it "visually". The last time I 
used this method was with dtfm, the CDE file manager, but I suspect 
whatever GNOME's equivalent will do the same.


5) Last resort: Create a new sub-directory and "mv * newdir/". Then 
move everything else back to the original location, and "rm -rf newdir" 
to delete the directory and the awkward file.



They're not clever ways, but they can help in a tight spot. I used #3 
this morning to delete a file named )(*&^%$"!

I used "rm *\!" to delete it as nothing else ended with a !

HTH
Brian

--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] crash kernel when inserting card in SD card reader on a dell M4400

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

The "WARNING: sdcard:..." message may be related to CR 6910217 (fixed in 
b131).


However, I can't say whether this is related to the panic or not. Can 
you include the stack trace? You've cut it off the bottom of the 
messages you posted.


Thanks,
Brian


On 02/ 1/10 12:44 PM, solarg wrote:

hello all,
i've os20xx.yy b130 on my dell laptop M4400. There is a SD card 
reader. If i try to use it, the kernel crashes:


Jan 30 19:30:14 tara genunix: [ID 408114 kern.info] 
/p...@0,0/pci8086,2...@1e/pci1028,2...@1,2/sdc...@0 (sdcard0) online
Jan 30 19:30:14 tara scsi: [ID 583861 kern.info] sd10 at sdcard0: 
target 0 lun 0
Jan 30 19:30:14 tara genunix: [ID 936769 kern.info] sd10 is 
/p...@0,0/pci8086,2...@1e/pci1028,2...@1,2/sdc...@0/d...@0,0
Jan 30 19:30:14 tara genunix: [ID 408114 kern.info] 
/p...@0,0/pci8086,2...@1e/pci1028,2...@1,2/sdc...@0/d...@0,0 (sd10) online
Jan 30 19:31:23 tara rootnex: [ID 561485 kern.warning] WARNING: 
sdcard: coding error detected, the driver is using ddi_dma_attr(9S) 
incorrectly. There is a small risk of data corruption in particular 
with large I/Os. The driver should be replaced with a corrected 
version for proper system operation. To disable this warning, add 'set 
rootnex:rootnex_bind_warn=0' to /etc/system(4).

Jan 30 19:31:33 tara unix: [ID 836849 kern.notice]
Jan 30 19:31:33 tara ^Mpanic[cpu1]/thread=ff01f15a0e60:
Jan 30 19:31:33 tara genunix: [ID 683410 kern.notice] BAD TRAP: type=8 
(#df Double fault) rp=ff01cf1aaf10 addr=0

Jan 30 19:31:33 tara unix: [ID 10 kern.notice]
Jan 30 19:31:33 tara unix: [ID 839527 kern.notice] hald-probe-volum:
Jan 30 19:31:33 tara unix: [ID 753105 kern.notice] #df Double fault
Jan 30 19:31:33 tara unix: [ID 243837 kern.notice] pid=4957, 
pc=0xfbadf178, sp=0xff000a289000, eflags=0x10286
Jan 30 19:31:33 tara unix: [ID 211416 kern.notice] cr0: 
8005003b cr4: 6f8

Jan 30 19:31:33 tara unix: [ID 624947 kern.notice] cr2: ff000a288ff8
Jan 30 19:31:33 tara unix: [ID 625075 kern.notice] cr3: 11ff57000
Jan 30 19:31:33 tara unix: [ID 625715 kern.notice] cr8: c
Jan 30 19:31:33 tara unix: [ID 10 kern.notice]
Jan 30 19:31:33 tara unix: [ID 592667 kern.notice]  rdi: 
ff01dd1d4c00 rsi:   16 rdx: ff022a886388


Is there a workaround? actually, i'm not able to upgrade to b131:
http://opensolaris.org/jive/thread.jspa?threadID=122392&tstart=30

thanks in advance for help,

gerard


___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] mimic size=1024m setting in /etc/vfstab when using rpool/swap (zfs root)

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

tmpfs and ufs/zfs are different things.

You limit the amount of "swap" (i.e. disk-backed 'memory') by varying 
the size of the device added using "swap -a", or the lines in vfstab 
with 'swap' in the "FS type" column. This is the "memory" available to 
all processes.


You limit the amount of swap use by tmpfs by using the "size=" mount 
option or the options column of the /tmp line in vfstab (which has an FS 
type of tmpfs, not swap).


Whilst I can't demonstrate re-mounting /tmp with the size= option, I can 
mount a new filesystem from swap in the same way whilst using zfs root:


# mount -Ftmpfs swap /a
# df -h /a
FilesystemSize  Used Avail Use% Mounted on
swap  704M 0  704M   0% /a
# umount /a
# mount -Ftmpfs -osize=100m swap /a
# df -h /a
FilesystemSize  Used Avail Use% Mounted on
swap  100M 0  100M   0% /a


See mount_tmpfs(1M) for the full range of options for tmpfs mounting. 
These options are independent of your root filesystem type.


If you're saying that with zfs root, setting "size=" on the tmpfs line 
of /etc/vfstab does not work, I would say a bug needs to be logged about it.



Regards,
Brian



On 02/ 1/10 06:15 AM, Prakash Kochummen wrote:

Hi,

While using ufs root, we had an option for limiting the /tmp size using mount 
-o size manual option or setting size=1024m in the vfstab.

Do we have any comparable option available when we use zfs root. If we execute
zfs set size=1024m rpool/swap
it resizes the whole of the swap area which results in reducing the VM size.

AFAIK in the ufs option for limiting swap size, we are just limiting the 
filesystem behaviour of the tmpfs filesystem while the kernel will still be 
able to use the swap space for paging etc. Is this correct understanding.

Thanks in advance.

Rgds
PK
   


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] export: couldn't set locale correctly

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Which shell are you using and which OS is this?
I'm guessing it's ksh, so I guess you're using Solaris 10? It could be 
Bourne shell /bin/sh, but this also implies Solaris 10.


From the info you've given, I'd say the en_US locale is not installed. 
"locale -a" will list all available locales. Does en_US appear in the list?



Regards,
Brian




On 01/ 7/10 12:07 PM, Malaiselvan wrote:

Hi,

I getting the error "export: couldn't set locale correctly" while trying to 
execute the below command in my profile

export LANG=en_US

Could someone encounter the same problem?

Regards
Malai
   


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] redirect "command --help" to file

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Standard | and > redirects will only redirect stdout. In bash (and other 
Bourne shell equivalents), you need something like:


bash-4.0$ keytool --help 2>&1 | less

csh-style shells should be something like this:

% keytool --help |& less

Check the man page for the shell you are using for the stderr 
redirection syntax.



Regards,
Brian


On 01/ 5/10 12:46 PM, Sven Aluoor wrote:

Hi folks

[Please add me CC]

How to redirect "command --help" to file?
Why normal way doesn't work?

   

keytool --help>  /tmp/keytool
 

or

   

keytool --help | tee /tmp/keytool
 

keytool usage:
[...]

   

cat /tmp/keytool
 

  [-providerClass  [-providerArg]] ...

cheers Sven
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
   


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] snv_111b x86 crashing

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

melbogia wrote:

melbogia wrote:


There is no "panic" or "syncing filesystems" in
  

/var/adm/messages. Here is what I see after I execute
the command "mkfile 100g /datapool/testfile"


I was on the machine at 1600 hours yesterday and
  

the next entry after that at 8:43 AM is system
startup information, it seems it can't even write
anything to /var/adm/messages before it reboots?


Also this may be relevant, the datapool pool
  

doesn't exist after it comes up from crash. I have to
do a "zpool import -f datapool" to import it.

  
  

This may be multiple issues. The fact a reboot
happens with no trace in 
/var/adm/messages is somewhat worrying to me.
However, we need to frame 
the issue. Things like:


When you were using the system on the 10th, how
were you connected 
to it? Were you logged in remotely (via

ssh/telnet/etc...)?
Where you on the console? (graphics console, or
 text mode)?
   What did you see on the screen around 16:19 ?



I was connected to the server via ssh and I didn't see anything at 16:19.
  


I can't imagine you saw absolutely nothing from your ssh session. I'm 
guessing that it hung, and eventually gave some error like "timeout" or 
"connection reset by peer" or something? Even if you reset it, did you 
try ssh again, ping, etc...? What were the results here?


Did you go (if able) to the system itself? What state was it in? etc...
It wasn't a power cut was it?   ;-)



I am not sure about the hardware reset issues, I'll poke around and see what I 
find. But there is another machine with the Opensolaris 2009.06 as well, it has 
the exact same hardware with the exception of hard disks. It has been working 
fine.

  


That's kind of my point. If there is an "identical" system (and beware - 
they are rarely exactly identical with no differences whatsoever), and 
it is functioning fine, then (assuming similar usage patterns) it may 
help point to a hardware/firmware issue, etc... Don't get me wrong - I'm 
not saying your hardware is bust - just something to bear in mind if the 
fault always stays with the one system and no other system is affected.




Dec 11 08:43:36 dirt zfs: [ID 427000 kern.warning]
  

WARNING: pool 'datapool' could not be loaded as it
was last accessed by another system (host: dirt
hostid: 0x409a4c). See:
http://www.sun.com/msg/ZFS-8000-EY

  
  

Whilst I can't comment on this line myself, it does
(IMO) explain why 
you had to force import the pool after the reboot.

Assuming there is only one host with name "dirt",
then this would seem 
to be a bug.



that is correct, there is only one host with that name in the environment.
  



You might want to ask this question on zfs-discuss, and give them the 
background.


Just a thought (assuming the system will let you do this), who else was 
logged in at the time? Could somebody have done a forced export of all 
zpools on the system? Could this explain why the messages file stopped 
being written to?


Regards,
Brian

--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] snv_111b x86 crashing

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

melbogia wrote:

There is no "panic" or "syncing filesystems" in /var/adm/messages. Here is what I see 
after I execute the command "mkfile 100g /datapool/testfile"

I was on the machine at 1600 hours yesterday and the next entry after that at 
8:43 AM is system startup information, it seems it can't even write anything to 
/var/adm/messages before it reboots?

Also this may be relevant, the datapool pool doesn't exist after it comes up from crash. 
I have to do a "zpool import -f datapool" to import it.
  


This may be multiple issues. The fact a reboot happens with no trace in 
/var/adm/messages is somewhat worrying to me. However, we need to frame 
the issue. Things like:


   When you were using the system on the 10th, how were you connected 
to it? Were you logged in remotely (via ssh/telnet/etc...)?

   Where you on the console? (graphics console, or text mode)?
   What did you see on the screen around 16:19 ?


Can you check any alternate boot environments, and make sure you are 
running from the BE you expect to be running from? e.g. did you have a 
pending beadm activate, and the reboot simply booted into the new 
environment?


Also, are there any known "hardware reset" issues for your platform? 
There have been bugs occasionally in the past where a driver will cause 
a system-wide reset without going through the panic mechanism. I can't 
recall any, but do remember one or two cropping up occasionally.




Dec 11 08:43:36 dirt zfs: [ID 427000 kern.warning] WARNING: pool 'datapool' 
could not be loaded as it was last accessed by another system (host: dirt 
hostid: 0x409a4c). See: http://www.sun.com/msg/ZFS-8000-EY
  


Whilst I can't comment on this line myself, it does (IMO) explain why 
you had to force import the pool after the reboot.
Assuming there is only one host with name "dirt", then this would seem 
to be a bug.


Regards,
Brian



--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] pkg install SUNWipkg downloads 300+Mb ??

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I've just updated the bug, but basically, yes - two packages. Now they 
are removed, the image-update works as expected.


Thanks,
Brian


david.co...@sun.com wrote:
Logged as bug 13241: 
http://defect.opensolaris.org/bz/show_bug.cgi?id=13241


Looks like I can't upgrade (although I'm hoping there is a workaround).

If I let it run to completion, I see:

DOWNLOAD  PKGS   FILESXFER (MB)
Completed  662/662 10506/10506  
329.8/329.8 pkg: Requested "install" operation would affect files 
that cannot be modified

in live image.
Please retry this operation on an alternate boot environment.


Do you have packages installed from "/contrib"?  If so, you may be
running into

13233 /contrib packages should not depend on "entire"
http://defect.opensolaris.org/bz/show_bug.cgi?id=13233

The work-around is to uninstall the packages in question - you can find
out the list by running

pkg contents -Ho pkg.name,action.raw -t depend | \
grep fmri=entire@ | cut -f1


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] pkg install SUNWipkg downloads 300+Mb ??

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Logged as bug 13241: http://defect.opensolaris.org/bz/show_bug.cgi?id=13241

Looks like I can't upgrade (although I'm hoping there is a workaround).

If I let it run to completion, I see:

DOWNLOAD  PKGS   FILESXFER (MB)
Completed  662/662 10506/10506  329.8/329.8 


pkg: Requested "install" operation would affect files that cannot be modified
in live image.
Please retry this operation on an alternate boot environment.


Regards,
Brian


Shawn Walker wrote:

Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:



Shawn Walker wrote:

Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:


I was trying to image-update to b129, and I wasn't going to be put 
off by the request to upgrade the pkg command:


$ pfexec pkg image-update -nv
Creating Plan - WARNING: pkg(5) appears to be out of date, and 
should be updated before

running image-update.  Please update pkg(5) using 'pfexec pkg install
SUNWipkg' and then retry the image-update.


However, I didn't expect the following command to begin downloading 
everything:


$ pfexec pkg install -v SUNWipkg
Creating Plan -
[ many lines elided ]
Actuators:
 restart_fmri: 
svc:/application/desktop-cache/pixbuf-loaders-installer:default

 restart_fmri: svc:/application/desktop-cache/gconf-cache:default
 restart_fmri: 
svc:/application/desktop-cache/input-method-cache:default

 restart_fmri: svc:/system/rbac:default
 restart_fmri: svc:/application/font/fc-cache:default
 restart_fmri: svc:/system/manifest-import:default
reboot-needed: true

DOWNLOAD  PKGS   FILESXFER 
(MB)
SUNWgnome-a11y-libs316/662  6310/10506  
146.5/329.8^C



Is this expected?
Whilst in my case this update is a prelude to an image-update 
anyway, I did not expect to have to wait for all 300Mb to download 
simply to update the pkg command.


By the looks of it, your system isn't properly constrained (missing 
the "entire" package perhaps?).  You're right that you shouldn't 
expect this large of a download for just SUNWipkg.  I'd have to see 
the lines you elided to say exactly what happened.


It would also be helpful to see the output of:

pkg info entire ips-incorporation

...and the output of "pkg publisher".

Cheers,


I don't believe I ever manually installed "entire", although it shows 
as installed. Here's what you asked for:


$ pfexec pkg info entire ips-incorporation
 Name: entire
  Summary: Build 128 entire incorporation
  Description: This package constrains package versions to those for 
build 128.
   WARNING: Proper system update and correct package 
selection
   depend on the presence of this incorporation.  
Removing this

   package will result in an unsupported system.
State: Installed
Publisher: opensolaris.org
  Version: 0.5.11
Build Release: 5.11
   Branch: 0.128
Packaging Date: November 25, 2009  5:17:47 AM
 Size: 0.00 B
 FMRI: 
pkg://opensolaris.org/ent...@0.5.11,5.11-0.128:20091125T051747Z


pkg: info: no packages matching the following patterns you specified are
installed on the system.  Try specifying -r to query remotely:

   ips-incorporation

$ pfexec pkg publisher
PUBLISHER TYPE STATUS   URI
opensolaris.org  (preferred)  origin   online   
http://ipkg.sfbay/dev/
contrib   origin   online   
http://pkg.opensolaris.org/contrib/
extra origin   online   
http://ipkg.sfbay/extra/
punchin   origin   online   
http://righthook.east:1/



I've attached a (gzipped) typescript of the install. I interrupted it 
rather than letting it run to completion, as I wasn't sure it would 
create me a new BE and install to that (rather than simply upgrading 
everything in my current BE!).


This looks like a possibly nasty install bug.

Can you please open a bug at defect.opensolaris.org under development 
-> pkg and attach the file you sent here?


Can you also attach the output of "pkg contents -m entire" ?

Cheers,


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] pkg install SUNWipkg downloads 300+Mb ??

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Shawn Walker wrote:

Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:


I was trying to image-update to b129, and I wasn't going to be put 
off by the request to upgrade the pkg command:


$ pfexec pkg image-update -nv
Creating Plan - WARNING: pkg(5) appears to be out of date, and should 
be updated before

running image-update.  Please update pkg(5) using 'pfexec pkg install
SUNWipkg' and then retry the image-update.


However, I didn't expect the following command to begin downloading 
everything:


$ pfexec pkg install -v SUNWipkg
Creating Plan -
[ many lines elided ]
Actuators:
 restart_fmri: 
svc:/application/desktop-cache/pixbuf-loaders-installer:default

 restart_fmri: svc:/application/desktop-cache/gconf-cache:default
 restart_fmri: 
svc:/application/desktop-cache/input-method-cache:default

 restart_fmri: svc:/system/rbac:default
 restart_fmri: svc:/application/font/fc-cache:default
 restart_fmri: svc:/system/manifest-import:default
reboot-needed: true

DOWNLOAD  PKGS   FILESXFER (MB)
SUNWgnome-a11y-libs316/662  6310/10506  
146.5/329.8^C



Is this expected?
Whilst in my case this update is a prelude to an image-update anyway, 
I did not expect to have to wait for all 300Mb to download simply to 
update the pkg command.


By the looks of it, your system isn't properly constrained (missing 
the "entire" package perhaps?).  You're right that you shouldn't 
expect this large of a download for just SUNWipkg.  I'd have to see 
the lines you elided to say exactly what happened.


It would also be helpful to see the output of:

pkg info entire ips-incorporation

...and the output of "pkg publisher".

Cheers,


I don't believe I ever manually installed "entire", although it shows as 
installed. Here's what you asked for:


$ pfexec pkg info entire ips-incorporation
 Name: entire
  Summary: Build 128 entire incorporation
  Description: This package constrains package versions to those for 
build 128.

   WARNING: Proper system update and correct package selection
   depend on the presence of this incorporation.  Removing this
   package will result in an unsupported system.
State: Installed
Publisher: opensolaris.org
  Version: 0.5.11
Build Release: 5.11
   Branch: 0.128
Packaging Date: November 25, 2009  5:17:47 AM
 Size: 0.00 B
 FMRI: 
pkg://opensolaris.org/ent...@0.5.11,5.11-0.128:20091125T051747Z


pkg: info: no packages matching the following patterns you specified are
installed on the system.  Try specifying -r to query remotely:

   ips-incorporation

$ pfexec pkg publisher
PUBLISHER TYPE STATUS   URI
opensolaris.org  (preferred)  origin   online   
http://ipkg.sfbay/dev/
contrib   origin   online   
http://pkg.opensolaris.org/contrib/
extra origin   online   
http://ipkg.sfbay/extra/
punchin   origin   online   
http://righthook.east:1/



I've attached a (gzipped) typescript of the install. I interrupted it 
rather than letting it run to completion, as I wasn't sure it would 
create me a new BE and install to that (rather than simply upgrading 
everything in my current BE!).


Many thanks,
Brian


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG



pkg_install_SUNWipkg.script.gz
Description: GNU Zip compressed data
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] pkg install SUNWipkg downloads 300+Mb ??

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I was trying to image-update to b129, and I wasn't going to be put off 
by the request to upgrade the pkg command:


$ pfexec pkg image-update -nv
Creating Plan - WARNING: pkg(5) appears to be out of date, and should be 
updated before

running image-update.  Please update pkg(5) using 'pfexec pkg install
SUNWipkg' and then retry the image-update.


However, I didn't expect the following command to begin downloading 
everything:


$ pfexec pkg install -v SUNWipkg
Creating Plan -
[ many lines elided ]
Actuators:
 restart_fmri: 
svc:/application/desktop-cache/pixbuf-loaders-installer:default

 restart_fmri: svc:/application/desktop-cache/gconf-cache:default
 restart_fmri: 
svc:/application/desktop-cache/input-method-cache:default

 restart_fmri: svc:/system/rbac:default
 restart_fmri: svc:/application/font/fc-cache:default
 restart_fmri: svc:/system/manifest-import:default
reboot-needed: true

DOWNLOAD  PKGS   FILESXFER (MB)
SUNWgnome-a11y-libs316/662  6310/10506  146.5/329.8^C


Is this expected?
Whilst in my case this update is a prelude to an image-update anyway, I 
did not expect to have to wait for all 300Mb to download simply to 
update the pkg command.



Regards,
Brian


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Group lost its members

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Hi Martin,

My understanding is that ZFS can cope with disks being re-arranged by 
searching for the unique identifier on each disk which tells the system 
which pool it belongs to.


That said, the demonstrations I've seen only involved re-positioning the 
disks rather than a complete change in transport. However, I don't see 
why it shouldn't work as long as the OS can build device paths to the 
new locations. As long as the disks show up in format, I guess you're 
good to go. Your suggested method looks good to me as a non-expert in 
ZFS and device path management :-)


zfs-disc...@opensolaris.org may be a better place to ask this particular 
question.


Regards,
Brian


Dr. Martin Mundschenk wrote:



This looks like bug 6835533 
( http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6835533 )

At least the mystery of the reboot can be solved :-)



This bug seems to be related to FireWire drives. My HDs also have USB 
interfaces. Is it possible to zpool export the pool, hook it to the 
USB port and zpool import the pool again? 


Martin



--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] BFU to b128a

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Ian Allison wrote:

Hi,

Just to follow up, I looked at the create_ramdisk script 
(/boot/solaris/bin/create_ramdisk) and it has a dependency on mkisofs.
If it can't find the mkisofs binary it sets the variable $format to 
ufs, this seems to cause a problem if the system has a ZFS root. 
Installing SUNWmkcdr and SUNWmkcd were enough to allow the bfu to update.


Sorry I didn't manage to reply again before you fixed it yourself.
I must admit I'm intrigued by the "fix", as the format of the ramdisk is 
not related to the format of your root filesystem (and indeed your 
conclusion falls down as 'isofs' != zfs). All that happens is that the 
ramdisk is created as an iso fs if possible, falling back to ufs if 
mkisofs is not available (as you found).


Looking at the script, it would seem that by installing the packages you 
mention, you've avoided the faulty bit of script. Nevertheless, in your 
case it's fixed your problem, but there still exists something (a bug?) 
in the ufs-handling part of the script. Would you be able to log a bug 
on it please, specifying what you initially did to install, then the 
exact steps (commands typed, etc...) to get to the bfu stage?


You can of course put in the addition of those two packages as the 
workaround.


Many thanks,
Brian



--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] attaching 2nd interface to a non-routed network

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I don't think (from what you've provided) that you've done anything 
wrong. What does "ifconfig -a" look like?


Some starter questions (and I've assumed OpenSolaris given the mailing 
list you've posted to):
   1) How do you know there is no traffic? Does "snoop -d bge1" show 
anything?
   2) Is the link up? "dladm show-link" or "dladm show-ether" should 
report this.
   3) Does the speed and duplex reported above match your expectation 
(and the switch)?
   4) What else is the switch connected to? Are those other devices 
able to contact each other?


Regards,
Brian


Eugene Vilensky wrote:

Greetings,

I've manually configured two network interfaces on two very different subnets.


# netstat -r

Routing Table: IPv4
 Destination   Gateway   Flags  Ref Use Interface
  - - -- -
default  140.yyy.yyy.yyy UG1   2310
140.yyy.yyy.yyy xxx.xxx.edu  U 1274 bge0
172.16.0.0   172.16.0.139 U 1  2 bge1


bge0 is correct, but I cannot get any traffic for bge1.
172.16.0.139/16 is the ipaddress of bge1.  bge1 is attached to a
layer2 switch and shouldn't have any routing.
should the gateway entry for this interface be deleted, set to the
local interface IP as is currently, or something else?

thanks all!
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Very slow boot time ( > 35minutes)

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

As long as you realise this file may be (and probably will be) 
overwritten during your next upgrade, so your changes will be undone, 
and you will have to remember to re-edit after each upgrade.


Generally, modifying the start methods is a bad thing, and this is not 
the right interface to disable services.
The correct interface is svcadm which updates the repository (whose 
contents persist across reboots / upgrades).


Having said that, it appears that the audio service is a "require_all" 
dependency for multi-user. Strange - I would have expected an 
optional_all. Can anybody comment on why this is?


If it were an optional dependency, then simply "svcadm disable audio" 
should suffice.


I suspect this should be raised as a bug (I've not checked for existing 
ones).


Regards,
Brian


Alastair Neil wrote:
or as in my case if you have a server with no audio, just comment out 
"devfsadm -i audio" from lib/svc/method/device-audio :)



On Tue, Dec 1, 2009 at 8:44 PM, Chris > wrote:


[url=http://bugs.opensolaris.org/view_bug.do?bug_id=6902551]Bug

#6902551[/url] was responsible for the audio device issue on
SVN_127 (its was always 127 not 125 as I mentioned earlier).

The fix described worked a treat and the box now boots.
--
This message posted from opensolaris.org 
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org





___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] How to make syslogger write to a fifo?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Hi Harry,

I've got nothing canned which I can quickly pass on, however, anything I 
gather will be from google ;-)


The top three hits searching for "writing smf manifest" look useful:

http://www.sun.com/bigadmin/content/selfheal/sdev_intro.jsp
http://wikis.sun.com/display/BigAdmin/SMF+Short+Cuts
http://blogs.warwick.ac.uk/chrismay/entry/solaris_smf_manifest/

I've not looked at them in depth, but they seem to contain a mixture of 
background and contain examples (or fragments).
I'd suggest copying /var/svc/manifest/system/utmp.xml as a starting 
point for modification (obviously don't modify utmp.xml itself!). IIRC, 
it implements a simple, single-daemon 'child' type of service, which is 
restarted if it dies.


Hopefully that is enough to get you started. I'd suggest copying the 
manifest from a simple service such as utmp.xml and customise it to your 
needs. If your service needs a startup script, then you should include 
/lib/svc/share/smf_include.sh so you can use the correct exit codes to 
signal the right things to the framework.


Hope that helps,
Brian



Harry Putnam wrote:

Brian Ruthven - Sun UK 
writes:
  

Personally, I would use an SMF service to wrap my reader, and place a
dependent entry in the manifest something like this:



Brian.. can you post some URLs about using SMF.  I'm completely
ignorant about it.  I realize I can google it but hoped URLs you
provided might save lots of time wasted on baloney hits.

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] How to make syslogger write to a fifo?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I believe you can create a named pipe (using mkfifo) somewhere in the 
filesystem (I'd suggest somewhere persistent, not /tmp or /var/run, 
etc...). I've seen it created as /var/log/logpipe or similar. Then 
simply name the file in syslog.conf without the '|' symbol.


However, note that if there is nothing reading from the pipe when 
syslogd starts (or when it receives a HUP) then it will ignore it, so 
you need to make sure something is reading the pipe before syslog 
starts. SMF is probably the best way to do this - you can insert a 
dependancy for the svc:/system/system-log service to make sure your pipe 
reader starts first.


Also, if there is nothing reading from the pipe when syslogd tries to 
write to it, it will close it and ignore it until the next 
restart/refresh. However, the smf "restart on" property of the 
dependancy can refresh system-log if your reader dies and is restarted.



Hope that helps,
Brian


Harry Putnam wrote:

Can anyone tell me how to make the system logger write to a fifo?

I've tried this in /etc/syslog.conf

   *.debug  |/var/adm/flt

Where `flt' is a fifo and the two elements are separated by tabs. 

After a sighup to systemlogger  I'm not seeing any data with 
  `cat flt'


Made sure data is been sent by system-log but nothing appears at the
fifo.

Doing something like (in two different xterms):

xterm 1
cat flt  


xterm 2
cat messages > flt

And I see the data so I know the fifo is working.

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] GTK+ development packages?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

It looks like wxWidgets is already integrated into Opensolaris (since 
snv_100 apparently), so you might save yourself some time and effort 
unless you really want the challenge of compiling it  :-)  I recall 
having some fun and games in the past with wxWidgets.


The gtk.h header (from gtk2.0) seems to have come in the 
SUNWgnome-base-libs package up to snv_115, then from snv_116, comes in 
package SUNWgtk2.


pfexec pkg install SUNWwxwidgets SUNWgtk2
or
pfexec pkg install SUNWwxwidgets SUNWgnome-base-libs

should get you going...

HTH
Brian



Peter C. Chapin wrote:

I'm attempting to compile wxWidgets on my OpenSolaris 2009.06 machine. The 
configuration requires GTK related headers and such. For example, it attempts 
to compile a test program that #includes gtk/gtk.h. Right now this fails as I 
don't have that file installed. Is there a package for that? I spent some time 
digging around in the opensolaris repository but I can't seem to find one. 
Should I be looking at a different repository?

Thanks!
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Trace stdout

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I suspect dtrace is a bit too low level given the information you supplied.

I would start by using "/usr/sbin/fuser nohup.out" to see what processes 
have the file open. Then, I would use pfiles against one or two of them 
to confirm nohup.out is fd1 (i.e. stdout). Then I would use truss to 
observe what data is being written:


$ fuser nohup.out
nohup.out: 2136o2131o
$ pfiles 2136
2136:/bin/sh ./script.sh
 Current rlimit: 256 file descriptors
  0: S_IFCHR mode:0620 dev:308,0 ino:713783913 uid:116669 gid:7 rdev:24,3
 O_RDWR
 /dev/pts/3
  1: S_IFREG mode:0600 dev:313,2 ino:710282559 uid:116669 gid:10 size:2664
 O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE
 /tmp/nohup.out
  2: S_IFREG mode:0600 dev:313,2 ino:710282559 uid:116669 gid:10 size:2664
 O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE
 /tmp/nohup.out
 10: S_IFREG mode:0755 dev:313,2 ino:710290470 uid:116669 gid:10 size:54
 O_RDONLY|O_LARGEFILE FD_CLOEXEC
 /tmp/script.sh

I'm interested in descriptors 1 and 2 above (as these have nohup.out open):
$ truss -twrite -w1,2 -p 2136
write(1, " P I D = 2 1 3 6\n", 9)= 9
write(1, " P I D = 2 1 3 6\n", 9)= 9
write(1, " P I D = 2 1 3 6\n", 9)= 9
^C


Does that do what you need?

As for a Dtrace bible, I'm assuming you have already looked at the 
"Solaris Dynamic Tracing Guide" on docs.sun.com?


This will give you the basics of syntax along with what you can and 
can't trace, although you may find it useful to know your way around the 
onnv source code as well (although this may only work reliably for the 
public interfaces such as system calls as you are using Solaris 10).


Hope that helps,
Brian



FrenKy wrote:

Hi *,
I'm very new with dtrace, but I have one problem and dtrace looks to be a 
promising candidate for analysis.

I have solaris 10 system which has many, many processes all sending their stdout to one file 
(one master process which starts all processes is started as "nohup masterProc 
&") and all childs output ends up in nohup.out.

On a platform where I'm working on, it is strictly forbidden to write anything  
to stdout or stderr (tracing mechanism exists) so I have to figure out which of 
the processes is writing to the file.

I have an idea which one is it, but I do not know exactly how to check.
Was thinking about syscall::write:entry, but I'm not sure...

Is there some "dtrace bible" going around?

Thanks in advance!
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Laptop Battery Monitor

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Which release of OpenSolaris are you using?

I used to have horrendous problems with the battery monitor under 
2008.11 on an Acer Ferrari 4000 (similar to what you describe).
I did find that plugging in or disconnecting the AC power would trigger 
a refresh, but it would then stay at the same level until the next AC 
insert/removal event, etc...


At present I'm using a Toshiba Tecra M10 with 2009.06 (updated to dev 
branch snv_124) with no battery monitor problems (that I've noticed!).


Regards,
Brian


Johnathon Tyler Harmon wrote:

When i installed open solaris on my Campaq laptop the battery monitor would 
never change off of 100% one time it even turned off on me when it said a 100% 
. Any one have any ideas on how to fix that. If i could get that fixed i would 
love to change back from windows to open solaris.
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] CDE hang issue on Solaris 10

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

You need to take this to your local Sun Solution Centre, rather than 
posting to this mailing list (which is for opensolaris, not Solaris 10).


Solaris 10 kernel 118833-36 is now really old, and whilst probably not 
related directly to your problem, does give a clue as to how currently 
patched your system may be. SunSolve shows quite a few patches for CDE 
on Solaris 10. The Sun Support guys would be able to deal with this for 
you, as well as sifting through the relevant patches and/or 
configuration issues.


Regards,
Brian


Kunal wrote:

I am facing some issue on Solaris 10 (SPARC 5.10 Generic_118833-36). The
issue is when I try to connect/login through CDE it hangs (hangs at login
screen). I tried connecting thourgh VNC client also but that also not
helped. I had done no configuration change or modified any kernel parameter
but this suddenly happened on my Solaris 10 server. This machine is in
production.

Below is the error message that appears when I try to login from CDE
environment on this server

"/usr/dt/bin/ttsession[1110]: [ID 161973 daemon.error] t_connect(): An event
requires attention".

Also if I try to open Gnome/Java environment on this machine it works fine.
The only issue is with the CDE session. The CDE vesion installed is 1.6 on
my server.
I tried googling this error but most of the search suggested to install
patch 119955-05 for CDE but this also not helped.

Below is the log file that I found ~/.dt/startlog


bash-3.00# cat startlog
--- Wed Sep 30 09:01:36 IST 2009
--- //.vnc/xstartup starting...
--- starting /usr/dt/bin/dthello &
/usr/dt/bin/dthello: display :1.0 doesn't know font -dt-interface
system-medium-r-normal-m*-*-*-*-*-*-*-*-*:
--- Xsession started by
--- setting font path...
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing //.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1001.swupnot...
--- sourcing /usr/dt/config/Xsession.d/1099.br...
//.vnc/xstartup[624]: date.: not found
--- could not read //.profile
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /dev/null
--- DTSOURCEPROFILE is 'true' (see //.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/9
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
You have new mail.
/usr/dt/bin/ttsession[27308]: starting
The Sun Notification Application is disabled, To enable it,
use the Preferences menu in the Sun Update Manager.


Else there are no logs that I found in .dt. Please help.

Regards, kunal
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] "2-button simulating middle-click" feature stops working mid-session?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Hi Alan,

Finally, this just happened to me again.
FWIW, I updated to snv_124 yesterday, and with no external mouse plugged 
in, I see the "(II) 3rd Button detected: disabling emulate3Button" line 
in /var/log/Xorg.0.log (full file attached).


I've been using the system for approx 1 hour so far, and only using the 
touchpad.

What further diagnosis would I need before filing a bug?

Thanks,
Brian


Alan Coopersmith wrote:

Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:
  

I have a Toshiba Tecra M10, and the mouse pad has two buttons.
Most of the time, I can highlight some text using the left button (click
and drag as normal), then I can press both buttons together to paste in
a target window (i.e. simulating the middle click).

This mostly works (and I usually copy-n-paste this way), but at some
point during my login session, it stops working, and instead I only ever
get the right-click context menu.



The default configuration of Xorg is to recognize left+right as emulating
a third button until/unless a third button is actually clicked, at which
point it assumes you don't need it any more.

Unfortunately, on builds before about 119, the default on Solaris is to
open /dev/mouse and have the kernel combine all mouse like devices into
a single output stream, so a click on an external mouse will disable it
on all mice.   With the switch to hal-based input hotplug in 119 and later,
each mouse is individually opened, so it should track each one seperately.

  

I've not worked out what changes this, and I've not got a clue where to
start diagnosing this.



Any messages in /var/log/Xorg.0.log about disabling 3 button emulation?

  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG


X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: SunOS 5.11 i86pc 
Current Operating System: SunOS opensolaris 5.11 snv_124 i86pc
Build Date: 16 September 2009  03:28:27PM
 

Solaris ABI: 64-bit
SUNWxorg-server package version: 6.9.0.5.11.10100,REV=0.2008.10.16
SUNWxorg-graphics-ddx package version: 6.9.0.5.11.10100,REV=0.2008.10.16
SUNWxorg-mesa package version: 6.9.0.5.11.10100,REV=0.2008.10.16
Before reporting problems, check http://sunsolve.sun.com/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 30 09:35:47 2009
(II) Loader magic: 14e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on solaris
(--) using VT number 2

(--) PCI:*(0:0:2:0) 8086:2a42:1179:0009 Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller rev 7, Mem @ 0xff40/4194304, 
0xe000/268435456, I/O @ 0xcff8/8, BIOS @ 0x/65536
(--) PCI: (0:0:2:1) 8086:2a43:1179:0009 Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller rev 7, Mem @ 0xc000/1048576, BIOS @ 
0x/65536
(WW) could not get frame buffer identifier from /dev/fb
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier  "Builtin Default intel Device 0"
Driver  "intel"
EndSection
Section "Screen"
Identifier  "Builtin Default intel Screen 0"
Device  "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default i810 Device 0"
Driver  "i810"
EndSection
Section "Screen"
Identifier  "Builtin Default i810 Screen 0"
Device  "Builtin Default i810 Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default vesa Device 0"
Driver  "vesa"
EndSection
Section "Screen"
Identifier  "Builtin Default vesa Screen 0"
Device  "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default fbdev Device 0"
Driver  "fbdev"
EndSection
Section "Screen"
Identifier  "Builtin Default fbdev Screen 0"
Device  "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
   

Re: [osol-discuss] Shift Page-UP

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Jürgen Keil wrote:

In linux, I can press Shift Page-Up on the console to scroll back the page.
This is handy when looking at log files on the console or output from tail -f [file] . 

However, I cant seem to be able to do it in open-solaris. 



In a gnome-terminal?  Shift-PageUp works for me...
  


I suspect we are talking about the console (i.e. the text mode before 
gdm/gnome fires up) rather than a gnome-terminal or any other graphical 
terminal emulator. Paul - can you please confirm this?


Does the  recently-added virtual console feature support any kind of 
scrollback like this? I've not played with it myself, and I can't see 
anything about keeping history or scrolling back in the vt(7I) man page.


Regards,
Brian

--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] "2-button simulating middle-click" feature stops working mid-session?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Alan Coopersmith wrote:

Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:
  

I have a Toshiba Tecra M10, and the mouse pad has two buttons.
Most of the time, I can highlight some text using the left button (click
and drag as normal), then I can press both buttons together to paste in
a target window (i.e. simulating the middle click).

This mostly works (and I usually copy-n-paste this way), but at some
point during my login session, it stops working, and instead I only ever
get the right-click context menu.



The default configuration of Xorg is to recognize left+right as emulating
a third button until/unless a third button is actually clicked, at which
point it assumes you don't need it any more.

Unfortunately, on builds before about 119, the default on Solaris is to
open /dev/mouse and have the kernel combine all mouse like devices into
a single output stream, so a click on an external mouse will disable it
on all mice.   With the switch to hal-based input hotplug in 119 and later,
each mouse is individually opened, so it should track each one seperately.
  


I don't often plug in an external mouse, and I've certainly noticed it 
disabling the emulation without an extra mouse. There are actually two 
pointing devices on the Tecra M10 I have - the the touchpad and the 
little blue joystick between the G-H keys. There are two sets of buttons 
(presumably for use with your preferred pointing device), but I've found 
that I can use each set interchangeably without loss of the emulation.


  

I've not worked out what changes this, and I've not got a clue where to
start diagnosing this.



Any messages in /var/log/Xorg.0.log about disabling 3 button emulation?

  


I'll check when this next happens.

Is there something wrong which needs diagnosing here, or should I simply 
apply the setting to xorg.conf from later in the thread and keep quiet?


(oh and can you remind me the current way to generate the "default" 
xorg.conf - is it still "Xorg -configure"?)


Thanks,
Brian


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Problem using snoop

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

My apologies - I've remembered this wrong. Serves me right for not 
testing it first :-)


Jürgen Keil wrote:

man snoop:

 -a   Listen to packets on /dev/audio (warning: can be noisy).

That's why you get no output on screen.



snoop -a produces both a packet dump on stdout,
and produces noise on the audio device.
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] "2-button simulating middle-click" feature stops working mid-session?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I have a Toshiba Tecra M10, and the mouse pad has two buttons.
Most of the time, I can highlight some text using the left button (click 
and drag as normal), then I can press both buttons together to paste in 
a target window (i.e. simulating the middle click).


This mostly works (and I usually copy-n-paste this way), but at some 
point during my login session, it stops working, and instead I only ever 
get the right-click context menu.


I've not worked out what changes this, and I've not got a clue where to 
start diagnosing this.


Can anybody lend a hand in helping diagnose this?

My usual applications are Firefox, Thunderbird, pidgin, gnome-terminals 
and a couple of java applets (although I'm fairly sure I can see this 
problem without launching any stand-alone java apps). Once it's 
happened, if I close all apps, the problem remains, so it is not the 
running presence of an app which is causing this.


If I plug in a USB mouse, the middle button pastes the highlighted text 
as expected. Also (somewhat strangely), if I press both USB mouse 
buttons together, it simulates the middle correctly! It only seems to be 
the builtin mouse pad buttons which "break" in this fashion.


Thanks,
Brian

--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Sun Fire T1000

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

What happens when you type "go" when you find one in this state? Failing 
that, try "sync" and see if it starts panicking.
Check the logs on the SP for any power events, reset activity, "send 
break" requests, failures, etc...


Admittedly, these not likely across multiple systems, but worth 
checking. Doesn't explain why they are at the ok prompt though...


Commands on the SP like "consolehistory" and "showlogs" should help you.

Incidentally, if "go" reports "no program active" or similar, but "sync" 
starts a panic, this is usually a clue that "init 0" or equivalent was 
run inside the OS to shut the system down gracefully. Check the messages 
file for a "Syncing filesystems... done" entry just prior to booting up 
again.



Brian


camps support wrote:

Every so often on multiple servers I have lost connection then when I connect 
to the serial port it is at the ok prompt.  No dumps or anything to speak of.  
Has anyone experienced this issue with the T1000?

I do not have this issue with any of the T2000 or M-series servers on hand.

Thanks,
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] osol 2009.06 console terminal mis-behaving

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

If by "the shell" you mean the default shell for root, then on OSol, 
you'll find this is bash instead of the traditional Bourne shell on 
solaris 10:


opensolaris# getent passwd root
root:x:0:0:Super-User:/root:/usr/bin/bash

The terminal handling may be different. A quick test shows that bash 
(like tcsh and possibly csh IIRC) will print the command just before 
executing it, even it was in the "typeahead" buffer:


$ bash
bash-3.2$ sleep 10
echo hello   <= typed while sleep was executing
bash-3.2$ echo hello   < reprinted by bash, not typed.
hello

A quick workaround would be to execute the command /usr/xpg4/bin/sh 
which seems to behave differently (although still may not be what you need):


$ /usr/xpg4/bin/sh
$ sleep 10
echo hello < typeahead
$ hello  < command output, command not re-echoed

(There may also a bash setting to change this behaviour - I'm just not 
aware of one).


Of course it may be better to set the shell prompt to something unique 
(perhaps a random string) during the test, and each command is only sent 
when the "unique" prompt is seen after the output from the previous 
command. Then it becomes less dependant on the shell implementation, and 
your test has better control over the timing of commands and the output 
it needs to check.


As for the backspace issue, I don't know. However, trying with a 
different shell, or perhaps a different $TERM setting may help. This may 
simply be bash's way of clearing a line when printing the prompt if 
typeahead exists (or perhaps it always does this?).


HTH,
Brian



Wing Choi wrote:


I test the console behavior with OSOL and came across something odd.
The automated testcases executes remotely by connecting to the machine's
virtual console thru the SC. It executes series of shell commands on the
console using Expect to help parse the output.  From reviewing the logs,
it appears the console terminal is putting out extraneous output that 
is interferring

with the return parsing in the testsuite.

Here's a snippet of one log:
# /usr/bin/ls /var/opt/SUNWldm/core  
/var/opt/SUNWldm/core: No such file or directory
# echo "StAtUs${?}StAtUs"
StAtUs2StAtUs
# /opt/SUNWldm/bin/ldm 
list-domain  

NAME STATE  FLAGS   CONSVCPU  MEMORY   UTIL  UPTIME
primary  active -n-cv-  SP  8 2G   0.8%  7h 7m
# echo "StAtUs${?}StAtUs"
StAtUs0StAtUs
# /usr/bin/ls 
/var/opt/SUNWldm/core 

/var/opt/SUNWldm/core: No such file or directory
# echo "StAtUs${?}StAtUs"
StAtUs2StAtUs
# /usr/bin/ls 
/var/opt/SUNWldm/core 

/var/opt/SUNWldm/core: No such file or directory
# echo "StAtUs${?}StAtUs"
StAtUs2StAtUs
# echo "StAtUs${?}StAtUs"
StAtUs0StAtUs
# /usr/bin/ls //core# /usr/bin/ls 
//core

//core: No such file or directory
# echo "StAtUs${?}StAtUs"
StAtUs2StAtUs
# /usr/bin/ls //core# /usr/bin/ls 
//core

//core: No such file or directory
# echo "StAtUs${?}StAtUs"
StAtUs2StAtUs
# /usr/bin/df -k /  # /usr/bin/df 
-k /

Filesystemkbytesused   avail capacity  Mounted on
rpool/ROOT/opensolaris
61415424 4552800 49551256 9%/
# echo "StAtUs${?}StAtUs"
StAtUs0StAtUs
# /usr/bin/ls //core# /usr/bin/ls 
//core

//core: No such file or directory
# echo "StAtUs${?}StAtUs"
StAtUs2StAtUs
#

Two issues that I see here:
It appears that the command "df -k" was sent to the
console and it was reflected twice. The other one is the additional 
spaces after some of the commands and then

what looks like a string of backspaces to take them back.

I've figured out that in the old sh, the queued shell commands are not 
typed again
into the terminal in between the first command and the queued 
command's execution.
However, in the new shell in osol, it appears the queued shell command 
appears
in the terminal again - in effect appearing twice in the terminal.  
But I can't figure

out the extra spaces and then backspaces...

Any ideas?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss ma

Re: [osol-discuss] no user mount of nfs filesystem

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Use the automounter.  :-)

Looks like we can use a nice direct map entry as we have discussed 
before. The system will automatically mount it upon first access (by any 
user).


This in /etc/auto_direct on the client should do:
/vzfsTest  vzfs:/vzfsTest

Then, after "svcadm restart autofs" (or run "/usr/sbin/automount"), you 
should simply be able to "cd /vzfsTest" as any user on the client, and 
the directory should be mounted for you.


Personally, I would also make sure the mount point on the client is mode 
777, and owned by root. Non-777 permissions can cause strange issues. 
I'm not sure about non-root ownership.


Regards,
Brian

Harry Putnam wrote:

Summary:
What do I need to do so that my user can mount an nfs filesystem being
offered by another osol OS?

Details:
The server (osol 2010.10 b118) created a zfs fs with sharenfs=on (no
special options)

mounted it at /vzfsTest

chown 1000:15 /vzfsTest (reader:wheel)
chmod g+s /vzfsTest (set-gid)

On a client (osol 2009.06 b111):
user reader is also uid 1000 gid 15 (reader:wheel)

mkdir /vzfsTest
chown 1000:15 /vzfsTest

On the client.. as user reader (uid 1000)
 mount -Fnfs vzfs:/vzfsTest /vzfsTest
  nfs mount: insufficient privileges



___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
  


--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] ssh issue with b118

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

This sounds like bug 6853997 - see 
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6853997


Try the workaround.
If so, it's fixed in build 119.

Brian


Rob McMahon wrote:
I've just updated to b118 (from 117), and something nasty seems to 
have happened to ssh. Each connection to a known host comes back with, 
e.g.,


The authenticity of host '�t
P� ()' can't be established.
RSA key fingerprint is 
Are you sure you want to continue connecting (yes/no)?

I know the hostname and ip are correct. I say `yes', and all works 
fine. A `cat -vet' of ~/.ssh/known_hosts shows


> cat -vet ~/.ssh/known_hosts | awk '{print $1}' | tail -3
M-(t^K^HPM-(^F^H
^P
M-(t^K^HPM-(^F^H
>

(Older entries look like `hostname,ip-address'.) The two identical 
mangles "hostnames" were for two completely different hosts.


Anyone else seen this ?

Rob



--
Brian RuthvenSun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] ssh-add and nevada b115

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I use multiple keys for different hosts, but I specify which key or 
"identity" to use in my ~/.ssh/config file on a per-host basis, e.g.:



Host myhost1
   IdentityFile ~/.ssh/six_dsa

Host myhost2
   IdentityFile ~/.ssh/half-a-dozen_dsa


Then, when I do "ssh myhost1", it will pick up the six_dsa file for the 
key, not a random one from the output of "ssh-add -l".


I can't spot anything in either ssh(1), ssh-add(1), ssh-agent(1) or 
ssh_config(4) man pages to say that the order in which keys are added is 
preserved, so I would suggest using the IdentityFile keyword in your 
config file to eliminate any guesswork that ssh has to do.


Regards,
Brian



jason wrote:

I am running into a problem with a ssh-add functionality in nevada b115.  I had 
a script that would do the following:

ssh-add ${HOME}/.ssh/*.[rd]sa

In previous versions of nevada, this would run fine, yet for b115, the order of files 
found via the ${HOME}/.ssh/*.[rd]sa is not kept.  This presents problems when ssh 
connections are made to other servers since the keys I want presented first, are not 
getting presented first.  This is confirmed when doing an "ssh-add -l".

Is there a way to control the key order so that the keys I want to have tried 
first, are used.  I thought that the order in which I added keys, would 
translate to the order in which those keys are presented to the remote server, 
yet it looks like this ordering is not kept.

Upon multiple tries of the "ssh-add ${HOME}/.ssh/*.[rd]sa" the results seem to vary.  I 
have to keep trying until I get the "ssh-add -l" to display the order I need.

Any insight would be greatly appreciated.
  


--
Brian RuthvenSun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[osol-discuss] Missing "pkg authority" references in man pages and cmd usage?

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

I may be missing an announcement or something, but it would seem that 
neither the man page nor the usage output from pkg mention the authority 
and set-authority sub commands.


They still work, so I can only assume one of four things:
   1) I'm going blind :-) and they are documented in a different place
   2) They have been deprecated in favour of something else (possibly 
the publisher keyword?)

   3) An oversight/omission
   4) They have been removed from the man page and usage to be a 
"hidden" admin interface?



I'm running snv_111a at present. I've checked snv_109, and the relevant 
sections were present in the man page.


Can anyone shed any light on this for me please?

Thanks,
Brian

--
Brian RuthvenSun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] snapshot creating & destroying scripts

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Sounds like Time Slider would help you out here:
http://blogs.sun.com/erwann/entry/zfs_on_the_desktop_zfs

Brian

Edward Ned Harvey wrote:


I’m building a fileserver, and want to start using snapshots on it. 
From the top of my head, I’m thinking I want to do something like 
snapshot once an hour for the most recent 24 hours, once a day for the 
most recent week, and once a week for the most recent month. I can put 
the effort into developing something like a cron script for this 
purpose, but I bet people have something they’d be willing to share.


Does anybody have any scripts they’d like to share with me, or want to 
influence me in any other direction?


No disclaimers needed if you’ve got some homegrown thing. I’m going to 
read it and understand it and probably modify it before I use it. So 
it won’t accidentally delete anything, trust me.


Thanks, ttyl…



___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
  


--
Brian RuthvenSun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] What's wrong? gedit from binaries

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

Quick workaround is to set:

$ LIBS="-lsocket -lnsl"
$ export LIBS

and re-run configure.
I've had to do the same recently. Seems we changed something in the 
linker to require explicit libraries.


Regards,
Brian


Oscar del Rio wrote:

norge wrote:

gmake[4]: Entering directory 
`/export/home/gothic/downloads/gedit-2.26.1/gedit'
/bin/sh ../libtool --tag=CC   --mode=link cc  -g -export-dynamic 
-no-undefined -export-symbols-regex "^[[^_]].*"   -o gedit gedit.o 
libgedit.la -R/usr/X11/lib -R/lib -L/usr/X11/lib -L/lib -lxml2 
-lgthread-2.0 -lpthread -lthread -lgtksourceview-2.0 -lgtk-x11-2.0 
-lgdk-x11-2.0 -lXi -lXext -lX11 -latk-1.0 -lpangoft2-1.0 
-lgdk_pixbuf-2.0 -lm -lmlib -lpangocairo-1.0 -lgio-2.0 -lXrandr 
-lXcursor -lXcomposite -lXdamage -lcairo -lXfixes -lpango-1.0 
-lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgconf-2 
-lglib-2.0   -R/usr/X11/lib -L/usr/X11/lib -lSM -lICElibtool: 
link: cc -g -o gedit gedit.o  ./.libs/libgedit.a -L/usr/X11/lib 
-L/lib -lxml2 -lgthread-2.0 -lpthread -lthread -lgtksourceview-2.0 
-lgtk-x11-2.0 -lgdk-x11-2.0 -lXi -lXext -lX11 -latk-1.0 
-lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lmlib -lpangocairo-1.0 -lgio-2.0 
-lXrandr -lXcursor -lXcomposite -lXdamage -lcairo -lXfixes 
-lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 
-lgconf-2 -lglib-2.0 -lSM -lICE -R/usr/X11/lib -R/lib

Undefinedfirst referenced
 symbol  in file
bind
./.libs/libgedit.a(bacon-message-connection.o)  (symbol belongs to 
implicit dependency /lib/libsocket.so.1)
accept  
./.libs/libgedit.a(bacon-message-connection.o)  (symbol belongs to 
implicit dependency /lib/libsocket.so.1)
listen  
./.libs/libgedit.a(bacon-message-connection.o)  (symbol belongs to 
implicit dependency /lib/libsocket.so.1)
socket  
./.libs/libgedit.a(bacon-message-connection.o)  (symbol belongs to 
implicit dependency /lib/libsocket.so.1)
connect 
./.libs/libgedit.a(bacon-message-connection.o)  (symbol belongs to 
implicit dependency /lib/libsocket.so.1)


Configure or libtool should have added -lsocket -lnsl to the linking 
libraries.  See "man -s 3socket socket" or "man -s 3socket bind" etc.


SYNOPSIS
 cc [ flag ... ] file ... -lsocket  -lnsl  [ library ... ]

You probably have to "fix" the configure script or the Makefiles it 
created.

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


--
Brian RuthvenSun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] [indiana-discuss] error: Failed to allocate internet-domain X11 display socket

[Brian Ruthven - Solaris Network Sustaining - Sun UK]

That bug (or rather the bug it was closed as a duplicate of) is 
technically S10-only because nevada (and hence opensolaris) plumbs in an 
IPv6 interface by default.


Do you have the ::1 "interface" plumbed in and up? Something like this:

lo0: flags=2002000849 mtu 
8252 index 1

   inet6 ::1/128

If not, then you can be exposed to this bug on OpenSolaris.

Regards,
Brian

solarg wrote:

hello all,
i have this problem into a zone in os2008.11 (b101)
This seems to be related to bug:
http://bugs.opensolaris.org/view_bug.do;jsessionid=2461d3b92d92e9e23ef6f8e8ee?bug_id=6732084 



but this bug talks only solaris 10.

Anybody else has this problem?

thanks in advance,

gerard

___
indiana-discuss mailing list
indiana-disc...@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


--
Brian RuthvenSun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org