OpenLLM-France/wikimedia huggingface dataset:
# Muggles' Guide to Harry Potter/Magic/Witch Weekly
## Overview

Witch Weekly is a weekly newspaper / magazine similar to the Muggle publication Women's Weekly. It seems to be aimed at middle-aged Wizarding housewives, and is generally full of stories about celebrities (including Harry on occasion) and handy household tips.

## Extended Description

When Rita Skeeter writes a story that implies that Hermione is leading both Harry and Viktor Krum on romantically, shortly after the Second Task in Harry Potter and the Goblet of Fire, she is able to get it published in Witch Weekly. As a direct result of this, Hermione gets great quantities of hate mail, one of which is filled with Bubotuber pus. Because of this, she has to miss several classes.
It turns out that Mrs. Weasley also reads Witch Weekly, and because of that story, she rather goes off Hermione; Hermione is dismayed at Easter that year, when the Easter egg that Mrs. Weasley sends Harry is about the size of an ostrich egg, and Hermione's is the size of a chicken's egg. This misunderstanding is not cleared up until the Weasleys come to cheer Harry on in the Third Task, and Harry tells Mrs. Weasley that Hermione was never his girlfriend.
Witch Weekly also gives out a periodic (probably annual) "Most Charming Smile Award," which Gilderoy Lockhart is inordinately proud of having won five times.

## Analysis

One thing that has been commented on elsewhere is the realism, the fullness of the vision of the Wizarding world. It is easy to believe, at least while the books are open in front of us, that the Wizarding world that Rowling describes could exist. A large part of that seems to be how completely the author has portrayed, not just the magical aspects of that world, but how the world's inhabitants get along from day to day. Witch Weekly is a tiny, but intriguing part of that. If this sort of publication can exist in the Muggle world, its absence from the Wizarding world would be a small irritant: what would Molly read in the market line-up? Additionally, gossipy pieces, like the discussion of Hermione, Harry, and Viktor, are clearly not news, and so would have to go into some sort of magazine. Failing to include Witch Weekly, or something very like it, would prevent that plot point appearing.

## Questions

Study questions are meant to be left for each student to answer; please don't answer them here.

## Greater Picture

In Harry Potter and the Order of the Phoenix, Rita Skeeter tells Hermione quite plainly that the object of a newspaper is to make money. Given that, a market of the type served by Witch Weekly would never be overlooked – all those housewives with a few spare Knuts at the store counter! Just as in the Muggle world, if there are Galleons to be made by selling writings slanted towards one audience, something will come along to make those Galleons. It is to the author's credit that the result is so very believable.
# Muggles' Guide to Harry Potter/Magic/Yeti
## Overview

The yeti, commonly known as Bigfoot or the Abominable Snowman, is a troll-like carnivore completely covered in pure white hair. Native to Tibet, yetis fear fire.

## Extended Description

In Harry Potter and the Chamber of Secrets, Year with the Yeti is one of the several supposed autobiographies of Gilderoy Lockhart that are assigned to Harry's Defence Against the Dark Arts class. Harry is selected by Lockhart to play a "yeti with a head-cold" in a dramatisation of one such story.

## Analysis

Whilst being largely regarded as a myth by the scientific community, the yeti remains a common feature of fiction and one of the most famous creatures of cryptozoology. True to this, it is mentioned in Fantastic Beasts and Where to Find Them that an International Task Force is based in the Himalayan mountains so as to prevent reporting of Muggle sightings of the yeti, which are apparently numerous.

## Questions

Study questions are meant to be left for each student to answer; please don't answer them here.
# Muggles' Guide to Harry Potter/Magic/Wingardium Leviosa
## Overview

Wingardium Leviosa is a common spell used to levitate objects.

## Extended Description

This is the first charm taught to Harry's first year class; it is a relatively simple charm, but only Hermione is able to perform it correctly at first.
It is explicitly mentioned at three other places in the series.
Firstly, during the same evening it is introduced, Ron uses it to levitate a club above the head of an attacking mountain troll; when he releases the spell, the falling club knocks out the troll.
Secondly, in Harry Potter and the Deathly Hallows, Harry uses it on a sidecar which has fallen off a flying motorcycle. In fact, Harry is actually in the sidecar when he uses Wingardium Leviosa on it; while it seems that the ability to fly unaided is exceptional among wizards, the ability to charm objects on which you are mounted is relatively simple.
Thirdly, in chapter 32 of the same book, Ron uses the spell on a fallen-off twig of the Whomping Willow to touch the knot on the tree's trunk that will stop its branches from violently attacking anyone near the tree. The Trio then enters the tunnel that leads from the Willow to the Shrieking Shack.
Wingardium Leviosa is also mentioned implicitly in the chapter about Harry's O.W.L. exams in Harry Potter and the Order of the Phoenix, where it is the answer to the first question Harry reads in his theoretical Charms exam. Harry instantly remembers the defeating of the mountain troll in his first Hogwarts year mentioned above, and therefore the answer comes easily to him, which greatly reduces his initial nervousness.

