Trinity Rescue Kit & MultiPass - USB Hacks - Hak5 PDF

Download as pdf or txt
Download as pdf or txt
You are on page 1of 9

USB Hacks

Home  Projects  USB Hacks  Trinity Rescue Kit & MultiPass  All Activity

Trinity Rescue Kit & MultiPass 

By Ingo
August 25, 2009 in USB Hacks

Reply to this topic

I can't seem to find the thread about the episode anymore... maybe just my own incompetense, but
anyways...
IHas anyone got Trinity Rescue Kit boot off MultiPass without problems?
n
gFirst TRK tells me that no CD was found and starts to check for HDDs and USB sticks
oThen it tells me that "cat: /etc/trkhd: No cusch file or directory"
Posted
August
"25,Seems we didn't find anything yet. Trying CD-drives once more"
2009
"Trying to find TRK on your 0 CD-drive(s)"
"Seems we didn't find teh TRK medium"
Then it asks me to manualy enter the device, so I give my USB stick which is "sdb1"
and again "/trk/trk3/trkramfs: No such file or directory"
and I get root@(none):# promp
My MultiPass lines for TRK
title Trinity Rescue Kit 3.3 build 321
kernel /TRK/kernel.trk initrd=/initrd.trk ramdisk_size=49152 root=/dev/ram0 vg
initrd /TRK/initrd.trk
Any ideas how to make this boot normaly?

 Quote

HThread
Pick one:
H
@   Reliom said:
L 

0 How to get Trinity Rescue Kit up and running


_ 1. Copy the TRK ISO contents to the "Root" of your USB Stick
F
0 2. Rename your USB stick to "TRK_3-3" without quotes... if you do not do this it will give you the
0 error that it cannot find the CD etc.
Posted
August
3. Add this to your "menu.lst"
25,
2009title Trinity Rescue Kit
configfile /submenu.lst
4. Create another list file called "submenu.lst" and add this to it. Note: You dont need them all
just the ones you want to use or if you only want a couple you can just add them to your
menu.lst instead.
title Main-menu
configfile /menu.lst
title TRK 3.3
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
initrd /initrd.trk
title TRK 3.3 - as bootserver to boot other TRK clients
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
trkbootnet
initrd /initrd.trk
title TRK 3.3 - running from RAM (best >= 512mb, 256mb min)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
trkinmem
initrd /initrd.trk
title TRK 3.3 - with bigger screenfont
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
normalfont
initrd /initrd.trk
title TRK 3.3 - in simple VGA mode (debugging of kernel output)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=1 pci=conf1 splash=off
initrd /initrd.trk
title TRK 3.3 - with Belgian keyboard (see docs for other)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
keyb_be
initrd /initrd.trk
title TRK 3.3 - Virusscan all drives (non interactive)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
virusscan
initrd /initrd.trk
title TRK 3.3 - Try more pcmcia and usb nics (when not detected)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
pcmcia
initrd /initrd.trk
title TRK 3.3 - Try more SCSI drivers (when disks not detected)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
scsidrv
initrd /initrd.trk
title TRK 3.3 - with a secure shell server enabled
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 sshd
initrd /initrd.trk
title TRK 3.3 - Execute local scripts on harddrive of PC
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
locscr
initrd /initrd.trk
title TRK 3.3 - Fileshare all drives, secured with user
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
smbsec
initrd /initrd.trk
title TRK 3.3 - Fileshare all drives as guest, no security
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
smbguest
initrd /initrd.trk
title TRK 3.3 - Single user mode
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
runlevel 1
initrd /initrd.trk
title TRK 3.3 - Acpi=off, noapic PCI=bios (Alternate boot 1)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose acpi=off noapic
pci=bios
initrd /initrd.trk
title TRK 3.3 - Acpi=off, noapic PCI=any (Alternate boot 2)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose acpi=off noapic
initrd /initrd.trk
title TRK 3.3 - PCI=conf2 (Alternate boot 3)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf2
initrd /initrd.trk
title TRK 3.3 - Verbose startup for debugging after initial bootfase
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
debugging
initrd /initrd.trk
timeout 100
title TRK 3.3 - SSH server and run from RAM
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 sshd
trkinmem
initrd /initrd.trk
title TRK 3.3 - SSH server, run from RAM, act as a secure fileserver
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 sshd
trkinmem smbsec
initrd /initrd.trk
title TRK 3.3 - with proxyserver support enabled
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
proxy
initrd /initrd.trk
title Memory tester: Memtest86+ v1.65
kernel memtest.x86
Edit/Note
When using updatetrk it copies everything from the root of where TRK was booted and rebuilds
which is going to thrash your usb stick and probably not work after it does... that is if you have
other files like BT4 etc on it... to get around this at least for now you can trk2usb it on another
usb update that one then copy the files over to the Multipass

  hobbyhack said: 

