Menu
▾
▴
trinux-talk
|
From: Blake, S. <Ste...@ve...> - 2002-09-03 16:35:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Matthew, Just tested this on one of our server boxes that has 4 NICs in it. If found 3 out of the 4. The one it didn't find was an Intel PRO/1000 Fiber NIC. I believe there are kernel drivers for this, you just might no be trying to insmod that particular one. I'll try it out on a couple of other stock machines we have here and let you know if I find any problems. Thanks, Stephen > -----Original Message----- > From: Matthew Franz [mailto:mf...@ci...] > Sent: Tuesday, September 03, 2002 2:02 AM > To: tri...@li...; > tri...@li... > Subject: [Trinux-talk] Small (6MB) Test 2.4.19 ISO > > > Howdy, > > I've released a small .iso for testing if anbody has the > time/inclination. > > It is based on 2.4.19 and my latest initrd.gz. It has booted > fine on my > Thinkpad, VMware, and an old K6--but I'd like wider testing > before doing > even a snapshot release on sourceforge. > > It loops through and attempts to insmod a half-dozen or so of the > most common NICs (it looks like I forgot a few old ISAs, though). > This does *not* have support for any PCMCIA NiCs. Once this appears > to > be stable, > I'll get to that. > > see: > > http://trinux.sf.net/release/ > http://www.io.com/~mdfranz/trinux/boot/ > > It is 3sep02-2419.iso (with matching .md5) and it is about 6mb. > > Feedback/flames are welcome. > > I know there is still some funkiness--for example some of the > packages are > getting loaded twice (I think). > > - mdf > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.2 iQA/AwUBPXTktsF/6XclvKB6EQK+ogCgmzl3xCph77YMkwvNt03nOcW64lsAnRgk ZRyQRolIHsHCTpS4qmJ9Y5BK =l25K -----END PGP SIGNATURE----- |
|
From: Joel N. <jn...@fr...> - 2002-09-10 13:51:20
|
Matthew, I tried your ISO image as a bootable CD for my old Compaq laptop. Worked great! The laptop has a built-in (non-PCMCIA) ethernet port that had not worked with older versions of Trinux I had used several months ago. Question: I understand that this is a "small" .iso -- how could I start from where you left off to build a "big" one? I don't know anything about editing/creating bootable .iso images -- but you seem to have really figured it out! I have immediate use for Trinux with a more complete set of network testing/debugging tools on a bootable CD. Thanks! Joel Noble jn...@fr... |
|
From: Matthew F. <mf...@ci...> - 2002-09-10 14:49:48
|
Here's the script I use to create the .iso ISO="/alt/trinux/trinux.iso" ISOROOT="/alt/trinux/iso" mkisofs -R -J -o $ISO -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table $ISOROOT I'll release a cdrtools.tgz package that has mkisofs and cdrecord that would allow you to make the iso and burn the image within trinux. I only have SCSI and firewire burners, so I'll need some help from folks with IDE burners to get that working. The easiest would be to make the iso within trinux and then just use windows to burn it. - mdf On Tue, Sep 10, 2002 at 07:52:18AM -0600, Joel Noble wrote: > > Matthew, > > I tried your ISO image as a bootable CD for my old Compaq laptop. Worked > great! > > The laptop has a built-in (non-PCMCIA) ethernet port that had not worked > with older versions of Trinux I had used several months ago. > > Question: I understand that this is a "small" .iso -- how could I start > from where you left off to build a "big" one? I don't know anything about > editing/creating bootable .iso images -- but you seem to have really > figured it out! > > I have immediate use for Trinux with a more complete set of network > testing/debugging tools on a bootable CD. > > > Thanks! > > Joel Noble > jn...@fr... -- Matthew Franz mf...@ci... Critical Infrastructure Assurance Group (CIAG) Cisco Systems, Inc. Austin, TX |
|
From: Matthew F. <mf...@ci...> - 2002-09-13 21:52:32
|
On Fri, Sep 13, 2002 at 10:19:04AM -0600, Joel Noble wrote: > > Hi, Matthew! Thanks for your quick response! > > I got the mkisofs package installed. I'm a little bit stuck on what to do > next, so if you don't mind, I'll go over what I think I'm doing, and > hopefully you can tell me where I'm confused. > > I'd like to start out with your package, and build on it by adding in more > Trinux tools. To do this, I need to get a copy of the stuff that went into > creating your .iso, and have that in a directory tree on my computer, like > you have in $ISOROOT in your example. Can I "unpack" the .iso you made > available and get this? I don't know how to do this. Perhaps I just mount > the CD I burned of the ISO and recursively copy everything over, > maintaining permissions? Yes, I think you are on the right track mount the trinux CD # mount -t iso9660 /dev/hdc /mnt # cp -a /mnt/* /iso-root #mkisofs -R -J -o ../place/where/there/is/room/trinux.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table /iso-root > > I seem to have isolinux.bin on my linux box (perhaps it came with mkisofs), > so that should be cool. However, I don't have a "boot.cat" file. Is this > something you had to make yourself? No. It shouldn't be necessary. > Most importantly, how should I put the Trinux packages into before making > the .iso? My guess is that I download all the packages I want and put them > into /trinux/bootpkg and then list them in the text file at > /trinux/tux/config/pkglist. However, some of your packages in the bootpkg > directory (e.g. tcpdump.tgz) are available on boot up, but are NOT in the > pkglist text file. I checked the FAQ, and section 2.5 seems to say that > they must be listed in the pkglist file -- but apparently that isn't true :( Unfortunately there is much in the documentation that is not true because I keep changing them. stuff in bootpkg always gets loaded. If you have a pkg directory, then only the files in pkglist list get loaded if pkglist exists I originally added the bootpkg just for floppies so some packages get loaded first So, yes just put whatever packages you want to get automatically loaded in bootpkg Assuming you are booting off the CD (you should have IDE support) so then if you actually want to burn it on your drive, get http://trinux.sf.net/pkg/2.4.19/scsi-misc.tgz and then manually insmod the ide-scsi.o (and maybe sg.o) and then you can do a man cdrecord to see how to Of course all of this assumes you have enough filesystem space for your .iso and the ISO source tree and the cdrtools.tgz package. - mdf |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X