## Questions

Study questions are meant to be left for each student to answer; please don't answer them here.
# Muggles' Guide to Harry Potter/Magic/Wit-Sharpening Potion
## Overview

Wit-Sharpening Potion was seen being made in Potions Class in Harry Potter and the Goblet of Fire, in the first Potions class after the Second Task.

## Extended Description

While the effects of this potion are never described, it can be assumed from the name that it is intended to increase perceptiveness or "wit". We do learn that the principal ingredients are powdered scarabs, ginger root, and armadillo bile, but unlike some other potions, we do not hear this one's finished state described.
The overall purpose of this potion in the narrative seems to be marking a change in concentration in the Potions class. In the earlier part of the year, up until Christmas, Potions had been centered on antidotes. Harry had found this topic particularly unnerving, as he expected Snape to poison him as part of the term-end test, to see how well Harry had made his antidotes. While the Second Task occurs nearly two months later, on 24 February, and this class occurs after that, we do not see any Potions classes during the intervening months; this is the first Potions class we have attended with Harry since Christmas.

## Questions

Study questions are meant to be left for each student to answer; please don't answer them here.
# QEMU/Devices/Virtio

VirtIO is a platform for IO virtualization, common to several hypervisors (and QEMU).
The guest operating system needs specialized drivers to handle these devices.

## Supported devices list

| Function | Bus | Type | Device | Usage example |
| Networking | PCI | 10Gb/s | virtio-net-pci | -net nic,model=virtio ... |
| Storage | PCI | SCSI | virtio-scsi-pci | -device virtio-scsi-pci -drive file=disk.img,if=none,id=hd0 -device scsi-hd,drive=hd0 ... |
| Storage | PCI | Custom | virtio-blk | -drive file=disk.img,if=virtio ... |
| Memory | PCI | RAM | virtio-balloon-pci |
| Serial | PCI | Serial | virtio-serial-pci |
| Random Number Generator | PCI | RNG | virtio-rng-pci | → virtio-rng-pci |

## virtio-rng-pci
### Entropy sources

To set up a VirtIO RNG, you first need to provide a source of entropy for it.
For devices exported by the kernel on UNIX-like systems, you can do so like this: -object rng-random,filename=/dev/random,id=rng0
It is obviously not limited to the kernel RNG, you can choose a hardware RNG too in the very same way.
It also supports EGD, though it is not recommended because of its poor performance. Example: -chardev socket,host=10.199.13.151,port=9000,id=chr0 -object rng-egd,chardev=chr0,id=rng0

### Adding the actual device

Then you can add the actual device, like this: -device virtio-rng-pci,rng=rng0
There's also an option to limit the amount of data the guest received, to avoid starving the host. Example: max-bytes=512,period=1000 for 512 bytes/s.

## Supported Guest Systems

| OS | Drivers |
| Microsoft Windows | http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers |
| Linux-based | 2.6.x, 3.x, 4.x |
| FreeBSD | 9.x (available), 10.x (in GENERIC kernel) https://www.freebsd.org/cgi/man.cgi?query=virtio&sektion=4 |
| NetBSD | 6.0+ |
| OpenBSD | 5.9+ |
# QEMU/Devices/USB/Root

The following USB controller devices are provided.

## xHCI

xHCI controllers can handle USB 1.0/2.0/3.0.
| name | bus | description |
| nec-usb-xhci | PCI |
| qemu-xhci | PCI |

## EHCI

EHCI controllers can only handle USB 2.0 (with a few exceptions not included by QEMU), so a companion controller is needed for USB 1.x.
| name | bus | description |
| usb-ehci | PCI |
| ich9-usb-ehci1 | PCI |

## UHCI