Trinity is working from it's own directories


1. create the trinity USB as shown in the show from the CD using the command line
2. copy all of the files on the trinity usb to /boot/trinity/ on your multipass usb drive - except
/trk3 dir
3. copy the /trk3 directory from the trinity usb to root of the multipass usb
When it boots it will ask you to identify where your USB is located (usually /sdb1)
title Trinity Rescue Kit
kernel /boot/trinity/kernel.trk initrd=/boot/trinity/initrd.trk ramdisk_si
initrd /boot/trinity/initrd.trk

This isn't perfect because you still have to tell it where the usb drive is but it keeps the root
directory clean.

  haxwithaxe said: 

Cheater's Trinity How To:


I'm being lazy and this is how i got trinity to work for me.
1) make a fat16 partition 128MB or larger behind the original one with the lable TRK_3-3.
2) boot into trk from cd and run trk2usb -n -d /dev/sdxY Where x= letter of thumb drive and Y=
the number of partition if it's the second one then Y=1
3) edit your menu.lst to have the following(adjust to fit your partition table)
title Trinity Rescue Kit
map (hd0,1)+1 (fd0)
map --hook
rootnoverify (fd0)
chainloader +1

thanks to romiz for how to chainload syslinux/isolinux from grub4dos


http://knowhowbyromiz.blogspot.com/2008/09...x-and-back.html

  casca said: 

I haven't tried this yet but found this in the Trinity Documentation
Link

 Quote

Thanks, mate!
I was hoping for something like Hobbyhack's method, but by the love of God I coudn't get it to work,
IReliom's method in other hand worked pefectly fine and also he did nice work with the submenu
nsadly now I have to keep TRK files in root of my USB -stick, but that shoudn't be all that big of a deal.
g
oAgain thank you for your effrots *bow*
Posted
August
25, Quote
2009
2 months later...

DHey!
d thought I'd share how to get Trinity Rescue Kit working by booting the ISO from Grub4dos.
Just
s
k
h title Trinity Rescue Kit - ISO

a map --mem (hd0,0)/trinity-rescue-kit.3.3-build-334.iso (hd32)

k map --hook

5 chainloader (hd32)

Posted
boot

November
3,On boot, it asks you where TRK is, and I reply sda1 since I am booting off USB. Might be different. I'm
2009
not sure if you need to unpack the /trk folder from the ISO in order for it to work.

 Quote

6 months later...

DThank you!!
This was perfect.
D
u
n Quote
D

e
a
d
Posted
May
4,
2010

D   dskhak5 said: 

D Hey!
u Just thought I'd share how to get Trinity Rescue Kit working by booting the ISO from Grub4dos.
n
D
e title Trinity Rescue Kit - ISO

a map --mem (hd0,0)/trinity-rescue-kit.3.3-build-334.iso (hd32)

d map --hook
Postedchainloader (hd32)
May boot
4,
2010
On boot, it asks you where TRK is, and I reply sda1 since I am booting off USB. Might be
different. I'm not sure if you need to unpack the /trk folder from the ISO in order for it to work.
Sorry for the double post
Thank You!!!
It worked pefectly

 Quote

12 years later...

EOldwouldthreadfail withbut theI founderror.out that the USB drive will only work on USB1 port. USB2 and USB3 ports
E
u
g Quote
e
n
e
Posted
December
6,
2022



Please do not bump old threads.
J Quote
t

y
l
e
6
Posted
December
6,
2022

Join the conversation


You can post now and register later. If you have an account, sign in now to post with your
account.

 Reply to this topic...

  Share
Followers 0

 Go to topic listing

Recently Browsing   0 members


No registered users viewing this page.

Home  Projects  USB Hacks  Trinity Rescue Kit & MultiPass  All Activity
Theme  Contact Us
Hak5 LLC
Powered by Invision Community

You might also like