The reason why you cannot just mount the partitions is because you have a disc image not images of individual partitions. You would need the offsets of the different partitions and use those when mount using its the loop and offset options.
In your case I would play back the image and then upgrade, but you don't indicate how you connected the 2.5" to you desktop computer, or how you are going to do that now. If you are going to use USB, then upgrading before playback is probably faster (but a bit more work), assuming the image is on an internal SATA drive. Because of the USB 2.0 vs SATA speed differences the upgrading is going to take longer. The playback of the image (upgraded or not) will take the same time.
If you want to upgrade before playback, then use parted to find the start of the images. parted hd.img
will give you a list of partition numbers, start and end. With the start information e.g 12345 you can mount a partition in the disk image:
mount -o loop,ro,offset=12345 hd.img /mnt/tmp
You might need to specify the partition type as well if your desktop does not recognise it. You can then update your fresh install with that info, remount the partition rw
clean out the partition and write things back. The only thing I am not sure about is if that would consfuse the ATX board's bootloader, but upgrading a system restored to disk would have the same problem.
while httpd
supports using patterns
in the context of some keywords (alias match
, location match
, server match
) the functionality you are looking for is not implemented in httpd
.
i see two ways to realize your intentions:
- crosspost on the
openbsd-misc
mailing list - one of the authors of httpd
might pick you up there
- use
pf
to firewall. i do strongly recommend this way for various reasons including
- higher grade of protection against denial-of-service types of attacks as the application (
httpd
) does not have to take any load
- packets from clients can be inspected and blocked on a global (
IP
) wide level - i.e. a flooding client may not connect to the ssh
port
i my opinion, pf
can be a very satisfying thing to learn.
besides, i suspect a possible answer to an according post on openbsd-misc
to be similar to my recommendation :)
Best Answer
Don't build from source. I've been following current for several years. You can do binary upgrades to new snapshots. And you can do a direct binary upgrade from release/stable to current.
Reboot.
At the prompt type:
Go through the motions of upgrading. When it asks for a hostname, I use this one, it's quite fast
When it asks for a path, change it to
Substitute amd64 for your architecture.
Continue with the upgrade prompts
Reboot after it's done.
Change PKG_PATH
Add this to ~/.profile and /root/.profile
Then run
In the future, you won't have to change PKG_PATH or the bsd.rd file path. It will remember. Like pepperidge farm.
To update to a new snapshot in the future, just
One thing to note. When the upgrade to a new snapshot will take you to a new version number, like from 6.2 to 6.3 which will happen rather soon, booting bsd.rd and following the prompts will only allow you to download the new bsd.rd ramdisk. You must reboot after it's finished and re-enter bsd.rd to continue with the upgrade. But you'll only have to do this once every six months, and it's automatic. Just don't freak out when it only says it's downloading bsd.rd
If you want to know if you should upgrade, just bookmark:
In your browser and visit it to check the dates on the archives.
Don't forget to visit one directory up once in a while:
To snag ports.tar.gz and update your ports tree