spawn.link

"I'm a hacker."

Wed, 24 May 2023 00:00:00 +0000

"I'm a hacker.

I create. I connect. I open.
Open doors to information.
And there's nothing wrong
with that. If you fear me,
you fear freedom. I don't
want your fear, I want your
respect. I don't want your
scorn, I want your compassion.
I don't want your resistance,
I want your invitation.
I'm a hacker. I'm free.

Are You?"

This is found on the back of a Covalent t-shirt I picked up at the NYC Linux Expo back in 2000 or 2001. After moving recently and finding this while unpacking I decided to look the text online and found nothing at all. So I’ve decided to address that.

mm f/ sec ISO " >

Fixing Citrix's "USERTrust RSA Certification Authority" error on Linux

Sun, 11 Dec 2022 00:00:00 +0000

Sometimes when using Citrix ICAClient on certain Linux distros you will get an error like

You have not chosen to trust "USERTrust RSA Certification Authority", the issuer of the server's security certificate.

You can fix this by copying a certificate you should already have on the system into a location ICAClient will see it. Why Citrix can’t look into all the normal cert paths is beyond me.

As root:

ln -s /etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem /opt/Citrix/ICAClient/keystore/cacerts/USERTrust_RSA_Certification_Authority.pem

This worked on my Linux Mint 21 system with Citrix Workspace 2212 installed via the offical deb package.

Review: IcyDock ToughArmor MB839SP-B

Tue, 01 Feb 2022 00:00:00 +0000

Back in November of 2021 IcyDock was kind enough to send me a ToughArmor MB839SP-B for review. At the time I was “upgrading” my server. I put “upgrading” in quotes because I went from a Mini ITX board with a 3rd gen Core i7 to a workstation ATX system in a SilverStone CS380 case running a 4th gen Core i7. Being the author of mergerfs I’ve experimented with a few setups and the CS380 just seemed better than my previous one. When I received the MB839SP-B I wasn’t able to immediately use it because of a number of unplanned for factors when building out the system (like needing power cable extensions.) After a couple weeks I got everything together and the MB839SP-B became a major component of this “new” build.

In a setup as complex as mine I find it useful to have a recovery install on a separate drive for when things go bad. My new board came with a MSATA slot and 128GB card which I installed Linux Mint for GUI based recovery situations but I still needed a primary OS drive. For that I used a 500GB WD SSD in the MB839SP-B. There are a few advantages to using the MB839SP-B for the main boot drive.

By having a dedicated controller for my boot drive I have minimal risk of contention with other devices that could happen when connected to the host SATA controller. This isn’t a huge issue but when my system is seriously under load it is good to minimize latency to the OS drive.
Since the drive is in a carrier it was very convenient when needing to test the recovery drive without going into the BIOS and for situations where the system might need to be manipulated off host. In this particular case I had to move from MBR to GPT and that required moving the drive back and forth to the original setup in order to rework partitions. That would have been a bigger pain without the carrier.
Helps free up a SATA port on the onboard controller allowing me to increase the storage density of my server.

When you get down to it there really isn’t much to the MB839SP-B but it works well and really comes in handy if your storage ever needs quick removal. I’ve not run into any issues. Performance is good. No complaints. The bare circuitry on the back of the device is not ideal if you have thicker cards near it but worse case some kapton tape would help keep from any shorting.

I want to thank Vincent from IcyDock for his support and help and IcyDock in general for their quality products. I look forward to seeing what IcyDock does next. I’d really love to see some inexpensive, basic electrical passthrough removable cages with carriers. No activity LEDs, no power regulation, nothing active. Something that helps increase the density of storage for us data hoarders on the cheap. Metal is nice but… decent plastic is fine :)

'Fixing' Suspended Bluetooth Audio Starting Quiet in Linux

Wed, 29 Dec 2021 00:00:00 +0000

During a sale I bought an Anker Soundcore Motion+. The idea was to use it as a computer speaker. I wasn’t sure when I ordered it if I would use it via Bluetooth or AUX. Once it arrived I found that when plugged in to charge the speaker had horrible noise when AUX was used. If you disconnected the USB cable it had a very low hiss but that nothing out of the ordinary. I tried a better shielded audio cable but it still occurred. After a bunch of testing I found that if I used a high quality Thunderbolt 3 (USB-C) cable and plugged it into the Dell D6000 USB dock I have (for extra monitors) then the noise was low enough to be usable. Why didn’t I use Bluetooth? I found that after 30’ish seconds the audio would not be generated for a second or so. Not a delay but as if the volume was low. I suspected it was going into a low power mode and it was extremely annoying. Especially given the audio was much clearer compared to the powered AUX mode. But it was “good enough” so I left it. However, after changing machines the hiss got worse so I’ve revisited the problem.

Turns out I was right. The speaker was being put to sleep and the low volume was it being woken back up and that took a second or two. It appears this can be managed on Linux (when using PulseAudio) by disabling the suspend on idle module. After doing so I have no delays when playing audio after a while of silence. Perhaps there is a more elegant way to do this (like per device disabling)?

To disable across the board:

Open “/etc/pulse/default.pa”
Comment out “load-module module-suspend-on-idle”
sudo pkill pulseaudio

I imagine there is some way to do similar on Windows but I’m not sure how to do so.

MacroSilicon HDMI Capture Device (534D:2109) [v3]

Tue, 15 Sep 2020 00:00:00 +0000

Yet another MacroSilicon based capture device. Ordered this after my original one died.

Appears to be the same chipset just in a new form factor.

This form factor is much nicer as it doesn’t take as much room at the plug so you don’t need to take up as much space or get an extension. The device also seems to run cooler though it doesn’t appear to be using the aluminum shell as a heatsink. The device in general is much smaller though due to the built in wire isn’t quite as convenient to carry around.

[680228.596753] usb 1-3: new high-speed USB device number 16 using xhci_hcd
[680228.748123] usb 1-3: New USB device found, idVendor=534d, idProduct=2109, bcdDevice=21.00
[680228.748128] usb 1-3: New USB device strings: Mfr=1, Product=0, SerialNumber=0
[680228.748132] usb 1-3: Manufacturer: MACROSILICON
[680228.749768] uvcvideo: Found UVC 1.00 device <unnamed> (534d:2109)
[680228.750899] uvcvideo 1-3:1.0: Entity type for entity Processing 2 was not initialized!
[680228.750903] uvcvideo 1-3:1.0: Entity type for entity Camera 1 was not initialized!
[680228.753449] hid-generic 0003:534D:2109.0009: hiddev0,hidraw0: USB HID v1.10 Device [MACROSILICON] on usb-0000:00:14.0-3/input4

Doesn’t appear I can easily take the PCB out of the case without damage so no images of the board.

MacroSilicon HDMI Capture Device (534D:2109) [v2]

Fri, 04 Sep 2020 00:00:00 +0000

Version 2 of a widely sold and inexpensive USB2 HDMI capture device.

Differences:

“Coffee” colored metal casing
small heatsink on the MacroSilicon chip
PCB layout updated (additional power safety?)

They are otherwise the same. Use the same chipset.

As reported by Linux (5.4.0-40-generic on Ubuntu 20.04):

Manufacturer: MACROSILICON
idVendor=534d
idProduct=2109
bcdDevice=21.00
Mfr=1, Product=0, SerialNumber=0

The uvcvideo and hid-generic drivers output the following:

[2155922.389360] uvcvideo: Found UVC 1.00 device USB Video (534d:2109)
[2155922.390038] uvcvideo 1-3:1.0: Entity type for entity Processing 2 was not initialized!
[2155922.390039] uvcvideo 1-3:1.0: Entity type for entity Camera 1 was not initialized!
[2155922.392032] hid-generic 0003:534D:2109.0013: hiddev1,hidraw3: USB
HID v1.10 Device [MACROSILICON USB Video] on usb-0000:00:14.0-3/input4

As with the original it works well with OBS 25.0.8 on Ubuntu 20.04. Using an ALSA audio device seems to be best with regard to video / audio sync. Need to use “YU12” as the “Video format” to get 60fps.

eEver UVC UAC HDMI Capture Device (1E4E:7001D)

Mon, 06 Jul 2020 00:00:00 +0000

In April 2020 I ordered a capture device that some had said was a reasonably priced 1080p60 USB3 capture device. It showed up July 5th. Since there appears to be a lack of information on the device online I’ll document what I find here for others.

As reported by Linux:

Product: eEver USB Device
Manufacturer: eEver
SerialNumber: 20000130041415
idVendor=1e4e
idProduct=701d
bcdDevice= 1.00
Mfr=6, Product=7, SerialNumber=3

The device, while being advertised as being USB3; having a blue USB port; and using a USB3 A to A cable, it is NOT seen as a USB3 device. According to Linux it registers as a high-speed device (aka USB2).

The usb and uvcvideo drivers outputs the following (5.4.0-40-generic on Ubuntu 20.04):

[241601.870573] usb 1-5: new high-speed USB device number 31 using xhci_hcd
[241602.031812] usb 1-5: New USB device found, idVendor=1e4e, idProduct=701d, bcdDevice= 1.00
[241602.031814] usb 1-5: New USB device strings: Mfr=6, Product=7, SerialNumber=3
[241602.031815] usb 1-5: Product: eEver USB Device [241602.031815] usb 1-5: Manufacturer: eEver
[241602.031816] usb 1-5: SerialNumber: 20000130041415
[241602.032468] uvcvideo: Found UVC 1.00 device eEver USB Device (1e4e:701d)
[241602.040993] uvcvideo: UVC non compliance -- GET_DEF(PROBE) not supported. Enabling workaround.
[241602.041361] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
[241602.041362] uvcvideo 1-5:1.0: Entity type for entity Processing 3 was not initialized!
[241602.041363] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!

While using OBS 25.0.8 I find the performance a bit unstable. Perhaps it’s due to attempting to push 1080p60 over USB2. Using a PulseAudio input resulted in a significant audio sync issues but the ALSA input was much better.

MacroSilicon HDMI Capture Device (534D:2109)

Mon, 06 Jul 2020 00:00:00 +0000

UPDATE2: Was sent a replacement device which is updated slightly from the original.

UPDATE1: My device died. I left it plugged in and OBS active overnight and it was dead in the morning. Got very hot. Possibly overheated and fried itself. It no longer registers at all.

A widely sold and inexpensive USB2 HDMI capture device.

As reported by Linux (5.4.0-40-generic on Ubuntu 20.04):

Manufacturer: MACROSILICON
idVendor=534d
idProduct=2109
bcdDevice=21.00
Mfr=1, Product=0, SerialNumber=0

The uvcvideo and hid-generic drivers output the following:

[68854.902315] uvcvideo: Found UVC 1.00 device <unnamed> (534d:2109)
[68854.903137] uvcvideo 1-1:1.0: Entity type for entity Processing 2 was not initialized!
[68854.903138] uvcvideo 1-1:1.0: Entity type for entity Camera 1 was not initialized!
[68854.905043] hid-generic 0003:534D:2109.0016: hiddev1,hidraw3: USB HID v1.10 Device [MACROSILICON] on usb-0000:00:14.0-1/input4

Works well with OBS 25.0.8 on Ubuntu 20.04. Using an ALSA audio device seems to be best with regard to video / audio sync. Need to use “YU12” as the “Video format” to get 60fps.

Is This A Thing? Explicitly Colliding Hashes?

Fri, 06 Dec 2019 00:00:00 +0000

tl;dr

Is there a way, besides brute force calculation, to solve the following where you know the function inputs, don’t know the function, and don’t care about the output besides needing certain inputs to have the same output and preferably to be within a certain range? Similar to a perfect hash but perfect in regard to the relation between input and output rather than no collisions in the output.

f(a0) = x
f(a1) = x
f(a2) = x
f(b0) = y
f(b1) = y
...

The Situation

I’m working on an emulator. An important consideration in an interpreter is the instruction dispatch performance. It can need to happen millions of times a second so any cost savings possible can have large impacts.

In modern CPU design you have a lot of performance uncertainty. Are the segments of hot code going to fit into the L1 cache? Will the hot data sets? How’s that branch prediction going? Etc. When building an emulator these can have significant impacts.

On an ARM60 there are about 100 instructions. Well… if we consider different styles of operands. For example: most of the arithmetic opcodes (ADD,CMP,etc.) have 3 different shift operand styles. To differentiate between those ~100 instructions there are 13 bits in total used across the 32bit instruction. The number of relevant bits differs per instruction as does their location.

Now… granted… branch prediction would be a possible problem here but what if you could find a function which given those masked 13bits would spit out a number in the range [0,100) which could be used as an index into a jump table or switch statement. Or maybe fewer and force the specific instruction interpretation do a bit more work?

You can use a lookup table to simplify this but that expands the hot data set which can impact performance. If you do a more traditional bit inspection you’re increasing the amount of conditional code and branch prediction failures.

The really unfortunate thing is that you probably can’t predict the impact in practice of any one of these things. I’m considering trying a number of strategies to compare but having this hash method would be neat to have to compare against and I don’t think I’ve seen such a thing attempted (probably due to the cost of finding f).

