aboutsummaryrefslogtreecommitdiff
path: root/docs/bsd/openbsd.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/bsd/openbsd.md')
-rw-r--r--docs/bsd/openbsd.md26
1 files changed, 13 insertions, 13 deletions
diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md
index 284f0468..783bd7bb 100644
--- a/docs/bsd/openbsd.md
+++ b/docs/bsd/openbsd.md
@@ -11,7 +11,7 @@ LibertyBSD and prioritise that in this guide.
This section relates to preparing, booting and installing OpenBSD on
your libreboot system, using nothing more than a USB flash drive (and
-*dd*). They\'ve only been tested on a Lenovo ThinkPad x200.
+*dd*). They've only been tested on a Lenovo ThinkPad x200.
- [Prepare the USB drive (in OpenBSD)](#prepare)
- [Installing OpenBSD without full disk encryption](#noencryption)
@@ -44,7 +44,7 @@ Connect the USB drive. Check dmesg:\
Check to confirm which drive it is, for example, if you think its sd3:\
**\$ disklabel sd3**
-Check that it wasn\'t automatically mounted. If it was, unmount it. For
+Check that it wasn't automatically mounted. If it was, unmount it. For
example:\
**\$ doas umount /dev/sd3i**\
@@ -85,7 +85,7 @@ Connect the USB drive. Check dmesg:\
Check lsblk to confirm which drive it is:\
**\$ lsblk**
-Check that it wasn\'t automatically mounted. If it was, unmount it. For
+Check that it wasn't automatically mounted. If it was, unmount it. For
example:\
**\$ sudo umount /dev/sdX\***\
**\# umount /dev/sdX\***
@@ -141,7 +141,7 @@ to boot a truly fully encrypted OpenBSD or LibertyBSD installation, by
putting everything in the flash chip.**
Alternatively, modifying GRUB to support booting fully encrypted OpenBSD
-installations would be possible, but probably not feasible; it\'s an
+installations would be possible, but probably not feasible; it's an
alien codebase to the OpenBSD project, not tightly integrated and the
OpenBSD bootloader already works.
@@ -166,22 +166,22 @@ OpenBSD will start booting. Yay!
Configuring Grub
----------------
-If you don\'t want to drop to the GRUB command line and type in a
+If you don't want to drop to the GRUB command line and type in a
command to boot OpenBSD every time, you can create a GRUB configuration
-that\'s aware of your OpenBSD installation and that will automatically
+that's aware of your OpenBSD installation and that will automatically
be used by libreboot.
On your OpenBSD root partition, create the **/grub** directory and add
the file **libreboot\_grub.cfg** to it. Inside the
**libreboot\_grub.cfg** add these lines:
-**default=0 timeout=3 menuentry \"OpenBSD\" {\
+**default=0 timeout=3 menuentry "OpenBSD" {\
    kopenbsd -r sd0a (ahci0,openbsd1)/bsd\
}\
**
-The next time you boot, you\'ll see the old Grub menu for a few seconds,
-then you\'ll see the a new menu with only OpenBSD on the list. After 3
+The next time you boot, you'll see the old Grub menu for a few seconds,
+then you'll see the a new menu with only OpenBSD on the list. After 3
seconds OpenBSD will boot, or you can hit enter to boot.
[Back to top of page](#pagetop).
@@ -191,16 +191,16 @@ seconds OpenBSD will boot, or you can hit enter to boot.
Troubleshooting
===============
-Most of these issues occur when using libreboot with coreboot\'s \'text
-mode\' instead of the coreboot framebuffer. This mode is useful for
+Most of these issues occur when using libreboot with coreboot's 'text
+mode' instead of the coreboot framebuffer. This mode is useful for
booting payloads like memtest86+ which expect text-mode, but for OpenBSD
it can be problematic when they are trying to switch to a framebuffer
-because it doesn\'t exist.
+because it doesn't exist.
In most cases, you should use the vesafb ROM images. Example filename:
libreboot\_ukdvorak\_vesafb.rom.
-won\'t boot\...something about file not found
+won't boot\...something about file not found
---------------------------------------------
Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and