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
disklabel(4)						     Kernel Interfaces Manual						      disklabel(4)

NAME
disklabel - Disk pack label SYNOPSIS
#include <sys/disklabel.h> DESCRIPTION
Each disk or disk pack on a system may contain a disk label which provides detailed information about the geometry of the disk and the par- titions into which the disk is divided. It should be initialized when the disk is formatted, and may be changed later with the disklabel program. This information is used by the system disk driver and by the bootstrap program to determine how to program the drive and where to find the file systems on the disk partitions. Additional information is used by the file system in order to use the disk most effi- ciently and to locate important file system information. The description of each partition contains an identifier for the partition type (standard file system, swap area, etc.). The file system updates the in-core copy of the label if it contains incomplete information about the file system. The label is located in sector number LABELSECTOR of the drive, usually sector 0 (zero) where it may be found without any information about the disk geometry. It is at an offset LABELOFFSET from the beginning of the sector, to allow room for the initial bootstrap. The disk sector containing the label is normally made read-only so that it is not accidentally overwritten by pack-to-pack copies or swap opera- tions; the DIOCWLABEL ioctl, which is done as needed by the disklabel program, allows modification of the label sector. A copy of the in-core label for a disk can be obtained with the DIOCGDINFO ioctl; this works with a file descriptor for a block or charac- ter (raw) device for any partition of the disk. The in-core copy of the label is set by the DIOCSDINFO ioctl. The offset of a partition cannot generally be changed, nor made smaller while it is open. One exception is that any change is allowed if no label was found on the disk, and the driver was able to construct only a skeletal label without partition information. Finally, the DIOCWDINFO ioctl operation sets the in-core label and then updates the on-disk label; there must be an existing label on the disk for this operation to succeed. Thus, the initial label for a disk or disk pack must be installed by writing to the raw disk. All of these operations are normally done using the disklabel program. RELATED INFORMATION
Files: disktab(4) Commands: disklabel(8) delim off disklabel(4)