Partition size for dual boot Ubuntu BT3 install

[rofler]

Hello, I am new to these forums, but I have read the guidelines, and I have searched the forums, etc.

I have an XPS M1330 w/ 4GB RAM that is being shipped from Dell pre-installed with Ubuntu (no Windows tax)

I am going to be dual booting BT3 onto my 200gb HD with Ubuntu.

I want to make a partition for backtrack so that Ubuntu's performance is not affected in any way by the size of the Hard drive space being used up by BT3, but still have BT3 run as fast as possible.

What size should I partition for BT3 if

a) There is no separate mount partition for /home
b) There is a separate mount partition for /home

I just need approximate values so that I can decide which is better to do.

P.S. I know about half of the people that will post on this thread will say give Backtrack 100%, but I am looking for an answer that I can actually use.

Thank you in advance.

--Rofler

[purehate]

I think you are a little confused. Putting certain files on a separate partition is more of a protection thing rather than a speed thing. Normally the /boot files and the kernel are put on a separate partition in order to protect them in case of a system problem. I think you will find when your "pre installed" ubuntu set up arrives it will have a /boot partition. you can use the same boot partition to store backtracks kernel and boot files.

A real install of backtrack needs 2.7 gigs so a min of 4 gigs is what I would recommend. I also recommend this because new linux user of install backtrack and the find its not what they thought it was. Its designed to operate from a usb or live cd enviorment. Its is also a security and penetration testing distro. Its not really good for email and you tube watching. If you are new to linux I would stick with your ubuntu for the time being.

[theprez98]

The answer to almost every question (other than "42") is:

It depends.

[rofler]

I'm not actually new to linux, I'm just new to dual booting linux distro's. I want to install BT3 largely so that I can keep the programs seperate from Ubuntu.

BT3 is a pentesting distro, I understand that.
It's also one of the best free security auditing cd's I'll find anywhere.
With no intention to run something like VMWare, I am planning to have BT3 permanently on my HD.
Thank you for clearing up the whole partition not equal to speed thing.
I think I will have a seperate home mount however, just so that it is easy to expand when it's full.

One last question, if I were to set up rainbow tables (WPA mostly) on my Compjter, where would be the best storage place? A partition? Or Home? Or somewhere else?

Thank you so much

--Rofler

[erg01]

...you can use the same boot partition to store backtracks kernel and boot files.

I want to make sure I am understanding this (as a Linux noob)...
Here are my assumptions as I understand them:
1. I want to use MORE than one Linux kernel for a triple boot scenario: One Windows, two Linux-es. I.e; the 'image=/boot/<kernel-filename>' entry in LILO.conf tells LILO where to 'find' the boot image.
2. I want ANOTHER linux distribution on it's own (fresh) partition (hda9).
3. Both Linux-es can share the existing swap partition (hda7)

So:
If I was to add yet another Linux OS to my existing hard drive, on a freshly created partition, then could I boot it by editing LILO like so (after copying the NEW linux kernel and boot files to the existing /boot directory):

LILO.conf before adding another Linux reference:

# Windows bootable partition config begins
other = /dev/hda1
label = WinXP
table = /dev/hda
# Windows bootable partition config ends

# BackTrack2.0 bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda8
label = BT2-Linux
read-only
# BackTrack2.0 bootable partition config ends


LILO.conf AFTER adding another Linux reference:

# Windows bootable partition config begins
other = /dev/hda1
label = XP-SP2
table = /dev/hda
# Windows bootable partition config ends

# BackTrack2.0 bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda8
label = BT2-Linux
read-only
# BackTrack2.0 bootable partition config ends

# NEW Linux bootable partition config begins
image = /boot/newVmlinuz
root = /dev/hda9
label = NEW-Linux
read-only
# NEW Linux bootable partition config ends

...where hda8 would be my existing Linux (BackTrack) root and hda9 would be the newly created Linux root.

My existing /boot is on hda6 and hda7 is the swap partition.
As long as my new /etc/fstab file is configured to point to these and LILO can find the NEW kernal (with it's own unique file name to distinguish it from the exisitng Linux/BT), will this work?

If not: what am I missing and what are my false assumptions?

(Not TRYING to muddy the water here )