nyuuzyou/wikis huggingface dataset:
Volkern

Volkern wordt ook wel Massief HPL, Volkunststof of Trespa genoemd en is een massieve kunststof.Dit materiaal bestaat uit papierlagen die met lagen hard versterkt zijn tot een homogene massa. Daaromheen worden een zogenaamde decorlaag en overlay aangebracht.
Volkern is speciaal ontwikkeld voor buitengebruik en is uitstekend bestand tegen zon-, regen- en vochtinvloeden en temperatuurschommelingen. Het oppervlak is veelal effen van kleur. Het voor volkern kenmerkende productieproces geeft de plaat de zwart bruine kleur als tegen de rand(en) wordt aangekeken.
==Productie==
De productie van Volkern is in hoge mate gelijk aan die van HPL. Afhankelijk van de uiteindelijke dikte van het materiaal worden lagen met fenolhars geïmpregneerd kraftpapier op elkaar gelegd en onder hoge druk en bij hoge temperatuur samengeperst tot een massieve plaat. Evenals bij HPL zijn de bovenste twee lagen papier, de zogeheten decorlaag en de overlay, gedrenkt in melaminehars. Volkern is verkrijgbaar in twee diktes: 12mm of 32mm. Beide diktes worden ook geleverd met een aluminium wapening in de kern. Het wordt vooral toegepast waar dunnere bladen gewenst zijn. Maar ondanks de stijlvolle, geringe dikte is een volkern keukenblad toch bijzonder solide.
==Eigenschappen==
* Antistatisch
* Erg hittebestendig
* Hard en compact, niet-poreus materiaal
* Vlekbestendig
* Weer- en vochtbestendig
* Vrij kras- slijt- en stootvast
* Hygiënisch
* Zeer onderhoudsarm
* Mogelijkheid tot zeer strakke maatvoering
==Toepassing==
* Volkern werkbladen
:* Massief laminaat (Volkern) werkbladen
:* Nanotech massief laminaat (Volkern) werkbladen
Vrijstaande koel- en vriesapparaten

Vrijstaande koel- en vriesapparaten zijn bedoeld voor tussenbouw of worden losstaand in de keuken geplaatst. Voorbeelden zijn een koel-vries combinatie, Amerikaanse (side-by-side) koelkast of wijnkoeler. 
===Voordeel vrijstaande koel- en vriesapparaten=== 
Dit type koel- en vrieskast kan overal in de keuken geplaatst worden.
===Nadeel vrijstaande koel- en vriesapparaten=== 
* het is geen onderdeel van de inbouwkeuken waardoor het wat minder strak oogt;
* Er kan zich vuil en stof tussen de koel-en vrieskast en de rest van de keuken ophopen
Ga terug naar het onderwerp koelen en vriezen als je hier nog meer over wilt weten.
Category:Keukenapparatuur
Zink

