aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSwift Geek <swiftgeek@gmail.com>2018-06-25 17:20:53 +0000
committerGogs <gogitservice@gmail.com>2018-06-25 17:20:53 +0000
commit40ab88187f77400c3aac7c16e45a43ab3dfdc8eb (patch)
treef832b9da50939680c1303514b8c91cdb1c2e7c1a /docs
parentdcdd7b0237e1f635b87c2215b5ddfd75b017f65a (diff)
parent89961a3cb7d38575c09ef72c350b7bddadf01756 (diff)
downloadlibrebootfr-40ab88187f77400c3aac7c16e45a43ab3dfdc8eb.tar.gz
librebootfr-40ab88187f77400c3aac7c16e45a43ab3dfdc8eb.zip
Merge branch 'www/fix-dead-links' of libreboot/libreboot into master
Diffstat (limited to 'docs')
-rw-r--r--docs/gnulinux/configuring_parabola.md2
-rw-r--r--docs/gnulinux/encrypted_parabola.md4
-rw-r--r--docs/gnulinux/grub_boot_installer.md2
-rw-r--r--docs/hardware/gm45_remove_me.md2
-rw-r--r--docs/hardware/x200.md6
-rw-r--r--docs/install/index.md2
-rw-r--r--docs/install/rpi_setup.md2
7 files changed, 7 insertions, 13 deletions
diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 1e525f59..935ff099 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -63,7 +63,7 @@ For more information related to `pacman`, review the following articles on the A
* [Configuring pacman](https://wiki.parabolagnulinux.org/Installation_Guide#Configure_pacman)
* [Using pacman](https://wiki.archlinux.org/index.php/Pacman)
-* [Additional Repositories](https://wiki.parabolagnulinux.org/Official_Repositories>)
+* [Additional Repositories](https://wiki.parabolagnulinux.org/Official_Repositories)
## Updating Parabola
Parabola is kept up-to-date, using `pacman`. When you are updating Parabola,
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index 74c74fce..48ef5b76 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -102,7 +102,7 @@ You can either fill the header with zeroes, or with random data; again, I chose
Also, if you're using an SSD, there are a two things you should keep in mind:
- There are issues with TRIM; it's not enabled by default through LUKS,
-and there are security issues, if you do enable it. See [this page](https://wiki.archlinux.org/index.php/Dm-cryptSpecialties#Discard.2FTRIM_support_for_solid_state_drives_.28SSD.29) for more info.
+and there are security issues, if you do enable it. See [this page](https://wiki.archlinux.org/index.php/Dm-crypt#Specialties) for more info.
- Make sure to read [this article](https://wiki.archlinux.org/index.php/Solid_State_Drives),
for information on managing SSD's in Arch Linux (the information applies to Parabola, as well).
@@ -381,7 +381,7 @@ for the LUKS passphrase, apply here as well. You will set this password with the
### Extra Security Tweaks
There are some final changes that we can make to the installation, to make it
-significantly more secure; these are based on the [Security](https://wiki.archlinux.org/index.php/Securit) section of the Arch wiki.
+significantly more secure; these are based on the [Security](https://wiki.archlinux.org/index.php/Security) section of the Arch wiki.
#### Key Strengthening
We will want to open the configuration file for password settings, and increase
diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md
index 7086b71d..7d4375e6 100644
--- a/docs/gnulinux/grub_boot_installer.md
+++ b/docs/gnulinux/grub_boot_installer.md
@@ -25,7 +25,7 @@ Overwrite the drive, writing your distro ISO to it with `dd`. For example, if we
That's it! You should now be able to boot the installer from your USB drive (the instructions for doing so will be given later).
## Prepare the USB drive in NetBSD
-[This page](https://wiki.netbsd.org/tutorials how_to_install_netbsd_from_an_usb_memory_stick/) on the NetBSD website shows how to create a NetBSD bootable USB drive, from within NetBSD itself. You should the `dd` method documented there. This will work with any GNU+Linux ISO image.
+[This page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) on the NetBSD website shows how to create a NetBSD bootable USB drive, from within NetBSD itself. You should the `dd` method documented there. This will work with any GNU+Linux ISO image.
## Prepare the USB drive in FreeBSD
[This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on the FreeBSD website shows how to create a bootable USB drive for installing FreeBSD. Use the `dd` method documented. This will work with any GNU+Linux ISO image.
diff --git a/docs/hardware/gm45_remove_me.md b/docs/hardware/gm45_remove_me.md
index 0ac2f49b..26e5f9f6 100644
--- a/docs/hardware/gm45_remove_me.md
+++ b/docs/hardware/gm45_remove_me.md
@@ -418,7 +418,7 @@ region.
According to the datasheet, it's supposed to add up to 0xBABA but can
actually be others on the X200.
-<https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums>
+<https://web.archive.org/web/20150912070329/https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums>
*"One of those engineers loves classic rock music, so they selected
0xBABA"*
diff --git a/docs/hardware/x200.md b/docs/hardware/x200.md
index 10f5f621..fdf992d1 100644
--- a/docs/hardware/x200.md
+++ b/docs/hardware/x200.md
@@ -132,12 +132,6 @@ comparing it with X200 (factory BIOS) and X200 (gm45 raminit code in
coreboot), to see what the differences are. Then tweak raminit code
based on that.
-Trouble undocking (button doesn't work)
-----------------------------------------
-
-This person seems to have a workaround:
-<https://github.com/the-unconventional/libreboot-undock>
-
LCD compatibility list {#lcd_supported_list}
----------------------
diff --git a/docs/install/index.md b/docs/install/index.md
index d4ac2f13..6cefad56 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -169,7 +169,7 @@ ASUS KCMA-D8?
-------------
If you have the proprietary BIOS, you need to flash libreboot
-externally. See [kcma-d8.md](kgpe-d8.md).
+externally. See [kcma-d8.md](kcma-d8.md).
If you already have coreboot or libreboot installed, without write
protection on the flash chip, then you can do it in software (otherwise,
diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md
index e46191e7..b083aac9 100644
--- a/docs/install/rpi_setup.md
+++ b/docs/install/rpi_setup.md
@@ -150,7 +150,7 @@ successfully. If not, just flash again.
Pi](http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/)
- [Flashing coreboot on a T60 with a Raspberry Pi -
the\_unconventional's
- blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/)
+ blog](https://web.archive.org/web/20150709043222/http://blogs.fsfe.org:80/the_unconventional/2015/05/08/coreboot-t60-raspberry-pi/)
- *Pomona SOIC Clip flashing*
- [Arch Linux Wiki - Installing Arch Linux on
Chromebook](https://wiki.archlinux.org/index.php/Chromebook)