headers
Adrian Saul | 1 Jul 13:04

Re: Persistent binding of devices in Solaris 10 x86_64


How do you mean it remembers the previous file name?

Do you man /dev/changers/≤dev> stays for the removed device and that the 
new entry is the next device?  Can I ask why it is a problem other than 
purely cosmetic naming?

Its certainly possible to fix - just change the symlinks in /dev.

FWIW I think the persistant naming in Solaris is one of its most admin 
friendly features.  You dont have to worry that rebooting the box will 
cause your tape devices to suddenly reorder because a silo was playing 
up, or that booting with a USB device attached causes a panic because 
your SCSI disks are out of order (*cough* damn linux *cough*)....

Nirmal B wrote:
> 
> 
> I am trying to configure tape library robotics with
> Solaris 10 x86_64. It works fine for the first time.
> Then if I connect another tape library, the OS seems
> to remember the previous device file name even if I do
> a kernel reconfiguration boot.
> 
> Do I have to delete the old /devices entry for tape
> library robotics (media changer)? Or just deleting the
> corresponding entry in /etc/path_to_inst file would be
> ok before the kernel reconfiguration?
> 
> I was trying with devfsadm -C (for cleanup) which
(Continue reading)

Permalink | Reply | 2 comments |
headers
lonebandit_usa | 1 Jul 13:45

boot-archive

A few months ago, I posted issues about shutting down and having issues 
on boot with a messed up boot archive...obviously I am not alone :-(

However I was wondering if there was any way to incorporate
this command "/sbin/bootadm -a update_all" into any 
shutdown/reboot/poweroff sequence...

Like in *BSD we have /etc/rc.shutdown...some place I could toss this 
command so its -always- run at reboot/shutdown.

It might help - cant hurt!?

-JD

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com
Permalink | Reply | 0 comments |
headers
maybird1776 | 1 Jul 13:51
Picon
Favicon
Gravatar

Re: P35 G33 motherboards anyone?

--- In solarisx86 <at> yahoogroups.com, Mariusz Zynel <sysadm@...> wrote:
>
> Peter Evans wrote:
> > Has anyone testdriven these boards with solaris/opensolaris/etc?
> > The g33 media board has six sata on a micro atx board, which sounds
> > ideal for a smallcutefileserver.

http://www.intel.com/products/motherboard/DG33TL/index.htm
"The Intel Desktop Board DG33TL Media Series in the uATX form factor 
delivers improved performance and capabilities for multimedia creation 
and enjoyment." 

This is one of the motherboards I'm reviewing for the Solaris HCL. All
of the basic devices work for a file server project. The motherboard 
supports up to 8GB RAM with a 1Gb NIC.

You also have a decent Sigmatel STAC9271D High-Def audio chip.

~ Ken Mays

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com
Permalink | Reply | 1 comment |
headers
Laurent Blume | 2 Jul 00:09
Favicon

Re: (Solved) Re: Pidgin 2.0.2 not working

It's actually a theme issue, some of them make Pidgin crash:
http://developer.pidgin.im/ticket/842

Hope Sun will fix that soon. Probably, since Pidgin will have to get in 
S10. The current Gaim is too old, notwithstanding the legal issue with 
the name.

Laurent

Laurent Blume a écrit :
> I've seen that, it's the pkg-config from Solaris' Glib that contains 
> them. SunCC only, GCC doesn't like it.
> I also built using Blastwave GCC 4 and Glib/GTK+, but I get the exact 
> same result. Weird.
> 
> If that's not a problem for you, Could you send me a binary so I can try 
> with a known working one?

--

-- 
/ Leader de Projet & Communauté    | I'm working, but not speaking for
\ G11N   http://fr.opensolaris.org | Bull Services http://www.bull.com
/ FOSUG  http://guses.org          |

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bravo Echo | 1 Jul 15:02
Picon
Favicon

CERC SATA 2S

Hi all;

If you have any information about CERC SATA 2S driver on Solaris10, please let me know.  I am using DELL
PowerEdge 800 and CERC 2S is onboard controler.  But I can not find driver for this.  

If you have special driver or develop it, I appreciate :)

Best regards,

       
____________________________________________________________________________________
Got a little couch potato? 
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz 

[Non-text portions of this message have been removed]

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com
Permalink | Reply | 9 comments |
headers
tamino1981 | 2 Jul 08:33
Picon
Favicon

How to get the previously date

Hi all,

I am new to solaris, 
could any one tell me how to get the previously date
using command line or shell script?
what about specified date?

Thanks in advance.

Regards,
Changer

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com
Permalink | Reply | 1 comment |
headers
virdi_deep | 2 Jul 10:41

Re: How to get the previously date

use the following command:
history

regards
deepti

