(Mar 09 2005 20:41) Jason C. Greb wrote: > Christian, > > Thank you for your reply. I have done this with the one on the CD, and > the disk works to load the drivers during the install. The problem is at > the end of the install, after its done partitioning and done copying > everything over, it copies over the extra modules. However, I would > think there would be a problem if there was just a BOOT driver, so I > created both. Next I am going to try editing the current drvblock.img on > the CD and replacing it back onto the CD with everything left there > except for a few I won't be using so there is enough room. However, > again, I don't know how I will take care of the module without the BOOT, > as the original drvblock.img doesn't contain non-BOOT modules. I guess > they are copied over during the install in an RPM. Looking on this list, > the only mention of driver disks had been during Trustix 1.5, and none > with the 2 series, however I may be wrong. This is what leads me to > believe that its in the installer, since the 2 series. I will file a bug > report, where do I do that? I just hope I can get a working system by > Friday... my customer is getting very antsy.
http://bugs.trustix.org On the other hand, given friday is the D-day for this, I would consider installing with the driver disk you have created, then chrooting into the installed system (mounted as /mnt/sysimage), downloading the driver source, building the modules for the installed kernel and installing the compiled modules right in that system. You should be able to chroot from tty3 or directly to the installed system when booting in rescue mode. This will at least give you the system you need by friday and thus extend the timeframe for understanding the problem and making a fix. kind regards c -- Christian Haugan Toldnes Software Engineer Trustix Secure Linux Development Office Tel Europe: +44 (0) 161 8747070 Office Tel US: +1 888 COMODO 1 (1 888 266 6361) Fax Europe: +44 (0) 161 8771767 Fax US: +1 201 963 9003 This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by replying to the e-mail containing this attachment. Replies to this email may be monitored by Comodo for operational or business reasons. Whilst every endeavour is taken to ensure that e-mails are free from viruses, no liability can be accepted and the recipient is requested to use their own virus checking software. _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
