(Mar 08 2005 18:48) Jason C. Greb wrote: > Can anyone help me? I have to get everything setup and finished by > Friday, and I have already been working on it for about a week now. I am > soo close to getting it cracked, but I seem to have come across this > issue. I have done the stuff manually, but that does not seem to work. I > am thinking it runs more commands after that that I don't see.
Hi Jason Are you having problems with the official driver disks? like with: http://http.trustix.org/pub/trustix/releases/trustix-2.2/i586/images/drvblock.img If so it should be reported as a bug in the installer for TSL-2.2. If the problem only occurs with customized driver disks, there must be a problem with the customization or creation of the disk. I'm almost ashamed to say this but as far as I remember every success story about driver disks on Trustix have been something like this: 1: grab the latest driver disk from http.trustix.org 2: grab the latest kernel source rpm (must correspond to the one on the CD) 3: get the -BOOT config file from ./configs in the source tree and place it as ./.config 4: insert the new driver code into the tree to replace the old driver code. 5: make oldconfig dep modules (remember stack protection issues) 6: loopback mount the driver disk 7: unzip modules.cz 8: replace the driver with the one you just compiled 9: wrap the driver disk back up. The reason I feel ashamed is that we really really really should have made a mkbootdisk script that at least handles points [1,6-9], so that people could do this more easily. I actually looked into it once, and the task is very much something that can be done with moderate programmin skills (preferably in bash or python, anyone? ;) ) Anyway, the procedure I just described should get you going. 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
