9front operating system FQA

PDF
Document
This book was typeset (troff -ms -mpictures|lp -dstdout|ps2pdf) in Lucida Sans
by the author, using a Lenovo ThinkPad X60 Tablet running the 9front operating system.
Rendered: 2016-2-25
9FRONT
9front.org
This is a work of fiction. Names, characters, places and incidents either are the product
of the authors imagination or are used fictitiously, and any resemblance to actual per&shy;
sons, living or dead, businesses, companies, events or locales is entirely coincidental.
MIT/CC0/Public Domain
9FRONT FREQUENTLY QUESTIONED ANSWERS
Those who can do, those who can’t write and those who can’t write make ezines.
Sape Mullender
ACHTUNG! This documents STRUCTURE and some of its TEXT is plagiarized! from the OPENBSD FAQ!!
ACHTUNG! Information provided by this document may be outdated or just plain
wrong. Use your brain. NO REFUNDS.
_sl’s info is incorrect.
anth_x
2
0 − Introduction to Plan 9
0.1 - What is Plan 9?
0.1.1 - Plan 9 is not UNIX
0.1.1.1 - Plan 9 is not plan9port
0.1.1.2 - Plan 9 is not Inferno
0.1.2 - Plan 9 is not a product
0.1.3 - Plan 9 is not for you
0.2 - Why Plan 9?
0.2.1 - What do people like about Plan 9?
0.2.1.1 - What do you use Plan 9 for?
0.2.2 - What do people hate about Plan 9?
0.2.2.1 - What is not in Plan 9
0.2.3 - Why did Plan 9s creators give up on Plan 9?
0.2.4 - What is the deal with Plan 9s weird license?
0.2.4.1 - Richard Stallman hates the Plan Nine license (circa 2000)
0.2.4.2 - Theo de Raadt hates the Plan 9 license (circa 2003)
3
0.2.4.3 - Everyone hates the Plan 9 license (circa 2014)
0.3 - Further Reading
0.3.1 - Plan 9 papers
0.3.2 - Man pages
0.3.3 - Web pages
0.3.4 - Books
1 − Introduction to 9front
1.1 - What is 9front?
1.1.1 - Cirnos been our mascot for a while.
1.2 - On what systems does 9front run?
1.3 - Why might I want to use 9front?
1.3.1 - New Features
1.3.1.1 - New Programs
1.3.1.2 - New Hardware Support
1.4 - Is 9front really free?
1.5 - How can I help support 9front?
1.6 - Who maintains 9front?
1.7 - When is the next release of 9front?
1.8 - What is included with 9front?
1.9 - Can I use 9front as a desktop system?
1.10 - Why is/isnt ProductX included?
1.11 - Fine, where can I get 9front?
1.11.1 - Mirrors
1.11.1.1 - 9front.iso
1.11.1.2 - Mercurial repository
4
2 − Getting to know 9front
2.1 - Web Pages
2.2 - Mailing Lists
2.2.1 - Mailing List Archives
2.2.2 - Other useful mailing lists
2.3 - Manual Pages
2.3.2 - How do I write my own manual page?
2.4 - Reporting Bugs
2.4.1 - Your bug report SUCKS
2.4.2 - How do I get more useful info for developers?
2.4.2.1 - Take a photo of the panic screen
2.4.2.2 - Make a stack trace of a crashed process
2.4.2.3 - Make a process snapshot
3 − Hardware
3.1 - Selecting Hardware
3.2 - Known Working Hardware
3.2.0 - Input Devices
3.2.0.1 - Mice
3.2.0.1.1 - IBM/Lenovo
3.2.0.2 - Keyboards
3.2.0.2.1 - IBM/Lenovo
3.2.1 - Audio
3.2.2 - Graphics
3.2.2.1 - AGP
3.2.2.2 - Integrated
3.2.2.3 - PCI Express
3.2.3 - Networking
5
3.2.3.1 - Ethernet
3.2.3.1.1 - Integrated
3.2.3.1.2 - USB
3.2.3.1.3 - PCMCIA
3.2.3.2 - WiFi
3.2.3.2.1 - Bridge (external)
3.2.3.2.2 - Mini-PCI
3.2.3.2.3 - Mini-PCI Express
3.2.3.2.4 - PCI
3.2.3.2.5 - PCMCIA
3.2.4 - Tablet Digitizers
3.2.4.1 - Serial
3.2.4.1.1 - Integrated
3.2.5 - Laptops
3.2.5.1 - Acer
3.2.5.2 - IBM/Lenovo
3.2.5.2.1 - ThinkPad
3.2.5.3 - Toshiba
3.2.5.3.1 - Satellite
3.2.6 - Desktops
3.2.6.1 - eMachines
3.2.6.2 - Igel
3.2.6.3 - Soekris
3.2.6.4 - IBM/Lenovo
3.2.6.4.1 - ThinkCentre
3.3 - Virtual Machines
3.3.1 - Qemu
6
3.3.1.1 - Installation
3.3.1.2 - Post-Installation Booting
3.3.1.2.1 - Multiboot
3.3.1.4 - Networking
3.3.1.4.1 - Linux VDE
3.3.1.4.2 - OpenBSD tun(4)
3.3.1.4.3 - Windows TAP
3.3.1.5 - Audio
3.3.1.6 - Graphics
3.3.2 - Virtualbox
3.3.2.1 - Ethernet
3.3.2.2 - Audio
3.3.2.3 - Graphics
3.3.2.4 - Known Working Versions
3.3.3 - Virtio
4 − 9front Installation Guide
4.1 - Pre-installation Checklist
4.2 - Creating bootable 9front install media
4.2.1 - ISO image
4.2.2 - USB drive
4.2.2.1 - Creating on Plan 9
4.2.2.2 - Creating on Linux
4.2.2.3 - Bootargs
4.3 - Performing a simple install
4.3.1 - boot
4.3.2 - bootargs
4.3.3 - user
7
4.3.4 - vgasize, monitor, mouseport
4.3.4.1 - Changing screen resolution
4.3.5 - inst/start
4.3.6 - configfs
4.3.7 - partdisk
4.3.8 - prepdisk
4.3.9 - mountfs
4.3.10 - configdist
4.3.11 - confignet
4.3.11.1 - dhcp
4.3.11.2 - manual
4.3.12 - mountdist
4.3.13 - copydist
4.3.14 - sysname
4.3.15 - tzsetup
4.3.16 - bootsetup
4.3.17 - finish
4.4 - Encrypted Partitions
5 − Building the System from Source
5.1 - Why should I build my system from source?
5.2 - Building 9front from source
5.2.1 - Update sources
5.2.1.1 - hgrc
5.2.2 - Building from source
5.2.2.1 - Cross compiling
5.3 - Building an ISO
8
5.4 - Common Problems when Compiling and Building
5.4.1 - Upgrading compilers
6 − Networking
6.1 - Before we go any further
6.2 - Network configuration
6.2.1 - Host name
6.2.2 - Identifying and setting up your network interfaces
6.2.2.1 - Wifi
6.2.2.1.1 - Interfaces
6.2.2.1.1.1 - wavelan
6.2.2.1.1.2 - wavelanpci
6.2.2.1.1.3 - iwl
6.2.2.1.1.4 - rt2860
6.2.2.1.1.5 - wpi
6.2.2.1.2 - WPA
6.2.2.1.3 - Wifi Roaming
6.2.2.1.4 - Wifi Debug
6.2.3 - IP address
6.2.4 - Default gateway
6.2.5 - DNS Resolution
6.2.5.1 - Caching DNS server
6.2.5.2 - DNS authoritative name server
6.2.6 - Network-wide configuration
6.2.7 - Activating the changes
6.2.7.1 - NIC
6.2.7.2 - cs
6.2.7.3 - dns
9
6.2.8 - Verifying network settings
6.2.8.1 - Checking routes
6.2.8.1.1 - Adding static routes
6.2.9 - Setting up your 9front box as a forwarding gateway
6.2.10 - Setting up aliases on an interface
6.3 - How do I filter and firewall with 9front?
6.4 - Dynamic Host Configuration Protocol (DHCP)
6.4.1 - DHCP client
6.4.2 - DHCP server
6.5 - PPP
6.6 - Setting up a network bridge in 9front
6.7 - How do I boot from the network?
6.7.1 - How do I tcp boot?
6.7.1.1 - Passing arguments to ipconfig at the bootargs prompt
6.7.2 - How do I boot using PXE?
7 − System Management
7.1 - Plan 9 Services Overview
7.1.1 - What is the kernel?
7.1.2 - What is the file server?
7.1.3 - What is the auth server?
7.1.4 - What is the cpu server?
7.1.5 - What is a terminal?
7.2 - Kernel configuration and maintenance
7.2.1 - How do I mount the 9fat partition?
7.2.2 - How do I modify plan9.ini?
7.2.3 - Kernel configuration file
7.2.4 - Kernel drivers
10
7.2.5 - How do I install a new kernel?
7.3 - Fileserver configuration and maintenance
7.3.1 - Adding users
7.3.2 - Configuring nvram
7.3.3 - Setting up a listener for network connections
7.3.4 - Mounting a file system from userspace
7.4 - Auth server configuration and maintenance
7.4.1 - Configuring an auth server
7.4.1.1 - Avoiding an ndb entry for the auth server
7.4.2 - Adding users
7.4.3 - secstored
7.4.3.1 - Adding users to secstore
7.4.3.2 - Converting from ps9k1 to dp9ik
7.5 - Cpu server configuration and maintenance
7.5.1 - Configuring a cpu server
7.6 - Terminal configuration and maintenance
7.6.1 - Configuring a terminal
7.6.2 - Configuring a Terminal to Accept cpu Connections
7.6.3 - UTC Timesync
7.7 - Mail server configuration and maintenance
7.7.1 - smtpd.conf
7.7.2 - rewrite
7.7.3 - names.local
7.7.4 - remotemail
7.7.5 - SMTP over TLS
7.7.6 - IMAP4 over TLS
7.7.7 - Spam Filtering
11
7.7.7.1 - ratfs
7.7.7.2 - scanmail
7.8 - Web server configuration and maintenance
7.8.1 - ip/httpd
7.8.2 - rc-httpd
7.9 - TLS certificates
8 − Using 9front
8.1 - rc
8.1.1 - Prompts
8.1.2 - /env
8.2 - rio
8.2.1 - The Pop-up Menu
8.2.2 - Window control
8.2.3 - Text in rio windows
8.2.4 - Scrolling
8.2.5 - Mouse Chording
8.2.6 - Keyboard Shortcuts
8.2.7 - Color scheme
8.2.8 - Why is rio like this?
8.2.9 - tips
8.2.9.1 - Taking a screenshot
8.2.9.2 - Prevent console messages from overwriting the screen
8.3 - Text Editors
8.3.1 - sam
8.3.1.1 - Scrolling
8.3.1.2 - Mouse Chording
8.3.1.3 - Why does sam have a separate snarf buffer from rio?
12
8.3.1.4 - Keyboard Shortcuts
8.3.2 - acme
8.4 - Internet
8.4.1 - Mail
8.4.1.1 - upasfs
8.4.1.1.1 - Reading gmail via IMAP
8.4.1.2 - nedmail
8.4.1.3 - nupas
8.4.2 - NNTP
8.4.3 - IRC
8.4.3.1 - ircrc
8.4.3.2 - irc7
8.4.4 - FTP
8.4.5 - HTTP
8.4.5.1 - mothra
8.4.5.2 - abaco
8.4.5.3 - hget
8.4.5.4 - charon
8.4.5.5 - i
8.4.6 - SSH
8.4.6.1 - ssh
8.4.6.2 - ssh2
8.4.6.3 - scpu
8.4.6.4 - OpenSSH
8.4.6.5 - sftpfs
8.4.6.5.1 - Mounting a remote u9fs share over SSH
8.4.7 - secstore
13
8.4.8 - drawterm
8.5 - Audio
8.6 - External Media
8.6.1 - Mount an ISO9660 CD-ROM
8.6.2 - Burn a CD-ROM
8.6.3 - Mount a FAT formatted USB device
8.7 - Emulation
8.7.1 - Linux Emulation
8.7.2 - Nintendo
8.7.3 - Sega
8.8 - Additional Software
8.8.1 - 9front sources server
8.8.2 - 9front contrib
8.8.3 - Other public 9p servers
8.9 - Bootstrapping architectures not included on the ISO
8.9.1 - amd64
8.9.2 - Raspberry Pi
8.10 - ACPI
8.10.1 - Enabling ACPI
8.11 - MP Table Override
8.12 - Revision Control
8.12.1 - cvs
8.12.2 - git
8.12.3 - Mercurial
8.12.4 - svn
14
9 − Troubleshooting
9.1 - First
9.2 - Booting
9.2.2 - Break into a shell
9.2.3 - Editing plan9.ini
9.2.4 - Boot media not recognized
9.2.5 - I moved my hard drive between ports
9.3 - Graphics
9.3.1 - Rio fails to start
9.3.2 - VESA BIOS does not contain a valid mode
9.4 - Networking
9.4.1 - Networking is not working
9.4.2 - Cannot resolve domain names
9.4.3 - /mnt/web/clone does not exist
9.4.4 - PCMCIA WiFi stopped working after reboot
9.5 - USB
9.5.1 - Devices not recognized or not working
9.5.2 - System freezes after showing memory sizes
9.6 - auth
9.99999999999999999999999999999999999999 - GIVE UP
Appendix
J - Junk
15
L - Languages
16
FQA 0 − Introduction to Plan 9
0.1 − What is Plan 9?
Plan 9 is a research operating system from the same group who created UNIX at Bell
Labs Computing Sciences Research Center (CSRC). It emerged in the late 1980s, and its
early development coincided with continuing development of the later versions of
Research UNIX. Plan 9 can be seen as an attempt to evolve some of the same ideas that
informed UNIX into the era of networking and graphics. Rob Pike has described Plan 9
as &quot;an argument&quot; for simplicity and clarity, while others have described it as &quot;UNIX, only
moreso.&quot;
From The Use of Name Spaces in Plan 9:
17
Plan 9 argues that given a few carefully implemented abstractions it is possi&shy;
ble to produce a small operating system that provides support for the largest
systems on a variety of architectures and networks.
From the intro(1) man page:
Plan 9 is a distributed computing environment assembled from separate
machines acting as terminals, CPU servers, and file servers. A user works at a
terminal, running a window system on a raster display. Some windows are
connected to CPU servers; the intent is that heavy computing should be done
in those windows but it is also possible to compute on the terminal. A sepa&shy;
rate file server provides file storage for terminals and CPU servers alike.
The two most important ideas in Plan 9 are:
&quot; private namespaces (each process constructs a unique view of the hierarchical file
system)
&quot; file interfaces (familiar from UNIX, but taken to the extreme: all resources in Plan
9 look like file systems)
Most everything else in the system falls out of these two basic ideas.
Read: intro(1); Plan 9 from Bell Labs; Designing Plan 9, originally delivered at the
UKUUG Conference in London, July 1990; and FQA 7 − System Management; for a more
detailed overview of Plan 9s design.
Today, Plan 9 continues in its original form, as well as in several derivatives and forks:
Plan 9 from Bell Labs The original Plan 9. Effectively dead, all the developers have
been run out of the Labs and/or are on display at Google.
Plan 9 from User Space Plan 9 userspace ported/imitated for UNIX (specifically OS X).
18
9legacy David du Colombiers cherry picked collection of patches from various
people/forks to Bell Labs Plan 9. (it is not a fork)
9atom Erik Quanstroms fork of Plan 9, maintained to eriks needs and occasionally
pilfered by 9front.
9front (thats us) (we rule (were the tunnel snakes))
NIX High performance cloud computing is NIX imploded in a cloud of political
acrimony and retarded bureaucratic infighting.
NxM A kernel for manycore systems never spotted in the wild.
Clive A new operating system from Francisco J. Ballesteros, designed to generate
grantwriting practice material and research projects for otherwise indolent students.
Akaros Akaros is an open source, GPL-licensed operating system for manycore
architectures. Has no bearing on anything but has attracted grant money.
Harvey Harvey is an effort to get the Plan 9 code working with gcc and clang.
Inferno Inferno is a distributed operating system started at Bell Labs, but is now
developed and maintained by Vita Nuova Holdings as free software. Just kidding it is not
developed or maintained.
0.1.1 − Plan 9 is not UNIX
In the words of the Bell Labs Plan 9 wiki:
Plan 9 is not Unix. If you think of it as Unix, you may become frustrated when
something doesnt exist or when it works differently than you expected. If
you think of it as Plan 9, however, youll find that most of it works very smo&shy;
othly, and that there are some truly neat ideas that make things much cleaner
19
than you have seen before.
Confusion is compounded by the fact that many UNIX commands exist on Plan 9 and
behave in similar ways. In fact, some of Plan 9s userland (such as the upas mail
interface, the sam text editor, and the rc shell) are carried over directly from
Research UNIX 10th Edition. Further investigation reveals that many ideas found in Plan
9 were explored in more primitive form in the later editions of Research UNIX.
However, Plan 9 is a completely new operating system that makes no attempt to
conform to past prejudices. The point of the exercise (circa the late 1980s) was to avoid
past problems and explore new territory. Plan 9 is not UNIX for a reason.
Read: UNIX to Plan 9 command translation, UNIX Style, or cat −v Considered Harmful
0.1.1.1 − Plan 9 is not plan9port
Plan 9 from User Space (also known as plan9port or p9p) is a port of many Plan 9 from
Bell Labs libraries and applications to UNIX-like operating systems. Currently it has been
tested on a variety of operating systems including: Linux, Mac OS X, FreeBSD, NetBSD,
OpenBSD, Solaris and SunOS.
Plan9port consists of a combination of mostly unaltered Plan 9 userland utilities pack&shy;
aged alongside various attempts to imitate Plan 9s kernel intefaces using miscellaneous
available UNIX programs and commands. Some of the imitations are more successful
than others. In all, plan9port does not accurately represent the experience of using
actual Plan 9, but does provide enough functionality to make some users content with
running acme on their Macbooks.
0.1.1.2 − Plan 9 is not Inferno
Inferno is a distributed operating system also created at Bell Labs, but which is now
developed and maintained by Vita Nuova Holdings as free software. It employs many
20
ideas from Plan 9 (and even shares some source code), but is a completely different OS.
Note: Inferno shares some compatible interfaces with Plan 9, including the 9P/Styx pro&shy;
tocol.
0.1.2 − Plan 9 is not a product
Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!smb
From: [email protected] (Steven Bellovin)
Newsgroups: comp.unix.wizards
Subject: Re: Plan 9? (+ others)
Message-ID: &lt;[email protected]&gt;
Date: 23 Aug 88 16:19:40 GMT
References: &lt;[email protected]&gt; &lt;[email protected]&gt; &lt;[email protected]&gt;
Organization: AT&amp;T Bell Laboratories, Murray Hill
Lines: 33
Plan 9 is not a product, and is not intended to be. It is research -an experimental investigation into a different way of computing. The
developers started from several basic assumptions: that CPUs are very
cheap but that we dont really know how to combine them effectively; that
*good* networking is very important; that an intelligent user interface
(complete with dot-mapped display and mouse) is a Right Decision; that
existing systems with networks, mice, etc., are not the correct way to
do things, and in particular that todays workstations are not the way to
go. (No, I wont bother to explain all their reasoning; thats a long
and separate article.) Finally, the UNIX system per se is dead as a
vehicle for serious research into operating system structure; it has grown
too large, and is too constrained by 15+ years of history.
Now -- given those assumptions, they decided to throw away what we have
today and design a new system. Compatibility isnt an issue -- they are
not in the product-building business. (Nor are they in the lets make
another clever hack business.) Of course aspects of Plan 9 resemble
the UNIX system quite strongly -- is it any surprise that Pike, Thompson,
et al., think that thats a decent model to follow? But Plan 9 isnt,
and is not meant to be, a re-implementation of the UNIX system. If you
want, call it a UNIX-like system.
Will Plan 9 ever be released? I have no idea. Will it remain buried?
I hope not. Large companies do not sponsor large research organizations
just for the prestige; they hope for an (eventual) concrete return in the
form of concepts that can be made into (or incorporated into) products.
--Steve Bellovin
Disclaimer: this article is not, of course, an official statement from AT&amp;T.
Nor is it an official statement of the reasoning behind Plan 9. I do think
its accurate, though, and Im sure Ill be told if Im wrong...
21
0.1.3 − Plan 9 is not for you
Let’s be perfectly honest. Many features that todays &quot;computer experts&quot; consider to
be essential to computing (javascript, CSS, HTML5, etc.) either did not exist when Plan 9
was abandoned, or were purposely left out of the operating system. You might find this
to be an unacceptable obstacle to adopting Plan 9 into your daily workflow. If you
cannot imagine a use for a computer that does not involve a web browser, Plan 9 may
not be for you.
See: http://harmful.cat-v.org/software/
0.2 − Why Plan 9?
You may ask yourself, well, how did I get here? In the words of Plan 9 contributor Russ
Cox:
Why Plan 9 indeed. Isnt Plan 9 just another Unix clone? Who cares?
Plan 9 presents a consistent and easy to use interface. Once youve settled in,
there are very few surprises here. After I switched to Linux from Windows
3.1, I noticed all manner of inconsistent behavior in Windows 3.1 that Linux
did not have. Switching to Plan 9 from Linux highlighted just as much in
Linux.
One reason Plan 9 can do this is that the Plan 9 group has had the luxury of
having an entire system, so problems can be fixed and features added where
they belong, rather than where they can be. For example, there is no tty
driver in the kernel. The window system handles the nuances of terminal
input.
If Plan 9 was just a really clean Unix clone, it might be worth using, or it might
not. The neat things start happening with user-level file servers and perprocess namespace. In Unix, /dev/tty refers to the current windows output
device, and means different things to different processes. This is a special
hack enabled by the kernel for a single file. Plan 9 provides full-blown perprocess namespaces. In Plan 9 /dev/cons also refers to the current windows
output device, and means different things to different processes, but the win&shy;
dow system (or telnet daemon, or ssh daemon, or whatever) arranges this,
and does the same for /dev/mouse, /dev/text (the contents of the current
window), etc.
Since pieces of file tree can be provided by user-level servers, the kernel need
not know about things like DOSs FAT file system or GNU/Linuxs EXT2 file
system or NFS, etc. Instead, user-level servers provide this functionality when
desired. In Plan 9, even FTP is provided as a file server: you run ftpfs and the
files on the server appear in /n/ftp.
We need not stop at physical file systems, though. Other file servers synthe&shy;
size files that represent other resources. For example, upas/fs presents your
mail box as a file tree at /mail/fs/mbox. This models the recursive structure
of MIME messages especially well.
As another example, cdfs presents an audio or data CD as a file system, one
22
file per track. If its a writable CD, copying new files into the /mnt/cd/wa or
/mnt/cd/wd directories does create new audio or data tracks. Want to fixate
the CD as audio or data? Remove one of the directories.
Plan 9 fits well with a networked environment, files and directory trees can be
imported from other machines, and all resources are files or directory trees,
its easy to share resources. Want to use a different machines sound card?
Import its /dev/audio. Want to debug processes that run on another
machine? Import its /proc. Want to use a network interface on another
machine? Import its /net. And so on.
Russ Cox
0.2.1 − What do people like about Plan 9?
Descriptive testmony by long time Plan 9 users Charles Forstyh, Anthony Sorace and
Geoff Collyer:
http://www.plan9.bell-labs.com/wiki/plan9/what_do_people_like_about_plan_9/
0.2.1.1 − What do you use Plan 9 for?
if you dont know what this is usefull
then its not for you
See: FQA 8 − Using 9front
0.2.2 − What do people hate about Plan 9?
John floren provides a humorous(?) overview of a typical new users reactions to Plan 9:
Hi! Im new to Plan 9. Im really excited to work with this new Linux system.
I hit some questions.
1 How do I run X11?
2 Where is Emacs?
3 The code is weird. It doesnt look like GNU C at all. Did the people who
wrote Plan 9 know about C?
4 I tried to run mozilla but it did not work. How come?
Is this guy you?
Related: BUD/S
23
0.2.2.1 − What is not in Plan 9
A summary of common features you may have been expecting that are missing from
Plan 9:
http://c2.com/cgi/wiki?WhatIsNotInPlanNine
0.2.3 − Why did Plan 9’s creators give up on Plan 9?
All of the people who worked on Plan 9 have moved on from Bell Labs and/or no longer
work on Plan 9. Various reasons have been articulated by various people.
Russ Cox:
I ran Plan 9 from Bell Labs as my day to day work environment until around
2002. By then two facts were painfully clear. First, the Internet was here to
stay; and second, Plan 9 had no hope of keeping up with web browsers. Port&shy;
ing Mozilla to Plan 9 was far too much work, so instead I ported almost all the
Plan 9 user level software to FreeBSD, Linux, and OS X.
Russ Cox (again):
The standard set up for a Plan 9 aficionado here seems to be a Mac or Linux
machine running Plan 9 from User Space to get at sam, acme, and the other
tools. Rob, Ken, Dave, and I use Macs as our desktop machines, but were a
bit of an exception. Most Google engineers use Linux machines, and I know
of quite a few ex-Bell Labs people who are happy to be using sam or acme on
those machines. My own setup is two screens. The first is a standard Mac
desktop with non-Plan 9 apps and a handful of 9terms, and the second is a
full-screen acme for getting work done. On Linux I do the same but the first
screen is a Linux desktop running rio (formerly dhogs 8&frac12;).
More broadly, every few months I tend to get an email from someone who is
24
happy to have just discovered that sam is still maintained and available for
modern systems. A lot of the time these are people who only used sam on
Unix, never on Plan 9. The plan9port.tgz file was downloaded from 2,522
unique IP addresses in 2009, which I suspect is many more than Plan 9 itself.
In that sense, its really nice to see the tools getting a much wider exposure
than they used to.
I havent logged into a real Plan 9 system in many years, but I use 9vx occa&shy;
sionally when I want to remind myself how a real Plan 9 tool worked. Its
always nice to be back, however briefly.
Russ
Russ Cox continues:
&gt;
&gt;
&gt;
&gt;
Can you briefly tell us why you (Russ, Rob, Ken and Dave)
no longer use Plan9 ?
Because of missing apps or because of missing driver for your hardware ?
And do you still use venti ?
Operating systems and programming languages have strong network effects:
it helps to use the same system that everyone around you is using. In my
group at MIT, that meant FreeBSD and C++. I ran Plan 9 for the first few
years I was at MIT but gave up, because the lack of a shared system made it
too hard to collaborate. When I switched to FreeBSD, I ported all the Plan 9
libraries and tools so I could keep the rest of the user experience.
I still use venti, in that I still maintain the venti server that takes care of back&shy;
ups for my old group at MIT. It uses the plan9port venti, vbackup, and vnfs,
all running on FreeBSD. The venti server itself was my last real Plan 9 installa&shy;
tion. Its Coraid hardware, but I stripped the software and had installed my
own Plan 9 kernel to run venti on it directly. But before I left MIT, the last
thing I did was reinstall the machine using FreeBSD so that others could help
keep it up to date.
If I wasnt interacting with anyone else itd be nice to keep using Plan 9. But
its also nice to be able to use off the shelf software instead of reinventing
wheels (9fans runs on Linux) and to have good hardware support done by
other people (I can shut my laptop and it goes to sleep, and even better, when
I open it again, it wakes up!). Being able to get those things and still keep
most of the Plan 9 user experience by running Plan 9 from User Space is a
compromise, but one that works well for me.
Russ
Rob Pike:
What Russ says is true but for me it was simpler. I used Plan 9 as my local
operating system for a year or so after joining Google, but it was just too
inconvenient to live on a machine without a C++ compiler, without good NFS
and SSH support, and especially without a web browser. I switched to Linux
but found it very buggy (the main problem was most likely a bad graphics
board and/or driver, but still) and my main collaborator (Robert Griesemer)
25
had done the ground work to get a Mac working as a primary machine inside
Google, and Russ had plan9port up, so I pushed plan9port onto the Mac and
have been there ever since, quite happily. Nowadays Apples are officially sup&shy;
ported so its become easy, workwise.
I miss a lot of what Plan 9 did for me, but the concerns at work override that.
-rob
0.2.4 − What is the deal with Plan 9’s weird license?
Over the years Plan 9 has been released under various licenses, to the consternation of
many.
The first edition, released in 1992, was made available only to universities. The process
for acquiring the software was convoluted and prone to clerical error. Many potential
users had trouble obtaining it within a reasonable time frame and many complaints were
voiced on the eventual Plan 9 Internet mailing list.
The second edition, released in 1995 in book-and-CD form under a relatively standard
commercial license, was available via mailorder as well as through a special telephone
number for a price of approximately $350 USD. It was certainly easier to acquire than
the first edition, but many potential users still complained that the price was too high
and that the license was too restrictive.
0.2.4.1 − Richard Stallman hates the Plan Nine license (circa 2000)
In the year 2000, the third edition of Plan 9 was finally released under a custom &quot;open
source&quot; license, the Plan 9 License. Richard Stallman was not impressed:
When I saw the announcement that the Plan Nine software had been released
as &quot;open source&quot;, I wondered whether it might be free software as well. After
26
studying the license, my conclusion was that it is not free; the license contains
several restrictions that are totally unacceptable for the Free Software Move&shy;
ment. (See http://www.gnu.org/philosophy/free-sw.html.)
Read more here:
http://www.linuxtoday.com/developer/2000070200704OPLFSW
0.2.4.2 − Theo de Raadt hates the Plan 9 license (circa 2003)
In the year 2002, the fourth edition of Plan 9 was released under the Lucent Public
License. This time, Theo de Raadt was not impressed:
The new license is utterly unacceptable for use in a BSD project.
Actually, I am astounded that the OSI would declare such a license acceptable.
That is not a license which makes it free. It is a *contract* with consequences;
let me be clear -- it is a contract with consequences that I am unwilling to
accept.
Read more here:
http://9fans.net/archive/2003/06/270
0.2.4.3 − Everyone hates the Plan 9 license (circa 2014)
In 2014, portions of the Plan 9 source code were again re-licensed, this time under the
GPLv2, for distribution with the University of California, Berkeleys Akaros operating sys&shy;
tem. Predictably, various parties were not impressed.
Russ Cox tried to make sense of the situation by commenting in a Hacker News thread:
When you ask &quot;why did big company X make strange choice Y regarding
licensing or IP&quot;, 99 times out of 100 the answer is &quot;lawyers&quot;. If the Plan 9
group had had its way, Plan 9 would have been released for free under a triv&shy;
ial MIT-like license (the one used for other pieces of code, like the one true
awk) in 2003 instead of creating the Lucent Public License. Or in 2000 instead
of creating the &quot;Plan 9 License&quot;. Or in 1995 instead of as a $350 book+CD
that came with a license for use by an entire &quot;organization&quot;. Or in 1992
instead of being a limited academic release.
Thankfully I am not at Lucent anymore and am not privy to the tortured nego&shy;
tiations that ended up at the obviously inelegant compromise of &quot;The Univer&shy;
sity of California, Berkeley, has been authorised by Alcatel-Lucent to release
all Plan 9 software previously governed by the Lucent Public License, Version
1.02 under the GNU General Public License, Version 2.&quot; But the odds are over&shy;
whelming that the one-word answer is &quot;lawyers&quot;.
Some have suggested that confusion about licensing may have contributed to Plan 9s
failure to supplant UNIX in the wider computing world.
27
0.3 − Further Reading
0.3.1 − Plan 9 papers
Academic papers that describe the Plan 9 operating system are available here:
http://doc.cat-v.org/plan_9/
0.3.2 − Man pages
Section (1) for general publicly accessible commands.
Section (2) for library functions, including system calls.
Section (3) for kernel devices (accessed via bind(1)).
Section (4) for file services (accessed via mount).
Section (5) for the Plan 9 file protocol.
Section (6) for file formats.
Section (7) for databases and database access programs.
Section (8) for things related to administering Plan 9.
0.3.3 − Web pages
The official website for the Plan 9 project is located at: http://plan9.bell-labs.com/plan9
Bell Labs Plan 9 wiki: http://www.plan9.bell-labs.com/wiki/plan9/plan_9_wiki
Much valuable information can be found at http://cat-v.org regarding aspects of UNIX,
Plan 9 and software in general.
28
0.3.4 − Books
Introduction to OS Abstractions Using Plan 9 From Bell Labs, by Francisco J Ballestros
(nemo)
Notes on the Plan 9 3rd Edition Kernel, by Francisco J Ballestros (nemo)
The UNIX Programming Environment, by Brian W. Kernighan (bwk) and Rob Pike (rob)
(this book is the most clear, concise and eloquent expression of the Unix and tool
philosophies to date)
9front DASH 1 (the document you are reading right now, in book form)
29
FQA 1 − Introduction to 9front
1.1 − What is 9front?
Plan9front (or 9front) is a fork of the Plan 9 from Bell Labs operating system. The project
was started to remedy a perceived lack of devoted development resources inside Bell
Labs,[citation needed] and has accumulated various fixes and improvements.
This FQA specifically covers only the most recent release of 9front.
1.1.1 − Cirno’s been our mascot for a while.
Our mascot
30
Glenda is getting old, Cirno is now our mascot.
http://touhou.wikia.com/wiki/Cirno
Pro
&quot; girl
&quot; has magical powers
&quot; associated with 9
&quot; upsets kfx
&quot; she is known to be the strongest
31
Alternatives
1.2 − On what systems does 9front run?
9front runs on the following platforms:
&quot; 386
&quot; amd64
&quot; arm
&quot; mips
32
Read: FQA 3.2 − Selecting Hardware
1.3 − Why might I want to use 9front?
New users frequently want to know whether 9front is superior to some other free UNIXlike operating system. That question is largely unanswerable and is the subject of count&shy;
less (and useless) religious debates. Do not, under any circumstances, ask such a ques&shy;
tion on IRC or on a 9front mailing list.
Whether 9front is right for you is a question that only you can answer.
1.3.1 − New Features
&quot; /shr, global mountpoint device shr(3)
&quot; /mnt is provided by mntgen(4)
&quot; #A, audio drivers for sb16, intel hd audio and ac97 (both playback and recording
supported!) audio(3)
&quot; New BIOS based boot loader 9boot(8) featuring a console and support for
FAT/ISO/PXE and being small (&lt;8K)
&quot; New EFI based boot loader efi
&quot; Made kernel compliant to multiboot specification so it can be booted by qemu or
grub directly.
&quot; Interruptable kernel qlocks (eqlock)
&quot; Defered clunks (closeproc) for cached mounts
&quot; New rc based boot(8) allows breaking into a shell at any time
&quot; Default file system is an improved cwfs(4) (cwfs64x)
&quot; Support for encrypted partitions cryptsetup(8). Read: FQA 4 - 9front Instal&shy;
lation Guide
&quot; New screen fonts: dejavu, germgoth, vga
&quot; No central replica; source updates are done with hg(1) (Mercurial)
&quot; Keyboard events with /dev/kbd. Read: kbdfs(8) and rio(4)
&quot; /lib/ken, /lib/rob, /lib/rsc
&quot; New listen(8) −p maxprocs option
&quot; Always available network aan(8) support in cpu(1)
&quot; MSI (message signalled interrupts), avoids problems with broken MP tables. Read:
33
icanhasmsi(8) (dump MSI info)
&quot; Legacy free ACPI support (aml interpreter libaml, mp interrupt routing,
scram)
&quot; New rio(1) −b option (black window backgrounds)
&quot; USB CD-ROM boot/install
&quot; USB drive boot
&quot; Improved USB mouse support
&quot; Support for USB ptp cameras
&quot; Stable across machines USB device names
&quot; VGA initialization done by interpreting the VESA BIOS with realemu(8),
working VESA screen blanking.
&quot; /dev/kbd and clipboard charset support for vnc(1)
&quot; New webfs(4) with HTTP1.1 and Keep-Alive support.
&quot; Qemu/KVM virtio block device and ethernet drivers. Read: FQA 4.5.1.3 − Virtio
&quot; Mouse wheel and chording support in sam(1)
&quot; Elliptic curve cryptography ec(2)
&quot; Working interrupt key (Del) in console
&quot; Wifi support with wpa/wpa2
&quot; SSE support
&quot; System-wide support for internationalized domain names
&quot; Unicode support in vt(1)
&quot; pc64, kernel for amd64
1.3.1.1 − New Programs
&quot; &quot; and &quot;&quot; (print, repeat previous command)
&quot; alarm(1) timeouts in rc scripts
&quot; audio(1) mp3, ogg, flac, &micro;law, wav
&quot; bullshit(1) print out a stream of bullshit
&quot; cifsd(8) CIFS/SMB server
34
&quot; derp(1) find changes between directories
&quot; feminize(1) replace sexist remarks
&quot; fplot(1)
&quot; New games: doom, glendy, mandel, mines, mole, packet
&quot; hg(1) and hgfs(4) (Mercurial)
&quot; hget(1) rewritten in rc, now uses webfs
&quot; hpost(1) extract and post HTML forms
&quot; hold(1) simple text editor
&quot; ipserv(8) proxy servers socksd and hproxy
&quot; memory(1) check memory usage
&quot; mothra(1) Tom Duffs web browser, now uses webfs
&quot; netaudit(8) network configuration checker
&quot; newt(1) Usenet client
&quot; nietzsche(1) print out Nietzsche quote
&quot; nintendo(1) Nintendo emulators: gb, gba, nes, snes
&quot; page(1) zoom and enhance!
&quot; paint(1) drawing program
&quot; play(1) audio player
&quot; pstree(1) print tree-like map of current processes and sub-processes
&quot; rc−httpd(8) HTTP server
&quot; resize(1) fast but low quality image resampler
&quot; rotate(1) rotate or mirror a picture
&quot; scram(8) ACPI and APM shutdown
&quot; sega(1) Sega Megadrive/Genesis emulator: md
&quot; ssam(1) stream interface to sam
&quot; sysinfo(1) print hardware report
&quot; sysupdate(1) update the local hg repository
35
&quot; theo(1) print out insults from Theo de Raadt
&quot; tput(1) measure read throughput
&quot; troll(1) automated trolling
&quot; tap(1) follow the pipes of a process
&quot; tif(1) tiff decoder
&quot; tojpg(1) jpeg encoder
&quot; totif(1) tiff encoder
&quot; torrent(1) bittorrent client
1.3.1.2 − New Hardware Support
Audio
&quot; AC97 /sys/src/9/pc/audioac97.c
&quot; HDA /sys/src/9/pc/audiohda.c
&quot; SB 16/ESS /sys/src/9/pc/audiosb16.c
Ethernet
&quot; ADMtek Pegasus /sys/src/cmd/nusb/ether/aue.c
&quot; Broadcom BCM57xx /sys/src/9/pc/etherbcm.c
&quot; Realtek RTL8150 /sys/src/cmd/nusb/ether/url.c
Wifi
&quot; Intel Centrino Advanced-N 6205 (iwl-6005)
&quot; Intel Centrino Ultimate-N (iwl-6000)
&quot; Intel Centrino Wireless-N 100
&quot; Intel WiFi Link 1000/4965/5100/5300 AGN
&quot; Intel PRO Wireless 3945ABG (wpi-3945abg)
&quot; Ralink RT2860/RT3090
36
Tablets
&quot; Wacom WACF004, WACF008
/sys/src/cmd/aux/wacom.c, /sys/src/cmd/aux/tablet.c
Video
&quot; AMD Geode LX driver
/sys/src/cmd/aux/vga/geode.c /sys/src/9/pc/vgageode.c
&quot; Intel G45 and Ivy Bridge driver
/sys/src/cmd/aux/vga/igfx.c /sys/src/9/pc/vgaigfx.c
SD Card
&quot; Ricoh /sys/src/9/pc/pmmc.c
Read: FQA 3.2 − Known Working Hardware for a list of complete machines known to
work.
1.4 − Is 9front really free?
Yes.
Read: FQA 0.2.4 − What is the deal with Plan 9’s weird license?
37
Note: The maintainers of 9front support the project largely from their own pockets. This
includes the time spent programming for the project, equipment used, the network
resources used to distribute 9front to you, and the time spent answering questions and
investigating users bug reports. The 9front developers are not independently wealthy
and even small contributions of time, equipment, and resources make a big difference.
1.5 − How can I help support 9front?
We are greatly indebted to the people and organizations that have contributed to the
9front project.
1.6 − Who maintains 9front?
9front is maintained by a development team spread across many different countries.
1.7 − When is the next release of 9front?
The 9front team makes new releases on a regular, but unscheduled, basis. More infor&shy;
mation on the development cycle can be found here:
http://lists.9front.org
1.8 − What is included with 9front?
Some useful programs included with the operating system are:
&quot; acid Programmable symbolic debugger.
&quot; acme Text editor, window system, mail client and more.
&quot; ape ANSI/POSIX environment.
&quot; cwfs64x Cached-worm file server based on the original Kens fs.
&quot; doom Science fiction horror-themed first-person shooter video game by id
Software.
&quot; gs Aladdin Ghostscript (PostScript and PDF language interpreter).
&quot; hjfs A new, experimental fs.
&quot; mercurial Distributed source control management tool.
&quot; mk Tool for describing and maintaining dependencies between files.
&quot; mothra Web browser by Tom Duff.
&quot; newt NNTP client.
&quot; nintendo Nintendo Game Boy, NES, SNES and GBA emulators.
38
&quot; openssl Toolkit implementing the Secure Sockets Layer (SSL v2/v3) and
Transport Layer Security (TLS v1) protocols as well as a general purpose cryptogra&shy;
phy library. (needed for python (needed for mercurial))
&quot; paint Drawing program.
&quot; page FAX, image, graphic, PostScript, PDF, epub, cbz viewer.
&quot; play Flac, ogg, mp3, sun, wav player.
&quot; plumber Mechanism for inter-process communication.
&quot; python 2.5.1 Interpreted programming language. (needed for mercurial)
&quot; rc Shell by Tom Duff.
&quot; rc−httpd Web server written in rc.
&quot; rio Rectangle multiplexer/window system.
&quot; sam Text editor.
&quot; sega Megadrive/Genesis emulator.
&quot; torrent BitTorrent client.
&quot; troff Text processor/typesetter.
&quot; upas A simpler approach to network mail.
1.9 − Can I use 9front as a desktop system?
This question is often asked in exactly this mannerwith no explanation of what the
asker means by &quot;desktop&quot;. The only person who can answer that question is you, as it
depends on what your needs and expectations are.
Figure it out.
1.10 − Why is/isn’t ProductX included?
People often ask why a particular product is or isnt included with 9front. The answer is
based on two things: the wishes of the developers and compatibility with the goals of
the project. A product will not be included simply because it is &quot;nifty.&quot;
A major consideration is the wishes of the developers. The 9front developers are the
ultimate judges of what does and doesnt go into the project. Just because an applica&shy;
tion is &quot;good&quot; doesnt mean the 9front project wishes to devote the resources needed to
maintaining it, or that they will share others enthusiasm about its place in 9front.
Incredibly, many users still see fit to demand otherwise.
39
1.11 − Fine, where can I get 9front?
If you simply cannot be dissuaded from trying 9front for yourself, obtain installation
media from the following locations.
1.11.1 − Mirrors
1.11.1.1 − 9front.iso
http://9front.org/iso/
http://r-36.net/9front/
http://9front.r0x0r.me/
http://mirror.9fags.net/
http://thefront.felloff.net/usr/cinap_lenrek/9front.torrent
http://mirror.9fags.net/
1.11.1.2 − Mercurial repository
https://code.9front.org/hg/plan9front (official)
http://code.criticalpha.se/hg/plan9front (read-only)
40
Good Luck
41
FQA 2 − Getting To Know 9front
2.1 − Web Pages
The official websites for the 9front project are located at:
&quot; http://9front.org main website
&quot; http://bugs.9front.org bug tracker
&quot; http://fqa.9front.org official documentation, frequently questioned answers
&quot; http://lists.9front.org mailing lists
&quot; http://man.9front.org man pages
&quot; http://wiki.9front.org informal documentation, developer scratchpad
Somewhat outdated, and not entirely applicable to 9front is the Bell Labs Plan 9 wiki:
http://www.plan9.bell-labs.com/wiki/plan9/plan_9_wiki
Some users have set up sites and pages with 9front specific information. As with every&shy;
thing on the Internet, a good search engine is going to make your life easier, as will a
healthy dose of skepticism. As always, do not blindly enter commands you do not under&shy;
stand into your computer.
That said, much valuable information can be found at http://cat-v.org regarding aspects
of UNIX, Plan 9 and software in general.
42
2.2 − Mailing Lists
The 9front project maintains several mailing lists which users should subscribe to and
follow. To subscribe to a mailing list, send an e-mail message to [email protected],
where list is the name of the mailing list. That address is an automated subscription ser&shy;
vice. In the body of your message, on a single line, you should include the subscribe
command. For example:
subscribe
After subscribing, list messages are received from and sent to [email protected], where list
is the name of the mailing list.
The lists are as follows:
9front general discussion
9front-bugs report bugs
9front-commits read-only log of commits to the 9front mercurial repository
9front-sysinfo read-only log of sysinfo(1) output from user systems
To unsubscribe from a list, you will again send an e-mail message to [email protected]. It should look like this:
unsubscribe
Before posting a question on the 9front mailing list, please check the rest of this FQA. If
asking a question possibly related to hardware, always include the output of
sysinfo(1)!
2.2.1 − Mailing List Archives
Mailing list archives are available via 9p:
43
% 9fs 9front
post...
% ls /n/lists
/n/lists/9atom
/n/lists/9changes
/n/lists/9fans
/n/lists/9front
/n/lists/9front−bugs
/n/lists/9front−commits
/n/lists/9front−sysinfo
/n/lists/9nag
/n/lists/acme−sac
/n/lists/cat−v
/n/lists/cypherpunks
/n/lists/dlr
/n/lists/harvey
/n/lists/harvey−commits
/n/lists/harvey−issues
/n/lists/inferno
/n/lists/nix
/n/lists/plan9port−dev
/n/lists/sam−fans
/n/lists/sierra31
/n/lists/skunk−works
/n/lists/tscm−l
/n/lists/tuhs
/n/lists/werc
/n/lists/www−html
/n/lists/www−talk
/n/lists/www−vrml
Each of these directories contains messages sent to the respective mailing list in mdir
format, one message per file. Erik Quanstroms nupas upas/fs can mount these directo&shy;
ries as mailboxes, for reading directly with a mail client.
2.2.2 − Other useful mailing lists
44
9fans Official mailing list of Plan 9 from Bell Labs.
9changes Notifications of changes to Plan 9 from Bell Labs (unofficial).
9nag Ping alerts for plan9.bell-labs.com (unofficial).
2.3 − Manual Pages
9front comes with extensive documentation in the form of manual pages. Considerable
effort is made to make sure the man pages are up-to-date and accurate. In all cases, 1.)
the source, followed by 2.) the man pages, are considered the authoritative source of
information for 9front.
You can find all the 9front man pages on the web at the following sites:
http://man.9front.org
http://felloff.net/sys/man
http://man.aiju.de
http://man.cat-v.org/9front
http://plan9.stanleylieber.com/man
as well as on your 9front computer.
In general, if you know the name of a command or a manual page, you can read it by
executing man command. For example: man vi to read about the MIPS binary
emulator. If you dont know the name of the command, or if man command doesnt
find the manual page, you can search the manual page database by executing
lookman something, where something is a likely word that might appear in the
title of the manual page youre looking for. For example:
% lookman vesa
man 3 vga # vga(3)
man 8 realemu # realemu(8)
man 8 vga # vga(8)
The resulting list is presented in the form of commands that can be highlighted and
sent using rios mouse button 2 menu.
For many, having a hardcopy of the man page can be useful. To make a printable copy
of a man page:
man −t vga realemu | lp −dstdout &gt; vga.ps
or:
man −t vga realemu | lp −dstdout | ps2pdf &gt; vga.pdf
2.3.1 − How do I display a man page source file?
The command man −w prints the location of the man pages source file:
45
% man −w vga realemu
/sys/man/3/vga
/sys/man/8/realemu
/sys/man/8/vga
2.3.2 − How do I write my own manual page?
As was mentioned in FQA 0.3.2 − Man pages, Plan 9 man pages are divided into sections
based upon the features they describe. For example, the troff source of the io(1) man
page is located in section 1, in the file /sys/man/1/io. You can examine this troff
source for a simple example of how to format and construct a typical man page.
For additional information, read: How to Write a Plan 9 Manual Page, man(6),
troff(1)
2.4 − Reporting Bugs
&quot;I have with Plan 9 Is there a way to&quot;
Remember: 9front developers cannot read your mind. Very detailed information is
required to diagnose most serious bugs.
Also remember: It is possible you simply don’t know what you’re doing. If you do
not understand how something is done in 9front or how it works, and cant figure out
how to resolve the problem using the manual pages, FQA 8 − Using 9front, or FQA 9 −
Troubleshooting, join #9front on irc.freenode.net or use the mailing list
([email protected]) to request help.
On the other hand, its possible you really found a bug. If so, please file a bug report by
sending an e-mail to 9front−bugs−[email protected]. The subject line of your
e-mail will be used to open an issue on the bug tracker, and your message will be
46
forwarded to the 9front-bugs mailing list.
2.4.1 − Your bug report SUCKS
A minimum useful bug report contains the following:
&quot; A complete description of what you did
&quot; A complete description of what you expected to happen
&quot; A complete description of what happened, instead
Extra credit:
&quot; The make and model of your computer
&quot; The URL returned when you run sysinfo -p on the affected system
2.4.2 − How do I get more useful info for developers?
The following sub-sections offer some useful tips.
2.4.2.1 − Take a photo of the panic screen
Under some circumstances, you may not be able to recover text directly from a crashed
system. In this situation, snap a photo of the screen, including as much of the screen in
good focus as possible, and upload the image somewhere where it can be retrieved by
developers.
47
2.4.2.2 − Make a stack trace of a crashed process
% hget http://www.jwz.org/blog/feed | rssread
panic: D2B called on non−block c580 (double−free?)
rssread 882285: suicide: sys: trap: fault read addr=0x0 pc=0x000038ef
% acid 882285
/proc/882285/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk()
abort()+0x0 /sys/src/libc/9sys/abort.c:6
ppanic(p=0xb5a0,fmt=0xbf72)+0x146 /sys/src/libc/port/malloc.c:166
pv=0xc100
msg=0xc310
v=0xdfffee90
n=0x2b
D2B(p=0xb5a0,v=0xc580)+0x5a /sys/src/libc/port/pool.c:966
a=0xc578
poolfreel(v=0xc580,p=0xb5a0)+0x20 /sys/src/libc/port/pool.c:1190
ab=0xc100
poolfree(p=0xb5a0,v=0xc580)+0x41 /sys/src/libc/port/pool.c:1325
free(v=0xc588)+0x23 /sys/src/libc/port/malloc.c:250
nextxmlpull(x=0xc548)+0x334 /usr/sl/src/xmlpull/xmlpull.c:221
nextxmlpull(x=0xc548)+0x2cb /usr/sl/src/xmlpull/xmlpull.c:316
main()+0x34 /usr/sl/src/rssread/rssread.c:159
st=0x1
f=0xc5a8
r=0x0
x=0xc548
_main+0x31 /sys/src/libc/386/main9.s:16
acid:
48
2.4.2.3 − Make a process snapshot
To collect even more information than a stacktrace, you can also make a full process
snapshot, which includes all the memory of the program. The snapshot file can later be
analyzed (even on a different machine [even on a different machine of a different archi&shy;
tecture]).
% snap 882285 &gt; rssread.snap
49
FQA 3 − Hardware
3.1 − Selecting Hardware
Selecting appropriate hardware to run your 9front system on is important, as it can
mean the difference between success and failure of a project.
If you are shopping for a new PC, whether you are buying it piece by piece or completely
pre-built, you want to make sure first that you are buying reliable parts. In the PC world,
this is not easy. Bad or otherwise unreliable or mismatched parts can make 9front
run poorly and crash often. The best advice we can give is to be careful, and buy
brands and parts that have been reviewed by an authority you trust. Sometimes, a
higher-price machine is a better quality machine. Other times, it is simply more
expensive.
There are certain things that will help bring out the maximum performance of your
system:
Let the application choose the hardware: It is usually better to make an
adjustment to the hardware you were planning on using rather than compromising
on your application design because you have something you &quot;really wanted to use.&quot;
Identify your bottlenecks: Dont pay extra for the cutting-edge processor if your
application is restricted by disk I/O. Dont pay for fast disk if your system is
restricted by network speed. Dont pay for much of anything if your bottleneck is a
300bps dial-up line.
Keep it simple: Simple hardware usually has simple problems. Complex hardware
that isnt supposed to ever break may take you a long time to repair when it breaks
anyway.
Use hardware you understand, or learn the new hardware before you
implement a production system: Regardless of the technical merits of the
50
hardware, committing to use a particular type of hardware before you have become
familiar with it, both how it works and how it fails, is foolish.
Avoid cheap network adapters: 9front supports a plethora of cheap network
adapters. These adapters work great in home systems, and low or moderate
throughput business and research environments. But, if you need high throughput
and low impact on your server, you are better off buying a quality network adapter.
Unfortunately, some name-brand adapters are not much better than the cheap
adapters, and some potentially good adapters do not have accurate documentation
available to write good drivers. Gigabit adapters often perform better than
10Mbps/100Mbps adapters, even when used on slower speed networks, due to
superior buffering.
Check FQA 3.2 − Known Working Hardware as well as the various supported hardware
pages on the Bell Labs Plan 9 wiki to help determine if your hardware or VM is
supported.
3.2 − Known Working Hardware
This list adds to the various supported hardware pages on the Plan 9 from Bell Labs
wiki. Note: NONE of these lists are all-inclusive. Some drivers listed on the Bell Labs
wiki have not been tested by 9front developers. The following list consists of hardware,
1.) that we have actually used, or 2.) about which we have received reliable reports from
users.
Some drivers and their options are also documented in plan9.ini(8).
Read: FQA 1.3.1.2 − New Hardware Support for information about new hardware drivers
in 9front.
3.2.0 − Input Devices
3.2.0.1 − Mice
3.2.0.1.1 − IBM/Lenovo
N700 Wireless/Bluetooth, 3 button Mouse and Laser Pointer
Part Number: 888015450
DPI: 1200
&quot;Just works&quot; with USB receiver. No additional driver required.
51
ScrollPoint Optical Mouse, 3 button, USB/PS2
Part Number: 31P7405
DPI: 800
3.2.0.2 − Keyboards
52
3.2.0.2.1 − IBM/Lenovo
IBM Model M 1391401
Part Number: 1391401
IBM UltraNav SK−8835
Part Number: SK-8835
53
3.2.1 − Audio
AMD FCH Azalia Controller
vid/did: 1022/780d
Intel 888 Microsoft UAA bus for HD audio
vid/did: 8086/284b
Intel 82801CA/CAM AC97
vid/did: 8086/2485
Intel 82801 DB DBM/DA AC 97
vid/did: 8086/24c5
Intel 486486 82801IB/IR/IH HD Audio
vid/did: 8086/293e
Intel HD NM10/ICH7
vid/did: 8086/27d8
54
Intel HD 6 Series/C200 Series
vid/did: 8086/1c20
Intel HD 7 Series/C210 Series
vid/did: 8086/1e20
3.2.2 − Graphics
3.2.2.1 − AGP
NVidia GeForce FX 5200 128MB VGA output
vid/did: 10de/0322
monitor=vesa vgasize=1600x1200x32
monitor=dellst2210 vgasize=1920x1080x32
NVidia GeForce FX 5700
vid/did: 10de/0341
monitor=vesa vgasize=1600x1200x32
monitor=dellst2210 vgasize=1920x1080x32
3.2.2.2 − Integrated
55
ATI Mobility Radeon 7500 128MB DVI/VGA output
vid/did: 1002/4c57
monitor=vesa vgasize=1024x768x32
ATI Mobility Radeon FireGL V3200/X600
vid/did: 1002/3154
monitor=vesa vgasize=1600x1200x32
ATI RS880
monitor=vesa vgasize=1280x1024x32
ATI X1300
Intel Mobile 945GM/GMS/GME, 943/940GML Express
vid/did: 8086/27a6
monitor=vesa vgasize=1400x1050x32
monitor=x60t vgasize=1400x1050x32
Intel X3100/GM965/PM965/GL960
vid/did: 8086/2a03
monitor=vesa vgasize=1680x1050x32
Intel Mobile Intel 4 Series 4500MHD
vid/did: 8086/2a42, 8086/2a43
monitor=vesa vgasize=1440x900x32
monitor=x301 vgasize=1440x900x32
Intel HD 3rd Gen Core processor Graphics Controller
vid/did: 8086/0166
monitor=vesa vgasize=1366x768x32
monitor=x230 vgasize=1366x768x32
NVidia GeForce FX Go5200 64M
vid/did: 10de/0324
monitor=cinema vgasize=1152x768x32
S3 SuperSavage IX/C 16MB
vid/did: 5333/8c2e
monitor=t23 vgasize=1024x768x32
monitor=vesa vgasize=1024x768x32
56
3.2.2.3 − PCI Express
NVidia GeForce 6200 LE
vid/did: 10de/0163
monitor=e228wfp vgasize=1680x1050x32
NVidia GeForce 8400 GS
vid/did: 10de/0422
monitor=vesa vgasize=1680x1050x32
NVidia GeForce 8600 GT
vid/did: 10de/0402
monitor=vesa vgasize=1600x1200x32
NVidia GeForce GTX 550
vid/did: 10de/0bee
monitor=vesa vgasize=1600x1200x32
3.2.3 − Networking
3.2.3.1 − Ethernet
3.2.3.1.1 − Integrated
Broadcom BCM5751M NetXtreme Gigabit
vid/did: 14e4/167d
tested 100/1000 mbps
Broadcom BCM5755/5780 NetXtreme Gigabit
vid/did: 14e4/167b
tested 100/1000 mbps
Broadcom BCM5782 NetXtreme Gigabit
vid/did: 14e4/1696
57
Intel 82540EP Gigabit
vid/did: 8086/101e
tested 100/1000 mbps
Intel 82562ET
tested 10/100 mbps
Intel 82566MM Gigabit
vid/did: 8086/1049
tested 100/1000 mbps
Intel 82567LM 82567LM−2 Gigabit
vid/did: 8086/10f5
tested 100/1000 mbps
Intel 82573L Gigabit
vid/did: 8086/109a
tested: 100/1000 mbps
Intel 82579LM Gigabit
vid/did: 8086/1502
tested: 100/1000 mbps
Intel 82801CAM PRO/100 VE
vid/did: 8086/1031
tested 10/100 mbps
Realtek RTL8139
vid/did: 10ec/8139
tested 10/100/1000 mbps
Realtek RTL8169/RTL8101E/RTL8102E
vid/did: 10ec/8136
tested 10/100/1000 mbps
3.2.3.1.2 − USB
58
Beceem Communications CLEAR Stick
vid/did 198f:8160
This is a WiMAX device that appears as a USB CDC Ethernet device
Works with nusb/ether
RNDIS
Android phones should work
Works with nusb/ether
3.2.3.1.3 − PCMCIA
3Com 3c589c
Set the following in plan9.ini: irq=3 port=0x300
3.2.3.2 − WiFi
3.2.3.2.1 − Bridge (external)
Iogear GWU627
802.11n
connect ethernet port to GWU627
HTTP management interface requires Javascript. Managed to program it using
Infernos charon browser, which supports ecmascript 1.0.
Vonets VAP11G
802.11g
connect ethernet port to VAP11G
Requires a proprietary Windows program (ships with the device) to program its set&shy;
tings before using it for the first time.
3.2.3.2.2 − Mini−PCI
Actiontec 800MIP
802.11b
often branded Lucent WaveLAN
ether0=type=wavelanpci ssid=MESH station=T42 irq=11
59
Ralink RT2860 802.11b
3.2.3.2.3 − Mini−PCI Express
Intel Centrino Advanced−N 6205 Taylor Peak (iwl−6005)
vid/did: 8086/0085
802.11g
ether0=type=iwl essid=MESH
Intel Centrino Ultimate−N (iwl−6000)
802.11g
ether0=type=iwl essid=MESH
Intel Centrino Wireless−N 100
802.11g
ether0=type=iwl essid=MESH
Intel Centrino Wireless−N 2230
802.11g
ether0=type=iwl essid=MESH
Intel PRO Wireless 3945ABG (wpi−3945abg)
802.11g
ether0=type=wpi essid=MESH
Intel WiFi Link 1000/4965/5100/5300 AGN
802.11g
ether0=type=iwl essid=MESH
Ralink RT3090
802.11g
3.2.3.2.4 − PCI
Ralink RT3090
802.11b
60
3.2.3.2.5 − PCMCIA
Linksys WPC11
802.11b
Prism 2.5
ISL37300P
RevA
Lucent WaveLAN PC24E−H−FC
802.11b
ether0=type=wavelan essid=MESH crypt=off station=x61 irq=11
3.2.4 − Tablet Digitizers
3.2.4.1 − Serial
3.2.4.1.1 − Integrated
Wacom WACF004
ThinkPad X4* series tablets
To enable the tablets serial port in plan9.ini:
uart2=type=isa port=0x200 irq=5
To turn on the tablet:
aux/wacom; aux/tablet &amp;
Wacom WACF008
ThinkPad X6* series tablets
To enable the tablets serial port in plan9.ini:
uart2=type=isa port=0x200 irq=5
To turn on the tablet:
aux/wacom; aux/tablet &amp;
61
3.2.5 − Laptops
3.2.5.1 − Acer
Aspire 5100 (donated by some poor kid)
cpu: 1795MHz AuthenticAMD AMD-K8, works
ethernet: rtl8139 100Mbps, works
keyboard and touchpad, works
graphics:
RS482M
ATI
RADEON
Xpress
Series,
monitor=vesa vgasize=1024x768x32 (native resolution not in VESA
BIOS); radeon driver untested
wifi: Atheros AR5005G, does not work
audio: SB450 High Definition Audio Controller
3.2.5.2 − IBM/Lenovo
62
3.2.5.2.1 − ThinkPad
380D
2635−3AU
cpu: cpu0: 152MHz GenuineIntel P55C MMX (AX 00000543 CX 00000000 DX
008001BF)
graphics:
Neomagic
MagicGraph
128ZV
monitor=vga vgasize=800x600x16
ethernet: 3Com 3C589 PCMCIA, works
63
R400
7439−1DG
cpu: 2527MHz GenuineIntel Core 2/Xeon (cpuid: AX 0x10676 CX 0x8E3FD DX
0xBFEBFBFF)
graphics:
Mobile
Intel
GM45
Express/4500MHD,
realemu(8)
monitor=vesa vgasize=1440x900x32
ethernet: Intel 82567LM 82567LM-2 Gigabit (10/100/1000), works
wifi: Intel Wifi Link 5100 AGN Mini-PCI Express, works
disk controller: Intel ICH9M/ME ICH9M/ME AHCI, works
dvd: MATSHITADVD-RAM UJ870A SB04 HE34 068E34 068597, works
audio: Intel 486486 82801IB/IR/IH HD Audio, works
usb: works
mp: mp + sata, ethernet works with *acpi=1
T23
2647−HSU
cpu: Intel Mobile Pentium III-M 866 MHz, 1.2 GHz
graphics: S3 SuperSavage IX/C 16MB, VGA 1024x768x32, realemu(8)
monitor=vesa vgasize=1024x768x32
ethernet: Intel 82801CAM PRO/100 VE or Intel 82562ET (10/100), works
wifi: Actiontec 800MIP (branded Lucent WaveLAN) Mini-PCI, works
audio: AC97, works
64
T42
2373−BK4
cpu: Intel Pentium M (Dothan) 1.7 GHz
graphics:
ATI
Mobility
Radeon
7500
32MB,
realemu(8)
monitor=vesa vgasize=1024x768x32
ethernet: Intel Gigabit Ethernet (10/100/1000), works
wifi: IBM 11a/b/g Mini-PCI, does not work; replaced with Actiontec 800MIP
(branded Lucent WaveLAN) Mini-PCI, works
disk controller: 82801DBM (ICH4-M), IDE DMA works
audio: AC97, works
T43p
2669−A92
cpu: Intel Pentium M (Dothan) 2.0 GHz (cpuid: AX 0x06D8 CX 0x0180 DX
0xAFE9FBFF)
graphics:
ATI
Mobility
Radeon
FireGL
V3200/X600,
realemu(8)
monitor=vesa vgasize=1600x1200x32 with internal LCD
ethernet: Broadcom BCM5751M (10/100/1000), works
wifi: replaced with Vonets VAP11G, works
disk controller: Intel 82801FBM SATA AHCI (ICH6-M): untested
usb: works
scram works with *acpi=1
mouse button 2 works with trackpad disabled in BIOS
T60p
2007−94U
cpu: Intel Core Duo (Yonah) 2.16GHz (cpuid: AX 0x06E8 CX 0xC1A9 DX
0xBFE9FBFF)
graphics:
ATI
MOBILITY
FireGL
V5200
realemu(8)
monitor=vesa vgasize=1600x1200x32 with internal LCD
audio: Intel BA101897 IDT High Definition, untested
ethernet: Intel 82573L Intel PRO/1000 PL (10/100/1000), works
wifi: Intel PRO Wireless 3945ABG (wpi-3945abg), may work now with wpi driver
disk controller: Intel 82801GB/GBM PATA100, 82801GBM/GHM AHCI, works
usb: works
mp: mp + sata, ethernet, usb works with *acpi=
mouse button 2 works with trackpad disabled in BIOS
T61
7659−CTO
cpu: Intel Core 2 Duo (Merom) 2.0 GHz FSB, 2-4MB L2 Cache CPU
graphics:
Intel
GMA
X3100,
realemu(8)
monitor=vesa vgasize=1280x800x32
with
internal
LCD;
monitor=vesa vgasize=1680x1050x32 with VGA or Mini Doc DVI output
and external monitor
65
ethernet: Intel 82566MM (10/100/1000), works
wifi: Intel Wireless WiFi Link 4965 AGN Mini-PCI Express, should work with iwl
driver
disk controller: Intel 82801HBM/HEM PATA, Intel 82801HBM SATA AHCI (ICH8-M):
IDE DMA works, SATA works
usb: works
mp: mp + sata, ethernet, usb works with *acpi=
mouse button 2 works with trackpad disabled in BIOS
7661−12U
cpu: Intel Core 2 Duo (Merom) 2.0 GHz FSB, 2-4MB L2 Cache CPU
graphics:
Intel
GMA
X3100,
realemu(8)
monitor=vesa vgasize=1280x800x32
with
internal
LCD;
monitor=vesa vgasize=1680x1050x32 with VGA or Mini Doc DVI output
and external monitor
ethernet: Intel 82566MM (10/100/1000), works
wifi: Intel PRO Wireless 3945ABG (wpi-3945abg), may work now with wpi driver;
replaced with Wavelan PC24E-H-FC PCMCIA, works
disk controller: Intel 82801HBM/HEM PATA, Intel 82801HBM SATA AHCI (ICH8-M):
IDE DMA works, SATA works
usb: works
mp: mp + sata, ethernet, usb works with *acpi=
mouse button 2 works with trackpad disabled in BIOS
T400
6475−EC7
cpu: 2261MHz GenuineIntel Core 2/Xeon (cpuid: AX 0x10676 CX 0x8E3FD DX
0xBFEBFBFF)
graphics:
Intel
Corporation
Mobile
4
Series,
realemu(8)
monitor=vesa vgasize=1440x900x32 with internal LCD
ethernet: i82567: 1000Mbps, works
wifi: Intel WiFi Link 5100 AGN Mini-PCI Express, works
disk controller: Intel ICH9M/ME AHCI, works
audio: Intel HDA, should work
T410i
2518−4QG
cpu: Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz
graphics:
Intel
Graphics
Media
Accelerator
HD,
monitor=vesa vgasize=1280x800x32 with internal LCD
ethernet: Intel 82577LM Gigabit, works
wifi: unknown, reportedly works
audio: unknown, reportedly works
66
realemu(8)
T420s
4171−53U
cpu: Intel&reg; Core&quot; i5-2540M (2.6GHz, 3MB L3, 1333MHz FSB) (cpuid: AX 000206A7
CX 17BAE3FF DX BFEBFBFF)
graphics: Intel HD Graphics 3000 (integrated Sandy Bridge GPU), realemu(8)
monitor=vesa vgasize=1600x900x32
ethernet: Intel 82579LM Gigabit, works
audio: Intel HD 6 Series/C200 Series, works
wifi: Intel Centrino Advanced-N 6205 Taylor Peak, etheriwl (firmware: iwn-6005),
works
X41 tablet
cpu: Intel Pentium M (Dothan) 1.6GHz LV (778) L2 2 MB cache
graphics:
Intel
GMA900,
monitor=vesa vgasize=1024x768x32
tablet: WACF004, works
ethernet: BCM5751M (10/100/1000), works
wifi: Intel PRO/Wireless 2915ABG Mini-PCI, does not work
realemu(8)
X60s
1704−GL5
coreboot
cpu cpu0: 1663MHz GenuineIntel P6 (cpuid: AX 0x06E8 CX 0xC1A9 DX
0xBFE9FBFF)
graphics:
Intel
945GM,
realemu(8)
monitor=vesa vgasize=1024x768x16
ethernet: Intel 82573L Intel PRO/1000 PL, works
audio: Intel HDA, untested
wifi: Ralink RT3090, works
67
X60 Tablet
6363−CTO
cpu: Intel Core Duo (Yonah) L2400 LV 1.66 GHz (2MB Cache) cpu0: 1663MHz Gen&shy;
uineIntel P6 (AX 000006EC CX 0000C1A9 DX BFE9FBFF)
lcd: replaced with HV121P01-100 (1400x1050)
graphics:
Intel
Graphics
Media
Accelerator
950,
realemu(8)
monitor=x60t vgasize=1400x1050x32;
monitor=vesa vgasize=1280x1024x32 (native 1400x1050 resolution not
in VESA BIOS)
tablet: WACF008, works
ethernet: Intel 82573L (10/100/1000), works
audio: Intel HD Audio with AD1981HD codec, speaker and green lineout work with
echo pin 5,3 &gt;/dev/audioctl
wifi: Intel WiFi Link 5100 AGN, works flashed with custom BIOS to remove WiFi
card whitelist
disk controller: Intel 82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI
mode], untested
mp: mp + sata, ethernet works with *acpi
X61s
cpu: Intel Core 2 Duo
graphics:
Intel
GM965/GL960,
realemu(8)
monitor=vesa vgasize=1024x768x32
ethernet: Intel 82566MM (10/100/1000), works
wifi: Intel PRO/Wireless 4965 AG or AGN [Kedron] Mini-PCI Express, untested,
should work with iwl driver
disk controller: Intel 82801HBM SATA (ICH8-M): IDE DMA works, SATA works
mp: mp + sata, ethernet works with *acpi=
68
X61 Tablet
7767−01U
cpu: Intel Core 2 Duo CPU L7700 (1.80 GHz)
lcd: replaced with HV121P01-100 (1400x1050)
graphics:
Intel
GMA
X3100,
realemu(8)
monitor=x60t vgasize=1400x1050x32;
monitor=vesa vgasize=1280x1024x32 (native 1400x1050 resolution not
in VESA BIOS)
tablet: WACF008, works
ethernet: Intel 82566MM (10/100/1000), works
audio: Intel HDA, works
wifi: Intel Centrino Advanced-N 6205 Taylor Peak (iwl-6005), works flashed
with custom BIOS to remove WiFi card whitelist
disk controller: Intel 82801HBM SATA (ICH8-M): IDE DMA works, SATA works mp:
mp + sata, ethernet works with *acpi=
X131e
3368−2FU
cpu: 1397MHz GenuineIntel P6 (cpuid: AX 0x206A7 CX 0x15BAE3BF DX 0xBFEBF&shy;
BFF)
graphics:
Intel
HD
Graphics
3000,
realemu(8)
monitor=vesa vgasize=1366x768x32
ethernet: Realtek RTL8167 PCIe Gigabit Ethernet: works
audio: Intel HDA, works
69
X200
7455−A54
cpu: Intel Core 2 Duo
graphics:
Mobile
Intel
GMA
4500MHD,
monitor=vesa vgasize=1280x800x32
ethernet: Intel 82567LF Gigabit (10/100/1000), works
wifi: Intel WiFi Link 5150, works
disk controller: Intel ICH9M/ME ICH9M/ME AHCI, works
audio: Intel 486486 82801IB/IR/IH HD Audio, works
usb: works
realemu(8)
X200s
7466−3SG
cpu: 1862MHz GenuineIntel Core 2/Xeon (cpuid: AX 0x10676 CX 0x8E3FD DX
0xBFEBFBFF)
graphics:
Mobile
Intel
GM45
Express/4500,
realemu(8)
monitor=vesa vgasize=1280x800x32
ethernet: Intel 82567LM 82567LM-2 Gigabit (10/100/1000), works
wifi: Intel WiFi Link 5300 AGN Mini-PCI Express, works
disk controller: Intel ICH9M/ME ICH9M/ME AHCI, works
audio: Intel 486486 82801IB/IR/IH HD Audio, works
usb: works
mp: mp + sata, ethernet works with *acpi=1
X201
3323−DBG
cpu: 2661MHz GenuineIntel P6
graphics:
Mobile
Intel
GMA
5700MHD,
realemu(8)
monitor=vesa vgasize=1280x800x32
ethernet: Intel Corporation 82577LM Intel 82577LM Gigabit, works
wifi: Intel Centrino Ultimate-N 6300 AGN, works
disk controller: Intel Corporation PCH (Ibex Peak) SATA AHCI, works
audio: Intel HDA, works
ssd: INTEL SSDSC2BW180A3L, works
usb: works
X220
4291−4CG
cpu: 2791MHz GenuineIntel P6 (cpuid: AX 0x206A7 CX 0x17BAE3FF DX 0xBFEBF&shy;
BFF)
graphics:
Intel
HD
3000,
realemu(8)
monitor=vesa vgasize=1366x768x32
ethernet: Intel 82579 (10/100/1000), works
audio: Intel HDA, works
wifi: Intel Centrino Advanced-N 6205, works
70
disk controller: works
ssd: INTEL SSDSA2BW160G3, works
usb: works
X230
2306−CTO
cpu: Intel Core i5-3320M (2.60 GHz, 3MB L3, 1600MHz FSB), cpuid: AX 0x306A9
CX 0x77BAE3FF DX 0xBFEBFBFF
graphics: Intel HD 3rd Gen Core processor Graphics Controller, realemu(8)
monitor=x230 vgasize=1366x768x32;
monitor=vesa vgasize=1366x768x32
ethernet: Intel 82579LM Gigabit (10/100/1000), works
wifi: Intel Centrino Advanced-N 6205 Taylor Peak, etheriwl (firmware: iwn-6005),
works
disk controller: Intel 7 Series Chipset Family 6-port SATA Controller AHCI mode,
ahci, works
usb: Intel 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1,
ehci, works
audio: Intel 7 Series/C210 Series Chipset Family High Definition Audio Controller,
works
efi: works
71
X230 Tablet
3434−CTO
cpu: Intel Core i5-3320M (Ivy Bridge), 2.6 GHz, 3 MB Shared L3 Cache, 2C/4T, 35
W TDP, 22 nm (cpuid: AX 0x306A9 CX 0x77BAE3FF DX 0xBFEBFBFF)
graphics:
Intel
HD
4000,
realemu(8)
monitor=vesa vgasize=1366x768x32
tablet: USB, untested
ethernet: Intel 82579 (10/100/1000), works
audio: Intel HDA, works
wifi: Intel 802.11b/g/n, might work
disk controller: works
ssd: SAMSUNG SSD 830 Series CXM03B1Q S0XYNEAC774074 128GB, works
usb: disable USB3 in BIOS, works
X250
20CM−CTO
cpu: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, cpuid: AX 000306D4 CX 77FAF&shy;
BBF DX BFEBFBFF
graphics: Intel Corporation Broadwell-U Integrated Graphics, realemu(8)
monitor=vesa vgasize=1920x1080x32
ethernet: Intel Corporation Ethernet Connection (3) I218-LM (10/100/1000), works
wifi: Intel Wireless-N 7265, does not work, but may not be hard to add to existing
etheriwl driver
disk controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode],
works
usb: Intel Corporation Wildcat Point-LP USB EHCI Controller, works
audio: Intel Corporation Broadwell-U Audio Controller, untested
72
X301
2776−P4U
cpu: Intel Core 2 Duo SU9400 1.4GHz 3MB cache, cpuid: AX 0x1067A CX
0x408E3FD DX 0xBFEBFBFF
graphics:
Mobile
Intel
GM45
Express/4500MHD,
realemu(8)
monitor=x301 vgasize=1440x900x32;
monitor=vesa vgasize=1440x900x32
ethernet: Intel 82567LM 82567LM-2 Gigabit (10/100/1000), works
wifi: Intel WiFi Link 5100 AGN Mini-PCI Express, works
disk controller: Intel ICH9M/ME ICH9M/ME AHCI, works
ssd: Samsung MMCRE64G8MPP-0VA 64GB, works
dvd: Matsushita DVD-RAM UJ-844, works
audio: Intel HD 486486 82801IB/IR/IH, works
usb: works
mp: mp + sata, ethernet works with *acpi=1
2776−P6U
cpu: Intel Core 2 Duo SU9400 1.4GHz 3MB cache, cpuid: AX 00010676 CX
0008E3FD DX BFEBFBFF
graphics:
Mobile
Intel
GM45
Express/4500MHD,
realemu(8)
monitor=x301 vgasize=1440x900x32;
monitor=vesa vgasize=1440x900x32
ethernet: Intel 82567LM Gigabit (10/100/1000), works
wifi: Intel WiFi Link 5100 AGN Mini-PCI Express, works
disk controller: 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller AHCI
mode, works
audio: Intel HD 82801I (ICH9 Family), works
usb: works
mp: mp + sata, ethernet works with *acpi=1
73
3.2.5.3 − Toshiba
3.2.5.3.1 − Satellite
M30−S309
cpu: 1397MHz GenuineIntel P6 (AX 00000695 CX 00000180 DX A7E9F9BF)
graphics:
NVidia
GeForce
FX
Go5200
64M,
monitor=cinema vgasize=1152x768x32
ethernet: Intel 82801DB PRO/100 VE (MOB) (i82557), works
disk controller: Intel 82801DBM (ICH4-M) IDE Controller, works
audio: Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC97 Audio Controller,
works
usb: Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller,
untested
3.2.6 − Desktops
74
3.2.6.1 − eMachines
T3302 cpu: AMD Sempron 3300+ 2GHz
chipset: VIA K8M800
graphics: VIA S3 UniChrome, replaced with NVidia GeoForce FX 5700 128MB DVI output,
1920x1080x32
ethernet: 3Com 3C905-TX Fast Etherlink 10/100 PCI TX
audio:
usb: works
3.2.6.2 − Igel
4210 LX Winestra
3.2.6.3 − Soekris
net6501−70
cpu: Intel Atom E680 1.6Ghz, both pc and pc64 work
ethernet: 4x Intel 82574L Gigabit Ethernet, works
usb: works
serial console: works, use console=0 b19200 in plan9.ini. 9boot hangs
without a serial cable attached; disable uartputc as a workaround
this machine does not have ACPI
3.2.6.4 − IBM/Lenovo
75
3.2.6.4.1 − ThinkCentre
M55
8810−D3U
cpu: Intel Core 2 Duo
graphics: Intel GMA 3000 internal (untested), replaced with NVidia GeForce 8400GS
DVI output, realemu(8) monitor=vesa vgasize=1680x1050x32
ethernet: Broadcom BCM5755 (10/100/1000), works
audio: Intel HDA, works
usb: works
mp: mp + sata, ethernet, usb works with *acpi=
3.3 − Virtual Machines
9front has been tested on several virtual machines. Details below.
Note: As a general rule it is a good idea to manually specify a unique MAC address for
each virtual machine instance running on the network, to avoid collisions.
3.3.1 − Qemu
The following is tested with qemu 1.5.0 and 2.0.50 running on Linux, using FQA 3.3.3 −
virtio for disk and network.
3.3.1.1 − Installation
Create a sparse disk image:
qemu−img create −f qcow2 9front.qcow2.img 30G
Boot the 9front.iso:
qemu−system−x86_64 −cpu host −enable−kvm −m 1024 \
−net nic,model=virtio,macaddr=52:54:00:00:EE:03 −net user \
−device virtio−scsi−pci,id=scsi \
−drive if=none,id=vd0,file=9front.qcow2.img −device scsi−hd,drive=vd0 \
−drive if=none,id=vd1,file=9front.iso −device scsi−cd,drive=vd1,bootindex=0
Finally, see: FQA 4.3 − Performing a simple install
3.3.1.2 − Post−Installation Booting
qemu−system−x86_64 −cpu host −enable−kvm −m 1024 \
−net nic,model=virtio,macaddr=52:54:00:00:EE:03 −net user \
−device virtio−scsi−pci,id=scsi \
−drive if=none,id=vd0,file=9front.qcow2.img −device scsi−hd,drive=vd0
76
3.3.1.2.1 − Multiboot
Multiboot can be used to start the 9front kernel directly, skipping the bootloader step:
−qemu −kernel 9pcf −initrd plan9.ini
3.3.1.4 − Networking
User networking is the default and works the same on every platform. More advanced
options are particular to specific host operating systems; several are described below.
Note: On many operating systems ICMP is limited to the superuser. One consequence is
that a VM running with guest networking cannot ping remote hosts.
3.3.1.4.1 − Linux VDE
Install vde2.
Setup a tap interface:
sudo tunctl −u $USER −t tap0
Start a virtual switch connected to the tap interface:
vde_switch −−tap tap0 −daemon
Connect the switch to the network of the host. Use DHCP:
slirpvde −−dhcp −−daemon
When booting 9front, add the following to the qemu command line arguments:
−net vde
3.3.1.4.2 − OpenBSD tun(4)
Tested: OpenBSD/amd64 4.9-CURRENT, qemu-0.9.1p18, kqemu-1.3.0pre11p3
Configure a tun(4) interface with an IP address selected for your qemu network.
Configure bridging between the tun(4) interface and your machines external
interface. Finally, configure NAT or rules to pass traffic for the qemu network in
pf.conf. Reboot.
To launch qemu as a regular user:
sudo
−net
−net
−hda
sh −c &quot;sudo −C 4 −u $USER qemu −m 768 \
nic,vlan=0,model=rtl8139,macaddr=52:54:00:12:33.36 \
tap,vlan=0,fd=3,script=no −no−fd−bootchk \
9front.qcow2.img 3&lt;&gt;/dev/tun0&quot;
Read: hostname.if(5), pf.conf(5), tun(4)
77
3.3.1.4.3 − Windows TAP
This is tested with the qemu for windows distribution. Download and run the installer
from openvpn to install the windows TAP driver. Create a new TAP interface with the
&quot;Add a new TAP virtual ethernet adapter&quot; from the openvpn start menu. Go to the net&shy;
work manager and rename that new TAP interface to something more sane like: &quot;qemutap&quot;. Configure ip addresses or bridge that interface with the network manager.
Now you should be able to run qemu on that interface:
qemu.exe −net nic −net tap,ifname=&quot;tap−qemu&quot; ...
3.3.1.5 − Audio
Run qemu with the flag
plan9.ini:
−soundhw
sb16 and put the following line in
audio0=type=sb16 port=0x220 irq=5 dma=5
Note: irq and dma values may vary.
3.3.1.6 − Graphics
Use monitor=vesa
Note: Some versions of QEMU running on OSX have exhibited graphical glitches when
using a 16-bit color mode (for example: 1024x768x16. Try a 32-bit mode instead (for
example: 1024x768x32).
3.3.2 − Virtualbox
Dont use Virtualbox. It tends to break between versions.
78
Read: http://www.landley.net/notes−2015.html#25−06−2015
If you cant be dissuaded, the following sections detail empircal observations re:
Virtualbox.
3.3.2.1 − Ethernet The emulated &quot;Intel PRO/1000 MT Server&quot; ethernet controller is
known to work.
3.3.2.2 − Audio
Put the following in plan9.ini:
audio0=type=sb16
3.3.2.3 − Graphics Use monitor=vesa
3.3.2.4 − Known Working Versions
4.3.14 r95030 on Windows 7
4.3.16 on Mac OS X
4.3.18 r96516 on Linux x86_64 kernel 3.14.22
4.3.18 on Windows 7:
just tried with vbox 4.3.18 on windows7. 9front boots fine in BIOS mode, but
the PCnet nic dosnt work. reason is that vbox pIIx pci irq routing is fucked so
the ethernet doesnt get interrupts. if i boot with *nopcirouting=1, it works
fine. theres a option to select the chipset so i tried ICH9 with IO-APIC
79
enabled. normal mp mode fails because of broken mp tables, but works with
*acpi=. also, it works with UEFI mode (which always uses ACPI). the usual
intel mt server nic also works (thats what is usually recommended for working
arround the broken ethernet).
pci routing issue has been fixed in latest kernel, should be available in iso
release after 3960.
4.3.20 r96996 on Mac OS X 10.6.8/10.9 and Ubuntu 14.04/14.10:
General -&gt; Basic Type: Other Version: Other/Uknown
System -&gt; Motherboard Chipset: PIIX3 Pointing Device: PS/2 Mouse Extended
Features: [x] Enable I/O APIC
System -&gt; Processor Extended Features: [x] PAE/NX (not sure this matters)
System -&gt; Acceleration [x] Enable VT-x/AMD-V [x] Enable Nested Paging
Display -&gt; Video Extended Features: [x] Enable 3D Acceleration (not sure this
matters)
Storage -&gt; Attributes Name: IDE Type: PIIX4 [x] Use Host I/O Cache
Audio -&gt; [x] Enable Audio Host Audio Driver: CoreAudio (Can be PulseAudio
or otherwise for Linux, etc. Shouldnt be hard to set this) Audio Controller:
Soundblaster 16
Network -&gt; Adapter 1 Attached to: NAT -&gt; Advanced Adapter Type: Intel
PRO/1000 MT Server Promiscuous Mode: Deny (Not sure this matters)
Note: Enabling USB 2.0 Controll in Ports -&gt; USB works just fine in 9front,
mounting under /shr flawlessly as long as the host has the Virtualbox Exten&shy;
sion Pack running.
80
3.3.3 − Virtio
Current versions of qemu/kvm and virtualbox as of 3.1 support faster paravirtualized
devices. Presently, 9front provides drivers for virtio hard disk and network.
The virtio-blk disk device should show up as: /dev/sdF0
The virtio-scsi disk device should show up as: /dev/sd00
81
FQA 4 − 9front Installation Guide
ACHTUNG! This document (and the 9front installer) pertains only to the 386 install tar&shy;
get. For other architectures, read: 8.9 - Bootstrapping architectures not included on the
ISO
82
4.1 − Pre−installation Checklist
Before you start your install, you should have some idea what you want to end up with.
You will want to know the following items, at least:
Machine name, hereafter referred to as sysname.
Hardware installed and available. Read: FQA 3.3 − Selecting Hardware. Check
FQA 3.2 − Known Working Hardware as well as the various supported hardware
pages on the Bell Labs Plan 9 wiki to help determine if your hardware or VM is
supported.
Network settings, if not using DHCP: Gather the requisite information for your
network (IP, netmask, default gateway, etc.). If you plan to install in a VM, see FQA
3.3 − Virtual Machines.
In case of trouble, see: FQA 9 − Troubleshooting, FQA 2.2.1 − Mailing List Archives
4.2 − Creating bootable 9front install media
4.2.1 − ISO image
Obtain the 9front.iso.
Read: 1.11.1 − Mirrors
83
4.2.2 − USB drive
Booting from USB disk is handled the same way as booting from internal hard drive. In
general, the boot process is able to use an ISO image stored on a FAT file system as its
root file system, so all that is needed is to install the 9boot(8) bootloader, a kernel
and the 9front.iso on the USB disk.
4.2.2.1 − Creating on Plan 9
The path to your USB device will look something like this: /dev/sdUxxxxx where
xxxxx is the unique name of your usb device.
Build and install the mbr and boot loader:
cd /sys/src/boot/pc
mk 9bootfat mbr pbs
disk/mbr −m mbr /dev/sdUxxxxx/data
If it doesnt already exist, create and format a FAT partition. Dont forget to set the FAT
partition active in the fdisk menu:
disk/fdisk −b /dev/sdUxxxxx/data
disk/format −b pbs −d −r 2 /dev/sdUxxxxx/dos
Mount the USB device:
dossrv −f /dev/sdUxxxxx/dos sdos
mount −c /srv/sdos /n/dos
Create a suitable /n/dos/plan9.ini:
bootfile=9pcf
mouseport=ask
monitor=ask
vgasize=ask
Note: By convention, Plan 9 usually expects text files to end with a newline. If the last
line of plan9.ini is not a newline, it could fail to be parsed correctly at boot time.
Copy files to the USB device:
cp /386/9bootfat /n/dos
chmod +al /n/dos/9bootfat # defrag magic
cp /386/9pcf /n/dos
cp /path/to/9front.iso /n/dos
Optional for EFI systems:
cd /sys/src/boot/efi; mk install
mkdir −p /n/dos/efi/boot
cp /386/boot*.efi /n/dos/efi/boot
Unmount the USB device:
84
unmount /n/dos
rm −f /srv/sdos
Boot the device.
Read: prep(8)
4.2.2.2 − Creating on Linux
Note: There are numerous methods for creating bootable USB devices on Linux. This is
one.
Obtain mbr, pbs, 9bootfat and 9pcf binaries. Either copy them from the dis&shy;
tributed ISO image (the files are located under /386/) or build up to date binaries on a
9front system. Read: FQA 5.2.2 − Building from source
On the Linux system, create a $dir with that contains the following files:
9front.iso
9pcf
plan9.ini (as described above)
9bootfat
mbr
pbs
Optional for EFI systems, create the directory boot in $dir and copy the files
bootia32.efi and bootx64.efi into it.
Use the makebootfat tool to create bootable device (ie. /dev/sdc):
$ makebootfat −m $dir/mbr −b $dir/pbs −o /dev/sdc $dir
Boot the device.
4.2.2.3 − Bootargs
At the bootargs prompt youll need to enter the path to the ISO on the USB device. It will
look something like this:
bootargs=local!/shr/sdUxxxxx/9front.iso
If a USB device is not listed, escape to a shell with !rc, and ls /shr to find it.
Read: 9.5.1 - Devices not recognized or not working
4.3 − Performing a simple install
There is nothing magical about installing Plan 9. It is simply a matter of populating a
Plan 9 file system ( cwfs or hjfs ) and arranging a bootstrap to eventually load a Plan
9 kernel that can then use that file system as its root.
In most cases, the file server is the only machine that needs to have a disk. Once the
85
initial file server is running, setting up an auth server, and enabling bootp and tftp
for PXE booting, will allow Plan 9 terminals and cpu servers to load kernels from the file
server and share its file system over the network.
Note: This guide describes the default installation of a terminal with disk, which is an
amalgamation of a normal Plan 9 network, but is sufficient for exploring the basics of
using Plan 9. Configuration of additional services (such as a file server with networking
listeners, a cpu server, etc.) is outlined in FQA 7 − System Management.
To install 9front, boot the 9front.iso image and follow the steps below.
4.3.1 − boot
Successfully booting the system will result in basic information about the state of the
system being printed on screen:
Plan 9
126 holes free
00018000 0009f000 552960
00485000 0cf2c000 212496384
213049344 bytes free
cpu0: 3395MHz GenuineIntel P6 (cpuid: AX 0x206A7 CX 0x82982203 DX 0xFEBFBFF)
ELCR: 0E20
#l0: AMD79C970: 10Mbps port 0x2000 irq 10: 000c291d0baf
mylex ctlr @ port 0x10c0: 32−bit wide SCSI host adapter
512M memory: 207M kernel data, 304M user, 929M swap
nusb/usbd: /dev/usb: no hubs
4.3.2 − bootargs
A list of attached storage devices is printed, followed by a prompt asking for a Plan 9
partition to boot from:
/dev/sdC0: VMware Virtual IDE Hard Drive
/dev/sdC0/data
/dev/sdD0: VMware Virtual IDE CDROM Drive
/dev/sdD0/data 9660
bootargs is (tcp, il, local!device) [local!/dev/sdD0/data]
In most cases, the suggested default will correspond to the device used to boot the ISO
image.
4.3.3 − user
Next, a prompt asks for a username:
user[glenda]:
Glenda is the default hostowner name. Dont change this until you know what you are
doing. Hit enter to accept the default.
Note: The hostowner differs from the concept of root on a UNIX system, where a
single user root may take control of all processes and files on the system. By contrast,
86
even the hostowner of a Plan 9 file server cannot violate file permissions on the file
system, except when permissions checking is disabled on the console or when entering
special commands at the console of the file server. The hostowner controls only the
processes running on the local machine (in the case of the filserver, the file server pro&shy;
cess itself is obviously owned by the systems hostowner). This fundamental separa&shy;
tion between control of processes and file permissions is exploited throughout the sys&shy;
tem, but can be confusing for users coming from a UNIX background.
4.3.4 − vgasize, monitor, mouseport
The next set of prompts deal with graphics display and the mouse:
vgasize is (text, 640x480x8, 1024x768x16, ...) [1024x768x16]
monitor is (vesa, xga, lcd, ...) [vesa]
mouseport is (ps2, ps2intellimouse, 0, 1, 2) [ps2]
The boot process prompts for the environment variables $vgasize, $monitor and
$mouseport, and the installer will later write those values to the systems
plan9.ini, from which they are loaded on subsequent system bootup.
Setting $monitor to anything besides vesa will bypass the emulated VESA BIOS and
attempt to use a native VGA driver for the video card in question. Read: /lib/vgadb
for a list of monitors and video cards that are already known by the system; and the man
pages vga(3), vga(8) and vgadb(6) for more information about how graphical
displays are configured.
The default $mouseport of ps2 is sufficient in most cases.
ps2intellimouse on laptops or for mice that have a scrollwheel.
Set
it
to
Note: Some laptops require the trackpad to be disabled in the BIOS in order for mouse
button 2 (the center button) to function in Plan 9. In a pinch, mouse button 2 may be
simulated by holding down the shift key while clicking mouse button 3 (the right but&shy;
ton).
After the install, changes intended to persist across reboots should be added to
plan9.ini.
Examples:
Values as they appear in plan9.ini:
monitor=vesa
vgasize=1024x768x16
mouseport=ps2intellimouse
Read: mouse(8), vga(3), vgadb(6), plan9.ini(8), realemu(8), vga(8),
FQA 7.2.2 − How do I modify plan9.ini?
After the mouseport prompt is answered, the boot process will attempt to start the
Plan 9 graphical environment, rio(1), opening a stats(8) window and a rio
window on top of a gray desktop background.
87
4.3.4.1 − Changing screen resolution
At this point it may be desireable to change the screen resolution. To change video
mode from the command line:
vesa:
Note: Only valid modes listed in the VESA BIOS may be used.
@{rfork n; aux/realemu; aux/vga −p} # obtain a list of vesa bios modes
@{rfork n; aux/realemu; aux/vga −m vesa −l 1024x768x16} # configure one of the v
vga:
aux/vga −m dellst2210 −l 1920x1080x32
4.3.5 − inst/start
Installation is performed by the rc scripts in /rc/bin/inst. To begin the installa&shy;
tion, type inst/start in the terminal window. Follow the prompts to complete the
installation, selecting the defaults where appropriate.
Note: Any task may be repeated by manually entering its name at the next Task to
do prompt.
term% inst/start
Tue Jul 17 12:38:50 CET 2012 Installation process started
The following Task to do steps are handled one at a time:
88
4.3.6 − configfs
You can install the following types of systems:
cwfs64x
hjfs
the cached−worm file server
the new 9front file server (experimental!)
File system (cwfs64x, hjfs)[cwfs64x]:
Note: The cwfs64x file server uses 16KB blocks, with its cache and permanent storage
locate on separate partitions. The hjfs file server uses 4KB blocks, with its cache and
permanent storage located on the same partition. If you are installing to a disk of less
than 12GB, you should choose hjfs.
Read: FQA 3.3 − What is an appropriate first system to learn 9front on?
In this example we will press enter to accept cwfs64x as the default.
4.3.7 − partdisk
The following disk devices were found.
sdC0 − VMware Virtual IDE Hard Drive
empty
0 3916
(3916 cylinders, 29.99 GB)
sdD0 − VMware Virtual IDE CDROM Drive
Disk to partition (sdC0, sdD0)[no default]:
Enter the media you wish to install to.
Disk to partition (sdC0, sdD0)[no default]: sdC0
The disk you selected HAS NO master boot record on its first sector.
(Perhaps it is a completely blank disk.)
Shall we create a blank EFI partition table (GPT)
or install traditional DOS partition table (MBR)?
Assuming a blank disk image, install a fresh mbr:
Install mbr or gpt (mbr, gpt)[no default]: mbr
This is disk/fdisk; use it to create a Plan 9 partition.
If there is enough room, a Plan 9 partition will be
suggested; you can probably just type ’w’ and then ’q’.
cylinder = 8225280 bytes
&gt;&gt;&gt;
For this example we will use the entire disk. Accept the defaults.
&gt;&gt;&gt; w
&gt;&gt;&gt; q
89
4.3.8 − prepdisk
The following Plan 9 disk partitions were found.
/dev/sdC0/plan9
empty
0 62910477
(62910477 sectors, 29.99 GB)
Plan 9 partition to subdivide (/dev/sdC0/plan9)[/dev/sdC0/plan9]:
Use the Plan 9 partition created in the previous step. Hit enter to select the default.
This is disk/prep; use it to subdivide the Plan 9 partition.
If it is not yet subdivided, a sensible layout will be suggested;
you can probably just type ’w’ and then ’q’.
no plan9 partition table found
9fat 204800
nvram 1
other 8957953
fscache 8957953
fsworm 44789770
&gt;&gt;&gt;
Again, accept the defaults.
&gt;&gt;&gt; w
&gt;&gt;&gt; q
4.3.9 − mountfs
The please choose your cwfs64x partitions
Hit enter to select each partition at the prompt.
−−rw−r−−−−− S 0 glenda glenda 4586471936 Jul
4 13:28 /dev/sdC0/fscache
Cwfs cache partition (/dev/sdC0/fscache)[/dev/sdC0/fscache]:
−−rw−r−−−−− S 0 glenda glenda 22932362240 Jul 4 13:28 /dev/sdC0/fsworm
Cwfs worm partition (/dev/sdC0/fsworm)[/dev/sdC0/fsworm]:
−−rw−r−−−−− S 0 glenda glenda 4586471936 Jul 4 13:28 /dev/sdC0/other
Cwfs other partition (/dev/sdC0/other)[/dev/sdC0/other]:
Since this is a fresh install, we choose yes to ream (format) the file system:
90
Ream the file system? (yes, no)[no]: yes
Starting cwfs64x file server for /dev/sdC0/fscache
Reaming file system
bad nvram key
bad authentication id
bad authentication domain
nvrcheck: can’t read nvram
config: config: config: auth is now disabled
config: config: config: config: config: config: current fs is &quot;main&quot;
cmd_users: cannot access /adm/users
63−bit cwfs as of Wed Jul 4 00:59:30 2012
last boot Tue Jul 17 13:34:57 2012
Configuering cwfs64x file server for /dev/sdC0/fscache
Mounting cwfs64x file server for /dev/sdC0/fscache
% mount −c /srv/cwfs /n/newfs
Mounting cwfs64x file server for /dev/sdC0/other
% mount −c /srv/cwfs /n/other other
4.3.10 − configdist
Are you going to download the distribution
from the internet or do you have it on local media?
Distribution is from (local, net)[local]:
We are installing from local media, so, local. Hit enter to accept the default.
Note: The net option attempts to download the ISO from the Internet and install it
directly to disk. Since the installer is most likely already running from an ISO image, this
option may prove to be of limited utility. The option is somewhat experimental, and may
work. Attempt it at your own risk.
4.3.11 − confignet
You can connect to the internet via
a local ethernet or a dial−up PPP connection.
Interface to use (ether, ppp)[ether]:
Please choose a method for configuring your ethernet connection.
manual − specify IP address, network mask, gateway IP address
dhcp − use DHCP to automatically configure
Configuration method (manual, dhcp)[dhcp]:
4.3.11.1 − dhcp
Hit enter to move on to the next task.
91
4.3.11.2 − manual
If you chose manual, enter values that are appropriate for your network.
Configuration method (manual, dhcp)[dhcp]: manual
ip address [no default]: 10.0.2.15
network mask [no default]: 255.255.255.0
gateway address [no default]: 10.0.2.2
4.3.12 − mountdist
Please wait... Scanning storage devices...
/dev/sdC0/9fat
/dev/sdC0/data
/dev/sdC0/fscache
/dev/sdC0/fsworm
/dev/sdC0/other
/dev/sdD0/data
The following storage media were detected.
Choose the one containing the distribution.
/dev/sdD0/data (iso9660 cdrom)
Distribution disk (/dev/sdD0/data, /dev/sdC0/fscache, /)[/]:
The CD-ROM is already mounted at /, so we hit enter to choose the default.
% mount /srv/boot /n/distmedia
Which directory contains the distribution?
Any of the following will suffice (in order of preference):
− the root directory of the cd image
− the directory containing 9front.iso
− the directory containing 9front.iso.bz2
Location of archives [/]:
And again, the root directory of the CD-ROM is already mounted at /, so hit enter to
choose the default.
% mount /srv/boot /n/distmedia
Which directory contains the distribution?
Any of the following will suffice (in order of preference):
− the root directory of the cd image
− the directory containing 9front.iso
− the directory containing 9front.iso.bz2
Location of archives [/]:
Hit enter.
92
4.3.13 − copydist Hit enter at the copydist prompt to begin the process of copying
the distribution files from the install media to the hard disk.
processing /sys/lib/sysconfig/proto/allproto
ACHTUNG! Currently, there is no progress meter. For systems without DMA, the
copydist task may exceed one hour in duration. Disk activity may be verified by
inspecting the stats(8) window.
Eventually, you should see the following:
file system made
93
This indicates that the system files have completed copying to the install target.
4.3.14 − sysname
Setup network configuration
sysname [cirno]:
Use a system name of your choice, or just hit enter to select the default.
4.3.15 − tzsetup
Setup Time Zone
Time Zone (Argentina, Australia_ACT, Australia_Broken−Hill,
Australia_LHI, Australia_NSW, Australia_North, Australia_Queensland,
Australia_South, Australia_Sturt, Australia_Tasmania,
Australia_Victoria, Australia_West, Australia_Yancowinna, Brazil_Acre,
Brazil_DeNoronha, Brazil_East, Brazil_West, CET, Canada_Atlantic,
Canada_Central, Canada_East−Saskatchewan, Canada_Eastern,
Canada_Mountain, Canada_Newfoundland, Canada_Pacific, Canada_Yukon,
Chile_Continental, Chile_EasterIsland, Cuba, EET, Egypt, GB−Eire, GMT,
HST, Hongkong, Iceland, Iran, Israel, Jamaica, Japan, Libya,
Mexico_BajaNorte, Mexico_BajaSur, Mexico_General, NZ, NZ_CHAT, Navajo,
PRC, Poland, ROC, ROK, Singapore, Turkey, US_Alaska, US_Arizona,
US_Central, US_East−Indiana, US_Eastern, US_Hawaii, US_Michigan,
US_Mountain, US_Pacific, US_Yukon, W−SU, WET)[US_Eastern]:
Daylight saving time (DST) is handled automatically. Type your chosen time zone and hit
enter.
4.3.16 − bootsetup
Setup Plan 9 FAT boot partition (9fat)
Plan 9 FAT partition (/dev/sdC0/9fat)[/dev/sdC0/9fat]:
Hit enter to accept the default. Any environment variables entered at the &gt; prompt
during boot, as well as settings configured during install will now be written to
/n/9fat/plan9.ini and the kernel will be copied to the 9fat partition.
94
dossrv: serving #s/dos
Initializing Plan 9 FAT partition.
% disk/format −r 2 −d −b /386/pbs /dev/sdC0/9fat
Initializing FAT file system
type hard, 12 tracks, 255 heads, 63 sectors/track, 512 bytes/sec
used 4096 bytes
% mount −c /srv/dos /n/9fat /dev/sdC0/9fat
% rm −f /n/9fat/9bootfat /n/9fat/plan9.ini /n/9fat/9pcf
% cp /n/newfs/386/9bootfat /n/9fat/9bootfat
% chmod +al /n/9fat/9bootfat
% cp /tmp/plan9.ini /n/9fat/plan9.ini
% cp /n/newfs/386/9pcf /n/9fat/9pcf
If you use the Windows NT/2000/XP master boot record
or a master boot record from a Unix clone (e.g., LILO or
FreeBSD bootmgr), it is probably safe to continue using
that boot record rather than install the Plan 9 boot record.
Since we are not installing on a disk with a pre-existing Windows installation, we choose
to install the Plan 9 master boot record and mark the partition active:
Install the Plan 9 master boot record (y, n)[no default]: y
Mark the Plan 9 partition active (y, n)[no default]: y
The Plan 9 partition is now marked as active.
4.3.17 − finish
The final task is to remove (or disable) the CD-ROM and finish by hitting enter to
reboot the machine.
Congratulations, youve just installed a 9front system!
Now your cat goes to sleep on the keyboard.
95
4.4 − Encrypted Partitions
9front supports booting from encrypted fsworm, fscache and other partitions.
The following assumes a hard drive /dev/sdC0:
&quot; Begin the installation process as normal by booting 9front.iso.
&quot; During partdisk and prepdisk, create the fsworm, fscache and other
partitions as normal.
&quot; At the mountfs prompt, enter !rc to drop to a shell prompt.
&quot; Format and activate the encrypted partitions (generates new encryption key):
96
cryptsetup −f /dev/sdC0/fsworm /dev/sdC0/fscache /dev/sdC0/other
cryptsetup −i /dev/sdC0/fsworm /dev/sdC0/fscache /dev/sdC0/other
&quot; Type exit to resume the installation.
&quot; During mountfs, select the partitions under /dev/fs instead of the ones under
/dev/sdC0.
&quot; During the rest of the installation, select the defaults, where appropriate.
&quot; During post-installation boot, at the bootargs prompt, type !rc to drop to a shell
prompt.
&quot; Activate the encrypted partitions (prompts for password):
cryptsetup −i /dev/sdC0/fsworm /dev/sdC0/fscache /dev/sdC0/other
&quot; Type exit to resume booting.
&quot; At the bootargs prompt, enter local!/dev/fs/fscache to continue booting
from the encrypted partition.
Note: Encrypted partitians are largely untested. Data integrity is not guaranteed. Use at
your own risk.
Encrypted partitions have not been tested with hjfs.
Read: cryptsetup(8)
97
FQA 5 − Building the System from Source
5.1 − Why should I build my system from source?
Some reasons why you might actually wish or need to build from source:
&quot; Updates have been committed since you performed the installation.
&quot; Test or develop new features.
5.2 − Building 9front from source
5.2.1 − Update sources
9front uses hg(1) to synchronize the system with the 9front repository:
cd /
bind −ac /dist/plan9front /
hg incoming
hg −v pull −u
which is consolidated in the command:
sysupdate
If hg refuses to update due to conflicts (e.g. if you installed something locally which was
later incorporated into 9front), this is a quick workaround which discards local changes:
hg update −C −−clean
After the tree is updated, recompile/build the updated programs as needed.
98
5.2.1.1 − hgrc
During
installation,
the
9front
Mercurial
repository
is
copied
to
/dist/plan9front/.hg, is chmod 775, and is owned by user glenda and
group sys. To update the repository when logged in as a user other than glenda,
add that user to group sys add then add the following to $home/lib/hgrc:
[trusted]
users=glenda
groups=glenda
To use Mercurial with webfs(4) instead of Pythons built-in HTTP:
[extensions]
hgwebfs=
Note: The hgwebfs extension expects login credentials to be present in
factotum(4), else Mercurial will abort when any attempt is made to access resources
that require authentication. To add credentials to factotum:
echo &acute;key proto=pass realm=PAIN server=code.9front.org service=http n
user=cinap_lenrek !password=FckG00gl!&acute; &gt;&gt;/mnt/factotum/ctl
Note: Depending on who you are and the repository being used, your credentials may
differ.
Credentials may be saved permanently and loaded into factotum at boot time using
FQA 8.4.7 − secstore.
5.2.2 − Building from source
Note: A minimum of 512MB RAM is needed to link some programs. If less than 512MB is
available, be sure to turn on swap before building. Read: swap(8), FQA 3.3 − What is
an appropriate first system to learn 9front on?
# create any missing directories needed for the build
cd /
. /sys/lib/rootstub
# build everything
cd /sys/src
mk install
mk clean
# build manpage indices
cd /sys/man
mk
# build the papers and html (optional)
cd /sys/doc
mk
mk html
Build the kernel for 386:
99
cd /sys/src/9/pc
mk install
Build the kernel for amd64:
cd /sys/src/9/pc64
mk install
Build the kernel for Raspberry Pi:
cd /sys/src/9/bcm
mk install
Read: FQA 7.2.5 − How do I install a new kernel?
5.2.2.1 − Cross compiling
To cross compile, simply set the objtype environment variable prior to running the
build. For example, to build all the amd64 binaries on a 386 system:
# create any missing directories needed for the build
cd /
. /sys/lib/rootstub
cd /sys/src
objtype=amd64 mk install
5.3 − Building an ISO
The 9front ISO is a livecd that also serves as install media.
Note: Currently, only the 386 architecture is built for the ISO. Read: FQA 8.9 −
Bootstrapping architectures not included on the ISO for more information on booting
other architectures.
# put your root file system into /n/src9
bind /root /n/src9
# put your hg repository there
bind −ac /dist/plan9front /n/src9
# build the iso
cd /sys/lib/dist
mk /tmp/9front.iso
5.4 − Common Problems when Compiling and Building
Most of the time, problems in the build process are caused by not following the above
directions carefully.
100
5.4.1 − Updating compilers
Changes to the compilers may necessitate updating the compiler before rebuilding the
rest of the system:
cd /sys/src/cmd/cc; mk install
cd /sys/src/cmd/6c; mk install
101
# choose the appropriate compiler for your archi
FQA 6 − Networking
6.1 − Before we go any further
Plan 9s approach to networking is unusual. For the bulk of this document, it helps if
you have read and at least partially understood FQA 0.1 − What is Plan 9?
Next, read: The Organization of Networks in Plan 9
If you are working with applications such as web servers, FTP servers, and mail servers,
you may benefit greatly by reading the RFCs. Most likely, you cant read all of them.
Pick some topics that you are interested in, or that you use in your network
environment. Look them up, find out how they are intended to work. The RFCs define
many (thousands of) standards for protocols on the Internet and how they are supposed
to work.
Note: A script for downloading all the RFCs is located in /lib/rfc/grabrfc. It
copies the files into /lib/rfc/, and it may take hours for the script to run to comple&shy;
tion.
6.2 − Network configuration
Basic networking is initially configured by the installation process. However, more com&shy;
plex settings or services may be desired. In Plan 9, network configuration is organized
in ndb, the network database.
From ndb(6):
The network database consists of files describing machines known to the local
installation and machines known publicly. The files comprise multi-line
tuples made up of attribute/value pairs of the form attr=value or sometimes
just attr. Each line starting without white space starts a new tuple. Lines
102
starting with # are comments.
The file /lib/ndb/local is the root of the database. Other files are included in
the database if a tuple with an attribute-value pair of attribute database and
no value exists in /lib/ndb/local. Within the database tuple, each pair with
attribute file identifies a file to be included in the database. The files are
searched in the order they appear. For example:
database=
file=/lib/ndb/common
file=/lib/ndb/local
file=/lib/ndb/global
declares the database to be composed of the three files /lib/ndb/common,
/lib/ndb/local, and /lib/ndb/global. By default, /lib/ndb/local is searched
before the others. How- ever, /lib/ndb/local may be included in the database
to redefine its ordering.
Within tuples, pairs on the same line bind tighter than pairs on different lines.
As mentioned, the installer adds basic information about the machine to the file
/lib/ndb/local, based on the questions asked during the installation. This file may
be edited to modify or expand the definition of the local network.
6.2.1 − Host name
Each machine on the network receives a corresponding section in ndb. The host name
(hereafter referred to as sysname) is assigned by setting the sys= tuple:
sys=x301
The resulting sysname is used by the /rc/bin/termrc and /rc/bin/cpurc
startup scripts, which in turn call upon any additional configuration that may exist in
/cfg/$sysname/. (Look at the scripts to see how they deal with /cfg.)
6.2.2 − Identifying and setting up your network interfaces
Network interfaces are recognized by their MAC addresses, which are identified to ndb
using the ether= tuple:
sys=x301 ether=00226811f7dd
Additional tuples in the same grouping will be used to configure the interface in ques&shy;
tion.
6.2.2.1 − Wifi
The following sections provide information pertaining to specific chipsets.
Read: plan9.ini(8), FQA Section 3.2 − Known Working Hardware
103
6.2.2.1.1 − Interfaces
6.2.2.1.1.1 − wavelan
Lucent Wavelan (Orinoco) IEEE 802.11b and compatible PCMCIA cards. Compatible
cards include the Dell TrueMobile 1150 and the Linksys Instant Wireless Network PC
Card. Port and IRQ defaults are 0x180 and 3 respectively.
These cards take a number of unique options to aid in identifying the card correctly on
the 802.11b network. The network may be ad hoc or managed (i.e. use an access
point): mode=[adhoc, managed] and defaults to managed. The 802.11b network
to attach to (managed mode) or identify as (ad hoc mode), is specified by
essid=string and defaults to a null string. The card station name is given by
station=string and defaults to Plan 9 STA. The channel to use is given by
channel=number where number lies in the range 1 to 16 inclusive; the channel is
normally negotiated automatically.
If the card is capable of encryption, the following options may be used:
crypt=[off, on] and defaults to on. keyN=string sets the encryption key N
(where N is in the range 1 to 4 inclusive) to string; this will also set the transmit key to N
(see below). There are two formats for string which depend on the length of the string.
If it is exactly 5 or 13 characters long it is assumed to be an alphanumeric key; if it is
exactly 10 or 26 characters long the key is assumed to be in hex format (without a
leading 0x). The lengths are checked, as is the format of a hex key. txkey=number
sets the transmit key to use to be number in the range 1 to 4 inclusive. If it is desired
to exclude or include unencrypted packets clear=[off, on] configures reception
and defaults to inclusion.
The defaults are intended to match the common case of a managed network with
encryption and a typical entry would only require, for example essid=left−
armpit key1=afish key2=calledraawaru if the port and IRQ defaults are
used. These options may be set after boot by writing to the devices ctl file using a
space as the separator between option and value, e.g.
echo
’key2
1d8f65c9a52d83c8e4b43f94af’
&gt;/net/ether0/0/ctl
Card-specific
power management may be enabled/disabled by pm=[on, off]
6.2.2.1.1.2 − wavelanpci
PCI Ethernet adapters that use the same Wavelan programming interface. Currently the
only tested cards are those based on the Intersil Prism 2.5 chipset.
6.2.2.1.1.3 − iwl
Intel Wireless WiFi Link mini PCI-Express adapters require firmware from
http://firmware.openbsd.org/firmware/iwn-firmware*.tgz to be present on attach in
/lib/firmware or /boot. To select the access point, the essid= and bssid=
parameters can be specified at boot or set during runtime like:
echo essid left−armpit &gt;/net/ether1/clone
If both essid= and bssid= are specified, both must match. Scan results appear in
the ifstats file and can be read out like:
104
cat /net/ether1/ifstats
Ad-hoc mode or WEP encryption is currently not supported. To enable WPA/WPA2
encryption, see wpa(8) for details.
6.2.2.1.1.4 − rt2860
Ralink Technology PCI/PCI-Express wireless adapters require firmware from
http://firmware.openbsd.org/firmware/ral-firmware*.tgz to be present on attach in
/lib/firmware or /boot. See the iwl section above for configuration details.
6.2.2.1.1.5 − wpi
Intel PRO Wireless 3945abg PCI/PCI-Express wireless adapters require firmware from
http://firmware.openbsd.org/firmware/*/wpi-firmware*.tgz to be present on attach in
/lib/firmware or /boot. See the iwl section above for configuration details.
6.2.2.1.2 − WPA
WPA1/TKIP and WPA2/CCMP are supported with the use of the wpa(8) command.
Read: wpa(8)
6.2.2.1.3 − Wifi Roaming
A script can be used to dynamically re-associate with available wifi access points:
http://plan9.stanleylieber.com/rc/wifiroam
Example usage:
@{wifiroam attwifi | aux/statusmsg −k wifiroam} &amp;
6.2.2.1.4 − Wifi Debug
For cards that use the wifi layer, debug prints (note: will appear on the console) may be
enabled with:
echo debug &gt;&acute;#l0/ether0/clone&acute;
# change this to suit if wifi interface is not #l0
or by adding debug=1 to the interface definition in plan9.ini.
Read: plan9.ini(8)
105
6.2.3 − IP address The ip= tuple is used to associate an IP address with the machine:
sys=x301 ether=00226811f7dd ip=192.168.0.31
If no ip= tuple is present, the boot scripts will attempt to bring up the interface using
DHCP (see below).
6.2.4 − Default gateway
The default gateway is configured using the ipgw= tuple, usually under an ipnet=
section that defines default settings for an entire subnet:
ipnet=9front ip=192.168.0.0 ipmask=255.255.255.0 ipgw=192.168.0.1
but it may also be specified on a per-machine basis:
sys=x301 ether=00226811f7dd ip=192.168.0.31 ipgw=192.168.0.1
Note: Tuples included in the definition of a machine supercede those defined for the
network to which the machine belongs.
6.2.5 − DNS Resolution
DNS resolvers may be specified using the dns= tuple, and may be configured for an
entire network:
ipnet=9front ip=192.168.0.0 ipmask=255.255.255.0 ipgw=192.168.0.1
dns=192.168.0.1
or on a per-machine basis:
sys=x301 ether=00226811f7dd ip=192.168.0.31 dns=192.168.0.1
These changes will take effect after a reboot. To configure a DNS resolver on the fly, it is
possible to manually edit /net/ndb:
ip=192.168.0.31 ipmask=255.255.255.0 ipgw=192.168.0.1
sys=x301
dom=x301.9front
dns=192.168.0.1
# add or modify dns= lines to associate the DNS
# server 192.168.0.1 with the running system
Note: /net/ndb is a synthetic file that represents the current operating state. It does
not persist across reboots.
Read: ip(3)
Finally, to turn on debug in dns:
echo −n debug &gt;/net/dns
106
6.2.5.1 − Caching DNS server
To run a caching DNS server, add entries corresponding to the DNS rootservers in
/lib/ndb/local:
#
# entries defining the dns root. these will be overridden by any
# authentic info obtained from the root.
#
dom=
ns=A.ROOT−SERVERS.NET
ns=B.ROOT−SERVERS.NET
ns=C.ROOT−SERVERS.NET
ns=D.ROOT−SERVERS.NET
ns=E.ROOT−SERVERS.NET
ns=F.ROOT−SERVERS.NET
ns=G.ROOT−SERVERS.NET
ns=H.ROOT−SERVERS.NET
ns=I.ROOT−SERVERS.NET
ns=J.ROOT−SERVERS.NET
ns=K.ROOT−SERVERS.NET
ns=L.ROOT−SERVERS.NET
ns=M.ROOT−SERVERS.NET
Next, modfiy /cfg/$sysname/termrc or /cfg/$sysname/cpurc (whichever is
appropriate) to include the following:
ndb/dns −rs
The caching DNS server will be started at boot time.
Finally, modify /lib/ndb/local such that the desired machines will use the IP
address of the new caching DNS server as their DNS server, either by changing the
dns= tuple under the ipnet of the corresponding network or by adding a dns= tuple
to the line of each desired machine.
Read: ndb(6) and ndb(8)
6.2.5.2 − DNS authoritative name server
An authoritative domain name record, with associated reverse-lookup and subdomains, looks like this:
107
dom=bell−labs.co soa=
refresh=10800 ttl=10800
serial=2012110732
# serial is automatically maintained if omitted
ns=ns5.he.net
ns=ns4.he.net
ns=ns3.he.net
ns=ns2.he.net
ns=nm.iawtp.com
ns=pp.iawtp.com
ns=mars2.iawtp.com
dnsslave=slave.dns.he.net
[email protected]
mx=pp.inri.net pref=5
mx=nm.inri.net pref=10
mx=mars2.inri.net pref=15
txtrr=&quot;v=spf1 mx −all&quot;
dom=125.191.107.in−addr.arpa soa=
refresh=3600 ttl=3600
ns=nm.iawtp.com
dom=bell−labs.co ip=107.191.125.208
dom=www.bell−labs.co cname=bell−labs.co
An FQDN may be assigned to an existing machine by adding the dom= tuple to its defi&shy;
nition:
sys=x301 dom=x301.bell−labs.co ether=00226811f7dd ip=192.168.0.31
Note: The dnsslave entries specify slave DNS servers that should be notified when the
domain changes. The notification service also requires the −n flag:
ndb/dns −nrs
Read: ndb(8)
6.2.6 − Network−wide configuration
Settings for an entire network subnet may be defined under an ipnet= tuple:
108
ipnet=9front ip=192.168.0.0 ipmask=255.255.255.0
ipgw=192.168.0.1
auth=192.168.0.2
authdom=9front
fs=192.168.0.3
cpu=192.168.0.4
dns=192.168.0.1
dnsdomain=9front
smtp=192.168.0.4
# ethernet/wifi router
sys=onoff dom=onoff.9front ip=192.168.0.1
# auth server
sys=auth dom=auth.9front ether=00d059b6dac8 ip=192.168.0.2
bootf=/386/9bootpxe
# cpu server
sys=cpu dom=cpu.9front ether=001125149137 ip=192.168.0.4
bootf=/386/9bootpxe
# file server
sys=fs dom=fs.9front ether=001641360117 ip=192.168.0.3
# terminal
sys=x301 dom=x301.9front ether=00226811f7dd ip=192.168.0.31
bootf=/386/9bootpxe
6.2.7 − Activating the changes
6.2.7.1 − NIC
Network interfaces are automatically initialized at boot time. To make a manual change
without rebooting, use the ipconfig(8) command:
ip/ipconfig −g 192.168.0.1 ether /net/ether0 192.168.0.31 255.255.255.0
6.2.7.2 − cs
To refresh the network database NOW after changing /lib/ndb/local:
echo −n refresh &gt; /net/cs
6.2.7.3 − dns
echo −n refresh &gt; /net/dns
109
6.2.8 − Verifying network settings
% cat /net/ndb
ip=192.168.0.31 ipmask=255.255.255.0 ipgw=192.168.0.1
sys=x301
dom=x301.9front
auth=192.168.0.2
dns=192.168.0.1
6.2.8.1 − Checking routes
% cat /net/iproute
0.0.0.0
/96
192.168.0.0
/120
192.168.0.0
/128
192.168.0.31
/128
192.168.0.255
/128
255.255.255.255 /128
192.168.0.1
192.168.0.0
192.168.0.0
192.168.0.31
192.168.0.255
255.255.255.255
4
4i
4b
4u
4b
4b
none
ifc
ifc
ifc
ifc
ifc
−
0
−
0
−
0
6.2.8.1.1 − Adding static routes
Route requests for 192.168.1.0/24 through the gateway 192.168.0.99 (which
itself must already be accessible via the existing network configuration):
echo &acute;add 192.168.1.0 255.255.255.0 192.168.0.99&acute; &gt;/net/iproute
Note: Manual configurations such as this may be added to optional boot scripts created
in /cfg/$sysname/.
Read: ip(3)
6.2.9 − Setting up your 9front box as a forwarding gateway
Read: ip(3)
6.2.10 − Setting up aliases on an interface
Read: ip(3)
6.3 − How do I filter and firewall with 9front?
No.
6.4 − Dynamic Host Configuration Protocol (DHCP)
110
6.4.1 − DHCP client
In /lib/ndb/local, if no ip= tuple is present in the machines definition, the boot
scripts will attempt to obtain an IP address via DHCP.
To obtain a DHCP lease manually:
ip/ipconfig
Read: ipconfig(8)
6.4.2 − DHCP server
From dhcpd(8):
111
Dhcpd runs the BOOTP and DHCP protocols. Clients use these
protocols to obtain configuration information. This infor−
mation comes from attribute/value pairs in the network data−
base (see ndb(6) and ndb(8)). DHCP requests are honored both
for static addresses found in the NDB and for dynamic
addresses listed in the command line. DHCP requests are
honored if either:
− there exists an NDB entry containing both the ethernet
address of the requester and an IP address on the originat−
ing network or subnetwork.
− a free dynamic address exists on the originating network
or subnetwork.
A BOOTP request is honored if all of the following are true:
− there exists an NDB entry containing both the ethernet
address of the requester and an IP address on the originat−
ing network or subnetwork.
− the entry contains a bootf= attribute
− the file in the bootf= attribute is readable.
Dynamic addresses are specified on the command line as a
list of addresses and number pairs. For example,
ip/dhcpd 10.1.1.12 10 10.2.1.70 12
directs dhcpd to return dynamic addresses 10.1.1.12 through
10.1.1.21 inclusive and 10.2.1.70 through 10.2.1.81 inclu−
sive.
Dhcpd maintains a record of all dynamic addresses in the
directory /lib/ndb/dhcp, one file per address. If multiple
servers have access to this common directory, they will cor−
rectly coordinate their actions.
Attributes come from either the NDB entry for the system,
the entry for its subnet, or the entry for its network. The
system entry has precedence, then the subnet, then the net−
work. The NDB attributes used are:
ip
ipmask
ipgw
dom
fs
auth
dns
ntp
time
wins
www
pop3
smtp
bootf
the IP address
the IP mask
the default IP gateway
the domain name of the system
the default Plan 9 file server
the default Plan 9 authentication server
a domain name server
a network time protocol server
a time server
a NETBIOS name server
a World Wide Web proxy
a POP3 mail server
an SMTP mail server
the default boot file; see ndb(6)
Dhcpd will answer BOOTP requests only if it has been specif−
ically targeted or if it has read access to the boot file
for the requester. That means that the requester must spec−
ify a boot file in the request or one has to exist in NDB
for dhcpd to answer. Dhcpd will answer all DHCP requests
for which it can associate an IP address with the requester.
112
To configure a DHCP server on your system, modify /cfg/$sysname/cpurc or
/cfg/$sysname/termrc (whichever is appropriate) to start dhcpd and tftpd at
boot time:
ip/dhcpd
Read: dhcpd(8)
6.5 − PPP
Read: Dailup modem config at the Bell Labs Plan 9 wiki.
6.6 − Setting up a network bridge in 9front
Read: bridge(3) and ip(3)
6.7 − How do I boot from the network?
First, read FQA 7.3.3 − Setting up a listener for network connections. The file server
should already be running a listener, and an auth server should already be configured
and running on the network.
6.7.1 − How do I tcp boot?
It is possible to boot from local media and then mount the root file system over the net&shy;
work. At the bootargs prompt, type tcp. At this point, ip/ipconfig will deter&shy;
mine network parameters using DHCP. When file (fs) or authentication (auth) server IP
addresses could not be determined over DHCP then the boot process will prompt for
those. When prompted for a user, enter a valid username and password that has
already been configured on the auth server. The machine should then proceed to mount
its root file system from the file server.
Note: Values for fs and auth may be added to plan9.ini.
Read: plan9.ini(8)
6.7.1.1 − Passing arguments to ipconfig at the bootargs prompt
When a DHCP server is not available, you may still tcp boot by configuring networking
manually at the bootargs prompt. Everything after tcp! is passed as arguments to
the ipconfig command.
At the prompt:
bootargs is (tcp, il, local!device) [tcp]
enter something like the following:
tcp!−g 192.168.0.1 ether /net/ether0 192.168.0.23 255.255.255.0
where 192.168.0.1 is the gateway, 192.168.0.23 is the static IP address and
255.255.255.0 the subnet mask.
113
Read: ipconfig(8)
6.7.2 − How do I boot using PXE?
It is also possible to PXE boot a system.
On the file server, add the following lines to /cfg/$sysname/cpurc to start dhcpd
and tftpd at boot time:
ip/dhcpd
ip/tftpd
Add an entry for tftp under the appropriate ipnet= tuple in /lib/ndb/local:
ipnet=9front ip=192.168.0.0 ipmask=255.255.255.0 ipgw=192.168.0.1
auth=192.168.0.2
authdom=9front
cpu=192.168.0.4
dns=192.168.0.1
dnsdomain=9front
smtp=192.168.0.4
tftp=192.168.0.3
Reboot the file server:
fshalt −r
To configure machines that will PXE boot from the file server, edit /lib/ndb/local
on the file server and add a bootf= (boot file) tuple to the line representing each
machine:
sys=x301 dom=x301.9front ether=00226811f7dd ip=192.168.0.31
bootf=/386/9bootpxe
For the system x301 we would then create a file /cfg/pxe/00226811f7dd on the
file server to serve as its plan9.ini:
bootfile=/386/9pcf
bootargs=tcp
nobootprompt=tcp
auth=192.168.0.2
fs=192.168.0.3
mouseport=ps2intellimouse
monitor=vesa
vgasize=1440x900x32
*acpi=1
user=sl
Note: The user= parameter refers to a single username that has been added both to
the file server (for file permissions) as well as to the auth server (for network authentica&shy;
tion).
If a file matching the remote systems MAC address is not found under /cfg/pxe/,
the file /cfg/pxe/default (if it exists) will be used instead.
114
Finally, boot the desired remote systems via PXE. When prompted for a user, enter a
valid username and password that has already been configured on the auth server. The
remote system should now proceed to boot from the file server.
115
FQA 7 − System Management
7.1 − Plan 9 Services Overview
In order to be an effective system manager it is a good idea to understand how the sys&shy;
tem is designed, and how it is intended to be used.
A Plan 9 installation consists of a disk file server, an authentication server, and one or
more cpu servers and terminalsall sharing the same disk file system.
That said, Plan 9 services may be run on separate machines, all together on one
116
machine, or in various combinations. The original design of Plan 9 assumed that each
network service would run on separate hardware; by design, individual components of
the system are generally unaware if they co-exist on the same machine or are dis&shy;
tributed amongst separate machines.
This document will describe individual services as if they are all running separately.
Read: Designing Plan 9, Plan 9 From Bell Labs, The Organization of Networks in Plan 9
7.1.1 − What is the kernel?
The kernel is a service that provides processes and resources to users active on an indi&shy;
vidual machine. Every Plan 9 machine boots a kernel.
At boot time the kernel takes on the identify of $user (the user who logs in at the con&shy;
sole), which becomes the hostowner of the system. The hostowner in turn 1.) con&shy;
trols access to the kernels resources, 2.) serves as the auth identity (authid) of the
machine and the services it provides.
Note: The hostowner differs from the concept of root on a UNIX system, where a
single user root may take control of all processes and files on the system. By contrast,
even the hostowner of a Plan 9 file server cannot violate file permissions on the file
server, except when permissions checking is disabled on the console or when entering
special commands at the console of the file server. The hostowner controls only the
processes running on the local machine. This fundamental separation between control of
processes and file permissions is exploited throughout the Plan 9 system, but can be
confusing for users coming from a UNIX background.
7.1.2 − What is the file server?
In a traditional Plan 9 network there is one disk file server, typically the only machine
with a physical hard disk, that serves files to all other machines on the network. In most
cases, other machines are either diskless or only use their disks for local caching. Ken
Thompsons original Plan 9 file server ran a unique, special-purpose kernel that only
served files, and whose configuration could only be changed at the console. In 9front,
the file server runs a normal kernel and typically also runs as a cpu server (for remote
access).
9front supports two different disk file systems for use on the file server: cwfs and
hjfs. cwfs is a userspace port of Ken Thompsons original Plan 9 file server. hjfs
is a new, experimental file server that stores both the cache and worm on a single parti&shy;
tion (and thus requires less disk space to be used effectively). Both are reasonably
robust.
Read: The Plan 9 File Server (deprecated, but partially applies to cwfs), cwfs(4),
hjfs(4)
Note: Since most Plan 9 systems have no disk, security of the file server is largely pro&shy;
tected from breaches of security in its clients. The fewer the programs that run on the
file server, the more isolated it can be from security holes in programs.
Note: Users seeking access to the file server must be added as a user on the file system
117
itself, and, if auth is enabled, added to the auth servers user database.
Note: Some users choose to run remote cpu or auth servers as stand-alone systmes,
each with their own local disk file systems. The distinction between all these types of
systems is fuzzy and can become even fuzzier as services are enabled and disabled in
different combinations.
7.1.3 − What is the auth server?
The auth server manages authentication for an entire Plan 9 network. It boots a normal
kernel but is usually run on a separate, diskless machine that performs no other func&shy;
tions, in order to reduce the danger of a security breach compromising its kernel pro&shy;
cesses. That said, the auth server is usually also configured as a cpu server, for remote
access.
Note: The cron(8) service should be run only on the auth server, where it can authen&shy;
ticate itself to access any of the other machines on the network.
Read: Security in Plan 9, auth(8)
7.1.4 − What is the cpu server?
The cpu server is used for remote computation. A cpu servers kernel runs processes in
isolation, on only that machine. The boot process of a cpu server (defined as such by
setting service=cpu in the machines plan9.ini or equivalent) may be examined
by reading the /rc/bin/cpurc script, which is executed at boot time. Running as a
cpu server causes the kernel to adjust certain resource values that ultimately determine
the behavior of the machine. For example, the cpurc script starts certain programs
only if the machine is recognized as a cpu server.
Common use cases for a separate cpu server are: To execute programs compiled for a
different architecture than that of the terminal; To execute programs closer to the data
they are operating upon (for example, if the terminal is running over a slow link but the
cpu server is on the same ethernet segment as the file server); To execute processes in
physical isolation from other processes. In the early days of Plan 9, a cpu server was
often significantly more powerful than the (often, special-purpose) hardware used for
diskless terminals. Today, terminals are typically powerful computers in their own right,
and the need for a separate machine running only as a cpu server is less common. That
said, it can be useful to execute unstable or unpredictable programs on a separate
machine so that frequently crashing and/or rebooting does not affect ones immediate
workspace environmentespecially when testing new code. In the case of remote (mail,
web, etc.) servers, it is also likely that cpu access would be desired.
In practice, the disk file server, the auth server, and even some terminals will often run
their own cpu listeners, to enable remote access to the processes controlled by their
kernels.
Note: Users seeking access to a cpu server must first be added on the file system of the
cpu servers corresponding file server (for permission to access and modify files) as well
as the user database of its designated auth server (for login authentication).
Read: The Organization of Networks in Plan 9, cpu(1), exportfs(4)
118
7.1.5 − What is a terminal?
The terminal is the machine at which the Plan 9 user is most often physically located.
Usually diskless, the terminal will almost always run with graphics enabled (for launch&shy;
ing the rio GUI or other graphical programs). The boot process of a terminal (defined
as such by setting service=terminal in the machines plan9.ini or equivalent)
may be examined by reading the /rc/bin/termrc script, which is executed at boot
time.
Note: Many Plan 9 users run stand-alone systems that operate effectively as a
combined terminal and file server. For example, inside a virtual machine such as qemu,
or booted from hard disk on a laptop. In this case the Plan 9 network is entirely selfcontained, running one kernel on one machine, which renders auth and cpu services
superfluous. This configuration trades some of the inherent security of separate hard&shy;
ware and kernel boundaries for the convenience of combining the whole system into a
single, bootable instance.
Note: Terminal users who do not run stand-alone machines or who wish to access Plan
9 network resources must first be added to the file system of the networks file server,
and to the user database of the networks auth server.
7.2 − Kernel configuration and maintenance
7.2.1 − How do I mount the 9fat partition?
9front has done away with the scripts 9fat:, c:, and so forth, that are found in the
Bell Labs Plan 9 distribution. Instead, use the 9fs script to mount the 9fat partition:
9fs 9fat
If you are not at the console, or if #S has not already been bound over /dev:
bind −b ’#S’ /dev # bind the local hard drive kernel device over /dev
9fs 9fat /dev/sdXX/9fat # specify the full path to the corresponding 9fat
Note: 9fs 9fat posts a file descriptor in /srv/dos. If this file already exists and is
already in use, 9fs 9fat will fail. If no other process is using the file it is safe to
simply remove it and run 9fs 9fat again.
Read: dossrv(4)
7.2.2 − How do I modify plan9.ini?
Mount the 9fat partition and then edit the file /n/9fat/plan9.ini.
Note: The file must end with a newline.
Read: plan9.ini(8)
119
7.2.3 − Kernel configuration file
Kernel configuration files are stored in the kernel directory and share the name of the
kernel to which they apply. For example, the configuration file for the pcf kernel is
/sys/src/9/pc/pcf.
7.2.4 − Kernel drivers
Kernel driver source files are located in the kernel source directory. For example, the pc
kernel source is located in /sys/src/9/pc.
7.2.5 − How do I install a new kernel?
To build and install the new kernel(s) on the file system:
For 386:
cd /sys/src/9/pc
mk install # kernel is copied to /386/9pcf
For amd64:
cd /sys/src/9/pc64
mk install # kernel is copied to /amd64/9pc64
For bcm (Raspberry Pi, etc.):
cd /sys/src/9/bcm
mk install # kernel is copied to /arm/9pif
For 386 and amd64 machines with local disk, it may be desired to install the new boot&shy;
loader and kernels onto the 9fat partition, in order to boot directly from disk. Note:
The bootloader needs to be continuous on disk, so simply copying over the original file
does not produce the desired effect. Instead:
9fs 9fat
rm /n/9fat/9bootfat
cp /386/9bootfat /n/9fat/
chmod +al /n/9fat/9bootfat # defrag magic
then copy the desired kernels:
For 386:
cp /386/9pcf /n/9fat/
For amd64:
cp /amd64/9pc64 /n/9fat/
Finally, if a different kernel is being intsalled than the one currently running, edit
plan9.ini and change bootfile to point to the new kernel.
120
Read: FQA 7.2.2 − How do I modify plan9.ini?
7.3 − Fileserver configuration and maintenance
7.3.1 − Adding users
Add a new user on the file server:
For cwfs:
echo newuser username &gt;&gt;/srv/cwfs.cmd
For hjfs:
echo newuser username &gt;&gt;/srv/hjfs.cmd
If needed, make the new user a member of another group (example: upas):
For cwfs:
echo newuser upas +username &gt;&gt;/srv/cwfs.cmd
For hjfs:
echo newuser upas +username &gt;&gt;/srv/hjfs.cmd
Both file servers store their user database in /adm/users. Examine this file, and the
contents of the /usr directory, to evaluate success.
Note: It is also possible to access the control file interactively:
For cwfs:
con −C /srv/cwfs.cmd
For hjfs:
con −C /srv/hjfs.cmd
From here commands may be entered directly.
Type Ctrl−\ to resume the con prompt, followed by q to quit.
Note: New users are created without a profile, mail directory, tmp directory (needed to
edit files with sam) or other confections. To install a default profile for a new user, upon
first login as that user, run:
/sys/lib/newuser
then edit /usr/username/lib/profile to your own specifications. The
newuser file system command is described in the man pages fs(8) (for cwfs) and
hjfs(8).
121
7.3.2 − Configuring nvram
The cpu kernel checks the nvram file for valid auth credentials and attempts to copy
them into factotum so that the machine may boot without manual intervention. To
configure the nvram, run the command auth/wrkey, which will prompt for an
authid, authdom, secstore key, and password. The authid is a synonym
for the hostowner of the machine and should be a valid user that has already been (or
will be) added to the corresponding auth server, in this case glenda. The authdom is
the authentication domain for the machine, in this case 9front. The secstore
key and password are secret passwords of eight characters or more in length. The
password is the password belonging to the authid user on the auth server
responsible for the authdom entered above. The secstore key is the password of
the user on the secure-store server (Read: FQA 7.4.3 − secstored). If the secstore
client (Read: FQA 8.4.7 − secstore) is not being used on this machine (for example, if
this is the auth server where secstored will run), just hit enter at the secstore
key: prompt.
Run the command auth/wrkey:
bad nvram key
bad authentication id
bad authentication domain
# You may not see these errors.
authid: glenda
authdom: 9front
secstore key: [glenda’s secstore password]
password: [glenda’s password]
Note: Booting the file system with authentication enabled and an invalid nvram file will
cause auth/wrkey to be run automatically at startup.
Read: auth(8)
7.3.3 − Setting up a listener for network connections
In order for remote machines to mount the file system of the file server, the file server
must first be running a network listener. This section details the steps required to trans&shy;
form a terminal with disk (the result of a default install of 9front) into a disk file server
for other machines.
The first step is to switch from the terminal service to the cpu service by editing the
service line in in /n/9fat/plan9.ini:
service=cpu
Read: FQA 7.2.2 − How do I modify plan9.ini?
Before rebooting, configure the nvram: FQA 7.3.2 − Configuring nvram. This allows the
machine to load auth credentials from the nvram file into factotum, so that it can
continue to boot without manual intervention.
Reboot:
fshalt −r
122
The next step (on cwfs; not needed on hjfs) is to enable authentication on the file
server, to prevent unauthorized users from accessing the disk over the network. At the
bootargs prompt, retype the default and add the −c flag to enter the file servers
config mode. At the config prompt, type noauth twice to toggle authentication on
the file server. Finally, type end to continue with the boot process:
bootargs is (tcp, local!device) [local!/dev/sdXX/fscache] local!/dev/sdXX/fscach
config: noauth
auth is now disabled
config: noauth
auth is now enabled
config: end
The machine will now continue to boot.
Once booted, the next step is to configure the file server to listen for connections from
remote hosts. Modify the bootargs of the file server in /n/9fat/plan9.ini:
For cwfs:
bootargs=local!/dev/sdXX/fscache −a tcp!*!564
For hjfs:
bootargs=local!/dev/sdXX/fs −m 702 −A −a tcp!*!564
Note: The −m 702 flag for hjfs allocates 702 megabytes of memory to be used as a
cache. This value is typically automatically calculated by the 9front installer, and may
differ on your system. There is no need to change whatever default was already
configured.
Read: FQA 7.2.2 − How do I modify plan9.ini?
Reboot the file server:
fshalt −r
When the system finishes booting it should now be listening for network connections to
the file system. Users who have been added to the file server and the auth server should
now be able to authenticate and mount the file server (tcp boot, etc.).
Read: cwfs(4), hjfs(4), FQA 6.7.1 − How do I tcp boot?
7.3.4 − Mounting a file system from userspace
For cwfs:
% cwfs64x −n fs −f /dev/sdE0/fscache
% mount /srv/fs /n/fs
# use the correct path to your fscache
Note:
Running the above commands will post the file systems’s console in
/srv/fs.cmd.
For hjfs:
123
to be announced
7.4 − Auth server configuration and maintenance
7.4.1 − Configuring an auth server
The auth server should be booted with service=cpu in plan9.ini, and ndb modi&shy;
fied to associate the new auth server with the desired authdom.
If the cpu server machine boots from a local disk, edit the service line in in
/n/9fat/plan9.ini:
service=cpu
Read: FQA 7.2.2 − How do I modify plan9.ini?
If the machine boots via PXE, edit the service line in in the file under /cfg/pxe/
that correspondes to its MAC address. In this case, /cfg/pxe/000c292fd30c:
service=cpu
Note: The contents of /cfg/pxe/000c292fd30c serves as the equivalent of
plan9.ini for the PXE booted machine. Any other settings that would normally be
configured in plan9.ini may also be entered there.
Next, ndb must be modified to associate the new auth server with the desired
authdom. Assuming the auth server has a MAC address of 00:0c:29:2f:d3:0c,
an IP address of 192.168.0.2, and a default gateway/DNS server of 192.168.0.1
that are all on the Class C network 192.168.0.0/24, and that the authdom is
9front, edit /lib/ndb/local and add the authdom and the auth servers IP
under the corresponding ipnet:
ipnet=9front ip=192.168.0.0 ipmask=255.255.255.0
ipgw=192.168.0.1
auth=192.168.0.2 # add auth server’s ip
authdom=9front # add authdom
fs=192.168.0.3
cpu=192.168.0.4
dns=192.168.0.1
dnsdomain=9front
smtp=192.168.0.4
Read: ndb(6)
Before rebooting, configure the nvram: FQA 7.3.2 − Configuring nvram. This allows the
machine to load auth credentials from the nvram file into factotum, so that it can
continue to boot without manual intervention.
Note: If the auth servers hostowner (referred to as authid in the auth/wrkey
dialogue) will be any other user than the default glenda, that user must be authorized
(in the auth context) to &quot;speak for&quot; other users. Assuming a hostowner of sl, add a rule
to /lib/ndb/auth:
124
hostid=sl
uid=!sys uid=!adm uid=*
This rule allows the user sl to speak for all users except for sys and adm.
Read: auth(8)
Reboot:
fshalt −r
At boot time, the shell script /rc/bin/cpurc consults ndb to determine if the
machine is an auth server. If it is, the script will launch the keyfs process and start lis&shy;
teners for auth connections. If, after booting, keyfs is not running, something went
wrong.
Finally, create an auth user and configure an auth password for the hostowner of the
machine. This auth user should be the same name as the authid that was entered at
boot time during the auth/wrkey dialogue. Likewise, set the password to match
the password that was entered during the auth/wrkey dialogue. Note: If the user
and password do not match what was entered during the auth/wrkey dialogue, users
will not be able to authenticate using this auth server.
Read: FQA 7.4.2 − Adding users
7.4.1.1 − Avoiding an ndb entry for the auth server
If an auth server for a given authdom is not found in the local ndb, then the
authdial() function from the libauthsrv library (used for resolving auth servers)
will default to the dns host name p9auth.example.com, where p9auth is the sub&shy;
domain, and example.com is the authdom. This convention (where followed) is useful
to avoid having to manually add auth server information for arbitrary remote networks
to the local ndb.
7.4.2 − Adding users
To add a new user to the auth server, login as the auth servers hostowner, make
sure auth/keyfs is running in your namespace, and then set an auth password for
the user:
% auth/keyfs
% auth/changeuser username
Password: # type password here, will not echo
Confirm password: # confirm password here, will not echo
assign Inferno/POP secret? (y/n) n
Expiration date (YYYYMMDD or never)[return = never]:
2 keys read
Post id:
User’s full name:
Department #:
User’s email address:
Sponsor’s email address:
user username installed for Plan 9
125
Note: Questions that appear after the keys read notice are optional. Hit Enter for
each one to leave them blank.
Read: auth(8), keyfs(4)
7.4.3 − secstored
Secstore authenticates to a secure-store server using a password and optionally a hard&shy;
ware token, then saves or retrieves a file. This is intended to be a credentials store
(public/private keypairs, passwords, and other secrets) for a factotum.
To set up secstored, login to the auth server as hostowner and:
mkdir /adm/secstore
chmod 770 /adm/secstore
Start secstored at boot time by adding the following to /cfg/$sysname/cpurc
on the auth server:
auth/secstored
Read: secstore(1), secstore(8)
7.4.3.1 − Adding users to secstore
secuser is an administrative command that runs on the secstore machine, normally
the auth server, to create new accounts and to change status on existing accounts. It
prompts for account information such as password and expiration date, writing to
/adm/secstore/who/user for a given secstore user.
Login to the auth server as hostowner and:
auth/secuser username
and answer the prompts.
By default, secstored warns the client if no account exists. If you prefer to obscure
this information, use secuser to create an account FICTITIOUS.
Read: FQA 8.4.7 − secstore for more information on using the secstore lient.
7.4.3.2 − Converting from ps9k1 to dp9ik
126
Date: Wed, 6 Jan 2016 03:54:08 +0100
From: [email protected]
To: [email protected]
Subject: [9front] new factotum/authsrv/keyfs
Reply−To: [email protected]
i just pushed the new code which adds dp9ik authentication support.
to update a system, the following things need to be done:
# make sure you have the latest libmp/libsec
cd /sys/src/libmp; mk install
cd /sys/src/libsec; mk install
# rebuild mpc (required for libauthsrv)
cd /sys/src/cmd; mk mpc.install
# rebuild libauthsrv / libauth
cd /sys/src/libauthsrv; mk install
cd /sys/src/libauth; mk install
# rebuild factotum/keyfs/authsrv
cd /sys/src/cmd/auth; mk install
# then rebuild kernel to include the new factotum,
# but dont reboot your authserver just yet...
cd /sys/src/9/pc; mk install
# if your /adm/keydb is still in DES format (cat it to see
# if the keyfile starts with the AES signature), you need to
# convert it to use the new dp9ik protocol:
# make backup
cp /adm/keys /adm/keys.old
auth/convkeys −ap /adm/keys
# now set the aes key in nvram (so authserver can decrypt
# the keydb when it boots)
auth/wrkey
# now you can reboot the AS and once its up, you have to
# set new passwords for the users. logging in with the
# old p9sk1 plan9 password should continue to work if
# you skip this.
passwd [username]
# if there are issues logging in with dp9ik because keydb
# doesnt have the new key yet, you can use delkey(1) to
# remove the dp9ik key from factotum as a work arround.
−−
cinap
127
7.5 − Cpu server configuration and maintenance
7.5.1 − Configuring a cpu server
Note: Operating a cpu server requires auth services. Read: FQA 7.4 − Auth server
configuration and maintenance
The first step in converting a terminal to a cpu server is to switch from the terminal
service to the cpu service.
If the cpu server machine boots from a local disk, edit the service line in in
/n/9fat/plan9.ini:
service=cpu
Read: FQA 7.2.2 − How do I modify plan9.ini?
If the machine boots via PXE, edit the service line in in the file under /cfg/pxe/
that correspondes to its MAC address. In this case, /cfg/pxe/000c292fd30c:
service=cpu
Note: The contents of /cfg/pxe/000c292fd30c serves as the equivalent of
plan9.ini for the PXE booted machine. Any other settings that would normally be
configured in plan9.ini may also be entered here.
Setting service=cpu causes the shell script /rc/bin/cpurc to be run at boot
time, which in turn launches a listener that scans the /rc/bin/service directory for
scripts corresponding to various network ports. Read: listen(8). The script
tcp17010 handles incoming cpu connections. Authentication for incoming cpu con&shy;
nections is performed by the auth server associated with the authdom by ndb. Read:
FQA 7.4.1 − Configuring an auth server
Before rebooting, configure the nvram: FQA 7.3.2 − Configuring nvram. This allows the
machine to load auth credentials from the nvram file into factotum, so that it can
continue to boot without manual intervention.
Reboot:
fshalt −r
7.6 − Terminal configuration and maintenance
7.6.1 − Configuring a terminal
The 9front ISO boots into a livecd running the 9pcf kernel, resulting in the simplest
form of terminal running on the 386 architecture. A terminal may also be network
booted (the preferred method) or installed to its own stand-alone file system on a local
storage device.
Read: FQA 6.7 − How do I boot from the network?
128
7.6.2 − Configuring a Terminal to Accept cpu Connections
If the hostowner factotum has been loaded with the appropriate key and the system
is listening for cpu connections, a user may cpu into a terminal that is not running
auth services. To configure a terminal to accept cpu connections in this fashion, substi&shy;
tute your choice of dom (this refers to the authdom), user and password, below:
echo &acute;key proto=p9sk1 dom=9front user=glenda !password=p@ssw0rd&acute; \
&gt;/mnt/factotum/ctl
aux/listen1 −t tcp!*!17010 /bin/cpu −R &amp;
7.6.3 − UTC Timesync
By default, /rc/bin/termrc sets TIMESYNCARGS=(−rLa1000000), to synchro&shy;
nize 9front time with the real time clock. On many systems this time is saved as UTC,
whereas Windows keeps the local time there. If your time is in UTC you should omit the
-L: Put TIMESYNCARGS=(−ra1000000) into /rc/bin/termrc.local, which is
executed by /rc/bin/termrc.
7.7 − Mail server configuration and maintenance
Incoming and outgoing mail is handled by upas and its related suite of programs. Con&shy;
figuration is handled by a number of files found in /mail/lib/, while many of
upas’ common functions are carried out by shell scripts that are (relatively) easy to
modify.
Note: The user who runs the assorted upas programs needs read and write permis&shy;
sions on /mail/queue and /mail/tmp, as well as write permissions for any mail&shy;
boxes where mail will be delievered.
Note: Be sure to configure proper DNS entries for your domains. If Plan 9 will host your
DNS, see: FQA 6.2.5.2 − DNS authoritative name server
129
Read: Upas − A Simpler Approach to Network Mail, mail(1)
The following sections describe configuration of basic Internet mail services.
7.7.1 − smtpd.conf
Some changes to the default smtpd.conf are required to accept mail for Internet
domain names, and to relay mail for remote hosts (most commonly, your own
machines). The following lines should be changed to correspond to your network:
# outgoing mail will be sent from this domain by default
defaultdomain
9front.org
# do not be an open relay
norelay
on
# disable dns verification of sender domain
verifysenderdom
off
# do not save blocked messages
saveblockedmsg
off
# if norelay is on, you need to set the
# networks allowed to relay through
# as well as the domains to accept mail for
ournets 199.191.58.37/32 199.191.58.42/32 192.168.4.0/24
# domain names for which incoming mail is accepted
ourdomains 9front.org, bell−labs.co, cat−v.org
Read: smtpd(6), smtp(8)
7.7.2 − rewrite
To act as an Internet mail server, copy rewrite.direct to rewrite and modify to
reflect your sites Internet domain name(s):
130
# case conversion for postmaster
pOsTmAsTeR alias postmaster
# local mail
\l!(.*) alias \1
(ttr|9front.org|bell−labs.co|cat−v.org)!(.*)
[^!@]+ translate &quot;/bin/upas/aliasmail &acute;&amp;&acute;&quot;
local!(.*) &gt;&gt; /mail/box/1/mbox
alias \2
# we can be just as complicated as BSD sendmail...
# convert source domain address to a chain a@b@c@d...
@([^@!,]*):([^!@]*)@([^!]*) alias \2@\3@\1
@([^@!]*),([^!@,]*):([^!@]*)@([^!]*) alias @\1:\3@\4@\2
# convert a chain a@b@c@d... to ...d!c!b!a
([^@]+)@([^@]+)@(.+) alias \2!\1@\3
([^@]+)@([^@]+) alias \2!\1
# /mail/lib/remotemail will take care of gating to systems we don’t know
([^!]*)!(.*) | &quot;/mail/lib/qmail &acute;\\s&acute; &acute;net!\1&acute;&quot; &quot;&acute;\2&acute;&quot;
Read: rewrite(6)
7.7.3 − names.local
To map incoming e-mail addresses to local usernames, edit names.local accord&shy;
ingly:
# postmaster goes to glenda
postmaster
glenda
Note: postmaster@[any domain] will be delivered to local user glenda.
7.7.4 − remotemail
Finally, upas needs to know what to do with mail that cannot be delivered locally. Edit
remotemail and enter the desired behavior.
To deliver mail directly to the remote server responsible for the Internet domain name in
question:
#!/bin/rc
shift
sender=$1
shift
addr=$1
shift
exec /bin/upas/smtp $addr $sender $*
Read: smtp(8)
131
7.7.5 − SMTP over TLS
First, make sure you have already created TLS certificates for your server.
Next, create a file /rc/bin/service/tcp587:
#!/bin/rc
user=‘{cat /dev/user}
exec /bin/upas/smtpd −c /sys/lib/tls/cert −n $3
# to use with listen1, change $3 to $net
7.7.6 − IMAP4 over TLS
First, make sure you have already created TLS certificates for your server.
Next, create a file /rc/bin/service/tcp993:
#!/bin/rc
exec tlssrv −c/sys/lib/tls/cert −limap4d \
−r‘{cat $3/remote} /bin/ip/imap4d −p \
−r‘{cat $3/remote} &gt;&gt;[2]/sys/log/imap4d
# to use with listen1, change $3 to $net
7.7.7 − Spam Filtering
7.7.7.1 − ratfs
From ratfs(4):
Ratfs starts a process that mounts itself (see bind(2)) on mountpoint (default
/mail/ratify). Ratfs is a persistent representation of the local network configu&shy;
ration and spam blocking list. Without it each instance of smtpd(6) would
need to reread and parse a multimegabyte list of addresses and accounts.
To configure the spam blocking list, edit /mail/lib/blocked as desired, according
to the rules laid out in the man page. Example:
# allow messages from any user at 9front.org
*allow 9front.org!*
# block messages from any user at bell−labs.com
*block bell−labs.com!*
# block messages from ip block of aol modems
block
152.166.0.0/15
If ratfs is already running, cause it to reload the modified /mail/lib/blocked:
echo reload &gt;/mail/ratify/ctl
For more details, read: ratfs(4), smtpd(6)
To
launch
ratfs
at
boot
/cfg/$sysname/cpustart:
time,
132
add
the
following
line
to
upas/ratfs
and add the following line to /lib/namespace:
mount −c #s/ratify /mail/ratify
Note: The directory served by ratfs must be visible from the upas listeners names&shy;
pace. Usually, this is accomplished by starting ratfs before the upas listeners.
7.7.7.2 − scanmail
Read: scanmail(8)
7.8 − Web server configuration and maintenance
If you must.
7.8.1 − ip/httpd
No.
7.8.2 − rc−httpd
The rc−httpd web server is a simple shell script that handles static files, directory
listings and drop-in CGI programs such as the werc anti-framework. rc−httpd is run
from a file in the directory scanned by listen(8), or called as an argument to
listen1(8).
Read: rc−httpd(8)
Note: rc−httpd is employed to serve the 9front.org family of websites.
7.9 − TLS certificates
To use TLS-enabled services on a Plan 9 mail server (poptls, apoptls, imaps, etc.) you
need to generate a certificate and key for your mail server and tell the factotum of
the server about that key:
ramfs −p
cd /tmp
auth/rsagen −t &acute;service=tls role=client owner=*&acute; &gt; key
chmod 600 key
cp key /sys/lib/tls/key # or: store key in secstore
auth/rsa2x509 ’C=FR CN=fakedom.dom’ /sys/lib/tls/key | \
auth/pemencode CERTIFICATE &gt; /sys/lib/tls/cert
Note: Here, FR is the two-digit country code, and fakedom.dom is the fully qualified
domain name.
To load the key into the servers factotum at boot time, add the following line to
/cfg/$sysname/cpustart:
133
cat /sys/lib/tls/key &gt;&gt;/mnt/factotum/ctl
134
FQA 8 − Using 9front
i am form china
here is lots of people knows
and documented is chinese
the time comllexity is need you test youself
and you will find it
wenwei peng
When applied consistently, simple conventions can combine to provide powerful results.
In Plan 9, conventions are preferred to rules. This section explores the Plan 9 approach
to actually using the computer.
8.1 − rc
The rc shell was written by Tom Duff for Research UNIX v10. It was later adopted as
the shell for Plan 9. Some of its conventions are unusual compared with other command
interpreters influenced by the Bourne shell. Although its syntax may seem strange at
first, have patience; rc was designed this way on purpose. Once its (few, but powerful)
features are internalized, rc simply gets out of the way.
Read: Rc − The Plan 9 Shell, rc(1)
8.1.1 − Prompts
Creating an rc function with the same name as your prompt allows you to easily
double-click to select at the end of a previously typed line and then send it using the
mouse button 2 menu (see the discussion of rio menus, below). This can be used to
approximate a form of command history (see also the commands &quot; and &quot;&quot;, which print
and execute the previous command, respectively).
135
Add something like this to your $home/profile:
fn term%{ $* }
In rc the ; character forces the end of a line and is treated as a noop when it appears
alone, so it is also possible to create a simple prompt that would require no special
prompt function in order for the prompt to be effectively ignored when selecting and
sending:
prompt=&acute;; &acute;
Obviously, the prompt can be named however the user sees fit.
8.1.2 − /env
Note: Contents of the /env directory are provided by the kernel and represent a sepa&shy;
rate accounting of the shells environment; rc reads /env only on startup, and
flushes/writes /env only before executing programs.
8.2 − rio
rio is the Plan 9 window system. More accurately, rio multiplexes input devices with
and serves a file interface to a series of rectangles, inside the boundaries of which are
drawn an arbitrary arrangement of pixels. Controlling the rectangles is more straightfor&shy;
ward, and at the same time more flexible, than what is commonly expected from most
&quot;window managers.&quot;
Read: rio(1), rio(4)
To effectively use rio, you need a three button mouse. If you only have a two button
mouse you can emulate the middle button by holding down the shift key whilst press&shy;
ing the right button.
136
Note: Button 1, 2, and 3 are used to refer to the left, middle, and right buttons respec&shy;
tively.
8.2.1 − The Pop−up Menu
Pressing and holding down mouse button 3 on the gray desktop or on a shell window
will give you a menu with the following options:
New
Resize
Move
Delete
Hide
Pressing and holding down mouse button 2 on a shell window results in a menu with the
following options:
cut
paste
snarf
plumb
look
send
scroll
Select an item by releasing the button over the menu item. Rio uses the same button
that started an action throughout that operation. If you press another button during the
action the operation is aborted and any intermediate changes are reversed.
Each menu acts as a action verb selector which then requires an object (i.e. window) to
be picked to indicate which window the verb is to act on. A further mouse action may
then be required.
8.2.2 − Window control
Clicking on a window brings it to the front.
You can directly change the shape of a window by clicking and dragging on the edge or
corner of the window border. Mouse button 1 or 2 will allow you to drag the edge or
corner to a new size, and mouse button 3 will allow you to move the window.
The mouse button 3 menu contains a list of all windows that are corrently obstructed by
137
other windows. Selecting a label tops the window.
The pop-up menu remembers the last command chosen, so as a shortcut you can just
press and release button 3 without moving the mouse between pressing and releasing
to select the previous command again.
In addition, rio serves a variety of files for reading, writing, and controlling windows.
Some of them are virtual versions of system files for dealing with the display, keyboard,
and mouse; others control operations of the window system itself. These files, as well as
the window(1) command, allow for controlling windows programmatically by reading
and writing text strings. Thus simplifying the automated opening and placement of vari&shy;
ous windows with user scripts.
Read: rio(4)
8.2.3 − Text in rio windows
Text in a rio window may be freely manipulated, edited, altered, deleted and/or acted
upon using either mouse chords or the options from the mouse button menus. (For an
example, see the discussion of the use of rc prompts, above.)
The special file /dev/text (for the current window), or /dev/wsys/n/text (for
window n) contains all text that has already appeared in the window. The contents of
this file may serve as a primitive form of command history (and may be acted upon
using standard command line tools), but are lost when the window is closed.
Seriously, read: rio(4)
8.2.4 − Scrolling
By default, a rio window will fill up with text and then block, obviating the need for a
separate pager program (though the p(1) pager program still ships with the system).
Endless scrolling may be enabled by selecting scroll from the mouse button 2 menu.
The up or down arrow keys and pgup or pgdwn keys may be used to scroll up or
down in consistently measured increments.
Holding down the shift key and pressing the up or down arrow key will scroll a single
line in the respective direction.
9fronts rio supports mousewheel scrolling. The heuristic employed is roughly the
same as that of clicking in the scrollbar on the left of the window: when the mouse
pointer is near the top of the window the scrolling increment is small, while as the
mouse pointer approaches the bottom of the window the scrolling increment grows pro&shy;
gressively larger. Presently this behavior is limited to rio, sam, and mothra but may
later be extended to other programs.
Note: While the behavior of the arrow and page keys is fairly consistent between pro&shy;
grams, mousewheel scrolling is not. So far, shift + up or down is only supported in
rio windows.
138
8.2.5 − Mouse Chording
Almost anywhere sam(1), acme(1), window(1) you can use the following
mouse chords:
mb1 Select text.
mb1 double click Select word under cursor, or at the end/start of a line, select
the whole line.
After selecting with mb1 and while still holding mb1 down (these chords also
work with text selected by double-clicking, the double-click expansion happens when
the second
click starts, not when it ends):
mb2 Cut text.
mb3 Paste text (can be reverted by clicking mb2 immediately afterwards).
To snarf (copy), click mb2 immediately followed by mb3.
8.2.6 − Keyboard Shortcuts
Almost anywhere sam(1), acme(1), window(1) you can use the following
shortcuts:
Ctrl−u Delete from cursor to start of line.
Ctrl−w Delete word before the cursor.
Ctrl−h Delete character before the cursor.
Ctrl−a Move cursor to start of the line.
Ctrl−e Move cursor to end of the line.
Ctrl−b Move cursor to the position immediately after the prompt. (rio only)
Read: UNIX Keyboard Bindings
In a rio(1) window, scroll up or down one line by holding shift and pressing the up
or down arrow.
8.2.7 − Color scheme
rio looks like this:
139
rios color scheme may be modified by editing the .c configuration files and recompiling:
Note: Someone will mock you for doing this.
See: http://plan9.stanleylieber.com/rio
Rob Pike, rios author, was all like:
the clean appearance of the screen comes mostly from laziness, but the color
scheme is (obviously) deliberate. the intent was to build on an observation by
edward tufte that the human system likes nature and nature is full of pale
140
colors, so something youre going to look at all day might best serve if it were
also in relaxing shades. renee french helped me with the specifics of the
color scheme (shes a professional illustrator and my color vision is suspect),
once id figured out how i wanted it to look. there are still some features of
the color system that i put in that i think no one has ever noticed. thats a
good thing, in my opinion; the colors should fade away, if youll pardon the
expression. having used other systems with different approaches to color
screens, most especially windows XP (extra pukey), i think tufte was right.
Rob Pike, 2003
The color scheme was an attempt to honor a point made originally in a little
brochure by Edward Tufte that the colors of nature are soft and quiet and
peaceful to look at, while most computer screens are covered in glaring bright
colors. When color came to the system I wanted it to be pleasant.
Rob Pike, 2008
See: edwardtufte.com
8.2.8 − Why is rio like this?
Window systems should be transparent. Thats the argument put forward in the famous
paper by rios author, Rob Pike.
141
Beyond this, Rob offered an explanantion (in response to a question on the 9fans mail&shy;
ing list) of some of the choices made in the design of 8&frac12; and rio:
&gt; functioning cursor keys would still be a speed benefit.
This feels true but is false. There were some fascinating experiments done a
few years ago in which people were given a long, tedious editing task. Some
of the people were keyboard fans, some were mouse fans. Both folks were
asked to do the task two ways, in random order, once using the mouse to do
the editing, once using cursor keys etc. Regardless of their predilections,
which was stated up front, after the experiment everyone who did the task
agreed that it was faster to use the keyboard than the mouse to complete the
task. Everyone. Heres the kicker: everyone was wrong. They were being
timed, and in fact the reverse was true. Although they thought the keyboard
was faster, doing the task using the mouse was faster for everyone, by a sub&shy;
stantial fraction.
The explanation, besides the obvious that arrow keys are actually pretty slow
if youre going more than a line or character, is that people feel the mouse
wastes time because you need to grab it and move it, but its time well spent.
The part of the brain that uses keyboard commands to move the cursor is a
higher-order function, and thinking and planning how to use the keys to get
to the destination blocks thinking about the editing task at hand. But using
the mouse is done by a lower-order part of the brain, which keeps the editing
part of the brain clear. Theres less task switching going on when you use the
mouse, so you work more efficiently.
If you dont believe me, the story is here:
http://www.asktog.com/readerMail/1999-12ReaderMail.html
Thanks to some forgotten 9fan who mentioned this a while back. I didnt
know about these experiments when I said, long ago, that using arrow keys to
142
point at a display is like telling someone how to go somewhere by giving
directions, while using a mouse is like pointing at a map. In fact, I never used
a screen editor until I had a mouse, for just this reason.
Rob Pike, 2001
8.2.9 − tips
8.2.9.1 − Taking a screenshot
To capture the entire screen:
topng &lt;/dev/screen &gt;screen.png
To capture only the current window:
topng &lt;/dev/window &gt;window.png
It is also possible to capture other windows:
topng &lt;/dev/wsys/n/window &gt;window.png
where n is the number of the window being captured.
Read: rio(4)
8.2.9.2 − Prevent console messages from overwriting the screen
To capture console messages in a rio window, open a new window and:
cat /dev/kprint
8.3 Text Editors
8.3.1 − sam
The text editor sam was created by Rob Pike for Research UNIX V9 (circa 1986), and
later included with Plan 9.
See: http://sam.cat-v.org
Read:
The Text Editor sam The original paper by Rob Pike.
A Tutorial for the Sam Command Language Documents the editing language.
sam quick reference card
sam(1) man page
143
Dan Flavin, Document for Untitled (to the innovator of Wheeling Peachblow), 1968
8.3.1.1 − Scrolling
9fronts slightly modified version of sam supports mousewheel scrolling in the same
manner as rio.
Read: FQA 8.2.4 − Scrolling
8.3.1.2 − Mouse Chording
9front sam supports the same mouse chording as rio.
Read: FQA 8.2.5 − Mouse Chording
8.3.1.3 − Why does sam have a separate snarf buffer from rio?
The programs author, Rob Pike, says:
was a consequence of running over 1200 baud when sam was first written.
you didnt want every cut and paste to bounce off the remote end at that
speed. nowadays that argument has less weight. on the other hand, i still
kinda like that you can have an editing session that doesnt corrupt what you
have in rios snarf buffer. i tried the unified way in acme and i often (not
always) miss the old way.
Rob Pike, 2003
144
8.3.1.4 − Keyboard Shortcuts
Esc Cut (and consequently, snarf) the selected text.
Ctrl−b Switch focus to the edit window.
8.3.2 − acme
There is also an alternative user interface, acme(4), that some people use as their editor.
Geoff Collyer
Handmade cyclogram by Russian cosmonaut, Georgi Grechko.
145
8.4 − Internet
Sending and receiving bits via alien protocols.
8.4.1 − Mail
Read: mail(1), FQA 7.7 − Mail server configuration and maintenance
8.4.1.1 − upasfs
From upasfs(4):
Fs is a user level file system that caches mailboxes and presents them as a file
system. A user normally starts fs in his/her profile after starting plumber(4)
and before starting a window system, such as rio(1) or acme(1). The file sys&shy;
tem is used by nedmail(1), acme(1)s mail reader, and imap4d and pop3 (both
pop3(8)) to parse messages. Fs also generates plumbing messages used by
biff and faces(1) to provide mail announcements.
Read: upasfs(4), pop3(8), faces(1)
8.4.1.1.1 − Reading gmail via IMAP
upas/fs −f /imaps/imap.gmail.com/[email protected]
The first time this command is run, you should see an error that looks something like
this:
upas/fs imap: server certificate 22471E10D5C1E41768048EF5567B27F532F33
not recognized
upas/fs: opening mailbox: bad server certificate
146
To add this certificate to your system, type:
echo &acute;x509 sha1=22471E10D5C1E41768048EF5567B27F532F33&acute; \
&gt;&gt;/sys/lib/tls/mail
Once upas/fs is running, you can open as many additional gmail mailboxes (labels) as
you wish:
echo open /imaps/imap.gmail.com/[email protected]/yourlabel \
yourlabel &gt;/mail/fs/ctl
Note: upas/fs reads the entire mailbox into RAM, which means it may fail to load
mailboxes that exceed the available system memory. This problem has been addressed
in Erik Quanstroms nupas, which reads the mailbox into an index file, then performs
new operations on the index where possible.
8.4.1.2 − nedmail
nedmail is a command line mail client similar to the classic mail client shipped with
Research UNIX.
Read: nedmail(1)
8.4.1.3 − nupas
Read: Scaling Upas, by Erik Quanstrom
Note: Installing nupas replaces the systems default upas.
README.9front and mkfile before attempting to install.
Read the included
8.4.2 − NNTP
Read: newt(1), nntpfs(4)
8.4.3 − IRC
8.4.3.1 − ircrc
ircrc is an IRC client implemented in rc. It is included with 9front.
Read: ircrc(1)
8.4.3.2 − irc7
A persistent IRC client was written in the c programming language by Andrey Mirt&shy;
chovski. It has been modified slightly by 9front users (mainly, adding an −e flag to the
ircsrv program that implements SSL connections).
147
8.4.4 − FTP
Read: ftpfs(4)
8.4.5 − HTTP
8.4.5.1 − mothra
mothra is a trivial web browser written in 1995 by Tom Duff. It ignores Javascript, CSS
and many HTML tags. It was dropped from Plan 9 after the 2nd Edition, but has been
picked up and (somewhat) refined for 9front. mothra now uses webfs, and no longer
supports non-HTTP protocols.
148
Read: mothra(1), webfs(4)
8.4.5.2 − abaco
no.
8.4.5.3 − hget
hget is a command line HTTP client (similar to programs such as curl or wget) that
started out as a c program in Plan 9 from Bell Labs, but was re-implemented in rc for
9front. hget now uses webfs and no longer supports non-HTTP protocols.
Read: hget(1), webfs(4)
8.4.5.4 − charon
The Inferno operating system can be run hosted on Plan 9, and includes a GUI web
browser called charon, which implements ECMASCRIPT 1.0 as well as additional HTML
attributes.
Note: charon is ancient and is not really a sufficient replacement for 9fronts web
browsers. The rudimentary javascript support can be useful for some simple tasks.
8.4.5.5 − i
There exists an unfinished/buggy port of charon from Infernos limbo programming
language to Plan 9 c.
8.4.6 − SSH
Several SSH clients exist for Plan 9, none of which are perfect.
8.4.6.1 − ssh
9front ships with the original Plan 9 native SSH1 client from Bell Labs.
Read: ssh(1)
8.4.6.2 − ssh2
Programmers at Coraid created a Plan 9 native SSH2 client that was picked up (and com&shy;
pletely rewritten) by Bell Labs. It is currently not included with 9front.
Note: There are bugs and expected features are missing. Consult the source.
149
8.4.6.3 − scpu
Two 9front users (taruti and mischief) worked on an SSH2 client written in the Go pro&shy;
gramming language. It has been extended to work with Plan 9 factotum(4), but still
does not fully honor complex Plan 9 dial(2) strings.
8.4.6.4 − OpenSSH
Plan 9 user fgb ported OpenSSH 4.7p1, OpenSSL 0.9.8g 19 Oct 2007 to Plan 9. It is
available in his contrib directory (on the Bell Labs server), or a 386 binary is available
here (to install, unpack it over /): openssh.tgz.
8.4.6.5 − sftpfs
An implementation of sftpfs was created for Plan 9 that can work with either the native
SSH clients or fgbs OpenSSH port.
8.4.6.5.1 − Mounting a remote u9fs share over SSH
The u9fs program runs on UNIX and serves an unencrypted 9P(2) share. It is possi&shy;
ble to mount such a share over SSH.
With ssh2:
srv −s 5 −e &acute;ssh2 −l sl wm &acute;&acute;/usr/local/bin/u9fs \
−u sl −na none&acute;&acute;&acute; wm /n/wm
With scpu:
srv −s 5 −e &acute;scpu −u sl −h wm −c \
&acute;&acute;/usr/local/bin/u9fs −u sl −na none&acute;&acute;&acute; wm /n/wm
In both cases, an SSH connection is opened to remote UNIX host wm, logged in with user
sl and mounted on Plan 9 under /n/wm.
Read: u9fs(4), srv(4)
8.4.7 − secstore
Typing in lots of passwords over and over again is annoying.
Secstore authenticates to a secure-store server using a password and optionally a hard&shy;
ware token, then saves or retrieves a file. This is intended to be a credentials store
(public/private keypairs, passwords, and other secrets) for a factotum.
Read: FQA 7.4.3 − secstored for information on setting up the secstore server, and: FQA
7.4.3.1 − Adding users to secstore to add users.
Once a user has been added to secstored, the user may add to the file read by
factotum at startup. To do so, open a new window and type
150
% ramfs −p; cd /tmp
% auth/secstore −g factotum
secstore password: [user’s secstore password]
% echo &acute;key proto=apop dom=x.com user=ehg !password=hi&acute; &gt;&gt; factotum
% auth/secstore −p factotum
secstore password: [user’s secstore password]
% read −m factotum &gt; /mnt/factotum/ctl
and delete the window. The first line creates an ephemeral memory-resident work&shy;
space, invisible to others and automatically removed when the window is deleted. The
next three commands fetch the persistent copy of the secrets, append a new secret, and
save the updated file back to secstore. The final command loads the new secret into the
running factotum.
The ipso command packages this sequence into a convenient script to simplify editing
of files stored on a secure store. It copies the named files into a local ramfs and
invokes ditor on them. When the editor exits, ipso prompts the user to confirm
copying modifed or newly created files back to secstore. If no file is mentioned, ipso
grabs all the users files from secstore for editing.
By default, ipso will edit the secstore files and, if one of them is named factotum, flush
current keys from factotum and load the new ones from the file.
Read: secstore(1), secstore(8)
8.4.8 − drawterm
drawterm is a program that users of non-Plan 9 systems can use to establish graphi&shy;
cal cpu connections with Plan 9 cpu servers. Just as a real Plan 9 terminal does,
drawterm serves its local name space as well as some devices (the keyboard, mouse,
and screen) to a remote cpu server, which mounts this name space on /mnt/term and
starts a shell. Typically, either explicitly or via the profile, one uses the shell to start
rio. The original version is effectively abandoned, but is available here:
http://swtch.com/drawterm
151
There also exists a fork of Russ Coxs drawterm to incorporate features from Plan9front
(http://9front.org), most importantly DP9IK authentication support (see authsrv(6)) and
the TLS based rcpu(1) protocol: http://drawterm.9front.org
8.5 − Audio
Read: audio(1), audio(3)
8.6 − External Media
8.6.1 − Mount an ISO9660 CD−ROM
mount &lt;{9660srv −s} /n/iso /dev/sdD1/data # cd−rom drive
or:
mount &lt;{9660srv −s} /n/iso /path/to/9front.iso
Read: dossrv(4)
8.6.2 − Burn a CD−ROM
cdfs
cp 9front.iso /mnt/cd/wd
rm /mnt/cd/wd
Read: cdfs(4)
152
8.6.3 − Mount a FAT formatted USB device
FAT formatted USB devices are automatically mounted under the /shr directory.
Note: Devices must be FAT or FAT32 formatted; exFAT is not supported.
8.7 − Emulation
8.7.1 − Linux Emulation
linuxemu is a program that can execute Linux/i386 ELF binaries on Plan 9. Semimodern web browsers and other Linux programs may be run using linuxemu (if nec&shy;
essary, in conjunction with the equis X11 server).
Note: linuxemu can only be run on a Plan 9 system booted with a 386 kernel and
binaries.
BOOTSTRAP
To run linuxemu, you need a Linux root file system packed into a tarball:
http://felloff.net/usr/cinap_lenrek/mroot-linuxemu.tbz
http://plan9.stanleylieber.com/linuxemu/mroot.tgz
The mroot−linuxemu.tbz version contains no symlinks and can be extracted with
plain Plan 9 tools bunzip and tar.
The
mroot.tgz
version
contains
the
same
Debian
Sarge
base
mroot−linuxemu.tbz, but with several additional packages pre-installed:
9base
153
as
dmenu-4.1.1
dwm-5.8.2
gcc 3.3.5
linux-kernel-headers
mercurial 0.9.4
opera 10.11
python 2.3.5
xlib-dev
and more.
You can create your own mroot with debootstrap on Debian Linux, or help write an
installer that unpacks and installs an alternative distribution on Plan 9... In any case,
linuxemu is not hardwired to any Linux distribution!
RUNNING
Use the provided linux script to chroot into your Linux mroot. The linux script is
neccesary because for Linux programs to run, shared libraries from your mroot have to
appear in its /lib and /usr/lib directories, while configuration files are expected to
be in /etc. The script will build a private namespace and then bind the Linux mroot
over the Plan 9 root. The original Plan 9 namespace is mounted within linuxemu
under /9.
Assuming mroot is located in the current directory, start linuxemu like this:
linux −r ./mroot /bin/bash −i
If the −r option is omitted, the Linux mroot defaults to /sys/lib/linux on the
Plan 9 machine.
In the Linux mroot, /etc/resolv.conf should be changed to match your network
nameserver. In addition, /etc/apt/sources.list should be updated to a working
Debian mirror. Sarge packages can still be accessed at:
deb
main
http://archive.debian.org/debian−archive/debian
sarge
EXAMPLES
Linux X11 programs may be used in conjunction with the equis X11 server. For
example, to run the Opera web browser under your Linux mroot, start equis in a
rio window, start linuxemu in another rio window and then from within
linuxemu:
dwm &amp; # X11 window manager
opera &amp; # web browser
154
Opera should (eventually) appear in the equis window. A window manager (this exam&shy;
ple uses dwm) is recommended so that X11 programs interact with window resources
properly.
DEBUGGING
If linuxemu crashes, use acid to figure out whats going on:
mk acid
acid −l linuxemu.acid &lt;pid&gt;
Then you can issue the following commands:
ustk()
dump a (userspace) stacktrace for the current thread:
umem(Current())
ufds(Current())
utrace(Current())
dump the
dump the
dump the
(enabled
memory mappings
filedescriptor table
internal tracebuffer
by −d option)
Use xasm() and xcasm() for disassembly for Linux code.
Read: acid(1)
You can also enable full trace logging:
linux −r ./mroot −dd /bin/bash −i &gt;[2]/tmp/linuxemu.log
This slows linuxemu down considerably. In case of race conditions, it often happens
that the bug disapears when doing full trace logging!
8.7.2 − Nintendo
Emulators for several Nintendo video game consoles ship with the system:
155
gb Game Boy
gba Game Boy Advance
nes Nintendo Entertainment System
snes Super Nintendo Entertainment System
Read: nintendo(1)
8.7.3 − Sega
An emulator for the Sega Megadrive/Genesis video game console ships with the system:
md Sega Mega Drive/Genesis
Read: sega(1)
156
8.7.4 − Commodore
An emulator for the Commodore 64 home computer ships with the system:
c64 Commodore 64
Read: commodore(1)
8.8 − Additional Software
8.8.1 − 9front sources server
Additional 9front software is available from a 9P share that is accessible from any Plan 9
system:
9fs 9front
The following files and directories will then be available under /n/:
9front/ 9front source
9front.torrent torrent of current 9front ISO image
bugs/ bug reports
contrib/ user contributed software
extra/ third party software source
fqa/ troff sources for 9front Frequently Questioned Answers
hardware/ known working hardware (sysinfo, firmware, manuals, etc.)
157
iso/ current 9front ISO image(s)
sources/ mostly complete mirror of Bell Labs sources server
8.8.2 − 9front contrib
Some 9front users maintain a contrib directory on an official 9front 9P share (similar to
the contrib arrangement provided by Bell Labs) that is accessible from any Plan 9 sys&shy;
tem:
9fs 9front
User directories will then be available under /n/contrib/.
8.8.3 − Other public 9p servers
A
list
of
active
public
9p
servers
http://www.9paste.net/qrstuv/9pindex
is
maintained
here:
8.9 − Bootstrapping architectures not included on the ISO
8.9.1 − amd64
To setup the amd64 port, install the 386 port from the ISO, then cross compile and
install the amd64 binaries and kernel.
Read: FQA 5.2.2.1 − Cross compiling, FQA 7.2.5 − How do I install a new kernel?
8.9.2 − Raspberry Pi
The most convenient way to use an rpi is to cross compile and install the arm binaries
and the bcm kernel on the network file server, and then tcp boot the rpi.
Read: FQA 5.2.2.1 − Cross compiling, FQA 6.7.1 − How do I tcp boot?
Outdated and possibly confusing instructions for installing directly onto the rpis sd
card are detailed in Appendix J − Junk
158
8.10 − ACPI
Plan9front currently has partial ACPI support for PCI interrupt routing and system shut&shy;
down.
8.10.1 − Enabling ACPI
ACPI is enabled with the presence of *acpi= boot parameter.
This will create the /dev/acpitbls file that can be used to read the systems acpi
tables. Specifying *acpi=0 will make acpi tables accessible thru the file but not use it
in the kernel.
8.11 − MP Table Override
This horrible hack should be considered obsolete, in particular with the implementation
of APIC renaming and MSI. It might still be useful.
Since some motherboard/BIOS manufacturer dont care about anything but ACPI, the MP
table might be in an unusable state which meant that *nomp=1 had to be used. The
new MP Table Override can be used to specify an entirely different MP table for 9front to
use.
To specify an MP table the *mp and *mpN options are used, for example (for illustration
purposes, not a valid mp table):
*mp=16
*mp0=00 11 33 13 15
*mp1=16 99 DD 1C
*mp2=9F 81 2a 0a 7b 8c 1c
*mp specifies the size in byte and *mpNR, where N is a consecutive number starting
with zero, specifies the data in hex form.
159
The in-hardware table can be dumped with *dumpmp=1 (PROTIP: use a serial console).
/sys/src/9/pc/mp.h is useful to have handy.
To Do
(Some are mutually exclusive)
&quot; Write an utility to generate a proper table from Linux or similar
&quot; Write user space tools to manipulate the mp table
&quot; Calculate size automatically (and drop *mp)
&quot; Use a text based format parsed by the kernel
&quot; Fix MP support altogether (might not be feasible)
Example
For the HP Compaq DC5700:
160
*mp=528
*mp0=00 00 10 03 65 0f 00 00 ff fb eb bf 00 00 00 00
*mp1=00 00 00 00 00 01 10 01 65 0f 00 00 ff fb eb bf
*mp2=00 00 00 00 00 00 00 00 01 00 50 43 49 20 20 20
*mp3=01 01 50 43 49 20 20 20 01 07 50 43 49 20 20 20
*mp4=01 20 50 43 49 20 20 20 01 ff 49 53 41 20 20 20
*mp5=02 02 11 01 00 00 c0 fe 03 00 0f 00 00 08 02 10
*mp6=03 00 0f 00 00 09 02 11 03 00 0f 00 00 0c 02 10
*mp7=03 00 0f 00 00 0d 02 11 03 00 0f 00 00 0e 02 12
*mp8=03 00 0f 00 00 74 02 14 03 00 0f 00 00 75 02 15
*mp9=03 00 0f 00 00 76 02 16 03 00 0f 00 00 77 02 17
*mp10=03 00 0f 00 00 68 02 14 03 00 0f 00 00 69 02 15
*mp11=03 00 0f 00 00 6a 02 16 03 00 0f 00 00 01 02 13
*mp12=03 00 0f 00 00 6c 02 15 03 00 0f 00 00 7c 02 11
*mp13=03 00 0f 00 00 7d 02 12 03 00 0f 00 00 7e 02 12
*mp14=03 00 0f 00 00 70 02 14 03 00 0f 00 00 71 02 15
*mp15=03 00 0f 00 00 72 02 16 03 00 0f 00 00 73 02 17
*mp16=03 00 0f 00 07 10 02 14 03 00 0f 00 07 11 02 15
*mp17=03 00 0f 00 07 12 02 16 03 00 0f 00 07 13 02 17
*mp18=03 00 0f 00 07 24 02 15 03 00 0f 00 07 25 02 16
*mp19=03 00 0f 00 07 26 02 17 03 00 0f 00 07 27 02 14
*mp20=03 00 0f 00 07 2c 02 16 03 00 0f 00 07 2d 02 17
*mp21=03 00 0f 00 07 2e 02 14 03 00 0f 00 07 2f 02 15
*mp22=03 00 0f 00 07 34 02 14 03 00 0f 00 07 35 02 15
*mp23=03 00 0f 00 07 36 02 16 03 00 0f 00 07 37 02 17
*mp24=03 00 0f 00 20 00 02 10 03 00 0f 00 20 01 02 11
*mp25=03 00 0f 00 20 02 02 12 03 00 0f 00 20 03 02 13
*mp26=03 00 00 00 ff 01 02 01 03 00 00 00 ff 03 02 03
*mp27=03 00 00 00 ff 04 02 04 03 00 00 00 ff 06 02 06
*mp28=03 00 00 00 ff 07 02 07 03 00 00 00 ff 08 02 08
*mp29=03 00 00 00 ff 09 02 09 03 00 00 00 ff 0c 02 0c
*mp30=03 00 00 00 ff 0d 02 0d 03 00 00 00 ff 0e 02 0e
*mp31=03 00 00 00 ff 0f 02 0f 04 01 00 00 ff 00 ff 01
*mp32=01 3f 50 43 49 20 20 20 03 00 0f 00 3f 00 02 11
8.12 − Revision Control
8.12.1 − cvs
OpenCVS was ported to Plan 9.
An implementation of a cvs file server, called cvsfs, was also created for Plan 9.
8.12.2 − git
More than one person has claimed to have ported git to Plan 9, but no code has ever
been made public. Please stop telling unsuspecting newbs that git is available for Plan
9.
In the meantime, someone wrote a shell script wrapper that attempts to replicate some
basic git actions by downloading a zip file from the repository and performing opera&shy;
tions on it.
161
8.12.3 − Mercurial
9front ships with Mercurial.
Read: FQA 5.2.1.1 − hgrc
8.12.4 − svn
No.
162
FQA 9 − Troubleshooting
9.1 − First
&quot; STATE YOUR ASSUMPTIONS.
&quot; cat /etc/os−release to verify you are not, in fact, running Ubuntu Linux
with a Plan 9 theme.
&quot; Are you running drawterm?
&quot; Verify your OpenBSD configuration.
163
&quot; Are you using the qwerty keyboard layout?
&quot; Before reporting a bug, try the latest ISO image.
&quot; MAKE SENSE.
&quot; When all else fails, see: FQA 2.4 − Reporting Bugs
9.2 − Booting
9.2.1 − Boot parameters
&quot; Immediately after the BIOS screen, hit any key until you see the &gt; prompt. From
there, values from plan9.ini may be temporarily added or changed. Read:
9boot(8)
&quot; Boot parameters beginning with a * are interpreted by the kernel. All other
parameters are passed as enviroment variables to the boot process.
&quot; Adding or changing a parameter: param=value
&quot; Removing a parameter: clear param=
&quot; When finished, type boot to resume booting.
9.2.2 − Break into a shell
At the [bootargs] prompt, type !rc and hit enter to break into a shell. Type exit
to return to the [bootargs] prompt.
164
9.2.3 − Editing plan9.ini
&quot; It is not possible to edit plan9.ini stored on the ISO, but parameters can be
changed temporarily before booting. See above.
&quot; On a harddrive installation, plan9.ini is stored with the bootloader and the
kernel in a small FAT partition called 9fat at the beginning of the plan9 parti&shy;
tion. The 9fat can be mounted by executing 9fs 9fat from the livecd or the
installed system. The file /n/9fat/plan9.ini can then be edited with a text
editor like acme(1), sam(1) or ed(1).
&quot; If your change to plan9.ini or the 9fat made the system unbootable, it is
always possible to manually override parameters on the &gt; prompt (see above) or
start the system from the livecd and pick your installed cwfs or hjfs partition on
the [bootargs] prompt. Example: local!/dev/sdC0/fscache
9.2.4 − Boot media not recognized
&quot; Break into a shell, then type grep −n ’^01’ ’#$/pci/’*ctl to get the
pci vid/did of the installed disk controllers. then look in the sd drivers to see if the
controller is already recognized.
&quot; Sometimes, there is a problem with the drive, not the controller.
/dev/sd*/ctl to get the status of the individual drives.
cat
&quot; Try different BIOS settings like AHCI/IDE mode.
&quot; Try the USB troubleshooting steps (see below). Sometimes USB problems prevent
unrelated devices from working properly.
9.2.5 − I moved my hard drive between ports
If your file system is cwfs(4):
&quot; Lets assume it went from sdE0 to sdE1.
&quot; At the bootargs prompt:
local!/dev/sdE1/fscache −c
filsys main c(/dev/sdE1/fscache)(/dev/sdE1/fsworm)
filsys dump o
filsys other /dev/sdE1/other
end
9.3 − Graphics
165
9.3.1 − Rio fails to start
See the discussion of graphics in FQA 4 − 9front Installation Guide. When you find a
working mode, update your plan9.ini.
9.3.2 − VESA BIOS does not contain a valid mode
The standard solution is to have the customer send the computer back to the manufac&shy;
turer, who reflashes the EEPROM with the correct information and return the computer
to the customer.
9.4 − Networking
9.4.1 − Networking is not working
Read: FQA 6.2.8 − Verifying network settings
9.4.2 − Cannot resolve domain names
If ndb/dns is running but you are still unable to resolve domains, you can try adding a
DNS server directly to /net/ndb.
Read: FQA 6.2.5 − DNS Resolution
9.4.3 − /mnt/web/clone does not exist
Programs that require webfs(4) to be running require webfs(4) to be running.
Read: hget(1), mothra(1)
9.4.4 − PCMCIA WiFi stopped working after reboot
Do fshalt and power down completely instead of just rebooting with fshalt −r.
9.5 − USB
9.5.1 − Devices not recognized or not working
&quot; Break into a shell, or simply type in a rio window: cat /dev/usbevent
and try plugging in a USB device. If the devices where detected, some output
should appear on screen. This doesnt mean we have a working driver for it but
verifies that the USB controller and HUB driver recognized the device.
&quot; Dump USB controller status to the console with
echo
dump
&gt;/dev/usb/ctl after that, you might recover the output from /dev/kmesg or
run cat /dev/kprint in a separate rio window to not spill it all over the
166
screen. Check the nintr and tdintr counters to see if they are all zero. If thats
the case, then this is might be a interrupt routing problem sometimes caused by
broken/incomplete BIOS MP tables. See below.
&quot; If USB keyboard is the only option, try to enable PS2 emulation in the BIOS and
disable kernel usb support. See below.
&quot; if the machine employs a USB3.0 (xHCI) controller, try to disable USB3.0 support
in BIOS as we dont have a driver for the xhci yet.
9.5.2 − System freezes after showing memory sizes
&quot; The boot parameter *acpi=1 might solve interrupt routing problems in the
case of broken or incomplete BIOS MP tables. (acpi is still experimental)
&quot; Try the boot parameter *nomp= to disable multiprocessor mode.
&quot; Try the boot parameter *nousbehci= (This disables USB 2.0.)
&quot; Try the boot parameter *nousbuhci=
&quot; Try the boot parameter *nousbohci=
&quot; Try the boot parameter *nousbprobe= (This disables USB completely)
9.6 − auth
9.99999999999999999999999999999999999999 − GIVE UP
Give up now.
Go away.
167
Every joke is a tiny revolution
George Orwell
168
Appendix J − Junk
Raspberry Pi
Prebuilt image
sdcard image available for the raspberry pi:
http://felloff.net/usr/cinap_lenrek/9front-pi-3125.9fcca5b8ac11.img.bz2.torrent
http://intma.in/downloads/9front-pi-3125.9fcca5b8ac11.img.bz2
I used Richard Millers pi.uboot.sd.img as a base, you may want to update the
firmware on the FAT partition with files from here:
https://github.com/raspberrypi/firmware
older versions:
9front 95b0756087eb from Sun Oct 20 22:38:35 CES 2013
http://intma.in/downloads/9front_pi.img.gz.torrent
http://intma.in/downloads/9front_pi.img.gz
Installation Instructions
If you dont want to use the provided image, follow these instructions to make your
own. You dont need a computer capable of running 9front, qemu will suffice.
169
Image
Make a FAT partition containing all the necessary files to boot the Raspberry Pi. An easy
way to do this is to use Richard Millers pi.uboot.sd.img (its small). Write it to
your SD card or do the following if youre using qemu (installing to an SD card directly
from qemu was very slow for me):
# set count to the size you want your image to be
# (in 512b units, see dd manpage)
dd if=/dev/zero of=9front−pi.img count=3782016
# copy minimal image to beginning of the newly created image
dd if=pi.uboot.sd.img of=9front−pi.img conv=notrunc
Boot and Installation
Now boot from the 9front CD. For qemu see FQA 3.3.1 - qemu, this is what I did:
qemu−system−i386 \
−enable−kvm \
−drive file=9front−pi.img,if=virtio \
−cdrom 9front−3125.9fcca5b8ac11.iso \
−boot d
Now do the installation (see FQA 4 - 9front Installation Guide for help), use hjfs.
Since you dont need a 9fat partition, you may want to delete the automatically created
partitions and create your own (start at sector 2 or prepdisk will complain). Note that
since youve removed 9fat, the installer will prompt you to do the prepdisk step again,
just type the next step in manually.
After the installation you have a 9front system that only has 386 binaries. The next step
is compile the arm binaries.
Compiling for ARM
Reboot and boot from CD again, but this time use the newly created partition as root
(e.g. local!/dev/sdF0/fs)
Before compiling you need to create some directories under /arm/bin:
echo allow &gt;&gt;/srv/hjfs.cmd
# allow changing ownership of files
cd /arm/bin
for(i in audio auth aux bitsy btc dial disk fs games ip ip/httpd ndb nusb replic
mkdir $i
chgrp −u sys $i
chgrp sys $i
}
Then compile everything:
cd /sys/src
objtype=arm mk install
cd 9/bcm
mk install &amp;&amp; mk install ’CONF=picpuf’
170
And copy the kernel to the FAT partition:
dossrv &gt;/dev/null &gt;[2]/dev/null
mount −c /srv/dos /n/dos /dev/sdF0/dos
cp /arm/9pif /arm/9picpuf /n/dos
Then set the kernel in /n/dos/config.txt to 9pif or 9picpuf for terminal or
cpu kernel and boot the image with the Raspberry Pi. At this point you can delete the
386 binaries if you dont need them.
Once booted on the Raspberry Pi, youre able to mount the dos partition with:
9fs pidos
This will mount the dos partition on /n/pidos, similar to how 9fs 9fat works.
171
FQA Appendix L − Languages
C
Read: Plan 9 C Compilers, How to Use the Plan 9 C Compiler
C++
Read: Bjarne Stroustrup: &quot;I Did It For You All...&quot;
172
C#
Go
173
# automatically converted ca certs from mozilla.org
hget http://curl.haxx.se/ca/cacert.pem &gt;/sys/lib/tls/ca.pem
# shell script that emulates git commands
hget http://9front.org/extra/rc/git &gt;$home/bin/rc/git
chmod 775 $home/bin/rc/git
# fetch the repository
git clone https://go.googlesource.com/go
cd go
git checkout go1.4.2
# build go
cd src
./make.rc
# install documentation
go get golang.org/x/tools/cmd/godoc
# go!
Read: Documentation − The Go Programming Language
Haskell
174
Perl
Perl 5.8.0, ported to Plan 9: http://plan9.bell-labs.com/sources/extra/perl.iso.bz2
PHP
175
Python
Python 2.5.1 is included with the 9front distribution, not because anyone loves Python,
but because it was required by Mercurial (also loved by no one), which was required by
Google Code (shutting down in 2015). An abject lesson in expediency.
Jeff Sickel ported Python 2.7 to Plan 9.
Ruby
Read: Ruby is Not Even Funny
176
">
Bonjour ! Je suis un chatbot IA spécialement formé pour vous aider avec le 9front 9front FAQ. J'ai soigneusement étudié le document et je peux vous aider à trouver les informations dont vous avez besoin ou expliquer le contenu en termes clairs et simples. Que vous recherchiez des conseils sur des fonctionnalités spécifiques, des étapes de dépannage ou une utilisation générale, n'hésitez pas à poser vos questions. Plus vous fournissez de détails sur vos préoccupations ou besoins, plus je pourrai vous aider avec précision et efficacité.
Assistant en train d''écrire
L''assistant n''est plus disponible. Veuillez réessayer plus tard.
Il semble que vous ayez accédé à un document rédigé en plusieurs langues, dont une qui n''est pas votre langue maternelle. Vous pouvez utiliser les liens suivants pour masquer temporairement les pages sans la langue que vous préférez.