web/lukegbcom: add all the rest of the posts
This commit is contained in:
parent
762a5a7271
commit
43e5ecf0db
6 changed files with 98 additions and 3 deletions
|
@ -71,4 +71,4 @@ export async function getSortedPostsData() {
|
|||
delete x.sortKey
|
||||
return x
|
||||
})
|
||||
}
|
||||
}
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Setting the Scene
|
||||
date: 2016-01-25T16:44:00
|
||||
date: 2016-01-25T16:44:00Z
|
||||
layout: Post
|
||||
hero: https://source.unsplash.com/7P_2hzKryQE/1270x952
|
||||
hero credit: https://unsplash.com/photos/7P_2hzKryQE
|
||||
|
|
34
web/lukegbcom/posts/2016-02-09-fixing-my-desktop-again.md
Normal file
34
web/lukegbcom/posts/2016-02-09-fixing-my-desktop-again.md
Normal file
|
@ -0,0 +1,34 @@
|
|||
---
|
||||
title: Fixing my Desktop (again)
|
||||
date: 2016-02-09
|
||||
layout: Post
|
||||
hero: https://source.unsplash.com/Kw_zQBAChws/1270x952
|
||||
hero credit: https://unsplash.com/photos/Kw_zQBAChws
|
||||
hero credit text: Ashim D'Silva
|
||||
classes:
|
||||
header: header-black-gradient
|
||||
tags:
|
||||
- linux
|
||||
---
|
||||
I successfully broke my computer again. Oops. I can watch systemd boot my system
|
||||
and then once my display manager (in my case, sddm) takes over, kaput.
|
||||
---
|
||||
|
||||
Once that's happened, I can't do anything else. I can't switch to a text console
|
||||
because my displays switch themselves off, nor can I start a graphical session
|
||||
because, again, my displays switch themselves off.
|
||||
|
||||
Rebooting yields this:
|
||||
|
||||
![Will this ever reboot?](/assets/2016-02-09-linux-on-the-desktop.9b0ec6532b5e.jpg)
|
||||
|
||||
(and clicking the reboot button does nothing)
|
||||
|
||||
I managed to fix this by booting into EFI shell, then specifying runlevel 3 by booting
|
||||
the kernel's [EFISTUB](https://wiki.archlinux.org/index.php/EFISTUB). My EFI shell didn't
|
||||
like the leading slash for some reason. Whatever.
|
||||
|
||||
Once that was done, a `pacman -Syu` (which updated the `nvidia` package, among some other things)
|
||||
and a `mkinitcpio -P linux` got me back up and running.
|
||||
|
||||
Simples!
|
36
web/lukegbcom/posts/2016-02-15-ard-installers.md
Normal file
36
web/lukegbcom/posts/2016-02-15-ard-installers.md
Normal file
|
@ -0,0 +1,36 @@
|
|||
---
|
||||
title: 'Apple Remote Desktop: Creating Installers'
|
||||
hero: https://source.unsplash.com/_NGCma7mAw4/1270x952
|
||||
hero credit: https://unsplash.com/photos/_NGCma7mAw4
|
||||
hero credit text: reza shayestehpour
|
||||
|
||||
hero-align: center 65%
|
||||
classes:
|
||||
header: header-no-gradient
|
||||
# hero credit: https://www.flickr.com/photos/pslee999/15589950511/
|
||||
date: 2016-01-25
|
||||
layout: Post
|
||||
tags:
|
||||
- university tech
|
||||
---
|
||||
|
||||
As a followup to my previous post, I was trying to create an Apple Remote Desktop installer. This is usually something that's fairly trivial:
|
||||
|
||||
---
|
||||
|
||||
1. Open Apple Remote Desktop
|
||||
2. Open `File` > `Create Client Installer...`
|
||||
3. Answer wizard questions
|
||||
4. Profit!
|
||||
|
||||
However, on trying this on my 10.11 Server install, I was instead presented with this:
|
||||
|
||||
![Apple Remote Desktop error](/assets/2016-01-25-ard-error.6f44efe96257.png)
|
||||
|
||||
In theory, ARD is supposed to automatically download components (like the client) which it doesn't have, and I actually managed to coax my local install of ARD, which had previously been giving the same error message, to do so.
|
||||
|
||||
In any event, if this happens, you can actually cheat and grab the client yourself from Apple's servers:
|
||||
|
||||
[http://swcdn.apple.com/content/downloads/59/10/031-23124/x0sj4t1vbimv6h3ejhjzf3nwa6vt9ekxgd/RemoteDesktopClientShell.pkg](http://swcdn.apple.com/content/downloads/59/10/031-23124/x0sj4t1vbimv6h3ejhjzf3nwa6vt9ekxgd/RemoteDesktopClientShell.pkg)
|
||||
|
||||
Not really sure if this is a good idea or not, but it fixed the problem for me!
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Secure Boot Shenanigans
|
||||
date: 2016-11-11
|
||||
date: 2016-11-11T16:30:00Z
|
||||
layout: Post
|
||||
tags:
|
||||
- linux
|
||||
|
|
25
web/lukegbcom/posts/2017-02-17-yubikey-neo-gnupg.md
Normal file
25
web/lukegbcom/posts/2017-02-17-yubikey-neo-gnupg.md
Normal file
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
title: YubiKey Neo GnuPG on Linux
|
||||
date: 2017-02-17
|
||||
layout: Post
|
||||
hero: https://www.yubico.com/wp-content/uploads/2013/02/YubiKey-NEO-+-finger.jpg
|
||||
hero credit: https://www.yubico.com/press/images/
|
||||
hero credit text: Yubico
|
||||
classes:
|
||||
header: header-black-gradient
|
||||
tags:
|
||||
- u2f
|
||||
- linux
|
||||
---
|
||||
|
||||
Just a quick note to remind myself, when I inevitably forget.
|
||||
|
||||
The built-in GnuPG smartcard support doesn't really work particularly well, in my experience, with the YubiKey Neo. To fix this (and use pcscd) instead, put the following in `~/.gnupg/scdaemon.conf`:
|
||||
|
||||
---
|
||||
|
||||
```txt
|
||||
pcsc-driver /usr/lib/libpcsclite.so
|
||||
card-timeout 5
|
||||
disable-ccid
|
||||
```
|
Loading…
Reference in a new issue