Intel and VIA controllers fall into this section. Other vendors tend to use OHCI.
These controllers support USB 1.0 and are more software-intensive than their counterparts, thus less efficient at virtualization.
| name | bus |
| ich9-usb-uhci1 | PCI |
| ich9-usb-uhci2 | PCI |
| ich9-usb-uhci3 | PCI |
| piix3-usb-uhci | PCI |
| piix4-usb-uhci | PCI |
| vt82c686b-usb-uhci | PCI |

## OHCI

Controllers under this section support USB 1.1.
| name | bus | description |
| sysbus-ohci | System | OHCI USB Controller |
| pci-ohci | PCI | Apple USB Controller |
# QEMU/Linux

    Note: Use ./configure --help to get a list of options, including the choices of architectures to target. If no options are selected, configure prepares all architectures, which is a very long process.
See the official documentation for further instructions and information.
# QEMU/Invocation
## QEMU options

QEMU is called with the following commands on host systems with x86 processor architecture.
The parameter Disk_image refers to the image of the first IDE hard disk (disk 0).
x86 architecture (32-bit):
x86 architecture (64 bit):
QEMU was called with 'qemu' before version 1.0.
The kernel-based virtual machine is often called with kvm instead of qemu. This is confusing, because the Native Linux KVM Tool is also invoked like that as well. Some distributions call with qemu-system-x86_64 or qemu-kvm.

### Debugging

Writes the log file to stderr. The following options are passed with commas to the command like : qemu -d int,cpu use -d help to get a full list.
Show generated host assembly code for each compiled Translation-Block (TB)
Show input assembly code for each compiled TB
Shows micro operations for each compiled TB
show micro ops after optimization
Show micro ops before indirect lowering
Show interrupts/exceptions in short format
Show trace before each executed TB (lots of logs)
Show CPU registers before entering a TB (lots of logs)
Log MMU-related activities
x86 only: show protected mode far calls/returns/exceptions
show CPU state before CPU resets
Log unimplemented functionality
Log when the guest OS does something invalid (eg accessing a non-existent register)
Dump pages at beginning of user mode emulation
Do not chain compiled TBs so that "exec" and "cpu" show complete traces

## Tracing

Configure like this :
Run like this :
* ↑ http://qemu-buch.de/de/index.php?title=QEMU-KVM-Buch/_Anhang/_Startoptionen_von_QEMU_und_KVM
* ↑ http://www.linux-kvm.org/images/c/c5/2011-forum-native-linux-kvm-tool.pdf
* ↑ http://wiki.qemu.org/Features/Tracing
* ↑ http://git.qemu-project.org/?p=qemu.git;a=blob_plain;f=docs/tracing.txt;hb=HEAD
# QEMU/Devices/Video
## VGA/SVGA

| Device | Bus | Description |
| cirrus-vga | PCI | Cirrus GD 5446 |
| isa-vga | ISA | Standard VGA |
| vmware-svga | PCI | VMware Virtual SVGA |
| isa-cirrus-vga | ISA | Cirrus VGA, ISA version |
| qxl-vga | | |
| ati-vga | PCI | Models: rv 100, 128 pro |
# QEMU/FreeDOS

FreeDOS is a great way to bring all of those old, much-loved and hard to replace programs from the DOS world back to life under a modern operating system. Using FreeDOS, graphical programs that won't run under Microsoft Windows, Wine or DOSBox might just run flawlessly under QEMU.
Download one of the bootable CD images from the FreeDOS distribution. The FreeDOS 1.2 "standard" CDROM image should work on most computers and PC emulators. FreeDOS 1.2 was released 25 December, 2016.

## Creating an image

To make it possible to exchange files with FreeDOS by copying files to and from the image, don't create the image as qcow. Instead, just create raw images. This will allow the FreeDOS image to be mounted under Linux and other Unix-like hosts just like a regular hard drive. Create a 100 MiB hard disk image named freedos.img:
Now boot up FreeDOS from the CD image (FD12CD.iso) and follow the menus to partition, format and install onto the hard drive.
Once the install is complete, you can boot FreeDOS from the image file without the CD.
To transfer files between FreeDOS and the host, stop QEMU and mount the FreeDOS image under the filesystem.
Reminder: never mount the image while QEMU is using it and remember to unmount it before starting QEMU again!
# QEMU/HostDevices

Example:
# Oberon/ETH Oberon/bootdos

This document was originally hosted at the ETHZ. It remains under the ETH license and is in the WayBack archive.
An operating system is started first. Then, using a program running in that environment, a further operating system is started. That program is able to start a kernel of the goal OS stored in a file in a DOS directory. The procedures for starting ETH Oberon and Linux in this way are so similar that everything boils down to this simple statement: the DOS-program noboot.exe is to ETH Oberon what loadlin is to Linux. This should become clear when looking at the example CONFIG.SYS and AUTOEXEC.BAT files below.
The correspondance is as follows (the names are indicative, not imperative):
It is not even necessary to have a (minimal) DOS partition on hard disk. A DOS boot diskette is enough.
Advantage: Adding a partition does modify the partition table in the MBR, but apart from that the MBR is not altered. Hence, the danger of malignous side effects due the addition of an OS, like ETH Oberon, to a system is minimized. The partition can be placed anywhere.
The following was tested with MS-DOS only but should also be applicable to IBM DOS, Caldera DOS and IBM DOS 2000. noboot is the DOS program which loads the Oberon kernel stored in a DOS directory in a file usually named "native.bin". The load process is directed by configuration specifications contained in another file (usually "native.par") stored in the same directory. noboot integrates itself seamless in an existing DOS or Windows 95/98 environment and can be used with most of the boot managers.
noboot requires a bare-bone DOS system and no more. If Oberon fails to start, e.g. hangs in the middle of the boot process, analyze the CONFIG.SYS and AUTOEXEC.BAT files and REM the lines related to memory management. In particular, those mentioning HIGH, or those involving the use of EMS or XMS. Alternatively, force Oberon to enter debug mode using the option -d mentioned below.
Start Oberon at the DOS prompt by executing the command:
If the running system is Windows 95/98, MS-DOS 7.0 is be started by restarting Windows in DOS mode or by pressing Shift-F5 when Windows starts. noboot is started in DOS-mode from the user interface. A special icon native.ico is provided for that purpose.
It is not possible to switch directly from Windows NT to Oberon. A DOS boot diskette or an additional, minimal DOS partition must be started in that case, via a boot manager for example.
These example texts control the access to three co-resident Oberon systems: MS-DOS, Oberon, Linux.
1 - Example NATIVE\NATIVE.PAR file
2 - Example CONFIG.SYS
3 - Example AUTOEXEC.BAT
4 - Example NATIVE\NATIVE.BAT
20 Nov 2002 - Copyright © 2002 ETH Zürich. All rights reserved. E-Mail: oberon-web at inf.ethz.ch Homepage: www.ethoberon.ethz.ch
# Oberon/ETH Oberon/bootfile

This document was originally hosted at the ETHZ. It remains under the ETH license and is in the WayBack archive.
If one feels it is too risky to partition a hard disk for installing a foreign OS on a working system hosting other OSes, the alternative is to install the unfamiliar OS in a large file in an existing file system. ETH Oberon can then co-exist with any number of other partition-based OSes, including Oberon, in these manners:
* if Windows is installed, in a FatFS
* if Linux is installed, in a Linux file system (EXT2)
As another example, this technique is also used by the free BeOS 5 Personal Edition.
When Windows is installed, this version of Oberon can be installed in a large FAT file. An easy-to-use installation program OberonInstaller.exe running under Windows is included. The program installs the big file and writes an Oberon boot file to a 1.44MB diskette, from which Oberon can then be booted. To uninstall, delete the file.
Note: It is an updated version of the software found on the CD-ROM included in the book Beginning Programming for Dummies.
When Linux is installed, an emulation of Native Oberon under Linux, is installed in a large file of the Linux file system (EXT2). The goal is not a tight integration in the Linux environment but a binary compatibility with Native Oberon. This implementation does not change the module interfaces. Oberon is started in the X11 environment by executiong a ./oberon command.
Installation and usage informations in Native Oberon Installation: Concepts and Procedures.
21 Nov 2002 - Copyright © 2002 ETH Zürich. All rights reserved. E-Mail: oberon-web at inf.ethz.ch Homepage: www.ethoberon.ethz.ch
# Reaktor/Tutorials/Reaktor as effects processor/Processing options
## Processing options

