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

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Created page with '{{Infobox_Software | name = SAFE Boot Disk | maintainer = ForensicSoft | os = {{Windows}} | genre = {{Live CD}} | license = {{Commercial}} | website = [http://www…')
 
(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/product.php http://www.forensicsoft.com/catalog/product.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.
+
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 [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 11: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)