shockrah/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated limage links

Browse Source
This commit is contained in:
shockrah 2020-04-22 22:40:26 -07:00
parent 165b19b572
commit 456f1882b8
4 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
posts/atx.md
View File

@ -20,11 +20,11 @@ The main parts I had to worry about were as folow in the table:
After opening the case I saw a few things that had to go. After opening the case I saw a few things that had to go.
![](../img/atx/before.jpg) ![](../media/img/atx/before.jpg)
1. Hard Drive bays 1. Hard Drive bays
![](../img/atx/hdd.jpg) ![](../media/img/atx/hdd.jpg)
I also took off the front IO panel since I have some plans to make this more flush later on, thus saving space to fit into a carry on bag. I also took off the front IO panel since I have some plans to make this more flush later on, thus saving space to fit into a carry on bag.
@ -33,18 +33,18 @@ I also took off the front IO panel since I have some plans to make this more flu
I have no idea what this thing is but it had to go since it wouldn't let my motherboard fit into the case. I have no idea what this thing is but it had to go since it wouldn't let my motherboard fit into the case.
Luckily there was only a few rivets holding it in to a quick chiseling and they were gone with the rack too. Luckily there was only a few rivets holding it in to a quick chiseling and they were gone with the rack too.
![](../img/atx/rack.jpg) ![](../media/img/atx/rack.jpg)
## Test fitting some things ## Test fitting some things
First I checked how the motherboard would fit into the case on its own; I was afraid of possibly adjusted the rear I/O sheild hole. First I checked how the motherboard would fit into the case on its own; I was afraid of possibly adjusted the rear I/O sheild hole.
![](../img/atx/mbtest.jpg) ![](../media/img/atx/mbtest.jpg)
Next I fiddled with the psu since fitting it into the case was going to be _really_ akward. Next I fiddled with the psu since fitting it into the case was going to be _really_ akward.
It ended up being as weird as I though but ultimately it works and seems to be stable so what you see in the picture is the setup I went with. It ended up being as weird as I though but ultimately it works and seems to be stable so what you see in the picture is the setup I went with.
![](../img/atx/psutest.jpg) ![](../media/img/atx/psutest.jpg)
I completely forgot about the hard drives until the end, but it worked out in a _totally not ghetto way_. I completely forgot about the hard drives until the end, but it worked out in a _totally not ghetto way_.
The 3.5 inc drive is the only one that I _really_ need to worry about for mounting honestly because of two reaons: The 3.5 inc drive is the only one that I _really_ need to worry about for mounting honestly because of two reaons:
@ -53,7 +53,7 @@ The 3.5 inc drive is the only one that I _really_ need to worry about for mounti
* The other drive is a laptop drive \ * The other drive is a laptop drive \
Which I know still doesn't excuse the mounting but hey it coulnd't really move even if it wanted to. Which I know still doesn't excuse the mounting but hey it coulnd't really move even if it wanted to.
![](../img/atx/hddfinal.jpg) ![](../media/img/atx/hddfinal.jpg)
Hard drives have a little shroud which I made out of some heavy duty duck tape and cardboard. Hard drives have a little shroud which I made out of some heavy duty duck tape and cardboard.
Kinda sketchy but not really since it holds things in a clean position and doesnt rattle at all. Kinda sketchy but not really since it holds things in a clean position and doesnt rattle at all.

6
posts/build.md
View File

@ -30,15 +30,15 @@ post() {
} }
build_all() { build_all() {
mkdir -p $rootDir/post/ $rootDir/fonts/ $rootDir/img/ mkdir -p $rootDir/post/ $rootDir/fonts/ $rootDir/media/img/
cp style.css "$rootDir" cp style.css "$rootDir"
cp prebuild/post/style.css "$rootDir/post/" cp prebuild/post/style.css "$rootDir/post/"
cp fonts/* $rootDir/fonts/ cp fonts/* $rootDir/fonts/
cp img/ $rootDir/img/ -r cp img/ $rootDir/media/img/ -r
mv $rootDir/img/favicon.png $rootDir/ mv $rootDir/media/img/favicon.png $rootDir/
# Try to get xargs to deal with this ugliness # Try to get xargs to deal with this ugliness
for r in prebuild/*md;do for r in prebuild/*md;do

2
posts/pop-dwm.md
View File

@ -57,4 +57,4 @@ Nothing crazy right? Yeap that's it really to setup DWM with any changes you mig
In case you're wondering here's what my setup currently looks like: In case you're wondering here's what my setup currently looks like:
![Background Images I found on /wg/](/img/desktop/dwm-pop.png) ![Background Images I found on /wg/](/media/img/desktop/dwm-pop.png)

4
posts/qute.md
View File

@ -11,7 +11,7 @@ I'm was Chromium user for a while since the adblocking and extension support was
Say what you want about syncing across devices and """_the cloud_""" but its pretty comfy since everything is setup essentially where-ever you go. Say what you want about syncing across devices and """_the cloud_""" but its pretty comfy since everything is setup essentially where-ever you go.
In other words Chrome and the like get the good ole' stamp of _werks for me_. In other words Chrome and the like get the good ole' stamp of _werks for me_.
![](../img/werks.png) ![](../media/img/werks.png)
## Out of the box experience ## Out of the box experience
@ -66,7 +66,7 @@ Hopefully we get a proper ad-blocker in the future that can keep things a bit cl
There are plenty of binds but if you just read the docs then you should be fine. There are plenty of binds but if you just read the docs then you should be fine.
[Link to official binding cheat sheet](https://raw.githubusercontent.com/qutebrowser/qutebrowser/master/doc/img/cheatsheet-big.png) [Link to official binding cheat sheet](https://raw.githubusercontent.com/qutebrowser/qutebrowser/master/doc/media/img/cheatsheet-big.png)
Just like any program with tons of keyboard shortcuts, it's better to learn whatever you need and progressively learn more commands as you need them. Just like any program with tons of keyboard shortcuts, it's better to learn whatever you need and progressively learn more commands as you need them.