To process live input, set your audio system (System?Audio + MIDI Settings) so you're getting meter movement on the Toolbar's Audio Input meters when you play, sing, or otherwise run audio into your computer's audio interface, then load an effect by opening an effect ensemble.
To process audio files, open Reaktor's Playerbox (Mac: Command F2—hold “f” key on Powerbooks/PC: Ctrl F2) and click the folder icon on it, which will open any .wav or .aif file, and give you transport and looping controls for playing the file thru any loaded effects ensemble; no additional wire connecting is required. You can access any other audio file in the same folder with the drop-down menu on the Playerbox, and the Playerbox stays loaded when you change to any other effect ensemble, even if it isn't visible (hit command/ctrl F2 again to see it).
To process other Reaktor ensembles/instruments, open the ensemble structure view (hit the toolbar Structure button, or use the contextual menu for the ensemble Ctrl-click [Mac], right-click [PC]) of a source ensemble and select, then delete, the wires from the source to the Audio Out module. Next, insert an effect instrument into the ensemble structure (using the contextual menu or by dragging it from the Browser), wire (or “patch”) the outputs of the source instrument into the inputs of the effect instrument by dragging from the instrument's Out ports to the effect's In ports, then connect the effect Outs to the Audio Out module.
next page
# Reaktor/Tutorials/Reaktor as effects processor/Signal routing devices
## Signal routing devices

Of course, there are devices you can use to create more flexible routings in Reaktor than the simple cabling schemes just described, so let's look at few. You'll find example ensembles using these devices in the downloads that accompany this tutorial.
next page
# Reaktor/Tutorials/Reaktor as effects processor/Scanners and distributors
## Scanners and distributors

Two other related modules also offer powerful and uncommon routing options: The Selector/Scanner and the Distributor/Panner. The Distributor allows you to sweep a send position along the inputs of a stack of parallel routings, so that at any given position you are selecting either a single input, or a crossfade between two adjacent inputs. It's as if you were walking down a corridor at night, pointing a flashlight at one wall which had equally spaced windows on it; your signal would be like the light coming from the windows. The Scanner does the same thing with a monitor position along a stacked set of outputs. You can choose either or both, depending on the sound you're after; distributing your inputs into a bank of delays, for instance, would let the feedback ring out after the input has moved on, while a scanner after the same delays would cut off the feedback tails when it moved.
Here's a simple example, using only delays, each with a distinctive texture.
Here's a slightly more complex version of the same basic idea. It adds several series routings to a basic stack of “in-scanned” effects, and several of the effects have envelop-follower inputs, so there's an envelop-follower instrument included, too (these were swiped from a powerful User-library effect: 4fx 004, by Self Oscillate—check it out... and thanks!).
The first effect chain is a filter feeding a 10-second stereo looping delay with MIDI foot-controlled feedback. With the scanner position at 0, and the feedback all the way up, you can record a loop, then play over it ad nauseam without adding to it, just by scanning to a higher position. Three very different effects (a ring-modded distortion plus a delay, a soft stereo echo, and Martin Brinkman's great Multiband Delay, a distinctive filtered multi-tap) provide a range of tones to crossfade between when soloing over the loop, which can be faded out with the feedback control. The whole thing's very seductive... and it's in the tutorial downloads.
next page
# Reaktor/Tutorials/Reaktor as effects processor/Scanned tables — draw your own waves
## Scanned tables — draw your own waves

Our next modulation tool expands the scope of the Positive-only LFO by allowing it to scan multiple wave-forms that you can draw yourself. You can also scan these wave-forms using a MIDI controller, such as a foot-pedal, or with an envelop follower, for totally sound-driven, customized modulations (many thanks to John Nowak, who built the tables!).
next page
# Reaktor/Tutorials/Reaktor as effects processor/Recommended hardware
## Recommended hardware

An ideal live or studio setup for using R effects is to use a mixer to monitor and process your audio, treating R and your computer as a hardware effects unit patched into the mixer's effects sends. Using a mixer allows you to hear the R effects either by themselves or mixed with the external audio sources they're processing, so you can keep your effect ensembles as full-wet processors. I always bring the R/computer outs into their own pair(s) of mixer channels, rather than the mixer's effects returns, so the processed signal (and any R sound sources) can be further processed by hardware effects using the mixer's additional effect sends.
A tabletop or footpedal MIDI controller is a great addition to any R studio. As a guitar player, I prefer footpedals, and I want lots of continuous-controller pedals as well as switches, or inputs for hooking up additional pedals. I use a Roland FC-200, and it's ideal, offering six pedal inputs in addition to the included switches and pedal. Once your MIDI system is configured properly, it's wonderful to simply control/?-click on any R panel control, choose MIDI Learn from the contextual menu, wiggle the controller you want to use, and see the control move in response.
next page