mmmmn

版权声明：转载时请以超链接形式标明文章原始出处和作者信息及本声明
http://mmmmn.blogbus.com/logs/1881041.html

1、>I have installed "all" the Solaris 9 software on the 9/05 distribution
>CDs, including companion CDs.  I see via NMAP that TCP port 1720 is
>listening.  A netstat -a does not show the port listening.  If I use
>the old "telnet to port 1720" it does connect...I just wanted to
>validate NMAP...I should never have doubted NMAP... ;-)

Try "rpcinfo -p"

>First part of my question is why is it that port 1720 does not show up
>as listening via netstat -a ?  Is there a global listener like RPC or
>something?

I'd still expect that to show up with netstat....

>Second part is does anyone know where to disable the H.323/port 1720
>processes or listener?  Please share :-)  /etc/inetd.conf dos not list
>port 1720?  I can not find anything on H.323 in /etc/init.d start up
>files...

I'd be very surprised if it was H.323.

Casper

2、> mistake:
>     /rmdisk/unamed_rmdisk0 ....  /rmdisk/unamed_rmdisk0
>   should be
>   /rmdisk/unamed_rmdisk0 ....  /rmdisk/unamed_rmdiskN
>
> "jerry" <jerry@xxxxxxxxxx> wrote in message
> news:do88p4$lon$1@xxxxxxxxxxxxxxxxxxx
>> Is it possible to connect multiple USB drives through a hub and have them
>> all mount, i.e.
>> /rmdisk/unamed_rmdisk0 ....  /rmdisk/unamed_rmdisk0
>>  Am running solaris 10 on a Blade2K and Blade1500, and am having touble
>> where all the disks show up, but they are symbolic links to the same
>> place
>> /rmdisk/disk0 -> unamed_rmdisk ... /rmdisk/diskN->unamed_rmdisk.
>>
>
>
     Well found out the answer to the problem, (if anyone is really
interested)  when you purchase USB disks check the disk labels, the ones we
purchsed had a space in the disk label  "WD abc "  "WD def" etc. removed the
space in the disk label  and everything works, can now run multiple USB
disks at the same time with Solaris10

3、A number of times, I've needed to install a COTS package that wanted a
specific OS version even though a newer version would work, too.  Most
times, just editing an install script is good enough.  But a few COTS
packages were harder to fool.  The web didn't have any easy answers, so
I figured out how to do this with ADB.  Here's a script:

http://lug.umbc.edu/~mabzug1/solaris_change_os_version.html

After seeing this, someone on my local SAGE group came up with a
PRELOAD hack to do a similar thing; it's probably safer than ADB:

http://www.bstern.org/libuname/

Oh yea, I can make my Solaris machine a Linux machine..or even Windows if

that matters.

http://www.roqe.org/sloggi/

-----
> > A number of times, I've needed to install a COTS package that wanted a
> > specific OS version even though a newer version would work, too.  Most
> > times, just editing an install script is good enough.  But a few COTS
> > packages were harder to fool.  The web didn't have any easy answers, so
> > I figured out how to do this with ADB.  Here's a script:
> >
> > http://lug.umbc.edu/~mabzug1/solaris_change_os_version.html

> Here's how to do it with Solaris 10 and DTrace. :-)
>
> http://blogs.sun.com/roller/page/jonh/20050321#it_s_been_a_long

Thanks!  I've added your link and the "sluggi" link to the webpage.

- Morty

4、I am working on a project to move our product media from CDs to DVD. We

currently use 3 CDs as part of our installation.

CD1 and CD2 - Solaris 9 OS CDs.
CD3 - Our product application CD.

Our installation process works this way...

1) We first install Solaris 9 (modified CD1 to be self-bootable) using
CD1 and CD2
2) Then we insert the CD3 (App CD) to install our applications.

I am trying to work on moving all the 3 CD contents to a DVD and here
is what I have gotten so far.

1) I took the Solaris 9 DVD and created slice 0 - slice 5 by using
mkisofs/dd etc. In essence I have created a modified ISO that can boot
Solaris 9.