I wrote a simple app to brute force the problem but no luck. I found the occasional function which would give the same output but only for small numbers of instruction masks and not across more than one instruction type. The pseudo code would be something like

foreach setOfMaskedInstructions
  foreach hashFunction
    if setOfMaskedInstructions hash to same value: 
      continue
    else: 
      exit program

3DO MacOS9 Development Environment

Tue, 05 Nov 2019 00:00:00 +0000

UPDATE: See https://3dodev.com/software/sdks

To help facilitate 3DO homebrew development I’ve been working to provide better access to 3DO build environments, tooling, and information. This first release is a QEMU PPC system based MacOS9 environment with the 3DO SDK installed along with other relevant tools. This package includes example start scripts for QEMU and 3 images (a base image, a snapshot to keep the base clean, and a scratch pad drive image) and you should be ready to go immediate after booting.

Image: 3DO_MacOS9_dev_image_1.0.0.zip

QEMU (tested on 4.1.0):

Windows
MacOS
Linux: your OS’s package manager or build yourself

In the future I’m looking to package Windows command line build tools in a more friendly way as well as packing those tools for use on Linux via WINE. I’ll also be releasing, in the least, a tutorial on creating 3DO compatible FMVs.

If you’d like to help in any way (documentation, examples, tutorials, port / create build tools, etc.) or have any suggestions on improving things please contact me. Also please contact me if you have any technical details regarding the 3DO. Including any development documentation not included in the 3DO Toolkit or Portfolio docs.

Using a Lenovo X1 Tablet Keyboard as a Wired Keyboard

Mon, 18 Feb 2019 00:00:00 +0000

Turns out the pogo pins on the X1 Tablet keyboards (gen 1,2 & 3) are just USB. 6 pins. 2 NC (not connected) and 4 standard USB [red (+5v), white (data+), green (data-), black (gnd)].

Thanks to cc9cii over on the /r/thinkpad subreddit we now have the pinout for the Gen1, Gen2, and Gen3 keyboards. The Gen1 and 2 are the same with 2 staggered rows of 3 pins and the Gen3 is 1 row of 6.

While the keyboard is facing you the pinouts are as follows:

Gen1 & Gen2:

top row: white (data+), red (+5v), NC
bottom row: black (gnd), green (data-), NC

ThinkPad X1 Tablet Gen 3 Thin Keyboard (01HX850 / Model TP00089K1):

NC, red (+5v), green (data-), white (data+), NC, black (gnd)

Ideally a magnetic pogo pin connector could be used to connect to the keyboard in the same way the tablet does but I’ve yet to find one that’d work. Another solution would be to build a 3D printed clamp. I was impatient and ended up cutting off the end of an old USB cable and soldering to the pogo pins. At some point I plan to purchase a female USB C or Mini B port and replacing the cable.

Update: Ended up buying a usb micro breakout board from AliExpress and epoxied that onto the edge and wired that up instead.

CAVEATS:

The Gen1 & Gen2 keyboards apparently requires drivers for the trackpad.
Gen3 trackpoint and buttons don’t currently work on Linux
Not all function keys will work on a typical system.

bbf: A Harddrive Bad Blcok Scan and Repair Tool

Mon, 13 Aug 2018 00:00:00 +0000

I wrote this tool a while back and posted it up on github but never advertised it. I’m a bit of a data hoarder and as a result have had to deal with dying harddrives many a times. I never found dd or badblocks to be as useful as I’d like and certainly not safe enough. On more than one occasion I’ve fat fingered the overwriting of a good drive after the OS decided to change the device name of a drive I was working on. As a result I cracked open the ATA specs and wrote a much safer, more featureful tool for scanning hard drives and attempting the reallocation of blocks.

Quick rundown of features:

readonly scanning of bad blocks
safe ‘fix’ mode which won’t overwrite good blocks
burnin mode for checking new drives
manual marking blocks as corrupted
find files given list of blocks
dump list of files and associated block ranges
dump list of blocks used by a file

Technically this tool should work on SSDs as well but I’m not sure they react the same way to error conditions.

Find out more over at github: https://github.com/trapexit/bbf

3DO Arcade - SAOT BIOS

Tue, 12 Jun 2018 00:00:00 +0000

After recently involving myself in the 3DO emulator 4DO I started looking over miscellaneous 3DO forums. Over at the Arcade-Museum.com forum I came across a post by willkaotix of klov who had the 3DO based arcade game Shootout At Old Tucson and had desoldered the ROM with an interest to get it dumped. This was back on 2015-10-18. Having not seen a conclusion to the thread nor the ROM floating in the wild I reached out to willkaotix.

