Why BackTrack3 Stored in USB Can Not Save Changes? What is the Theory Behind it?


 
Thread Tools Search this Thread
Special Forums UNIX Desktop Questions & Answers Why BackTrack3 Stored in USB Can Not Save Changes? What is the Theory Behind it?
# 1  
Old 01-13-2009
Why BackTrack3 Stored in USB Can Not Save Changes? What is the Theory Behind it?

I have a 16 GB Flash Drive. I changed the settings & set it as local disk, so my Vista recognizes it as a local disk, not removable disk.

After that, i deleted the whole partition & then i made new partitions. I chose 9 GB to be in FAT32 format & 7 GB will be in ex2 format to save future changing in BT3.

Questions:

1. Why backtrack in FAT32 format can not save changes even though there are a lot of space?
2. How backtrack in FAT32 is related to EX2 partition?
3. Windows does not recognize EX2 partition, does this mean when i plug my USB on machine with Win OS, all my changes in backtrack will not appear?
3. Windows has only two partition formats FAT & NTFS - As far as i know. How many formats Linux have, what are they? and what is the role of each format?
4. What partition formats are called file system?

I'm new towards these stuff, i hope you can clarify to me in an easy & simple way.
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Save value from output of Corestat and save in a list for each core

I am trying to modify the "corestat v1.1" code which is in Perl.The typical output of this code is below: Core Utilization CoreId %Usr %Sys %Total ------ ----- ----- ------ 5 4.91 0.01 4.92 6 0.06 ... (0 Replies)
Discussion started by: Zam_1234
0 Replies

2. UNIX for Dummies Questions & Answers

USB-USB cable between linux and windows computers

Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive. Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies

3. Solaris

SUN Custer Theory

Hi, Newbie to the cluster, Would like to some basic idea on the cluster framework.:confused: Any pointer to a link which is useful.:p How to explain on cluster's disk? :( Scenario, node1, node2, Storage1 and Storage2. 1. If storage1 attached to node1, and node1 fault; node1 failed to... (10 Replies)
Discussion started by: simka
10 Replies
Login or Register to Ask a Question
WREN(3) 						     Library Functions Manual							   WREN(3)

NAME
wren, ata - hard disk interface SYNOPSIS
bind #H[drive] /dev bind #w[target[.lun]] /dev /dev/hd0disk /dev/hd0partition /dev/sd0disk /dev/sd0partition ... DESCRIPTION
The hard disk interfaces (wren, #w, is a SCSI disk; ata, #H, is an IDE or ATA disk) serve a one-level directory giving access to the hard disk partitions. The parameter to attach defines the numerical SCSI target and logical unit number or the IDE drive number to access. Both default to zero. Each partition name is prefixed by hd and the numeric drive identifier. The partition always exists and covers the entire disk. The size of each partition as reported by stat(2) is the number of bytes in the partition, so the size of is the size of the entire disk. The partition also always exists; it is the last block on the disk for SCSI, second to last for IDE. If it contains valid partition data, those partitions will be visible as well. Every time the device is bound, the partitions are updated to reflect any changes in the parti- tion file. The format of the partition file is the string plan9 partitions on a line, followed by partition specifications, one per line, consisting of a name and textual strings for the block start and limit for each partition on the disk. The program prep(8) writes the partition table for the disk; its use is preferred to writing it by hand. SEE ALSO
prep(8), scsi(3) SOURCE
/sys/src/9/port/devwren.c /sys/src/9/pc/devata.c WREN(3)