Menu
▾
▴
vacm-develop
You can subscribe to this list here.
| 2000 |
Jan
(2) |
Feb
(16) |
Mar
(66) |
Apr
(85) |
May
(50) |
Jun
(55) |
Jul
(44) |
Aug
(67) |
Sep
(27) |
Oct
(34) |
Nov
(34) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(26) |
Feb
(20) |
Mar
(28) |
Apr
(45) |
May
(5) |
Jun
(4) |
Jul
(2) |
Aug
|
Sep
(18) |
Oct
(9) |
Nov
(1) |
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: <ra...@ra...> - 2001-04-27 23:41:08
|
On 28 Apr, Wichert Akkerman scribbled: > Previously ra...@ra... wrote: > > i get the same problem you do here.. are you sure you're building this > > right? the rpms build fine in their buildroots. i hae a feeling that > > somehting your'e doing is wierd. > > The exact same approach works for dpkg and all GNU software, and > the GNU Coding Guidelines say it has to work as well.. I'm quite > sure it's really vacm that does something nasty somewhere. glade builds the entire flim makefile configure etc. stuff. its all automake./autoconf built. those paths there are just build from the stuff theat automake. autoconf and gettext spew out - all of whihc are gnu tools.. make distcheck works and making with a buildroot works :) to be honest - i'm not sure why you do it that way.. its odd. -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... ra...@va... VA Linux Systems ra...@de... Mobile Phone: +1 408 887 3163 Work Phone: +1 510 687 7069 |
|
From: Wichert A. <wi...@va...> - 2001-04-27 23:25:20
|
Previously ra...@ra... wrote: > i get the same problem you do here.. are you sure you're building this > right? the rpms build fine in their buildroots. i hae a feeling that > somehting your'e doing is wierd. The exact same approach works for dpkg and all GNU software, and the GNU Coding Guidelines say it has to work as well.. I'm quite sure it's really vacm that does something nasty somewhere. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: <ra...@ra...> - 2001-04-27 23:21:06
|
On 28 Apr, Wichert Akkerman scribbled: > Previously ra...@ra... wrote: > > err seeing your build commands donmt event work... > > That's because I was pasting make commands, where each command > is run in a seperate shell process so the cd doesn't affect > the next command. If you use a shell directly do: > > mkdir build > (cd build && ../configure) ooooh... :) > make -C build > mkdir -p debian/tmp > make -C build DESTDIR=`pwd`/debian/tmp install > > > [- 3:56PM ~/C/DEV/vacum/2.0/vacm/build -] > > This prompt scares me, it looks so much like a DOS prompt.. i get the same problem you do here.. are you sure you're building this right? the rpms build fine in their buildroots. i hae a feeling that somehting your'e doing is wierd. -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... ra...@va... VA Linux Systems ra...@de... Mobile Phone: +1 408 887 3163 Work Phone: +1 510 687 7069 |
|
From: Wichert A. <wi...@va...> - 2001-04-27 22:51:58
|
Previously ra...@ra... wrote: > err seeing your build commands donmt event work... That's because I was pasting make commands, where each command is run in a seperate shell process so the cd doesn't affect the next command. If you use a shell directly do: mkdir build (cd build && ../configure) make -C build mkdir -p debian/tmp make -C build DESTDIR=`pwd`/debian/tmp install > [- 3:56PM ~/C/DEV/vacum/2.0/vacm/build -] This prompt scares me, it looks so much like a DOS prompt.. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: <ra...@ra...> - 2001-04-27 22:44:30
|
On 28 Apr, Wichert Akkerman scribbled:
> Previously ra...@ra... wrote:
> > errr this is odd.. well first those build liens done even work.. :)
> > thats a first problem
>
> I'm waiting for a patch :) In the meantime I'm redoing the
> init-scripts to work on Debian system and finishing up the
> packaging.
err seeing your build commands donmt event work...
[- 3:31PM ~/C/DEV/vacum/2.0/vacm -]cd build && ../configure
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
configure: error: source directory already configured; run make distclean there first
[- 3:31PM ~/C/DEV/vacum/2.0/vacm/build -]make -C build
make: *** build: No such file or directory. Stop.
notice this error? its buildign onyl because theres probably somehting
there form soem previous build effort.
[- 3:31PM ~/C/DEV/vacum/2.0/vacm/build -]mkdir -p debian/tmp
[- 3:31PM ~/C/DEV/vacum/2.0/vacm/build -]make -C build DESTDIR=`pwd`/debian/tmp install
make: *** build: No such file or directory. Stop.
[- 3:56PM ~/C/DEV/vacum/2.0/vacm/build -]
> Are the /etc/vacm_sys_statd.passwd and /etc/vacm_user_admd.passwd
> indeed just flags to indicate which daemons to run? It looks
> like it, so I'm killing them and putting that flag in
> /etc/vacm.conf instead.
>
> Wichert.
>
--
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
The Rasterman (Carsten Haitzler) ra...@ra... ra...@va...
VA Linux Systems ra...@de...
Mobile Phone: +1 408 887 3163 Work Phone: +1 510 687 7069
|
|
From: Wichert A. <wi...@va...> - 2001-04-27 22:40:29
|
Previously ra...@ra... wrote: > errr this is odd.. well first those build liens done even work.. :) > thats a first problem I'm waiting for a patch :) In the meantime I'm redoing the init-scripts to work on Debian system and finishing up the packaging. Are the /etc/vacm_sys_statd.passwd and /etc/vacm_user_admd.passwd indeed just flags to indicate which daemons to run? It looks like it, so I'm killing them and putting that flag in /etc/vacm.conf instead. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: <ra...@ra...> - 2001-04-27 22:36:20
|
On 28 Apr, Wichert Akkerman scribbled: > Previously ra...@ra... wrote: > > i'd be willing to say theres a bug in a latergettext. dont build form > > cvs - use pre-built tarballs then your gettext version doesnt matter :) > > I'm using the vacm 2.0.5 .tar.gz from sourceforge. errr this is odd.. well first those build liens done even work.. :) thats a first problem -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... ra...@va... VA Linux Systems ra...@de... Mobile Phone: +1 408 887 3163 Work Phone: +1 510 687 7069 |
|
From: Wichert A. <wi...@va...> - 2001-04-27 22:28:38
|
Previously ra...@ra... wrote: > i'd be willing to say theres a bug in a latergettext. dont build form > cvs - use pre-built tarballs then your gettext version doesnt matter :) I'm using the vacm 2.0.5 .tar.gz from sourceforge. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: <ra...@ra...> - 2001-04-27 22:27:33
|
On 28 Apr, Wichert Akkerman scribbled: > Previously ra...@ra... wrote: > > dont look at me.. but i think your build proceedure is screwed :) > > I have gettext 0.10.37, I'm willing to bet you have an older > version. Upgrades are kind of mandatory, libc won't even build > with an older version anymore.. gettext-0.10.35-23 i'd be willing to say theres a bug in a latergettext. dont build form cvs - use pre-built tarballs then your gettext version doesnt matter :) -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) ra...@ra... ra...@va... VA Linux Systems ra...@de... Mobile Phone: +1 408 887 3163 Work Phone: +1 510 687 7069 |
|
From: Wichert A. <wi...@va...> - 2001-04-27 22:24:50
|
Previously ra...@ra... wrote: > dont look at me.. but i think your build proceedure is screwed :) I have gettext 0.10.37, I'm willing to bet you have an older version. Upgrades are kind of mandatory, libc won't even build with an older version anymore.. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: <ra...@ra...> - 2001-04-27 22:19:56
|
On 27 Apr, Wichert Akkerman scribbled:
>
> There is something wrong with the vacm 2.0.5 buildsystem it seems.
> This does not work:
>
> mkdir build
> cd build && ../configure
> make -C build
> mkdir -p debian/tmp
> make -C build DESTDIR=`pwd`/debian/tmp install
dont look at me.. but i think your build proceedure is screwed :)
[- 3:31PM ~/C/DEV/vacum/2.0/vacm -]cd build && ../configure
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
configure: error: source directory already configured; run make distclean there first
[- 3:31PM ~/C/DEV/vacum/2.0/vacm/build -]make -C build
make: *** build: No such file or directory. Stop.
[- 3:31PM ~/C/DEV/vacum/2.0/vacm/build -]mkdir -p debian/tmp
[- 3:31PM ~/C/DEV/vacum/2.0/vacm/build -]make -C build DESTDIR=`pwd`/debian/tmp install
need i say more :)
(nb all of vacm passes make distcheck - so i'm going to be betting you
have a problem your end as passing make distcheck means u buuildroot
properly)
> It dies in clients/flim/po with this error:
>
> Making install in po
> make[4]: Entering directory `/home/wichert/sources/debian/vacm/vacm-2.0.5/build/clients/flim/po'
> if test -r "../../../../clients/flim/../../../clients/flim/../../mkinstalldirs"; then \
> ../../../../clients/flim/../../../clients/flim/../../mkinstalldirs /usr/share; \
> else \
> /bin/sh ../../../../clients/flim/mkinstalldirs /usr/share; \
> fi
> ../../../../clients/flim/mkinstalldirs: ../../../../clients/flim/mkinstalldirs: No such file or directory
> make[4]: *** [install-data-yes] Error 127
> make[4]: Leaving directory `/home/wichert/sources/debian/vacm/vacm-2.0.5/build/clients/flim/po'
>
> This actually shows two errors:
> * an outdated gettext is used that does not handle DESTDIR unlike the
> rest of the buildsystem
> * it tries to use clients/flim/mkinstalldirs which does not exist
>
> Until this is fixed I'm afraid I'll have to disable flim in the Debian
> packages.
>
> Wichert.
>
--
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
The Rasterman (Carsten Haitzler) ra...@ra... ra...@va...
VA Linux Systems ra...@de...
Mobile Phone: +1 408 887 3163 Work Phone: +1 510 687 7069
|
|
From: Wichert A. <wi...@va...> - 2001-04-27 21:59:16
|
Can the install-location for documentation as given in docs/Makefile.am be changed to use $(datadir) instead of $(prefix)? Documentation does fit the `read-only architecture-indepdenent data' description, and it also has the advantage of making things FHS-complient. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: Wichert A. <wi...@ci...> - 2001-04-27 21:43:51
|
There is something wrong with the vacm 2.0.5 buildsystem it seems. This does not work: mkdir build cd build && ../configure make -C build mkdir -p debian/tmp make -C build DESTDIR=`pwd`/debian/tmp install It dies in clients/flim/po with this error: Making install in po make[4]: Entering directory `/home/wichert/sources/debian/vacm/vacm-2.0.5/build/clients/flim/po' if test -r "../../../../clients/flim/../../../clients/flim/../../mkinstalldirs"; then \ ../../../../clients/flim/../../../clients/flim/../../mkinstalldirs /usr/share; \ else \ /bin/sh ../../../../clients/flim/mkinstalldirs /usr/share; \ fi ../../../../clients/flim/mkinstalldirs: ../../../../clients/flim/mkinstalldirs: No such file or directory make[4]: *** [install-data-yes] Error 127 make[4]: Leaving directory `/home/wichert/sources/debian/vacm/vacm-2.0.5/build/clients/flim/po' This actually shows two errors: * an outdated gettext is used that does not handle DESTDIR unlike the rest of the buildsystem * it tries to use clients/flim/mkinstalldirs which does not exist Until this is fixed I'm afraid I'll have to disable flim in the Debian packages. Wichert. -- _________________________________________________________________ / Nothing is fool-proof to a sufficiently talented fool \ | wi...@ci... http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | |
|
From: San M. <net...@va...> - 2001-04-16 20:00:32
|
they can, but i believe the quanta boards do not have ICMB firmware support as yet. Jeong Hwan Park wrote: > I have read the release notes of VACM 2.0.5. > > I have read this release has the improved hardware management for Quanta > which has two ICMB ports (One is IN ICMB and the other is OUT). > > Does the VACM 2.0.5 support these ICMB (intellegent chassis management > bus) ports? > I think these ICMB ports can remove the terminal server or multiport > serial cards which is used to connect the EMP port when these ICMP ports > are connected in a daisy chain. > > > _______________________________________________ > Vacm-develop mailing list > Vac...@li... > http://lists.sourceforge.net/lists/listinfo/vacm-develop |
|
From: Zac 'z. S. <zsp...@va...> - 2001-04-16 17:00:26
|
On Mon, Apr 16, 2001 at 11:33:18AM +0530, Rama Krishna S (EPD-BLRSJP-PEG) wrote: > > Quanta uses SMIC Interface to access the BMC and Intel Server used KCS. Will > VACM work on Quanta??? Yes, the latest release includes a quanta module which works... -z |
|
From: Jerry K. <ka...@va...> - 2001-04-16 16:57:24
|
Looking at the source, it's issuing "/sbin/shutdown -h[-r] now" to the nodes. Jerry. On Sat, Apr 14, 2001 at 09:40:11AM -0500, dr...@va... wrote: > > What is RSH:SHUTDOWN:<NODE_ID> doing? A "shutdown -h" command > or a "halt" command? > > What is RSH:RESTART:<NODE_ID> doing? A "shutdown -r" command > or a "reboot" command? > > > -- > Tony Kubinski 1.877.VALINUX x76776 (work) > Systems Engineer 1.781.823.6029 (fax) > VA Linux Systems 1.630.248.5293 (cell) > Chicago dr...@va... (email) > 630...@mo... (text page) > > _______________________________________________ > Vacm-develop mailing list > Vac...@li... > http://lists.sourceforge.net/lists/listinfo/vacm-develop |
|
From: Rama K. S (EPD-BLRSJP-PEG) <sr...@wi...> - 2001-04-16 06:27:41
|
Quanta uses SMIC Interface to access the BMC and Intel Server used KCS. Will VACM work on Quanta??? -----Original Message----- From: Jeong Hwan Park [mailto:jh...@ww...] Sent: Sunday, April 15, 2001 9:25 PM To: zsp...@va... Cc: jh...@br...; vac...@li... Subject: [Vacm-develop] Quanta's ICMB port and VACM 2.0.5? I have read the release notes of VACM 2.0.5. I have read this release has the improved hardware management for Quanta which has two ICMB ports (One is IN ICMB and the other is OUT). Does the VACM 2.0.5 support these ICMB (intellegent chassis management bus) ports? I think these ICMB ports can remove the terminal server or multiport serial cards which is used to connect the EMP port when these ICMP ports are connected in a daisy chain. _______________________________________________ Vacm-develop mailing list Vac...@li... http://lists.sourceforge.net/lists/listinfo/vacm-develop |
|
From: Jeong H. P. <jh...@ww...> - 2001-04-15 15:57:39
|
I have read the release notes of VACM 2.0.5. I have read this release has the improved hardware management for Quanta which has two ICMB ports (One is IN ICMB and the other is OUT). Does the VACM 2.0.5 support these ICMB (intellegent chassis management bus) ports? I think these ICMB ports can remove the terminal server or multiport serial cards which is used to connect the EMP port when these ICMP ports are connected in a daisy chain. |
|
From: <dr...@va...> - 2001-04-14 15:43:22
|
What is RSH:SHUTDOWN:<NODE_ID> doing? A "shutdown -h" command
or a "halt" command?
What is RSH:RESTART:<NODE_ID> doing? A "shutdown -r" command
or a "reboot" command?
--
Tony Kubinski 1.877.VALINUX x76776 (work)
Systems Engineer 1.781.823.6029 (fax)
VA Linux Systems 1.630.248.5293 (cell)
Chicago dr...@va... (email)
630...@mo... (text page)
|
|
From: gregory j p. <gj...@va...> - 2001-04-10 17:57:40
|
So, things were working with an early flim/vacm/kernel. I upgraded and got everything working w/ vash. THe serial_console from vash and shell work. EMP power on/off and identify from vash work. The serial_console and emp back to node don't work under flim. Ideas? -- gregory j pryzby < gjp at valinux dot com > Herbivores ate well because their food didn't ever run! |
|
From: Zac 'z. S. <za...@va...> - 2001-04-10 16:29:19
|
On Tue, Apr 10, 2001 at 11:21:09AM -0500, Greg Pratt wrote: > Have you upgraded the firmware using the firmware cd? This is unlikely to be a firmware issue. As san said, if there's nothing spewing out the port, it is probably a bios setting problem. If you are *sure* the bios is set up correctly and you are still seeing no data, I would then check for a bad cable and also physically remove the power cable and then plug it back in. Zac |
|
From: <dr...@va...> - 2001-04-10 16:28:31
|
No. Don't have one. If someone can cut one and fedex to me,
that would be great!
Greg Pratt wrote:
>
> Have you upgraded the firmware using the firmware cd?
>
> -Greg
> dr...@va... wrote:
> >
> > Here is the dumpdmi results from the 2240 that doesn't
> > want to speak EMP.
> >
> > --
> > Tony Kubinski 1.877.VALINUX x76776 (work)
> > Systems Engineer 1.781.823.6029 (fax)
> > VA Linux Systems 1.630.248.5293 (cell)
> > Chicago dr...@va... (email)
> > 630...@mo... (text page)
> >
> > ------------------------------------------------------------------------
> > Name: 2240.dumpdmi.txt
> > 2240.dumpdmi.txt Type: Plain Text (text/plain)
> > Encoding: 7bit
--
Tony Kubinski 1.877.VALINUX x76776 (work)
Systems Engineer 1.781.823.6029 (fax)
VA Linux Systems 1.630.248.5293 (cell)
Chicago dr...@va... (email)
630...@mo... (text page)
|
|
From: Greg P. <gp...@va...> - 2001-04-10 16:21:28
|
Have you upgraded the firmware using the firmware cd? -Greg dr...@va... wrote: > > Here is the dumpdmi results from the 2240 that doesn't > want to speak EMP. > > -- > Tony Kubinski 1.877.VALINUX x76776 (work) > Systems Engineer 1.781.823.6029 (fax) > VA Linux Systems 1.630.248.5293 (cell) > Chicago dr...@va... (email) > 630...@mo... (text page) > > ------------------------------------------------------------------------ > Name: 2240.dumpdmi.txt > 2240.dumpdmi.txt Type: Plain Text (text/plain) > Encoding: 7bit |
|
From: San M. <net...@va...> - 2001-04-10 16:10:02
|
if you're not seeing any data through minicom then the bios on the remote machines is not setup correctly. Please have a look at the
documentation screenshots which show the proper settings
-san
dr...@va... wrote:
> --
> Tony Kubinski 1.877.VALINUX x76776 (work)
> Systems Engineer 1.781.823.6029 (fax)
> VA Linux Systems 1.630.248.5293 (cell)
> Chicago dr...@va... (email)
> 630...@mo... (text page)
>
> ------------------------------------------------------------------------
>
> Subject: Re: [se] VACM Question
> Date: Tue, 10 Apr 2001 08:15:57 -0500
> From: dr...@va...
> CC: se...@li..., vac...@va...
> References: <3AD...@va...> <200...@va...> <3AD...@va...> <200...@va...> <3AD...@va...> <200...@va...> <200...@va...>
>
> I'm not getting anything thru minicom from the client's EMP
> port at any port settings.
>
> Ari Jort wrote:
> >
> > Tony,
> >
> > Also, use minicom to check out the port on which EMP data
> > should be coming. Run it on the mayor, set to 19200,
> > but try other speeds also.
> >
> > If you see garbage data pulsing every 2 seconds or so,
> > then you might actually have EMP going across.
> >
> > The garbage looks kinda like this:
> >
> > .$,%.,$.#,*,#.,$%{,@>
> >
> > basically, lots of punctuation :)
> >
> > If you see that in minicom, then you know for sure
> > that the monitored machine is in fact sending EMP data out.
> > If vash can't see it, then you know it's a nexxus problem.
> >
> > Have you configured the nodes correctly in nexxus?
> >
> > Send us you /usr/lib/vacm/vacm_configuration file.
> >
> > Stay in touch so we can get this. Pratt experience
> > from yesterday has me a little nervous.
> >
> > Plus, Trey and I are going onsite today to Bear Stearns
> > to do precisely what Pratt was doing the other day.
> > Expectations are reasonable and I feel prepared, so I'm
> > not worried. At least not yet.
> >
> > Do we have that emergency hotline to San set up yet?
> >
> > ari
> >
> > On Tue, Apr 10, 2001 at 05:59:33AM -0700, Greg Pryzby wrote:
> > > On Tue, Apr 10, 2001 at 06:52:13AM -0500, dr...@va... wrote:
> > > >
> > > > Thanks...vacm_sys_statd now runs and client system data
> > > > can be retrieved by the mayor. No, I wasn't using either
> > > > flim or hoover, just vash. There seems to be some basic EMP
> > > > communication issue that is escaping me.
> > >
> > > What is working/isn't for emp? What can yo do?
> > > /var/log/vacm.log
> > > /var/log/vacm*nodename*log
> > >
> > > should help debug the problem.
> > >
> > > Send exact commands and responses and we can fix /answer Qs.
> >
> > --
> > --------------------------------------------------------------
> > Ari Jort * ar...@va... * 212 858 7686
> > VA Linux Systems * 140 Broadway Suite 4616 * New York NY 10005
> > http://valinux.com * http://nylug.org
>
> --
> Tony Kubinski 1.877.VALINUX x76776 (work)
> Systems Engineer 1.781.823.6029 (fax)
> VA Linux Systems 1.630.248.5293 (cell)
> Chicago dr...@va... (email)
> 630...@mo... (text page)
>
> **********************
> se mailing list
>
|
|
From: <dr...@va...> - 2001-04-10 15:32:46
|
Here is the dumpdmi results from the 2240 that doesn't
want to speak EMP.
--
Tony Kubinski 1.877.VALINUX x76776 (work)
Systems Engineer 1.781.823.6029 (fax)
VA Linux Systems 1.630.248.5293 (cell)
Chicago dr...@va... (email)
630...@mo... (text page) |