Zink is een scheikundig element met symbool Zn en atoomnummer 30. Het is een blauw/wit overgangsmetaal.
===Ontdekking===
Zinklegeringen worden al eeuwenlang gebruikt. In Palestina en het vroegere Transsylvanië zijn objecten gevonden die tot 87% zink bevatten en dateren uit 1400 v.Chr. Rond het jaar 1000 was men in India al in staat zink te smelten en gedeeltelijk te zuiveren. Aan het einde van de 14e eeuw konden Hindoestanen zink onderscheiden van de toen al bekende andere metalen. In de Westerse Wereld wordt de ontdekking van zink veelal toegeschreven aan de Duitser Andreas Sigismund Marggraf, die het in het jaar 1746 isoleerde door het mineraal calamien te reduceren met houtskool. De herkomst van de naam 'zink' is onduidelijk.
De reden dat men in Europa pas in de 18e eeuw zink leerde maken, terwijl messing ("geel koper"), een legering van koper en zink, al vele eeuwen bekend was, is gelegen in de moeilijkheid bij het bereiden van dit metaal. Zink wordt namelijk al bij betrekkelijk lage temperatuur (907 graden Celsius) gasvormig. In de ovens waarin zinkerts met koolstof verhit wordt, heeft het metaal dus de neiging om in gasvormige toestand met de uitlaatgassen te ontsnappen. Als evenwel een mengsel van kopererts en zinkerts gebruikt werd, loste de zinkdamp meteen in het vloeibare koper op. Daarom bood het maken van messing geen probleem. In India en China was al omstreeks 1100 ontdekt dat het metaal gewonnen kon worden door een relatief koud voorwerp (bijvoorbeeld een aardewerken pot) in de gasvormig zink bevattende uitlaatgassen te steken. De zinkdamp slaat dan op dit voorwerp neer. Zink werd in India al in de 13e eeuw uit het mineraal calamien gewonnen door het met organisch materiaal, zoals wol, te reduceren.[1] Uit de 14e eeuw zijn zinken munten bekend, waarschijnlijk geslagen in het hindoe-koninkrijk Kangra in Himachal Pradesh.[2] Tussen 1600 en 1750 werd zink (in betrekkelijk kleine hoeveelheden) uit India en China naar het op dit punt technologisch achtergebleven Europa geëxporteerd.
===Toepassingen===
In de industrie wordt zink veelal gebruikt in legeringen. Enkele belangrijke toepassingen zijn:
*Als legeringsmateriaal in messing, zilvernikkel, soldeertin.[1]
*In batterijen.[1]
*Als regenpijp, dakgoot en dakbedekking
*Als muntmetaal. De Amerikaanse cent bestaat uit zink met een dun koperlaagje. Zowel in België als in Nederland werd zink in oorlogstijd gebruikt als goedkoop muntmetaal.
*In de geneeskunde wordt zinkoxide gebruikt als werkzaam onderdeel van diverse zalven bij eczeem. Het heeft een indrogende, verkoelende en adstringerende (samentrekkende) werking. Zink wordt ook als voedingssupplement toegepast.
Main Page

Session	Programs Used 	Topic 	Date
1 	TinkerCAD, IronCAD, Photoshop 	Introduction to Computer Aided Design (CAD), CAD Operation	1/22
2 	IronCAD, Photoshop 	Basic modeling with IronCAD 	1/27
3 	IronCAD, Photoshop 	Advanced modeling with IronCAD 	1/29
4 	IronCAD, Photoshop, Illustrator	Creating Technical Drawings of CAD Models 	2/3
3D Navigation

== IronCAD ==
If you are having trouble with orbiting:
* The problem is that your orbit centerpoint has drifted away from your object of interest
* You can reset your centerpoint by pressing F8, this zooms your view to all objects and sets your centerpoint at the middle of all objects
* If you have many objects and that is unfeasible, suppress all objects you are not working on
* Then press F8 again and only your objects of interest will be zoomed to
Lofting

Lofting is distinct from extrusion and sweeping because it allows the profile of the face to be altered.
== IronCAD ==
# Create a 2D sketch on the surface
# Make the profile that you want the surface to be lofted through
# Complete the sketch and make as many more as you need for the entire loft
# Offset the lofting profiles using the triball the amount you need them to be
# Doing the Loft
## Select Loft
## Select the part you want the loft from
## Starting from the surface on the part, select the profiles in order. A faint green outline should show up.
## Finish the Loft and see your new lofted part!
Main Page

__NOEDITSECTION__
__NOTOC__
 Welcome to Alpine Linux Wiki! 
Alpine Linux is a security-oriented, lightweight Linux distribution based on musl libc and Busybox.
Here is a more detailed overview of what makes our distribution distinctive; and a comparison with other distros.
== How can we help you? ==
	Installation Installing Alpine Linux 		FAQ Frequently Asked Questions 		Glossary
	Tutorials and Howtos Basic and advanced configuration tasks		Developer Documentation Alpine Linux Development		Contribute Contribute to Alpine Linux
* Current releases latest is 
* Links to other sites with information about Alpine
For licensing on any contributions, see the Privacy Policy.
2600hz

blue.box is an open source GUI for administration and configuration of FreeSWITCH and Asterisk based VoIP systems. It supports multi-tenancy and skinning, and is completely modular.
== Install Lighttpd ==
== Installing FreeSwitch ==
First use apk to install the needed software parts.
Change the permissions of 
== Starting ==
 