--- In solarisx86 <at> yahoogroups.com, "tamino1981" <tamino1981@...> 
wrote:
>
> Hi all,
> 
> I am new to solaris, 
> could any one tell me how to get the previously date
> using command line or shell script?
> what about specified date?
> 
> Thanks in advance.
> 
> Regards,
> Changer
>

Please check the Links page before posting:
    http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86 <at> yahoogroups.com
UNSUBSCRIBE:  solarisx86-unsubscribe <at> yahoogroups.com
Permalink | Reply | 0 comments |
headers
Bravo Echo | 1 Jul 03:09
Picon
Favicon

some questions on Sol10

Hi all;

I have some questions about ZFS and resistration procedure.

First of all,
I want to do mirror 2 hard drives (c1d0 and c2d0).  I tried following command to mirror.
1. zpool create pool1 mirror c1d0 c2d0 (also tried to do c1d0s0 c2d0s0)
2. zpool mirror pool1 c1d0 c2d0
But I can not do the mirror because / and swap slice is already mounted.
How can I do the mirror with ZFS??  Or I have nothing to use volume manager instead??

Second,
I could resistration at the first installation, but I reinstalled Solaris10 again on the same hardware. 
And I can not resister.  This is very important step because of security patch update.   I guess that this
hardware ID and details have been already resistered and still remain SUN database?!  
Please see the log file bellows.
-----------------------------------------------------------------------------------------------------
Jul  1 09:37:35 dns1 cacao[1114]: [ID 702911 daemon.warning]
com.sun.scn.jmx.impl.AbstractComponent.log : SCNClientConfigImpl.activate("Register the
Solaris software without choosing an update option") -- module unlocked
Jul  1 09:37:41 dns1 cacao[1114]: [ID 702911 daemon.warning]
com.sun.scn.jmx.impl.AbstractComponent.log : SCNClientConfigImpl.deactivate("Register the
Solaris software without choosing an update option") -- module locked
Jul  1 09:45:49 dns1 cacao[1114]: [ID 702911 daemon.warning]
com.sun.scn.service.BaseServiceClient.dumpThrowable : XYXYXY
Jul  1 09:45:49 dns1 java.rmi.RemoteException: HTTP
\343\203\210\343\203・\203潟\202鴻\203\235\343\203若\203\210\343\202・\203・\203\274:
java.net.SocketTimeoutException: connect timed out; nested exception is:
Jul  1 09:45:49 dns1    HTTP
\343\203\210\343\203・\203潟\202鴻\203\235\343\203若\203\210\343\202・\203・\203\274:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nirmal B | 1 Jul 14:51
Picon
Favicon

Re: Persistent binding of devices in Solaris 10 x86_64

I forgot to mention that the /devices entry for the
new medium changer (second one) does not get created.
I need to know the device file name (in /devices/...
format) for the second media changer to change the
symlink in /dev. There is only one physical device
reference in /devices which is that of the first media
changer. I have disconnected it and don't want to use
it for the time being. 

So, the question is do I have to remove the old
/devices/... files of the first changer (using rm) or
just the corresponding entry in /etc/path_to_inst file
or both before doing a kernel reconfiguration boot? Is
this the recommended procedure or should I use
devfsadm  with a cleanup option? Can anyone clarify
this?

Persistent binding is a useful feature indeed. But if
this is what is meant by persistent binding, I will
have to disable this feature in my case --- just to
get Solaris x86 forget about the previous device and
create physical device files for the new device.

--- Adrian Saul <asaul <at> home-box.ods.org> wrote:

> 
> How do you mean it remembers the previous file name?
> 
> Do you man /dev/changers/≤dev> stays for the removed
> device and that the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Adrian Saul | 2 Jul 13:13

Re: Persistent binding of devices in Solaris 10 x86_64


No, there is no need to remove the old device to populate a new one.

What is the old device path, and what do you expect the new one to be?

Nirmal B wrote:
> 
> 
> I forgot to mention that the /devices entry for the
> new medium changer (second one) does not get created.
> I need to know the device file name (in /devices/...
> format) for the second media changer to change the
> symlink in /dev. There is only one physical device
> reference in /devices which is that of the first media
> changer. I have disconnected it and don't want to use
> it for the time being.
> 
> So, the question is do I have to remove the old
> /devices/... files of the first changer (using rm) or
> just the corresponding entry in /etc/path_to_inst file
> or both before doing a kernel reconfiguration boot? Is
> this the recommended procedure or should I use
> devfsadm with a cleanup option? Can anyone clarify
> this?
> 
> Persistent binding is a useful feature indeed. But if
> this is what is meant by persistent binding, I will
> have to disable this feature in my case --- just to
> get Solaris x86 forget about the previous device and
> create physical device files for the new device.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane