Difference between revisions of "Talk:Burning the Installation Media"

From PC-BSD Wiki
Jump to: navigation, search
(helpful for USB sticks)
m (style only)
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
 
==helpful for USB sticks==
 
==helpful for USB sticks==
* no need to zero the entire thing, can be a limited zero that will be as effective- dd if=/dev/zero of=/dev/usbstick bs=1024 count=10
+
* no need to zero the entire thing, can be a limited zero that will be as effective- <code>dd if=/dev/zero of=/dev/usbstick bs=1024 count=10</code>
  
 
* If KDE or Dolphin or Device Notifier succeed to mount a USB stick but you cannot unmount it, even when you are not actively using it, switch to root and then issue the shell command.
 
* If KDE or Dolphin or Device Notifier succeed to mount a USB stick but you cannot unmount it, even when you are not actively using it, switch to root and then issue the shell command.
  
* A USB stick can be subdivided as any other HDD could: first gpart create, then newfs. So, gpart create -s MBR /dev/usbstick then gpart add -t freebsd -s <size you want> /dev/usbstick and finally, mount -t ufs /dev/usbstick /mount/point. If a USB stick might be used for an installer image, one slice could be 5120M and the remaining space is chosen by leaving off the size designation, such as gpart add -t freebsd /dev/usbstick. To use the first partition of the usb stick for the image, use dd if=<image> of=/dev/da0s1 bs=512M.
+
* A USB stick can be subdivided as any other HDD could: first gpart create, then newfs. So, <code>gpart create -s MBR /dev/usbstick</code> then <code>gpart add -t freebsd -s <size you want> /dev/usbstick</code> and finally, <code>mount -t ufs /dev/usbstick /mount/point</code>. If a USB stick might be used for an installer image, one slice could be 5120M and the remaining space is chosen by leaving off the size designation, such as <code>gpart add -t freebsd /dev/usbstick</code>. To use the first partition of the usb stick for the image, use <code>dd if=<image> of=/dev/da0s1 bs=512M</code>.
 +
 
 +
* Dolphin/Device Notifier caveat: It may allow a mount point within /media to be created, but it is possible that the ownership or permissions could be wrong. Best case is that /media/mountname is owned by you and wheel group. <code>chown username:wheel /media/mountname</code>.
 +
 
 +
* Live media caveat: This method may not be compatible with booting the usb on any random system. In that situation, simply zero and then dd the image to the stick. Perhaps if the BSD boot selector is added it may work, but that has not yet been verified.
  
 
Of course the above is generic and some adjustments are needed.
 
Of course the above is generic and some adjustments are needed.

Latest revision as of 12:44, 10 June 2012

[edit] helpful for USB sticks

  • no need to zero the entire thing, can be a limited zero that will be as effective- dd if=/dev/zero of=/dev/usbstick bs=1024 count=10
  • If KDE or Dolphin or Device Notifier succeed to mount a USB stick but you cannot unmount it, even when you are not actively using it, switch to root and then issue the shell command.
  • A USB stick can be subdivided as any other HDD could: first gpart create, then newfs. So, gpart create -s MBR /dev/usbstick then gpart add -t freebsd -s <size you want> /dev/usbstick and finally, mount -t ufs /dev/usbstick /mount/point. If a USB stick might be used for an installer image, one slice could be 5120M and the remaining space is chosen by leaving off the size designation, such as gpart add -t freebsd /dev/usbstick. To use the first partition of the usb stick for the image, use dd if=<image> of=/dev/da0s1 bs=512M.
  • Dolphin/Device Notifier caveat: It may allow a mount point within /media to be created, but it is possible that the ownership or permissions could be wrong. Best case is that /media/mountname is owned by you and wheel group. chown username:wheel /media/mountname.
  • Live media caveat: This method may not be compatible with booting the usb on any random system. In that situation, simply zero and then dd the image to the stick. Perhaps if the BSD boot selector is added it may work, but that has not yet been verified.

Of course the above is generic and some adjustments are needed.