willkaotix got back to me and having realized he had the ability to dump the ROM himself he did so… and here it is: 3do_arcade_saot_rom.zip

filename: 3do_arcade_saot.bin
size: 524288
crc32: b832da9a
md5: 8970fc987ab89a7f64da9f8a8c4333ff
sha1: 520d3d1b5897800af47f92efd2444a26b7a7dead

I’ve added support for the ROM in LibRetro’s 4DO core. This enables the loading, ~~but currently not the playing~~ (see below), of the publicly available dumped 3DO arcade games: Shootout At Old Tucson and Orbatak. The reason these games are not currently playable is due to these arcade games using custom controllers but there is an effort to reverse engineer them. It was/is possible to use the patched FZ-10 BIOS as well to boot these but for completeness it is nice to have this dumped finally.

Things of note: the BIOS is half the size of retail units. It has no attract mode. Retail games will not boot when using it.

Enjoy! And thank you willkaotix.

~~P.S. If you know anything about the 3DO arcade controller board protocol (or that of the lightgun, flightstick, or other nonstandard peripherals) please contact me.~~

UPDATE (2018-06-18): I’ve pushed an update to 4DO to enable support for the 3DO mouse an initial support for lightguns. While I may need to create separate lightgun devices in the future to distinguish between retail and arcade… it looks like at least SAOT used an extended version of the retail lightgun protocol. While you can’t use the mouse to control where you’ll shoot you can use the different buttons to add coins, shoot, or enter the service menu.

UPDATE (2018-06-28): Lightgun/Gamegun support is available now for both retail and ALG games (though ALG games come up as 2nd player). Tested Mad Dog 2 and that worked as well. Next is to investigate Orbatak’s input.

UPDATE (2018-07-04): Orbatak’s input now supported. The trackball and buttons replicated via an analog joypad.

3DO Emulation

Sat, 07 Apr 2018 00:00:00 +0000

I recently decided to take on the task of cleaning up the 3DO emulator 4DO which is based on FreeDO. Specifically the libretro core version.

I reached out to the project lead on 4DO and he’s supportive of my efforts to rework and improve 4DO via the libretro port (rather than fork or adopt the Windows only 4DO codebase).

So far I’ve fixed a significant issue with rendering (appeared like a vsync problem), ported over specific game hacks, improved joypad handling, added CHD support, and I’m now in the process of doing a major cleanup of the code and APIs. Once that’s finished I’ll be focusing on improving performance and expanding features.

I’ve also put together a github repo to store any and all 3DO information. If you have any information regarding the 3DO console please consider sending it my way or issuing a pull request to the repo.

scorch: silent corruption checker

Tue, 15 Nov 2016 00:00:00 +0000

A new tool designed to provide a workflow around hashing files and then checking them later in order to find corruption. Combined with external backup solutions (such as CrashPlan or Amazon Cloud) this tool lets you forgo heavier tools like SnapRaid which require dedicated drives. This doesn’t provide recovery of data. Only corruption detection.

https://github.com/trapexit/scorch

WTF?! Kubernetes' rbd_util.go

Fri, 02 Sep 2016 00:00:00 +0000

https://github.com/kubernetes/kubernetes/blob/release-1.4/pkg/volume/rbd/rbd_util.go#L57

po := path.Join(sys_path, name, "pool")
img := path.Join(sys_path, name, "name")
exe := exec.New()
out, err := exe.Command("cat", po, img).CombinedOutput()

Does Kubernetes not have code review? Fork/exec’ing cat to read content from files? This is embarrassing bad.

ChromeOS & OpenVPN: Using OVPN Files to Setup OpenVPN on ChromeOS

Mon, 22 Aug 2016 00:00:00 +0000

First you need to split the “ovpn” file into the CA cert, client cert, and client key. If you’re using Crouton with ChromeOS you can do this on the ChromeOS device. Otherwise you’ll need to do this on another machine. The below is from an Ubuntu desktop.

I’ve also created a small script to do the same: split-ovpn