2) I need to figure out a way of adding my application contents to the
DVD. The slice 0 that I extracted from the Solaris 9 DVD does not seem
to have enough room to hold my application data (after removing the
unwanted contents such as 1of2_CDDoc etc).

I need suggestions on how I can expand the size of slice 0 (I will have

to re-create the VTOC and the starting cylinder etc of slices 1 - 5)
and then put in my app contents as part of slice 0. After that I want
to recreate the ISO. The net result would be a DVD that will install
Solaris 9 and also my application. If slice 0 is not the place to put
this, could I resize slice 5 to add my app data ?

Any help is appreciated.

Thanks Venkat

I wanted to do the same thing too... Here is my plan
(1) Run prtvtoc on the DVD, you need to copy down the size & offset for every

partition. You need to stop vold before you can run provtoc.
(2) Run dd/whatever to extract your slice.
(3) The vtoc is the first 512 bytes of slice 0, dump it to a file call

vtoc.dd. I like dd if=slice.s0 of=vtoc.dd bs=512 count=1
(4) do a hex dump on vtoc.dd. I like od -t x1 vtoc.dd
Now is the fun part, the numbers that you got from part (1) are somewhere in

the hex dump in part (4). You need to convert the numbers to hex, then scan

through the hex dump to find them.
(5) suppose you change the size of any slice (in your final product), then

you need to adjust the number accordingly. You can manually fix vtoc.dd to

get the correct numbers in there.
(6) do what you need to do to get all your software in. Put all the slices

together in a new image
(7) put the fixed vtoc as the first 512 bytes of the new image
(8) Burn it. Run prtvtoc on the new DVD to test it. Mount it... whatever.

Make sure you see all slices... very much like the install DVD. If you have

this much, I think your new DVD will install just fine.

Good luck and please post back your results.

5、> ohaya wrote:
> > Hi,
> >
> > I posted about this problem a couple of days ago.  I am trying to use
> > flarcreate to backup a system image.  This time, I'm trying to save the
> > image to a USB hard drive, mounted on /foo.  The line I'm using to run
> > flarcreate is:
> >
> > flarcreate -n myimage.flar -c -S -R / -x /foo/myimage.flar
> >
> > I've run this before on this system, without errors, but this time, I
> > had installed Directory Server 5.2 before trying to do the flarcreate.
> >
> > I did an "init 0" and then "boot -s" to boot into single-user mode.
> > Then I run the flarcreate command line above.
> >
> > The errors I'm getting are:
> >
> > cpio: "/var/Sun/mps/admin-serv/tmp/iwswatchdog.605" ?
> > cpio: "/var/Sun/mps/admin-serv/tmp/iwsadmin.606" ?
> > cpio: "/var/Sun/mps/admin-serv/tmp/iwswatchdog.286" ?
> > cpio: "/var/Sun/mps/admin-serv/tmp/iwsadmin.287" ?
> >
> > Can anyone tell me what is causing these errors, and how to eliminate
> > them?
> >
> > Also, what are the ".xxx" numbers at the end of the error lines?
> >
> > I'm really worried that these backups are not good.
> >
> > Thanks,
> > Jim
>
> The 605 means the Directory Server was running with the PID 605
>
> The only thing that may cause you problems is that you're missing the
> shutdown script of DS and, you're bringing the DS down the hard way
> (with, it's never a good thing on a database).
>
> Those files are deleted every time you shutdown the DS and are created
> when you start it. Because they are special files in unix, they don't
> get caught in backups, cp, mv and stuff. Don't worry about that (but do
> worry about the hard shutdown you're doing).

Jaime,

THANKS for the explanation!  FYI, I did a restore of the .flar file,
just to test that that restored image works, and indeed, it does work.

And yes, you're right.  I hadn't been explicitly shutting down DS, but
rather just did a couple of "sync"s and then an "init 0" to get to the
boot prompt, so "mystery solved"...

6、Since vendors seem to change chipsets willy-nilly, it would help a lot
if you could post the pci ids of the card in question... or even
better,

 /usr/X11/bin/scanpci -v

provides lots of useful info.

This may be a SysKonnect part, for which there is a 32 bit driver in
the latest
Solaris Express builds...

- Bart

.