View Single Post
  #3   (View Single Post)  
Old 18th February 2016
J65nko J65nko is offline
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 3,507

I just downloaded NetBSD-7.0-amd64-install.img.gz on my OpenBSD box. After gunziping it became:
$  ls -l NetBSD-7.0-amd64-install.img
-rw-r--r--  1 adriaan  wheel  576716800 Feb 18 21:57 NetBSD-7.0-amd64-install.img
Because I suspected that this was an bootable USB image I ran file(1) on it:
$ file NetBSD-7.0-amd64-install.img
NetBSD-7.0-amd64-install.img: x86 boot sector; partition 1: ID=0xa9, active, starthead 32, startsector 2048, 1124352 sector
So this confirmed it has a boot sector ......

Next step was to write this image to an USB stick/key (remember still using OpenBSD ):

Checking how the USB stick was detected
$ dmesg | tail
umass0 at uhub0 port 5 configuration 1 interface 0 "Innostor PenDrive" rev 2.10/0.01 addr 2
umass0: using SCSI over Bulk-Only
scsibus3 at umass0: 2 targets, initiator 0
sd0 at scsibus3 targ 1 lun 0: <Innostor, Innostor, 1.00> SCSI4 0/direct removable serial.1f750917000000000205
sd0: 15073MB, 512 bytes/sector, 30870077 sectors
Being detected as an OpenBSD sd0 device I wrote the NetBSD image:

$ sudo dd if=NetBSD-7.0-amd64-install.img of=/dev/rsd0c bs=1m
I can confirm this is an NetBSD install image, it booted successfully into the NetBSD installer......
Conclusion: NetBSD provides an install image, that you write to an USB key/stick
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote