On 7/12/06, Jirtme Loyet <jerome@loyet.net> wrote:
> This an extreme case: It's on a remote server on which I have only access to
> a rescue linux. So from this linux, I want to create an customm installer,
> to pack it and install it on the disk so that after reboot openbsd would
> install itselft automatically. I've find equivalent for many utilities from
> openbsd to linux but the last operation (install the openbsd bootloader on
> the image which is localy mounted) need more work. I'll try to use grub
> instead of the openbsd bootloader and if it's not working, I'll have to port
> installboot to linux. That's why I was looking for a port for installboot.

Not renewing the contract or switching providers, and making their
management aware of the reason is a great way to provide awareness of
*BSD and the need for their customers to have the choice to use
alternate OS's, or something so standard as serial console access.
This can help the OpenBSD project in the long run, as indirect as it
may be.

This is similar to hounding a hardware vendor to provide exact chipset
names and revisions of the hardware they try to sell you, and not
accepting "It is supported in linux" as an answer.

Sometimes you have to be square with these companies that think they
are "hip" to open source solutions. They're full of smoke. Just my two
cents.