wiki

zandra's wiki
git clone git://zandra.org/wiki
Log | Files | Refs | README

commit b20811565001e2e4a8cdf5c0e909cb7bd30f21a5
parent aa4ad33d0d9e2a1bc07b96a570fb4daf18e2906f
Author: Ben O'Neill <ben@benoneill.xyz>
Date:   Sat,  2 Jan 2021 14:16:39 -0500

updates

Diffstat:
Minstallation-guide.md | 20++++++++------------
Anetworking.md | 50++++++++++++++++++++++++++++++++++++++++++++++++++
Apkgtools.md | 12++++++++++++
3 files changed, 70 insertions(+), 12 deletions(-)

diff --git a/installation-guide.md b/installation-guide.md @@ -17,23 +17,19 @@ architecture, compile flags, and more here. After this, you can begin the build process: ``` -# required definitions for mkbuild -export configmk=$(pwd)/config.mk # in zandra base directory -export mkbuild=$(pwd)/mkbuild # in zandra base directory - -# add cross compiler to $PATH (replace /opt/cross/bin if installed somewhere else) -# also make sure your pkgtools installation is in $PATH -export PATH="/opt/cross/bin:$PATH" - -mk init # initialize git submodules -mk # build base packages +[user@zandra ~]$ export mkbuild=$(pwd)/mkbuild # required for mkbuild +[user@zandra ~]$ export configmk=$(pwd)/config.mk # required for mkbuild +[user@zandra ~]$ export PATH="/opt/cross/bin:$PATH" # add cross compiler to $PATH + +[user@zandra ~]$ mk init # initialize git submodules +[user@zandra ~]$ mk # build base packages ``` ## Installing the packages to a root directory ``` -export ROOT="rootdir" # replace with desired path (an existing directory) -mk install +[user@zandra ~]$ export ROOT="rootdir" # replace with desired path (an existing directory) +[user@zandra ~]$ mk install ``` ## Making a bootable image diff --git a/networking.md b/networking.md @@ -0,0 +1,50 @@ +# Zandra Networking Guide + +## A Note on Drivers + +The minimal kernel configuration used in Zandra means that your +network drivers are likely not included if you aren't using Qemu. +These can be added by compiling your own kernel, either locally or +from another machine. + +## Wired + +Wired internet connection can be activated using 2 shell commands. +These can also be made a `svc` service (although this hasn't been +implemented yet). First, however, you must use `ip link` to find out +what your wired network interface is called: + +``` +[user@zandra ~]$ ip link +1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 +2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 + link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff +[user@zandra ~]$ +``` + +Now, you must turn the interface on and start a DHCP daemon. + +``` +[user@zandra ~]$ ip link set eth0 up +[user@zandra ~]$ sdhcp +``` + +## Wireless + +Wireless internet connection can be activated using `wpa_supplicant` as well as `sdhcp`. + +``` +[user@zandra ~]$ ip link # find wireless interface name +1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 +2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 + link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff +3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 + link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff +[user@zandra ~]$ wpa_passphrase "Wireless SSID" "password" >> /etc/wpa_supplicant.conf # add network +[user@zandra ~]$ wpa_supplicant -B -i wlan0 -D nl80211 -c /etc/wpa_supplicant.conf # start wpa_supplicant +[user@zandra ~]$ sdhcp # start DHCP +``` + +Again, this can be automated. diff --git a/pkgtools.md b/pkgtools.md @@ -0,0 +1,12 @@ +# Zandra Package Management Guide + +``` +# install foo +searchpkg '^foo#' | fetchpkg +installpkg foo#1.0.pkg.tgz # replace with actual version + +# remove foo +removepkg foo +``` + +You can remove packages by running removepkg foo.