Starting http and sql server and adding to boot
== Installing 2600hz ==
Create a folder
Checkout the source code from the git repository
Change the folder permissions
Create a symlink to the create directory
== Configuring bluebox ==
Log on your bluebox
Browse to: http://WEBSERVER_IP_ADDRESS/bluebox and start configuration.
* Welcome to Bluebox 1.0 Setup Wizard
Accept Terms and Conditions
Next
* Initial Configuration
Select pqsl as database server, bluebox as database name, postgres as user, no password
Set Default Timezone
Note: Set Port to 3306 (for mysql); see - https://2600hz.atlassian.net/browse/BLUEBOX-445
Next
* Create Main Administrator
Master Administration Account
Email Address:youremail@yourserver.net
Password:adminpassword
Confirm Password:adminpassword
Next 
* Telephony Engine
In Telephony Configuration
Conf Directory: /etc/freeswitch
Global Sound File Directory: /usr/sounds
Next 
Conflicting configuration files will be permanently erased if you continue!
Next
* Installation
Ready to Install
Next
After that you will see Click here to use Bluebox 1.0!
And you finish you Bluesbox installation.
Note: If you are using the Alpine ACF, or if you change the port in the lighttpd.conf file, the go to the port you set.
e.g: if you set the port to 8080, then browse to: http://WEBSERVER_IP_ADDRESS:8080/bluebox
Note: Needs PHP DOM package (apk add php-dom)
Note: This documentation need some minor fixes.
Category:SQL
Category:Telephony
A20 OLinuXino Lime2

== Installation ==
Everything except U-boot is already present in the Generic ARM tarball on the download page.
=== Compile U-boot ===
Download the latest stable tag from the u-boot repository
then configure and compile u-boot
This should output a combined SPL file with u-boot called u-boot-sunxi-with-spl.bin
=== (OR) Using U-boot from NetBSD ===
NetBSD u-boot may also be used to complete the steps below. After extracting latest tarball, directory contains u-boot-sunxi-with-spl.bin.
=== Prepare an SD Card ===
Firstly, erase the first part of your SD Card including the partition table). 
Secondly, create a DOS partition table and add a primary partition to your card. 
Start the partition at sector 2048, change its type to W95 FAT32, and set its bootable flag.
 
Finally, create a FAT filesystem on the new partition. 
=== Copy Data to the SD Card ===
Copy SPL with u-boot to the SD Card offset by 8KB (specific to Sunxi). 
Mount the partition and extract files from the Generic ARM tarball onto it. 
 ├── alpine.apkovl.tar.gz
 ├── apks
 │ └── armv7
 │ ├── alpine-base-3.17.2-r0.apk
 │ ├── ...
 │ └── zlib-1.2.13-r0.apk
 ├── boot
 │ ├── dtbs-lts
 │ │ └── sun7i-a20-olinuxino-lime2.dtb
 │ ├── initramfs-lts
 │ ├── modloop-lts
 │ ├── System.map-lts
 │ └── vmlinuz-lts
 └── extlinux
 └── extlinux.conf
=== After Installation ===
The default login is root, HDMI should work out-of-the-box, ethernet is off by default. Use setup-alpine to complete the remaining configuration. The Installation page should guide you from here.
Category:ARM
Category:Installation
ACF acf www example

= Set the hostname with a web interface =
In this example we will use the hostname-model.lua and hostname-controller.lua from the previous example to set the hostname using the acf web interface.
For this example, we will assume you have root access on the linux box you are running on (preferably an alpine box!)
== Use the existing code ==
We should have 'mvc.lua in the current directory, with the controller and model in helloworld/app The Controller and Model look the same as the end of the mvc.lua example, except we've taken out the on_load, pre_exec, post_exec, and on_unload methods. 
=== helloworld/app/hostname-controller.lua ===
 -- hostname controller code 
 
 module ( ... , package.seeall )
 
 
 create = function (self ) 
 return self.model.update(self.clientdata.hostname)
 end 
 
 read = function (self)
 return self.model.read()
 end 
 
 update = create
 
 delete = function (self )
 self.clientdata.hostname="" 
 return self.worker:create() 
 end
