Re: Thinstation-general Digest, Vol 121, Issue 5

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Thinstation-general Digest, Vol 121, Issue 5

arnoldmoreno
I have over 200 HP 8000s deployed using ThinStation.  I've also build the machine module but I think what you're wanting is just to add the network module in build.conf.  

Before I built the machine module, I actually used this in my build.conf for the e1000:

module e1000e

I haven't had any problems using this line.

Thank you,

Arnold  Moreno

Northside ISD - Lead Systems Administrator

http://www.nisd.net

(210) 397-7865



On Tue, Jun 14, 2016 at 10:11 PM, <[hidden email]> wrote:
Send Thinstation-general mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/thinstation-general
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Thinstation-general digest..."


Today's Topics:

   1. Re: e1000 network module (McHenry)
   2. Re: e1000 network module (Don Cupp)


----------------------------------------------------------------------

Message: 1
Date: Tue, 14 Jun 2016 18:47:40 -0700 (MST)
From: McHenry <[hidden email]>
Subject: Re: [Thinstation-general] e1000 network module
To: [hidden email]
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="us-ascii"

Thanks again Don. I understand a machine profile will include only the
required modules however I thought I could include a module in another
build with the modules XXX line. In my case when I used the VMWare machine
profile everything worked on the workstation except the NIC. When I added
"module e1000" it still didn't work?



On 15 June 2016 at 11:19, Don Cupp [via Thinstation] <
[hidden email]> wrote:

> You need to make a machine profile. The process for getting this done, is
> documented at the top of build.conf.example
> ########################################################
> ### --- Machine Modules to include in boot image --- ###
> ########################################################
> # A machine profile is a set of modules for a specific set of hardware
> # components like a thinclient with adapters. It does not include any
> # filesystem modules, those need to be selected individualy. Making a
> # a machine profile is a two step process. First you will need to make
> # an allmodules build like "./build --allmodules" with the extensions-x
> # package included. Once the client machine is booted with that image
> # you can open and xterm or telnet in and run "hwlister.sh". hwlister.sh
> # will compile some lists and attempt to post them to the pxe server
> assigned
> # to the client. If the pxe server is this workstation and you are hosting
> # files directly out of this build env, you can then run
> # "./mkmachine SOME-MODEL" and the files will be put into the machine
> folder
> # under that model name. Now all you have to do is add a line to this file
> # like "machine SOME-MODEL" and you will no longer have to make
> # allmodules builds. If this is not the pxe server, you will have to
> # move stuff around on your own, but the most important files are
>
> # modules.list and firmware.list.
>
>
>
> On Tuesday, June 14, 2016 7:21 PM, McHenry <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=26066&i=0>> wrote:
>
>
> Hi Don and thanks for the reply.
>
> At the top of my build.conf file i have a set of machine profiles, is this
> what you mean? I have now enabled:
> machine classic-generic
>
> Even though I have "module e1000" enabled was it not loading because i have
> the incorrect machine profile selected?
>
>
>
>
> --
> View this message in context:
> http://thinstation.4464.n7.nabble.com/e1000-network-module-tp26062p26064.html
> Sent from the thinstation-general mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.
> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
>
> _______________________________________________
> Thinstation-general mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=26066&i=1>
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>
>
>
> ------------------------------------------------------------------------------
>
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.
> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
> _______________________________________________
> Thinstation-general mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=26066&i=2>
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://thinstation.4464.n7.nabble.com/e1000-network-module-tp26062p26066.html
> To unsubscribe from e1000 network module, click here
> < > .
> NAML
> <
http://thinstation.4464.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://thinstation.4464.n7.nabble.com/e1000-network-module-tp26062p26067.html
Sent from the thinstation-general mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Wed, 15 Jun 2016 03:11:28 +0000 (UTC)
From: Don Cupp <[hidden email]>
Subject: Re: [Thinstation-general] e1000 network module
To: "[hidden email]"
        <[hidden email]>,    McHenry
        <[hidden email]>, "[hidden email]"
        <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="utf-8"

It is possible to include multiple machine profiles. You might be missing a bus module, so the machine never even finds the nic, and so does not load it's module. I don't know which bus module you need, but it sounds like it gets loaded with an allmodules build.

Sent from Yahoo Mail on Android

  On Tue, Jun 14, 2016 at 6:47 PM, McHenry<[hidden email]> wrote:   Thanks again Don. I understand a machine profile will include only the required modules however I thought I could include a module in another build with the modules XXX line. In my case when I used the VMWare machine profile everything worked on the workstation except the NIC. When I added "module e1000" it still didn't work?



On 15 June 2016 at 11:19, Don Cupp [via Thinstation] <[hidden email]> wrote:

 You need to make a machine profile. The process for getting this done, is documented at the top of build.conf.example
| ######################################################## |
|  | ### --- Machine Modules to include in boot image --- ### |
|  | ######################################################## |
|  | # A machine profile is a set of modules for a specific set of hardware |
|  | # components like a thinclient with adapters. It does not include any |
|  | # filesystem modules, those need to be selected individualy. Making a |
|  | # a machine profile is a two step process. First you will need to make |
|  | # an allmodules build like "./build --allmodules" with the extensions-x |
|  | # package included. Once the client machine is booted with that image |
|  | # you can open and xterm or telnet in and run "hwlister.sh". hwlister.sh |
|  | # will compile some lists and attempt to post them to the pxe server assigned |
|  | # to the client. If the pxe server is this workstation and you are hosting |
|  | # files directly out of this build env, you can then run |
|  | # "./mkmachine SOME-MODEL" and the files will be put into the machine folder |
|  | # under that model name. Now all you have to do is add a line to this file |
|  | # like "machine SOME-MODEL" and you will no longer have to make |
|  | # allmodules builds. If this is not the pxe server, you will have to |
|  | # move stuff around on your own, but the most important files are |
|  | # modules.list and firmware.list. |




    On Tuesday, June 14, 2016 7:21 PM, McHenry <[hidden email]> wrote:


 Hi Don and thanks for the reply.

At the top of my build.conf file i have a set of machine profiles, is this
what you mean? I have now enabled:
machine classic-generic

Even though I have "module e1000" enabled was it not loading because i have
the incorrect machine profile selected?




--
View this message in context: http://thinstation.4464.n7.nabble.com/e1000-network-module-tp26062p26064.html
Sent from the thinstation-general mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general


   If you reply to this email, your message will be added to the discussion below: http://thinstation.4464.n7.nabble.com/e1000-network-module-tp26062p26066.html   To unsubscribe from e1000 network module, click here.
 NAML


View this message in context: Re: e1000 network module
Sent from the thinstation-general mailing list archive at Nabble.com.

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381

------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general


End of Thinstation-general Digest, Vol 121, Issue 5
***************************************************


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general