The popular open-source contract for web professionals by Stuff & Nonsense
- Originally published: 23rd December 2008
- Revised date: March 15th 2016
- Original post
(updated versions of this document, plus more, live here)
This will show you how to get Guix running on WSL2.
We're going to go as "minimal" as possible, without starting off one of the readily available WSL2 distros.
Parts of this guide should help with understanding how to set up any custom distro on WSL, not just Guix.
Disclaimer: I'm a Guix nOOb! (hence going through the trouble of installing it on WSL2)
| /* | |
| EXAMPLE - Teensy Simple WAV Player with Teensy Audio Audio Shield | |
| Library : https://github.com/RyoKosaka/HelloDrum-arduino-Library | |
| Blog : https://open-e-drums.tumblr.com/ | |
| */ | |
| /* NOTICE | |
| This code is unstable! |
Being new to training ML models using Google Cloud VM instances, I faced issues where my ssh connection to the cloud instance (using either the clound web-based ssh client or using cloud shell) would disconnect from time to time (for example when I power off my laptop or the network gets disconnected) which would terminate the model training process. Therefore I searched for a ssh client that can handle disconnection and can resume connection without disrupting the process running on the server and came across with Mosh mobile shell, a remote terminal app that supports roaming.
It took me a while to figure out how to set up a third party ssh terminal using the google cloud OAuth. Here's a step-by-step guide:
Since this writing, another Mosh user kindly advised me that using terminal multiplexer co
| #!/usr/bin/env python | |
| from sys import argv | |
| from itertools import izip | |
| from cogent.parse.fastq import MinimalFastqParser | |
| """ Usage | |
| python merge_bcs_reads.py X Y Z | |
| X: barcodes fastq file |
Revised date: 07/11/2012
Between us [company name] and you [customer name]
We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.
Put this in the file /etc/systemd/system/irssiscreen@.service
[Unit]
Description=irssiscreen
After=network.target