=== helloworld/app/hostname-model.lua ===
 -- Model functions for retrieving / setting the hostname
 module ( ..., package.seeall )
 
 -- All functions return a table with
 -- A value, the type of the value, and a message if there was an error
 
 local hosttype={ type="string" }
 
 update= function ( name )
 -- Check to make sure the name is valid 
 
 if (name == nil) then
 hosttype.msg = "Hostname cannot be nil"
 elseif (#name > 16) then
 hosttype.msg = "Hostname must be less than 16 chars"
 elseif (string.find(name, "[^%w%_%-]")) then
 hosttype.msg = "Hostname can contain alphanumerics only"
 end
 
 -- If it is, set the hostname
 if (hosttype.msg == nil ) then
 local f = io.open("/etc/hostname", "w")
 if f then
 f:write(name .. "\n")
 f:close()
 end
 f = io.popen ("/bin/hostname -F /etc/hostname")
 f:close()
 return read()
 -- Otherwise, return the error message
 else
 hosttype.value = name
 return hosttype
 end
 end
 
 read= function ()
 local f = io.popen ("/bin/hostname")
 local n = f:read("*a") or "none"
 f:close()
 n=string.gsub(n, "\n$", "")
 hosttype.value = n
 return (hosttype) 
 end
== Get and configure ACF ==
1. Grab a copy of all the acf code and support libraries from svn and copy into an directory
2. Copy the acf.conf file to 
3. Start the web server 
You'll need haserl, lua, and mini_httpd installed to run acf. If not already done, please install them.
Start mini_httpd (by hand for now)
4. Move your hostname model and controller
5. Create a new view template, which is a "lua server page" Create the file as 
 <? local form = ... ?> 
 <h1>Hostname</h1>
 
 <form action="update" method=post> 
 <p>The Hostname is now <input name=hostname value="<?= form.value ?>"</p>
 
 <p>input type=submit value=Submit></p>
 </form>
6. Create a new roles file, which gives all users permission to access your actions. Create the file as /usr/share/acf/app/sample/hostname.roles
 GUEST=hostname/read,hostname/update
== Try the app ==
point your browser to your host/cgi-bin/acf/sample/hostname/read
You should now be able to update the hostname using the web interface, and your existing model and controller.
Category:ACF
ALSA

== Install ==
First you will need to install the Alsa packages, Linux sound driver and volume adjuster.
== Setup ==
Then you will need to add all your users (including root) to the audio group.
Find the default sound card.
The default sound card will show up. Try turning up the volume of Master and the device(s) such as speakers or microphones that you need, and audio should work ( - help, - toggle mute, ...)
If there are no volume controls visible, try hitting on your keyboard and toggling between the sound cards (which all might have the same name in the context menu that pops up except for the numbers next to and before the names).
Once you've found the sound card name that gives you volume controls, set the unique number that showed up in the context menu as your default soundcard.
Scroll down until you find the lines that start with defaults.ctl.card and defaults.pcm.card and put the number (you found in the context menu of the alsamixer command for the soundcard you want as your default) at the end of those lines separated by a space for each. For example, if the default sound card you want is "1".
Save your nano work by pressing + and confirm the changes by pressing . Then exit nano by pressing +.
Try turning up the volume of Master and the device(s) such as speakers or microphones that you need with the alsamixer command, and audio should work.
Alsa service is not started on install, you need to start it and to add it on OpenRC.
Gstreamer can now catch the device and the audio mixer is working.
Category:Installation
Category:Desktop
Category:Multimedia
Category:Sound
Category:Drivers
Category:Hardware
APKBUILD examples

The following APKBUILD examples will assist you in understanding how to create an APKBUILD and provide snippets to use in your own APKBUILD files. Often there are multiple possible solutions for a problem available. If you align your way to solve an issue with an existing solution, make the AKPBUILD files more legible for others and reduce the chance to implement a misbehaviour.
== Simple APKBUILD ==
* Simple APKBUILD example
* Meta APKBUILD example
* Fixing permissions in APKBUILD
* Git checkout APKBUILD
== Subpackages ==
* Subpackages
* Multiple subpackages
== Special subpackages ==
* -doc subpackage
* -test subpackage
* -examples subpackage
* -lang subpackages
== Application specific examples ==
* ACF
* JavaScript
* Perl
* Php
* Python
* Ruby
* Lua
* Go
* OCaml
* Haskell
* Chicken Scheme
* Neovim
Category:Development
APKBUILD examples:Go

== Go package policies ==
Go previous to version 1.6 did not handle dependencies (very well).
Every package inside alpine aports should be made reproducible (aka reproducible builds). Many Go projects still do not support proper verdoring and will pull all its depends from master branches. Because of this, packages made in different time spans could differ from each other (they are not bit to bit equal). We can prevent this if the source from which we build will always be the same (hence we use checksums to verify source tarballs which we fetch from upstream projects).
We currently have 3 situations a Go packages could belong to:
# A package has no vendor directory (or is empty).
# A package has a vendor directory and contains a vendor file.
# A package has a vendor directory has a vendor file but also includes all deps.
TODO:
write something about glide for #1
write something about glide or another pkg manager for #2
just do go build for #3
Allow stripping of go bins https://github.com/golang/go/issues/1242
Category:Development
APKBUILD examples:Haskell

Packaging Haskell software may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python2-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called Cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.
It is not necessary to create a separate package for a Haskell library with this method.
At this time, there is no site directory where all Haskell programs should go.
You need to have this make depends:
 makedepends="ghc cabal"
Your prepare() statement should look like:
 prepare() {
 cd "$builddir"
 cabal sandbox init
 cabal configure --prefix=/usr
 }
Your build() statement should look like:
 build() {
 # the cabal install will automatically fetch all dependencies and compile all dependencies and the main program
 cabal install $pkgname-$pkgver --enable-relocatable
 }
After cabal install is done, it will place all the files in a hidden folder at "$builddir"/.cabal. Dump the contents of that folder into "$pkgdir"/usr/lib/$pkgname. Then, make a symlink from $pkgname/usr/lib/$pkgname/bin/$pkgname to /usr/bin/$pkgname 
Your package() statement should look like:
 package() {
 mkdir -p "$pkgdir/usr/lib"
 mv "$builddir"/.cabal "$builddir"/$pkgname
 mv "$builddir"/$pkgname "$pkgdir"/usr/lib/
 mkdir -p "$pkgdir/usr/bin"
 cd "$pkgdir/usr/bin"
 ln -s /usr/lib/$pkgname/$bin/$pkgname $pkgname
 }
As with licensing, make sure you put the licenses of the dependencies that cabal pulls also in the license= field.
== Finding packages ==
If you are a package creator, you can find additional packages in the Hackage package archive.
You can also search on GitHub but this guide doesn't tell you how to integrate a GitHub Haskell project with a Cabal sandbox yet.
Category:Development
APKBUILD examples:JavaScript

Packaging JavaScript based apps is easy as long as there is no heavy dependencies that may break on musl. Currently Electron based GUI apps are not supported but a wide range of command line apps are available on Linux which can be packaged for use for Alpine users.
Because there are literally hundreds of dependencies for a Node.js application, it makes more sense to just keep them all internal dependencies except those that require special patching. We are going to just cover the trivial packages easy packages for now.
Again, only package applications not Node.js libraries, but only if the Node.js package requires patching on musl.
== Requirements ==
* Node.js -- nodejs
* npm -- nodejs-npm
* A open source project with a package.json file in the root or in the app folder
== Which archive to get? ==
You still want to grab the archive file (.zip, .tar.gz, ...). Do not use npm install $pkgname@$pkgver. If the archive doesn't exist, then you can use that command in snapshot().
== Global variables ==
 depends="nodejs-npm"
== Build ==
In this step we tell npm to get the dependencies and build the binary dependencies if any. These dependencies will be placed in a folder called node_modules in the same directory as the package.json. You may need to do this repetitively at the root level and in the app folder if any, or wherever you see a package.json file without a node_modules.
 build() {
 cd "$builddir"
 npm install
 }
== Package ==
This is a simple example without documentation. You need to package the bin folder, the package*.json file, and the lib folder. There may be other files that need to be packaged. All apps should be placed in the "$pkgdir"/usr/lib/node_modules/$pkgname to make them visible for other nodejs programs or to keep track of the npm dependencies for CVE check for future tool.
You also want to place symlinks for some programs but not all because there is some overlap between npm apps for compatibility reasons and the native apps. Only symlink the main or major programs not the dependencies.
 package() {
 cd "$builddir"
 install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname
 cp -a bin lib node_modules package*.json "$pkgdir"/usr/lib/node_modules/$pkgname
 ln -s /usr/lib/node_modules/$pkgname/bin/$pkgname "$pkgdir"/usr/bin
 }
== Testing ==
 check() {
 cd "$builddir"
 npm test
 }
== Licensing ==
Since you are packaging the dependencies and the app under one package, you should list all the licenses for those dependencies in the license field. Use grep and find to find them.
== Security updates ==
In an event of a CVE notice and a update to fix that CVE for a npm dependency, you need to rebuild the package(s) and increment the pkgrel.
Category:Development