Simon Kissel wrote: > Anyway, back to Trustix. > > Trustix 2.2 uses Kernel 2.4 and therefore Isdn4Linux/HiSax. And yes, > the default kernel even has HiSax as a module. Everything looked nice > on first sight. > > But reading the how-to's, I found out I needed the isdn4k-utils > package to get isdnctrl and hisaxctrl and basicly everything else > needed to configure ISDN. > > To my surprise, this package is only available for Trustix 3.0. > > Well, Trustix 3.0 on the other hand uses Kernel 2.6, and the Trustix > default kernel has isdn4linux disabled. Instead Capi 4 Linux is > enabled. To configure this, one would need the capi4k-utils package. > > This package is not available for Trustix 3.0, but only as a contrib > for... Trustix 2.2! > > Maybe I'm just incompetent, but for me this looks a little insane. > Trustix 3.0 should have the capi4k-utils package, and Trustix 2.2 > should have the isdn4k-utils package, but it's the other way round.
Sounds like a mess. Let's fix it. :) Can you add this as a bug report in the bugzilla? > > What I'm looking for is instructions to get a HFC-S based PCI ISDN > card to connect to some ISP. > > I guess there are the following possible routes to do this: > > - Get the isdn4k-utils package for Trustix 2.2, and then hope that > one of the dozens of confusing howtos works ;) Since 2.2 is the stable version, and as you say, the isdn part of 2.6.x kernels are not fully functional, this is the obvious solution. To test you can simply grab and rebuild the source rpm from 3.0: wget http://http.trustix.org/pub/trustix/releases/trustix-3.0/srpms/isdn4k-utils-0.0.20051001-1tr.src.rpm rpm --rebuild isdn4k-utils-0.0.20051001-1tr.src.rpm You might need to install some packages (like rpm-devel) to be able to do this. > > - Compile a new kernel including the mISDN patches on Trustix 3.0, and > pray that then suddenly mISDN und capi4linux together magically form > something working (as this seems to be completely undocumented)... Let's assume the kernel developers will fix this problem soonish, and follow their approach. Since TSL 3.x isn't matured yet, we are free to include packages and make needed changes over time. Patching the kernel is, well, something we like to spend some time thinking about before we jump into it. :) Kind regards c -- Christian Haugan Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
