You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(20) |
Sep
(4) |
Oct
(29) |
Nov
(24) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(9) |
Feb
(26) |
Mar
(10) |
Apr
(4) |
May
(5) |
Jun
(13) |
Jul
(53) |
Aug
(15) |
Sep
(42) |
Oct
(30) |
Nov
(92) |
Dec
(45) |
2002 |
Jan
(36) |
Feb
(63) |
Mar
(24) |
Apr
(21) |
May
(30) |
Jun
(59) |
Jul
(34) |
Aug
(17) |
Sep
(57) |
Oct
(104) |
Nov
(21) |
Dec
(16) |
2003 |
Jan
(31) |
Feb
(56) |
Mar
(40) |
Apr
(55) |
May
(45) |
Jun
(38) |
Jul
(48) |
Aug
(33) |
Sep
(13) |
Oct
(19) |
Nov
(7) |
Dec
(9) |
2004 |
Jan
(15) |
Feb
(20) |
Mar
(1) |
Apr
(1) |
May
(6) |
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
|
Dec
(1) |
2005 |
Jan
(18) |
Feb
(3) |
Mar
(2) |
Apr
(2) |
May
|
Jun
(6) |
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
(9) |
Feb
|
Mar
|
Apr
(16) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Joerg O. <ov...@de...> - 2002-01-24 15:06:49
|
Am 23:24 23.01.02 -0600 schrubst Du: -> Here is a more robust version of the faq. Enjoy and distribute at will. Hey, great stuff, really helpful! I'm still pondering this sentence though: "As of the final release of 0.80 (which will probably be in August '01) ..." ;) jo +-------------------------------------------------------------------+ | __ __ __ __ _ _ It ain't over 'till it's Joerg Over... | | / _ \ V / -_) '_/ | | \___/\_/\___|_| | +-------------------------------------------------------------------+ |
From: Matthew F. <mf...@ci...> - 2002-01-24 14:38:54
|
Great work! This has been needed for a long time. It is available at http://trinux.sf.net/faq/ and there is a link off the main page. Thanks again, - mdf > > Here is a more robust version of the faq. Enjoy and distribute at will. > mstrhelix > > _____________________________________________________________________________________________________________ > Chat with friends online, try MSN Messenger: Click Here > > |
From: windham l. <mst...@ho...> - 2002-01-24 05:24:13
|
-= Trinux FAQ =- vers. 0.2 1.23.02 Compiled by Lance Windham Send questions or comments to mst...@ho... Table of Contents 1. Introduction and General Information 1.1. What Is Trinux? 1.2. Trinux, huh? What is it good for? 1.3. What Hardware is Supported? 1.4. What Software does Trinux Support? 1.5. What happened to my finger, find and other common UNIX utilities? 2. Trinux Installation and Configuration. 2.1. Download, where and how? 2.2. Bootdisks: ide, iso, and the like. 2.3. Selecting Packages. 2.4. Network Package Loading 2.5. Fixed Disk Package Loading 2.6. Floppy Package Loading 2.7. Building package disks 3. Optimizing Trinux 3.1. Loading Kernel modules 3.2. how can I use my mouse with gpm? 3.3. Using swap space, swap-on ? 3.4. Building your own initrd! 4. Misc. questions 4.1. Why a few applications complain about the missing libraries? 4.2. How can I set up a NFS client on the Trinux box? 4.3. How can I set up a PPP client/server daemon on my Trinux box? 4.4. How can I set up SSH on my Trinux box? 4.5. How can I clone a hard drive? 4.6. How can I build an initrd? 4.7. I have a USB Keyboard? 4.8. Samba client to connect to NT/Win2k/NetWare shares. 4.9. Mount: full version 4.10. gethome and savehome. 4.11. Trinux source 4.12. What keeps Trinux from being multi-user? 4.13. How can I make my own Linux from scratch? 4.14. mounting loop filesystems 4.15. modifying linuxrc 4.16. I would like to use an alternate keymap for my trinux box. 4.17. parallel zip drive 4.18. what is rebol? 4.19. what is contained on the bootdisk? 4.20. what is tmpfs? 5.0. Networking Trinux 5.1. trinux -> trinux 5.2. linux -> trinux 5.3. windows -> trinux 5.4. NIC module list -=/\/\/\/\/\/\/\=- 1. Introduction and General Information 1.1. What is Trinux? Trinux is a ramdisk-based Linux distribution that boots from a single floppy or CD-ROM, loads it packages from an HTTP/FTP server, a FAT/NTFS/ISO filesystem, or additional floppies. 1.2. Trinux, huh, What is it good for? Trinux contains the latest versions of popular Open Source network security tools for port scanning, packet sniffing, vulnerability scanning, sniffer detection, packet construction, active/passive OS fingerprinting, network monitoring, session-hijacking, backup/recovery, computer forensics, intrusion detection, and more. Trinux also provides support for Perl, PHP, and Python scripting languages. Remote Trinux boxes can be managed securely with OpenSSH. 1.3. What Hardware Is Supported? Trinux will boot on any i486 or better with at least 12-16 megabytes of RAM, depending on how many packages are loaded. Hardware support for many common Ethernet cards is provided in the default kernel and additional NICs are supported via Linux kernel modules. 1.4. What Software does Trinux Support? Trinux 0.8x is/was developed using Slackware 7.1 and supports the latest 2.4.x kernels and glibc 2.1.x. Trinux was first released in April 1998. Versions up through 0.51 were based on Debian 1.31 binaries linked against libc5. Version 0.6x was built using RedHat Linux 5.2. 1.5. What happened to my finger, find and other common UNIX utilities. Trinux utilizes Busybox to replace many common UNIX utilities. http://busybox.lineo.com ------------------------------------------------------------------------- 2. Trinux Installation and Configuration. 2.1. Download, where and how? Trinux can be obtained at the following locations: http://trinux.sourceforge.net http://www.io.com/~mdfranz/trinux http://gd.tuwien.ac.at/opsys/linux/trinux/ http://the.wiretapped.net/security/operating-systems/trinux/ 2.2. Bootdisks: ide, iso, and the like. Since Trinux is a floppy-based distribution, it is only available in the form of raw disk images, which must be written to floppies after they have been downloaded. Trinux requires a boot disk whose purpose is to load the linux kernel, mount the initrd (initial ramdisk), create additional ramdisks, configure networking, and load packages from additional floppies or from other sources. Floppy Images 1.4MB boot floppy images will need to be written using rawrite (a DOS program) or better yet Rawrite for Windows. On UNIX systems, you can use the dd command to do a low-level image copy. Be sure to check the size of the file that you downloaded. It should be 1474560 bytes. As of version 0.81pre0-2.4.5 , there are four possible boot images to choose from: * Network - contains a stripped down kernel with support for common Ethernet NiCs, but no integrated support for IDE devices or filesystems (except for FAT and minix). * PCMCIA - contains the smallest kernel (no built-in ISA/PCI NIC support) and PCMCIA kernel-module packages for 3Com, Xircom, and a few more PCMCIA NICs. Other PCMCIA modules are available. Best for network package loading. See pcmcia-cs project for a list of supported cards * IDE - nearly identical to the standard image except that the kernel has support for IDE hard drives and CD-ROMs and FAT, NTFS (read only), and minix filesystems. * ISO - test release based on 0.81 linuxrc/initrd but still with 2.4.5 kernel primarily useful for laptop(pcmcia) users. NOTE: you must be able to boot from cd in your CMOS setup. 2.3. Selecting Packages. Only a bare minimum of Trinux's functionality is provided on the initial boot floppy: basically enough to boot the kernel, build the ramdisks, extract a minumum number of necessary utilities, and configure the network. As as a result, it is necessary for users to decide what applications they want to include. 2.4. Network Package Loading For me, this is the preferred method of loading Trinux. Packages are maintained on a centralized HTTP/HTTP server and after obtaining an IP address a selection of packages are automatically loaded and installed via snarf. This saves the trouble of building and updating floppies. On a fast network (close to the web server) a Trinux box can be up and running in around a minute. As of 0.80rc2, use the "net" boot image if you are going to use network booting, although all version of Trinux can use this feature once the network is properly configured, or (if you are a laptop user) use the pcmcia boot disk. If I forgot to load a package (or if I want to test a new one) I just use the getpkg command to retrieve and install it. For now, getpkg does not initialize the package, so you need to check /etc/init.d for a package initialization script that would install kernel modules or start background processes. As of the final release of 0.80 (which will probably be in August '01) getpkg will automically initialize the package and install the kernel modules via the scripts in /etc/init.m. Network package loading will be used unless packages are found on a fixed disk partition (see below). If Trinux is unable to contact the default HTTP url due to network problems (interface, routing, DNS, configuration, etc.), it will resort to floppy loading. Laptop users will have to use multiple floppies, because the PCMCIA packages will not fit on the boot disk. Assuming your network is properly configured or you use DHCP, the following steps are necessary to configure network package loading: 1. Select an HTTP/FTP server that has trinux packages. This value is set by /tux/config/server on the boot floppy (a:\tux\config\ server) which contains a list of servers that Trinux will attempt to contact to load packages. See the mirror page for a mirror close to you. 2. Modify /tux/config/pkglist on the boot floppy (a:\tux\config\pkglist) to add any new package names that you want Trinux to load automatically. All of these configuration files are in ASCII text so it best to use an editor such as notepad (or the DOS editor) or vi that does not add formatting characters. See below for which packages you might want to add or delete. 2.5. Fixed Disk Package Loading Fixed Disk Package Loading (including CD-ROM booting and package loading) For users who cannot (or do not want to) use network package loading, this is the best option. It is also the fastest. This is also the option laptop users should choose because the pcmcia package does not fit on the boot disk. 1. Download the "ide" boot floppy that has support for IDE hard drives, CD-ROMs, and minix, VFAT, NTFS, ISO9660 filesystems. 2. Visit the packages page to see what packages you need. 3. Create a trinux directory at the root (C:\ D:\ /, .etc ) of a FAT,Minix, NTFS, or ISO9660 filesytem. This is where you should download any and all packages you want to load. 4. If you are using a Windows FAT16/32 filesystem, the boot kernel already supports this filesystem, if you are using an NTFS or EXT2(Linux) filesystem, you need to download the kernel module (ntfs.o or ext2.o) and copy it to the boot floppy. 5. Download packages from ibiblio (what used to be MetaLab) or one of the mirror and save them to the directory you created in step 2. Trinux will automatically use the first filesytem it finds with a trinux directory to load packages. 6. Modify /tux/config/pkglist on the boot floppy (a:\tux\config\ pkglist to add any new package names that you want Trinux to load automatically. All of these configuration files are in ASCII text so it best to use an editor such as notepad (or the DOS editor) or vi that does not add formatting characters. 2.6. Floppy Package Loading This method of loading packages is the slowest and most cumbersome, and Trinux only chooses this if it cannot find a package server or a local filesystem to load packages from. 2.7. Building package disks Building package disks is fairly straightforward and involves the following steps: 1. Get a bunch of floppy disks. Actually, 2-3 disks should do. 2. Visit the packages page to see what packages you need. 3. Download packages from ibiblio (what used to be MetaLab) or one of the mirrors. -------------------- 3. Optimizing Trinux 3.1. Loading Kernel modules There are two ways to load Kernel modules in Trinux. At boot-time or after login. boot-time: add modulename.o to your bootdisk as well as modulename.o to your /tux/config/modules file. after: use insmod to insert the module file. i.e.-> # insmod modulename.o To verify if the module was loaded you can then do a -># lsmod to list loaded modules. 3.2. How can I use my mouse with gpm? pkgadd gpm pkgadd libgpm pkgadd gpm-links pkgadd modmice.tgz <- unpack mouse modules insmod mousedev.o <- insert/load module insmod input.o <- needed for mouse support ln -sf /dev/psaux /dev/mouse <- link for gpm pkgadd gpm -t ps2 <- gpm -t (type of mouse) 3.3. How can I customize initrd.gz? To customize your initrd.gz file which is basically just a compressed minix filesystem all you have to do is: # mount -o loop initrd /mnt then just cd to the /mnt directory and modify the files inside this directory. After you are done modifiying the files in this dir just unmount the dir and gzip it back up and place it onto your bootdisk and bahm! your done. ------------------------------------------ 4. Misc. questions 4.1. Why a few applications complain about missing libraries? . this means that you are missing libraries and must pkgadd the specific libs. 4.2. How can I set up a NFS client on the Trinux box? nfs-client.tgz, ntfs.o(fsmod.tgz), reiserfs.tgz # pkgadd nfs-client.tgz (nfs kernel mods) # pkgadd netutil.tgz (full versions of mount/umount) you can also tail -f /var/log/messages to see if the volumes were mounted and/or do a tcpdump 4.3. How can I set up a PPP client/server daemon on my Trinux box? - windmodems will not work. - make sure modem is detected. - pkgadd serial-net.tgz trinux> lsmod Module Size Used by bsd_comp 4360 0 (unused) ppp_async 6700 0 (unused) ppp_generic 15432 0 [bsd_comp ppp_async] slhc 5180 0 [ppp_generic] serial 54928 0 (unused) isa-pnp 31568 0 [serial] ide-disk 7052 2 ide-probe-mod 9256 0 ide-mod If you don't see this then try /etc/init.m/ppp # dmesg isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Serial driver version 5.05a (2001-03-20) SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A CSLIP: code copyright 1989 Regents of PPP generic driver version 2.4.1 PPP BSD Compression module registered 4.4. How can I set up SSH on my Trinux box? # pkgadd openssh # pkgadd opensshd You must generate an RSA keypair on your client and copy your public key to the boot floppy, which will then be added to the authorized_keys file when Trinux boots. execute an ssh-keygen and the keypair will be put in ~/.ssh. Copy your Public Key to the Boot Floppy Make a copy of the public key created by ssh-keygen (this will most-likely be identity.pub) and rename this file to keys. Copy this file to the \tux\pkg\opensshd\ directory the boot floppy. NOTE: You can have multiple RSA keys in the keys file. What I typically do is boot Trinux, mount the boot floppy, then scp the identity.pub files from the UNIX boxes I want to connect from to Trinux. Then I append the identity.pub to /.ssh/authorized_keys if I want to be able to login without having to reboot. You can also specify a key file (via URL) in /tux/pkg/opensshd/ kserver so you don't have to update floppies. For example I use http://blahblah.cisco.com/tux/sshkeys and then add keys to that file when I want to let another host connect to a trinux box. 4.5. How can I clone a hard drive? 4.6. How can I build an initrd? # gunzip initrd.gz # pkgadd fsmods # insmod loop.o # mount -t loop initrd /mnt then just cd to /mnt and modify accordingly 4.7. I have a USB (Device)/Keyboard? -> add the usb package to the boot floppy # pkgadd usb-input # pkgadd usb-core 4.8. Using the Samba client to connect to NT/Win2k/NetWare shares. # insmod smbfs.o (available in the fsmods.tgz kernel package) # pkgadd smbmount # pkgadd smbcore 4.9. Where can I locate -> Mount: the full version # pkgadd netutil 4.10. gethome and savehome. -> 4.11. Trinux source -> Much of trinux is actually stored in a compressed minux file system on the boot disk -- initrd.gz. You can poke around this / modify it by using the loop back device. The config files for the kernel can be found at http://trinux.sourceforge.net/kernel/2.4.13/. Note that this is for the 2.4.13 and 2.4.5 kernel. Everything was compiled on Slackware 7.1 (glibc2.1.3) 4.12. What keeps Trinux from being multi-user? -> there are some weird libc/busybox issues which prevent passwd and login from working. 4.13. How can I make my own Linux from scratch? -> see the linux from scratch faq 4.14. mounting loop filesystems # insmod loop.o (from the fsmods.tgz pkg) # mount -t loop loopfile /mnt 4.15. modifying linuxrc # insmod loop.o # mount -t loop initrd /mnt # cd /mnt; vi linuxrc 4.16. I would like to use an alternate keymap for my trinux box. # loadkmap < hu.map 4.19. what is contained on the bootdisk? initrd.gz - compressed initial ramdisk filesystem (this is actually MINIX) license - the splash screen shown on the initial boot version - what version of trinux bzimage - the Linux kernel image ldlinux.sys - the boot loader (DO NOT DELETE) syslinux.cfg - boot loader config file basenet.tgz - a minimal set of network utils to get things going tux - directory where config/init scripts are <-/\/\/\-> 5.0. Networking Trinux 5.1. trinux -> trinux -> boot trinux and check if eth0 came up via # dmesg | grep "eth0" 5.1. linux -> trinux 5.2. windows -> trinux 5.4. NIC module list |
From: <hk...@sy...> - 2002-01-23 11:11:39
|
Hi Florian, syslogd is started from linuxrc. linuxrc is packed into initrd.gz. Download its source to be able to modify. You will need then the script to create initrd.gz from source, which you can find somewhere in the mailing list archive. Hajni |
From: <FLO...@LH...> - 2002-01-22 18:36:35
|
Hi, can anybody tell me where the busybox syslogd is started from or how I could get it to start with the -R parameter for remote syslogging right from the start? Thanks Florian |
From: Jochen G. <geo...@th...> - 2002-01-21 20:14:55
|
hello i'm lokking for a module for my d-link DFE-550TX Fast Ethernet (pci) adapter.... is there any? thanks for all hints beste gruesse jochen georges _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: <hk...@sy...> - 2002-01-21 15:57:45
|
Hi,=20 I checked, and loadkmap loads the hu.map right, but the problem is only with the display: If I save the special characters to a file under trinux,=20 and read the file under an other, complete linux box, I can see that all national characters are right. So the probem is with the display, which means that the ISO-8859-2 code page=20 ought to be used, but no stuff is included in trinux for that. What shall I do to be able to use that? /Hajni |
From: <hk...@sy...> - 2002-01-21 14:26:36
|
Hi, I would like to use an alternate keymap for my trinux box. I downloaded the hu.map binary file from the tomsrtbt program, and wanted to load it by # loadkmap < hu.map (Tomsrtbt uses the same loadkmap program, I suppose). It works, but some specific hungarian letters are not correct=20 or cannot be displayed at all. I cannot change the hu.map file, because it is binary. I checked the map file at=20 other linux distributions, but those files are just simple text files.=20 What shall I do to be able to use a correct alternate (hungarian) keymap ? Thank you in advance if anyone can help me. Please send any help directly to me, because I am not subscribed to the = list. /Hajni |
From: Jeremy L. <je...@ga...> - 2002-01-18 19:35:40
|
Have you had any luck in getting the USB keyboard support to work? I see that there is a new usb-input.tgz package in the kernel directory. Should I try to compile it? Or does it still not work? Thanks. Jeremy Linden |
From: <sig...@ac...> - 2002-01-14 14:35:34
|
Hi! I've tried to find the solution of my problem by roughly browsing this maillist but with no success. My problem is: I have a laptop which run Win2K on NTFS filesystem with a PCMCIA card. When DL the PCMCIA version I get the network connection up-and-running, and when DL the IDE version I get the ntfs mounted ok (after adding the ntfs.o file). I want to get both my filesystem mounted and the network up, but this I'm not able to do. At home I have an CD-RW, but I'm looking for a solution where I can add packages at work and my colleagues could use the same solution WITHOUT access to a CD-R. Sincerily Sigurd Egset ________________________________________________ Sigurd Egset Accenture Mob: +47 917 23 444 Mail: sig...@ac... ________________________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. |
From: Matthew F. <mf...@ci...> - 2002-01-13 23:26:06
|
SCSI, parallel, or IDE (I assume that I have IDE, its been a while)? - mdf On Sun, 13 Jan 2002, Kevin Stenger wrote: > Date: Sun, 13 Jan 2002 15:03:43 -0500 > From: Kevin Stenger <kst...@cf...> > To: tri...@li... > Subject: [Trinux-talk] Parallel zip drive > > Can anyone give me some suggestions on how to mount a zip 100 in Trinux. > > Thanks > > Kevin > > kst...@cf... > > > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > |
From: Kevin S. <kst...@cf...> - 2002-01-13 20:03:23
|
Can anyone give me some suggestions on how to mount a zip 100 in Trinux. Thanks Kevin kst...@cf... |
From: Matthew F. <mf...@ci...> - 2002-01-11 13:42:33
|
Right, slackware 8.0 using glibc 2.2 (which is huge) vs Slack 7.1 which is 2.1.x -mdf > > I would like to add some packages to my trinux box and > asking for any information on adding programs, etc. to Trinux. I saw that > slackware was used to develop it and downloaded a copy of slackware 8.0. > > My assumption was to get slackware running, install and compile other > program then repackage the files and/or copy over to Trinux. Is this correct > ? > > After typing above I had re-read the home page and found > "Trinux 0.7x/0.8x is was developed using Slackware 7.1 and supports the > latest 2.2.x kernels and glibc 2.1.x. Trinux 0.8x supports Linux kernel > 2.4.x." > > I read the slackware 8 page and found > Slackware 8 - glibc-2.2.3 runtime support > > does this mean I need to use slackware 7.1 then more items over.. am I > thinking correctly here. > > Thank you, > Mark > > > _________________________________________________________________ > Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > |
From: Mark L. <mar...@ho...> - 2002-01-11 11:41:32
|
I would like to add some packages to my trinux box and asking for any information on adding programs, etc. to Trinux. I saw that slackware was used to develop it and downloaded a copy of slackware 8.0. My assumption was to get slackware running, install and compile other program then repackage the files and/or copy over to Trinux. Is this correct ? After typing above I had re-read the home page and found "Trinux 0.7x/0.8x is was developed using Slackware 7.1 and supports the latest 2.2.x kernels and glibc 2.1.x. Trinux 0.8x supports Linux kernel 2.4.x." I read the slackware 8 page and found Slackware 8 - glibc-2.2.3 runtime support does this mean I need to use slackware 7.1 then more items over.. am I thinking correctly here. Thank you, Mark _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com |
From: <Ian...@la...> - 2002-01-10 18:01:14
|
Hi Matthew, Trinux ISOs are giving me a problem. First the Floppy image for the PCMCIA (trinux-0.80rc2-pcmcia.img) works= beautifully. Thanks. I have downloaded both trinux-0.81pre0-2.4.5.iso=A0=A0trinux-80rc2-2.4.5.iso files and have pr= oblems with both. I have checked the trinux-80rc2-2.4.5.iso MD5 checksum and it matches t= hat in the trinux.sourceforge.net site I have read it back from the CD and = it is the same so my CD is also the same. The CD starts to boot but the ke= rmel hangs. I have tried it on two machines here. One which has run Linux fo= r several years a Pentium II 233 from Sony (Vaio PCG 737). Another machin= e, an IBM T20 512MB RAM PIII 750MHz does the same. I am reluctant to use i= t on my servers because I want them to stay up. (One is an Alpha anyway). The other ISO trinux-0.81pre0-2.4.5.iso MD5 137264378ae7863d5e75fffb9fc3f463=A0 trinux-0.81pre0-2.4.5.iso will not even begin to boot. It appears to have no boot sector as the P= Cs (same as above) boot from the hard drive as normal. Investigating the ISO file on the server with a loopback mount gives th= is /home/ianm/incoming/trinux-0.81pre0-2.4.5.iso on /mnt/t1 type iso9660 (ro,loop=3D/dev/loop0) [ianm@bmf incoming]$ cd /mnt/t1 [ianm@bmf t1]$ cd isolinux/ [ianm@bmf isolinux]$ file * boot.cat:=A0=A0=A0=A0 data bzimage:=A0=A0=A0=A0=A0 x86 boot sector initrd.gz:=A0=A0=A0 gzip compressed data, deflated, original filename, = `initrd', last modified: Thu Nov=A0 8 12:22:22 2001, max compression, os: Unix isolinux.bin: file: read failed (Input/output error). Remember the MD5 checksum is the same as that on Sourceforge. This is n= ot the only file to fail. Please advise. My suspicion is incorrect options to mkisofs but there i= s no way I can tell. Thanks for what otherwise is a great package and regards, Ian = |
From: <FLO...@LH...> - 2002-01-10 11:56:30
|
Hi, when using the adaptec bzImage for my Trinux Boot disk I experience a strange behavior at boot time. When the partitions check is perfomed, the following partitions are found (9187 17942564 512-byte MB) hdwr sectors It looks like Trinux takes the Harddisk information found at boot time an takes them for partions. [ root ]# dmesg |grep 512-byte SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB) For those "partitions", Trinux creates directories in the system root. Does anybody know what the problem could be. Rigth now I help myself in deleting the directories again in the post install script. Thanks Florian |
From: <tb...@ti...> - 2002-01-10 04:56:41
|
Sorry, I did not keep close track of what I did. Mostly, I think it was the linuxrc file, however, I think I needed to make some accomodating changes in another script or two. I forget. Mostly, I was changing, and testing, changing and testing, until I had the iso the way I wanted it, and since I burned up a stack of CD blanks getting it, I thought others might find it useful. Sorry, no diffs or patch file. On Wed, 9 Jan 2002, David GLAUDE Mailing wrote: > Mr Timothy Burt, > Do you have some more specific information > on what file did change exactly in your version of the iso? > Would you have some kind of patch or diff or TGZ with a copy > of the file modified. > Thanks. > David GLAUDE > > This is your latest e-mail on the topic: > " > I have made some changes to the linuxrc file to smooth out the boot > process for the CDROM version of Trinux. It works much better for me now. > Hopefully, I didn't break any of the floppy boot dependant code... > > In addition, I added another Ram disk config for bigger ramdisks, if > you have 512M of ram. > > And one more change, I disabled the DHCP default. The startup will ask if > you want to use DHCP, or allow you to enter your own network values. > > These changes were applied to the stock trinux-0.80rc2-2.4.5 iso. > > I have posted my modified version of the CDROM iso on my server at: > > http://www.timburt.com/trinux/trinux-0.80tburt-2.4.5.iso > > Matt says he will put it up on sourceforge, so when he gets around to it, > I will probably take the above URL down. > > Hopefully, this will help some of you who are using the iso and having > trouble adding packages. > > Note that after successful bootup, the CDROM is not mounted. If you want > to use addpkg, you will need to mount the cdrom and find the package you > want to add. > " > > > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > -- -------------------- Timothy Burt Internet Specialist |
From: David G. M. <dgl...@gm...> - 2002-01-09 16:51:26
|
Mr Timothy Burt, Do you have some more specific information on what file did change exactly in your version of the iso? Would you have some kind of patch or diff or TGZ with a copy of the file modified. Thanks. David GLAUDE This is your latest e-mail on the topic: " I have made some changes to the linuxrc file to smooth out the boot process for the CDROM version of Trinux. It works much better for me now. Hopefully, I didn't break any of the floppy boot dependant code... In addition, I added another Ram disk config for bigger ramdisks, if you have 512M of ram. And one more change, I disabled the DHCP default. The startup will ask if you want to use DHCP, or allow you to enter your own network values. These changes were applied to the stock trinux-0.80rc2-2.4.5 iso. I have posted my modified version of the CDROM iso on my server at: http://www.timburt.com/trinux/trinux-0.80tburt-2.4.5.iso Matt says he will put it up on sourceforge, so when he gets around to it, I will probably take the above URL down. Hopefully, this will help some of you who are using the iso and having trouble adding packages. Note that after successful bootup, the CDROM is not mounted. If you want to use addpkg, you will need to mount the cdrom and find the package you want to add. " |
From: windham l. <mst...@ho...> - 2002-01-09 03:42:54
|
-= Trinux FAQ =- vers. 0.1 12.02.01 compiled by Lance Windham Table of Content 1. Introduction and General Information 1.1. What Is Trinux? 1.2. Trinux, huh? What is it good for? 1.3. What Hardware is Supported? 1.4. What Software does Trinux Support? 1.5. What happened to my finger, find and other common UNIX utilities? 2. Trinux Installation and Configuration. 2.1. Download, where and how? 2.2. Bootdisks: ide, iso, and the like. 2.3. Selecting Packages. 2.4. Network Package Loading 2.5. Fixed Disk Package Loading 2.6. Floppy Package Loading 2.7. Building package disks 2.8. Current Package List. 3. Optimizing Trinux 3.1. Loading Kernel modules 3.2. how can I use my mouse and gpm? 3.3. Using swap space, swap-on ? 3.4. Building your own initrd! 4. Misc. questions 4.1. Why a few applications complain about the missing libncurses.so.5? 4.2. How can I set up a NFS client on the Trinux box? 4.3. How can I set up a PPP client/server daemon on my Trinux box? 4.4. How can I set up SSH on my Trinux box? 4.5. How can I clone a hard drive? 4.6. How can I build an initrd? -=/\/\/\/\/\/\/\=- 1. Introduction and General Information 1.1. What is Trinux? Trinux is a ramdisk-based Linux distribution that boots from a single floppy or CD-ROM, loads it packages from an HTTP/FTP server, a FAT/NTFS/ ISO filesystem, or additional floppies. ------------------------------------------------------------------------- 1.2. Trinux, huh, What is it good for? Trinux contains the latest versions of popular Open Source network security tools for port scanning, packet sniffing, vulnerability scanning, sniffer detection, packet construction, active/passive OS fingerprinting, network monitoring, session-hijacking, backup/recovery, computer forensics, intrusion detection, and more. Trinux also provides support for Perl, PHP, and Python scripting languages. Remote Trinux boxes can be managed securely with OpenSSH. ------------------------------------------------------------------------- 1.3. What Hardware Is Supported? Trinux will boot on any i486 or better with at least 12-16 megabytes of RAM, depending on how many packages are loaded. Hardware support for many common Ethernet cards is provided in the default kernel and additional NICs are supported via Linux kernel modules. ------------------------------------------------------------------------- 1.4. What Software does Trinux Support? Trinux 0.7x/0.8x is/was developed using Slackware 7.1 and supports the latest 2.2.x kernels and glibc 2.1.x. Trinux 0.8x supports Linux kernel 2.4.x. Trinux was first released in April 1998. Versions up through 0.51 were based on Debian 1.31 binaries linked against libc5. Version 0.6x was built using RedHat Linux 5.2. -------------------------------------------------------------------------- 1.5. What happened to my finger, find and other common UNIX utilities. Trinux utilizes Busybox to replace many common UNIX utilities. http://busybox.lineo.com ------------------------------------------------------------------------- 2. Trinux Installation and Configuration. 2.1. Download, where and how? Trinux can be obtained at the following locations: http://trinux.sourceforge.net http://www.io.com/~mdfranz/trinux http://gd.tuwien.ac.at/opsys/linux/trinux/ http://the.wiretapped.net/security/operating-systems/trinux/ ------------------------------------------------------------------------- 2.2. Bootdisks: ide, iso, and the like. Since Trinux is a floppy-based distribution, it is only available in the form of raw disk images, which must be copied to floppies after they have been downloaded. Trinux requires a boot disk whose purpose is to load the linux kernel, mount the initrd (initial ramdisk), create additional ramdisks, configure networking, and load packages from additional floppies or from other sources. Floppy Images 1.4MB boot floppy images will need to be written using rawrite (a DOS program) or better yet Rawrite for Windows. On UNIX systems, you can use the dd command to do a low-level image copy. Be sure to check the size of the file that you downloaded. It should be 1474560 bytes. As of version 0.81pre0-2.4.5 , there are four possible boot images to choose from: * Network - contains a stripped down kernel with support for common Ethernet NiCs, but no integrated support for IDE devices or filesystems (except for FAT and minix). * PCMCIA - contains the smallest kernel (no built-in ISA/PCI NIC support) and PCMCIA kernel-module packages for 3Com, Xircom, and a few more PCMCIA NICs. Other PCMCIA modules are available. Best for network package loading. See pcmcia-cs project for a list of supported cards * IDE - nearly identical to the standard image except that the kernel has support for IDE hard drives and CD-ROMs and FAT, NTFS (read only), and minix filesystems. * ISO - test release based on 0.81 linuxrc/initrd but still with 2.4.5 kernel primarily useful for laptop (pcmcia) users. ------------------------------------------------------------------------- 2.3. Selecting Packages. Only a bare minimum of Trinux's functionality is provided on the initial boot floppy: basically enough to boot the kernel, build the ramdisks, extract a minumum number of necessary utilities, and configure the network. As as a result, it is necessary for users to decide what applications they want to include. 2.4. Network Package Loading For me, this is the preferred method of loading Trinux. Packages are maintained on a centralized HTTP/HTTP server and after obtaining an IP address a selection of packages are automatically loaded and installed via snarf. This saves the trouble of building and updating floppies. On a fast network (close to the web server) a Trinux box can be up and running in around a minute. As of 0.80rc2, use the "net" boot image if you are going to use network booting, although all version of Trinux can use this feature once the network is properly configured, or (if you are a laptop user) use the "pcmcia/laptop" boot disk. If I forgot to load a package (or if I want to test a new one) I just use the getpkg command to retrieve and install it. For now, getpkg does not initialize the package, so you need to check /etc/init.d for a package initialization script that would install kernel modules or start background processes. As of the final release of 0.80 (which will probably be in August '01) getpkg will automically initialize the package and install the kernel modules vi the scripts in /etc/init.m. Network package loading will be used unless packages are found on a fixed disk partition (see below). If Trinux is unable to contact the default HTTP url due to network problems (interface, routing, DNS, configuration, etc.), it will resort to floppy loading. Laptop users will have to use multiple floppies, because the PCMCIA packages will not fit on the boot disk. Assuming your network is properly configured or you use DHCP, the following steps are necessary to configure network package loading: 1. Select an HTTP/FTP server than has trinux packages. This value is set by /tux/config/server on the boot floppy (a:\tux\config\server) which contains a list of servers that Trinux will attempt to contact to load packages. See the mirror page for a mirror close to you. 2. Modify /tux/config/pkglist on the boot floppy (a:\tux\config\pkglist) to add any new package names that you want Trinux to load automatically. All of these configuration files are in ASCII text so it best to use an editor such as notepad (or the DOS editor) or vi that does not add formatting characters. See below for which packages you might want to add or delete. 2.5. Fixed Disk Package Loading Fixed Disk Package Loading (including CD-ROM booting and package loading) For users who cannot (or do not want to) use network package loading, this is the best option. It is also the fastest. This is also the option laptop should choose because the pcmcia package does not fit on the boot disk. 1. Download the "ide" boot floppy that has support for IDE hard drives, CD-ROMs, and minix, VFAT, NTFS, ISO9660 filesystems. 2. Visit the packages page to see what packages you need. 3. Create a trinux directory at the root (C:\ D:\ /, .etc ) of a FAT, Minix, NTFS, or ISO9660 filesytem. This is where you should download any and all packages you want to load. 4. If you are using a Windows FAT16/32 filesystem, the boot kernel already supports this filesystem, if you are using an NTFS or EXT2 (Linux) filesystem, you need to download the kernel module (ntfs.o or ext2.o) and copy it to the boot floppy. 5. Download packages from ibiblio (what used to be MetaLab) or one of the mirror and save them to the directory you created in step 2. Trinux will automatically use the first filesytem it finds with a trinux directory to load packages. 6. Modify /tux/config/pkglist on the boot floppy (a:\tux\config\pkglist to add any new package names that you want Trinux to load automatically. All of these configuration files are in ASCII text so it best to use an editor such as notepad (or the DOS editor) or vi that does not add formatting characters. 2.6. Floppy Package Loading This method of loading packages is the slowest and most cumbersome, and Trinux only chooses this if it cannot find a package server or a local filesystem to load packages from. 2.7. Building package disks Building package disks is fairly straightforward and involves the following steps: 1. Get a bunch of floppy disks. Actually, 2-3 disks should do. 2. Visit the packages page to see what packages you need. 3. Download packages from ibiblio (what used to be MetaLab) or one of the mirrors. -=/\/\/\/\/\/=- 3. Optimizing Trinux 3.1. Loading Kernel modules There are two ways to load Kernel modules in Trinux. At boot-time or after login. boot-time: add modulename.o to your bootdisk as well as modulename.o to your /tux/config/modules file. after: use insmod to insert the module file. i.e.-> # insmod modulename.o To verify if the module was loaded you can then do a -># lsmod to list loaded modules. 3.2. How can I use my mouse with gpm? pkgadd modmice.tgz <- unpack mouse modules insmod mousedev.o <- insert/load module insmod input.o <- needed for mouse support ln -sf /dev/psaux /dev/mouse <- link for gpm gpm -t ps2 <- gpm -t (type of mouse) 3.3. How can I customize initrd.gz? To customize your initrd.gz file which is basically just a compressed minix filesystem all you have to do is: mount -o loop initrd /mnt then just cd to the /mnt directory and modify the files inside this directory. After you are done modifiying the files in this dir just unmount the dir and gzip it back up and place it onto your bootdisk and bahm! your done. |
From: <tb...@ti...> - 2002-01-08 16:39:26
|
I think that many newbies gravitate to Trinux because it offers a running Linux system with only a boot floppy. This is true, but I would hesitate to suggest that it is a good Linux for a Newbie to start with. Trinux is foremost an intrusion detection tool, and comes loaded with some very powerful tools. However, the tools assume a somewhat advanced knowledge of networking, and often present information of use only to advanced users. Trinux has alot of the traditional Linux stripped away. For two reasons, 1) to keep it light and bootable from a floppy, and 2) as an ID tool, it doesn't need alot of the multi-user capabilities. An example of this is that Trinux does not use a password file. It has no password. For a newbie, I would recommend sticking with a standard Linux distribution until you feel very comfortable, then give Trinux a look see. It took me a couple of days of messing with it to get Trinux to boot and come up the way I wanted it. I had to research many of the bootup scripts (/linuxrc is where it all starts) to see why it did not do what I wanted, and then make adjustments or modify the scripts to my liking. Not recommended for a newbie! That said, here are some answers to your questions...... On Tue, 8 Jan 2002, Intrusion Detector wrote: > TO add insult to injury ... I originally sent this > email to the news group!!! Is this an indication of > Newbie-itus or what?!?!? DUH!!!! > > ANyway, hope someone can help with this ...... > (although somewhat embarrassed, I include the original > email) > > OK, > > Up front people ... I apologize (or apologise) for the > dumb questions I am about to ask but I am a newbie to > Linux having just, and I do mean just, installed SUSE > and now trying my hand at Trinux. OK, so I'm trying > the switch ......... > > REQUEST: > > 1. Request on installation procedures > Sorry but the documentation on the website is not the > best for us REALLY newbie folks > > 2. With the exception of NMap, how the other programs > are run within the Trinux environment; From the command line, but you must first add them with a getpkg or pkgadd command. (I think the command names are correct), with some packages, it may be necessary to run the init script by hand too. > > 3. After you get up off the floor from your spat of > uncontrollable laughter, realise (or realize) that I > am truly serious. > > 4. rather than post to the entire group I would > appreciate a little hand holding here from a > "sympathetic" subscriber. > > In advance, I thank you. > > Environment: > 1. OS - Windows '98 (OK,OK, I'm also a tad bit behind > in that area!!) > > 2. HArdware: IBM THinkpad 600. Am willing to give mre > details, but only after receipt of individual email. If you have a CD-Rom, then you might try my iso: http://timburt.com/trinux/trinux-0.80tburt-2.4.5.iso It works for me, and some others have reported success with it. But my iso is not without it's own problems.. :-( Booting from the iso has the advantage of loading up many of the support packages from the cdrom, and not the network... or Dos partition... > > 3. Used the latest version of Trinux and the IDE > image; > > 4. Wrote the image file to a floppy using RawWrite; > > 5. Created the c:/trinux directory and copied all the > files from the website to this directory (I used the > website in Texas (duh); I had difficulties getting this to work. Not sure why. I switched to network upload. The base Trinux kernel does include support for FAT filesystems (but not Linux!) so the underlying support is there. > > 6. Turned system off and rebooted from floppy: > > 7. ON boot: > 7.1 Kernel Loaded (v 2.4.5) > 7.3 Created HDA1 through HDA6 (From my limited > experience these are hard disks recognized by the > Linux system and I have NO idea why there are so many. > I have but 2 partitions: 1 for Windows and 1 for SUSE > Linux); > > 7.3 Added packages like the bash (I do get the BASH# > prompt) and some others that were downloaded; A crippled version of bash, as well as many other commands (mount) are available in the bootup OS. Enough for you to look around and see what is going right, and what failed. > > 8. Welsome message appears with a request to activate > the console by pressing return. > > OK ......so I press enter and get <BASH#> then I try > to activate the other programs (e.g. scanners, > ipaudit, and nothing but "sh: ipaudit: command not > found" then back to the prompt. > This is most likely caused by the package not loading, even tho you thought it did. Some commands fail silently... I had trouble getting Trinux to find the /trinux folder on my disk, but it didn't matter because I wanted to download from the net anyway. Note that Trinux runs in Ram, and if you are starting with 16 or 32 MB, you may find that you run out before you get too many packages loaded. Use df to see how much ramdisk is available. > > Sooooooooo, there ya go. Now, can someone please help. > I have searched through the email archives and a > French guy came close to the problem I am having, but > there was no definitive answer. > > ANyways, hope I have been detailed enough. > > Kind regards > You are doing better than some. However, you still have a rocky road ahead. Getting SSH running can be frustrating. See the prior posts. > > > > > __________________________________________________ > Do You Yahoo!? > Send FREE video emails in Yahoo! Mail! > http://promo.yahoo.com/videomail/ > > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > -- -------------------- Timothy Burt Internet Specialist |
From: Intrusion D. <ide...@ya...> - 2002-01-08 14:55:44
|
TO add insult to injury ... I originally sent this email to the news group!!! Is this an indication of Newbie-itus or what?!?!? DUH!!!! ANyway, hope someone can help with this ...... (although somewhat embarrassed, I include the original email) OK, Up front people ... I apologize (or apologise) for the dumb questions I am about to ask but I am a newbie to Linux having just, and I do mean just, installed SUSE and now trying my hand at Trinux. OK, so I'm trying the switch ......... REQUEST: 1. Request on installation procedures Sorry but the documentation on the website is not the best for us REALLY newbie folks 2. With the exception of NMap, how the other programs are run within the Trinux environment; 3. After you get up off the floor from your spat of uncontrollable laughter, realise (or realize) that I am truly serious. 4. rather than post to the entire group I would appreciate a little hand holding here from a "sympathetic" subscriber. In advance, I thank you. Environment: 1. OS - Windows '98 (OK,OK, I'm also a tad bit behind in that area!!) 2. HArdware: IBM THinkpad 600. Am willing to give mre details, but only after receipt of individual email. 3. Used the latest version of Trinux and the IDE image; 4. Wrote the image file to a floppy using RawWrite; 5. Created the c:/trinux directory and copied all the files from the website to this directory (I used the website in Texas (duh); 6. Turned system off and rebooted from floppy: 7. ON boot: 7.1 Kernel Loaded (v 2.4.5) 7.3 Created HDA1 through HDA6 (From my limited experience these are hard disks recognized by the Linux system and I have NO idea why there are so many. I have but 2 partitions: 1 for Windows and 1 for SUSE Linux); 7.3 Added packages like the bash (I do get the BASH# prompt) and some others that were downloaded; 8. Welsome message appears with a request to activate the console by pressing return. OK ......so I press enter and get <BASH#> then I try to activate the other programs (e.g. scanners, ipaudit, and nothing but "sh: ipaudit: command not found" then back to the prompt. Sooooooooo, there ya go. Now, can someone please help. I have searched through the email archives and a French guy came close to the problem I am having, but there was no definitive answer. ANyways, hope I have been detailed enough. Kind regards __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ |
From: Richard S. A. <ash...@mi...> - 2002-01-04 14:11:27
|
SUBSCRIBE |
From: Matthew F. <mf...@ci...> - 2001-12-29 04:47:15
|
Ah, Microsoft Natural keyboard's are great. Using one right now with Linux. First the good news -- it should work if you use a floppy since it will require adding the usb package to the boot floppy. The bad news, you won't be able to boot from the CD-ROM. You still might be able to load the packages off the CD-ROM but network packaging loading will be easier/faster. The first step will be to get the keyboard detected and working (which will require a few modifications to the usb package but shouldn't be hard and I'm working on now). I should be able to put out floppy boot image tonight and you (or anyone else) can test it on their system to make sure it works with their USB chipset. -mdf > I have a USB Keyboard, the Micro$oft Natural Keyboard Pro (yuck!), and I > tried to boot Trinux from CD. It detected my Ethernet card, and asked me > whether I wanted to configure it or not. It wouldn't let me press "y" or > "n" to reply so it was stuck. Any way you can help? Thanks in advance. > > Jeremy Linden > > > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > |
From: Jeremy L. <je...@ga...> - 2001-12-28 23:32:07
|
I have a USB Keyboard, the Micro$oft Natural Keyboard Pro (yuck!), and I tried to boot Trinux from CD. It detected my Ethernet card, and asked me whether I wanted to configure it or not. It wouldn't let me press "y" or "n" to reply so it was stuck. Any way you can help? Thanks in advance. Jeremy Linden |
From: Matthew F. <mf...@ci...> - 2001-12-28 14:52:46
|
Ok, its done (gdb.tgz). It runs but haven't checked on any real binaries/src though. -mdf > > I was wondering how much trouble it would be for you to include a gdb package for trinux? > > > "There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence." - Jeremy > S. Anderson - > > ____________________________________________________________________________________________________________________________________ > Chat with friends online, try MSN Messenger: Click Here > _______________________________________________ Trinux-talk mailing list Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > |