These pages on The NetBSD Foundation's internal Kerberos deployment are being migrated to https://www.NetBSD.org/developers/kerberos.html.
First, Kerberize your system. Then:
Firefox
- Open Firefox.
- Go to about:config.
- Filter for
network.negotiate-auth. - Set
network.negotiate-auth.trusted-uris(notnetwork.negotiate-auth.delegation-uris) tonetbsd.org. - (Windows only) Filter for
use-sspi, then setnetwork.auth.use-sspitofalse.
Konqueror
Possibly the same as Safari?
Safari (Mac OS X)
- Open Safari.
- There is no Step 2.
Google Chrome
Run Chrome with the
--auth-server-whitelistargument. For example, in Mac OS X:$ open /Applications/Google\ Chrome.app --args --auth-server-whitelist="*.netbsd.org"
Internet Explorer
Internet Explorer can use Microsoft's built-in Kerberos. Anyone know how? Some possibly relevant links:
Sadly, it seems MS IE can only use tickets cached inside LSA (Local Security Authority), and this cache is only created upon logon through winlogon service. Which means that a
host/<windows_machine>principal would be needed for each Windows client that wants to cache a TGT. This is only suitable for Intranet-like networks. Maybe there is another way to manage the LSA after login, similar to kinit(1)... --jym
Getting access
- Developer? Set a password. Non-developer? Bear with us. For now, please freely add comments to pages.
Creating page "Foo Bar"
Editing page "Foo Bar"
Use the Edit link in the Wiki drop-down menu. For markup advice while editing, see the FormattingHelp link at bottom. Or cheat: use the Source link (also under Wiki) on a page that does what you want.
When you save, your changes are committed to wikisrc, and the
pages affected by your edit are automatically regenerated. Your
change will be displayed in RecentChanges as type web.
Previewing your changes
Use the Preview button at bottom.
These pages on The NetBSD Foundation's internal Kerberos deployment are being migrated to https://www.NetBSD.org/developers/kerberos.html.
Why enable Kerberos on your system?
Convenience and security. With Kerberos, a single login grants access to all NetBSD web services. Configuration is easy and you only have to do it once (sometimes less).
NetBSD
Create a file ~/.krb5/config with the following contents:
[libdefaults]
name_canon_rules = as-is:match_domain=netbsd.org
NetBSD will now autodiscover and uses the NETBSD.ORG KDC as defined in DNS. To use Kerberized TNF services, log in with your Kerberos password:
$ kinit <username>@NETBSD.ORG
The right-hand side is a Kerberos realm, not a DNS domain. Case is significant!
Mac OS X
OS X autodiscovers and uses the NETBSD.ORG KDC as defined in DNS. To use Kerberized TNF services, log in with your Kerberos password:
Launch
Ticket Viewer.appfrom/System/Library/CoreServicesPress the "Add Identity" button
In the identity field enter your
<username>@NETBSD.ORGThe right-hand side is a Kerberos realm, not a DNS domain. Case is significant!
Enter the password associated with this identity in the password field
By default Ticket Viewer.app will save password details in keychain, un-tick "Remember password in my keychain" if this is not desired behaviour
Press continue
If successful, you'll be returned to the main window with a new entry below the icons containing <username>@NETBSD.ORG and the date and time which the ticket obtained is due to expire.
Alternately, from the command line:
koolaid:~ 196> kinit <username>@NETBSD.ORG
<username>@NETBSD.ORG's Password:
koolaid:~ 197>
The klist command will show current tickets. Additionally, a kinit created entry will show up in Ticket Viewer.app.
Windows XP
Windows does not provide an easy way to configure and use KDCs different from the one embedded into an Active Directory.
Therefore, to use Kerberos, you should follow the following steps:
Download the MIT Kerberos for Windows installer. It is composed of different tools traditionally found with Kerberos distributions, like kinit(1) or klist(1), and a Network Identity Manager, an application used to manage credential caching of Kerberos tickets.
Install the package. Use the default provided options, then restart the computer.
The Network Identity Manager (PDF) should automatically start when you login. As there is no principal currently configured, it should open a dialog box to obtain the new credentials.
Enter your principal:
Username: Realm: NETBSD.ORG
Click
Ok. After a few seconds, it should obtain the TGT for you from the NETBSD.ORG KDC.
Orange 
moo test
THIS PAGE NEEDS AN UPDATE BECAUSE been a while since he looked like that
This site
You can mostly point a finger at me for how wiki.netbsd.org works (or sometimes doesn't).
If you've got an idea about how it ought to, edit the todo list!
Here's what's been done so far.
qmail-run from pkgsrc
Start with my overview of qmail patches and packages, particularly qmail-run.
schmonz.com blog posts
These pages on The NetBSD Foundation's internal Kerberos deployment are being migrated to https://www.NetBSD.org/developers/kerberos.html.
What TNF uses this password for
Anything not requiring the maximum level of trust. For example: integrated single sign-on authentication for the wiki, blog, and other web apps.
What TNF will never use this password for
Anything requiring the maximum level of trust. For example: write access to source trees.
How to set your Kerberos password initially
$ ssh -t <username>@cvs.netbsd.org pwstore
How to change your Kerberos password
$ ssh -t <username>@mollari.netbsd.org passwd -k <username>@NETBSD.ORG
How to reset a forgotten Kerberos password
Send mail to admins@netbsd.org and request to clear your password. Then set a new initial password like above.
How to use your Kerberos password
Welcome to my spot on the NetBSD wiki
Random work and ideas
- Keylock support for kauth(9): keylock
- Playing with sensors sensors
- I brought this programming language to NetBSD: dingbat.pdf
My company
- My company: https://msys.ch/
- Our product: https://arcapos.swiss/
Stuff I'm to blame for
- rewrote the interrupt handling code in ?macppc, made it machine independent enough to work on other PowerPC platforms as well
- rewrote the ADB subsystem used on ?macppc and probably ?mac68k - no more phantom events, keyboard LEDs work now, mouse button emulation, support for ?cuda's i2c bus, all in all it's much smaller and simpler than the old code
- wrote a bunch of graphical console drivers ( see below )
- wrote a bunch of Xorg/XFree86 drivers
- added generic support for virtual consoles, scrollback buffers etc. to wscons
- ?wscons-ified ?sparc64
- added provision to allow console drivers to be machine independent
- made ?Xorg work on ?macppc, ?shark, ?sgimips, ?sparc and ?sparc64
- craploads of bugfixes and other minor improvements
Drivers I wrote:
- ?cuda - the microcontroller found on older PCI PowerMacs, provides ADB, realtime clock, nvram, power control and in some cases an i2c bus
- ?pmu - the microcontroller found in PowerBooks, iBooks and newer pre-G5 PowerMacs, provides realtime clock, nvram, power control and sometimes ADB, battery, environmental sensors or volume and brightness control
- ?nadb - ADB device discovery, attached to ?cuda or ?pmu
- ?adbkbd - driver for ADB keyboards, includes emulation for mouse buttons 2 and 3
- ?adbms - driver for ADB mice and trackpads. Supports tapping on trackpads.
- ?adbbt - driver for volume, brightness etc. control keys found on some PowerBooks and all(?) iBooks
- ?sgsmix - additional mixer chip found in beige G3 Macs, supports additional bass and treble control, requires ?cuda since it's controlled via i2c which the old ADB subsystem does not support
- ?dbri - a driver for the ISDN / audio chip found in the SPARCstation 20 and SPARCbook 3GX, it's audio only, there is no support for the ISDN part
- ?panel - driver for the buttons on the SGI Indy's front panel
- agten - accelerated console driver for Fujitsu AG-10e SBus graphics boards
- cgtwelve - a console driver for Sun CG12 / Matrox SG3 graphics boards
- ?chipsfb - accelerated console driver for Chips & Technologies 65550 graphics controllers
- genfb - a generic framebuffer console driver. Depends on machine-dependent code to pass setup information as device properties
- ?gfb - dumb framebuffer console driver for Sun ?XVR-1000 graphics boards
- pm2fb - accelerated console driver for Permedia 2 graphics controllers
- ?r128fb - accelerated console driver for ATI Rage 128 graphics controllers
- ?voodoofb - accelerated console driver for 3Dfx Voodoo 3 graphics controllers
- ?voyagerfb - accelerated console driver for Gdium Liberty MIPS-based laptops
- wcfb - console driver for 3Dlabs Wildcat graphics boards
- ?xf86-video-ag10e - accelerated Xorg driver for Fujitsu AG-10e graphics boards
- ?xf86-video-crime - accelerated Xorg driver for the SGI O2's onboard rendering engine
- xf86-video-igs - accelerated Xorg driver for IGS CyberPro 2010 and similar chips, tested on ?shark only but supporting at least ?netwinder should be trivial
- ?xf86-video-pnozz - accelerated Xorg driver for the SBus Weitek P9100 found in SPARCbook 3GX laptops
Drivers I substantially improved
- igsfb - added mode setting support
- ?machfb - added hardware acceleration
- ?pnozz - added hardware acceleration and cursor sprite support
- ?crmfb - added hardware acceleration, cursor sprite, DDC2 and mode setting support
- ?tcx - added hardware acceleration
- ?tslot - adapted from OpenBSD, support for the PCMCIA slots in the SPARCbook 3GX
- ?xf86-video-suncg6 - added hardware acceleration
- ?xf86-video-suntcx - added hardware acceleration
TODO:
- figure out why anti-aliased font rendering with ?XAA in ?Xorg 1.6 is ridiculously slow compared to 1.4
Actually there is some progress. The miGlyphs() function uses a scratch pixmap to render characters into which it then renders into the target pixmap. Since off-screen pixmaps in XAA are currently broken and the Xorg people refuse to fix it the scratch pixmap will be in RAM with all XAA drivers resulting in software rendering ( not that XAA knows how to accelerate vram-to-vram composite ops anyway ). I got around that by implementing a private Glyphs() method for the crime driver which gives a nice speedup but still gets us nowhere near the performance we had with Xorg 1.4. A private Glyphs() implementation for XAA which avoids the scratch pixmap resulted in a small but measurable speedup with the ?sunffb driver. - add acceleration to Xorg's ?sunleo driver
I have some docs and hardware but the docs are incomplete - the way WIDs are encoded is missing and I can't find one that by default gives us a 24bit RGB or BGR display. - implement mode setting for ?voodoofb, ?voyagerfb, ?r128fb, ?chipsfb etc.
- figure out how to do composite ops on Fujitsu's AG-10e graphics board
- figure out how to use the SX rendering engine on Sun ?SparcStation 20 mainboards
I have a disassembler dump of Sun's own DDX, it shouldn't be all that difficult to do basic blitter operations. The SX itself could probably accelerate composite ops as well but there's no chance to do that without actual documentation.
Jonathan Kollasch
ddb(4) tips
locating a softc
This locates a device's softc using it's cfdriver_t (e.g. &mainbus_cd, &cpu_cd) and its "device unit" (e.g. the 0 in mainbus0).
db{0}> call device_lookup_private(ohci_cd, 0)
0xffff800045fb2008
locating structure members
This uses gdb(1) and a kernel with debugging symbols to find the offset to a element in a structure.
$ gdb netbsd.gdb
...
(gdb) print &((struct ohci_softc *)0)->iot
$3 = (bus_space_tag_t *) 0x478
(gdb) print &((struct ohci_softc *)0)->ioh
$4 = (bus_space_handle_t *) 0x480
peeking at mapped registers
db{0}> call bus_space_read_4(*(ffff800045fb2008+478), *(ffff800045fb2008+480), 0)
0x110
Unfinished Projects
x86 UEFI kernel loader
Needs more work and cleanup. Work has been done using the OVMF BIOS images for Qemu.
bcm47xx for evbmips
Boots multiuser on NFS root, needs more work and cleanup. This project is on hold until there's a miniature userland that fits in 4-8MiB flash storage devices, on a flash-oriented file system. bce(4) and bwi(4) would need refactoring to be bus-independent.
Memory-mapped PCI config access on x86
Needs cleanup, and maybe some more validation of MCFG tables.
Hiya.
Getting wikisrc
$ cvs -d <username>@wiki.netbsd.org:/cvsroot get wikisrc
wiki.netbsd.org != cvs.netbsd.org, so your SSH public keys
can drift out of sync; if they've drifted so far that you can't fix
it yourself, file a ticket to admins@ requesting that they copy
your keys over from nbcvs.
Creating page "Foo Bar"
$ cd .../wikisrc
$ echo '[[!meta title="Foo Bar, or, A Nice-Looking Title"]]' > foo_bar.mdwn
$ $EDITOR foo_bar.mdwn
$ cvs add foo_bar.mdwn
$ cvs commit -m "all about Foo Bar" foo_bar.mdwn
Editing page "Foo Bar"
$ cd .../wikisrc
$ $EDITOR foo_bar.mdwn
$ cvs commit -m "more about Foo Bar" foo_bar.mdwn
When you commit to wikisrc, the pages affected by your edit are
automatically regenerated. Your change will be displayed in
RecentChanges as type cvs.
Previewing your changes
See Preview setup page.
Also known as billc
Internet Relay Chat (IRC) on irc.freenode.net
These are rules and guidelines for discussions in the public channels.
#NetBSD
This is a general chat channel for NetBSD users and developers who interface between the users and the source trees. This is a good place for new users to get help with problems they are having with release builds, as well as leading-edge users who are tripping over bugs in our current development tree. These channels are not a replacement for the bug-reporting system of GNATS or the mailing lists, but function as an enhancement of more 'real-time' discussion. It is quite common that the response to a question will be to search the mailing lists, or to open a bug report. The conversation in this channel is not too strict, but it is appreciated if people stay on the NetBSD topic or at least keep off-topic conversations within reason so as to not annoy the patrons of the channel.
The target audience is NetBSD users, and is architecture-agnostic.
#pkgsrc
This is an OS-agnostic channel for pkgsrc and pkgsrc-wip users and developers. There are a couple of 'bots' in the channel that will display source commits to the channel for the public GIT repository and the pkgsrc-wip tree hosted on SourceForge. This channel is specifically for discussion of pkgsrc, changes to pkgsrc, and suggestions to pkgsrc, and not a general chat channel. This place is good for bootstrap help that you can't find on the mailing lists or documentation.
The target audience is pkgsrc developers and users.
#NetBSD-code
This is a channel specifically for discussion of NetBSD source changes, ideas,
The target audience is developers and Google Summer of Code students.
Offshoot channels for specific working groups of NetBSD, such as #netbsd-ru
- [[#pkgsrc]]
My talk about NetBSD in Hungarian language (Software Freedom Day 2009, Szeged):
http://videos.flosszine.org/2009/10/16/netbsd-bemutatasa-es-desktop-hoka-adam/
this contains a random collection of info about the NetBSD.org servers. Unless specified they are at TastyLime and owned by TNF. Note the time of last commit, the info may be seriously out of date.
we currently (2024-05-01) have:
public services:
homeworld (mail.NetBSD.org, ns.NetBSD.org)
That's a standard postfix with gld, amavisd, spamassassin for mail, a majordomo with a few local patches (and the despamming patterns from hell), plus bind for the nameservice.mollari (wiki.NetBSD.org, releng.NetBSD.org, gnats.NetBSD.org, back-end for www.NetBSD.org and mail-index.NetBSD.org which are on the Fastly CDN)
Apache, with ikiwiki for this wiki, plus req for the releng site, gnats, and a very much hacked upon mhonarcvir (blog.NetBSD.org, monitor.NetBSD.org, rt.NetBSD.org)
Apache, with Apache Roller on tomcat on native openjdk for blog, Xymon for monitor and rt (what a surprise
) for rt. rt is used as coordination tool of a few teams and restricted to members of those teams.morden (ftp.NetBSD.org, rsync.NetBSD.org, back-end for cdn.NetBSD.org)
the ftp, http and rsync function themselves are fairly straightforward. It runs a few automatic updates for the src and pkgsrc regions that generate the daily CVS update mails and do a bunch of checks on pkgsrc, too.nyftp.NetBSD.org (back-end for nycdn.NetBSD.org)
ftp, http and rsync, fairly dumb. It's situated at Columbia University, hence the 'ny' in the nameanoncvs.NetBSD.org
offers anoncvs via ssh and pserver, plus rsync of the cvs repository, using port redirectsanonhg.NetBSD.org
anonymous Mercurial service, experimental
non-public services:
cvs.NetBSD.org
the master CVS repository; only developers (TNF members) with valid account auth can connect here.hg.NetBSD.org
the master Mercurial repository, experimental; only developers (TNF members) with valid account auth can connect here.build.NetBSD.org (aka b45) + b41-b48
build is the coordinator/manager of the build workers, and they produce the NetBSD-daily contents (situated at Columbia University)franklin.NetBSD.org
the backup server, basically lots'o disk storing encrypted dumpsbabylon4.NetBSD.org @WWU, babylon5.NetBSD.org @Regensburg
the TNF-run anita checks run on thesesheridan.NetBSD.org
Xen server running vir, and a few smaller administrative functionsxenhost.NetBSD.org
Xen server running mollari, hg and anonhg, the experiment-with-Mercurial systemslochley.NetBSD.org
situated at WWU, runs the repo conversions under joerg@'s directiontessa.NetBSD.org
a webserver for finance-exec situated at WWUshadow.NetBSD.org
the i386 + x86_64, 9.0 + 10.0 package builder situated at WWUvictory.NetBSD.org
the evbarm* and aarch64 package builder situated at WWUconsole servers at TastyLime, Columbia University and WWU
these are small devices (two of them evbarm-based) with USB2Serials and conserver8. conserver is most approvedcole.NetBSD.de
off-site, off-continent backup for the most precious data in case ca.us gets the big one. Racked at Regensburg, Germany, owned by spz@archive.NetBSD.de
back-end for archive.NetBSD.org, a VM on colewip.pkgsrc.org
the git server for pkgsrc-WIP, a VM on cole
Sun PGX32
This is a re-badged Tech Source Raptor GFX 8P, which in turn is a bog standard 3D Labs Permedia 2 with Sun firmware in ROM. The board has 8MB RAM and a 33MHz/32bit PCI interface.
OpenFirmware name: TSI,GFXP
Common header:
0x00: 0x00093d3d 0x02900006 0x03800001 0x0000ff00
Vendor Name: 3D Labs (0x3d3d)
Device Name: GLINT Permedia 2V (0x0009)
There is nothing really remarkable about this card, Xorg's ?glint driver Just Works(tm) and the pm2fb driver provides an accelerated console.
The firmware is rather buggy:
- the linebytes property is always the same as width, even with more than 8 bit colour depth
- some property names have trailing spaces
- the ?color! method does nothing so we can't change the palette in 8 bit
There are workarounds in genfb and pm2fb for the first two problems, and pm2fb doesn't depend on firmware calls to access palette registers.
haad's wiki page
Things to blame me for:
- NetBSD LVM
- device-mapper driver in kernel
- NetBSD ZFS port
- some changes in proplib
NetBSD Kernel Debugger tutorial
NetBSD ZFS porting guide
?NetBSD zfs howto
My own todo list
Iain Hibbert
The following list is a test of the man template:
And the pkg template for linking to pkgsrc.se:
and linking to problem reports using the pr template:
Description
Use this template to create a man page link. The template can use four parameters:
name- This required parameter is the name of the manpage.section- This recommended parameter is the manpage section.arch- This optional parameter is the machine architecture.collection- This optional parameter refers to the NetBSD version (e.g. "NetBSD-10.0").
Examples
Link to ls man page:
[[!template id=man name="ls"]]
Link to ls(1) man page, with section:
[[!template id=man name="ls" section="1"]]
Link to ls(1) man page, specifying section and architecture:
[[!template id=man name="ls" section="1" arch="i386"]]
Link to ls(1) man page, specifying section, architecture and collection:
[[!template id=man name="ls" section="1" arch="i386" collection="NetBSD-5.0"]]
Description
Use this template to create a Problem Report link. The template uses one parameter:
- number - This required parameter is the Problem Report number.
Examples
Link to PR #42245:
[[!template id=pr number=42245]]
Description
Use this template to create a link to a pkgsrc's package. The template uses two parameters:
- category - This required parameter is the category of the package.
- name - This required parameter is the name of the package.
Examples
Link to www/apache package page:
[[!template id=pkg category="www" name="apache"]]
CRIME
This is the rendering engine, memory controller etc. found in SGI's ?O2 workstations. NetBSD has hardware accelerated drivers for both the kernel ( ?crmfb ) and ?Xorg ( ?xf86-video-crime ).
Video memory is allocated from main memory in chunks of 64KB which, depending on pixel size, result in 128x128, 256x128 or 512x128 tiles. Output is handled by either ?GBE for the VGA port or ?mace and the AV module for composite video or s-video ( we don't support TV output yet ).
The drawing engine has two parts - the main Rendering Engine which supports all kinds of fancy operations including alpha blending, z-buffering and whatnot, and the Memory Transfer Engine which only supports simple fills and copies but does them really, really fast ( at memory bandwidth speed according to the docs we have ).
Both engines share a set of TLBs:
- Three TLBs map tiled buffers with up to 16x16 tiles. Entries are the upper 16 bit of each tile's physical address so tiles have to be 64KB-aligned.
- Two TLBs map linear buffers with 4KB-aligned pages, up to 128KB each.
- There are other TLBs for texture buffers, stencil buffers etc. but for now we don't really know how to use them.
All TLBs can only be written with 64bit-aligned writes, unaligned writes are ignored, writes smaller than 64bit result in the upper bits being written as zeroes. Reads can be any size with natural alignment.
Partial writes to at least a few other registers work though.
Sun SX
This is the rendering engine built into the ?SPARCstation 20's memory controller.
OpenPROM name: SUNW,SX
Sun used to call this a Pixel Processor, which is exactly what it is. As far as we know this thing doesn't have much in common with conventional blitters, there are no command or coordinate registers, instead there is a bunch of registers to point the engine at memory regions ( may or may not be a CG14 VSIMM ) and a port to feed it instructions. The instruction format is unknown, but from published papers we know the SX is some sort of SIMD processor with a non-trivial number of registers, so it could likely be used to accelerate composite operations. Unfortunately it can't read instructions from memory and as far as we know it doesn't have any kind or branch instructions so we always have to feed it instructions one by one using the main CPU ( and if this is indeed the only way to feed it instructions then branching instructions don't make any sense anyway ). So far there is no driver support for the SX in any open source operating system, drivers exist for Solaris and NEXTSTEP.
Fujitsu AG-10e
This is Frankenstein's monster of graphics cards. It's a double-wide, double-decked ?SBus device with three different graphics chips - each with its own memory, a high end RAMDAC and a DSP.
There is:
- a GLint 300SX with 2x 6MB framebuffer ( that's what the firmware says, the chip itself claims to have 16MB framebuffer ) and 16MB 'local buffer' - whatever that is, 3D Labs claims they can't find any docs but I doubt they even checked. This chip provides a 24bit true colour visual.
- an Imagine I128 with 4MB RAM, this chip provides an 8 bit visual.
- a Weitek P9100 with 2MB framebuffer, this chip provides WIDs
- an IBM RGB561 RAMDAC which supports a truckload of features and WID control over pretty much everything
- an Analog Devices DSP with its own memory, we have no clue what it's being used for
Evidently there is some sort of SBus-to-PCI bridge on the card, from the graphics chip listed above only the P9100 is known to exist as an ?SBus variant, and even that was probably an in-house hack done by Tadpole. We have a kernel driver for it ( agten at ?sbus ) which uses the I128 to provide an accelerated console and switches to the GLint's 24bit visual when X runs. The ?xf86-video-ag10e driver is mostly glue code to map framebuffer and registers via /dev/fb*, run the ?xf86-video-glint driver's 300SX support and deal with the different DAC.
mmm, a world of incompatible wikitext styles
Wiki page for Alistair Crooks (agc)
NetBSD Core Team - 1999 to present
NetBSD Foundation Director 2002-2003, 2004 to present
President of the NetBSD Foundation, 2005 to present
Things to blame me for:
- the du(1) and termcap(3) routines in Minix
- regular expression caching code in Postgres95 and PostgreSQL
- UTF-8 library and regular expression code
- pkgsrc
- user(8) - user and group management suite of utilities
- digest - ultra-portable message digest/hashing utility
- the portable iSCSI target
- ReFUSE - FUSE compatible, based on puffs
- ReFUSE-based file systems
- iSCSI userland initiator
- Google Summer of Code Mentoring
- Role-Based Access Control kernel
- netpgp - BSD-licensed privacy software
- NetBSD roadmaps
Future blame
- HKP server for netpgp keys
- iSCSI kernel-based initiator integration
- further netpgp-based software
Dr. Hubert 'hubertf' Feyrer
Visit my real homepage or check out my NetBSD blog.
More information is available on request.
Behold! For now I have a wiki page!
Blame for:
- raid(4) parity maps.
- The Xen block device backend in all its trampolined glory.
- Also, the Xen clock.
- The sparse kernel core dumps on i386.
- Assorted minor fixes.
- Probably stuff I'm forgetting.
TODO:
- Fix raidctl(8)
-moutput for RAID-0 sets. - Re-re-re-re-dust-off the raid(4) raid nested-autoconfigure thing and likewise.
- Trying to defer RAID sets until all the components show up is actually a bad idea.
- There's an order-of-configure field that could be automagically set, but that can be later.
- I probably also need to figure out wedge autodetection, but that can be later.
- tail(1) -r doesn't work on large files. FreeBSD seemed to have an acceptable fix when last I looked. (FIXME: send-pr this if it isn't already.)
- The curses bugs (FIXME: link the PRs) I ran across.
- I also had some disagreements with the keypad handling which might or might not be ruled an all-the-world-is-not-ncurses issue.
- xentimed(8), which doesn't exist yet but should.
- xbd(4) is still lacking a dump routine, I think?
- Also a man page, last I saw.
- Anyway, at one point I'd more or less figured this out, and I don't think that part of the interface has changed much.
- Speaking of which, if I went completely insane I could try to port libsa to Xen.
- Which actually isn't that insane, given that PV-GRUB exists.
- And speaking of that, I should probably write a “NetBSD on Linode et al.” howto that isn't insane.
The pages on The NetBSD Foundation's internal Kerberos deployment have been migrated to https://www.NetBSD.org/developers/kerberos.html.
Kerberos is a single sign-on authentication protocol, used by many organizations and natively supported by many applications including web browsers and mail readers.