X-Sylpheed-Account-Id:1
S:andy.sharp@onstor.com
SCF:#mh/Mailbox/sent
X-Sylpheed-Sign:0
X-Sylpheed-Encrypt:0
X-Sylpheed-Privacy-System:
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB31284F9B9BB@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 23 Apr 2009 17:09:10 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Patrick Haverty <patrick.haverty@onstor.com>
Cc: Brian Stark <brian.stark@onstor.com>
Subject: Re: bcm drivers and additions for leopard
Message-ID: <20090423170910.24443f13@ripper.onstor.net>
References: <20090423130111.1b37b0dd@ripper.onstor.net>
	<102AB4F33EBBDB4C91915B145C8E9FB31284F9B9BB@exch1.onstor.net>
Organization: Onstor
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

OK, I talked to Abdallah and he gave me a bit more information, but
I'm still confused.  I can always just "do as you say" and not try to
understand it, but then what use would I be? ~:^)  OK, well, that's
what I'll do, I'll just add that touch up to the script for Ops.

He also said that a network based method would work for him because he
does have to attach each one to the network, so I'm going to
network-ize the ops-kit.

Cheers,

a

On Thu, 23 Apr 2009 14:13:18 -0700 Patrick Haverty
<patrick.haverty@onstor.com> wrote:

> Nope, That's the broken version.  Here's the fixed version:
> 
> root@myhost:/volumes# cat /etc/vfstab
> #device         device          mount           FS      fsck    mount   mount
> #to mount       to fsck         point           type    pass    at boot options
> #
> /devices        -               /devices        devfs   -       no      -
> /proc           -               /proc           proc    -       no      -
> ctfs            -               /system/contract ctfs   -       no      -
> objfs           -               /system/object  objfs   -       no      -
> sharefs         -               /etc/dfs/sharetab       sharefs -       no      -
> fd              -               /dev/fd         fd      -       no      -
> swap            -               /tmp            tmpfs   -       yes     -
> 
> syspool/rootfs-nmu-000  -                       zfs     -       no      -
> /dev/zvol/dsk/syspool/swap      -               -       swap    -       no      - 
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Thursday, April 23, 2009 1:01 PM
> To: Patrick Haverty
> Cc: Brian Stark
> Subject: Re: bcm drivers and additions for leopard
> 
> OK, what you pasted here seems to be the fixed version.  Can you past the broken version?
> 
> On Thu, 23 Apr 2009 11:55:22 -0700 Patrick Haverty <patrick.haverty@onstor.com> wrote:
> 
> > Yeah, the vfstab file might be different for different configurations.  The change should be the same, so maybe there's a fancy way to script the edit.  Basically the second "/" (the one under mount point) in the line that starts with syspool needs to be deleted.  If it is not then the console displays an error message every boot that mentions something about two or duplicate mount points.  The message also specifies removing the offending / character.
> > 
> > 
> > root@myhost:/volumes# cat /etc/vfstab
> > #device         device          mount           FS      fsck    mount   mount
> > #to mount       to fsck         point           type    pass    at boot options
> > #
> > /devices        -               /devices        devfs   -       no      -
> > /proc           -               /proc           proc    -       no      -
> > ctfs            -               /system/contract ctfs   -       no      -
> > objfs           -               /system/object  objfs   -       no      -
> > sharefs         -               /etc/dfs/sharetab       sharefs -       no      -
> > fd              -               /dev/fd         fd      -       no      -
> > swap            -               /tmp            tmpfs   -       yes     -
> > 
> > syspool/rootfs-nmu-000  -               /       zfs     -       no      -
> > /dev/zvol/dsk/syspool/swap      -               -       swap    -       no      - 
> > 
> > 
> > 
> > -----Original Message-----
> > From: Brian Stark
> > Sent: Thursday, April 23, 2009 11:33 AM
> > To: Andy Sharp; Patrick Haverty
> > Subject: RE: bcm drivers and additions for leopard
> > 
> > Andy,
> > 
> > The attachment that Pat sent earlier shows the paths for the bmc drivers as well as the edit needed for syslog.conf.  We may also want to do the pkill shown at the bottom of the doc.
> > 
> > I've attached the doc to this email.
> > 
> > 
> > Brian
> > 
> > 
> > -----Original Message-----
> > From: Andy Sharp
> > Sent: Thursday, April 23, 2009 11:28 AM
> > To: Patrick Haverty
> > Cc: Brian Stark
> > Subject: bcm drivers and additions for leopard
> > 
> > On Thu, 23 Apr 2009 09:30:38 -0700 Patrick Haverty <patrick.haverty@onstor.com> wrote:
> > 
> > > Pretty much they just need to be copied to the right place, buy we 
> > > have to autostart the ipmievd as discussed in another thread.  Since 
> > > there are drivers (bmc) that have the same name I'm not sure how I 
> > > could send them without getting them mixed up (I still have to tread 
> > > lightly around Linux/UNIX/OpenSolaris stuff).  Would it be possible 
> > > for you to pull them from the locations listed in the doc I sent 
> > > previously?  All of the files should be on any of the systems we've used to test the ipmitool.
> > > Leopard-7 10.3.19.8 (root/back-door) is one.  If you can't access 
> > > that I guess I can send the two bmc files in separate messages.
> > 
> > Starting a new thread since this is a bit off topic from the old one.
> > 
> > I can't find any email with the paths for the drivers, so if you could dig those up for me, that would be helpful.
> > 
> > The ipmievd thing is all quite easily scriptable.  If the vfstab and/or the syslog.conf changes are always the same, I can just throw those into the script as well.  I'm assuming the vfstab stuff isn't always the same because it's configuration dependent.
> > 
> > Cheers,
> > 
> > a
> > 