$ ls
client.ovpn
$ awk ‘//{flag=1;next}/</ca>/{flag=0}flag’ client.ovpn > ca.crt
$ awk ‘//{flag=1;next}/</cert>/{flag=0}flag’ client.ovpn > client.crt
$ awk ‘//{flag=1;next}/</key>/{flag=0}flag’ client.ovpn > client.key
$ openssl pkcs12 -export -in client.crt -inkey client.key -out client.p12
Copy the files to your ChromeOS device via SD Card, USB stick, email, Google Drive, etc.
Goto ChromeOS’s Settings menu
In the Search bar next to “About Chrome OS” type “certificates” and wait for the “HTTPS/SSL > Manage certificates…” button to appear and click it
Select the “Authorities” tab and click “Import…”
Find and select the file “ca.crt”
Select the “Your Certificates” tab and click “Import and Bind to Device…”
Find and select the file “client.p12”
Click “Done”
Click “X” on the Search to bring you back to the main Settings
Click on “Add connection” under “Internet connection”
Select “OpenVPN / L2TP”
Change “Provider Type” to “OpenVPN”
Change “Server CA certificate” to that which you just added
Change “User certificate” to that which you just added
Fill in “Server hostname” with the value found in the original “ovpn” file with the line starting with “remote”. The line will look something like “remote my.hostname.com 1194”. The “Server hostname” would be in this case “my.hostname.com:1194”.
Pick a “Server name”. Can be anything you like.
Enter your client’s “Username” and “Password” if needed.

Backup, Recovery, & Maintenance Howtos

Wed, 03 Feb 2016 00:00:00 +0000

https://github.com/trapexit/backup-and-recovery-howtos

There is a lot of information scattered throughout the internet about creating backups of files, filesystems, hard drives, solid state drives, etc. However, there is really no one place where the different methods and technologies are described, compared, and packaged as full stack solutions. Recovery is almost a black art. Random tools you find talked about on miscellaneous forums.

Rather than using a wiki which can get messy I’ve created a git repo of Markdown files which try to walk through different backup solutions, end to end. From describing what they are to how to recover and maintain them.

I’ve started with a document on using mergerfs, snapraid, and CrashPlan given that’s my setup. Should be noted that I’m the author of mergerfs.

Pull requests are very, very welcome. All any any tech, platforms, setups are welcome.

Resetting Your Wii to (Almost) Factory State

Tue, 15 Jul 2014 00:00:00 +0000

Resetting / revirginizing your Wii to (almost) factory state

WARNING: This will completely erase everything on your system.
You’ll need giantpune’s wiiqt tools. It appears they’ve been abandoned for some time so I’ve cloned the code to https://github.com/trapexit/wiiqt just in case.
For Windows: ohneschwanzenegger, nandExtract, nandBinCheck, giantpune-tools-dlls. On other platforms they’ll need to be built locally.
Use BootMii [hackmii_installer_v1.2] to acquire an up to date version of your Wii’s nand.bin. We want to make sure that the bad block list is up to date.
Using ohneschwanzenegger:
1. Nand Dump > New nand…
2. Click “Existing Nand…”
3. Leave “Keys”, “Boot 1 & 2”, and “uid.sys” alone. (Set to “From old nand”)
4. Click “OK”
5. You should see: Set path to nand as PATH
  Created /shared2/test/testlog.txt
6. Content > Format
  You are about to format PATH
  This cannot be undone. Are you sure you want to do it?
  Click “Yes” Formatting nand…
  Created /shared2/test/testlog.txt
  Done!
7. Set the “Local Cache” directory to some temporary directory. ("/tmp", “c:\temp”, etc.)
8. In the top text entry line enter “4.3U” or whichever OS version you wish to install.
9. Click “Get It!”
10. You’ll see lots of “Received a completed download from NUS” and matching* “Installed title XXXXXXXXXXXXXX vXXXXX to nand”* and finally “NUS object is done working”
11. You’ll be presented with the same dialog box as when selecting Content > Setting.txt
  Probably should change the “Code” and “SerNo” to what’s on the bottom of your Wii.
  Click “OK”
12. Content > Write meta entries
13. Content > Flush
14. Exit ohneschwanzenegger
Place the nand.bin file you created with ohneschwanzenegger on the SD card’s root directory. (Overwriting the previously dumped file.)
Boot the Wii into BootMii using the SD card and restore the nand
If you expect to restore the nand in the future you may want to setup the Wii and then dump again.

Introducing mergerfs: another fuse union filesystem

Tue, 20 May 2014 00:00:00 +0000

https://github.com/trapexit/mergerfs

https://github.com/trapexit/mergerfs/blob/master/README.md

hello_world

Thu, 17 Apr 2014 00:00:00 +0000

http://github.com/trapexit