Difference between pages "Nickfile (NK2)" and "Talk:Linux Logical Volume Manager (LVM)"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(External Links)
 
(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:
[[Microsoft]] [[Outlook]] uses the '''Nickfile (NK2)''' to store e-mail address aliases.
+
Should we change
  
The file type is also known as the Outlook AutoComplete File or the Nickname file.
+
:To make the volume group known to the system
 +
:vgexport $VOLUMEGROUP
  
== MIME types ==
+
to
  
The actual mime type of the NK2 format is unspecified
+
:To make the volume group known to the system
 +
:vgimport $VOLUMEGROUP
 +
?
  
== File signature ==
+
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)
 
+
The NK2 has the following file signature:
+
hexadecimal: 0D F0 AD BA
+
 
+
Note that other sources claim that the file signature is
+
hexadecimal: 0D F0 AD BA 0A 00 00 00
+
 
+
== Contents ==
+
 
+
The NK2 basically contains a list of items. The attributes of these items are defined by the [[Microsoft]] [[Outlook]] [[Message API (MAPI)]].
+
 
+
== External Links ==
+
 
+
* [https://googledrive.com/host/0B3fBvzttpiiSZFNVS2JjWkNnelk/Nickfile%20(NK2)%20format.pdf Nickfile (NK2) format specification], by the [[libnk2|libnk2 project]]
+
* [https://googledrive.com/host/0B3fBvzttpiiSRlR1QkU5Vk43ZWs/MAPI%20definitions.pdf MAPI definitions], by the [[libpff|libpff project]]
+
 
+
[[Category:File Formats]]
+

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)