Difference between pages "SAFE Boot Disk" and "Talk:Linux Logical Volume Manager (LVM)"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Fixed broken link)
 
(Created page with "Should we change :To make the volume group known to the system :vgexport $VOLUMEGROUP to :To make the volume group known to the system :vgimport $VOLUMEGROUP ? vgexport ma...")
 
Line 1: Line 1:
{{Infobox_Software |
+
Should we change
  name = SAFE Boot Disk |
+
  maintainer = [[ForensicSoft]] |
+
  os = {{Windows}} |
+
  genre = {{Live CD}} |
+
  license = {{Commercial}} |
+
  website = [http://www.forensicsoft.com/catalog/products.php http://www.forensicsoft.com/catalog/products.php] |
+
}}
+
  
The '''System Acquisition Forensic Environment (SAFE) Boot Disk''' is the first and only commercially available forensically sound Windows Boot disk by [[ForensicSoft]]. SAFE is a fully licensed version of Windows PE protected that is protected by the proven [[SAFE Block XP]] software write blocking technology.
+
:To make the volume group known to the system
 +
:vgexport $VOLUMEGROUP
  
'''SAFE Boot Disk''' now allows you to boot any x86-based computer without the need to remove the drives or worry about the need for special adapters or controller cards. Because '''SAFE Boot Disk''' is based on Windows PE it includes built in driver support as well as the ability to easily install any drivers that may be missing. This also means the '''Safe Boot Disk''' includes built in support for the NTFS file system without the need for third party tools and has the ability to write to NTFS and NTFS compressed file systems, taking advantage of larger partition sizes, larger file size limits and the advantage of native NTFS compression.
+
to
  
In order to ensure the '''SAFE Boot Disk''' is a forensically sound Live CD it has the proven write blocking technology used by [[SAFE Block XP]] built in to ensure that upon booting every attached disk and flash device are automatically blocked without any required user interaction. Unlike some of the Linux Live CD's this is true write blocking and not just mounting read-only or not auto-mounting.
+
:To make the volume group known to the system
 +
:vgimport $VOLUMEGROUP
 +
?
  
Finally '''SAFE Boot Disk''' provides access to Host Protected Areas (HPAs) and Device Configuration Overlay (DCOs) on IDE (PATA and SATA) disks, has built in Case Logging and built in tools for exploration, viewing, and simple forensics functions.
+
vgexport makes volume groups ''unknown'' to the system, vgimport makes exported volumes ''known'' to the system. See also [http://www.tldp.org/HOWTO/LVM-HOWTO/recipemovevgtonewsys.html this]. You should also remember, that both vgexport/vgimport alter the data on the physical device. I also added "loop" option to the mount command example, since "-o ro" may alter the data in the file system (replay the journal, etc) [[User:.FUF|.FUF]] ([[User talk:.FUF|talk]]) 10:19, 7 May 2014 (CDT)

Latest revision as of 10:19, 7 May 2014

Should we change

To make the volume group known to the system
vgexport $VOLUMEGROUP

to

To make the volume group known to the system
vgimport $VOLUMEGROUP

?

vgexport makes volume groups unknown to the system, vgimport makes exported volumes known to the system. See also this. You should also remember, that both vgexport/vgimport alter the data on the physical device. I also added "loop" option to the mount command example, since "-o ro" may alter the data in the file system (replay the journal, etc) .FUF (talk) 10:19, 7 May 2014 (CDT)