[27514] in resnet
Re: Managing Hardware Drivers in MDT
daemon@ATHENA.MIT.EDU (Doughty, Marc)
Fri Mar 30 10:14:23 2012
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=e89a8ff256323ca41e04bc766fa6
Message-ID: <CAEPWjzt6k_YNK5zJrwpuXNe5iaEVB0Fh85M35keR22Nd0_MijA@mail.gmail.com>
Date: Fri, 30 Mar 2012 10:12:45 -0400
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: "Doughty, Marc" <marc_doughty@brown.edu>
To: RESNET-L@listserv.nd.edu
In-Reply-To: <E9F8CA088AE7B645B6A412B2F7133AAA2BC706F9@SMCEXMBX02.mikenet.smcvt.edu>
--e89a8ff256323ca41e04bc766fa6
Content-Type: text/plain; charset=ISO-8859-1
We're using WDS, and only parts of the MDT. What I do is this:
/DRIVERS
/<class>-<vendor>[-item]-<version>
e.g. /video-nvidia-verde-295.73
/audio-sigmatel-stac93xx-5.0.1403
/DRIVERS.PE
/chipset-intel-10.3.1019
/lan-intel-16.8
/storage-intel-matrix-9.6
Using this method, I can add the entire 'DRIVERS.PE' folder recursively to
the boot images/utility disks, while the all-inclusive DRIVERS folder gets
slipstreamed into the images themselves. We pushed hard to only build x64
images going forward, so I don't have to worry about that. If you're doing
x86 AND x64, you probably want to have two separate DRIVERS hierarchies:
/DRIVERS
/x86
/PEx86
/x64
/PEx64
- Marc Doughty
"If you aren't sure who is the give-way vessel, you are the give-way
vessel."
On Fri, Mar 30, 2012 at 9:08 AM, Umansky, Shawn <SUmansky@smcvt.edu> wrote:
> Has anyone found a preferable way to manage/organize their hardware
> drivers in MDT (i.e., folders based on hardware model, etc.)? I know it's
> somewhat personal preference, but am curious to learn how others handle
> this (and why it works for them). Any advice is welcome.
>
> Thanks,
> Shawn
>
> Shawn L. Umansky
> Network Engineer
> Saint Michael's College
> Phone: (802) 654-2763
> SUmansky@smcvt.edu
>
> ___________________________________________________
> You are subscribed to the ResNet-L mailing list.
>
> To subscribe, unsubscribe or search the archives,
> go to http://LISTSERV.ND.EDU/archives/resnet-l.html
> ___________________________________________________
>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--e89a8ff256323ca41e04bc766fa6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
We're using WDS, and only parts of the MDT. What I do is this:<div><br>=
</div><div><font face=3D"'courier new', monospace">/DRIVERS</font><=
/div><div><font face=3D"'courier new', monospace">=A0 =A0 =A0/<c=
lass>-<vendor>[-item]-<version></font></div>
<div><font face=3D"'courier new', monospace">e.g. /video-nvidia-ver=
de-295.73</font></div><div><font face=3D"'courier new', monospace">=
=A0 =A0 =A0/audio-sigmatel-stac93xx-5.0.1403</font></div><div><font face=3D=
"'courier new', monospace">=A0 =A0 =A0/<a href=3D"http://DRIVERS.PE=
">DRIVERS.PE</a></font></div>
<div><font face=3D"'courier new', monospace">=A0 =A0 =A0 =A0 =A0 /c=
hipset-intel-10.3.1019</font></div><div><font face=3D"'courier new'=
, monospace">=A0 =A0 =A0 =A0 =A0 /lan-intel-16.8</font></div><div><font fac=
e=3D"'courier new', monospace">=A0 =A0 =A0 =A0 =A0 /storage-intel-m=
atrix-9.6</font></div>
<div><br></div><div>Using this method, I can add the entire '<a href=3D=
"http://DRIVERS.PE">DRIVERS.PE</a>' folder recursively to the boot imag=
es/utility disks, while the all-inclusive DRIVERS folder gets slipstreamed =
into the images themselves. We pushed hard to only build x64 images going f=
orward, so I don't have to worry about that. If you're doing x86 AN=
D x64, you probably want to have two=A0separate=A0DRIVERS hierarchies:</div=
>
<div><br></div><div>/DRIVERS</div><div>=A0 =A0 =A0/x86</div><div>=A0 =A0 =
=A0 =A0 =A0 /PEx86</div><div>=A0 =A0 =A0/x64</div><div>=A0 =A0 =A0 =A0 =A0 =
/PEx64<br clear=3D"all"><br>- Marc Doughty<br>"If you aren't sure =
who is the give-way vessel, you are the give-way vessel."<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 30, 2012 at 9:08 AM, Umansky=
, Shawn <span dir=3D"ltr"><<a href=3D"mailto:SUmansky@smcvt.edu">SUmansk=
y@smcvt.edu</a>></span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Has anyone found a preferable way to manage/organize their hardware drivers=
in MDT (i.e., folders based on hardware model, etc.)? =A0I know it's s=
omewhat personal preference, but am curious to learn how others handle this=
(and why it works for them). =A0Any advice is welcome.<br>
<br>
Thanks,<br>
Shawn<br>
<br>
Shawn L. Umansky<br>
Network Engineer<br>
Saint Michael's College<br>
Phone: <a href=3D"tel:%28802%29%20654-2763" value=3D"+18026542763">(802) 65=
4-2763</a><br>
<a href=3D"mailto:SUmansky@smcvt.edu">SUmansky@smcvt.edu</a><br>
<br>
___________________________________________________<br>
You are subscribed to the ResNet-L mailing list.<br>
<br>
To subscribe, unsubscribe or search the archives,<br>
go to <a href=3D"http://LISTSERV.ND.EDU/archives/resnet-l.html" target=3D"_=
blank">http://LISTSERV.ND.EDU/archives/resnet-l.html</a><br>
___________________________________________________<br>
</blockquote></div><br></div>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--e89a8ff256323ca41e04bc766fa6--
