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
IMEDIFF2(1)															       IMEDIFF2(1)

NAME
imediff2 - An interactive fullscreen 2-way merge tool SYNOPSIS
imediff2 [-m] [-u] [-a] [-b] [-c] [-N new-file] [-o outputfile] {file1} {file2} DESCRIPTION
Merge two (slightly different) files interactively with a user friendly fullscreen interface in text mode. Imediff2 shows the differences of given two files (in color if the terminal supports them), lets you scroll the file and toggle changes be- tween old and new version one by one. If the 'unresolved' mode is enabled, you can optionally save both versions. Additionally, if the $EDITOR environment variable is set or if /usr/bin/editor exists and is executable, you can also launch an external editor and manually edit the half-merged file before saving it, perhaps to resolve the 'unresolved' parts. Empty lines are shown in reverse colors so you see that you can select them. If a line is missing completely from one file, imediff2 dis- plays it as a reversed '?'. While it seems to take one line in the editing phase, it is naturally not saved into the output file. To see a list of keyboard commands, hit h or ? in the editor. The program exits with status 0 if the changes were saved, 1 if the merging was aborted and 2 if the parameters were invalid. OPTIONS
-o outputfile, --output=outputfile Write output to given file. If missing, changes will not be saved. -N, --new-file Treat absent files as empty. -m, --mono Force monochrome display. -u, --unresolved Enable 'unresolved' mode (see above). -a Start with version A (default). -b Start with version B. -c Start with unresolved changes (implies -u). -h, --help Show summary of options and exit. -V, --version Show version and exit. KEYBOARD COMMANDS
The following keyboard commands are available in the editor. h, ? Show commands. up, down, left, right Move in document. page up, page down Move a screenfull. enter Toggle selected change. n, tab, space Jump to next change. p Jump to previous change. a Set current chunk to version A. b Set current chunk to version B. u Set current chunk to unresolved. shift+a Set all changes to version A. shift+b Set all changes to version B. shift+u Set all changes to unresolved. e Launch external editor. r Discard editor-made changes. (Available only after e.) x, s Save and exit. q, ctrl+c Exit without saving. home, end Jump to start or end. SEE ALSO
sdiff (1), diff (1), merge (1), diff3 (1). COPYRIGHT
This manual page as well as the program itself was written by Jarno Elonen (<elonen@iki.fi>). Unlike the program itself, which is licensed under the GNU General Public License (GPL) version 2 (or any later version, at your option), this document has been placed into the Public Domain. AUTHOR
Jarno Elonen. 2006-03-10 IMEDIFF2(1)