Re: [Thinstation-developer] list of modules in 23svn - kernel 2.6.31.5

[Don C. <don...@ya...>]

Mmmm. Just thinkin out loud here, but what if we take a completely different approach.
 
How about making a profiler build of thinstation. It would contain basic wired networking, X but no clients, and ALL kernel modules and ALL firmwares and ALL X drivers. It would never actually launch into X, but only do the configuration and then it would build a platform package with all the kernel drivers that actually loaded plus firmware files that were requested and the xorg driver that was chosen by the configurator and offer to push via tftp to your devstation.
 
We could really thin out the build.conf with something like that, without having to make a bunch of metapackages, or maybe just turn user submitted versions of these into metapackages.
 
What do you all think.

--- On Thu, 9/30/10, Jason Meers <jas...@gm...> wrote:


From: Jason Meers <jas...@gm...>
Subject: Re: [Thinstation-developer] list of modules in 23svn - kernel 2.6.31.5
To: "Mike Eriksen" <thi...@gm...>
Cc: "thinstation-developer" <thi...@li...>
Date: Thursday, September 30, 2010, 9:18 AM


I think meta packages are a possible solution, but haven't even begun
to look at how you would do it.

meta-hp-thinclinet
meta-wyse-thinclinet
meta-dell-gx1xx
meta-dell-gx2xx
meta-intel-atom2xx
meta-via-epia
meta-nvidia-nforce4

Jason_Meers




On 30 September 2010 16:25, Mike Eriksen <thi...@gm...> wrote:
> On Thu, Sep 30, 2010 at 3:03 PM, Jason Meers
> <jas...@gm...> wrote:
>> Just for info:
>> list of modules in 23svn - kernel 2.6.31.5 - 30th September 2010
>>
>> Jason_Meers
> [CUT]
>
> That's nothing short of horrible and there is no way we can maintain
> the current layout of build.conf. 107 wired NICs... We have to do
> something like:
>
> #!!!Ethernet 10-100 Mbit Modules
> # Select among these:
> # 3c501 3c503 3c505 3c507 3c509 3c515 3c59x 8139cp 8139too 82596 8390 8390p
> # ac3200 acenic amd8111e at1700 b44 bnx2 bnx2x bsd_comp cassini cnic
> cs89x0 depca
> # dl2k dnet e100 e2100 eepro eexpress epic100 eth16i ethoc ewrk3
> fealnx forcedeth
> # hamachi hp-plus hp hp100 ipg jme ks8842 lance lp486e mdio natsemi ne ne2k-pci
> # ni5010 ni52 ni65 niu ns83820 pcnet32 ppp_async ppp_deflate ppp_generic
> # ppp_synctty qla3xxx r6040 r8101 r8168 r8169 s2io sc92031 seeq8005
> sis190 sis900
> # skge sky2 slhc smc-ultra smc9194 smsc9420 starfire sundance sungem sungem_phy
> # sunhme tehuti tg3 tlan tun typhoon via-rhine via-velocity vmxnet vmxnet3 wd
> # znet atl1 atl2 be2net cxgb cxgb3 e1000 e1000e enic igb igbvf ixgb ixgbe
> # mlx4_core mlx4_en myri10ge netxen_nic
> #
> #Sample configuration: (multiple drivers are allowed, but only include
> what you really need)
> #module r8168
> #module via-rhine
>
> But that's not without problems itself. I foresee a mail storm like
> "Which module for my Dell?"
>
> Mike
> --
> Operator of the Danish TS-O-Matic.
> http://thinstation.org
> - a light, full featured linux based thin client OS
>

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Thinstation-developer mailing list
Thi...@li...
https://lists.sourceforge.net/lists/listinfo/thinstation-developer